WO2012051752A1 - Serving gateway for handling communications of mobile terminal - Google Patents

Serving gateway for handling communications of mobile terminal Download PDF

Info

Publication number
WO2012051752A1
WO2012051752A1 PCT/CN2010/077876 CN2010077876W WO2012051752A1 WO 2012051752 A1 WO2012051752 A1 WO 2012051752A1 CN 2010077876 W CN2010077876 W CN 2010077876W WO 2012051752 A1 WO2012051752 A1 WO 2012051752A1
Authority
WO
WIPO (PCT)
Prior art keywords
serving gateway
mobile terminal
configured
gw
mobility management
Prior art date
Application number
PCT/CN2010/077876
Other languages
French (fr)
Inventor
Frank Mademann
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to PCT/CN2010/077876 priority Critical patent/WO2012051752A1/en
Publication of WO2012051752A1 publication Critical patent/WO2012051752A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16Gateway arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements, e.g. access security or fraud detection; Authentication, e.g. verifying user identity or authorisation; Protecting privacy or anonymity ; Protecting confidentiality; Key management; Integrity; Mobile application security; Using identity modules; Secure pairing of devices; Context aware security; Lawful interception
    • H04W12/02Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements, e.g. access security or fraud detection; Authentication, e.g. verifying user identity or authorisation; Protecting privacy or anonymity ; Protecting confidentiality; Key management; Integrity; Mobile application security; Using identity modules; Secure pairing of devices; Context aware security; Lawful interception
    • H04W12/10Integrity
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W92/00Interfaces specially adapted for wireless communication networks
    • H04W92/16Interfaces between hierarchically similar devices
    • H04W92/24Interfaces between hierarchically similar devices between backbone network devices

Abstract

A serving gateway (S-GW) for handling communications of a mobile terminal over a communication network is provided. The S-GW comprises an interface (201) for receiving a request to allocate data transfer resources for transferring data between the mobile terminal and the S-GW, a storage (203) for providing request handling information for handling the request, and a processor (205) for initiating a procedure to allocate the data transfer resources upon the basis of the request handling information.

Description

Serving gateway for handling communications of a mobile terminal

DESCRIPTION TECHNICAL FIELD

The invention relates to the field of mobile communications. BACKGROUND OF THE INVENTION

The number of data terminals and also the amount of data transfer transactions in a mobile communication network between a mobile terminal and network's entities is continuously increasing. In this regard, the LTE/SAE system (Long Term

Evolution/Service Architecture Evolution) is designed to reduce the number of entities or nodes compared to e.g. the UMTS (Universal Mobile

Telecommunications System).

By way of example, the current LTE/SAE architecture employs a model which releases in idle phases the connection between the mobile terminal, radio, e.g. a RAN, and the core network. When a data transfer is required, then a connection between the mobile terminal and the core network may be set up again via the RAN. On the core network side, there are usually two core network entities which are involved in that process, namely a Serving Gateway (S-GW) and a Mobility Management Entity (MME). Typically, these two entities are implemented as separate core network nodes. Thus, a considerable signalling traffic may result for these two core network nodes when many mobile terminals frequently change between idle and active phases. SUMMARY OF THE INVENTION

It is the object of the invention to provide a concept for efficiently handling communications of a mobile terminal over a communication network.

This object is achieved by the features of the independent claims. Further embodiments are apparent from the dependent claims. The invention is based on the finding that some procedures which usually are handled by a Mobility Management Entity (MME) may be implemented in an S-GW. Therefore, the S-GW may be enabled to handle e.g. a service request procedure that may establish a connection between a mobile terminal and a core network, without involving the MME. By way of example, the S-GW may obtain and store parameters which may be required to establish a connection between the mobile terminal, a radio system and a core network for transferring data from or to the mobile terminal. In addition, the S-GW may be configured to perform a security function for verifying the integrity of the mobile terminal or of the signalling of the mobile terminal that initiates a connection set-up, e.g. initiates a service request procedure from the mobile terminal side. Additionally, the S-GW may obtain a paging functionality from the MME which may further simplify the handling of paging (i.e. calling idle mobile terminals for data transfer) and may reduce signalling according to some implementations. Furthermore, the S-GW may also obtain a paging functionality from a serving GPRS support node (SGSN) in order to align the paging functionality of the S-GW for LTE and UMTS radio access networks. According to a first aspect, the invention relates to an S-GW comprising an interface for receiving a request to allocate data transfer resources for transferring data between the mobile terminal and the S-GW, a storage for providing request handling information for handling the request, and a processor for initiating a procedure to allocate the data transfer resources upon the basis of the request handling information. The interface may be arranged to interface with a radio interface or with a RAN. The interface may comprise a receiver and/or a

transmitter for communicating with network entities, e.g. with the radio access network (RAN). The request handling information may comprise one of the afore- mentioned parameters.

According to a first implementation form of the first aspect, the invention relates to the S-GW, the request being a service request to establish a communication link between the mobile terminal and the S-GW. Thus, the service request e.g.

according to the 3GPP standard may at least partly be handled by the S-GW.

According to a second implementation form of the first aspect, the invention relates to the S-GW, being configured to transmit any message that implies cryptographic protection or integrity protection handling to the MME. The MME reports the outcome of that security procedure handling. The MME informs the S- GW about the outcome of the integrity check of messages. By way of example, the S-GW forwards service requests messages to the MME for checking, i.e. verifying, the integrity. According to a third implementation form of the first aspect, the invention relates to the S-GW, being configured to cryptographically identify and/or authentify and/or encrypt and/or decrypt and/or to protect and/or to check at least a part of the mobile terminal's signalling, in particular a message from the mobile terminal. The authentication of the mobile terminal and the generation of parameters/keys for security procedures may remain on the MME. The MME may provide the parameters/keys to the S-GW. By way of example, the security procedures for handling the service request may be transferred to the S-GW by the MME.

