SHORT MESSAGE SERVICE AND SUPPLEMENTARY SERVICES MESSAGES

[0002] TECHNICAL FIELD

[0003] This application is related to wireless communications.

[0004] BACKGROUND

[0005] Current efforts in the third generation partnership project

(3GPP) long term evolution (LTE) program aim to bring new technology, new architecture, and new methods to provide improved spectral efficiency, reduced latency, and better utilization of radio resource to bring faster user experiences and richer applications and services with lower cost. Enabling the traditional commercially viable wireless services, especially the short message service (SMS), would greatly enhance the acceptance of the LTE technology in the wireless service product market.

[0006] In the current LTE specification, the SMS service is either not fully defined or it depends on the Internet protocol (IP) multimedia service (IMS) based SMS service or the circuit switched (CS) fallback methodology, such that the overhead of development cost is large, the network service interactions are complex and the transport efficiency is low. For supplementary services (SS) in LTE, the supportability has yet to be defined and enabled.

[0007] It would be desired to provide methods and apparatus that enable SMS and SS in LTE with implementation and backbone routing simplicity, while achieving overall data transport efficiency.

[0008] SUMMARY

[0009] Methods and apparatus for communicating SMS and SS messages in an LTE network via evolved packet system (EPS) mobility management (EMM) over the LTE control plane are described. A radio resource control (RRC) connection signaling radio bearer (SRB) -2 may be used for SMS and SS transport over the LTE control plane between a wireless transmit/receive unit (WTRU) and a mobility management entity (MME). EMM interfaces and primitives are defined for actions towards SMS and SS entities for enabling SMS and SS services in LTE via the LTE control plane media. Message formats for SMS and SS message transport are also disclosed for sending SMS and SS messages within EMM uplink (UL) non-access stratum (NAS) transport and downlink (DL) NAS transport messages.

[0010] BRIEF DESCRIPTION OF THE DRAWINGS

[0011] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings wherein:

[0012] Figure 1 shows a wireless communication system including a

WTRU having a protocol entity architecture;

[0013] Figure 2 shows a wireless communication system with a WTRU having an alternate protocol entity architecture;

[0014] Figure 3 shows a procedure for supporting an outgoing SMS;

[0015] Figure 4 shows a procedure for supporting an incoming SMS;

[0016] Figure 5 shows call independent supplementary services supported using the systems of Figures 1 and 2;

[0017] Figure 6 shows an overall NAS message header format for EMM;

[0018] Figure 7 shows an EMM message UL/DL transport format;

[0019] Figure 8 shows an SMS and SS message header plus payload format;

[0020] Figure 9 shows an EMM message format supporting SMS and SS in LTE;

[0021] Figure 10 is a signaling diagram for a mobile terminated (MT)

SMS procedure; and

[0022] Figure 11 is a signaling diagram for an MT SS procedure. [0023] DETAILED DESCRIPTION

[0024] When referred to hereafter, the terminology "wireless transmit/receive unit (WTRU)" includes but is not limited to a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a computer, or any other type of user device capable of operating in a wireless environment. [0025] When referred to hereafter, the terminology "evolved Node-B

(eNodeB)" includes but is not limited to a base station, a site controller, an access point (AP), or any other type of interfacing device capable of operating in a wireless environment. [0026] Enabling SMS and SS over EMM

[0027] Figure 1 shows a wireless LTE communication system 100 including a WTRU 105, an evolved universal terrestrial radio access network (E-UTRAN) 110, an MME 115 and a mobile switching center (MSC)/visitor location register (VLR) 120. The E-UTRAN includes a plurality of eNodeBs. The system 100 provides EMM functionality in the WTRU 105 and the MME 115, and supports SMS and SS by accessing an EMM interface over an LTE C- plane media. The MSC/VLR 120 may be part of a global system for mobile communications (GSM) network or universal mobile telecommunications system (UMTS) network, and is considered to be in the CS domain. The E- UTRAN 110 and the MME 115 are part of an LTE network, which is considered to be in a packet switch (PS) domain. SMS traffic may be transferred over the control plane of the LTE network using a CS fallback mechanism or directly.

