Method and apparatus for communicating short message service and supplementary services messages

Short message service and additional service message communication method and device

This application is related to wireless communication.

The current goal of the Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) project is to introduce new technologies, new architectures, and new methods to provide improved spectrum efficiency, reduced latency, and better radio resources Utilize, thereby bringing faster user experience and richer applications and communications at a lower cost. Allowing traditional commercially viable wireless services (especially short message service (SMS)) will greatly increase the acceptance of LTE technology in the wireless service product market.

In the current LTE specification, the SMS service is either not fully defined, or depends on the SMS service based on Internet Protocol (IP) Multimedia Service (IMS) or adopts the fallback method of circuit switching (CS). This makes the development cost huge, the network service interaction is complicated, and the transmission efficiency is low. For additional services (SS) in LTE, it has been decided to define and activate its support capabilities.

It is desirable to provide a method and equipment that can enable SMS and SS in LTE to have simpler implementation and main link routing while achieving overall data transmission efficiency.

Describes the method and equipment for transmitting SMS and SS messages in the LTE network via the Evolved Packet System (EPS) Mobility Management (EMM) on the LTE control plane. The radio resource control (RRC) connection signaling radio bearer (SRB)-2 can be used for SMS and SS transmission on the LTE control plane between a wireless transmit/receive unit (WTRU) and a mobility management entity (MME). The EMM interface and primitives are defined for the behavior towards SMS and SS entities to allow SMS and SS services via LTE control plane media in LTE. It also reveals the message format of SMS and SS message transmission to send SMS and SS messages in EMM uplink (UL) non-access stratum (NAS) transmission, and send downlink (DL) NAS transmission messages.

The term "wireless transmit/receive unit (WTRU)" mentioned below includes but is not limited to user equipment (UE), mobile station, fixed or mobile subscriber unit, pager, cell phone, personal digital assistant (PDA), computer or Any other type of user equipment capable of operating in a wireless environment.

The term "evolved node-B (eNodeB)" mentioned below includes, but is not limited to, base stations, site controllers, access points (APs), or any other types of peripheral devices that can operate in a wireless environment.

Allow SMS and SS through EMM Figure 1 shows a wireless LTE communication system 100, which includes a WTRU 105, an evolved universal terrestrial radio access network (E-UTRAN) 110, an MME 115, and a mobile switch Center (MSC)/Visitor Location Register (VLR) 120. E-UTRAN includes multiple eNodeBs. The system 100 provides EMM functionality in the WTRU 105 and MME 115, and supports SMS and SS by accessing the EMM interface on LTE C-plane media. The MSC/VLR 120 may be a part of a Global System for Mobile Communications (GSM) network or a Universal Mobile Telecommunications System (UMTS) network, and is considered to be in the CS domain. E-UTRAN 110 and MME 115 are part of the LTE network and are considered to be in the packet switching (PS) domain. The SMS service can be delivered on the control plane of the LTE network using the CS inefficient mechanism or directly.

As shown in Figure 1, the WTRU 105 includes an SMS agreement entity 125, an SS agreement entity 130, a mobility management (MM) agreement entity 135, an EMM agreement entity 140, and an LTE RRC agreement entity 145. The EPS EMM agreement entity 140 in the WTRU 105 will forward SMS and SS requests/messages to the LTE network via the LTE RRC agreement entity 145 and the SRB 150.

The corresponding functionality can exist on the LTE network side (for example, in the base station or in the core network element). The LTE EMM protocol entity 155 in the MME 115 forwards SMS and SS messages to/from a traditional SMS or SS processing center (such as MSC/VLR 120) via the service gateway (SG) interface between the MME 115 and the MSC/VLR 120 And receive, and forward and receive the SMS to a service center (SC) (not shown).

Logically, the SG interface is defined between the MME and VLR functional entities. The interface defined here lies between the existing connection management (CM) agreement entities (SMS and SS) and the new MM agreement entity (ie EMM) of LTE.

Figure 2 shows a wireless LTE communication system 200 including a WTRU 205 with an alternative agreement entity architecture. The WTRU 205 includes an SMS agreement entity 225, an SS agreement entity 230, an MM agreement entity 235, an EPS EMM agreement entity 240, and an LTE RRC agreement entity 245. However, unlike the agreement entity architecture of the WTRU 105 shown in Figure 1, the SMS agreement entity 225 and the SS agreement entity 230 do not directly communicate with the EMM agreement entity 240, but only communicate with the MM agreement entity 235. .

