WO2009039886A1 - Système de communications et procédé de gestion de communication de données de paquets - Google Patents

Système de communications et procédé de gestion de communication de données de paquets Download PDF

Info

Publication number
WO2009039886A1
WO2009039886A1 PCT/EP2007/060254 EP2007060254W WO2009039886A1 WO 2009039886 A1 WO2009039886 A1 WO 2009039886A1 EP 2007060254 W EP2007060254 W EP 2007060254W WO 2009039886 A1 WO2009039886 A1 WO 2009039886A1
Authority
WO
WIPO (PCT)
Prior art keywords
packet data
node
mobility management
gateway node
data gateway
Prior art date
Application number
PCT/EP2007/060254
Other languages
English (en)
Inventor
Folke AHLSTRÖM
Jan Backman
Lasse Olsson
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/EP2007/060254 priority Critical patent/WO2009039886A1/fr
Publication of WO2009039886A1 publication Critical patent/WO2009039886A1/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/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer

Definitions

  • the present invention relates to handling of downlink packet data addressing an end user station which is in an idle mode, i.e. for which there is no radio bearer active.
  • the invention relates to a communication system handling network initiated radio bearer setup or re-establishment.
  • the invention also relates to a core network mobility management node and a core network packet data gateway node respectively and to methods for network initiated radio bearer setup.
  • Network initiated setup of bearers or re-establishment of bearers is for example discussed in 3GPP TR 23.873 V.4.0.0 7.4.5 where an SGSN controller performs all control functions of an SGSN (Serving GPRS Support Node) and an enhanced GGSN (Gateway GPRS Support Node) , also denoted xGGSN, performs SGSN and GGSN transfer functionality through a direct GTP (GPRS Tunnelling Protocol) tunnel between a radio access network node and the xGGSN, hence bypassing the SGSN.
  • GPRS Tunnelling Protocol GPRS Tunnelling Protocol
  • a notification request is sent from the packet data gateway node to the mobility management node, for example an SGSN.
  • the SGSN initiates a paging request to trigger the service request procedure in the end user station. This means that re- establishment of radio access bearer is requested. It also means that, after a radio access bearer has been setup, the GGSN must be updated before it is able to transfer downlink packet data. Here a tunnel between the radio access network and the GGSN is re-established.
  • the updating procedure produces a high load on the (e.g. S4) interface between the packet data gateway node and the SGSN or the (e.g. SIl) interface between packet data gateway node and an MME (Mobility Management Entity) , which is clearly disadvantageous.
  • Such high signalling loads may in the long run cause overload of the core network interfaces.
  • a procedure as described above is disclosed in the state of the art represented in Fig. 1.
  • the procedure begins with reception of a downlink PDU in xGGSN, I 0 , whereupon a PDU (Protocol Data Unit) notification request message is sent from the packet data gateway node to the mobility management node, 2 0 , and a response message to the packet data gateway node actually only providing information that the notification request message has been received, 2 0 .
  • PDU Protocol Data Unit
  • This initiates the radio access bearer setup procedure and after the messages shown in steps 3o, 4 0 , 5o, 6o follows an update PDP context procedure, messages 7 0 , 7 0 .
  • an object of the present invention to provide a solution to the above mentioned problems for different types of networks and nodes, particularly for an SAE/GW (Systems Architecture Evolution/Gateway) node, and to enable re-establishment of radio bearers, without introducing a state machine as referred to above, and through which it becomes possible to, in a straightforward manner, handle downlink payload packets received after a re-establishment procedure has been initiated, but not terminated. It is also a particular object to provide a system in which the mobility management node only supports or only has to support control signalling but no user plane, payload, packets, e.g. to obviate a requirement that user plane handling be supported in a mobility management node.
  • SAE/GW Systems Architecture Evolution/Gateway
  • a communication system supporting communication of packet data which comprises a core network with a number of packet data gateway nodes and mobility management nodes.
  • the packet data gateway node is adapted to initiate a radio bearer setup or re-establishment procedure at reception of packet data addressing an end user station in idle mode, or when there is no active radio bearer to said user station, by sending a packet data notification request message to the mobility management node.
  • gateway node protocol handling means for communication with the mobility management node.
  • the mobility management node comprises second protocol handling means for packet data gateway node communication which are adapted to generate a response message to a received packet data notification request message, which response message not only contains an information element indicating if the request is acceptable or accepted, but also supplementary information elements which at least comprise identification information relevant for radio bearer re- establishment, or for user plane, packet data, communication and control plane, or signalling, communication with the radio network node handling the addressed end user station.
  • second protocol handling means for packet data gateway node communication which are adapted to generate a response message to a received packet data notification request message, which response message not only contains an information element indicating if the request is acceptable or accepted, but also supplementary information elements which at least comprise identification information relevant for radio bearer re- establishment, or for user plane, packet data, communication and control plane, or signalling, communication with the radio network node handling the addressed end user station.
  • the mobility management node is further adapted to send said notification response message to a packet data gateway node when a radio bearer actually has been setup or re-established and the packet data gateway node is adapted to decode the received notification response message, and then to, substantially directly, forward downlink packet data towards the end user station, (the packet having initiated the procedure and eventually in the meantime received packets which are to use the same radio resources).
  • the core network of course comprises a plurality of packet data gateway node s and mobility management nodes in a conventional manner; reference to but one of each category is made since that is what is needed to explain the inventive concept.
  • the second protocol handling means can also be said to be extended (with respect to known protocol handling means, wherein the extension consists in the generation of the notification response message as discussed above) .
  • the present invention also provides a mobility management node (of a core network) which supports communication with a radio network node and a packet data gateway node. It comprises control plane handling means adapted to, at reception of a notification request message from the (or a) packet data gateway node concerning radio bearer resources for packet data addressing a mobile end user station in an idle mode, i.e.
  • information relevant to the request comprising an information element indicating if the request is accepted or not and supplementary information elements comprising at least identification information relevant for radio resource re-establishment or user plane, and control plane, signalling, communication with a radio network node to or over which the mobile user station is connected and to provide said information in a notification response message, also denoted an extended notification response message. It is further adapted to send said notification response message to the packet data gateway node .
  • the present invention provides a packet data gateway node with gateway node protocol handling means for communication with a core network mobility management node.
  • the gateway protocol handling means comprise decoding means adapted to decode a received extended notification response message comprising an information element indicating the acceptability or allowability of the notification request, and supplementary information elements at least comprising identification information required for radio bearer setup or re-establishment. It is adapted to decode said supplementary information and to send the received packet data to said radio network node directly, over a setup or re-established radio bearer (or in some implementations to the mobility management node) .
  • the invention also provides a method for handling downlink packets addressing an end user station in idle mode and for which a radio bearer has been released.
  • the method comprises the steps of, in a core network packet data gateway node; receiving a data packet addressing the end user station in idle mode; generating or providing a notification request message and sending the notification request message to a mobility management node related to the released radio bearer.
  • the method comprises the steps of: sending a paging request to a radio network node to initiate a paging and radio bearer re-establishing procedure; receiving or collecting information relating to the re-established radio resources (bearer) ; generating a notification response message (also called an extended notification response message) comprising an information element indicating the allowability of the request and supplementary information elements at least comprising identification related information required for radio resource establishment or user plane and control plane communication and, sending the (extended) notification response message to the packet data gateway node.
  • a notification response message also called an extended notification response message
  • the method comprises the steps of: receiving and decoding the (extended) notification response message and sending, substantially directly after decoding, the downlink data packet, using the decoded information, most preferably to the radio network node or, in an alternative embodiment, to the mobility management node.
  • a service request as discussed above can be initiated by the network without producing a high signalling load and unduly loading involved core network nodes. It is also an advantage of the invention that radio bearers can be re-established in a fast and easy manner, without requiring a large amount of signalling capacity. In addition thereto it is an advantage that a solution is provided through which it is possible to, in an easy and efficient manner, handle downlink data packets in the core network also when there is no active radio bearer, particularly for mobile end user stations in an idle mode.
  • network initiated re-establishment of radio bearers can be provided without requiring the introduction or use of state machines or new state machines between procedures in a packet data gateway node in order to keep control of associated, but separate procedures, and for packets to be sent on the same radio bearer.
  • Fig. 1 is a sequence diagram showing a procedure for a network initiated service request according to the state of the art
  • Fig. 2 is a sequence diagram illustrating a procedure for a network initiated service request according to the present invention
  • Fig. 3 is a block diagram of a system in which the inventive concept is implemented
  • Fig. 4 schematically and in a simplified manner illustrates a packet data gateway node according to one embodiment of the present invention
  • Fig. 5 schematically and in a simplified manner illustrates a mobility management node according to an embodiment of the present invention
  • Fig. 6 is a flow diagram describing one implementation of the inventive concept.
  • Fig. 7 is a flow diagram describing the steps taken in a packet data gateway node for network initiated bearer re-establishment according to one embodiment of the present invention.
  • the second protocol handling means of the mobility management node which are provided for packet data gateway node communication, are extended such that in response to a notification request message, a response message is provided which include, in addition to information as to whether the request is allowable, also supplementary information elements.
  • These supplementary information elements particularly at least comprise identification information which is relevant or needed for communication with the radio network over which the addressed end user will be connected, for control plane as well as for user plane communication. This supplementary information is thus included in the notification response message (extended), and sent to the concerned packet data gateway node.
  • the (extended) notification response message is decoded in the packet data gateway node, which re-establishes radio bearers which then are used for downlink data packets towards the end user station.
  • the supplementary information elements particularly at least contain information required for reestablishing radio resources for communication of packet data to the end user station that was addressed, via the radio network node.
  • this supplementary information elements at least comprises the mobile subscriber identity, for example IMSI (International Mobile Subscriber Identity) of the addressed end user station, routeing/location/ tracking area identity (depending on which radio technology that is used) indicating where the mobile end user station is, tunnel endpoint identifiers for control plane and user plane traffic, signalling address of the mobility management node and preferably also recovery information.
  • IMSI International Mobile Subscriber Identity
  • one or more further supplementary information elements may optionally be included in the notification response according to the present invention.
  • one or more of the below mentioned information elements may be included: Selection mode, NSAPI, linked NSAPI, Charging Characteristics, Trace Reference, Trace Type, End User Address, Access Point Name (APN) , user plane packet data gateway node address (if user plane communication supported in the mobility management node) MSISDN, Qos Profile, TFT (Traffic Flow Template) , Trigger Id, OMC (Operation and Maintenance Centre) Identity, APN Restriction, RAT Type, User Location Information, MS Time Zone, CAMEL Charging Information Container, Additional Trace Information.
  • the notification response comprises a PDU (Packet Data Unit) notification response as described in 3GPP 29.060, which however is extended with respect thereto.
  • PDU Packet Data Unit
  • the notification response comprises all possible data that is needed in the packet data gateway node about the stored radio bearer, particularly a PDP context.
  • the packet data gateway node can save memory capacity by only storing a pointer (to a storing means in the mobility management node) and the address of the mobility management node and then fetch the (desired) data on demand.
  • the packet data gateway node can fetch any desired data regarding the radio bearer, particularly a PDP context, and the mobile user station, for example a User Equipment (UE) .
  • the information indicating the allowability may comprise a Cause value or a Cause code wherein for example the Cause code "Request Accepted" indicates if the radio bearer, particularly a PDP context, activation will proceed. Particularly, for other Cause values the PDP context activation procedure will not proceed.
  • Cause codes or Cause values are: “No resources available”, “Service not supported”, “System failure”, “IMSI not known”, “MS is GPRS Detached”, “GPRS connection suspended”, “Mandatory IE incorrect”, “Mandatory IE missing”, “Optional IE incorrect”, “Invalid message format”, “Roaming restriction”.
  • the mobility management node comprises control plane handling means adapted to collect/receive the identity related information of the addressed end user station and the radio access network node, and the packet data gateway node. It is also adapted to order, e.g. by means of the first protocol handler, establishment or re-establishment of the radio resources.
  • the mobility management node preferably comprises or communicates with information storing means for holding the collected end user station and packet data gateway node (and radio network node) related information. Particularly these storing means are connected to the control plane handling means.
  • the gateway protocol handling means are adapted to support reception and decoding of a notification response message comprising one or more of the supplementary information elements discussed above (also denoted extended notification response message) .
  • the packet data gateway node in an advantageous implementation comprises a control plane, or control plane handling means, a user plane, here also called user plane handling means, and a payload buffering means.
  • the payload buffering means is provided in order to make it possible to hold user data intended for the addressed end user, which is received after a notification request message concerning download packet data intended for the addressed end user has been sent, but before the notification response message has been received (when the radio bearer has been re-established, which enables transmission of the first packet) . Since, according to the present invention, a single procedure is provided, it becomes easy to buffer further subsequent incoming downlink packets in the buffering means and, once a first packet has been sent, i.e.
  • the radio bearer is reestablished, the subsequent packets are fetched from the buffer and provided to the end user station.
  • the mobility management node is connected to a subscriber location information holding means holding end user station related information, from which the mobility management node has obtained information (at attach of a mobile station, or activation of a PDP context) which is stored and is used for the notification response message.
  • the notification response message actually replaces an update PDP context procedure, with request and response, to provide the gateway node with information about the stored PDP context.
  • the notification response message particularly comprises a PDU notification response, for example as described in 3GPP 23.873, V.4.0.0, Section 7.4.5 "Service Request Initiated by Network Procedure" and also described in Fig. 1 above.
  • an xGGSN receives a downlink PDP PDU for an UE in idle state, I 0 .
  • the xGGSN then sends a PDU Notification Request Message to a cSGSN related to the PDP context, 2 0 .
  • the cSGSN then returns a PDU Notification Response or Cause Message to the xGGSN in order to acknowledge that it shall request the UE to re-activate the PDP contexts, 2 0 .
  • the cSGSN sends a Paging Message to the RNC, which pages the UE by sending a Paging Message to the UE, 3o.
  • the UE sends a Service Request Message containing P-TMSI, RAI, CKSN, Service Type to the cSGSN, 4 0 , wherein Service Type specifies Paging Response. Then the cSGSN may perform an authentication procedure and the cSGSN knows whether the downlink packet requires RAB establishment, e.g. downlink PDU or not, e.g. Request PDP Context Activation. The cSGSN shall then perform the security mode procedure, 5o.
  • the cSGSN sends a Radio Access Bearer Assignment Request with one or more RAB IDs, on or more xGGSN TEIDs, QoS Profiles, xGGSN IP Address (es) message to the RNC, which sends a Radio Bearer Setup to the UE.
  • the UE returns respond a Radio Bearer Setup Complete Message to the RNC which sends a RAB Assignment Response with RAB ID, TEIDs, RNC IP Addresses Message cSGSN to indicate that GTP tunnels are established on the Iu interface and radio access bearers are established between the RNC and the UE, 60.
  • the cSGSN When the cSGSN has received the IP Address or Addresses and the TEIDs from the RAN, it sends an Update PDP Context Request, 7 0 , to each concerned xGGSN, which updates its PDP Context Fields and returns an Update PDP Context Response message, 7o, and the tunnel between RAN and the xGGSN is reestablished, whereupon the xGGSN sends the downlink packet, 80.
  • a PDU Notification Response is according to the present invention not sent until the information has been collected or gathered and then it also includes the supplementary information. Then the GGSN, or a packet data gateway node in general, can send the downlink PDU substantially at once, which means that the procedure is not split up or divided into two or more distinct procedures. This is very advantageous and allows to save signalling resources etc., e.g. up to 50% as compared to if the known procedures were used. It also becomes possible to easily store further, later, arriving downlink PDUs in the holding means of the gateway node as discussed above.
  • the packet data gateway node is adapted to store a pointer to the information storing means in the management node and the address of the mobility management node.
  • the gateway protocol handler is adapted to activate the pointer to fetch end user station and/or data relating to an established radio bearer from the mobility management node which means that storing capacity can be saved in the packet data gateway node. This also means that any desired data can be fetched at any time.
  • the user plane or payload traffic is sent directly from the packet data gateway node to the concerned radio access network node, for example an eNodeB or an RNC depending on in which communication system the concept is implemented.
  • the user plane traffic, user data is sent after reception and decoding of the extended notification message (including radio resource re-establishment) in the second protocol handling means.
  • the mobility management node optionally only handles control plane messages, i.e. does not have any user plane, which is advantageous.
  • the gateway node may for example comprise an SAE/GW, a serving gateway or a GGSN and a mobility management node may then comprise an MME (Mobility Management Entity), or an SGSN.
  • the user plane data may be sent to the mobility management node, applicable for example in some implementations where the packet data gateway node is an GGSN and the mobility management node comprises an SGSN (with a user plane) .
  • Fig. 2 is a sequence diagram describing the inventive procedure according to a first embodiment. It is supposed that a packet data gateway node (PDGW) receives a downlink data packet DL Pl addressing an UE in idle state as discussed above, 1. The packet data gateway node knows that no bearers are active and therefore sends a notification request message to the mobility management node (related to the deactivated radio bearer, which particularly may be a PDP context), 2. This is done in order to obtain information about radio resources. In the state of the art the procedure is interrupted, cf.
  • PDGW packet data gateway node
  • the notification response is sent only after an update PDP context request/response procedure whereas according to the present invention it is one single procedure which means that there is no need for any state machine or similar to keep control of different procedures, when the procedure is initiated, the subsequent part of the procedure initiated, and that these two different parts or procedures actually belong together.
  • the messaging i.e. signalling, is considerably reduced since the update PDP context procedure is eliminated.
  • the packet data gateway node may comprise an SAE/GW or a GGSN etc.
  • the mobility management node may comprise an MME or an SGSN and the radio network node may comprise an RNC or an eNodeB etc.
  • the inventive concept of course also covers other nodes providing similar functionalities .
  • Fig. 3 very schematically and conceptually illustrates a system in which the inventive concept can be implemented. In the figure it is intended to show embodiments for different types of 3GPP accesses. It is shown a PDGW 10 connected over the S4 interface to SGSN 2OB which in turn communicates with a HLR (Home Location Register) 21B handling subscriber data.
  • HLR Home Location Register
  • the PDGW 10 here can be connected to a UTRAN or a GERAN, here being illustrated simply as an RNC (Radio Network Controller) 3OB only, to which an MS 4OB is connected.
  • PDGW 10 is also connected to a Mobility Management Entity (MME) 2OA over an SIl interface which in turn is connected to an E-UTRAN represented through eNodeB 30A to which a User (UE) 4OA is connected.
  • MME 20A communicates with a subscriber location database HSS (Home Subscriber System) 21A, but as discussed above, the relevant subscriber information has already been provided to MME (at attach) .
  • HSS Home Subscriber System
  • a packet data notification request is sent from PDGW 10 to MME 20A, IA.
  • MME 20A communicates with eNodeB 30A, 2A, using subscriber data stored in MME 20A itself as discussed above to obtain the supplementary information element information (via the paging procedure) for inclusion in a notification response, 4A, to PDGW 10.
  • PDGW 10 is informed about the re-establishment performed by SGSN (or MME) of the radio resources and sends the received PDU directly to eNodeB 3OA, 5A.
  • a notification request message is sent over the S4 interface (here) to SGSN 2OB, IB.
  • SGSN 2OB assembles the information needed, i.e. the supplementary information in communication with RNC 3OB, 2B using stored subscriber data and then returns a notification response, 4B, to PDGW 10.
  • a PDU may be provided to SGSN 20B, 5B.
  • RNC 30B, 5B ' i.e.
  • the illustrated system includes both GERAN/UTRAN access and access over E-UTRAN (a 3GPP SAE/LTE access, System Architecture Evolution/Long Term Evolution) . According to different embodiments systems in which only GERAN and/or UTRAN accesses are supported as well as systems with only accesses via eNodeB are of course covered by the present invention.
  • Fig. 4 is a very schematical block diagram of one exemplary packet data gateway node in which the inventive concept can be implemented. It is here supposed that the packet data gateway node is an SAE/GW 10. It should also be clear that only means and features that are relevant and necessary for the functioning of the inventive concept, or even specific for the inventive concept, are illustrated in the figure. These means and functions are also for explanatory reasons illustrated in a conceptual manner.
  • SAE/GW 10 comprises a gateway protocol handler 11 with a user plane (UP) handler 13 and a control plane (CP) handler 12.
  • the SAE/GW 10 has both a user plane and a control plane wherein the CP handler 10 supports or communicates with means comprising or handling protocols responsive for communication with external networks and with mobility management nodes respectively.
  • the UP handler 13 comprises or is associated with means handling user plane protocols enabling communication of downlink payload packets and, here, for communicating user plane packets to a radio network node, here eNodeB.
  • the gateway protocol handler 11 also comprises decoding means 14.
  • the decoding means can be seen as included in the CP handler 12, but also, in still another embodiment, arranged externally of the gateway protocol handler, the main thing being that a functionality is provided which allows decoding of a received extended notification response message as discussed above. Exactly how this is implemented is not a restrictive feature but it can be done in many ways, and Figure 4 merely intends to illustrate the functionality itself.
  • the CP handler 12 also comprises a control functionality, here illustrated as a control means 12i, which actually is adapted to keep control of when a notification request message has been sent concerning a particular bearer or PDP context and preferably of when a response has been received.
  • control means 12i which actually is adapted to keep control of when a notification request message has been sent concerning a particular bearer or PDP context and preferably of when a response has been received.
  • These means serve the purpose of enabl ing that downlink packets intended for the same bearer/end user station arriving after a notification request message has been sent but when no response has yet been received such that such downlink packets can be stored into buffering means 15, and to, when the response message has been received, activate transmission of the first downlink packet or packet data unit having initiated the transmission of the notification request message and subsequently further possibly in the buffering means stored PDUs.
  • UP handler 13 illustrates how a downlink packet, DL PL (payload) is received in UP handler 13, information thereon also being provided to CP handler 12 which initiates sending of a notification request message to an MME.
  • Information that for a particular released bearer such a notification request message has been sent is held in controlling means 12i and subsequently, when a notification response message is received, decoding means 14 are adapted to decode the message, particularly the supplementary information elements.
  • the UP handler 13 sends the packet to eNodeB .
  • the first PDU initiating the notification request message may be held in the buffering means 15. Alternatively, it is temporarily held in e.g. a separate cache associated with the UP handler 13 or in any other appropriate manner. It should be clear that the functioning would be similar for e.g. a GGSN, a split-up SAE/GW, i.e. a serving gateway and a PDN gateway etc.
  • Fig. 5 is a schematical block diagram of a mobility management node 20. It shows an embodiment in which the mobility management node comprises an MME (Mobility Management Entity) 20. As discussed above with reference to Fig. 4, also in this figure only those functions or means that are necessary for implementation of the inventive concept are illustrated and they are also illustrated in a schematical, conceptual manner to indicate the functions which are specific for the inventive concept.
  • MME 20 comprises first protocol handling means 21 for communication with a radio network node, here an eNodeB . It also comprises second protocol handling means 22 for communication with a packet data gateway node, e.g. an SAE/GW as in Fig. 4.
  • the second protocol handling means 22 are extended to, upon reception of a notification request message, initiate generation of an extended notification response message.
  • control plane, CP, handler 23 which is in communication with the first protocol handler 21 to initiate a paging process in order to re-establish a radio bearer and to gather and collect supplementary information as requested or in a configured manner. It should be clear that this could be illustrated and done in different manners, the main thing being that supplementary information about the end user station and the radio network node over which it is connected, when a radio access bearer has been re-established, is provided to the packet data gateway node e.g. sent by the second protocol handling means 22, or more generally sent over the second protocol used for control plane communication with the packet data gateway node (e.g. SAE/GW) .
  • the packet data gateway node e.g. sent by the second protocol handling means 22, or more generally sent over the second protocol used for control plane communication with the packet data gateway node (e.g. SAE/GW) .
  • the notification request message may indicate which supplementary, and optionally supplementary additional, information that is to be provided. It may also be hardware or software coded in the MME 20 which type of information that is to be provided at reception of a notification request message.
  • Fig. 6 is a schematical flow diagram describing the main procedural steps according to one implementation of the present invention. It is supposed that a downlink packet Pl, which addresses a user equipment UEi which is in an idle mode, i.e. for which there is no radio bearer active, is received in packet data gateway node, 100. Since the packet data gateway node knows that there is no radio bearer setup or active, it generates a notification request message and sends it to the relevant mobility management node, 101. Upon reception of the notification request message, the mobility management node initiates a paging procedure to obtain identity related information about the user station and the radio network node that is concerned, 102. Preferably at least addressing related information for communication in both directions, i.e.
  • the notification response message is extended with the collected or obtained identity related supplementary information elements needed for re-establishment of the inactive, released, radio bearer, 103.
  • more or less supplementary information data can be collected and possibly stored in the storing means of which all or at least the minimum necessary supplementary information as discussed above is included in the extended notification response message, which then is sent to the packet data gateway node, 104.
  • the extended notification response message is decoded in the packet data gateway node, 105, and the packet data can now, after re-establishment, be sent on from the packet data gateway node, preferably directly to the radio network node, 106.
  • Fig. 7 is a flow diagram schematically describing a procedure when a downlink packet Pl', which addresses an UE' which is in an idle mode, is received in for example an SAE/GW, 200.
  • a notification request message is generated and sent to, for example, an MME, 201. It is then continuously monitored or kept control of whether any further packets P X1 addressing the UE' are received, i.e. packets for which the same context or radio bearers are to be used, 201A.
  • the continuous or discrete monitoring procedure is illustrated as a loop back to box 201A. If one or more further packets are received, it is examined or checked whether a radio bearer has been reestablished, 201B, e.g.
  • P X1 is stored in buffering means, 201C, if yes, it is established if the first Pl' has been sent, 201D, and if yes, P X1 is sent, 201E. It is actually monitored continuously or in a discrete manner (at discrete moments in time) if packets are received as well as if the radio bearer has been reestablished, and/or if Pl' has been sent. This can be done in many different ways and in one implementation the sending of Pl ' triggers an examination as to whether there are any packets in the buffering means. This procedure of monitoring possible reception of further packets, storing thereof etc.