[0028] As shown in Figure 1, the WTRU 105 includes an SMS protocol entity 125, an SS protocol entity 130, a mobility management (MM) protocol entity 135, an EMM protocol entity 140 and an LTE RRC protocol entity 145. The EPS EMM protocol entity 140 in the WTRU 105 will forward SMS and SS requests/messages towards the LTE network via the LTE RRC protocol entity 145 and SRB 150. [0029] A corresponding functionality may exist on the LTE network side, (e.g., in a base station or a core network component). An LTE EMM protocol entity 155 in the MME 115 handles the forwarding and receiving of SMS and SS messages towards/from the traditional SMS or SS processing center, such as the MSC/VLR 120, via a serving gateway (SG) interface between the MME 115 and the MSC/VLR 120, and towards a service center (SC) (not shown) for SMS.

[0030] Logically, the SG interface is defined between the MME and VLR functional entities. The interface defined herein is between the existing connection management (CM) protocol entities (SMS and SS) and the new MM protocol entity, EMM, for LTE.

[0031] Figure 2 shows a wireless LTE communication system 200 including a WTRU 205 with an alternate protocol entity architecture. The WTRU 205 includes an SMS protocol entity 225, an SS protocol entity 230, an MM protocol entity 235, an EPS EMM protocol entity 240 and an LTE RRC protocol entity 245. However, unlike the protocol entity architecture of the WTRU 105 shown in Figure 1, the SMS protocol entity 225 and the SS protocol entity 230 do not communicate directly with the EMM protocol entity 240, but instead only communicate with the MM protocol entity 235. [0032] The protocol entity architecture of Figure 2 also differs from that of Figure 1 by the direct interface between the MM protocol entity 235 and the EMM protocol entity 240. This direct interface provides SMS and SS in LTE and legacy access networks. When an SMS/SS message is created, it will be sent to the MM protocol entity 235 in order to be delivered. Upon reception of the SMS/SS message, the MM protocol entity 235 checks for the existing radio access technology (RAT) of the terminating WTRU. If the existing RAT is either GSM/enhanced data rates for GSM evolution (EDGE) radio access network (GERAN) or UTRAN, the MM protocol entity 235 continues according to known procedures. However, in case the existing RAT is E-UTRAN/LTE, the MM protocol entity 235 contacts the EMM protocol entity 240 and delivers the higher layer information (the SMS/SS message). From this point forward, the defined procedures for EMM SMS/SS delivery are then followed.

[0033] The interface between the MM protocol entity 235 and the EMM protocol entity 240 may have a set of control primitives and data carriage containers (i.e., data primitives). The control primitives may be used for translating SMS and MM primitives sent to the EMM protocol entity 240 for session/connection establishment and error indication.

[0034] Enhanced EMM (E-EMM) Interface for SMS

[0035] The SMS protocol entities 125 and 225, (also referred to herein as an enhanced SMS (E-SMS) since the underlying RAT is LTE), communicate with a corresponding peer entity, (in the WTRU and the MME), using an

EMM interface over an LTE control plane.

[0036] When an SMS message is to be sent and an EMM connection

(through the LTE RRC connection) does not exist at the time, one must be established at the request of the E-SMS on the originating end.

[0037] The primitives and interactions used for SMS/EMM state manipulation between the E-SMS and the EMM include:

1) SMS-EMM-Conn-Est-Req (from E-SMS to EMM for requesting establishment of a connection for outgoing SMS if no connection currently exists);

2) SMS-EMM-Conn-Est-Cnf (from EMM to E-SMS to confirm the connection establishment request);

3) SMS-EMM-Conn-Est-Ind (from EMM to E-SMS for indicating incoming SMS message); and

4) SMS-EMM-Conn-Est-Rsp (from E-SMS to EMM for responding to the incoming SMS message indication).

[0038] Connection release primitives are also defined and include the following:

1) SMS-EMM-Rel-Req (from E-SMS to EMM for requesting release of established connection); 2) SMS- EMM-ReI- Cnf (from EMM to E-SMS for confirming the release request);

3) SMS-EMM-Rel-Ind (from EMM to E-SMS for indicating a connection release); and

4) SMS-EMM-Rel-Rsp (from E-SMS to EMM for responding to the connection release indication).

[0039] The data primitives between the E-SMS and EMM are also defined and include the following:

1) SMS-EMM-Data-Req (a primitive for carrying an SMS message from E-SMS to EMM); and

2) SMS-EMM-Data-Ind (a primitive for carrying an SMS message from EMM to E-SMS).

[0040] The following control protocol (CP) messages are used to transparently support the transportation of the SMS messages between the E- SMSs on the WTRU and the network component, (i.e., the MSC): CP-Data, CP-ACK and CP-Error messages.

[0041] Figure 3 shows signaling that occurs between an E-SMS protocol entity 305 and an EMM protocol entity 310 in a wireless communication system 300. As shown in Figure 3, when originating an SMS, the E-SMS 305 entity checks with the EMM 310 sending an SMS-EMM-Conn-Est-Req message 315 to the EMM protocol entity 310. The EMM protocol entity 310 in turn checks to see if it already has an EMM-connection over the LTE RRC connection. If that is the case, the EMM protocol entity 310 responds with an SMS-EMM-Conn-Est-Cnf message 320 back to the E-SMS protocol entity 305. If no EMM connection exists over the LTE RRC connection, the EMM protocol entity 310 triggers the LTE RRC to establish an RRC connection towards the currently attached E-UTRAN for "service request". When the RRC connection is successfully established, the EMM protocol entity 310 will then send an SMS-EMM-Conn-Est-Cnf message 320 back to the E-SMS 305. The outgoing SMS data activity may then proceed using Data-Req message 325 and Data- Ind message 330 to transport SMS messages. [0042] Figure 4 shows signaling that occurs between an E-SMS protocol entity 405 and an EMM protocol entity 410 in a wireless communication system 400. As shown in Figure 4, in the case of an incoming SMS, the EMM protocol entity 410 will be paged if no EMM/RRC connection towards the E-

UTRAN exists. As the EMM protocol entity 410 responds to the page for establishing an RRC connection, the EMM protocol entity 410 will indicate the

SMS event to the E-SMS protocol entity 405 via an SMS-EMM-Conn-Est-Ind message 415 and the E-SMS protocol entity 405 will respond with an SMS-

EMM-Conn-Est-Rsp message 420. The incoming SMS data activity may then proceed using Data-Req message 425 and Data-Ind message 430 to transport

SMS messages.

[0043] E-EMM Interface for SS

[0044] The SS protocol entities 130 and 230, (also referred to herein as an enhanced SS (E-SS) since the underlying RAT is LTE), communicate with a corresponding peer entity, (in the WTRU and the MME), using an EMM interface over an LTE control plane.

[0045] When an SS message is to be sent and an EMM session (through the LTE RRC connection) does not exist at the time, one must be established at the request of the E-SS on the originating end.

[0046] The primitives and interactions used for SS/EMM state manipulation between the E-SS and the EMM include:

1) SS-EMM-Sess-Est-Req (from E-SS to EMM for requestingestablishment of a session for outgoing SS if no session currently exists);

2) SS-EMM-Sess-Est-Cnf (from EMM to E-SS to confirm of the session establishment request);

3) SS-EMM-Sess-Est-Ind (from EMM to E-SS for indicating an incoming SS message); and

4) SS-EMM-Sess-Est-Rsp (from E-SS to EMM for responding to the incoming SS message indication). [0047] Session release primitives are also defined and include the following:

1) SS-EMM-Rel-Req (from E-SS to EMM for requesting release of established session);

2) SS-EMM-Rel-Cnf (from EMM to E-SS for confirming the release request);

3) SS-EMM-Rel-Ind (from EMM to E-SS for indicating a session release); and

4) SS-EMM-Rel-Rsp (from E-SS to EMM for responding to the session release indication).