The difference between the agreement entity architecture of FIG. 2 and FIG. 1 lies in the direct interface between the MM agreement entity 235 and the EMM agreement entity 240. This direct interface provides SMS and SS in LTE and traditional access networks. When the SMS/SS message is created, it will be sent to the MM agreement entity 235 to be delivered. Once the SMS/SS message is received, the MM agreement entity 235 checks the existing radio access technology (RAT) of the terminal WTRU. If the existing RAT is GSM/Enhanced Data Rate for GSM Evolution (EDGE) Radio Access Network (GERAN) or UTRAN, the MM protocol entity 235 continues to execute according to the known process. However, when the existing RAT is E-UTRAN/LTE, the MM protocol entity 235 contacts the EMM protocol entity 240 and transmits higher-level information (SMS/SS messages). From then on, the process defined for EMM SMS/SS delivery will be followed.

The interface between the MM protocol entity 235 and the EMM protocol entity 240 may have a set of control primitives and a data carrier container (that is, data primitives). The control primitives can be used to translate SMS and MM primitives sent to the EMM agreement entity 240, where the SMS and MM primitives are used for session/connection establishment and error indication.

The enhanced EMM (E-EMM) interface of SMS SMS protocol entities 125 and 225 (here also called enhanced SMS (E-SMS), this is because the basic RAT is LTE) and the corresponding peer entities on the LTE control plane (In WTRU and MME) Use the EMM interface for communication.

When the SMS message will be sent and the EMM connection (via LTE RRC connection) does not exist at this time, an EMM connection must be established under the E-SMS request on the initiator.

The primitives and interactions used for the SMS/EMM status operation between E-SMS and EMM include: 1) SMS-EMM-Conn-Est-Req (from E-SMS to EMM, used for connections that do not currently exist In case of request to establish a connection for exporting SMS); 2) SMS-EMM-Conn-Est-Cnf (from EMM to E-SMS, used to confirm the connection establishment request); 3) SMS-EMM-Conn-Est-Ind (From EMM to E-SMS, used to indicate the entered SMS message); and 4) SMS-EMM-Conn-Est-Rsp (from E-SMS to EMM, used to respond to the entered SMS message instruction).

The connection release primitive is also defined, which includes the following primitives: 1) SMS-EMM-Rel-Req (from E-SMS to EMM, used to request the release of the established connection); 2) SMS-EMM-Rel-Cnf ( From EMM to E-SMS, used to confirm the release request); 3) SMS-EMM-Rel-Ind (from EMM to E-SMS, used to indicate connection release); and 4) SMS-EMM-Rel-Rsp (from E-SMS to EMM, used to respond to the connection release instruction).

It also defines the data primitives between E-SMS and EMM, which includes the following primitives: 1) SMS-EMM-Data-Req (primitives used to carry SMS messages from E-SMS to EMM); and 2 ) SMS-EMM-Data-Ind (a primitive used to carry SMS messages from EMM to E-SMS).

The following control protocol (CP) messages are used to transparently support the transmission of SMS messages between the E-SMS on the WTRU and the network element (ie MSC): (CP-Data (CP-data), CP-ACK, and CP -Error (CP-error) message).

Figure 3 shows the signaling that occurs between the E-SMS agreement entity 305 and the EMM agreement entity 310 in the wireless communication system 300. As shown in Figure 3, when an SMS is initiated, the E-SMS 305 entity sends an SMS-EMM-Conn-Est-Req message 315 to the EMM agreement entity 310 to check the EMM 310. The EMM agreement entity 310 in turn checks whether it already has an EMM connection on the LTE RRC connection. If so, the EMM agreement entity 310 sends back an SMS-EMM-Conn-Est-Cnf message 320 to the E-SMS agreement entity 305 as a response. If there is no EMM connection on the LTE RRC connection, the EMM agreement entity 310 triggers the LTE RRC to establish an RRC connection to the currently connected E-UTRAN to perform a "service request". When the RRC connection is successfully established, the EMM agreement entity 310 will then send back an SMS-EMM-Conn-Est-Cnf message 320 to the E-SMS 305. The output SMS data activity can then use the Data-Req (data-Req) message 325 and the Data-Ind (data-Ind) message 330 to transmit the SMS message.