According to a fourth implementation form of the first aspect, the invention relates to the S-GW, being configured to cryptographically encrypt and/or decrypt or integrity protect and/or check all messages to/from the mobile terminal that require security procedures. The messages may be directly provided to the S-GW by the mobile terminal, in particular in a set-up phase of a communication link. By way of example, all security procedures are transferred to the S-GW by the MME.

According to a fifth implementation form of the first aspect, the invention relates to the S-GW, wherein the storage is configured to store cryptographic information, in particular a cryptographic key, for identifying or authentifying the mobile terminal, or for encrypting or decrypting or integrity protecting or checking a message from or to the mobile terminal. The cryptographic information may be perceived by the S-GW from an earlier service request that was served by the MME or may be provided to the S-GW by the MME.

According to a sixth implementation form of the first aspect, the invention relates to the S-GW, being configured to transmit information relating to a location of the mobile terminal towards a communication network, in particular towards a public data network gateway, e.g. when a service request procedure triggers the transmission, e.g. because the location changed compared to the last informed location. According to a seventh implementation form of the first aspect, the invention relates to the S-GW, wherein the service request procedure comprises

establishing the communication channel for a transition of the mobile terminal from an idle state to an active state. This may comprise establishing or modifying a radio bearer.

According to an eighth implementation form of the first aspect, the invention relates to the S-GW, wherein the interface is configured for interfacing between the S-GW and a radio system, e.g. E-UTRAN (evolved UMTS Terrestrial Radio Access Network), and wherein the interface is configured to communicate according to the interface definition for the S1 Mobility Management Entity (S1 MME) according to the LTE technology. According to a ninth implementation form of the first aspect, the invention relates to the S-GW, wherein the interface is configured to intercept a signalling between a mobile terminal, in particular over an E-UTRAN according to the LTE technology, and an MME according to the LTE technology. According to a tenth implementation form of the first aspect, the invention relates to the S-GW, wherein the interface is configured to receive cryptographic information from an MME, and wherein the processor is configured to perform a security procedure for verifying the authenticity or integrity of the received request upon the basis of the received cryptographic information.

According to a an eleventh implementation form of the first aspect, the invention relates to the S-GW, wherein the storage is configured to store cryptographic information provided by an MME in response to an earlier request that was processed by the MME. The S-GW does not verify the authenticity of subsequent requests and establishes resources using stored cryptographic information. The S- GW counts the number of procedures without verification and gives every Nth request to the MME for processing to avoid that the counters involved in

authenticity or integrity verification are outside the interval that can still be synchronized without causing detection of security issues.

According to a twelfth implementation form of the first aspect, the invention relates to the S-GW, being configured to perform a message verification procedure e.g. for authenticity or integrity and to indicate a result of the message verification procedure to an MME so that the MME does not perform a message verification procedure. According to a thirteenth implementation form of the first aspect, the invention relates to the S-GW, wherein the processor is configured to trigger the interface to transmit a request towards the communication network, in particular towards an MME according to the LTE technology, for verifying authenticity or integrity of the received service request.

According to a fourteenth implementation form of the first aspect, the invention relates to the S-GW, wherein the processor is configured to store information, in particular an identity of a serving radio node, location information, cell identity or area identity, to decide whether it can process the request or whether the request is to be forwarded towards an MME for processing, e.g. when the MME performs a location tracking or when location restrictions apply. In addition, the MME may indicate for which mobile terminals the S-GW can perform the service request without involving the MME, possibly also giving criteria, e.g. as long as the serving radio node or the location is not changed.

According to a fifteenth implementation form of the first aspect, the invention relates to the S-GW, wherein the interface is configured to receive Non Access Stratum (NAS) security related information from an MME, the NAS security information comprising in particular a NAS message counter, a NAS security key and/or a NAS coding algorithm, and wherein the processor is configured to update a current NAS message counter parameter with the received NAS message counter parameter. The interface may optionally be configured to provide a NAS message counter to the MME so that the MME can update its NAS message counter for performing NAS security procedures.

According to a sixteenth implementation form of the first aspect, the invention relates to the S-GW, wherein the interface interfaces to a radio system and is configured to page the mobile terminal. This may also be processor specific functionality to page when downlink data arrive. By assuming the S-GW adopts the S1 Mobility Management Entity (S1 MME) interface, the paging may already be included.

According to a seventeenth implementation form of the first aspect, the invention relates to the S-GW, being configured to manage communications of the mobile terminal according to the LTE technology. According to an eighteenth implementation form of the first aspect, the invention relates to the S-GW, wherein the interface of the S-GW is configured to receive communications for an MME via an S1 MME interface, and to forward the communications towards the MME.

According to a second aspect, the invention relates to a communication system according to the Long Term Technology, the communication system comprising an MME, a E-UTRAN radio system forming e.g. a radio interface, and the S-GW, the interface of the S-GW being configured to receive communications towards the MME via an S1 MME interface from the E-UTRAN radio system, and to forward the communications towards the MME.

According to a third aspect, the invention relates to a method for handling communication of a mobile terminal by an S-GW, the method comprising receiving a request to allocate data transfer resources for transferring data between the mobile terminal and the S-GW, providing request handling information for handling the request, and initiating a procedure to allocate the data transfer resources upon the basis of the request handling information.

According to a fourth aspect, the invention relates to a communication method for communicating according to the Long Term Technology using an MME, an E- UTRAN radio system and the inventive S-GW, the communication method comprising receiving communications towards the MME via an S1 Mobile

Management Entity interface from the E-UTRAN radio system by the S-GW, and forwarding the communications towards the MME by the S-GW. Further embodiments of the invention will be described with reference to the following figures, in which: Fig. 1 shows a communication system according to an implementation form;

Fig. 2 shows a block diagram of an S-GW according to an implementation form; Fig. 3 shows a service request procedure according to an implementation form;

