WO2015168494A1 - Procédés et appareil de gestion de temporisation - Google Patents

Procédés et appareil de gestion de temporisation Download PDF

Info

Publication number
WO2015168494A1
WO2015168494A1 PCT/US2015/028697 US2015028697W WO2015168494A1 WO 2015168494 A1 WO2015168494 A1 WO 2015168494A1 US 2015028697 W US2015028697 W US 2015028697W WO 2015168494 A1 WO2015168494 A1 WO 2015168494A1
Authority
WO
WIPO (PCT)
Prior art keywords
service request
retry
request
status indicator
retried
Prior art date
Application number
PCT/US2015/028697
Other languages
English (en)
Inventor
Curt Wong
Original Assignee
Nokia Solutions And 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 Solutions And Networks Oy filed Critical Nokia Solutions And Networks Oy
Publication of WO2015168494A1 publication Critical patent/WO2015168494A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/18Management of setup rejection or failure

Definitions

  • the present invention relates generally to radio network communications. More particularly, various embodiments relate to improved systems and techniques for prevention of timing conflicts between entities in a radio communications network.
  • a network can comprise large numbers of base stations such as eNBs, and these base stations are served by core network elements packet core elements, serving gateways (SGWs), packet gateways (PGWs), authentication, authorization, and accounting (AAA) elements, policy and charging rule function (PCRF) elements, and the like.
  • SGWs serving gateways
  • PGWs packet gateways
  • AAA authentication, authorization, and accounting
  • PCRF policy and charging rule function
  • numerous instances of core network elements may be provided, and user devices may, upon failure to connect to a first element, attempt connection to another element of the same type.
  • a method comprises sending a previous service request to a serving core network element of a wireless communications network, determining that the previous service request has not been received and, upon the determination that the previous service request has not been received, configuring a retry status indicator and sending a retried service request to a serving core network element of the wireless communications network, wherein the retried service request includes the retry status indicator.
  • a method comprises receiving at a serving core network element of a wireless communications network, a service request sent from an initiating device, examining the service request to determine whether or not the service request includes a retry status indicator, and determining whether or not to provide service based on whether or not the service request includes a retry status indicator.
  • an apparatus comprises at least one processor and memory storing a program of instructions.
  • the memory storing the program of instructions is configured to, with the at least one processor, cause the apparatus to at least send a previous service request to a serving core network element of a wireless communications network, determine that the previous service request has not been received, and, upon the determination that the previous service request has not been received, configure a retry status indicator and sending a retried service request to a serving core network element of the wireless communications network, wherein the retried service request includes the retry status indicator.
  • an apparatus comprises at least one processor and memory storing a program of instructions.
  • the memory storing the program of instructions is configured to, with the at least one processor, cause the apparatus to at least receive at a serving core network element of a wireless communications network, a service request sent from an initiating device, examine the service request to determine whether or not the service request includes a retry status indicator, and determine whether or not to provide service based on whether or not the service request includes a retry status indicator.
  • a computer readable medium stores a program of instructions.
  • Execution of the program of instructions by at least one processor configures an apparatus to at least send a previous service request to a serving core network element of a wireless communications network, determine that the previous service request has not been received, and, upon the determination that the previous service request has not been received, configure a retry status indicator and sending a retried service request to a serving core network element of the wireless communications network, wherein the retried, service request includes the retry status indicator.
  • a computer readable medium stores a program of instructions. Execution of the program of instructions by at least one processor configures an apparatus to at least receive at a serving core network element of a wireless communications network, a service request sent from an initiating device, examine the service request to determine whether or not the service request includes a retry status indicator, and determine whether or not to provide service based on whether or not the service request includes a retry status indicator.
  • an apparatus comprises means for sending a previous service request to a serving core network element of a wireless communications network, means for determining that the previous service request has not been received and means for, upon the determination that the previous service request has not been received, configuring a retry status indicator and sending a retried service request to a serving core network element of the wireless communications network, wherein the retried service request includes the retry status indicator.
  • an apparatus comprises receiving at a serving core network element of a wireless communications network, a service request sent from an initiating device, means for examining the service request to determine whether or not the service request includes a retry status indicator, and means for determining whether or not to provide service based on whether or not the service request includes a retry status indicator,
  • Fig. 1 illustrates a wireless network according to an embodiment of the invention
  • Fig. 2 illustrates an operations diagram according to an embodiment of the present invention
  • Fig. 3 illustrates a process according to an embodiment of the present invention
  • Fig. 4 illustrates a data processing device that may be used in carrying out one or more embodiments of the present invention.
  • Embodiments of the present invention address problems relating to conflicts presented upon connection attempts to redundant elements in a wireless communication network, particularly attempts to connect to a second element upon failure to connect to a first element.
  • a scenario such as the following may occur:
  • a user equipment sends a network attachment request.
  • the network's mobility management entity sends a call session request (CSReq) to a serving gateway (SGW).
  • the SGW forwards the CSReq to a first packet gateway (PGW-1).
  • the PGW-1 does not respond, or the response is lost, so that the MME does not receive a call setup response (CSResp) with "Request accepted" from the PGW-1, so the MME retries the CSReq, sending a CSReq to PGW-2.
  • This retry attempt has a successful outcome, with PGW-2 responding and the response being received by the MME.
  • IP internet protocol
  • IMS internet protocol multimedia system
  • PCRF policy and charging rule function
  • the PGW-1 is processing its queue, and eventually the CSReq that was previously received is ready.
  • the PGW-1 sends a credit control request initialization (CCR-I) to the PCRF.
  • CCR-I credit control request initialization
  • the PCRF assumes that the CCR-I represents a request for a session update and overwrites the UE context with PGW-1 information due to the new (to the PCRF) CCR-I.
  • the packet data network (PDN) information in the AAA may also be overwritten with the information associated with the PGW-1 information.
  • PDN packet data network
  • the dedicated bearer creation bearer procedure fails and the application function (AF), which in this example is the packet call session control function (P-CSCF) sends a failure notification to the UE when a (for example) voice over LTE (VoLTE) session is needed.
  • AF application function
  • P-CSCF packet call session control function
  • connection fails, and can be resolved by powering the UE off and then on again, so that a new ATTACH can be made to re-synchronize the UE context in the network.
  • a sending entity may start a retry index timer. As long as the timer is active, each retry will have a retry index included. The first retry will set the index to an initial value and subsequent retries will increment the value (for example, the initial value may be set to one with subsequent retries incrementing the value by 1).
  • the entity receiving a request (such as a PCRF or AAA, of which generally only one exists in an area accessible to a single UE) examines the request for a retry index.
  • the receiving entity starts a retry guard timer and as long as the timer is running, a higher retry index value (meaning a later attempt) can overwrite a request that has a lower retry index value or no retry index value.
  • Fig. 1 illustrates a wireless network 100 according to an embodiment of the present invention.
  • the network 100 comprises a number of base stations, implemented as eNBs 102 A and 102B, defining cells 104A and 104B, respectively.
  • the eNBs 102A and 102B receive services from a core network 108, which may comprise elements such as a mobility management entity (MME) 110, a serving gateway 111, packet gateways PGW-1, PGW-2, and PGW-3 (112, 114, and 116), a policy charging and rules function entity (PCRF) 118, and an authentication, authorization, and accounting entity (AAA) 120.
  • MME mobility management entity
  • PCRF policy charging and rules function entity
  • AAA authentication, authorization, and accounting entity
  • the core network 108 provides access to the Internet 124 and, through the Internet 124, to content such as that provided by content servers 126 and 128.
  • the various elements comprising the core network 108 perform functions to support services needed by the eNBs and the UEs, and external-facing elements of the core network (such as the SGW 111 and the PGWs 112, 114, and 116) receive and relay requests originating at the UEs or eNBs.
  • Elements of the core network 108 respond to service requests, such as Authorization requests, session establishment requests, call service requests, and numerous other types of requests originating at UEs and conveyed by network elements between the UEs and the core network 108, or originating at network elements between the UEs and the core network 108.
  • the core network 108 comprises redundant elements, and a response failure from one element may lead to a request to another element of the same type.
  • Requests within the core network 108 may originate at an originating node (such as the MME 110 and be passed to intermediate nodes such as the SGW 111 and PGWs 112-116.
  • the intermediate nodes prepare their own requests for the receiving or serving nodes 118 or 120.
  • Fig 2 illustrates a communication and operations diagram 200, showing various core network elements and operations and communications undertaken in supporting communication according to one or more embodiments of the present invention.
  • various elements may be thought of as originating nodes, intermediate nodes, and receiving or serving nodes.
  • the MME is an originating node, originating the initial request and directing this request and subsequent retries to intermediate nodes.
  • the PGWs are intermediate nodes, receiving requests from the MME and creating their own requests and sending these to the PCRF, which responds to the different requests.
  • the diagram 200 illustrates an originating node (MME 202), intermediate nodes (SGW 203, PGW-1 (204A), PGW-2 (204B), PGW-3 (204C)), and a receiving or serving node (PCRF 208).
  • the diagram 200 illustrates an unfulfilled request and subsequent retries by the MME 202, and the operations undertaken to avoid responding to outdated requests.
  • One or more core network elements use a retry index timer and a retry index as described above.
  • a UE attaches to the MME 202.
  • no retry index timer associated with this UE is running.
  • the MME 202 selects the PGW-1 (204A) and sends a CSReq to the SGW 203, so that the CSReq arrives at the PGW-1 (204A).
  • the PGW-1 (204A) is queues the request and is unable to process the request for some time, due to a heavy load.
  • the MME 202 times out and begins a retry procedure.
  • the MME 202 selects the PGW-2 (204B) and prepares a CSReq specifying the PGW2 (204B).
  • the request includes a retry index set to 1.
  • the MME 202 starts a retry index timer.
  • the PGW-2 (204B) processes the request normally and sends a CCR-I to the
  • the PCRF 208 creates a session that is bound to PGW-2 (204B).
  • the PCRF 208 notes that the request includes a retry index, and so starts a retry guard timer.
  • the PGW-2 (204B) sends a response, which is not received by the MME 202.
  • the MME 202 thus never receives the response, and determines that it needs to perform another retry, sending a request to the PGW-3 (204C).
  • the MME 202 selects the PGW-3 (204C) and (because the retry index timer is still active) sets the retry index to "2".
  • the MME 202 prepares a CSReq specifying the PGW-3 (204C) including the retry index set to "2", and sends it to the SGW 203 for relaying to the PGW-3 (204C).
  • the PGW-1 (204A) processes the CSReq and sends a CCR-I to the PCRF 208.
  • This CCR-I has no retry index value, and the PCRF 208 has already received a CCR-I including a retry index value of "1". Therefore, the new (to the PCRF 208) CCR-I from the PGW-1 (204A) is ignored.
  • the PCRF 208 receives the CCR-I from the PGW-3 (204C), with its retry index value of "3". Because this CCR-I has a higher retry index value than does the previously received CCR-I, the previously received CCR-I (with the retry index value of 1) is overwritten. The PCRF 208 then begins a session bound to the PGW-3 (204C).
  • Fig. 3 illustrates a process 300 according to one or more embodiments of the present invention, involving steps undertaken by an MME acting as an originating node, PGWs acting as intermediate nodes, and an PCRF acting as a receiving or serving node.
  • the MME selects a PGW-1 and sends a CSReq to an SGW, specifying the PGW-1.
  • the MME performs a retry, starting a retry index timer, setting a retry index to "1" and sending to the CSW a CSReq designated for a PGW-2.
  • the PGW-2 sends a CCR-I to a PCRF, with a retry index (set to 1) included, and sends a response to the MME.
  • the PCRF creates a session bound to the PGW-2 and (because the request includes a retry index) starts a retry guard timer.
  • the MME upon failure to detect the response from the PGW-2, the MME performs a retry.
  • the retry index timer has already been started, so the retry index is set to "2".
  • the MME sends to the CSW a CSReq designated for a PGW-3.
  • the PGW-3 sends a CCR-I to the PCRF, with a retry index (set to 2) included, and sends a response to the MME, which receives the response.
  • the PGW-1 sends a CCR-I to the PCRF, which ignores the CCR-I because the retry guard timer is running and the CCR-I lacks any retry index.
  • the PCRF receives the CCR-I from the PGW-3.
  • the CCR-I from the PGW-3 has a retry index of "2" which is higher than the retry index of "1" of the current CCR-I, so the PCRF overwrites the information stored from the CCR-I with the index value of 1 (previously received from the PGW-2) and binds a PCRF session to the PGW-3.
  • Fig. 4 illustrates a data processing element according to one or more embodiments of the present invention.
  • Data processing devices such as the device 400 may be used for various core network elements such as those described above.
  • the data processing device 400 includes processing means such as at least one data processor (DP) 402, storage such as at least one computer-readable memory (MEM) 404 storing data 406 and at least one computer program (PROG) 408 or other set of executable instructions.
  • processing means such as at least one data processor (DP) 402, storage such as at least one computer-readable memory (MEM) 404 storing data 406 and at least one computer program (PROG) 408 or other set of executable instructions.
  • DP data processor
  • MEM computer-readable memory
  • PROG computer program
  • At least one of the PROGs 408 in the data processing device 400 is assumed to include a set of program instructions that, when executed by the associated DP 402, enable the device to operate in accordance with the exemplary embodiments of this invention, as detailed above.
  • the exemplary embodiments of this invention may be implemented at least in part by computer software stored on the MEM 404, which is executable by the DP 402 of the data processing device 400, or by hardware, or by a combination of tangibly stored software and hardware (and tangibly stored firmware).
  • An electronic devices implementing these aspects of the invention need not be the entire devices as depicted at Figure4 or may be one or more components of same such as the above described tangibly stored software, hardware, firmware and DP, or a system on a chip SOC or an application specific integrated circuit ASIC.
  • the various embodiments of the data processing device can include, but are not limited to cellular network elements. These may include core network elements such as serving gateways, packet gateways, policy charging and rules function elements, mobility management entities, authentication, authorization and accounting entities, and numerous other types of core network elements.
  • core network elements such as serving gateways, packet gateways, policy charging and rules function elements, mobility management entities, authentication, authorization and accounting entities, and numerous other types of core network elements.
  • the new MME may be assigned a higher index value so that its requests will automatically take priority. For example, if a packet data network (PDN) connect request is received from a new MME after context request and response has been performed with an old MME, the higher index value of the new MME will lead to overwriting of any outstanding request (before the relocation procedure) with the new request.
  • PDN packet data network
  • a process comprises providing a core network element from which a request is being sent with information indicating the retry status of the request.
  • the information indicating the retry status comprises an indication of relative priority of the request.
  • the relative priority of the request is indicated by the presence or absence of a retry index number.
  • the relative priority of the request is indicated by the value of a retry index number.
  • a request with a retry index number takes priority over a request with no retry index number and a request with a higher retry index number takes priority over a request with a lower retry index number.
  • a request representing a retry initiates a retry index timer and relative priority is given to requests based on their retry status only during the pendency of the retry index timer.
  • a request with a lower retry status is ignored if a request with a higher retry status has been received.
  • a previously-received request with a lower retry status is discarded and overwritten if a request with a higher retry status is received.
  • an apparatus comprises at least one processor and memory storing a program of instructions.
  • the memory storing the program of instructions is configured to, with the at least one processor, cause the apparatus to at least, upon failure to receive a response to a prior request from a serving core network element, initiate a retry index timer, configure a new request including a retry index, and send the new request including the retry index to the serving core network element.
  • the new request is to a different core network element than the prior request.
  • the request is a call session request.
  • the call session request is sent to a designated packet gateway.
  • the apparatus is a mobility management entity.
  • an apparatus comprises at least one processor and memory storing a program of instructions.
  • the memory storing the program of instructions is configured to, with the at least one processor, cause the apparatus to at least, upon receiving a request from a requesting element, examine the request for retry status and, depending at least in part on a retry status of the request, determine whether or not to provide service based on the request.
  • determining whether or not to provide service based on the request comprises ignoring the request if it has a higher retry status than does a previously received request.
  • determining whether or not to provide service based on the request comprises discarding and overwriting a lower status request upon receiving a higher status request.
  • the request is a call session request.
  • the request comprises a credit control request initialization.
  • serving the request comprises creating a context for a user device designating a gateway element specified in the request.
  • examining and acting based on retry status of requests is carried out only during the pendency of a timer.
  • an apparatus comprises at least one processor and memory storing a program of instructions.
  • the memory storing the program of instructions is configured to, with the at least one processor, cause the apparatus to at least, upon receiving a request from an initiating device including a retry status indication, send a service request to a . serving device, wherein the service request includes a retry status request based on the received request.
  • the apparatus is a packet gateway, the received request is a call session request, and the service request is a credit control request initialization.
  • a method comprises, upon failure to receive a response to a prior request from a serving core network element, initiating a retry index timer, configure a new request including a retry index, and send the new request including the retry index to the serving core network element.
  • the new request is to a different core network element than the prior request.
  • the request is a call session request.
  • the call session request is sent to a designated packet gateway.
  • the method is performed by a mobility management entity.
  • a method comprises, upon receiving a request from a requesting element, examine the request for retry status and, depending at least in part on a retry status of the request, determining whether or not to provide service based on the request.
  • determining whether or not to provide service based on the request comprises ignoring the request if it has a higher retry status than does a previously received request.
  • determining whether or not to provide service based on the request comprises discarding and overwriting a lower status request upon receiving a higher status request.
  • the request comprises a credit control request initialization.
  • serving the request comprises creating a context for a user device designating a gateway element specified in the request.
  • examining and acting based on retry status of requests is carried out only during the pendency of a timer.
  • a method comprises, upon receiving a request from an initiating device including a retry status indication, sending a service request to a serving device, wherein the service request includes a retry status request based on the received request.
  • method is performed by a packet gateway, the received request is a call session request, and the service request is a credit control request initialization.
  • a non-transitory computer readable medium stores a program of instructions. Execution of the program of instructions by a processor configures an apparatus to at least, upon failure to receive a response to a prior request from a serving core network element, initiate a retry index timer, configure a new request including a retry index, and send the new request including the retry index to the serving core network element.
  • the new request is to a different core network element than the prior request.
  • the request is a call session request.
  • the call session request is sent to a designated packet gateway.
  • the apparatus is a mobility management entity.
  • a non-transitory computer readable medium stores a program of instructions. Execution of the program of instructions by a processor configures an apparatus to at least, upon receiving a request from a requesting element, examine the request for retry status and, depending at least in part on a retry status of the request, determine whether or not to provide service based on the request.
  • determining whether or not to provide service based on the request comprises ignoring the request if it has a higher retry status than does a previously received request.
  • determining whether or not to provide service based on the request comprises discarding and overwriting a lower status request upon receiving a higher status request.
  • the request is a call session request. In another embodiment of the invention, the request comprises a credit control request initialization.
  • serving the request comprises creating a context for a user device designating a gateway element specified in the request.
  • examining and acting based on retry status of requests is carried out only during the pendency of a timer.
  • a non-transitory computer readable medium stores a program of instructions. Execution of the program of instructions by a processor configures an apparatus to at least, upon receiving a request from an initiating device including a retry status indication, send a service request to a serving device, wherein the service request includes a retry status request based on the received request.
  • the apparatus is a packet gateway, the received request is a call session request, and the service request is a credit control request initialization.

Landscapes

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

Abstract

L'invention concerne des systèmes et des techniques pour gérer des demandes de service pour des éléments de communication de réseau sans fil, de façon à empêcher des conflits et une confusion entre une demande envoyée précédemment et une demande réessayée envoyée en raison d'un échec de réception d'une réponse à la demande envoyée précédemment. Un élément d'initiation, lors de la détermination du fait qu'une demande de service envoyée précédemment n'a pas été reçue, configure un indicateur d'état de ré-essai et envoie une demande de service réessayée à un élément de réseau principal de desserte du réseau de communication sans fil, la demande de service réessayée comprenant l'indicateur d'état de ré-essai. Un élément de desserte, lors de la réception d'une demande de service, examine la demande de service pour déterminer si la demande de service comprend ou non un indicateur d'état de ré-essai et détermine s'il faut ou non fournir un service sur la base du point de savoir si la demande de service comprend ou non un indicateur d'état de ré-essai.
PCT/US2015/028697 2014-05-01 2015-05-01 Procédés et appareil de gestion de temporisation WO2015168494A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201461987132P 2014-05-01 2014-05-01
US61/987,132 2014-05-01

Publications (1)

Publication Number Publication Date
WO2015168494A1 true WO2015168494A1 (fr) 2015-11-05

Family

ID=54359359

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/028697 WO2015168494A1 (fr) 2014-05-01 2015-05-01 Procédés et appareil de gestion de temporisation

Country Status (1)

Country Link
WO (1) WO2015168494A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018014152A1 (fr) * 2016-07-18 2018-01-25 华为技术有限公司 Procédé de gestion de déconnexion anormale de réseau central, et terminal

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100030880A1 (en) * 2008-07-29 2010-02-04 International Business Machines Corporation Failover in proxy server networks
US20100312846A1 (en) * 2008-01-25 2010-12-09 Zte Corporation Method for releasing buffered data of a serving gateway
US20120039167A1 (en) * 2010-08-10 2012-02-16 Qualcomm Incorporated System, apparatus, and method for improving redial performance in wireless communication systems
US20120281566A1 (en) * 2011-04-01 2012-11-08 Interdigital Patent Holdings, Inc. Method and apparatus for controlling connectivity to a network
US8578035B2 (en) * 2010-09-27 2013-11-05 Telefonaktiebolaget Lm Ericsson (Publ) Technique for relocating a serving gateway associated to a user equipment

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100312846A1 (en) * 2008-01-25 2010-12-09 Zte Corporation Method for releasing buffered data of a serving gateway
US20100030880A1 (en) * 2008-07-29 2010-02-04 International Business Machines Corporation Failover in proxy server networks
US20120039167A1 (en) * 2010-08-10 2012-02-16 Qualcomm Incorporated System, apparatus, and method for improving redial performance in wireless communication systems
US8578035B2 (en) * 2010-09-27 2013-11-05 Telefonaktiebolaget Lm Ericsson (Publ) Technique for relocating a serving gateway associated to a user equipment
US20120281566A1 (en) * 2011-04-01 2012-11-08 Interdigital Patent Holdings, Inc. Method and apparatus for controlling connectivity to a network

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018014152A1 (fr) * 2016-07-18 2018-01-25 华为技术有限公司 Procédé de gestion de déconnexion anormale de réseau central, et terminal
CN108605035A (zh) * 2016-07-18 2018-09-28 华为技术有限公司 核心网异常挂断的处理方法和终端
US10841968B2 (en) 2016-07-18 2020-11-17 Huawei Technologies Co., Ltd. Method for processing abnormal core network disconnection and terminal
CN108605035B (zh) * 2016-07-18 2021-07-30 荣耀终端有限公司 核心网异常挂断的处理方法和终端

Similar Documents

Publication Publication Date Title
US10652945B2 (en) Mobile terminated call improvements
US9668293B2 (en) Relocation of mobility anchor for nomadic subscribers
EP2192728A1 (fr) Procédé, système et dispositif pour accueillir l'adressage de l'adresse ip statique d'utilisateur dans un système d'évolution à long terme
US20130044608A1 (en) Node and method for signalling in a proxy mobile internet protocol based network
US8190149B2 (en) Dynamic GGSN relocation in a GPRS network
US11696358B2 (en) Methods and nodes for handling bearers
WO2011157166A2 (fr) Procédé de traitement de restauration de service et élément de réseau de gestion de mobilité
US10015834B2 (en) Apparatus, device, and method for establishing connection to packet data network
US9893899B2 (en) Network connection re-establishment method, related device and system
US11381453B2 (en) Method and system for service software upgrade in an evolved packet core (EPC) system
WO2016119262A1 (fr) Procédé de reprise sur sinistre de service, dispositif associé et système de communication
WO2017202305A1 (fr) Procédé de gestion de connexion pour la transmission de petites données, entité scef, mme, et ue
KR101889588B1 (ko) 피엠아이피브이6 엠에이지 복원
EP2346219A1 (fr) Procédé de traitement d échec de reconstruction de charge
WO2015168494A1 (fr) Procédés et appareil de gestion de temporisation
WO2011127861A2 (fr) Procédé de traitement de défaillance d'équipement de réseau et équipement de passerelle de réseau de données par paquets
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
WO2014090011A1 (fr) Procédé d'initiation de signalisation, appareil et dispositif passerelle
US10904133B2 (en) Data packet sending method, mobile router, and network device
US20160337237A1 (en) Data Packet Sending Method and Mobile Router

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

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

Country of ref document: EP

Kind code of ref document: A1