Figure 4 shows the signaling that occurs between the E-SMS agreement entity 405 and the EMM agreement entity 410 in the wireless communication system 400. As shown in Figure 4, in the case of incoming SMS, if there is no EMM/RRC connection towards E-UTRAN, the EMM agreement entity 410 will be paged. When the EMM agreement entity 410 responds to the paging to establish an RRC connection, the EMM agreement entity 410 will indicate the SMS event to the E-SMS agreement entity 405 via the SMS-EMM-Conn-Est-Ind message 415, and the E-SMS agreement entity 405 will respond with SMS-EMM-Conn-Est-Rsp message 420. Entering the SMS data activity can then be done using Data-Req message 425 and Data-Ind message 430 to transmit the SMS message.

SSs E-EMM interface SS agreement entities 130 and 230 (here also referred to as enhanced SS (E-SS), this is because the basic RAT is LTE) on the LTE control plane with the corresponding peer entities (in WTRU and MME Middle) Use the EMM interface for communication.

When the SS message is to be sent and the EMM session (connected via LTE RRC) does not exist at this time, an EMM session must be established under the E-SS request on the initiator.

The primitives and interactions used for the SS/EMM state operation between E-SS and EMM include: 1) SS-EMM-Sess-Est-Req (from E-SS to EMM, used for non-existent session In case of request to establish a session for outputting SS); 2) SS-EMM-Sess-Est-Cnf (from EMM to E-SS, used to confirm the session establishment request); 3) SS-EMM-Sess-Est-Ind (From EMM to E-SS, used to indicate the input SS message); and 4) SS-EMM-Sess-Est-Rsp (from E-SS to EMM, used to respond to the input SS message instruction).

The session release primitives are also defined, which include the following primitives: 1) SS-EMM-Rel-Req (from E-SS to EMM, used to request the release of established sessions); 2) SS-EMM-Rel-Cnf ( From EMM to E-SS, used to confirm the release request); 3) SS-EMM-Rel-Ind (from EMM to E-SS, used to indicate session release); and 4) SS-EMM-Rel-Rsp (from E-SS to EMM, used to respond to the session release instruction).

It also defines the data primitives between E-SS and EMM, which includes the following primitives: 1) SS-EMM-Data-Req (primitives used to carry SS messages from E-SS to EMM); and 2 ) SS-EMM-Data-Ind (a primitive used to carry SS messages from EMM to E-SS).

For SS in LTE, only call-independent SS messages are supported in the LTE standard. This is because the CS call service is not supported in LTE Release 8. Currently, the following call irrelevant SSs are supported and are shown in Figure 5.

Assuming that the SS message header structure is the same as the SMS message header structure (see Figure 8), the above-mentioned supported call-independent SS messages will be inserted into the octet-9 (with SS message header).

Encapsulation mechanism for SMS and SS transmission with EMM. The basic EMM message format used for encapsulation. The EMM message used to transmit SMS or SS is generated by the following process: The SMS message or SS message (shown in Figure 8) includes In the information element (IE) of the EMM UL NAS transmission message or DL NAS transmission message (shown in Figure 7), it is then encapsulated in the NAS message header of the EMM message shown in Figure 6.

The NAS message shown in Figure 7 is a UL NAS transmission message or a DL NAS transmission message carrying SMS or SS for a predetermined service. Figure 9 shows additional details of the header and body of the NAS transmission message.

SMS and SS message headers currently used CM-level SMS messages (CP-data, CP-ACK, CP-error) and SS messages may have the header format shown in Figure 8.

In Figure 8, the transaction-identification code field can be used for SMS and SS as the field for its initial transaction identification code. The protocol identifier field can be used to identify the packaged SMS or SS or others. The message type field can be used to indicate the type of each individual SMS or SS message.