Fig. 4 shows a service request procedure according to an implementation form;

and Fig. 5 shows a service request procedure according to an implementation form. DESCRIPTION OF THE DRAWINGS

Fig. 1 shows an implementation form of a communication system based on the Long Term Evolution (LTE) technology. The communication system comprises a serving gateway 101 (S-GW), a Mobility management entity 103 (MME) and a mobile terminal 105 forming an embodiment of user equipment (UE). The

communication system further comprises an E-UTRAN radio system 107 (evolved UMTS Terrestrial Radio Access Network) forming a radio interface between the mobile terminal 105 and the S-GW 101 . The communication system further comprises a home subscriber server 109 (HSS) which is in communication with the MME 103. The communication system further comprises a serving GPRS support node 11 1 (SGSN) which is in communication with the MME 103 and the S-GW 101 . The S-GW 101 further communicates with a public data network (PDN) gateway 1 13 which is in communication with a policy and charging rules function 1 15 (PCRF) and operators IP services 1 17, such as IMS or PSS. The mobile terminal 105 may communicate with the E-UTRAN radio system 107 on the basis of the LTE-Uu interface. The E-UTRAN radio system 107

communicates with the S-GW 101 over the S1 -MME Interface. In this regard, the S-GW 101 may be configured to forward the S1 -MME messages towards the MME 103 via an S1 -MME relay 1 19. Thus, the S1 -MME signalling between the E- UTRAN radio system 107 and the MME 103 is not performed directly between the E-UTRAN radio system 107 and the MME 103. Rather, the S-GW 101 may form an intermediate node receiving and forwarding the S1 -MME signalling from and towards the E-UTRAN radio system 107 and the MME 103. The MME 103 may communicate with the SGSN 11 1 via the S3 interface, wherein the

communications between the MME 103 and the HSS 109 may be based upon the S6a interface. Furthermore, the MME 103 and S-GW 101 may communicate upon the basis of the S1 1 interface. The S-GW 101 communicates with e.g. a UTRAN communication network over the S12 interface. Moreover, the S-GW 101 may communicate with the PDN gateway 1 13 over the S5 interface. The PDN gateway 1 13 communicates with the PCRF 1 15 over the Gx interface, wherein the PCRF 1 15 communicates with the Operators IP Services 117 via the Rx interface and via the SGi interface. Referring to the communication system shown in Fig. 1 , the relations and functions between E-UTRAN radio system 107, S-GW 101 and MME 103 have been modified with respect to the S1 -MME signalling in that all S1 -MME signalling between the E-UTRAN radio system 107 and the MME 103 is looped via the S- GW 101 . This allows the S-GW 101 to handle frequent transactions as the Service Request procedures or its simple version. As a simple Service Request procedure we denote the subset of those procedures that do not require more from the MME 103 than setting up the S1 connection between the E-UTRAN radio system 107 and the S-GW 101 , which is to establish a data path for the mobile terminal 105. It may also include setting up the radio bearers and may thus also be called "idle to active transition" for data transfer. According to some implementation forms, the simple Service Requests are idle to active transitions for data transfer, i.e. establishing S1 and radio interface resources, without any additional functionality. Other requests than simple Service Requests may still be handled by the MME 103, e.g. when special checks may be performed during the Service Request procedure or when errors occur.

In order to be able to handle simple Service Request procedures by the S-GW 101 without involving the MME 103, the S-GW 101 may store some or all parameters that are required to handle the simple Service Request procedure. In this regard, the function S1 -Relay 119 may derive the parameters which may be required for handling simple Service Requests from the S1 signalling between MME 103 and the E-UTRAN radio system 107 as this signalling is looped through the S-GW 101 . In addition, some parameters may also be provided by the MME 103 to the S-GW 101 . Therefore, alternatively, also a signalling may be introduced that provides required parameters directly from the MME 103 to the S-GW 101 so that the S- GW 101 does not need to derive these parameters from the S1 signalling.

In addition, the S-GW 101 may be able to perform security procedures that may be deployed when handling the simple Service Request procedure. Thus, these procedures may not be performed by the MME 103. By way of example, the S-GW 101 comprises in this regard the functionality of an MME according to the 3GPP standard, and comprises the parameters to be able to verify the integrity of the Service Request message without involving the MME 103. Furthermore, the S-GW 101 may also be configured to perform an integrity check or integrity protection of messages from or to the mobile terminal.

According to some implementation forms, the S-GW 101 may also ask the MME 103 to check the message integrity, which involves the MME 103 for this part. However, the signalling is still reduced and security functions on the S-GW 101 may be avoided.

According to some implementation forms, all security functions for integrity and/or encryption of terminal NAS messages as e.g. addressed in the following may be allocated on the S-GW 101. Then the S-GW 101 indicates to the MME 103 whether the integrity check was successful for messages that are processed by the MME. However, the authentication function, which derives the security keys for other security functions, may remain on the MME 103.

The radio system, i.e. radio interface, E-UTRAN and its elements such as an eNodeB which is not shown in Fig. 1 may remain unaffected by the enhanced functionality of the S-GW 101 , apart from a possible adaptation of a configuration of these entities. In particular, from eNodeB's point of view it may still look like being connected with the MME 103. The routing by the eNodeB may be based on an MME identification (ID) or on MME-code. In order to enable routing of the S1- MME connection via different S-GWs 101 , the MME 103 may get multiple MME- IDs/codes assigned when multiple S-GWs 101 are used. The MME 103 may obtain at least one MME-ID/code for each S-GW 101 that the MME 103 can use or select. The S-GW 101 may also use the MME-ID to route signals to the right MME when serving multiple MMEs, or the S-GW 101 may derive the related MME from the S1 connection that is used between the eNodeB and an MME as there may be a dedicated S1 connection towards the eNodeB for each MME served by the S- GW 101 .