Landscapes

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

Abstract

La présente invention concerne un système de communications comportant un réseau principal avec un nœud de passerelle de données par paquets (10) et un nœud de gestion de mobilité (20A; 20B). Le nœud de passerelle de données par paquets (10) est apte au lancement d'une procédure de rétablissement de porteuse radio lors de la réception de données de paquet pour une station d'utilisateur final (40A, 40B) en mode repos par la transmission (40A; 40B) d'un message de notification de demande au nœud de gestion de mobilité (20A; 20B). Le nœud de gestion de mobilité comprend des seconds moyens de gestion de protocole (22) aptes à générer un message de réponse de notification comprenant un élément d'information indiquant si la demande de notification est admissible, et des éléments d'information supplémentaire comprenant au moins une information d'identification pertinente pour le rétablissement de ressources radio d'utilisateur. Le nœud de gestion de mobilité (20; 20A; 20B) est apte à transmettre ladite réponse de notification au nœud de passerelle de données de paquet (10). Le nœud de passerelle de données de paquet (10) est apte à décoder le message de réponse de notification transmis, et ensuite retransmettre directement le paquet de données en liaison descendante reçu vers la station d'utilisateur final (40A; 40B) au moyen des ressources de porteuse rétablies.
PCT/EP2007/060254 2007-09-27 2007-09-27 Système de communications et procédé de gestion de communication de données de paquets WO2009039886A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2007/060254 WO2009039886A1 (fr) 2007-09-27 2007-09-27 Système de communications et procédé de gestion de communication de données de paquets

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2007/060254 WO2009039886A1 (fr) 2007-09-27 2007-09-27 Système de communications et procédé de gestion de communication de données de paquets