EMM message format encapsulating SMS and SS messages Figure 9 shows the header (to support SMS or SS) combined on the EMM plus the message body (ie, the payload). By using this message format, the LTE access layer control plane bearer is used to carry SMS or SS traffic between the WTRU and the network. In the first case, there is a direct interface between the SMS/SS entity and the EMM entity at the WTRU. Once an EMM session/connection is established with E-UTRAN and MME via the LTE RRC connection, the WTRU can use the EMM and RRC interfaces up to LTE SRB-2 as the SMS/SS transmission medium. SRB-2 (Signal Radio Bearer 2) is mapped on the bidirectional logical channel DCCH (Dedicated Control Channel) on the UL/DL transmission channel UL-DCH (Uplink Shared Channel)/DL-SCH (Downlink Shared Channel) , The bidirectional logical channel DCCH is then mapped to the physical channel PUSCH (physical uplink shared channel)/PDSCH (physical downlink shared channel) in LTE. If there is no RRC connection in the case of mobile originated (MO) SMS, the EMM agreement entity triggers the RRC agreement entity to establish the RRC connection.

In one case, the SMS agreement entity 125 in the WTRU 105 shown in FIG. 1 uses the header and payload shown in FIG. 8 to generate an SMS message, and sends the SMS message to the EMM agreement entity 140. The EMM protocol entity 140 then uses the header format shown in Figure 7 to format the UL/DL NAS transmission message, whereby the SMS message is inserted into the NAS message body IE of the UL/DL NAS transmission message. The UL/DL NAS transmission message is then encapsulated in the NAS message field of the EMM message shown in Figure 6, and forwarded to the RRC protocol entity 145. Then the RRC agreement entity 145 formats the UL/DL information delivery message to include the EMM message, and transmits the UL/DL information delivery message on the SRB 150.

In another case, the SS agreement entity 130 in the WTRU 105 shown in FIG. 1 uses the header and payload shown in FIG. 8 to generate the SS message, and sends the SS message to the EMM agreement entity 140. Then the EMM protocol entity 140 uses the header format shown in Figure 7 to format the UL/DL NAS transmission message, so that the SS message is inserted into the NAS message body IE of the UL/DL NAS transmission message. Then the UL/DL NAS transmission message is encapsulated in the NAS message field of the EMM message shown in FIG. 6 and forwarded to the RRC agreement entity 145. Then the RRC agreement entity 145 formats the UL/DL information delivery message to include the EMM message, and transmits the UL/DL information delivery message on the SRB 150.

Figure 10 shows a signalling diagram for the MT SMS procedure using the primitives defined above. As shown in Figure 10, the WTRU 1000 includes an SMS agreement entity 1005, an EMM agreement entity 1010, and an RRC agreement entity 1015. The network 1020 is described as a single entity to make the presentation concise.

In the case of MT SMS, the network 1020 may send a paging 1025 to the WTRU 1000 when the WTRU 1000 is in an idle state, and the WTRU 1000 may respond with a service-request 1030 (using a paging response) to establish an RRC connection. Then the EMM protocol entity 1010 can use the EMM DL NAS transmission message and the UL NAS transmission message to send and receive SMS messages. The RRC protocol entity 1015 uses an RRC downlink information transfer (Downlink Information Transfer) message 1135 and an RRC uplink information transfer (Uplink Information Transfer) message 1140 for transmission.

Figure 11 shows a signaling diagram for the MT SS procedure using the primitives defined above. As shown in Figure 11, the WTRU 1100 includes an SS agreement entity 1105, an EMM agreement entity 1110, and an RRC agreement entity 1115. The network 1120 is described as a single entity to make the description concise.

In the case of MT SMS, the network 1120 may send a paging 1125 to the WTRU 1100 when the WTRU 1100 is in an idle state, and the WTRU 1100 may respond with a service request 1130 (using a paging response) to establish an RRC connection. Then the EMM protocol entity 1110 can use the EMM DL NAS transmission message in the RRC downlink information transfer message 1135 and the EMM UL NAS transmission message in the RRC uplink information transfer message 1140 to send or receive SS messages.

The features described above will now be summarized with reference to Figure 1.

In one case, the WTRU 105 of Figure 1 uses the SMS agreement entity 125 to send an SMS message to request the EMM agreement entity 140 to send the SMS message. Then the EMM protocol entity 140 initiates a process to send the UL NAS transmission message including the IE including the SMS message. The SMS agreement entity 125 can send an SMS message to the EMM agreement entity 140. The EMM protocol entity 140 formats the UL NAS transmission message to include the SMS message, encapsulates the UL NAS transmission message in the EMM message, and sends the EMM message to the LTE RRC protocol entity 145. The LTE RRC protocol entity 145 formats the UL information transmission message to include the EMM message, and transmits the UL information transmission message on the SRB. The UL information transfer message can be sent to the MME 115.