According to some implementation forms, the MME 103 may be enhanced to interwork with or support the S-GW functionality of the S-GW 101 that is

introduced by the principles described herein. By way of example, the MME 103 may provide the S-GW 101 with any information required to handle simple Service Requests autonomously, which includes parameters like updated RAB parameters, security parameters or mobility management data for paging. Furthermore, the MME 103 may handle temporary IDs to allocate temporary IDs with the MME IDs/codes that are specific per used/selected S-GW.

In order to enable a security function on the S-GW 101 , the MME 103 may provide the S-GW 101 with NAS message counters and key parameters that are stored by the S-GW 101 . According to some implementation forms related to handling security parameters, a (or every) S1 release by the MME 103 may provide the NAS message counter and NAS key(s) and NAS security algorithm(s) to the S- GW 101 . Further, a (or every) S1 setup between the S-GW 101 and the MME 103 may provide the counters from the S-GW 101 to the MME 103. This may be performed to keep the parameters synchronised in the S-GW 101 and in the MME 103 with the parameters in the mobile terminal as otherwise security functions may detect security issues. According to some implementation forms, all security functions are on the S-GW 101 or the MME 103 may check the integrity of the Service Request message, where upon other handling of the security parameters may apply. According to some implementation forms, the network triggered Service Request procedures may also be performed according to the principles described herein . In addition, the paging functionality can be moved from the MME 103 and also from a SGSN of the UMTS architecture to the S-GW 103, which will be addressed in connection with Fig. 5.

Fig. 2 shows a block diagram of a serving gateway (S-GW) 200 for handling communications of a mobile terminal according to an implementation form. The S- GW comprises an interface 201 , e.g. an interface towards a RAN, for receiving a request for providing or allocating data transfer resources for transferring data between the mobile terminal and the S-GW, a storage 203 for providing request information for handling the request, and a processor 205 for initiating a procedure allocating data transfer resources upon the basis of the request handling information. With reference to Figs. 1 and 2, the S1 relay 119 shown in Fig. 1 may be provided by the interface 201 and/or by the processor 205. The data transfer resources may comprise a communication channel between the mobile terminal and the S-GW. Correspondingly, the request handling information relate to parameters, which are usually handled or provided by an MME for handling e.g. a service request according to the 3GPP standard.

The S-GW 200 may be configured to perform a method for handling

communications of a mobile terminal. In this case, the structure shown in Fig. 2 correspondingly depicts the method steps. Fig. 3 shows a service request procedure which may be performed by the S-GW of Fig. 2 in a communication system, e.g. in the communication system of Fig. 1 additionally having a radio network node 301 , e.g. an eNodeB according to the 3GPP standard.

In step 1 , the mobile terminal 103 transmits a Non-Access Stratum (NAS) service request towards the eNodeB 301 . The mobile terminal 103 sends the NAS message Service Request e.g. encapsulated in a Radio Resource Control (RRC) message to the eNodeB 301 . The RRC message(s) that can be used to carry the S-TMSI (Serving Temporary Mobile Subscriber Identity) and this NAS message are described in the 3GPP TS 36.300 specification.

In step 2, the eNodeB 301 forwards the NAS service request towards the S-GW 101 . In step 2A, the NAS service request may be forwarded to the MME 103.

In particular, the eNodeB 301 forwards the NAS message to the MME 103 via the S-GW 101 . The NAS message is encapsulated in an S1 -AP (S1 Application Protocol (for S1 interface)): Initial UE Message (NAS message, TAI+ECGI

(Tracking Area identity + E-UTRAN Cell Global Identifier) of the serving cell, S- TMSI, CSG ID (Closed Subscriber Group Identity), CSG access Mode) as e.g. described in the 3GPP TS 36.300 specification. The CSG ID is provided if the mobile terminal 105 sends the Service Request message via a CSG (Closed

Subscriber Group) cell or via a hybrid cell. A CSG access mode may be provided if the mobile terminal 105 sends the Service Request message via a hybrid cell. If the CSG access mode is not provided but the CSG ID is provided, the MME 103 may consider the cell as a CSG cell.

If the S-GW 101 cannot handle the Service Request, then the S-GW 101 may forward the NAS message to the MME 103 together with a NAS message counter if stored. This may be performed when the S-GW 101 has no sufficient data to handle the Service Request or if further handling is required, e.g. when the mobile terminal 105 has changed the CSG or changed RAT (Radio Access Technology) or error handling. Further, the S-GW 101 may forward the Service Requests when re-authentication is required, e.g. when a certain number of Service requests is exceeded or a certain data volume or a certain usage time. The NAS message counter may indicate the actual counter value belonging to the message, a short form of it or is just the number of NAS messages processed by the S-GW 101 without involving the MME 103 so that the MME 103 can adjust its message counter. If the MME 103 cannot handle the Service Request it may reject the Service Request.

If a CSG ID is indicated and CSG access mode is not provided, and there is no subscription data for this CSG ID or the CSG subscription is expired, the MME rejects the Service Request with an appropriate cause. The mobile terminal 105 may remove the CSG ID of the cell where the mobile terminal 105 has initiated the service request procedure from an allowed CSG list, if present.

If the mobile terminal 105 has emergency EPS (Evolved Packet System) bearers, i.e. if at least one EPS bearer has an ARP (Allocation and Retention Priority) value reserved for emergency services, or if CSG access restrictions do not allow the mobile terminal 105 to obtain normal services, then the MME 103 may deactivate all non-emergency bearers and accept the Service Request. Subsequently, in step 3, authentification or security procedures may be performed between the mobile terminal 105 and the MME 103 and between the MME 103 and the HSS 109 as defined in the 3GPP TS 33.401 standard. In step 4A, an S1 -AP initial context set-up request may be transmitted from the MME 103 towards the S-GW 101. Thereafter, in step 4, the initial context set-up request may be forwarded by the S-GW 101 towards the eNodeB 301 . The S-GW 101 stores the information received from MME 103 as needed for processing of subsequent Service Requests without involving the MME 103.

