WO2011134504A1 - Commande de connexion dans un scénario de redémarrage/reprise - Google Patents

Commande de connexion dans un scénario de redémarrage/reprise Download PDF

Info

Publication number
WO2011134504A1
WO2011134504A1 PCT/EP2010/055698 EP2010055698W WO2011134504A1 WO 2011134504 A1 WO2011134504 A1 WO 2011134504A1 EP 2010055698 W EP2010055698 W EP 2010055698W WO 2011134504 A1 WO2011134504 A1 WO 2011134504A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
gateway network
message
restart
gateway
Prior art date
Application number
PCT/EP2010/055698
Other languages
English (en)
Inventor
Giorgi Gulbani
Original Assignee
Nokia Siemens Networks Oy
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 Nokia Siemens Networks Oy filed Critical Nokia Siemens Networks Oy
Priority to PCT/EP2010/055698 priority Critical patent/WO2011134504A1/fr
Publication of WO2011134504A1 publication Critical patent/WO2011134504A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/32—Release of transport tunnels

Definitions

  • the present invention relates to an apparatus, method and computer program product related to a control of
  • the present invention is related to a mechanism for identifying and deleting hanging
  • connections such as packet data network connections, wherein one example of the proposed mechanism is in particular applicable to identify and delete hanging connections at an MME or S4-SGSN in case a remote gateway element, in particular a PGW has been restarted.
  • EUTRAN evolved universal terrestrial radio access network
  • GERAN - GSM Global System for Mobile Communications
  • EDGE enhanced data rates for GSM evolution
  • PLMN public land mobile network
  • ISDN Integrated Services Digital Network
  • wireless communication networks such as the cdma2000 (code division multiple access) system
  • cdma2000 (code division multiple access) system e.g., cdma2000 (code division multiple access) system
  • 3G 3rd generation
  • UMTS Telecommunications System
  • 2G 2nd generation
  • GSM Global System for Mobile communications
  • GSM General Packet Radio System
  • EDGE Wireless Local Area Network
  • WLAN Wireless Local Area Network
  • WiMAX Microwave Access
  • 3GPP 3 rd Generation Partnership Project
  • Telecoms & Internet converged Services & Protocols for Advanced Networks
  • TISPAN International Telecommunication Union
  • ITU International Telecommunication Union
  • 3GPP2 3 rd Generation Partnership Project 2
  • WiMAX Forum the WiMAX Forum and the like are working on standards for telecommunication network and access environments.
  • network elements such as a user equipment and another communication equipment, such as a database, a server, etc.
  • intermediate network elements such as network control elements, support nodes, service nodes and interworking elements are involved which may belong to different communication networks.
  • Data stored in location registers are automatically updated in normal operation; the main information stored in a location register defines the location of each mobile station or UE and the subscriber data required to handle traffic for each mobile subscriber.
  • the main information stored in a location register defines the location of each mobile station or UE and the subscriber data required to handle traffic for each mobile subscriber.
  • the subscriber data required to handle traffic for each mobile subscriber.
  • One possibility for handling such a situation is for example to send an information from the restarted network element to network elements connected thereto, such as an own Recovery or Restart (referred to hereinafter as an own Recovery or Restart (referred to hereinafter as an own Recovery or Restart (referred to hereinafter as an own Recovery or Restart (referred to hereinafter as an own Recovery or Restart (referred to hereinafter as an own Recovery or Restart (referred to hereinafter as an own Recovery or Restart (referred to hereinafter as
  • restart/recovery Counter IE to a corresponding peer, for example via a GTPvl-C signaling path.
  • a network element receiving this IE for example a GGSN receiving a SGSN's restart counter, will delete corresponding contexts. In case any hanging contexts are still left over at a network element, for example if a receipt of a SGSN's new restart counter failed to reach GGSN, then the network element (here the GGSN) can still delete them, for example if a respective inactivity timer expires.
  • the current mechanism used in the legacy networks may not work in other networks.
  • GTPv2 entities involved in Bearer Context management, i.e. MME/S4-SGSN (depending via which access a connection to an UE is established) , an SGW and a PGW.
  • MME/S4-SGSN depending via which access a connection to an UE is established
  • SGW Serving Mobility Management Entity
  • PGW Packet Control Function
  • the SGW can communicate an own restart (i.e. send a restart/recovery IE related to the SGW) , but it is not possible for the SGW to communicate the restart of the PGW to the MME/S4-SGSN.
  • the reason for this is that the SGW sends only own
  • the MME/S4-SGSN is typically connected to multiple PGWs via the same SGW.
  • the MME/S4-SGSN is not able to identify correct PGWs if it receives a PGW restart/recovery counter from the SGW.
  • an object of the invention to provide an apparatus, method and computer program product by means of which an improved mechanism for controlling connections of a communication network in a restart scenario is provided.
  • an improved mechanism which allows a deletion of hanging connections or contexts, which is caused e.g. by a restart of a network element in the communication path which is not (directly) connected to network element such as a
  • a method comprising receiving a first message from a first gateway network element, the first message comprising an initial restart/recovery information element related to a second gateway network element, generating a connection related data set on the basis of information contained in the first message from the first gateway network element, receiving a second message from the first gateway network element, the second message comprising an incremented restart/recovery
  • an apparatus comprising a first receiver configured to receive a first message from a first gateway network element, the first message comprising an initial restart/recovery information element related to a second gateway network element, a first processor portion configured to generate a connection related data set on the basis of information contained in the first message from the first gateway network element, a second receiver configured to receive a second message from the first gateway network element, the second message comprising an incremented restart/recovery information element related to the second gateway network element, a second processor portion configured to process the second message for determining connections linked to second gateway network element on the basis of information
  • a third processor portion configured to delete context data of connections determined to be linked to the second gateway network element .
  • the initial restart/recovery information element and the incremented restart/recovery information element may be a respective counter value indicating a restart state of the second gateway network element
  • the first message may be a response message in a
  • connection or session establishment procedure and the second message may be a control plane message according to a tunnel control and management protocol;
  • connection related data set generated on the basis of information contained in the first message from the first gateway network element may comprise at least one of the following parameters: an identification element of the first gateway network element, an identification element of the second gateway network element, an address information of the first gateway network element, an address
  • the processing of the second message for determining connections linked to second gateway network element may comprise determining the presence of the incremented restart/recovery information element related to the second gateway network element on the basis of a comparison with the initial restart/recovery information element related to the second gateway network element contained in the
  • connection related data set and identifying the second gateway network element by matching at least one of the address information of the first gateway network element, the tunnel endpoint identifier of the first gateway network element, and the bearer identifier information contained in the connection related data set with corresponding
  • determined to be linked to the second gateway network element may comprise a deletion of context data having the corresponding identification element of the second gateway network element
  • the processing as defined above may be executed in a communication control network element, in particular at least one of a serving general packet radio service support node and a mobility management entity, wherein the first gateway network element may be a serving gateway network element, and the second gateway network element may be a packet data network gateway network element.
  • an apparatus comprising a receiver configured to receive an initial restart/recovery information element related to a second gateway network element, a transmitter configured to send a first message to a communication control network element, the first message comprising the initial
  • restart/recovery information element related to the second gateway network element wherein the receiver is further configured to receive an incremented initial
  • restart/recovery information element from the second gateway network element
  • the transmitter is further configured to send a second message to the communication control network element, the second message comprising the incremented restart/recovery information element received from the second gateway network element.
  • the initial restart/recovery information element and the incremented restart/recovery information element may be a respective counter value indicating a restart state of the second gateway network element
  • the first message may be a response message in a
  • connection or session establishment procedure and the second message may be a control plane message according to a tunnel control and management protocol;
  • the processing may be executed in a serving gateway network element, wherein the second gateway network element may be a packet data network gateway and the communication control network element may be at least one of a serving general packet radio service support node and a mobility management entity.
  • a computer program product for a computer comprising software code portions for performing the steps of the above defined methods, when said product is run on the computer.
  • the computer program product may comprise a computer-readable medium on which said software code portions are stored.
  • the computer program product may be directly loadable into the internal memory of the computer and/or transmittable via a network by means of at least one of upload, download and push procedures.
  • a network element such as an SGW
  • another network element such as an MME or S4-SGSN
  • a further network element such as a PGW
  • a communication control network element such as a MME or SGSN
  • a bearer or PDP context for example, established for a UE or the like is not usable anymore and is thus to be deleted, by determining which other network element (e.g. the PGW) has conducted a restart or the like.
  • the MME/S4-SGSN is able to correctly identify PGWs being restarted when it receives a corresponding PGW restart/recovery counter from the SGW. Therefore, by cleaning hanging contexts at MME/S4-SGSN, network and memory resources are released.
  • the proposed solution provides backward compatibility to already existing communication standards since the restart/recovery information element included in the signaling to the communication control network element can be made an optional parameter.
  • a receiving network element is not able to understand the IE, for example in case a SGSN of a previous release stage is involved in the communication path, it is possible to ignore the IE and to continue default processing.
  • a network element whose restart is to be considered in the processing can change an own address, such as an S5/S8 IP address.
  • an own address such as an S5/S8 IP address.
  • network elements involved in the initial communication establishment may change (e.g. the MME/S4- SGSN may change, but SGW is maintained) while the correct identification of the restarted network element (e.g. the PGW) can still be performed.
  • Fig. 1 shows a diagram illustrating an example of a
  • Fig. 2 shows a flow chart illustrating a procedure for identifying connections to be deleted so as to control communication connections according to an example of an embodiment of the invention.
  • Fig. 3 shows a flow chart illustrating a procedure for providing information used for identifying connections to be deleted so as to control communication connections according to an example of an embodiment of the invention.
  • Fig. 4 shows a diagram illustrating a configuration of a communication control network element executing a control for identifying connections to be deleted according to an example of an embodiment of the invention.
  • Fig. 5 shows a diagram illustrating a configuration of a gateway network element executing a control for providing information used for identifying connections to be deleted according to an example of an embodiment of the invention.
  • a communication system which may be based on a 3GPP LTE system where a UE is able to establish a connection, such as a PDN connection, via different access networks, such as
  • 3GPP EUTRAN access networks and 3GPP GERAN or UTRAN access networks.
  • the present invention is not limited to an application in such a system or environment but is also applicable in other
  • a basic system architecture of a communication network may comprise a commonly known architecture comprising a wired or wireless access network subsystem and a core network, such as an EPC.
  • Such an architecture comprises one or more access network control units, radio access network
  • transceiver stations with which a UE is capable to
  • gateway network elements such as gateway network elements, HSS network elements, policy and charging control network elements and the like are usually comprised.
  • HSS network elements HSS network elements
  • policy and charging control network elements are usually comprised.
  • signaling links used for a communication connection or a call between user terminals and/or servers than those described in detail herein below.
  • the network elements such as gateway elements like a PGW, a SGW etc., network control elements like an MME, an S4-SGSN etc., a UE and the like, and their
  • correspondingly used devices and network element comprise several means and components (not shown) which are required for control, processing and
  • Such means may comprise, for example, a processor unit for executing instructions, programs and for processing data, memory means for storing instructions, programs and data, for serving as a work area of the processor and the like (e.g. ROM, RAM, EEPROM, and the like) , input means for inputting data and instructions by software (e.g. floppy diskette, CD-ROM, EEPROM, and the like) , user interface means for providing monitor and manipulation possibilities to a user (e.g. a screen, a keyboard and the like), interface means for establishing links and/or connections under the control of the processor unit (e.g. wired and wireless interface means, an antenna, etc.) and the like.
  • a processor unit for executing instructions, programs and for processing data
  • memory means for storing instructions, programs and data, for serving as a work area of the processor and the like
  • input means for inputting data and instructions by software (e.g. floppy diskette, CD-ROM, EEPROM, and the like)
  • user interface means for providing
  • a simplified architecture of an exemplary communication network is shown in which the control of connections according to examples of embodiments of the invention may be implemented.
  • the communication network shown in Fig. 1 is based on a 3GPP EPS wherein access for a subscriber, i.e. the UE 10, is possible via different access networks.
  • the UE 10 may attach to the network for establishing a connection to a destination, such as IP services (not shown) provided by the operator, via at least one of EUTRAN 21 wherein in this case a MME 31 represents a communication control network element to be considered in examples of embodiments of the invention, and GERAN/UTRAN 22 wherein in this case an SGSN, such as an S4-SGSN
  • FIG. 1 represents a communication control network element to be considered in examples of embodiments of the invention. It is to be noted that the network architecture shown in Fig. 1 depicts only those network elements which are useful for understanding the principles of the examples of
  • the communication network comprises a plurality of access networks.
  • a first one is a 3GPP based EUTRAN access network 21 with the MME 31 representing a control node for the 3GPP (LTE) access network, a 2G/3G access network (GERAN/UTRAN) 22 with an SGSN as being a control element thereof,
  • LTE 3GPP
  • GERAN/UTRAN 2G/3G access network
  • the MME 31 as an example of a
  • communication control network element is a network element or node that is serving the UE 10 when attached to EUTRAN
  • the MME 31 stores information regarding e.g. mobility management, routing and security.
  • the MME 31 is configured to support control plane signaling from the EUTRAN and also performs security and authentication mechanisms for the subscriber.
  • a communication with an eNodeB (not shown) or the like of the EUTRAN for the control plane is achieved for example with Sl-MME
  • the MME 31 also supports the interfaces, such as an S3 interface, which enables user and bearer information exchange for inter 3GPP access network mobility. This interfaces may utilize GTPv2-C, for example. Furthermore, the MME 31 supports an Sll interface which provides related control and mobility support between the EUTRAN and a 3GPP anchor function of an SGW 40
  • the S4-SGSN 32 another example of a communication control network element is a network element or node that is serving the UE (also referred to as mobile station) attached to the GERA /U RAN 22.
  • the SGSN 32 stores information regarding e.g. mobility management, routing and security. Specifically, the S4-SGSN 32 delivers data packets to/from the UE 10 within its geographical service area and is responsible for packet routing, mobility management, subscriber authentication, charging functions, and storage of subscription information and location information.
  • the S4-SGSN 32 communicates with base stations of the UTRAN/GERAN 22 via a Iu-PS interface. For retrieving authentication information, storage of subscription
  • the S4-SGSN 32 communicates also with the HSS.
  • the S4-SGSN 32 is enhanced to support an S4 interface to the SGW 40, which provides related control and mobility support between GPRS Core and the 3GPP Anchor function of the SGW 40.
  • the control plane specifies a tunnel control and management protocol (i.e. GTPv2-C) , allowing access to a packet data network for the UE.
  • GTPv2-C tunnel control and management protocol
  • Reference sign 40 denotes an SGW as a first gateway network element.
  • the SGW 40 is connected to the MME 31 via the Sll interface, for example, and to the S4-SGSN 32 via the S4 interface, for example.
  • the SGW 40 provides mobility anchoring for inter-3GPP mobility, and relays the traffic between 2G/3G system and a PGW 50 (described later) via an S5 interface.
  • the SGW 40 provides also packet routeing and forwarding between the PGW 50 and 3GPP access network.
  • Reference sign 50 denotes the PGW as a second gateway network element.
  • the PGW 50 provides connectivity from the UE 10 to external PDNs by being the point of exit and entry of traffic for the UE 10.
  • the PGW 50 performs policy enforcement, packet filtering for each user, charging support, lawful Interception and packet screening.
  • Another key role of the PGW 50 is to act as the anchor for mobility between 3GPP and non-3GPP technologies.
  • S5 provides user plane tunneling and tunnel management between the SGW 40 and the PGW 50.
  • Fig. 2 shows a procedure for controlling connections in a restart/recovery scenario which is
  • a downstream side network element i.e. a network element where another network element is
  • a network node being restarted such as a communication control network element like the MME 31 or the SGSN 32 shown in Fig. 1
  • Fig. 3 shows a procedure for controlling connections in a restart/recovery scenario which is executed in a network element, such as a first gateway network element like the SGW 40 as shown in Fig. 1, being directly connected to a restarting network element, such as a second gateway network element like the PGW 50 as shown in Fig. 1.
  • arrows indicated with reference signs A and B in Figs. 2 and 3 which show where an action of the first gateway network element influences the processing of the
  • step S100 procedures for
  • connection or session for the UE 10 are conducted which may correspond to the standard procedures and are thus not described in greater detail as they are commonly known to those skilled in the art.
  • the establishment of a connection or session may comprise procedures for an Initial Attach, an UE Requested PDN
  • the communication control network element e.g. the MME 31 or the S4-SGSN 32 receives in step S110 from a first gateway network element such as the SGW 40
  • This message is for example the first response message sent by the SGW 40, e.g. the first Create Session Response message or the first Create PDP Context Response message.
  • this first message comprises a specific information element
  • the restart/recovery IE may be an optional feature for the system processing. In other words, in case the SGW 40 is not configured to send a corresponding IE with the first response message, the operation of the communication control network element is not affected, i.e. a processing without the provision of this IE is also possible. On the other hand, in case the receiving
  • the communication control network element is not able to detect or understand the a PGW's restart/recovery IE included in the message from the SGW 40, the parameter is ignored while the SGW is not forced to omit the IE from a message.
  • the PGW's restart/recovery IE represents for example an optional GTPv2 feature or the like (depending on which control plane communication type is used in a
  • the second gateway network element is not directly connected to the communication control network element and may thus not usually sent by itself a restart/recovery IE to the communication control network element.
  • the communication control network element
  • the communication control network element creates e.g. a bearer/PDP context wherein the received initial PGW's restart/recovery IE is stored therein.
  • the connection related data set comprises, besides the PGW's restart/recovery IE the following information:
  • the MME/S4-SGSN is configured to populate for example the default Bearer/PDP Context with the following parameters :
  • the PGW's restart/recovery IE is received from the SGW 40 and to be used for the Bearer/PDP Context data, there is created the following association in the default Bearer/PDP Context:
  • step S130 the communication control network element
  • MME/S4-SGSN receives a control plane message from the first gateway network element (i.e. a second message) which identifies the PGW 50 (indicated by "B" related to Fig. 3 which is described below) .
  • This control plane message is, for example, the first GTPv2 message belonging to a given
  • an incremented PGW's restart/recovery counter value is sent to the SGW 40 which in turn forwards the incremented PGW's
  • restart/recovery counter to the communication control network element as a further PGW's restart/recovery IE (to be described later) .
  • the restart/recovery IE may be an optional feature for the system processing.
  • the SGW 40 is not configured to send a corresponding IE with the first control plane message
  • the operation of the communication control network element is not affected, i.e. a processing without the provision of this IE is also possible.
  • the receiving communication control network element is not able to detect or understand the a PGW's restart/recovery IE included in the message from the SGW 40, the parameter is ignored while the SGW is not forced to omit the IE from a message.
  • the PGW's restart/recovery IE represents an optional GTPv2 feature or the like (depending on which control plane communication type is used in a communication system) .
  • connections linked to the second gateway network element are determined on the basis of information contained in the control plane message and information contained in the connection related data set.
  • the communication control network element MME/S4-SGSN
  • identifies step S150) if the PGW 50 has been restarted on the basis of the incremented restart/recovery counter value (retrieved from the corresponding IE) and determines the the PGW's FQDN by means of the identities of the SGW 40 (SGW's IP address and TEID-C) .
  • SGW's IP address and TEID-C the identities of the SGW 40
  • bearer's EBI may be used for the determination and identification.
  • a corresponding processing may comprise a determination that an incremented PGW's restart/recovery IE is present. This may be done, for example, by comparing the counter value indicated in the IE with the initial PGW's restart/recovery information element in the connection related data set. By matching e.g. the corresponding SGW's IP address for CP and the SGW's TEID-C and/or the default bearer's EBI, it is possible to determine the corresponding PGW's FQDN related to the incremented PGW's restart/recovery counter.
  • control plane message e.g. the
  • GTPv2 message received from the SGW may have a UE
  • SGW's CP IP address and SGW's TEID-C identify the UE, and therefore UE ' s all PDN connection to different PGWs .
  • PGW's restart/recovery counter which has default bearer's EBI pointing to the given PGW.
  • another part of the control plane message e.g. the GTPv2 message received from the SGW have PDN connection
  • SGW s CP IP address and SGW s TEID-C identify a specific PDN connection to a specific PGW.
  • MME/S4-SGSN performs a processing where the received PGW s restart/recovery counter is matched with the PGW s FQDN .
  • the communication control network element After identifying the PGW 50 as being restarted, the communication control network element conducts in step S160 a deletion of context data, i.e. all bearer/PDP contexts linked to the PGW in question, i.e. which have the same PGW s FQDN (in other words, the determined PGW s FQDN identifies all bearers or contexts in question) .
  • context data i.e. all bearer/PDP contexts linked to the PGW in question, i.e. which have the same PGW s FQDN (in other words, the determined PGW s FQDN identifies all bearers or contexts in question) .
  • step S200 procedures for establishing a connection or session for the UE 10 are conducted which may correspond to the standard procedures and are thus not described in greater detail as they are commonly known to those skilled in the art.
  • the establishment of a connection or session may comprise procedures for an Initial Attach, an
  • the first gateway network element e.g. the SGW 40, receives in step S210 an initial (PGWs)
  • restart/recovery counter is introduced and forwarded as an IE (i.e. the PGWs restart/recovery IE) in a message (step S220) to the communication control network element, e.g. the MME 31 or the S4-SGSN 32, which message is related to the establishment of the session or connection (indicated by "A" related to Fig. 2 which is described above) .
  • the message is for example the first response message sent by the SGW 40, e.g. the first Create Session Response message or the first Create PDP Context Response message.
  • step S230 the SGW 40 receives from the PGW 50 an indication that the PGW 50 has restarted. This information is transmitted in the form of an incremented PGW's
  • the SGW 40 conducts an own
  • the SGW 40 uses in step S240 the first control plane message to the communication control network element (indicated by "B" related to Fig. 2 which is described above) .
  • the control plane message is, for example, the first GTPv2 message belonging to a given PDN connection, which is sent across S4/S11 interface from the SGW 40 after being informed by the PGW 50 across the S5 interface about a restart of the PGW 50, and identifies the PGW 50.
  • the network element 30 configured to execute, for example, a procedure according to Fig. 2 may comprise a processing function or processor 310, such as a CPU or the like, which executes instructions given by programs or the like related to the power control.
  • the processor 310 may comprise further portions dedicated to specific processings
  • Portions for executing such specific processings may be also provided as discrete elements or within one or more further processors, for example.
  • Reference sign 320 denotes a transceiver or input/output (I/O) unit connected to the processor 310 (or corresponding other elements comprising the functions of the further portions) .
  • the I/O unit 320 may be used for communicating with network elements of the communication network, in particular the SGW via respective interfaces or reference points (S4/S11) .
  • Reference sign 330 denotes a memory usable, for example, for storing data and programs to be executed by the processor 310 and/or as a working storage of the processor 310 (for example for storing the
  • the processor 310 is configured to execute processings related to the control of connections in a restart/recovery scenario described in examples of embodiments of the invention.
  • the processor 310 comprises a receiver portion 311 which receives the first message (e.g. Create Session Response message or the like) from the SGW
  • Reference sign 312 denotes a portion used for creating and storing the connection related data set as described above in
  • Reference sign 313 denotes a further receiver portion which receives the second message (e.g. the first GTPv2 message) from the SGW 40, wherein the receiver portion 313 may be configured to detect the second message (e.g. the first GTPv2 message) from the SGW 40, wherein the receiver portion 313 may be configured to detect the second message (e.g. the first GTPv2 message) from the SGW 40, wherein the receiver portion 313 may be configured to detect the second message (e.g. the first GTPv2 message) from the SGW 40, wherein the receiver portion 313 may be configured to detect the second message (e.g. the first GTPv2 message) from the SGW 40, wherein the receiver portion 313 may be configured to detect the second message (e.g. the first GTPv2 message) from the SGW 40, wherein the receiver portion 313 may be configured to detect the second message (e.g. the first GTPv2 message) from the SGW 40, wherein the receiver portion 313 may be configured to detect the
  • FIG. 5 a block circuit diagram of a first gateway network element 40, such as the SGW 40, is shown which is configured to implement the control mechanism described in connection with Fig. 3. It is to be noted that the first gateway network element 40 shown in Fig. 5 may comprise several further elements or functions besides those
  • the first gateway network element 40 configured to execute, for example, a procedure according to Fig. 3 may comprise a processing function or processor 410, such as a CPU or the like, which executes instructions given by programs or the like related to the power control.
  • the processor 410 may comprise further portions dedicated to specific processings described below. Portions for executing such specific processings may be also provided as discrete elements or within one or more further processors, for example.
  • Reference signs 420 and 430 denote transceiver or
  • I/O input/output
  • the I/O unit 420 may be used for communicating with network elements of the communication network, in particular the PGW via respective interfaces or reference points (S5)
  • the I/O unit 430 may be used for communicating with network elements of the
  • the I/O units 420 and 430 may be a combined unit comprising the communication equipment towards all network elements in question, or may comprise a distributed structure with a plurality of different interfaces.
  • Reference sign 440 denotes a memory usable, for example, for storing data and programs to be executed by the processor 410 and/or as a working storage of the processor 410.
  • the processor 410 is configured to execute processings related to the control of connections in a restart/recovery scenario described in examples of embodiments of the invention.
  • the processor 410 may comprise a receiver portion (411) which receives the initial PGW's restart/recovery counter from the PGW 50.
  • Reference sign 412 denotes a processing portion which forwards the initial PGW's restart/recovery counter to the communication control network element in the first message (e.g. Create Session Response message or the like) .
  • Reference sign 413 denotes a receiver which receives the incremented PGW's
  • Reference sign 414 denotes a processing portion which forwards the incremented PGW's restart/recovery counter to the communication control network element in the second message (e.g. the first GTPv2 message) after the receipt of the information regarding the restart of the PGW 50.
  • the MME 31 deletes all MM Bearer contexts affected by the restart that it may have stored. During or immediately after the MME 31 restarts, the MME 31 places a local MME restart counter value in the first GTPv2 message it sends to the SGW 40 (for example, either into Echo Request/Response, or into Create Session Request) .
  • the MME 31 receives from the SGW 40 the SGW restart counter in a GTPv2 message (for example, either echo
  • the MME 31 may per default delete all PDN connection table data/MM bearer contexts associated with the peer node that fails as well as freeing any internal MME resources associated with those PDN connections.
  • the MME 31 may optionally perform other implementation specific actions such as to clear external resources (e.g. Sl-MME messages to clear RNC resources) or more advanced forms of restoration. It is to be noted that the MME 31 will have the identity of the SGW currently in use for a PDN connection available in the MME's PDN
  • connection table as part of existing EPC procedures as well as other peer state data.
  • the SGW 40 deletes all MM Bearer contexts affected by the restart that it may have stored. During or immediately after an SGW Restart the SGW may
  • the SGW 40 requests/responses the SGW 40 sends to PGW 50.
  • the SGW 40 receives from the MME 31 an MME restart counter in a GTPv2 message (for example, either Echo request/ response, or Create Session Request) .
  • the SGW 40 will receive from PGW 50 the PGW restart counter in a GTPv2 message (for example, either Echo request/ response or in
  • the SGW 40 When the SGW 40 detects that a peer MME or peer PGW has restarted, it deletes all PDN connection table data/MM bearer contexts associated with the peer node that fails as well as freeing any internal SGW resources associated with those PDN connections. The SGW 40 does not try to directly clear resources in the MME 31 or the PGW 50. The SGW 40 may optionally perform other implementation specific actions such as messages to clear other external resources (e.g.
  • the SGW 40 has the identity of the MME 31 and PGW 50 currently in use for a PDN connection available in the SGW' s PDN connection table as part of existing EPC procedure.
  • the PGW 50 deletes all MM bearer contexts affected by the restart that it may have stored.
  • the PGW 50 places the PGW restart counter value in the first GTPv2 message (e.g. echo requests/response) or in the ⁇ heartbeat requests/responses the PGW 50 sends to the SGW 40.
  • the PGW restart counter value in the first GTPv2 message (e.g. echo requests/response) or in the ⁇ heartbeat requests/responses the PGW 50 sends to the SGW 40.
  • the PGW 50 receives from SGW 40 the SGW restart counter in a GTPv2 message (e.g. echo requests/response) or in ⁇ heartbeat requests/responses.
  • a GTPv2 message e.g. echo requests/response
  • ⁇ heartbeat requests/responses e.g. ⁇ heartbeat requests/responses.
  • the PGW 50 detects that a peer SGW has restarted it deletes all PDN connection table data/MM bearer contexts associated with the peer node that fails as well as freeing any internal PGW resources associated with those PDN connections.
  • the PGW 50 does not try to directly clear resources in the SGW 40.
  • the PGW may optionally perform other implementation specific actions such as messages to clear other external resources (e.g. PCC messages) .
  • the PGW 50 has the identity of the SGW currently in use for a PDN connection available in the PGW' s PDN connection table as part of existing EPC procedure.
  • elements of a restart procedure in a remote peer are described. That is, in this section, procedures executed, for example, with regard to the MME/S4-SGSN are described in case a restart of a network node not directly connected to it, such as the PGW 50, are described.
  • a detection and handling of remote peer's restart is an optional feature, which significantly reduces the signaling load when either an MME/S4-SGSN, or a PGW restarts.
  • the feature may be utilized even if only one part of MME, S4-SGSN, SGW and PGW network elements support it within a PLMN. If an MME/S4-SGSN/SGW/PGW does not support this optional feature, the hanging contexts may be
  • an MME/S4-SGSN that does not support the feature may silently ignore the received PGW restart counter, and a non-supporting SGW will not forward the IE to the MME.
  • the MME/S4-SGSN compares PGW restart counter values before and after the PGW
  • the SGW 40 forwards the PGW restart counter to the MME 31.
  • the first case is that ISR is inactive and the second case is that ISR is
  • the SGW 40 forwards the initial PGW restart counter to the MME 31 during the first PDN connection establishment between the SGW 40 and the PGW 50. That is, the SGW 40 may forward the optional PGW restart counter to the MME 31 with the first Create Session
  • the SGW 40 detects a PGW restart, the SGW 40 forwards the PGW restart counter to the MME 31.
  • the SGW 40 may detect the PGW restart either after receiving GTPv2/PMIPv6 echo/heartbeat message, or after receiving any of the tunnel management messages:
  • the SGW 40 may forward an optional PGW restart counter IE to the MME 31 with the same message ;
  • the SGW 40 may send an optional PGW restart counter to the MME 31 for example with a Delete Bearer Request message.
  • the MME 31 receives PGW restart counter, it detects and handles the PGW restart accordingly. Furthermore, the MME 31 identifies the PGW 50 as follows:
  • SGW's F-TEID uniquely identifies the PGW 50; if the received GTPv2 message has a UE granularity, then in addition to the SGW's F-TEID, the default bearer's EBI uniquely identifies the PGW 50.
  • SGW 40 sends a Delete bearer request message to both the MME 31 and the S4-SGSN 32. Therefore, if ISR is activated, the SGW 40 sends corresponding
  • an apparatus comprising a first receiving means configured to receive a first message from a first gateway network element, the first message comprising an initial restart/recovery information element related to a second gateway network element, a first processing means configured to generate a connection related data set on the basis of information contained in the first message from the first gateway network element, a second receiving means configured to receive a second message from the first gateway network element, the second message comprising an incremented restart/recovery
  • a second processing means configured to process the second message for determining connections linked to second gateway network element on the basis of information contained in the second message and information contained in the connection related data set, and a third processing means configured to delete context data of connections determined to be linked to the second gateway network element .
  • an apparatus comprising receiving means configured to receive an initial restart/recovery information element related to a second gateway network element, transmitting means configured to send a first message to a communication control network element, the first message comprising the initial
  • restart/recovery information element related to the second gateway network element wherein the receiving means is further configured to receive an incremented initial restart/recovery information element from the second gateway network element, and the transmitting means is further configured to send a second message to the
  • the second message comprising the incremented restart/recovery information element received from the second gateway network element.
  • an access technology via which signaling is transferred to and from a network element or node like a UE may be any technology by means of which a node can access an access network (e.g. via a base station or generally an access node) .
  • WiMAX Worldwide Interoperability for Mobile communications
  • Infrared and the like may be used; although the above technologies are mostly wireless access technologies, e.g. in different radio spectra, access technology in the sense of the present invention implies also wirebound
  • IP based access technologies like cable networks or fixed lines but also circuit switched access technologies; access technologies may be distinguishable in at least two categories or access domains such as packet switched and circuit switched, but the existence of more than two access domains does not impede the invention being applied thereto,
  • - usable access networks may be any device, apparatus, unit or means by which a station, entity or other user equipment may connect to and/or utilize services offered by the access network; such services include, among others, data and/or (audio-) visual communication, data download etc . ;
  • a UE may be any device, apparatus, unit or means by which a system user or subscriber may experience services from an access network, such as a mobile phone, personal digital assistant PDA, or computer;
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the invention in terms of the functionality implemented;
  • CMOS complementary metal-oxide-semiconductor
  • ECL emitter Coupled Logic
  • TTL Transistor- Transistor Logic
  • any method steps and/or devices, units or means likely to be implemented as software components may for example be based on any security architecture capable e.g. of
  • devices, apparatuses, units or means can be implemented as individual devices, apparatuses, units or means, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device, apparatus, unit or means is preserved,
  • an apparatus may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of an apparatus or module, instead of being hardware implemented, be implemented as software in a
  • (software) module such as a computer program or a computer program product comprising executable software code
  • a device may be regarded as an apparatus or as an
  • an SGW sends a new, optional IE, which is called PGW's restart/recovery IE, to an MME/S4-
  • the MME/S4-SGSN which indicates an initial restart/recovery counter of a PGW.
  • the MME/S4-SGSN stores this IE in a newly created bearer/PDP context along with identification information for the SGW, tunnel endpoint identification information of the SGW, identification information of a PGW, and a default bearer's identification. If the PGW restarts, it sends an own incremented restart/recovery counter to the SGW which forwards this information to the MME/S4-SGSN with a first GTPv2 message. After receipt of this information, the
  • MME/S4-SGSN identifies the identity of the PGW by
  • the MME/S4-SGSN deletes all bearer/PDP contexts linked to the PGW in question .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention porte sur un mécanisme permettant de commander des connexions dans un scénario de redémarrage/reprise au moyen duquel il est possible d'identifier et de supprimer des connexions ou contextes en attente. Durant une procédure d'établissement de connexion, une SGW envoie un nouvel IE facultatif, qui est appelé IE de redémarrage/reprise de PGW, à une MME/S4-SGSN qui indique un compteur de redémarrage/reprise initial d'une PGW. La MME/S4-SGSN stocke cet IE dans un contexte de support/PDP nouvellement créé conjointement avec des informations d'identification pour la SGW, des informations d'identification de point d'extrémité de tunnel de la SGW, des informations d'identification d'une PGW, et un identifiant d'un support par défaut. Si la PGW redémarre, elle envoie son propre compteur de redémarrage/reprise incrémenté à la SGW qui transmet ces informations à la MME/S4-SGSN avec un premier message GTPv2. Après réception de ces informations, la MME/S4-SGSN identifie l'identité de la PGW par des informations concernant la SGW. Ensuite, la MMES4-SGSN supprime tous les contextes de support/PDP liés à la PGW en question.
PCT/EP2010/055698 2010-04-28 2010-04-28 Commande de connexion dans un scénario de redémarrage/reprise WO2011134504A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2010/055698 WO2011134504A1 (fr) 2010-04-28 2010-04-28 Commande de connexion dans un scénario de redémarrage/reprise

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2010/055698 WO2011134504A1 (fr) 2010-04-28 2010-04-28 Commande de connexion dans un scénario de redémarrage/reprise

Publications (1)

Publication Number Publication Date
WO2011134504A1 true WO2011134504A1 (fr) 2011-11-03

Family

ID=43415300

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2010/055698 WO2011134504A1 (fr) 2010-04-28 2010-04-28 Commande de connexion dans un scénario de redémarrage/reprise

Country Status (1)

Country Link
WO (1) WO2011134504A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015521010A (ja) * 2012-05-25 2015-07-23 クゥアルコム・インコーポレイテッドＱｕａｌｃｏｍｍ Ｉｎｃｏｒｐｏｒａｔｅｄ キャリアアグリゲーションのためのカスコード転換スイッチを有する低雑音増幅器
CN104995956A (zh) * 2013-09-25 2015-10-21 华为技术有限公司 一种数据通道建立的方法、装置及系统
WO2017118397A1 (fr) * 2016-01-06 2017-07-13 夏普株式会社 Procédé et dispositif de gestion de contexte d'ue
US10177722B2 (en) 2016-01-12 2019-01-08 Qualcomm Incorporated Carrier aggregation low-noise amplifier with tunable integrated power splitter
US10666555B2 (en) * 2010-09-15 2020-05-26 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for relocating and restoring connections through a failed serving gateway and traffic offloading

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
"Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Restoration procedures (3GPP TS 23.007 version 9.3.0 Release 9)", TECHNICAL SPECIFICATION, EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE (ETSI), 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS ; FRANCE, vol. 3GPP CT 4, no. V9.3.0, 1 April 2010 (2010-04-01), XP014046401 *
"Universal Mobile Telecommunications System (UMTS); LTE; 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 (3GPP TS 29.274 version 9.2.0 Release 9)", TECHNICAL SPECIFICATION, EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE (ETSI), 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS ; FRANCE, vol. 3GPP CT 4, no. V9.2.0, 1 April 2010 (2010-04-01), XP014046701 *
ERICSSON: "Cleanup of hanging PDN connections/bearers", 3GPP DRAFT; C4-100409_WAS093574_29274_CLEANUP_PGW_HANGING_PDN_CONNECT IONS_REL8, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG4, no. San Francisco, US; 20100222, 2 March 2010 (2010-03-02), XP050411050 *
ERICSSON: "Discussion paper on the handling of hanging PDN connections/bearers Specs: 3GPP TS 23.007, 3GPP TS 29.274", 3GPP DRAFT; C4-093571_DISC_ON_THE_HANDLING_OF_HANGING_PDN_CONNECTIONS _BEARERS_Y, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. Beijing; 20091109, 9 November 2009 (2009-11-09), XP050387199 *
ERICSSON: "Discussion paper on the handling of hanging PDN connections/bearers Specs: 3GPP TS 23.007, 3GPP TS 29.274", 3GPP DRAFT; C4-100405_DISC_ON_THE_HANDLING_OF_HANGING_PDN_CONNECTIONS _BEARERS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG4, no. San Francisco, US; 20100222, 2 March 2010 (2010-03-02), XP050411046 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10666555B2 (en) * 2010-09-15 2020-05-26 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for relocating and restoring connections through a failed serving gateway and traffic offloading
JP2015521010A (ja) * 2012-05-25 2015-07-23 クゥアルコム・インコーポレイテッドＱｕａｌｃｏｍｍ Ｉｎｃｏｒｐｏｒａｔｅｄ キャリアアグリゲーションのためのカスコード転換スイッチを有する低雑音増幅器
CN104995956A (zh) * 2013-09-25 2015-10-21 华为技术有限公司 一种数据通道建立的方法、装置及系统
CN104995956B (zh) * 2013-09-25 2019-06-18 华为技术有限公司 一种数据通道建立的方法、装置及系统
WO2017118397A1 (fr) * 2016-01-06 2017-07-13 夏普株式会社 Procédé et dispositif de gestion de contexte d'ue
US10177722B2 (en) 2016-01-12 2019-01-08 Qualcomm Incorporated Carrier aggregation low-noise amplifier with tunable integrated power splitter

Similar Documents

Publication Publication Date Title
US10652945B2 (en) Mobile terminated call improvements
EP3603127B1 (fr) Système et procédé destinés à permettre un déclenchement de dispositif pour une distribution de données de protocole non internet dans un environnement de réseau
US20160029278A1 (en) Handover of mobility management entity for load balancing
JP6368859B2 (ja) Ｐｄｎ接続再確立方法、リセット中央サーバ、モビリティ管理ネットワーク要素、およびデータゲートウェイ
CN109417702B (zh) 包括片的通信网络中的接入控制
US20120110193A1 (en) Reselection system for bearer binding and event reporting function and method thereof
EP3422752B1 (fr) Procédé et dispositif pour traiter paquets de données
WO2011079634A1 (fr) Procédé de délestage de trafic, entité fonctionnelle de délestage de trafic et système de délestage de trafic
EP2904869B1 (fr) Procédés, dispositifs, et produits-programmes informatiques pour maintenir des dispositifs attachés sans support par défaut
CN107113799B (zh) 一种业务链策略的制定方法及设备
JP2014039341A (ja) トンネル管理方法、トンネル管理装置および通信システム
US20140226606A1 (en) Communication system, communication method, and communication program
CN108235376B (zh) 一种用户面锚点选择方法及装置
CN111869310A (zh) 用于执行小数据快速路径通信的方法和系统
WO2011134504A1 (fr) Commande de connexion dans un scénario de redémarrage/reprise
KR101944647B1 (ko) 데이터 처리 방법, 장치, 단말기, 이동성 관리 엔티티 및 시스템
US20190007862A1 (en) Method and apparatus for transmitting control message in software defined network-based mobile communication system
EP3310117B1 (fr) Procédé d'établissement d'une connexion d'un terminal mobile à un réseau de radiocommunication mobile et composant de réseau d'accès radio
EP3468252B1 (fr) Procédé permettant d'établir un tunnel entre des passerelles locales, et passerelle
JP7207764B2 (ja) サービスデータフロー処理方法および関連デバイス
EP3977812B1 (fr) Procédés, systèmes et supports lisibles par ordinateur pour la détection d'état et la sélection améliorées d'une passerelle de signalisation (sgw) pour des appels d'urgence
WO2010124644A1 (fr) Procédé de mise en oeuvre de services d'urgence, système de mise en oeuvre de services d'urgence et dispositif réseau
CN104796941A (zh) 通过twan接入核心网时的拥塞控制方法及装置
EP3979682B1 (fr) Procédé de mise en oeuvre de continuité de service, appareil et système associés
WO2019028795A1 (fr) Procédé et dispositif de détermination de chemin de service

Legal Events

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

Ref document number: 10715273

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10715273

Country of ref document: EP

Kind code of ref document: A1