In another case, the WTRU 105 of Figure 1 uses the EMM protocol entity 140 to send SMS messages to receive DL NAS transmission messages including IEs containing the SMS message. The EMM agreement entity 140 forwards the SMS message to the SMS agreement entity 125. The RRC protocol entity 145 can receive the DL information transfer message, retrieve the DL NAS transmission message from the DL information transfer message, and forward the DL NAS transmission message to the EMM protocol entity 140. Then the EMM protocol entity 140 retrieves at least one NAS message header from the DL NAS transmission message. The RRC protocol entity can receive the DL information delivery message from the MME.

In another case, the WTRU 105 in Figure 1 requests the EMM protocol entity 140 to send the SS message by using the SS protocol entity 130 to send the SS message. Then the EMM protocol entity 140 initiates a process to send the UL NAS transmission message including the IE including the SS message. The SS agreement entity 130 may send the SS message to the EMM agreement entity 140. The EMM protocol entity 140 formats the UL NAS transmission message to include the SS message, encapsulates the UL NAS transmission message in the EMM message, and sends the EMM message to the LTE RRC protocol entity 145. The LTE RRC protocol entity 145 arranges the format of the UL information transmission message to include the EMM message, and transmits the UL information transmission message on the SRB. The UL information transfer message can be sent to the MME 115.

In another case, the WTRU 105 of FIG. 1 uses the EMM protocol entity 140 to transmit the SS message to receive the DL NAS transmission message including the IE including the SMS message. The EMM agreement entity 140 forwards the SS message to the SS agreement entity 130. The RRC protocol entity 145 can receive the DL information transfer message, retrieve the DL NAS transmission message from the DL information transfer message, and forward the DL NAS transmission message to the EMM protocol entity 140. Then the EMM protocol entity 140 retrieves at least one NAS message header from the DL NAS transmission message. The RRC protocol entity can receive the DL information delivery message from the MME.

Examples: 1. A method for transmitting a short message service (SMS) message, the method includes: an SMS protocol entity requests an evolved packet system (EPS) mobility management (EMM) protocol entity to send an SMS message; and the EMM protocol entity starts sending an uplink (UL) The procedure of the non-access stratum (NAS) to transmit a message. The UL NAS transmission message includes an information element (IE), and the IE contains the SMS message.

2. As the method described in embodiment 1, the method further includes: the SMS agreement entity sends the SMS message to the EMM agreement entity; the EMM agreement entity formats the UL NAS transmission message to include the SMS message, and The UL NAS transmission message is encapsulated in an EMM message, and the EMM message is sent to a radio resource control (RRC) protocol entity; and the RRC protocol entity formats the UL information transfer message to include the EMM message and sends it to the signaling The UL information transmission message is transmitted on the radio bearer (SRB).

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

4. A method for transmitting short message service (SMS) messages, the method includes: an evolved packet system (EPS) mobility management (EMM) protocol entity receives a downlink (DL) non-access stratum (NAS) transmission message, the The DL NAS transmission message includes an information element including the SMS message; and the EMM protocol entity forwards the SMS message to the SMS protocol entity.

5. As the method described in embodiment 4, the method further includes: a radio resource control (RRC) protocol entity receives a DL information transfer message, removes the DL NAS transmission message from the DL information transfer message, and transmits the DL NAS message Forward to the EMM protocol entity; and the EMM protocol entity removes at least one NAS message header from the DL NAS transmission message.

6. The method according to embodiment 5, wherein the RRC agreement entity receives the DL information transfer message from a mobility management entity (MME).

7. A method for transmitting an additional service (SS) message, the method comprising: an SS protocol entity requests an evolved packet system (EPS) mobility management (EMM) protocol entity to send an SS message; and the EMM protocol entity starts sending an uplink (UL) The procedure of the non-access stratum (NAS) to transmit a message. The UL NAS transmission message includes an information element (IE), and the IE contains the SS message.

8. As in the method of embodiment 7, the method further includes: the SS agreement entity sends the SS message to the EMM agreement entity; the EMM agreement entity formats the UL NAS transmission message to include the SS message, and The UL NAS transmission message is encapsulated in an EMM message, and the EMM message is sent to the Radio Resource Control (RRC) protocol entity; and the RRC protocol entity formats the UL information delivery message to include the EMM message and sends it to the signaling The UL information transmission message is transmitted on the radio bearer (SRB).

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