In step 4, the S-GW 101 sends S1 -AP Initial Context Setup Request including an S-GW address, S1-TEID(s) (Tunnel Endpoint Identifier (for S1 interface)) (UL), EPS Bearer QoS(s), Security Context, MME Signalling Connection Id, Handover Restriction List, CSG Membership Indication) message to the eNodeB 301 . This step may activate the radio and S1 bearers for all the active EPS Bearers. The eNodeB 301 stores the Security Context, MME Signalling Connection I D, EPS Bearer QoS(s) and S1 -TEID(s) in the UE RAN context, described e.g. in the 3GPP TS 36.300 specification. If step 2a is not performed, i.e. if the MME 103 is not involved, then the S-GW 101 performs step 4 by using stored information.

The MME 103 may request to establish Emergency EPS Bearer if the mobile terminal 105 is not allowed to access the cell where the mobile terminal 105 initiated the service request procedure due to CSG access restriction.

If the Service Request is performed via a hybrid cell, then CSG Membership Indication indicating whether the mobile terminal 105 is a CSG member may be included in the S1 -AP message from the MME 103 to the RAN. Based on this information, the RAN may perform differentiated treatment for CSG and non-CSG members. In step 5, a radio bearer establishment procedure is performed between the mobile terminal 105 and the eNodeB 301 .

In this regard, the eNodeB 301 may perform the radio bearer establishment procedure. The user plane security is established at step 5 as e.g. described in the 3GPP TS 36.300 specification. When the user plane radio bearers are setup, an EPS bearer state synchronization may be performed between the mobile terminal 105 and the network, i.e. the mobile terminal 105 may locally remove any EPS bearer for which no radio bearers are setup and, if the radio bearer for a default EPS bearer is not established, the mobile terminal 105 may locally deactivate all EPS bearers associated to that default EPS bearer.

In step 6, uplink data are transmitted by the mobile terminal 105 via the eNodeB 301 , the S-GW 101 , the MME 103 towards the PDN gateway 1 13.

The uplink data from the mobile terminal 105 may now be forwarded by the eNodeB 301 to the S-GW 101 . The eNodeB 301 sends the uplink data to the address of the S-GW 101 , and TEID provided in the step 4. The S-GW 101 forwards the uplink data to the PDN gateway 1 13.

Thereafter, in step 7, an S1-AP initial context set-up complete message is transmitted by the eNodeB 301 towards the S-GW 101 . Subsequently, in step 7A, the S1 -AP initial context set-up complete message is forwarded by the S-GW 101 towards the MME 103 which responds with the delete bearer request in step 8.

In reference to step 7, the eNodeB 301 sends an S1 -AP message Initial Context Setup Complete including eNodeB address, List of accepted EPS bearers, list of rejected EPS bearers, S1 TEID(s) (DL) to the S-GW 101 , as e.g. described in the 3GPP TS 36.300 specification. The S-GW 103 is now able to transmit downlink data towards the mobile terminal 105. In reference to step 7a, the S-GW 101 forwards the message to the MME 103 if the MME 103 is involved in the procedure of if one or more RABs were not accepted by the eNodeB 301 .

If a default EPS bearer is not accepted by the eNodeB, all the EPS bearers associated to that default bearer may be treated as non-accepted bearers. The MME releases the non-accepted bearers by triggering the bearer release procedure as specified in 3GPP standard. If the S-GW 101 receives a download (DL) packet for a non-accepted bearer, the S-GW 101 drops the DL packet and does not send a Downlink Data Notification to the MME 103.

In step 9, a modify bearer request message is transmitted between the S-GW 101 and the PDN gateway 1 13. If the RAT Type has changed compared to the last reported RAT Type or if the location of the S-GW 101 or CSG need to be reported, then the S-GW 101 may send the Modify Bearer Request message (RAT Type) per PDN connection to the PDN gateway 1 13. The User Location Information IE and/or User CSG Information IE may also be included.

Subsequently, in step 10 a PCF-initiated IP CAN session modification may be executed. If dynamic PCC (Policy and Charging Control) is deployed, then the PDN gateway 1 13 may interact with the PCRF 1 15 to obtain the PCC rule(s) according to the RAT Type by means of a PCEF initiated IP-CAN Session

Modification procedure as e.g. described in the 3GPP TS 23.203 specification. If dynamic PCC is not deployed, then the PDN gateway 1 13 may apply local QoS policy.

Thereafter, in step 1 1 , a modified bearer response may be transmitted by the PDN gateway 1 13 towards the S-GW 101 .

With reference to Fig. 3, the S-GW 101 , which may have the structure of the S- GW 200, stores all parameters needed to handle the most frequent procedure cases that do not require any specific action from the MME 103 other than verifying the integrity of the Service Request message and providing the eNodeB 301 with the stored bearer and security parameters. Procedures other than simple Service Requests, e.g. with error handling, may by processed by the MME 103. By way of example, for a Proxy Mobile IP (PMIP) based S5/S8, the procedure steps 9 and 10 concerning the GTP-based S5/S8 may correspond to those as defined in the 3GPP TS 23.402 standard.

According to some implementation forms, also some problematic conditions of the current UE triggered Service Request procedure may be avoided by the invention. By way of example, under certain conditions, the current Service Request procedure when initiated by the mobile terminal 105 can cause immediate

Downlink Packet Notification messages towards the MME 103, which may be considered as a problem according to some implementations. This may occur when uplink data cause response data on the downlink which arrive at the S-GW 101 before the connection is established for the downlink data. This problem may be avoided as the signalling happens directly between mobile terminal 105 and S- GW 101 without involving the MME 103 that might introduce some delay. Fig. 4 shows a network triggered service request procedure in the context of the communication network shown in Fig. 1 . Furthermore, a RNC/BSC 401 may be provided.

