WO2011095256A1 - Redémarrage de nœud homologue - Google Patents

Redémarrage de nœud homologue Download PDF

Info

Publication number
WO2011095256A1
WO2011095256A1 PCT/EP2010/070224 EP2010070224W WO2011095256A1 WO 2011095256 A1 WO2011095256 A1 WO 2011095256A1 EP 2010070224 W EP2010070224 W EP 2010070224W WO 2011095256 A1 WO2011095256 A1 WO 2011095256A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
peer node
restarted
pgw1
sgw
Prior art date
Application number
PCT/EP2010/070224
Other languages
English (en)
Inventor
Yong Yang
Original Assignee
Telefonaktiebolaget L M 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 L M Ericsson (Publ) filed Critical Telefonaktiebolaget L M Ericsson (Publ)
Publication of WO2011095256A1 publication Critical patent/WO2011095256A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition

Definitions

  • the embodiments to be described relate to signaling between entities in a mobile communication network during restarting of a peer node, e.g. a packet data network gateway.
  • a peer node e.g. a packet data network gateway.
  • Figure 1 a illustrates a known non-roaming architecture for 3GPP accesses
  • figure 1 b illustrates a known non-roaming architecture for 3GPP accesses within EPS using PMIP- based S5.
  • an EPC network When an EPC network is utilized for either E-UTRAN access or GERAN/UTRAN access, to allow a UE to access a packet data service such as VoIP or a streaming service or similar, the UE needs to set up a PDN connection that i.a. involves the logical entities MME or S4-SGSN, SGW and PGW at the control plane.
  • a PDN connection i.a. involves the logical entities MME or S4-SGSN, SGW and PGW at the control plane.
  • 3GPP TS 23.401 e.g. TS 23.401 v 9.3.0
  • the restart procedure is outlined as follows: "Across GTP-C based interfaces an SGSN, GGSN, SGW and PGW utilize either GTPv1-C or GTPv2-C Echo Request and Echo Response messages or GTP-C messages containing the Recovery Information Element to detect and handle a restart.
  • a GTP-C entity shall maintain two Restart counters:
  • a GTP-C entity may have a common local Restart counter for all peers, or it may have a separate local Restart counter for each peer.
  • a GTP-C entity may probe the liveliness of each peer with which it is in contact by sending an Echo Request message (see clause X 'Path management procedures") .
  • the presence of the Restart counter in Echo Request or in a GTP-C message depends on the GTP-C version and therefore is specified in 3GPP TS 29.060 [8] and 3GPP TS 29.274 [13], respectively.
  • the GTP-C entity that receives a Recovery Information Element in an Echo Response or in another GTP-C message from a peer shall compare the received remote Restart counter value with the previous Restart counter value stored for that peer entity.
  • Restart counter value received in the Echo Response or in the GTP-C message shall be stored for the peer.
  • an SGW When an SGW detects that a peer MME or peer PGW has restarted (see clause 18 "GTP-C based restart procedures") it shall delete 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 shall not try to directly clear resources in the MME or PGW. The SGW may optionally perform other implementation specific actions such as messages to clear other external resources (e.g. PCC messages).
  • GTP error indication message shall be handled as follows:
  • the eNodeB If the eNodeB receives a GTP error indication from the SGW, it shall initiate the E-RAB Release procedure and immediately locally release the E-RAB (i.e. without waiting for a response from the MME).
  • the eNodeB If the eNodeB receives a GTP error indication from a peer eNodeB over X2, it shall ignore it. "
  • the MME When the MME receives the S1 -AP message "E-RAB release indication" from the eNB, then the MME shall start MME Initiated Dedicated Bearer Deactivation as specified in the 3GPP TS23.401 .
  • the hanging PDN connections in the MME will be or have to be removed per Bearer Context one by one.
  • this specification discloses a method in a first node in a mobile
  • the method comprises the actions of: receiving from a peer node information relating to a restart of the peer node; and processing the received information, comprising a determination that the peer node has restarted, and deleting data associated with at least one data connection associated with the restarted peer node; and sending a request to delete bearers to at least a further node correlated with the restarted peer node so as to enable the further node to delete all data connections and/or bearer contexts associated with the restarted peer node.
  • a situation e.g. involving hanging PDN connections or similar may be handled with a mechanism that e.g. allows a SGW to use one single GTPv2 message per MME to delete all the PDN connections which are associated with that restarted PGW.
  • This may involve inclusion, by the SGW, of the SGW IP address for S1 1/S4 and the PDN GW Address in Use (control plane) of each PDN connection in the deletion message initiated from the SGW after it receives an incremented restart counter from the PGW.
  • embodiments of the present solution may also avoid the high signaling load occurring if the SGW has to send a Delete Bearer Request message per PDN connection. Instead, the embodiments may use one single request to delete bearers per MME.
  • embodiments of the present solution may use an error indication mechanism performed on the user plane to detect the broken PDN connections due to the restart in the PGW. This facilitates a deletion of all the PDN connections which are handled by the restarted PGW, compared to a deletion of each such PDN connection one by one.
  • Figure 1 a is a block diagram of a mobile communication network
  • Figure 1 b is a block diagram of a mobile communication network
  • Figure 2a a schematic illustration an exemplifying wireless communication system in the form of a 3GPP LTE system 200
  • Figure 2b is a block diagram of a network node
  • Figure 3a is a flow chart of a signaling method
  • Figure 3b is a sequence diagram, of the signalling method
  • Figure 4 is a block diagram of a mobile communication network.
  • Figure 5a is a copy of a part of the information storage table for the MME as specified in 3GPP TS23.401 , chapter 5.7.2, table 5.7.2-1 ,
  • Figure 5b is is a copy of subsequent part of the information storage table for the MME as specified in 3GPP TS23.401 , chapter 5.7.2, table 5.7.2-1 ,
  • Figure 5c is still a copy of still a subsequent part of the information storage table for the MME as specified in 3GPP TS23.401 , chapter 5.7.2, table 5.7.2-1 ,
  • Figure 6a is a copy of table 7.2.9.2-1 in 3GPP TS 29.274-v920,
  • Figure 6b is a copy of table 7.2.9.2-2 of 3GPP TS 29.274-v920.
  • Fig. 2a illustrates an exemplifying 3GPP LTE system 200 comprising a plurality of User Equipments (UE) 215a, 215b and an Evolved Packet System (EPS) 210.
  • the exemplifying EPS 210 comprises at least one Home Subscriber Server (HSS) 215, possibly at least one Policy and Charging Rules Function (PCRF) 216, at least one Mobility Management Entity (MME) 21 1 , at least one Serving Gateway (SGW) 212a, at least one enhanced Node B (eNB) 213a and at least one PDN Gateway (PGW) 214a.
  • EPC Evolved Packet Core
  • the LTE system 200 comprises the MME 21 1 , the SGW 212a and the PGW 214a.
  • the general structure of the exemplifying LTE system 200 in Figure 2a is well known as such to those skilled in the art and there is no need for a detailed description.
  • the components of the LTE system 200 are the same as those in the exemplifying LTE systems in Figure 1 a and/or Figure 1 b, unless otherwise is explicitly or implicitly made clear from the description herein. Nevertheless, a brief explanation of the components in the system 200 being relevant to embodiments of the present solution will be given below,
  • the eNB 213a is an access point or similar configured to communicate with the UE:s 215a and/or 215b via a wireless radio interface Uu.
  • the UE 215a and/or 215b may be any device used by a user to communicate with the EPS 210.
  • the UE may e.g. be a hand- 5 held telephone, a card in a laptop computer, or any other device that is configured to connect to the eNBs of the EPS.
  • the MME 21 1 is responsible for the overall mobility in the LTE system 200. When a UE 215a or 215b registers, the MME 21 1 will request subscriber data from the HSS 215 and
  • the MME 21 1 will also take care of signalling to and from the UE 215a or 215b by means of two different signalling protocols. This is commonly referred to as Non Access Stratum (NAS) signalling.
  • NAS Non Access Stratum
  • the MME 21 1 will communicate this with the SGW 212a.
  • the bearers are commonly referred to as
  • EPS bearers or PDN connections.
  • the MME 21 1 When a UE 215a or 215b is registered to the MME 21 1 , then the MME 21 1 will handle all paging functions and mobility management functions (tracking area updates etc). If a UE 215a or 215b registers in a foreign network, then the MME or similar that is located in that network will obtain subscriber data from the HSS 215 in the home network. This is referred to as roaming functions.
  • the main task of the SGW 212a is to tunnel UE user-data between the PGW 214a and the eNB 213a.
  • the SGW 212a is the node in the EPS 210 that charges user-data and takes care of accounting functions (charging between operators) or similar.
  • the SGW 212a will get orders from the MME 21 1 to establish, modify and release EPS 25 bearers.
  • the SGW 212a comprises a Decision Unit 212a configured to operatively perform the actions in methods according to embodiments of the present invention, and a computer readable memory 30 212b and a communication interface 212c.
  • the Decision Unit 212a is preferably
  • the decision unit 212a may be a processor that is configured to execute computer program instruction sets stored in the computer readable memory 212b for performing signaling with other nodes in a system such as the systems illustrated in Figures 1 a and 1 b and 2a discussed above and in the following (e.g. other nodes in the system 200 in Figure 2a).
  • the PGW 214a is the interface between the internal IP network of the EPS 210 and various external Packet Data Networks (PDN) 218, e.g. various external IP networks such as the common and well known Internet or similar. It may be added that a SGW and a PGW may be combined and co-located in the same or neighbouring hardware as a matter of implementation for vendors of core networks.
  • PDN Packet Data Networks
  • the PGW 214a is also the so called policy and charging enforcement point.
  • the main principle is that policy and charging function verifies that an UE 215a or 215b only sends data according to what it has requested and allowed.
  • the policies are transferred from the PCRF 216 to the PGW 214a which then acts as a Policy and Charging Enforcement Function (PCEF) so as to perform packet filtering (for example, by removing not accepted packets).
  • PCEF Policy and Charging Enforcement Function
  • the IP Multimedia Subsystem (IMS) belongs to the control plane and a UE 215a or 215b will request services from the IMS system.
  • IMS IP Multimedia Subsystem
  • UE 215a or 215b will request services from the IMS system.
  • some function in the user plane such as a PCEF or similar must supervise that users only send the correct amount of data to the correct destination.
  • control layer will indicate what a user is allowed to do and it is the task of the PCRF 216 to create rules for this. This is referred to as a "policy”.
  • PCRF 216 will also create charging rules and send this information to the PGW 214a.
  • the short lines labelled Gi, Gx, S1 -U, S3, S5/S8, S6a and Uu etc are in correspondence with the 3GPP specifications and illustrate that logical interfaces with the corresponding names are used for
  • FIG 3a is a flow chart of a method according to an embodiment of the present solution that may be performed in a serving gateway, SGW, such as an SGW 212 in Figure 2a, 2b or 4.
  • SGW serving gateway
  • the SGW 212 may receive, once the PGW 214a has recovered from a restart, information relating to the restart of the PGW 2 4a.
  • the SGW 212 may e.g. receive an incremented Restart Counter from the PGW 214a, e.g. via an Echo Request/Response message or some other PDN signaling message.
  • processing of the received information may be performed, comprising a determination that the PGW 214a has restarted. This may e.g.
  • the SGW 212 may then delete 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 as stated in the 3GPP specification.
  • the SGW 212 sends a request to delete bearers (e.g. in the form of a Delete Bearer Request) to the MME 21 1 or MMEs as may be the case, preferably together with the PDN GW Address in Use (control plane) and SGW IP address for S1 1/S4, to allow MME 21 1 to correlate with the restarted PGW 214a and the sending SGW 212, to delete all the PDN connections and/or bearer contexts associated with that PGW 214a and the sending SGW 212 at the MME 214a or MMEs as may be the case.
  • bearers e.g. in the form of a Delete Bearer Request
  • FIG. 3b is a sequence diagram illustrating the method in Figure 3a. Turning now to Figure 4, a more detailed description of a signaling method according to an embodiment of the present solution will be described.
  • UE1 there are several UEs (i.e. UE1 , UE10, UE1 1 , UE1 x, and UE2 and UE3) registered at a MME (i.e. MME1 ) and located in different Tracking Areas. It is also assumed that these UEs are connected via different SGWs (i.e. SGW1 , SGW2, SGW3) to the same PGW (i.e. PGW1 ).
  • SGWs i.e. SGW1 , SGW2, SGW3
  • UE1 , UE10, UE1 1 and UE1 x are located in Tracking Areal and that they are registered in MMEI and that they have setup PDN connections via SGW1 and PGW1. It is also assumed that UE2 is located in Tracking Area2 and that it is registered in MME1 and that it has setup PDN connection via SGW2 and PGW1. It is further assumed that UE3 is located in Tracking Area3 and that it is registered in
  • PGW1 may either send Echo Request preferably including its incremented Restart Counter, or reply with Echo Response if it receives Echo Request from SGWs, or in response to the received other PDN connection related signaling message, e.g. Create Session Request, the SGW1 will include the increment Restart Counter.
  • SGW1 sends a request to delete bearers (e.g. a Delete Bearer Request) to MME1 to inform MME1 to remove all the PDN connections and/or bearer contexts associated with MME1 , SGW1 and PGW1. So PDN connections and/or bearer contexts for UE1 , UE10, UE1 1 and UE1x will be removed in MME1.
  • a request to delete bearers e.g. a Delete Bearer Request
  • MME1 may expect that SGW2 will also send a request to delete bearers (e.g. a Delete Bearer Request) to MME1 to inform MME1 to remove all the PDN connections and/or bearer contexts associated with MME1 , SGW2 and PGW1 . So PDN connection and/or bearer context for UE2 will be removed in MME1.
  • a request to delete bearers e.g. a Delete Bearer Request
  • MME1 may expect that SGW3 will also send a request to delete bearers (e.g. a Delete Bearer Request) to MME1 to inform MME1 to remove all the PDN connections and/or bearer contexts associated with MME1 , SGW3 and PGW1. So PDN connection and/or bearer context for UE3 will be removed in MME1. So until now, all the hanging PDN connections and/or bearer contexts in MME1 due to the restart of PGW are totally and safely cleared.
  • a request to delete bearers e.g. a Delete Bearer Request
  • SGW1 may send special format of Delete Bearer Request to MME2 and MME3 as well.
  • the SGW After an SGW restart, the SGW shall delete all MM Bearer contexts affected by the restart that it may have stored. During or immediately after an SGW Restart the SGW shall place local SGW restart counter value in all GTPv2 Echo requests/responses messages and ⁇ heartbeat
  • the SGW will receive the MME restart counter in GTPv2 Echo requests and Echo response messages that the SGW receives from the MME.
  • the SGW will receive the PGW restart counter in GTPv2 Echo requests/ responses and PMIPv6 heartbeat requests/responses that the SGW receives from the PGW.
  • a possible impact of embodiments discussed herein comprises that the SGW should in addition initiate the deletion for all the PDN connections from that restarted PGW at the corresponding MMEs, preferably by using GTPv2 message Delete Bearer Request, possibly with a proper cause code or similar which is used to indicate that the PGW has restarted.
  • the SGW may optionally perform other implementation specific actions such as messages to clear other external resources (e.g. PCC messages).
  • an SGW detects that a peer MME has restarted (see clause 18 "GTP-C based restart procedures ") it shall delete 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 shall not try to directly clear resources in the PGW.
  • the SGW will have the identity of the MME and PGW currently in use for a PDN connection available in the SGW's PDN connection table as part of existing EPC procedure.
  • GTPv2 message Delete Bearer Request according to 3GPP TS 29.274-v910 is as follows: 7.2.9.2 Delete Bearer Request
  • the direction of this message shall be from PGW to SGW and from SGW to MME/S4-SGSN (see Table 6. 1-1).
  • a Delete Bearer Request message shall be sent as part of the following procedures:
  • this Request is sent by the PGW to the SGW and shall be forwarded to the MME or S4-SGSN.
  • the message shall also be sent on the S4/S11 interface by the SGW to the SGSN/MME to delete the bearer resources on the other ISR associated CN node if the ISRAI flag is not set in the Modify Bearer Request message.
  • the message shall also be sent on the S4/S11 interface by the SGW to the SGSN/MME to delete the bearer resources on the other ISR associated CN node in the TAU/RAU/Handover procedures if the ISR related Cause IE is included in the Delete Session Request message.”
  • a possible impact of embodiments discussed herein comprises that a Delete Bearer Request message or similar may also be sent on the S4/S1 1 interface by the SGW to the MME/S4-SGSN, preferably as part of the SGW initiated PDN connection/EPS bearer cleanup procedures as specified in 3GPP TS 23.007v 9.2.0.
  • Figure 6a is a copy of table 7.2.9.2-1 in 3GPP TS 29.274-v920
  • Figure 6b is a copy of table 7.2.9.2-2 of 3GPP TS 29.274-v920 that tabulates information elements in a Delete Bearer Request message, complemented with information (underlined) that may be used in an embodiment realizing the mechanism discussed above.
  • Table 7.2.9.2-1 has the following title in 3GPP TS 29.274-v920;
  • Table 7.2.9.2-1 specifies the presence of lEs in the Delete Bearer Request message.
  • Said table 7.2.9.2-1 as shown in Figure 6a comprises exemplifying underlined
  • Table 7.2.9.2-2 shown in Figure 6b has the following title in 3GPP TS 29.274-v920; "Table 7.2.9.2-2: Bearer Context within Delete Bearer Request"
  • Some embodiments are directed to a method in a first node in a mobile communication network.
  • the method comprises the actions of receiving from a peer node information relating to a restart of the peer node; and processing the received information comprising a determination that the peer node has restarted and deleting data associated with at least one data connection associated with the restarted peer node; and sending a request to delete bearers to at least a further node correlated with the restarted peer node enabling the further node to delete all data connections and/or bearer contexts associated with the restarted peer node.
  • said "request to delete bearers" sent to a further node as indicated above may be any suitable message, provided that the message enables the further node to delete data connections and/or bearer contexts associated with the restarted peer node.
  • the information relating to a restart of the peer node may be obtained by receiving a packet data network, PDN signalling message from the peer node.
  • the packet data network, PDN signalling message may be an echo response message or an echo request message received from the peer node.
  • the received information relating to a restart of the peer node may comprise an incremented restart counter.
  • the data connection may be a packet data network, PDN connection.
  • the first node may be a serving gateway, SGW, and the peer node may be a PDN Gateway, PGW, and the further node may be a mobility management entity, ME.
  • the request to delete bearers may comprise the PDN GW Address in use for the PDN Gateway, PGW, and the SGW IP address for S1 1/S4 for the serving gateway, SGW, enabling the mobility management entity, MME, to correlate with the restarted PDN Gateway, PGW, and the sending serving gateway, SGW, so as to delete all PDN connections and/or bearer contexts associated with the restarted PDN Gateway, PGW, and the serving gateway, SGW.
  • Some other embodiments are directed to a first node in a mobile communication network.
  • the first node comprises a decision unit and memory circuitry configured to operatively perform the actions of receiving from a peer node information relating to a restart of the peer node; and processing the received information, comprising a determination that the peer node has restarted and deleting data associated with at least one data connection associated with the restarted peer node; and sending a request to delete bearers to at least a further node correlated with the restarted peer node enabling the further node to delete all data connections and/or bearer contexts associated with the restarted peer node.
  • the "request to delete bearers" sent to a further node as indicated above may be any suitable message, provided that the message enables the further node to delete data connections and/or bearer contexts associated with the restarted peer node.
  • the information relating to a restart of the peer node may be obtained by the first node receiving a packet data network, PDN signalling message from the peer node.
  • the packet data network, PDN signalling message may be an echo response message or an echo request message received by the first node from the peer node.
  • the information received by the first node relating to a restart of the peer node may comprise an incremented restart counter.
  • the data connection may be a packet data network, PDN connection.
  • the first node may be a serving gateway, SGW, and the peer node may be a PDN Gateway, PGW, and the further node may be a mobility management entity, MME.
  • the request to delete bearers sent by the first node may comprise the PDN GW Address in use for the PDN Gateway, PGW, and the SGW IP address for S1 1/S4 for the serving gateway, SGW, enabling the mobility management entity, MME, to correlate with the restarted PDN Gateway, PGW, and the sending serving gateway, SGW, so as to delete all PDN connections and/or bearer contexts associated with the restarted PDN Gateway, PGW, and the serving gateway, SGW.

Abstract

La présente invention porte sur un premier nœud et un procédé dans un premier nœud (212) dans un réseau de communication mobile (200). Le procédé comprend les opérations consistant à recevoir (301) d'un nœud homologue (214a) des informations relatives à un redémarrage du nœud homologue (214a) ; traiter (302) les informations reçues, y compris déterminer que le nœud homologue (214a) a redémarré, et supprimer des données associées à au moins une connexion de données associée au nœud homologue ayant redémarré (214a) ; et envoyer (303) une requête de suppression de supports à au moins un autre nœud (211) corrélé au nœud homologue ayant redémarré (214a), permettant à l'autre nœud (211) de supprimer toutes les connexions de données et/ou tous les contextes de support associés au nœud homologue ayant redémarré (214a).
PCT/EP2010/070224 2010-02-02 2010-12-20 Redémarrage de nœud homologue WO2011095256A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US30070710P 2010-02-02 2010-02-02
US61/300,707 2010-02-02

Publications (1)

Publication Number Publication Date
WO2011095256A1 true WO2011095256A1 (fr) 2011-08-11

Family

ID=43618122

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2010/070224 WO2011095256A1 (fr) 2010-02-02 2010-12-20 Redémarrage de nœud homologue

Country Status (1)

Country Link
WO (1) WO2011095256A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013029245A1 (fr) * 2011-08-31 2013-03-07 华为技术有限公司 Procédé, système et dispositif de traitement de support
CN103797838A (zh) * 2013-12-31 2014-05-14 华为技术有限公司 一种业务处理的方法和设备
EP2874349A4 (fr) * 2012-08-01 2015-07-15 Huawei Tech Co Ltd Procédé et appareil de traitement de chemin de communication
WO2015163712A1 (fr) * 2014-04-23 2015-10-29 엘지전자 주식회사 Procédé pour réagir à une défaillance d'un pdn particulier
WO2020171765A1 (fr) * 2019-02-22 2020-08-27 Telefonaktiebolaget Lm Ericsson (Publ) Atténuation d'attaques dos
WO2020222842A1 (fr) * 2019-05-01 2020-11-05 Nokia Technologies Oy Signalisation de capacités d'équipement utilisateur optimisée comprenant la récupération à partir d'une défaillance de base de données
EP4079096A4 (fr) * 2019-12-19 2022-12-21 Telefonaktiebolaget LM Ericsson (publ) Procédé et appareil de signalisation de fermetures de session dans un réseau de communication

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004043086A2 (fr) * 2002-11-05 2004-05-21 Telefonaktiebolaget Lm Ericsson (Publ) Notification collective de reenclenchement de noeud destinee a un sous ensemble de connections de reseau d'acces radio
US20090239526A1 (en) * 2008-03-21 2009-09-24 Research In Motion Limited Evolved Packet System Quality of Service Enforcement Deactivation Handling to Prevent Unexpected User Equipment Detach
WO2009117886A1 (fr) * 2008-03-26 2009-10-01 华为技术有限公司 Procédé et système de notification de réinitialisation de dispositif, passerelle de desserte et de données par paquet et élément de gestion de mobilité
US20090264131A1 (en) * 2007-08-07 2009-10-22 Huawei Techonologies Co., Ltd. Method, system, and device for user detachment when a handover or change occurs in heterogeneous network
EP2139190A1 (fr) * 2008-04-30 2009-12-30 Huawei Technologies Co., Ltd. Procédé, système et dispositif de déconnexion cachée

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004043086A2 (fr) * 2002-11-05 2004-05-21 Telefonaktiebolaget Lm Ericsson (Publ) Notification collective de reenclenchement de noeud destinee a un sous ensemble de connections de reseau d'acces radio
US20090264131A1 (en) * 2007-08-07 2009-10-22 Huawei Techonologies Co., Ltd. Method, system, and device for user detachment when a handover or change occurs in heterogeneous network
US20090239526A1 (en) * 2008-03-21 2009-09-24 Research In Motion Limited Evolved Packet System Quality of Service Enforcement Deactivation Handling to Prevent Unexpected User Equipment Detach
WO2009117886A1 (fr) * 2008-03-26 2009-10-01 华为技术有限公司 Procédé et système de notification de réinitialisation de dispositif, passerelle de desserte et de données par paquet et élément de gestion de mobilité
EP2139190A1 (fr) * 2008-04-30 2009-12-30 Huawei Technologies Co., Ltd. Procédé, système et dispositif de déconnexion cachée

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 (Release 8)", 3GPP STANDARD; 3GPP TS 29.274, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V8.4.0, 18 December 2009 (2009-12-18), pages 1 - 141, XP050401224 *
"3rd Generation Partnership Project; Technical Specification Group Core Network; Restoration procedures (Release 8)", 3GPP STANDARD; 3GPP TS 23.007, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V8.6.0, 17 December 2009 (2009-12-17), pages 1 - 37, XP050400946 *

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013029245A1 (fr) * 2011-08-31 2013-03-07 华为技术有限公司 Procédé, système et dispositif de traitement de support
CN103155688A (zh) * 2011-08-31 2013-06-12 华为技术有限公司 一种承载的处理方法、系统及装置
US11233694B2 (en) 2012-08-01 2022-01-25 Huawei Technologies Co., Ltd. Method and device for processing communication path
US10243783B2 (en) 2012-08-01 2019-03-26 Huawei Technologies Co., Ltd. Method and device for processing communication path
EP2874349A4 (fr) * 2012-08-01 2015-07-15 Huawei Tech Co Ltd Procédé et appareil de traitement de chemin de communication
US9503317B2 (en) 2012-08-01 2016-11-22 Huawei Technologies Co., Ltd. Method and device for processing communication path
CN103797838A (zh) * 2013-12-31 2014-05-14 华为技术有限公司 一种业务处理的方法和设备
US10165618B2 (en) 2013-12-31 2018-12-25 Huawei Technologies Co., Ltd. Service processing method and device
CN103797838B (zh) * 2013-12-31 2018-08-07 华为技术有限公司 一种业务处理的方法和设备
US10602350B2 (en) 2014-04-23 2020-03-24 Lg Electronics Inc. Method for responding to failure of specific PDN
WO2015163712A1 (fr) * 2014-04-23 2015-10-29 엘지전자 주식회사 Procédé pour réagir à une défaillance d'un pdn particulier
WO2020171765A1 (fr) * 2019-02-22 2020-08-27 Telefonaktiebolaget Lm Ericsson (Publ) Atténuation d'attaques dos
WO2020222842A1 (fr) * 2019-05-01 2020-11-05 Nokia Technologies Oy Signalisation de capacités d'équipement utilisateur optimisée comprenant la récupération à partir d'une défaillance de base de données
JP2022530550A (ja) * 2019-05-01 2022-06-29 ノキア テクノロジーズ オサケユイチア データベース障害からの回復を含む最適化されたユーザ機器能力シグナリング
TWI776145B (zh) * 2019-05-01 2022-09-01 芬蘭商諾基亞科技公司 包括從資料庫故障復原之最佳化使用者設備能力傳訊技術
US11540117B2 (en) 2019-05-01 2022-12-27 Nokia Technologies Oy Optimized user equipment capabilities signaling including recovery from database failure
JP7404398B2 (ja) 2019-05-01 2023-12-25 ノキア テクノロジーズ オサケユイチア データベース障害からの回復を含む最適化されたユーザ機器能力シグナリング
EP4079096A4 (fr) * 2019-12-19 2022-12-21 Telefonaktiebolaget LM Ericsson (publ) Procédé et appareil de signalisation de fermetures de session dans un réseau de communication

Similar Documents

Publication Publication Date Title
US11323921B2 (en) Method, system, and device for user detachment when a handover or change occurs in heterogeneous network
US10652945B2 (en) Mobile terminated call improvements
EP2471307B1 (fr) Relocalisation d'ancre de mobilité pour des abonnés nomades
JP5964442B2 (ja) Ｉｒａｔハンドオーバ中ｉｐコンテキストのロスを最小化するためのシステムおよび方法
US9713042B2 (en) Method and system for notifying attribute of IP address and SGW
US8892134B2 (en) Mobile communication method, call control node, priority control node and mobility management node
US11696358B2 (en) Methods and nodes for handling bearers
EP2481228A1 (fr) Procédé permettant de traiter une défaillance d'une entité de gestion de la mobilité (mme) dans un réseau lte/epc
WO2011095256A1 (fr) Redémarrage de nœud homologue
WO2009117886A1 (fr) Procédé et système de notification de réinitialisation de dispositif, passerelle de desserte et de données par paquet et élément de gestion de mobilité
US9838924B2 (en) Method and device for processing inter-system reselection or switch
CN101600192B (zh) 用户上下文同步方法、设备及系统
EP2761969B1 (fr) Restauration de mag pmipv6
WO2012013103A1 (fr) Procédé et système de rapport d'identité de passerelle
WO2016019559A1 (fr) Appareil, système, et procédé d'identification d'équipement d'utilisateur de réseau partagé
US9838913B2 (en) Method and apparatus for removing policy and charging control rule from default bearer
US11284239B2 (en) Central node management of UE context
WO2016112774A1 (fr) Procédé de mise à jour de position et unité de gestion de mobilité

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

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

Country of ref document: EP

Kind code of ref document: A1