Publications (1)

Publication Number Publication Date
WO2009039886A1 true WO2009039886A1 (fr) 2009-04-02

Family

ID=38739950

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2007/060254 WO2009039886A1 (fr) 2007-09-27 2007-09-27 Système de communications et procédé de gestion de communication de données de paquets

Country Status (1)

Country Link
WO (1) WO2009039886A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011110106A1 (fr) * 2010-03-12 2011-09-15 电信科学技术研究院 Procédé, système et appareil adaptés pour sélectionner un tunnel sur le plan de données en fonction du statut d'un équipement d'utilisateur
WO2016186543A1 (fr) * 2015-05-20 2016-11-24 Telefonaktiebolaget Lm Ericsson (Publ) Procédés et nœuds de gestion de supports
EP3104660A1 (fr) * 2009-07-08 2016-12-14 Huawei Technologies Co., Ltd. Procédé, appareil et système de routage de données de plan d'utilisateur dans un réseau mobile
WO2019001749A1 (fr) * 2017-06-30 2019-01-03 Telefonaktiebolaget Lm Ericsson (Publ) Procédé d'établissement d'un appel vocal sur protocole internet (voip) entre un équipement utilisateur (ue) appelant et un ue appelé

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050002407A1 (en) * 2003-05-01 2005-01-06 Interdigital Technology Corporation Method and apparatus for delivery of data-based/voice services over piconets and wireless LANs (WLANs) coupled to 3GPP devices including protocol architecture and information elements relating to short message services (SMS) over WLANs
WO2007039757A2 (fr) * 2005-10-05 2007-04-12 Vodafone Group Plc Reseaux de telecommunications
WO2007079689A1 (fr) * 2006-01-10 2007-07-19 Zte Corporation Procede de radiomessagerie dans des systeme d'acces differents

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050002407A1 (en) * 2003-05-01 2005-01-06 Interdigital Technology Corporation Method and apparatus for delivery of data-based/voice services over piconets and wireless LANs (WLANs) coupled to 3GPP devices including protocol architecture and information elements relating to short message services (SMS) over WLANs
WO2007039757A2 (fr) * 2005-10-05 2007-04-12 Vodafone Group Plc Reseaux de telecommunications
WO2007079689A1 (fr) * 2006-01-10 2007-07-19 Zte Corporation Procede de radiomessagerie dans des systeme d'acces differents

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3104660A1 (fr) * 2009-07-08 2016-12-14 Huawei Technologies Co., Ltd. Procédé, appareil et système de routage de données de plan d'utilisateur dans un réseau mobile
US10015718B2 (en) 2009-07-08 2018-07-03 Huawei Technologies Co., Ltd. Method, apparatus, and system for routing user plane data in mobile network
US10674420B2 (en) 2009-07-08 2020-06-02 Huawei Technologies Co., Ltd. Method, apparatus, and system for routing user plane data in mobile network
WO2011110106A1 (fr) * 2010-03-12 2011-09-15 电信科学技术研究院 Procédé, système et appareil adaptés pour sélectionner un tunnel sur le plan de données en fonction du statut d'un équipement d'utilisateur
US9204475B2 (en) 2010-03-12 2015-12-01 China Academy Of Telecommunications Technology Method, system, and apparatus for selecting data plane tunnel according to the status of user equipment
WO2016186543A1 (fr) * 2015-05-20 2016-11-24 Telefonaktiebolaget Lm Ericsson (Publ) Procédés et nœuds de gestion de supports
US9877232B2 (en) 2015-05-20 2018-01-23 Telefonaktiebolaget Lm Ericsson (Publ) Methods and nodes for managing bearers
WO2019001749A1 (fr) * 2017-06-30 2019-01-03 Telefonaktiebolaget Lm Ericsson (Publ) Procédé d'établissement d'un appel vocal sur protocole internet (voip) entre un équipement utilisateur (ue) appelant et un ue appelé
US11445560B2 (en) 2017-06-30 2022-09-13 Telefonaktiebolaget Lm Ericsson (Publ) Method of establishing a voice over internet protocol, VoIP, call between a calling user equipment, UE, and a called UE

Similar Documents

Publication Publication Date Title
JP7177217B2 (ja) セッション管理のためのシステムおよび方法
US11690130B2 (en) Network initiated release assistance information
US11070627B2 (en) Discovery of a user plane function that supports cellular IoT optimization
US11019668B2 (en) PDU session establishment for cellular IoT
US12108470B2 (en) Application triggering for a wireless device
US20240306069A1 (en) Support of user plane transactions over a mobile network
EP2790454B1 (fr) Procédé pour le rattachement à un réseau e-utran et entité de gestion de la mobilité correspondante
EP2332319B1 (fr) Systèmes et procédés de libération massive de ressources associée à une défaillance de noeud
US12101740B2 (en) Signaling delivery in a wireless network
WO2009039886A1 (fr) Système de communications et procédé de gestion de communication de données de paquets

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: 07803611

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: 07803611

Country of ref document: EP

Kind code of ref document: A1