In step 1 , the PDN gateway 1 13 may forward downlink data towards the S-GW 103 which, in step 2A, transmits a downlink data notification towards the MME 103. The MME 103 responds in step 2B with the downlink data notification

acknowledgement.

Alternatively, in step 2A, the S-GW 101 may transmit the downlink data notification towards the SGSN 1 1 1 which, in step 2B, responds with the downlink data notification acknowledgement. In step 3A, the MME 103 initiates paging towards the eNodeB 301 . In step 3b, the paging may be initiated by the SGSN 1 1 1 towards the RNC/BSC 401 .

In step 4A, the eNodeB 301 or, in step 4B, the RNC/BSC 401 pages the mobile terminal 105.

In step 5, a service request procedure is executed. Thereafter, in step 6A, a stop paging message is transmitted by the S-GW 101 towards the SGSN 1 1 1 or, in step 6B, towards the MME 103. Thereafter, a downlink data transmission may be performed.

Fig. 5 shows a network-triggered service request procedure according to an implementation form. Unlike in Fig. 4, in step 3A, the S-GW 101 initiates paging towards the eNodeB 301 or towards the RNC/BSC 401 by step 3b. Thereafter, the steps 4A, 4B, 5 and the downlink data transfer may be performed as in Fig. 4. Furthermore, according to Fig. 5, the steps 2a and 2b and/or the steps 6a and 6b as shown in Fig. 4 may be omitted.

With reference to Figs. 4, the network-triggered service request procedure is initiated when downlink data have to be transferred to a mobile terminal 105 that is in ECM (EPS Connection Management) IDLE state. But also if the MME 103 needs to signal with the mobile terminal 105 that is in ECM-IDLE state, e.g. to perform the MME/HSS-initiated detach procedure for the ECM-IDLE mode, or if the mobile terminal 105 or the S-GW 101 receives control signalling, e.g. Create Dedicated Bearer Request or Modify Dedicated Bearer Request, then the MME 103 starts network triggered service request procedure from step 3.

If ISR is activated, when the S-GW 103 receives a Create Dedicated Bearer Request or Modify Bearer Request for the mobile terminal 105, and the S-GW 101 does not have a downlink S1 -U and the SGSN 403 has notified the S-GW 101 that the mobile terminal 105 has moved to PMM-IDLE or STANDBY state, then the S- GW 101 buffers signalling messages and triggers MME 103 and SGSN 403 to page the mobile terminal 105. In this case the S-GW 101 may be notified about the current RAT type based on the UE triggered service request procedure. The S-GW 101 may continue executing the dedicated bearer activation or dedicated bearer modification procedure, i.e. send the corresponding buffered signalling to the MME 103 or SGSN 403 which mobile terminal resides in now and inform the current RAT type to the PDN gateway 1 13 if the RAT type has been changed compared to the last reported RAT Type. If dynamic PCC is deployed, the current RAT type information may also be conveyed from the PDN gateway 113 to the PCRF 1 15. If the PCRF 1 15 response leads to an EPS bearer modification the PDN gateway may initiate a bearer update procedure described in the following:

With reference to step 1 , when the S-GW 101 receives a downlink data packet for a UE known as not user plane connected, i.e. if the S-GW context data indicates no downlink user plane TEID), then S-GW 101 buffers the downlink data packet.

With reference to step 3a, if the mobile terminal 105 is registered in the MME 103, then the S-GW 101 sends a paging message including e.g. NAS ID for paging, TAI(s), UE identity based DRX (Discontinuous Reception) index, Paging DRX length, list of CSG IDs for paging, to each eNodeB 301 belonging to the tracking area(s) in which the mobile terminal 105 is registered, as e.g. described in the specifications 3GPP TS 36.300 and 3GPP TS 36.413. According to some implementation forms, the steps 3 and 4 shown in Fig.4 may be omitted if the MME 103 already has a signalling connection over S1 -MME towards the mobile terminal 105.

When the MME 103 is configured to support paging optimisation in the core network (CN), then the MME 103 may avoid sending paging messages to those eNodeB(s) with CSG cells for which the mobile terminal 105 does not have a CSG subscription. When the MME 103 is configured to support paging optimisation in the eNodeB 301 , then the list of CSG IDs for paging may be included in the paging message. For paging optimisation, the CSG IDs of expired CSG subscriptions and valid CSG subscriptions may be both included in the list. If the mobile terminal 105 has emergency bearer service, then the MME 103 may not perform the paging optimization. According to some implementation forms, the eNodeB 301 reports to the MME 103 the CSG ID as e.g. described in the 3GPP TS 36.413 specification.

With reference to step 3b, if the mobile terminal 105 is registered in the SGSN, then the S-GW 101 sends paging messages to RNC/BSS, as described in the 3GPP TS 23.060 specification.

With reference to step 4a, if the eNodeB 301 receives paging messages from the MME 103, then the mobile terminal 105 may be paged by the eNodeB 301 as described in the specifications 3GPP TS 36.300 and 3GPP TS 36.304 .

With reference to step 4b, if the RNC/BSS 401 receives paging messages from the SGSN 403, then the mobile terminal 105 is paged by the RNSC/BSS 401 as e.g. described in the 3GPP TS 23.060 specification.

With reference to step 5, when the mobile terminal 105 is in the ECM-IDLE state, upon reception of paging indication in E-UTRAN access, then the mobile terminal 105 initiates the UE triggered Service Request procedure according to the principles described herein. If the MME 103 already has a signalling connection over S1 -MME towards the mobile terminal 105, then the messages sequence performed start from the step when the MME 103 establishes the bearer(s).

Upon reception of paging indication in UTRAN or GERAN access, the mobile terminal 105 may respond in respective access as specified in the 3GPP