[0048] The data primitives between the E-SS and the EMM are also defined and include the following:

1) SS-EMM-Data-Req (a primitive for carrying a SS message from E-SS to EMM); and

2) SS-EMM-Data-Ind (a primitive carrying a SS message from EMM to E-SS).

[0049] For SS in LTE, only the call independent SS messages will be supported for the LTE standard, since CS call service is not supported in release-8 LTE. Currently, the following call independent SS are supported and shown in Figure 5.

[0050] Given that the SS message header construction is the same as those for SMS (see Figure 8), the above supported call independent SS messages will be inserted at the octet-9 (with the SS message header) in the

EMM message shown in Figure 9.

[0051] Encapsulation Mechanism for SMS and SS transport with EMM

[0052] Base EMM Message Format for Encapsulation

[0053] The EMM message for transporting the SMS or SS is generated by including the SMS message or the SS message (shown in Figure 8) in an information element (IE) of the EMM UL NAS transport message or DL NAS transport message (shown in Figure 7), which is then encapsulated into the

NAS message header of the EMM message shown in Figure 6. [0054] The NAS message shown in Figure 7 is either a UL NAS transport message or a DL NAS transport message that carries the SMS or SS message for the intended service. Additional details of the header and body of the NAS transport message are shown in Figure 9. [0055] SMS and SS Message Header

[0056] The currently used CM level SMS messages, (CP-Data, CP-ACK and CP- Error), as well as the SS messages may have the header format shown in Figure 8.

[0057] In Figure 8, the transaction-identifier field may be used for SMS and SS as a field for their original transaction identifiers. The protocol discriminator field may be used to identify the encapsulated SMS or SS or others. The message type field may be used to indicate a type of each individual SMS or SS messages.

[0058] EMM Message Format for Encapsulating SMS and SS Messages

[0059] The combined header on EMM to support SMS or SS plus the message body, (i.e., the payload), is illustrated in Figure 9. With this message format, the LTE access stratum control plane bearers are used to carry the SMS or the SS traffic between the WTRU and the network. In a first scenario, a direct interface between the SMS/SS entities and the EMM entity at the WTRU exist. Once the EMM session/connection is established with the E- UTRAN and MME via the LTE RRC connection, the WTRU may use the EMM and RRC interface through to the LTE SRB-2 as the SMS/SS transporting media. The SRB-2 (signal radio bearer 2) is mapped over the bidirectional logical channel DCCH (dedicated control channel), which is over the UL/DL transport channel UL-SCH (uplink shared channel)/DL-SCH (downlink shared channel), which is then mapped over the physical channel PUSCH (physical uplink shared channel)/PDSCH (physical downlink shared channel) in LTE. If an RRC connection does not exist in a mobile originated (MO) SMS scenario, the EMM protocol entity triggers the RRC protocol entity to establish an RRC connection. [0060] In one scenario, the SMS protocol entity 125 in the WTRU 105 shown in Figure 1 generates an SMS message using the header and payload shown in Figure 8, and sends the SMS message to the EMM protocol entity 140. The EMM protocol entity 140 then formats a UL/DL NAS transport message using the header format shown in Figure 7, whereby the SMS message is inserted in the NAS message body IE of the UL/DL NAS transport message. The UL/DL NAS transport message is then encapsulated in the NAS message field of the EMM message shown in Figure 6, and is forwarded to the RRC protocol entity 145. The RRC protocol entity 145 then formats an UL/DL information transfer message to include the EMM message, and transmits the UL/DL information transfer message over the SRB 150. [0061] In another scenario, the SS protocol entity 130 in the WTRU 105 shown in Figure 1 generates an SS message using the header and payload shown in Figure 8, and sends the SS message to the EMM protocol entity 140. The EMM protocol entity 140 then formats a UL/DL NAS transport message using the header format shown in Figure 7, whereby the SS message is inserted in the NAS message body IE of the UL/DL NAS transport message. The UL/DL NAS transport message is then encapsulated in the NAS message field of the EMM message shown in Figure 6, and is forwarded to the RRC protocol entity 145. The RRC protocol entity 145 then formats an UL/DL information transfer message to include the EMM message, and transmits the UL/DL information transfer message over the SRB 150.

