(19)
(11)EP 2 568 728 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
27.02.2019 Bulletin 2019/09

(21)Application number: 11777537.9

(22)Date of filing:  29.04.2011
(51)International Patent Classification (IPC): 
H04W 4/14(2009.01)
H04L 29/06(2006.01)
H04W 72/04(2009.01)
H04W 88/02(2009.01)
H04W 12/02(2009.01)
H04W 88/08(2009.01)
(86)International application number:
PCT/KR2011/003244
(87)International publication number:
WO 2011/139056 (10.11.2011 Gazette  2011/45)

(54)

METHOD AND SYSTEM FOR DELIVERING SMS (SHORT MESSAGE SERVICE) MESSAGES IN A MOBILE COMMUNICATION SYSTEM

VERFAHREN UND SYSTEM ZUM SENDEN VON SMS-NACHRICHTEN IN EINEM MOBILKOMMUNIKATIONSSYSTEM

PROCÉDÉ ET SYSTÈME POUR LA DÉLIVRANCE DE MESSAGES SMS (SERVICE DE MESSAGES COURTS) DANS UN SYSTÈME DE COMMUNICATION MOBILE


(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

(30)Priority: 03.05.2010 KR 20100041602

(43)Date of publication of application:
13.03.2013 Bulletin 2013/11

(73)Proprietor: Samsung Electronics Co., Ltd.
Gyeonggi-do 443-742 (KR)

(72)Inventors:
  • CHO, Song-Yean
    Gyonggi-do 443-742 (KR)
  • KIM, Soeng-Hun
    Gyonggi-do 443-742 (KR)
  • CHOI, Sung-Ho
    Gyonggi-do 443-742 (KR)
  • BAE, Beom-Sik
    Gyonggi-do 443-742 (KR)

(74)Representative: Grünecker Patent- und Rechtsanwälte PartG mbB 
Leopoldstraße 4
80802 München
80802 München (DE)


(56)References cited: : 
WO-A1-2010/018801
KR-A- 20100 021 690
KR-A- 20100 021 384
KR-A- 20100 038 563
  
  • NEC: "UE-EPC Signalling Setup: S1AP corrections", 3GPP DRAFT; R3-082691, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. Prague, Czech Republic; 20080924, 24 September 2008 (2008-09-24), XP050323959, [retrieved on 2008-09-24]
  • "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 (Release 8)", 3GPP STANDARD; 3GPP TS 24.301, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V8.5.0, 31 March 2010 (2010-03-31), pages 1-275, XP050402198, [retrieved on 2010-03-31]
  
Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


Description

[Technical Field]



[0001] The present invention relates to a method and system for delivering Short Message Service (SMS) messages in a mobile communication system.

[Background Art]



[0002] Generally, SMS, a value-added service in mobile communication systems, refers to a service of sending short texts to the other party. At present, mobile communication systems such as Long Term Evolution (LTE) use a Circuit Switched Fall Back (CSFB) function that uses the Mobile Switching Center (MSC) existing in the legacy network. In terms of the delivery overhead, quite a lot of control messages are required to support a User Equipment (UE) in an idle state in sending one SMS message which is limited to 160 characters. International patent application WO 2010/018801 A1 suggests including a parameter identifying the purpose of a request, in particular for an SMS message, in a NAS: Service Request message sent by the user equipment such that the mobility management entity (MME) can decide whether to establish resources for bearer establishment and to activate the AS security based on this parameter. The 3GPP TSG-RAN WG3 # 61 bis Draft "UE-EPC Signalling Setup: S1AP corrections" discloses a change request with respect to TS 36.413 (E-UTRAN S1 application protocol (S1AP) version 8.3.0).

[Disclosure]


[Technical Problem]



[0003] The present invention provides a method and system for efficiently providing an SMS service in an LTE system.

[0004] The present invention provides a method and system for reducing a load during an SMS service in an LTE system.

[Technical Solution]



[0005] The present application solves the technical problem by a method according to claim 1, and a corresponding system according to claim 2.

[Advantageous Effects]



[0006] According to the present invention, loads of a UE and an eNB, for SMS delivery, may be reduced in the evolved mobile communication systems.

[Description of Drawings]



[0007] 

FIG. 1 is an end-to-end signal flow diagram of sending an SMS message from an idle UE A to an idle UE B in an LTE system to which the present invention is applied;

FIG. 2 is a signal flow diagram of processing a Message Origination (MO) call during SMS sending according to a first embodiment of the present invention;

FIG. 3 is a signal flow diagram of processing a Message Termination (MT) call for SMS reception according to the first embodiment of the present invention;

FIG. 4 is a signal flow diagram of processing an MO call during SMS sending according to a first illustrative example not being part of the present invention;

FIG. 5 is a signal flow diagram of processing an MT call for SMS reception according to the first illustrative example;

FIG. 6 is a signal flow diagram of processing an MO call during SMS sending according to a second illustrative example not being part of the present invention; and

FIG. 7 is a signal flow diagram of processing an MT call for SMS reception according to the second illustrative example.


[Best Mode]



[0008] Preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings. The same reference numerals are used throughout the drawings to refer to the same or like elements of embodiments of the present invention.

[0009] In the following description, specific details such as detailed configuration and components are merely provided to assist the overall understanding of exemplary embodiments of the present invention. Therefore, it should be apparent to those skilled in the art that various changes and modifications of the embodiments described herein can be made. The scope of the present invention is defined by the claims. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness.

[0010] In an LTE system to which the present invention is applied, in order to determine the amount of actual overload for SMS provision in terms of the entire system, an end-to-end signal flow diagram of sending one SMS message from a UE A in an idle state to a UE B in an idle state may be analyzed as shown in FIG. 1.

[0011] FIG. 1 is an end-to-end signal flow diagram of sending an SMS message from an idle UE A 100 to an idle UE B 122 in an LTE system to which the present invention is applied. For convenience' sake, FIG. 1 is divided into FIG. 1A and FIG. 1B.

[0012] In step 124, the UE A 100 in an idle state sends a Radio Resource Control (RRC) setup request message for making an RRC connection to an evolved Node-B (eNB) 102, to send an SMS message.

[0013] Upon receiving the RRC setup request message from the UE A 100 in step 124, the eNB 102 allocates a signal radio bearer and sends an RRC setup message including the allocation information to the UE A 100, in step 126.

[0014] Upon receiving the RRC setup message in step 126, the UE A 100 sends a service request message for a connection with a Mobile Management Entity (MME) 104 to the eNB 102 using an RRC setup complete message in order to send an SMS message, in step 128.

[0015] Upon receiving the RRC setup complete message in step 128, the eNB 102 sends a service (SVC) request message that the UE A 100 sends to the MME 104, using an initial UE message, in step 130. The eNB 102 allocates eNB S1AP id, which is a temporary id for identifying a message from the UE A 100, and then includes the temporary id in the initial UE message.

[0016] Upon receiving the initial UE message including the service request message from the UE A 100 in step 130, the MME 104 activates a security context between the UE A 100 and the MME 104, which it created according to an authentication procedure that it performed before the UE A 100 was in an idle state, and generates an Access Stratum (AS) security key used between the UE A 100 and the eNB 102, based on a Non Access Stratum (NAS) security key in this context, in step 132. The MME 104 activates a non-GBR bearer that the UE A 100 was using before it transitions to an idle state. In step 132, the MME 104 includes the generated AS security key, information about non-GBR bearers to be activated, and MME S1 AP id, which is a temporary id allocated by the MME 104, in an initial context setup message that the MME 104 sends to the eNB 102, and sends the initial context setup message to the eNB 102.

[0017] Upon receiving the initial context setup message in step 132, the eNB 102 sends an AS security command message to the UE A 100 based on the AS security key included in the received message, in step 134. In step 136, the eNB 102 receives a response thereto and activates AS security. In step 138, the eNB 102 activates radio bearers by performing RRC reconfiguration on the bearers to be activated.

[0018] If activation of radio bearers is successful, the UE A 100 activates NAS layer security in step 150, interpreting it as an implicit signal implying that the MME 104 has accepted the service request from the UE A 100 (AS layer security is activated in step 136).

[0019] If activation of radio bearers is successful, the eNB 102 notifies it to the MME 104 using an initial context setup response message in step 140.

[0020] In step 142, the UE A 100 sends an SMS message using the activated NAS key. (a NAS message is sent in an AS layer using a UL NAS transport, and is sent even in S1AP between the eNB 102 and the MME 104 using the UL NAS transport).

[0021] Upon receiving the SMS message from the UE A 100 in step 142, the MME 104 sends it to an MSC/Visitor Location Register (VLR) 106 in step 144.

[0022] In step 148, the MSC/VLR 106 sends ACK indicating its reception of the SMS message to the UE A 100 to prevent the UE A 100 from retransmitting the SMS message. In step 146, the MSC/VLR 106 forwards the SMS message to an SMS-Interworking MSC (IWMSC) 108 to send the SMS message to an SMS recipient (UE B 122).

[0023] In step 152, the SMS-IWMSC 108 sends the SMS message to an SMS Center (SC) 110.

[0024] In step 154, the SC 110 sends the received SMS message to a SMS-Gateway Mobile Switching Center (GMSC) 112.

[0025] In step 156, the SMS-GMSC 112 finds out routing information for an SMS receiving side (UE B 122), i.e., information about an MSC that can send an SMS message to the receiving side, via a Home Location Register/Home Subscribe Server (HLR/HSS) 114.

[0026] In step 158, the SMS-GMSC 112 forwards the SMS message to a receiving side-related MSC 116. In step 160, if the UE B 122, or an SMS receiving (or terminating) UE, is in an idle state, the MSC 116 sends a paging to the UE B 122 via an MME 118 and an eNB 120, in order to switch the UE B 122 to an active state.

[0027] Upon receiving the paging in step 160, the UE B 122 establishes an RRC connection with the eNB 120 and sends a service request message for responding to the paging to the eNB 120 in step 162, in order to respond to the paging.

[0028] In step 164, the eNB 120 sends a service (SVC) request message from the UE B 122 to the MME 118 using an initial UE message.

[0029] After receiving the service request message, the MME 118 sends the service request message to the MSC 116 to the MSC 116 in step 166 in order to receive from the MSC 116 the SMS message to be delivered to the UE B 122. Upon receiving the service request message from the MME 118, the MSC 116 sends the SMS message to the MME 118 through downlink unit data in step 168.

[0030] In step 170, the MME 118 sends an initial UE context setup request message to the eNB 120 in order to perform AS security and non-GBR bearer activation for the UE B 122 that sent the service request message in step 162. Upon receiving the initial UE context setup request message in step 170, the eNB 120 activates AS security by sending and receiving security mode command/complete messages, and activates non-GEBR bearers using an RRC reconfiguration/complete message, in step 172.

[0031] If activation of radio bearers is successful, the UE B 122 activates NAS layer security, interpreting it as an implicit signal implying that the MME 118 has accepted the service request message from the UE B 122 (AS layer security is activated in step 172). In step 174, if activation of radio bearers is successful, the eNB 120 notifies it to the MME 118 using an initial context setup response message. In step 176, the MME 118 encrypts the SMS message received from the MSC 116 using the activated NAS security, attaches MAC for integrity check thereto, and then delivers the resulting SMS message to the UE B 122 using a NAS message.

[0032] Upon receiving the SMS message in step 176, the UE B 122 sends ACK indicating its reception of the SMS message to the MSC 116 via the MME 118 in step 177 in order to prevent the MSC 116 from retransmitting the SMS message.

[0033] After receiving the SMS message, the UE B 122 sends a delivery report message, which it sends to the SC 110, to the MSC 116 via the MME 118 in steps 178 and 180. In step 182, the MSC 116 sends ACK indicating its reception of the delivery report message to the UE B 122 via the MME 118.

[0034] The delivery report message, sent by the UE B 122 or a SMS receiving UE, is sent by the MSC 116 to the SC 110 via the SMS-GMSC 112 in step 184.

[0035] In step 186, the SC 110 sends the received delivery report message to the UE A 100, which is a UE that has sent the SMS message, via the SMS-IWMSC 108, the MSC/VLR 106, and the MME 104.

[0036] Upon receiving the delivery report message in step 186, the UE A 100 or an SMS sending (or originating) terminal sends ACK, which is a response to the delivery report message, to the MSC/VLR 106 in step 188.

[0037] In the above-described process of FIG. 1, in which Message Origination (MO) and delivery report for SMS sending are processed, an SMS message is received once at the SC 110 that relays SMS messages, an SMS message is sent once by the SC 110, a report on SMS delivery is received once at the SC 110, and a report on SMS delivery is sent once by the SC 110, so the SC 110 receives a total of two messages and sends a total of two messages. The MSCs 106 and 116 receive a total of three messages and send a total of three messages. However, the SMS sending/receiving terminals 100 and 122, and the eNBs 102 and 120 each send a total of six messages and receive a total of six messages, and the MME 118 sends a total of four messages and receives a total of four messages. The number of messages sent and received by/at each UE and each network entity is listed in Table 1 below, showing that when SMS messages are sent and received using the CSFB function, most of the load is concentrated on the UEs, the eNBs and the MMEs.
Table 1
 UEeNBMMEMSCSC
MSG Tx 6 9 5 3 2
MSG Rx 5 9 6 3 2


[0038] The present invention provides the following embodiments for reducing the loads of UEs and eNBs during SMS delivery in a mobile communication system such as LTE, to which the present invention is applied, like Table 1.

First Embodiment



[0039] A first embodiment of the present invention corresponds to a method in which if a UE 200 sends only SMS messages, no data bearer is set up between the UE 200 and an eNB 202.

[0040] FIG. 2 is a signal flow diagram of processing a Message Origination (MO) call during SMS sending according to a first embodiment of the present invention. Although FIG. 2A and FIG. 2B form one drawing, they are separated for convenience' sake.

[0041] In step 214, a UE 200 or an SMS originating UE sends an RRC connection request message to an eNB 202 to request an RRC connection. In step 216, the eNB 202 sends an RRC connection setup message to the UE 200 in response to the RRC connection request message received in step 214.

[0042] In step 218, the UE 200 sends an RRC connection complete message. During the sending, the UE 200 includes a service request message in the RRC connection complete message. The service request message includes an indicator 'SMS only' indicating SMS sending-only, a Key Set Indicator (KSI), and MAC. The KSI is information indicating a set of an encryption/decryption key allocated through recent authentication, an encryption/decryption key used for integrity assurance/check, and an integrity assurance/check key, and the MAC is a sort of hash value calculated using an Integrity Key (IK). The KSI and the MAC are terms generally used in the technical field of the present invention, and thus will not described in detail. This service request message is sent to an MME 204 via the eNB 202 using an initial UE message in step 220.

[0043] In step 220, the eNB 202 allocates an eNB UE S1AP id, which is a temporary id of a UE and is to be used in an S1AP connection (a temporary id the eNB 202 allocates to identify the UE A 200), and includes it as a parameter of the initial UE message. Upon receiving the initial UE message in step 220, the MME 204 sends an 'initial context setup for signaling' message to the eNB 202, for a UE for SMS exchange, in step 222.

[0044] Since no data bearer will be set up between the UE 200 and the eNB 202 in the first embodiment of the present invention, the 'initial context setup for signaling' message to be sent in the initial context setup for signaling, to be performed in step 222 does not include information about data bearers, and the MME 204 sends MME UE S1AP id that the MME 204 allocates as a temporary id of a UE in an S1AP connection (a temporary id the MME 204 temporarily allocates to identify the UE 200) and a Key of eNB (KeNB) necessary for the eNB 202 to set up AS security, using a parameter.

[0045] Upon receiving the 'initial context setup for signaling' message that the MME 204 sent in step 222, the eNB 202 sets up only AS security and sets up no radio bearer corresponding to the data bearer. In step 224, the eNB 202 sends an AS security command (SEC MOD CMD) message to the UE 200.

[0046] If AS security is successfully set up, the UE 200 having received the AS security mode command in step 224 activates NAS security in step 226, considering that the MME 204 has accepted the service request (SMS only, etc.) of step 218 from the UE 200. In step 228, the UE 200 sends a security mode (SEC MOD) complete message to the eNB 202 in response to step 224. The AS security refers to security between the eNB 202 and the UE 200, and the NAS security refers to security between the UE 200 and the MME 204.

[0047] After activating AS security, the eNB 202 transmits the results to the MME 204 using an 'initial context setup complete for signaling' message in step 230.

[0048] In step 232, the UE 200 sends an SMS message to the MME 204 using an uplink NAS transport message. In step 234, the MME 204 sends the SMS message to an MSC 206 using uplink unit data. Steps 232 and 234 in FIG. 2 correspond to steps 142 and 144 in FIG. 1.

[0049] Upon receiving the SMS message from the MME 204 in step 234, the MSC 206 forwards the received SMS message to an SC 212 via an SMS-IWMSC 210 in step 236. In step 238, the MSC 206 transmits an SMS receipt ACK message informing the UE 200 of the normal reception of the SMS message to the MME 204 through downlink unit data. In step 240, the MME 204 sends the SMS receipt ACK to the UE 200 using a downlink NAS transport message. Steps 238 and 240 correspond to details of step 148 in FIG. 1.

[0050] In step 242, the SC 212 sends a delivery report message to the MSC 206 via the SMS-IWMSC 210.

[0051] Upon receiving the downlink NAS transport message in step 240, the UE 200 sends an ACK message for indicating its reception of the delivery report message, to the MME 204 using an uplink NAS transport message in step 248. Step 248 corresponds to step 188 in FIG. 1. Through steps 250 and 252, the connection between the MME 204, the eNB 202 and the UE 200 is released.

[0052] A process of processing a Message Termination (MT) call for SMS reception according to the first embodiment of the present invention will be described below with reference to FIG. 3. FIG. 3 is a signal flow diagram of processing a Message Termination (MT) call for SMS reception according to the first embodiment of the present invention. FIGs. 3A and 3B form one drawing, but they are separated for convenience' sake.

[0053] In step 314, an SC 312 forwards an SMS message received from an SMS originating UE to an MSC 306 via an SMS-IWMSC 310 and an HLR/HSS 308. In step 316, the MSC 306 sends a paging message to a UE 300 that is to receive the SMS message.

[0054] Upon receiving the paging message, the UE 300 sends an RRC connection request message to an eNB 302 in step 318. In response thereto, the eNB 302 sends an RRC connection setup message to the UE 300 in step 320.

[0055] Upon receiving the RRC connection setup message, the UE 300 sends an RRC connection complete message to the eNB 302 in step 322. The RRC connection complete message includes a service request message. The service request message includes an indicator 'SMS only information' indicating that the service request message is only for SMS sending, KSI, and MAC. Upon receiving the service request message, the eNB 302 sends the service request message to an MME 304 using an initial UE message in step 324. In step 324, the eNB 302 allocates an S1AP eNB UE id, which is a temporary id of a UE and is to be used in an S1AP connection, and sends it using a parameter of the initial UE message.

[0056] Upon receiving the initial UE message, the MME 304 sends an 'initial context setup for signaling' message to the eNB 302, for a UE for SMS exchange, in step 326. Since no data bearer will be set up between the UE 300 and the eNB 302 in the first embodiment, the 'initial context setup for signaling' message for signaling to be performed in step 326 does not include information about data bearers, and the service request message and an S1AP MME UE id that the MME 304 allocates as a temporary id of a UE in S1AP connection are sent using a parameter.

[0057] Upon receiving the 'initial context setup for signaling' message that the MME 304 sent in step 326, the eNB 302 sets up only AS security and sets up no radio bearer corresponding to the data bearer. In step 328, the eNB 302 sends an AS security command (SEC MOD CMD) message to the UE 300. If AS security is successfully set up, the UE 300 having received the AS security command message activates NAS security in step 330, considering that the MME 304 has accepted the service request (SMS only, etc.) for the UE 300. In step 332, the UE 300 sends a security mode (SEC MOD) complete message to the eNB 302 in response to step 328.

[0058] After activating AS security, the eNB 302 having received the security mode complete message transmits the results to the MME 304 using an 'initial context setup for signaling complete' message in step 334. In step 336, the MME 304 sends a service request message to the MSC 306 in order to request sending of the SMS message that the MSC 306 received in step 314.

[0059] Upon receiving the service request message from the MME 304 in step 336, the MSC 306 forwards the SMS message to the UE 300 via the MME 304 in step 338.

[0060] Upon receiving the SMS message in step 338, the UE 300 may send only a delivery report message, omitting SMS receipt ACK message transmission in step 340, if a delivery report transmission time for the received SMS message is less than a preset timer value T. In step 340, the UE 300 may determine whether to send both an SMS receipt ACK message and a delivery report message using one UL NAS transport message.

[0061] In step 342, the UE 300 sends an SMS receipt ACK message for indicating the normal reception of an SMS message. However, the UE 300 may omit step 342, if it determines in step 340 to send a delivery report message within a preset timer value.

[0062] In step 344, the UE 300 sends a delivery report to the MSC 306 via the MME 304. The SMS receipt ACK message sent in step 342 may be sent together with a delivery report message using a UL NAS transport message that is sent in step 344.

[0063] Upon receiving the delivery report message in step 344, the MSC 306 sends the received delivery report message to the SC 312 in step 346.

[0064] In step 348, if the MSC 306 receives a delivery report message before receiving an SMS receipt ACK, it considers that the UE 300 has successfully received an SMS message.

[0065] In step 350, the MSC 306 sends a delivery report receipt ACK message to the UE 300 via the MME 304. In step 352, the MME 304 and the eNB 302 release their connection with the UE 300.

[0066] The process of processing an MT call for SMS reception in the first embodiment of the present invention is different from the process of processing an MO call for SMS sending in that the paging reception triggers the service request for the UE 300. In addition, the process of processing an MT call for SMS reception is different from the process of processing an MO call for SMS sending in FIG. 2 in that after receiving the SMS message, the UE 300 sends an ACK for SMS message receipt and a delivery report using one UL NAS transport message, or the UE 300 sends only the delivery report and upon receiving it, the MME 304 may determine that ACK for SMS message receipt is implicitly included.

[0067] According to the first embodiment of the present invention, messages sent and received by/at a UE and an eNB are reduced in number by 2 and 4 in total, respectively, as shown in Table 2, compared to Table 1.
Table 2
 UEeNBMMEMSCSC
MSG Tx 5 8 4 3 2
MSG Rx 4 8 5 3 2

First Illustrative Example



[0068] A first illustrative example not being part of the present invention corresponds to a method in which if a UE sends only SMS messages, no data bearers and no AS securities are set up.

[0069] The first illustrative example is characterized in that the AS securities as well as the data bearers are not set up. If a UE in an idle state intends to send one SMS message, the UE makes an RRC connection, sends one SMS message in a NAS message, and then, immediately releases the RRC connection, so additional RRC messages are not likely to occur. Since the SMS message is protected by NAS security by being sent in a NAS message, the need for AS security setup is low. Therefore, in the first illustrative example, data bearers are not set up and AS securities are not activated.

[0070] A signal flow diagram of processing an MO call during SMS sending according to a first illustrative example is as shown in FIG. 4. FIG. 4A and FIG. 4B form one drawing, but they are separated for convenience' sake.

[0071] Steps 414 to 420 in FIG. 4 are the same as steps 214 to 220 in FIG. 2, so description thereof will be omitted.

[0072] After receiving an initial UE message in step 420, an MME 404 sends to an eNB 402 an initial UE message response that does not include a data bearer context and KeNB 'eNB key' for AS security setup and includes a service accept message for the service request message transmitted in step 418 and an MME UE S1AP id, in step 424. In the first illustrative example, since data bearer and AS security are not setup, the MME 404 sends the initial UE message response, which does not include a KeNB unlike in the first embodiment of the present invention, to the eNB 402 in step 424.

[0073] In step 426, the eNB 402 sends Service request Accept, which is Accept for a service request message that a UE 400 sent, to the UE 400 using a downlink transport message.

[0074] In the first illustrative example, the UE 400 may activate NAS security in any one of steps 422 and 428.

[0075] Step 422 represents a case in which the UE 400 performs NAS security activation after checking a response with respect to an RRC connection complete message including a service request message in an RLC layer which is a lower layer of RRC, and step 428 represents a case in which the UE 400 performs NAS security activation after receiving a Service request Accept message that the MME 404 explicitly sent in step 426. In other words, in the first illustrative example, the UE 400 may perform NAS security activation in step 422 or step 428.

[0076] In step 430, the eNB 402 sends an initial UE message response ACK to the MME 404. Steps 432 to 452 are the same as steps 232 to 252, so detailed description thereof will be omitted.

[0077] In other words, the process of processing an MO call for SMS sending according to the first illustrative example is different from the process of processing an MO call for SMS sending according to the first embodiment of the present invention, in the process in which as shown in FIG. 4, after receiving an initial UE message in step 420, the MME 404 sends to the eNB 402 an initial UE message response that does not include a data bearer context and KeNB for AS security setup, in step 424; in the process in which upon receiving the response, the eNB 402 sends an initial UE message ACK message to the MME 404 in step 430; in the process (step 422) in which the UE 400 activates NAS security after checking the success in sending of an RRC connection complete message in RLC which is a lower layer of RRC that sends a service request; or in the process (step 428) in which the UE 400 activates NAS security after receiving the response message with respect to the service request that the MME 404 explicitly sent.

[0078] A process of processing an MT call for SMS reception according to the first illustrative example will be described below with reference to FIG. 5. FIG. 5A and FIG. 5B form one drawing, but they are separated for convenience' sake.

[0079] Steps 514 to 524 in FIG. 5 are the same as steps 314 to 324 in FIG. 3, so detailed description thereof will be omitted.

[0080] In step 526, an MME 504 sends a service request message to an MSC 506. In step 528, the MSC 506 sends an SMS message received in step 514 to the MME 504 using DL unit data.

[0081] In the first illustrative example, a UE 500 selectively performs step 530 or step 532 depending on the time that NAS security activation is performed. Step 530 shows a case (step 530c) in which NAS security activation for the UE 500 is performed after the UE 500 receives an ACK message from an RLC layer, for the RRC connection complete message, and step 532 shows a case (step 532d) in which NAS security activation for the UE 500 is performed after the UE 500 receives a service request accept message from the MME 504.

[0082] The procedure performed in step 530 will be described in detail. In step 530a, the MME 504 sends an initial UE message response message to an eNB 502, and in response thereto, the eNB 502 sends an initial UE message response ACK message to the MME 504 in step 530b. In step 530c, the UE 500 performs NAS security activation.

[0083] The procedure performed in step 532 will be described in detail. In step 532a, the MME 504 sends an initial UE message response message to the eNB 502. In step 532b, the eNB 502 sends a downlink transport message including a service request accept message, to the UE 500. In step 532c, the eNB 502 sends an initial UE message response ACK message to the MME 504 in response to step 532a. In step 532d, the UE 500 performs NAS security activation.

[0084] In step 534, the MME 504 forwards the SMS message received in step 528 to the UE 500 using a DL NAS transport message, and the UE 500 performs step 536. Step 536 is the same as step 340 in FIG. 3, step 538 is the same as step 342 in FIG. 3, and step 540 is the same as step 344 in FIG. 3, so detailed description thereof will be omitted.

[0085] In addition, steps 542, 544 and 546 in FIG. 5 are the same as steps 348, 346 and 352 in FIG. 3, respectively, so detailed description thereof will be omitted.

[0086] As described above, like the process of processing an MO call for SMS sending according to the first illustrative example, the process of processing an MT call for SMS sending according to the first illustrative example is characterized in that the eNB 502 and the MME 504 exchange an initial UE message response message that does not include a data bearer context and KeNB for AS security setup, and an initial UE message ACK message, and NAS security activation for the UE 500 may be performed in any one of steps 530c and 532b. According to the first illustrative example, the messages sent and received by/at a UE and an eNB are reduced in number by 3 and 6 in total, respectively, as shown in Table 3, compared to Table 1.
Table 3
 UEeNBMMEMSCSC
MSG Tx 4 8 (7*) 4 3 2
MSG Rx 4 (3*) 7 5 3 2


[0087] In Table 3, (number*) represents a case where service accept is not used and NAS security is activated by ACK from RLC.

Second Illustrative Example



[0088] A second illustrative example not being part of the present invention corresponds to a method in which if a UE sends only SMS messages, NAS security is activated before sending of a service request message and an SMS message is sent in a service request message.

[0089] In the second illustrative example, a radio bearer for signaling is allocated when an eNB 602 sends an RRC connection setup message after a UE 600 sends an RRC connection request message to the eNB 602. Thus, thereafter, a NAS message may be send using the allocated radio bearer. In other words, the service request message is sent on a dedicated radio bearer allocated to a UE, so that unlike when a common signaling channel is shared, an SMS message, for which the limit in message size is a maximum of 160 bytes, may be included in the service request message. Therefore, the second illustrative example provides a method of sending an SMS message in a service request message and a service request accept message as in FIGs. 6 and 7.

[0090] A process of processing an MO call during SMS sending according to a second illustrative example will be described below with reference to FIG. 6. FIG. 6A and 6B form one drawing, but they are separated for convenience' sake.

[0091] Steps 614 and 616 are the same as steps 214 and 216 in FIG. 2, respectively, so detailed description thereof will be omitted. After receiving an RRC connection setup message from the eNB 602 in step 616, the UE 600 activates NAS security before sending a service request message, in step 616. In step 620, the UE 600 encrypts the SMS message using a security key, which is an encryption key, in the activated security context, includes it in a service request message, and sends the service request message to the eNB 602 using an RRC connection complete message. The service request message may include an indicator 'SMS only' indicating that the service request message is only for SMS sending, KSI, MAC, the encrypted SMS message (enc(SMS msg)), and flag information indicating that the SMS message has been encrypted (enc flg). In step 620, the UE 600 sends only a MAC for integrity check in the service request message without encrypting the service request message itself in the existing manner.

[0092] While only the SMS message has been encrypted and sent in step 620 of FIG. 6A, according to another variation, the service request message including the SMS message as well as the SMS message are encrypted and then the MAC may be delivered to the MME 604 together with the encrypted service request message. In this case, the MME 604 performs verification with respect to the MAC and upon completion of verification with respect to the MAC, the encrypted service request message is decrypted using a previously stored security context to extract the SMS message included in the service request message and send the extracted SMS message to the MSC 606.

[0093] Upon receiving the RRC connection complete message including the service request message in step 620, the eNB 602 sends an initial UE message including the service request message and the eNB UE S1AP id to an MME 604 in step 622. Upon receiving the initial UE message in step 622, the MME 604 performs integrity check using a MAC code included in the service request message, and if its validity is identified, the MME 604 activates the security context. The MME 604 then decrypts the SMS message included in the service request message using the security key (encryption key) included in the security context, and then sends the decrypted SMS message to the MSC 606 in step 624. Step 626 is the same as step 236 in FIG. 2, so its detailed description will be omitted.

[0094] In the second illustrative example, for the process after the MME 604 sends an SMS message to an MSC 606, two kinds of steps 628 and 630 are possible.

[0095] Step 628 "Alternative A" corresponds to a case where the MME 604 independently handles the SMS receipt ACK message and the initial UE message. In other words, the MME 604 sends an initial UE message response message to the eNB 602 in step 628a after receiving the initial UE message including a service request message in step 622, and receives an initial UE message response ACK message from the eNB 602 in step 628b. The MME 604 sends an SMS receipt ACK message that the MSC 606 sent in step 628c, to the UE 600 in step 628d, after sending the SMS message included in the service request message to the MSC 606 in step 624.

[0096] As such, in FIG. 6, the initial UE message response and the SMS receipt response may be separately handled or they may be handled at the same time.

[0097] However, step 630 "Alternative B" corresponds to a case where the MME 604 handles the SMS receipt ACK message and the initial UE message together. In other words, after receiving the initial UE message including a service request message from the eNB 602 in step 622, a procedure after sending the SMS message in the service request message to the MSC 606 in step 624 is different from step 628. That is, upon receiving an SMS receipt ACK message from the MSC 606 in step 630a, the MME 604 sends the received SMS receipt ACK message to the eNB 602 along with an initial UE message response message in step 630b. In step 630c, the eNB 602 sends the SMS receipt ACK message to the UE 600 using a DL information transport message.

[0098] Steps 632 to 640 are the same as steps 242 to 252 in FIG. 2, so detailed description thereof will be omitted.

[0099] A process of processing an MT call for SMS reception according to the second illustrative example will be described with reference to FIG. 7.

[0100] FIG. 7 is a signal flow diagram of processing an MT call for SMS reception according to the second illustrative example. FIG. 7A and 7B form one drawing, but they are separated for convenience' sake.

[0101] Steps 714 to 726 are the same as steps 514 to 526 in FIG. 5, so detailed description thereof will be omitted.

[0102] Any one of steps 728 and 730 may be performed depending on whether an MME 704 independently handles the initial UE message or handles it along with the SMS message in the process of processing an MT call for SMS reception in the second illustrative example.

[0103] The procedure performed in step 728 will be described in detail. In step 728a, the MME 704 sends a response to an initial UE message received in step 724, to an eNB 702. In step 728b, the eNB 702 sends to the MME 704 an ACK message indicating that it has received the initial UE message response message in step 728a.

[0104] In step 728c, an MSC 706 sends the SMS message it received in step 714, to the MME 704. In step 728d, the MME 704 sends, to a UE 700, a service request accept message with an SMS message and a flag encFlag indicating the inclusion of an encrypted SMS message, using a downlink NAS transport message.

[0105] Upon receiving the downlink NAS transport message, the UE 700 checks the encFlag, and activates NAS security in step 728e. Thereafter, the UE 700 decrypts the encrypted SMS message that was sent together with the service request accept message using an encryption key in the activated NAS security context.

[0106] Next, the procedure performed in step 730 will be described in detail. In step 730a, the MSC 706 sends the SMS message received in step 714 to the MME 704. In step 730b, the MME 704 sends to the eNB 702 a response to the initial UE message it received in step 724. Upon receiving the initial UE message response in step 730b, the eNB 702 sends a service request accept message with an SMS message and a flag enc Flag indicating the inclusion of an encrypted SMS message, to the UE 700 using a downlink NAS transport message in step 730c.

[0107] On the other hand, as another variation of steps 730b and 730c, if the MME 704 encrypts an SMS message and a service request message including the SMS message instead of encrypting only the SMS message, and adds an MAC for transmission to the UE 700, then the UE 700 having received the encrypted message first performs verification with respect to the MAC and, upon completion of verification with respect to the MAC, decrypts the service request message including the SMS message by using a previously stored security context and extracts the SMS message included in the service request message.

[0108] Upon receiving the downlink NAS transport message, the UE 700 checks the enc Flag and activates NAS security in step 730d. Thereafter, the UE 700 decrypts the encrypted SMS message that was sent together with the service request accept message, using an encryption key in the activated NAS security context. In step 730e, the eNB 702 sends to the MME 704 an ACK indicating that it has received the initial UE message response message in step 730b.

[0109] Steps 732 to 736 in FIG. 7 are the same as steps 536 to 540 in FIG. 5, so detailed description thereof will be omitted. Further, steps 738, 740 and 742 in FIG. 7 are the same as steps 544, 542 and 546 in FIG. 5, so detailed description thereof will be omitted.

[0110] Although it is assumed that NAS security is activated in any one of steps 728 and 730 in the process of processing an MT call for SMS reception according to the second illustrative example, NAS security may be activated in between steps 720 and 722 if the UE 700 may determine that it receives only the SMS service over Circuit Switched (CS) service, based on the paging message it received in step 716.

[0111] The processing of an MT call according to the second illustrative example, like the processing of an MO call, sends the SMS message using initial UE message response message. Receiving a paging for SMS message reception, sending a service request message according thereto, and activating NAS security in the second illustrative example are the same as those in the first illustrative example.

[0112] However, the second illustrative example is different from the first illustrative example in that after sending an RRC connection complete message in step 722, the UE 700 receives the service request accept message with an SMS message from the eNB 702 in step 728d or 730c, checks encFlag indicating the inclusion of the encrypted SMS message, activates NAS security in step 728e or 730d, and then decrypts the encrypted SMS message that was sent together with the service request accept message, using the encryption key in the activated NAS security context. Like the MO call processing, the MME 704 may handle the initial UE message together with the SMS message as in Alternative-A (step 728), or may handle them independently as in Alternative-B (step 730).

[0113] According to the second illustrative example, the messages sent and received by/at a UE and an eNB are reduced in number by 5 and 6, respectively, i.e., by 11 in total, as shown in Table 4 below, compared to Table 1.
Table 4
 UEeNBMMEMSCSC
MSG Tx 3 6 (5*) 4 3 2
MSG Rx 3 6 (5*) 5 3 2


[0114] In table 4, (number*) represents the number of control messages in alternative-B.


Claims

1. A method for delivering a Short Message Service, SMS, message in a mobile communication system, comprising:

sending, by an originating User Equipment, UE, (200), to an evolved Node-B, eNB, (202) a service request message for requesting SMS sending in a process of setting up RRC connection using a Radio Resource Control, RRC, connection complete message (218);

sending, by the eNB (202), the received service request message to a Mobile Management Entity, MME, (204) using an initial UE message (220);

sending, by the MME (204), an initial context setup message (222) that does not include information about data bearers, to the eNB (202) in response to the initial UE message;

upon receiving the initial context setup message, setting up (224), by the eNB (202), Access Stratum, AS, security with the originating UE (200);

if the AS security is set up, performing, by the originating UE (200), Non Access Stratum, NAS, security process (226) with the MME (204); and

upon completion of the NAS security process with the MME, transmitting, by the originating UE (200), the SMS message to the MME (204) using an uplink NAS transport message (232).


 
2. A system for delivering a Short Message Service, SMS, message in a mobile communication system, comprising:

an originating User Equipment, UE, (200) configured to send a service request message for requesting SMS sending in a process of setting up RRC connection using a Radio Resource Control, RRC, connection complete message;

an evolved Node-B, eNB, (202) configured to send the service request message included in the RRC connection complete message using an initial UE message, if the RRC connection complete message is received when setting up the RRC connection with the originating UE; and a Mobile Management Entity, MME, (204) configured to send an initial context setup message which does not include information about data bearers to the eNB, if the initial UE message is received from the eNB,

wherein, if the initial context setup message is received by the eNB, the eNB sets up Access Stratum, AS, security with the originating UE, and if the AS security is set up, the originating UE performs a Non Access Stratum, NAS, security process with the MME, and upon completion of the NAS security process with the MME, the originating UE sends the SMS message to the MME using an uplink NAS transport message.


 
3. The method of claim 1 or the system of claim 2, wherein the service request message comprises information indicating SMS-sending only, a Key Set Identifier, KSI, and a Message Authentication Code, MAC,
wherein the initial UE message comprises the service request message and a temporary identifier which the eNB allocates to identify the originating UE.
 
4. The method of claim 1 or the system of claim 2, wherein the initial context setup message comprises a Key of eNB, KeNB, for setting up the AS security between the eNB and the originating UE and a temporary identifier which the MME temporarily allocates to identify the originating UE in S1 Application Protocol, AP, connection.
 
5. The method of claim 1 or the system of claim 2, wherein the eNB having received the initial context setup message sets up no data bearer with the originating UE.
 


Ansprüche

1. Verfahren zum Senden einer Kurznachrichtendienst-, SMS-, Nachricht in einem Mobilkommunikationssystem, mit:

Senden, durch eine Ausgangsbenutzereinrichtung, UE, (200), an einem evolvierten Knoten-B, eNB, (202), einer Dienstanforderungsnachricht zur Anforderung des Sendens einer SMS in einem Vorgang zur Errichtung einer RRC-Verbindung unter Anwendung einer Funkressourcensteuer-, RRC-, Verbindungsabschlussnachricht (218);

Senden, durch den eNB (202), der empfangenen Dienstanforderungsnachricht an eine Mobilverwaltungseinheit, MME, (204) unter Anwendung einer anfänglichen UE-Nachricht (220);

Senden, durch die MME (204), einer anfänglichen Kontexterstellungsnachricht (222), die keine Informationen über Datenträger enthält, an den eNB (202) in Reaktion auf die anfängliche UE-Nachricht;

bei Empfang der anfänglichen Kontexterstellungsnachricht, Erstellen (224), durch den eNB (202), einer Zugriffsschicht-, AS-, Sicherheit in Verbindung mit der Ausgangs-UE (200);

wenn die AS-Sicherheit eingerichtet ist, Ausführen, durch die Ausgangs-UE (200), eines Nicht-Zugriffsschicht-, NAS-, Sicherheitsvorgangs (226) mit der MME (204); und

bei Beendigung des NAS-Sicherheitsvorgangs mit der MME, Senden, durch die Ausgangs-UE (200), der SMS-Nachricht an die MME (204) unter Anwendung einer Aufwärtsverbindungs-NAS-Transportnachricht (232).


 
2. System zum Senden einer Kurznachrichtendienst-, SMS-, Nachricht in einem Mobilkommunikationssystem, mit:

einer Ausgangs-Benutzereinrichtung, UE, (200), die ausgebildet ist, eine Dienstanforderungsnachricht zum Anfordern eines Sendens einer SMS in einem Vorgang des Erstellens einer RRC-Verbindung unter Anwendung einer Funkressourcensteuer-, RRC-, Verbindungsabschlussnachricht zu senden;

einem evolvierten Knoten-B, eNB, (202), der ausgebildet ist, die Dienstanforderungsnachricht, die in der RRC-Verbindungsabschlussnachricht enthalten ist, unter Anwendung einer anfänglichen UE-Nachricht zu senden, wenn die RRC-Verbindungsabschlussnachricht empfangen wird, wenn die RRC-Verbindung zu der Ausgangs-UE eingerichtet wird; und

einer Mobilverwaltungseinheit, MME, (204), die ausgebildet ist, eine anfängliche Kontexterstellungsnachricht, die keine Information über Datenträger enthält, an den eNB zu senden, wenn die anfängliche UE-Nachricht aus dem eNB empfangen wird,

wobei, wenn die anfängliche Kontexterstellungsnachricht von dem eNB empfangen wird, der eNB eine Zugriffsschicht-, AS-, Sicherheit in Verbindung mit der Ausgangs-UE einrichtet, und wenn die AS-Sicherheit eingerichtet ist, die Ausgangs-UE einen Nichtzugriffsschicht-, NAS-, Sicherheitsvorgang in Verbindung mit der MME ausführt, und bei Beendigung des NAS-Sicherheitsvorgangs in Verbindung mit der MME die Ausgangs-UE die SMS-Nachricht an die MME unter Anwendung einer Aufwärtsverbindungs-NAS-Transportnachricht sendet.


 
3. Verfahren nach Anspruch 1 oder System nach Anspruch 2, wobei die Dienstanforderungsnachricht Information enthält, die ein Nur-SMS-Senden, eine Schlüsselfeststellungskennung, KSI, und einen Nachrichtenauthentifizierungscode, MAC, enthält,
wobei die anfängliche UE-Nachricht die Dienstanforderungsnachricht und eine temporäre Kennung enthält, die der eNB zuweist, um die Ausgangs-UE zu erkennen.
 
4. Verfahren nach Anspruch 1 oder System nach Anspruch 2, wobei die anfängliche Kontexterstellungsnachricht einen Schlüssel eines eNB, KeNB, zur Erstellung der AS-Sicherheit zwischen dem eNB und der Ausgangs-UE und eine temporäre Kennung enthält, die die MME temporär zuweist, um die Ausgangs-UE in einer S1-Anwendungsprotokoll-, AP-, Verbindung zu erkennen.
 
5. Verfahren nach Anspruch 1 oder System nach Anspruch 2, wobei der eNB, der die anfängliche Kontexterstellungsnachricht empfangen hat, keinen Datenträger zu der Ausgangs-UE einrichtet.
 


Revendications

1. Procédé de distribution d'un message SMS, soit Short Message Service, dans un système de communication mobile, comprenant :

l'envoi, par un équipement utilisateur UE, soit User Equipment, d'origine (200) à un noeud B évolué eNB (202), soit evolved Node-B, d'un message de requête de service pour requérir l'envoi d'un SMS dans un processus d'établissement d'une connexion à contrôle de ressource radio RRC, soit Radio Resource Control, à l'aide d'un message de connexion achevée RRC (218) ;

l'envoi, par l'eNB (202), du message de requête de service reçu à une entité de gestion mobile MME (204), soit Mobile Management Entity, à l'aide d'un message d'UE initial (220) ;

l'envoi à l'eNB (202), par la MME (204), d'un message d'établissement de contexte initial (222) qui ne comprend pas d'information concernant des porteurs de données, en réponse au message d'UE initial ;

lors de la réception du message d'établissement de contexte initial, l'établissement (224), par l'eNB (202), d'une sécurité de strate d'accès AS, soit Access Stratum, avec l'UE d'origine (200) ;

si la sécurité AS est établie, la mise en oeuvre par l'UE d'origine (200) d'un processus de sécurité à strate de non-accès NAS, soit Non Access Stratum, (226) avec la MME (204) ; et

lors de l'achèvement du processus de sécurité NAS avec la MME, la transmission du message SMS par l'UE d'origine (200) à la MME (204) à l'aide d'un message de transport NAS de liaison montante (232).


 
2. Système de distribution d'un message SMS dans un système de communication mobile, comprenant :

un équipement utilisateur UE d'origine (200) configuré pour envoyer un message de requête de service pour requérir l'envoi d'un SMS dans un processus d'établissement de connexion RRC à l'aide d'un message de connexion achevée à contrôle de ressource radio RRC ;

un noeud B évolué eNB (202) configuré pour envoyer le message de requête de service inclus dans le message de connexion achevée RRC à l'aide d'un message d'UE initial, si le message de connexion achevée RRC est reçu lors de l'établissement de la connexion RRC avec l'UE d'origine ; et

une entité de gestion mobile MME (204) configurée pour envoyer à l'eNB un message d'établissement de contexte initial qui n'inclut pas d'information concernant des porteurs de données, si le message d'UE initial est reçu en provenance de l'eNB,

dans lequel, si le message d'établissement de contexte initial est reçu par l'eNB, l'eNB établit une sécurité de strate d'accès AS avec l'UE d'origine, et si la sécurité AS est établie, l'UE d'origine met en oeuvre un processus de sécurité à strate de non-accès NAS avec le MME, et lors de l'achèvement du processus de sécurité NAS avec la MME, l'UE d'origine envoie le message SMS à la MME à l'aide d'un message de transport NAS de liaison montante.


 
3. Procédé selon la revendication 1 ou système selon la revendication 2, dans lequel le message de requête de service comprend de l'information indiquant l'envoi de SMS uniquement, un identifiant de jeu de clés KSI, et un code d'authentification de message MAC, soit Message Authentication Code,
dans lequel le message d'UE initial comprend le message de requête de service et un identifiant temporaire qu'attribue l'eNB pour identifier l'UE d'origine.
 
4. Procédé selon la revendication 1 ou système selon la revendication 2, dans lequel le message d'établissement de contexte initial comprend une clé d'eNB KeNB, soit Key of eNB, pour établir la sécurité AS entre l'eNB et l'UE d'origine, et un identifiant temporaire que la MME attribue temporairement pour identifier l'UE d'origine dans une connexion à protocole d'application AP S1.
 
5. Procédé selon la revendication 1 ou système selon la revendication 2, dans lequel l'eNB ayant reçu le message d'établissement de contexte initial n'établit aucun porteur de données avec l'UE d'origine.
 




Drawing















































Cited references

REFERENCES CITED IN THE DESCRIPTION



This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

Patent documents cited in the description