TS 24.008 specification and the SGSN 403 may notify the S-GW 101 .

The S-GW 101 may supervise the paging procedure with a timer. If there is no response from the mobile terminal 105 to the paging request message, it may repeat the paging. The repetition strategy is operator dependent. In the case of paging optimization, paging optimization may be disabled. If the MME 103 and/or the SGSN 403 receive no response from the mobile terminal 105 after this paging repetition procedure, it may use the Downlink Data Notification Reject message to notify the S-GW 101 about the paging failure. In that case, if ISR is not activated, the S-GW 101 may delete the buffered packet(s). If ISR is activated and the S-GW 101 receives paging failure from both SGSN 403 and the MME103, then the S-GW 101 may delete the buffered packet(s) or rejects the control signalling which triggers the Service Request procedure.

The S-GW 101 transmits downlink data towards the mobile terminal 105 via the RAT which performed the Service Request procedure.

Claims

CLAIMS:
1 . Serving gateway for handling communications of a mobile terminal over a communication network, the serving gateway comprising: an interface (201 ) for receiving a request to allocate data transfer resources for transferring data between the mobile terminal and the serving gateway; a storage (203) for providing request handling information for handling the request; and a processor (205) for initiating a procedure to allocate the data transfer resources upon the basis of the request handling information.
2. Serving gateway of claim 1 , being configured to transmit a message that implies cryptographic handling or integrity protection handling towards a Mobility Management Entity over the communication network.
3. The serving gateway of claim 1 or 2, the request being a service request to establish a communication link between the mobile terminal and the serving gateway.
4. The serving gateway of any of the preceding claims, being configured to cryptographically identify or authentify a message to or from the mobile terminal.
5. The serving gateway of any of the preceding claims, being configured to cryptographically encrypt or decrypt a message to or from the mobile terminal or perform an integrity protection or an integrity check of a message to or from the mobile terminal.
6. The serving gateway of any of the preceding claims, wherein the storage (203) is configured to store cryptographic information, in particular a cryptographic key, for identifying or authentifying the mobile terminal, or for encrypting or decrypting or perform an integrity protect or an integrity check of a message or the transferred data from or to the mobile terminal.
7. The serving gateway of any of the preceding claims, being configured to transmit information relating to a location of the mobile terminal towards a communication network, in particular triggered by a service request towards a public data network gateway.
8. The serving gateway of any of the preceding claims, wherein the service request procedure comprises establishing a communication channel for a transition of the mobile terminal from an idle state to an active state.
9. The serving gateway of any of the preceding claims, wherein the interface (201 ) is configured for interfacing between the serving gateway (200) and a radio system, and wherein the interface (201 ) is configured to communicate according to the interface definition for the S1 Mobility Management Entity according to the Long Term Evolution technology.
10. The serving gateway of any of the preceding claims, wherein the interface (201 ) is configured to intercept a signaling between a mobile terminal, in particular over an E-UTRAN according to the Long Term Evolution technology, and a Mobility Management Entity according to the Long Term Evolution technology.
1 1 . The serving gateway of any of the preceding claims, wherein the interface (201 ) is configured to receive cryptographic information from a Mobility
Management Entity, and wherein the processor (205) is configured to perform a security procedure for verifying the authenticity or integrity of the received request from a mobile terminal upon the basis of the received cryptographic information .
12. The serving gateway of any of the preceding claims, wherein the storage (203) is configured to store cryptographic information provided by a Mobility Management Entity in response to an earlier request that was processed by the Mobility Management Entity.
13. The serving gateway of any of the preceding claims, being configured to perform a message integrity verification procedure and to indicate a result of the message verification procedure to a Mobility Management Entity.
14. The serving gateway of any of the preceding claims, wherein the processor (205) is configured to trigger the interface (201 ) to transmit a request towards a Mobility Management Entity according to the Long Term Evolution technology, for requesting the Mobility Management Entity to verify the integrity of the received service request.
15. The serving gateway of any of the preceding claims, wherein the processor (205) is configured to store information, in particular an identity of serving radio node, location information, cell identity or area identity, to decide whether it can process the request of whether the request is to be forwarded towards a Mobility Management Entity.
16. The serving gateway of any of the preceding claims, wherein the interface is configured to receive Non Access Stratum, NAS, information by a message from the Mobility Management Entity, the message comprising parameters, in particular a NAS message counter, a NAS security key and/or a NAS security algorithm, and wherein the processor is configured to update a current NAS message counter parameter with the received NAS message counter parameter.
17. The serving gateway of any of the preceding claims, wherein the interface (101 ) is configured to page the mobile terminal.
18. The serving gateway of any of the preceding claims, being configured to manage communications of the mobile terminal according to the Long Term Evolution technology.
19. The serving gateway of any of the preceding claims, wherein the interface (201 ) is configured to receive communications for a Mobility Management Entity via an S1 Mobility Management Entity interface, and to forward the
communications towards the Mobility Management Entity.
20. A communication system according to the Long Term Technology, the communication system comprising: a Mobility Management Entity (103); a E-UTRAN radio system (107); and the serving gateway (101 , 200) of any of the preceding claims, the interface (201 ) of the serving gateway (101 , 200) being configured to receive communications towards the Mobility Management Entity (103) via an S1 Mobility Management Entity interface from the E-UTRAN interface (107), and to forward the
communications towards the Mobility Management Entity (107).
21 . A method for handling communications of a mobile terminal by a serving gateway, the method comprising: receiving a request to allocate data transfer resources for transferring data between the mobile terminal and the serving gateway; providing request handling information for handling the request; and initiating a procedure to allocate the data transfer resources upon the basis of the request handling information.
22. A communication method for communicating according to the Long Term Technology using a Mobility Management Entity, a E-UTRAN interface and the serving gateway according to any of the claims 1 to 18, the communication method comprising: receiving communications towards the Mobility Management Entity via an S1 Mobility Management Entity interface from the E-UTRAN radio system by the serving gateway, and forwarding the communications towards the Mobility Management Entity by the serving gateway.
PCT/CN2010/077876 2010-10-19 2010-10-19 Serving gateway for handling communications of mobile terminal WO2012051752A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2010/077876 WO2012051752A1 (en) 2010-10-19 2010-10-19 Serving gateway for handling communications of mobile terminal

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201080025277.XA CN102812771B (en) 2010-10-19 2010-10-19 Service gateway for a communication process of the mobile terminal
PCT/CN2010/077876 WO2012051752A1 (en) 2010-10-19 2010-10-19 Serving gateway for handling communications of mobile terminal