[0062] Figure 10 shows a signaling diagram for an MT SMS procedure using the primitives defined above. As shown in Figure 10, a WTRU 1000 includes an SMS protocol entity 1005, an EMM protocol entity 1010 and an RRC protocol entity 1015. A network 1020 is illustrated as a single entity for simplicity.

[0063] In an MT SMS scenario, the network 1020 may send the WTRU

1000 a page 1025 while the WTRU 1000 is in an idle state, and the WTRU 1000 may respond with a service-request 1030 (with paging response) for establishing the RRC connection. The EMM protocol entity 1010 may then send and receive the SMS message using the EMM DL NAS transport message and UL NAS transport message. The RRC protocol entity 1015 uses an RRC DownlinklnformationTransfer message 1135 and an RRC UplinklnformationTransfer message 1140 for the transportation. [0064] Figure 11 shows a signaling diagram for an MT SS procedure using the primitives defined above. As shown in Figure 11, a WTRU 1100 includes an SS protocol entity 1105, an EMM protocol entity 1110 and an RRC protocol entity 1115. A network 1120 is illustrated as a single entity for simplicity.

[0065] In an MT SMS scenario, the network 1120 may send the WTRU

1100 a page 1125 while the WTRU 1010 is in an idle state, and the WTRU 1100 may respond with a service request 1130 (with paging response) for establishing the RRC connection. The EMM protocol entity 1110 may then send and receive the SS message using the EMM DL NAS transport message in an RRC DownlinklnformationTransfer message 1135, or an EMM UL NAS transport message in the RRC UplinklnformationTransfer message 1140. [0066] The features described above will be now summarized by referring to Figure 1.

[0067] In one scenario, the WTRU 105 of Figure 1 communicates SMS messages by using the SMS protocol entity 125 to request the EMM protocol entity 140 to send an SMS message. The EMM protocol entity 140 then initiates a procedure to send a UL NAS transport message including an IE containing the SMS message. The SMS protocol entity 125 may send the SMS message to the EMM protocol entity 140. The EMM protocol entity 140 formats the UL NAS transport message to include the SMS message, encapsulates the UL NAS transport message in an EMM message, and sends the EMM message to the LTE RRC protocol entity 145. The LTE RRC protocol entity 145 formats a UL information transfer message to include the EMM message, and transmits the UL information transfer message over an SRB. The UL information transfer message may be transmitted to the MME 115. [0068] In another scenario, the WTRU 105 of Figure 1 communicates

SMS messages by using the EMM protocol entity 140 to receive a DL NAS transport message including an IE containing an SMS message. The EMM protocol entity 140 forwards the SMS message to the SMS protocol entity 125. The RRC protocol entity 145 may receive a DL information transfer message, extract the DL NAS transport message from the DL information transfer message, and forward the DL NAS transport message to the EMM protocol entity 140. The EMM protocol entity 140 then extracts at least one NAS message header from the DL NAS transport message. The RRC protocol entity may receive the DL information transfer message from an MME. [0069] In yet another scenario, the WTRU 105 of Figure 1 communicates

SS messages by using the SS protocol entity 130 to request the EMM protocol entity 140 to send an SS message. The EMM protocol entity 140 then initiates a procedure to send a UL NAS transport message including an IE containing the SS message. The SS protocol entity 130 may send the SS message to the EMM protocol entity 140. The EMM protocol entity 140 formats the UL NAS transport message to include the SS message, encapsulates the UL NAS transport message in an EMM message, and sends the EMM message to the LTE RRC protocol entity 145. The LTE RRC protocol entity 145 formats a UL information transfer message to include the EMM message, and transmits the UL information transfer message over an SRB. The UL information transfer message may be transmitted to the MME 115.

[0070] In yet another scenario, the WTRU 105 of Figure 1 communicates