10. A method for transmitting an additional service (SS) message, the method includes: an evolved packet system (EPS) mobility management (EMM) protocol entity receives a downlink (DL) non-access stratum (NAS) transmission message, the The DL NAS transmission message includes an information element, and the information element includes the SS message; and the EMM protocol entity forwards the SS message to the SS protocol entity.

11. As the method described in embodiment 10, the method further includes: a radio resource control (RRC) protocol entity receives a DL information transfer message, removes the DL NAS transmission message from the DL information transfer message, and transmits the DL NAS message Forward to the EMM protocol entity; and the EMM protocol entity removes at least one NAS message header from the DL NAS transmission message.

12. The method according to embodiment 11, wherein the RRC agreement entity receives the DL information transfer message from a mobility management entity (MME).

13. A wireless transmit/receive unit (WTRU) for transmitting short message service (SMS) messages, the WTRU includes: an SMS protocol entity configured to generate a request for sending SMS messages; and an evolved packet system (EPS) mobile The EMM protocol entity is configured to initiate the process of sending uplink (UL) non-access stratum (NAS) transmission messages in response to the request. The UL NAS transmission message includes an information element (IE), and the IE Contain the SMS message.

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

15. The WTRU of embodiment 14, the WTRU further comprising: a radio resource control (RRC) protocol entity, configured to receive EMM messages from the EMM protocol entity, and format the UL information delivery message to include the EMM message The UL information transmission message is transmitted within and on the Signaling Radio Bearer (SRB).

16. The WTRU as described in embodiment 15, wherein the UL information delivery message is transmitted to a mobility management entity (MME).

17. A wireless transmit/receive unit (WTRU) for transmitting short message service (SMS) messages, the WTRU comprising: an SMS protocol entity; and an evolved packet system (EPS) mobility management (EMM) protocol entity, configured as Receive a downlink (DL) non-access stratum (NAS) transmission message and forward the SMS message to the SMS protocol entity. The DL NAS transmission message includes an information element, and the information element includes the SMS message.

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

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

20. A wireless transmit/receive unit (WTRU) for transmitting additional service (SS) messages. The WTRU includes: an SS protocol entity configured to generate a request for sending SS messages; and an evolved packet system (EPS) mobile The EMM protocol entity is configured to initiate the process of sending uplink (UL) non-access stratum (NAS) transmission messages in response to the request. The UL NAS transmission message includes an information element (IE), and the IE Contain the SS message.

twenty one. The WTRU in embodiment 20, wherein the EMM protocol entity is further configured to format the UL NAS transmission message to include the SS message, and encapsulate the UL NAS transmission message in the EMM message.

22. The WTRU of embodiment 21, the WTRU further comprising: a radio resource control (RRC) protocol entity, configured to receive the EMM message from the EMM protocol entity, and format the UL information to transfer the message to the EMM message The UL information transmission message is included and transmitted on the Signaling Radio Bearer (SRB).

twenty three. The WTRU in embodiment 22, wherein the UL NAS transmission message is transmitted to a mobility management entity (MME).

24. A wireless transmit/receive unit (WTRU) for transmitting additional service (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) transmission message and forward the SS message to the SS protocol entity. The DL NAS transmission message includes an information element (IE), and the IE contains the SS message.

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

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

Although the features and elements of the present invention are described in specific combinations, each feature or element can be used alone without other features and elements, or used in various situations with or without other features and elements. . The method or flowchart provided here can be implemented in a computer program, software, or firmware executed by a general-purpose computer or processor, where the computer program, software, or firmware is included in a computer-readable storage medium in a tangible manner of. Examples of computer-readable storage media include read-only memory (ROM), random access memory (RAM), temporary memory, cache memory, semiconductor memory devices, internal hard disks, and removable disks. Magnetic media, magneto-optical media, and optical media such as CD-ROM disks and digital versatile discs (DVD).

For example, suitable processors include: general-purpose processors, special-purpose processors, traditional processors, digital signal processors (DSP), multiple microprocessors, one or more microprocessors associated with DSP cores, Controller, microcontroller, dedicated integrated circuit (ASIC), field programmable gate array (FPGA) circuit, any kind of integrated circuit (IC) and/or state machine.