Publications (1)

Publication Number Publication Date
WO2012051752A1 true WO2012051752A1 (en) 2012-04-26

Family

ID=45974619

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/077876 WO2012051752A1 (en) 2010-10-19 2010-10-19 Serving gateway for handling communications of mobile terminal

Country Status (2)

Country Link
CN (1) CN102812771B (en)
WO (1) WO2012051752A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI501610B (en) * 2009-03-27 2015-09-21 Nokia Corp Method and apparatus for providing shared services
EP2903362A4 (en) * 2012-09-25 2016-05-25 Nec Corp Gateway apparatus, mobile communication system, and paging method
CN106254018A (en) * 2016-08-12 2016-12-21 深圳欧奇科技有限公司 High-speed signal receiving and multipath de-multiplexing integrated system and data processing method

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104170420B (en) * 2013-04-02 2018-10-30 华为技术有限公司 Open wireless method and apparatus of pipeline capacity

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040132166A1 (en) * 2001-04-10 2004-07-08 Bioprocessors Corp. Determination and/or control of reactor environmental conditions
US6905834B1 (en) * 1997-11-25 2005-06-14 Ut-Battelle, Llc Bioluminescent bioreporter integrated circuit detection methods
US20090156914A1 (en) * 2005-11-10 2009-06-18 Nellcor Puritan Bennett Llc Medical sensor and techinique for using the same
US20100207035A1 (en) * 2009-01-23 2010-08-19 Govind Rao Fluorescence based sensors utilizing a mirrored cavity

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8855138B2 (en) * 2008-08-25 2014-10-07 Qualcomm Incorporated Relay architecture framework
JP5320618B2 (en) * 2008-10-02 2013-10-23 株式会社日立製作所 Routing control method and an access gateway apparatus

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6905834B1 (en) * 1997-11-25 2005-06-14 Ut-Battelle, Llc Bioluminescent bioreporter integrated circuit detection methods
US20040132166A1 (en) * 2001-04-10 2004-07-08 Bioprocessors Corp. Determination and/or control of reactor environmental conditions
US20090156914A1 (en) * 2005-11-10 2009-06-18 Nellcor Puritan Bennett Llc Medical sensor and techinique for using the same
US20100207035A1 (en) * 2009-01-23 2010-08-19 Govind Rao Fluorescence based sensors utilizing a mirrored cavity

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI501610B (en) * 2009-03-27 2015-09-21 Nokia Corp Method and apparatus for providing shared services
EP2903362A4 (en) * 2012-09-25 2016-05-25 Nec Corp Gateway apparatus, mobile communication system, and paging method
US9681415B2 (en) 2012-09-25 2017-06-13 Nec Corporation Gateway device, mobile communication system, and paging method
CN106254018A (en) * 2016-08-12 2016-12-21 深圳欧奇科技有限公司 High-speed signal receiving and multipath de-multiplexing integrated system and data processing method

Also Published As

Publication number Publication date
CN102812771A (en) 2012-12-05
CN102812771B (en) 2017-04-12

Similar Documents

Publication Publication Date Title
EP2702712B1 (en) Method for processing data associated with session management and mobility management
EP2567573B1 (en) Method and apparatus for performing handover
US8694003B2 (en) LTE RRC connection re-establishment requesting method, cause value setting method and terminal
JP4863530B2 (en) Wireless device and a base station for handover method for link failure recovery and to implement this method
US20180139671A1 (en) Short message transmission and handover procedures
CN103875196B (en) Method and apparatus in a mobile communication system to efficiently support multiple frequency bands for
WO2011055999A2 (en) Method and apparatus for transmitting data in a wireless communication network system
EP2742705B1 (en) Method for processing data associated with idle mode signaling reduction in a wireless communication system
US20110269499A1 (en) Method and arrangement for load balancing in a wireless communication system
US20120069737A1 (en) Overload avoidance with home node b gateway (henb gw) in lte
KR101903041B1 (en) Method and apparatus for transmitting and receiving data in mobile communication system
US20100226314A1 (en) Method for user equipment performing direct communications via hnb access systems
CN102340754B (en) Data transmission and receiving methods and equipment
US8971268B2 (en) Method and apparatus for transmitting uplink data associated with MTC device trigger function
CN101977416B (en) Overload control method and system apparatus mtc
WO2007078159A1 (en) Method and apparatus for transmitting sip data of idle mode ue in a mobile communication system
CN103609150B (en) Traffic diversion via the local network based apn apn proprietary or non-proprietary information
EP2584805B1 (en) Wireless communication system and method for establishing a connection between user equipment and a mobility management entity thereof
CN102340826B (en) A data transmission method and apparatus
CN102714537B (en) Communication method in a mobile communication system using MTC equipment, and device for same
CN102333293A (en) Small data transmission method and equipment
JP5813249B2 (en) Attach methods and mobility management entity over tea to the E-utra
CN104718788A (en) Method for processing paging and method for relaying downlink data
US10219143B2 (en) Data transmission method, mobility management entity, and mobile terminal
RU2414081C2 (en) Method of transmitting signals in mobile communication system

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201080025277.X

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10858540

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10858540

Country of ref document: EP

Kind code of ref document: A1