SS messages by using the EMM protocol entity 140 to receive a DL NAS transport message including an IE containing an SS message. The EMM protocol entity 140 forwards the SS message to the SS protocol entity 130. The RRC protocol entity 145 may receive a DL information transfer message, extract the DL NAS transport message from the DL information transfer message, and forward the DL NAS transport message to the EMM protocol entity 140. The EMM protocol entity 140 then extracts at least one NAS message header from the DL NAS transport message. The RRC protocol entity may receive the DL information transfer message from an MME. [0071] Embodiments

1. A method of communicating short message service (SMS) messages, the method comprising: an SMS protocol entity requesting an evolved packet system (EPS) mobility management (EMM) protocol entity to send an SMS message; and the EMM protocol entity initiating a procedure to send an uplink (UL) non-access stratum (NAS) transport message including an information element (IE) containing the SMS message.

2. The method of embodiment 1 further comprising: the SMS protocol entity sending the SMS message to the EMM protocol entity; the EMM protocol entity formatting the UL NAS transport message to include the SMS message, encapsulating the UL NAS transport message in an EMM message, and sending the EMM message to a radio resource control (RRC) protocol entity; and the RRC protocol entity formatting a UL information transfer message to include the EMM message, and transmitting the UL information transfer message over a signaling radio bearer (SRB).

3. The method of embodiment 2 wherein the UL information transfer message is transmitted to a mobility management entity (MME).

4. A method of communicating short message service (SMS) messages, the method comprising: an evolved packet system (EPS) mobility management (EMM) protocol entity receiving a downlink (DL) non-access stratum (NAS) transport message including an information element (IE) containing an SMS message; and the EMM protocol entity forwarding the SMS message to an SMS protocol entity.

5. The method of embodiment 4 further comprising: a radio resource control (RRC) protocol entity receiving a DL information transfer message, removing the DL NAS transport message from the DL information transfer message, and forwarding the DL NAS transport message to the EMM protocol entity; and the EMM protocol entity removing at least one NAS message header from the DL NAS transport message.

6. The method of embodiment 5 wherein the RRC protocol entity receives the DL information transfer message from a mobility management entity (MME).

7. A method of communicating supplementary services (SS) messages, the method comprising: an SS protocol entity requesting an evolved packet system (EPS) mobility management (EMM) protocol entity to send an SS message; and the EMM protocol entity initiating a procedure to send an uplink (UL) non-access stratum (NAS) transport message including an information element (IE) containing the SS message.

8. The method of embodiment 7 further comprising: the SS protocol entity sending the SMS message to the EMM protocol entity; the EMM protocol entity formatting the UL NAS transport message to include the SS message, encapsulating the UL NAS transport message in an EMM message, and sending the EMM message to a radio resource control (RRC) protocol entity; and the RRC protocol entity formatting a UL information transfer message to include the EMM message, and transmitting the UL information transfer message over a signaling radio bearer (SRB).

9. The method of embodiment 8 wherein the UL information transfer message is transmitted to a mobility management entity (MME).

10. A method of communicating supplementary services (SS) messages, the method comprising: an evolved packet system (EPS) mobility management (EMM) protocol entity receiving a downlink (DL) non-access stratum (NAS) transport message including an information element (IE) containing an SS message; and the EMM protocol entity forwarding the SS message to an SS protocol entity.

11. The method of embodiment 10 further comprising: a radio resource control (RRC) protocol entity receiving a DL information transfer message, removing the DL NAS transport message from the DL information transfer message, and forwarding the DL NAS transport message to the EMM protocol entity; and the EMM protocol entity removing at least one NAS message header from the DL NAS transport message.

12. The method of embodiment 11 wherein the RRC protocol entity receives the DL information transfer message from a mobility management entity (MME).

13. A wireless transmit/receive unit (WTRU) for communicating short message service (SMS) messages, the WTRU comprising: an SMS protocol entity configured to generate a request to send an SMS message; and an evolved packet system (EPS) mobility management (EMM) protocol entity configured to initiate a procedure to send an uplink (UL) non-access stratum (NAS) transport message including an information element (IE) containing the SMS message in response to the request.