The processor associated with the software can be used to implement a radio frequency transceiver for use in a wireless transmit and receive unit (WTRU), user equipment (UE), terminal, base station, radio network controller (RNC) or any host computer To be used in. WTRU can be used in combination with modules implemented in hardware and/or software, such as cameras, camera modules, video phones, speaker phones, vibration devices, speakers, microphones, TV transceivers, hands-free headsets, keyboards, Bluetooth ®module, frequency modulation (FM) radio unit, liquid crystal display (LCD) display unit, organic light-emitting diode (OLED) display unit, digital music player, media player, video game console module, Internet browser And/or any wireless local area network (WLAN) or ultra-wideband (UWB) module.

<p>100, 200 wireless LTE communication system</p><p>105, 205, 1000, 1100, WTRU wireless transmit/receive unit</p><p>110, E-UTRAN evolved universal terrestrial radio access network</p><p>115. MME mobility management entity</p><p>120. MSC/VLR mobile switching center/visitor location register</p><p>125, 225, 1005 SMS agreement entity</p><p>130, 230, 1105 SS agreement entity</p><p>135, 160, 235 MM agreement entity</p><p>140, 240 EPS EMM agreement entity</p><p>145, 245 LTE RRC agreement entity</p><p>150. SRB signaling radio bearer</p><p>155 LTE EMM agreement entity</p><p>300, 400 wireless communication system</p><p>305, 405 E-SMS agreement entity</p><p>310, 410, 1010, 1110 EMM agreement entity</p><p>315 SMS-EMM-Conn-Est-Req message</p><p>320 SMS-EMM-Conn-Est-Cnf message</p><p>325, 425 Data-Req message</p><p>330, 430 Data-Ind message</p><p>415 SMS-EMM-Conn-Est-Ind message</p><p>420 SMS-EMM-Conn-Est-Rsp message</p><p>1015, 1115 RRC agreement entity</p><p>1020, 1120 network</p><p>1025, 1125 paging</p><p>1030, 1130 service request</p><p>1135 RRC downlink information transfer message</p><p>1140 RRC uplink information transmission message</p><p>CP control protocol</p><p>Data</p><p>DL downlink</p><p>EMM Evolved Packet System Mobility Management</p><p>EPS Evolved Packet System</p><p>E-SMS Enhanced SMS</p><p>LTE long-term evolution</p><p>MM mobility management</p><p>MSC Mobile Switching Center</p><p>MT mobile terminal</p><p>NAS non-access layer</p><p>RRC radio resource control</p><p>SMS messaging service</p><p>SMS-EMM-Conn-Est-Cnf From EMM to E-SMS, used to confirm connection establishment request</p><p>SMS-EMM-Conn-Est-Ind From EMM to E-SMS, used to indicate the incoming SMS message</p><p>SMS-EMM-Conn-Est-Req From E-SMS to EMM, used to request the establishment of a connection for exporting SMS when there is no connection currently</p><p>SMS-EMM-Conn-Est-Rsp From E-SMS to EMM, used to respond to incoming SMS message instructions</p><p>SS additional services</p><p>SS-EMM- Sess-Est-Ind From EMM to E-SS, used to indicate the input SS message</p><p>SS-EMM-Sess-Est-Rsp From E-SS to EMM, used to respond to the input of SS message instructions</p><p>UL uplink</p><p>VLR visitor location register</p>

Schematic description

The present invention can be understood in more detail from the following description, which is given in the form of examples and can be understood in conjunction with the accompanying drawings, in which:

Figure 1 shows a wireless communication system including a WTRU with an agreed entity architecture;

Figure 2 shows a wireless communication system including a WTRU with an alternative agreement entity architecture;

Figure 3 shows the process used to support the export of SMS;

Figure 4 shows the process used to support incoming SMS;

Figure 5 shows the call-independent additional services supported by the system of Figures 1 and 2;

Figure 6 shows the total NAS message header format used for EMM;

Figure 7 shows the UL/DL transmission format of EMM messages;

Figure 8 shows the format of SMS and SS message header plus payload;

Figure 9 shows the EMM message format supporting SMS and SS in LTE;

Figure 10 is a signaling diagram for the mobile terminal (MT) SMS process; and

Figure 11 is a signaling diagram for the MT SS procedure.