14. The WTRU of embodiment 13 wherein the EMM protocol entity is further configured to format the UL NAS transport message to include the SMS message, and encapsulate the UL NAS transport message in an EMM message.

15. The WTRU of embodiment 14 further comprising: a radio resource control (RRC) protocol entity configured to receive the EMM message from the EMM protocol entity, format a UL information transfer message to include the EMM message, and transmit the UL information transfer message over a signaling radio bearer (SRB).

16. The WTRU of embodiment 15 wherein the UL information transfer message is transmitted to a mobility management entity (MME).

17. A wireless transmit/receive unit (WTRU) for communicating short message service (SMS) messages, the WTRU comprising: an SMS protocol entity; and an evolved packet system (EPS) mobility management (EMM) protocol entity configured to receive a downlink (DL) non-access stratum (NAS) transport message including an information element (IE) containing an SMS message and forwarding the SMS message to the SMS protocol entity.

18. The WTRU of embodiment 17 further comprising: a radio resource control (RRC) protocol entity configured to receive a DL information transfer message, extract the DL NAS transport message from the DL information transfer message, and forward the DL NAS transport message to the EMM protocol entity.

19. The WTRU of embodiment 18 wherein the RRC protocol entity receives the DL information transfer message from a mobility management entity (MME).

20. A wireless transmit/receive unit (WTRU) for communicating supplementary services (SS) messages, the WTRU comprising: an SS protocol entity configured to generate a request to send an SS message; and an evolved packet system (EPS) mobility management (EMM) protocol entity configured to initiate a procedure to send an uplink (UL) non-access stratum (NAS) transport message including an information element (IE) containing the SMS message in response to the request.

21. The WTRU of embodiment 20 wherein the EMM protocol entity is further configured to format the UL NAS transport message to include the SS message, and encapsulate the UL NAS transport message in an EMM message. 22. The WTRU of embodiment 21 further comprising: a radio resource control (RRC) protocol entity configured to receive the EMM message from the EMM protocol entity, format a UL information transfer message to include the EMM message, and transmit the UL information transfer message over a signaling radio bearer (SRB).

23. The WTRU of embodiment 22 wherein the UL NAS transport message is transmitted to a mobility management entity (MME).

24. A wireless transmit/receive unit (WTRU) for communicating supplementary services (SS) messages, the WTRU comprising: an SS protocol entity; and an evolved packet system (EPS) mobility management (EMM) protocol entity configured to receive a downlink (DL) non-access stratum (NAS) transport message including an information element (IE) containing an SS message and forwarding the SS message to the SS protocol entity.

25. The WTRU of embodiment 24 further comprising: a radio resource control (RRC) protocol entity configured to receive a DL information transfer message, extract the DL NAS transport message from the DL information transfer message, and forward the DL NAS transport message to the EMM protocol entity.

26. The WTRU of embodiment 25 wherein the RRC protocol entity receives the DL information transfer message from a mobility management entity (MME).

[0072] Although features and elements are described above in particular combinations, each feature or element can be used alone without the other features and elements or in various combinations with or without other features and elements. The methods or flow charts provided herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable storage medium for execution by a general purpose computer or a processor. Examples of computer-readable storage mediums include a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). [0073] Suitable processors include, by way of example, a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), and/or a state machine.

[0074] A processor in association with software may be used to implement a radio frequency transceiver for use in a wireless transmit receive unit (WTRU), user equipment (UE), terminal, base station, radio network controller (RNC), or any host computer. The WTRU may be used in conjunction with modules, implemented in hardware and/or software, such as a camera, a video camera module, a videophone, a speakerphone, a vibration device, a speaker, a microphone, a television transceiver, a hands free headset, a keyboard, a Bluetooth® module, a frequency modulated (FM) radio unit, a liquid crystal display (LCD) display unit, an organic light- emitting diode (OLED) display unit, a digital music player, a media player, a video game player module, an Internet browser, and/or any wireless local area network (WLAN) or Ultra Wide Band (UWB) module.