WO2017079926A1 - Procédé et appareil de restauration de service - Google Patents

Procédé et appareil de restauration de service Download PDF

Info

Publication number
WO2017079926A1
WO2017079926A1 PCT/CN2015/094345 CN2015094345W WO2017079926A1 WO 2017079926 A1 WO2017079926 A1 WO 2017079926A1 CN 2015094345 W CN2015094345 W CN 2015094345W WO 2017079926 A1 WO2017079926 A1 WO 2017079926A1
Authority
WO
WIPO (PCT)
Prior art keywords
mme
mobile subscriber
paging
message
hss
Prior art date
Application number
PCT/CN2015/094345
Other languages
English (en)
Inventor
Xiaotang XIE
Weixing Wang
Pengle WANG
Lihong Zhang
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
Priority to PCT/CN2015/094345 priority Critical patent/WO2017079926A1/fr
Publication of WO2017079926A1 publication Critical patent/WO2017079926A1/fr

Links

Images

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
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • 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/06—Registration at serving network Location Register, VLR or user mobility server
    • H04W8/065—Registration at serving network Location Register, VLR or user mobility server involving selection of the user mobility server

Definitions

  • the non-limiting and exemplary embodiments of the present disclosure generally relate to the communications field, and specifically to a method, an apparatus, and a computer program product for network triggered service restoration.
  • Evolved Packet System presents the EPS evolution of the 3rd Generation (3G) /Universal Mobile Telecommunications System (UMTS) standard introduced by the 3rd Generation Partnership Project (3GPP) standard committee.
  • a User Equipment UE
  • EPC Evolved Packet Core
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • P-GW Public Data Network Gateway
  • the P-GW may interact with a Policy and Charging Rules Function (PCRF) .
  • the EPC may comprise the S-GW, P-GW, HSS, and PCRF.
  • the EPC network is required to have a service restoration capability, such as network triggered service restoration (NTSR) functionality.
  • NTSR network triggered service restoration
  • the network triggered service restoration procedure is an optional feature for MME, S4-Serving GPRS (General Packet Radio Service) Support Node (S4-SGSN) and S-GW. Some requirements shall apply if the MME, S4-SGSN and S-GW support this feature.
  • MME General Packet Radio Service
  • S4-SGSN General Packet Radio Service Support Node
  • the S-GW upon receipt of a first downlink user plane or control plane packet on a maintained S5/S8 bearer or PCC signaling from PCRF, the S-GW shall immediately send a Downlink Data Notification (DDN) message including the International Mobile Subscriber Identification Number (IMSI) to the respective MME or S4-SGSN.
  • DDN Downlink Data Notification
  • IMSI International Mobile Subscriber Identification Number
  • the S-GW may send the DDN message to another MME or S4-SGSN (the same type of mobility node as the failed one) located in the same pool as the failed node if the S-GW cannot send it to the failed MME or S4-SGSN (e.g. because it did not restart) .
  • an S-GW becomes aware that an MME/S4-SGSN has failed and has not restarted.
  • the MME or S4-SGSN upon receipt of a DDN message including the IMSI, the MME or S4-SGSN shall respond to the SGW with a DDN Acknowledge (Ack) message and should page and force the UE identified by the IMSI to re-attach to the network.
  • the paging area and subscriber′s identity i.e. IMSI or SAE (System Architecture Evolution) -Temporary Mobile Subscriber Identity (S-TMSI) /Packet Temporary Mobile Subscriber Identity (P-TMSI) used during the paging procedure are implementation dependent.
  • IMSI or SAE System Architecture Evolution
  • S-TMSI System Architecture Evolution
  • P-TMSI Packet Temporary Mobile Subscriber Identity
  • the UE may start a reattach procedure as specified in subclause 5.6.2.2.2 of 3GPP TS 24.301 V13.3.0 and subclause 4.7.9.1.2 of 3GPP TS 24.008 V13.3.0 by sending an Attach Request with the IMSI.
  • the attach procedure is specified in clause 5.3.2 of 3GPP TS 23.401 V13.4.0.
  • the attach procedure as illustrated in Figure 5.3.2.1-1 of 3GPP TS 23.401 is represented in FIG. 1 for better understanding of the present disclosure. Detailed description of the attach procedure can be found in 3GPP TS 23.401, which thus will not be repeated herein for the purpose of conciseness, except for operations numbered 8 and 9 as shown in FIG. 1.
  • the MME may send an Update Location Request (ULR) (MME Identity, IMSI, Mobile Entity (ME) Identity, MME Capabilities, ULR-Flags) message to the HSS.
  • the HSS may send Cancel Location (IMSI, Cancellation Type) to the old MME.
  • the old MME acknowledges with Cancel Location Ack (IMSI) and removes the Mobility Management (MM) and bearer contexts.
  • An MME is a key control plane node in an EPC network. Once the MME fails, a big loss may occur in the whole network and it usually takes a long time to recover, thereby deteriorating user’s experience. Accordingly, a concept of MME pool is proposed in 3GPP to improve system robustness.
  • An MME pool refers to an area comprised of one or more MMEs, usually more than three MMEs. Each eNodeB under the MME pool may be connected to every MME in the MME pool and each UE under the MME pool may be attached to any MME in the MME pool.
  • FIG. 2 shows an exemplary network organized with an MME pool and multiple S-GWs.
  • the MME pool comprises three MMEs, i.e. MME-1, MME-2 and MME-3. It is assumed that both MME and S-GW support NTSR procedure as specified in clause 25 of 3GPP TS 23.007 V13.2.0.
  • MME serving the UE i.e. MME-1 fails or S11 interface between S-GW-1 and MME-1 is broken, and meanwhile downlink data arrives at S-GW-1
  • S-GW-1 will then send a DDN message with the IMSI of the UE to another MME, e.g. MME-2 in the MME pool.
  • MME-2 This will trigger MME-2 to initiate paging with the IMSI to force the UE to re-attach to the network, in the case that S-TMSI is not available due to the network failure.
  • the UE Upon receiving a paging message with the IMSI, the UE initiates the reattach procedure by sending an Attach Request including the IMSI to its serving eNB. Then the eNB will select an MME in the MME Pool based on a known MME selection mechanism for the UE to attach so that the connection failure to MME-1 may be recovered.
  • the eNB may select a new MME, e.g. MME-3 other than the one who initiates the paging with the IMSI (which will be referred to as IMSI paging hereafter) for the UE to attach.
  • MME initiating the IMSI paging i.e. MME-2
  • MME-3 the MME initiating the IMSI paging
  • MME-2 doesn′t know that the UE has attached to MME-3, it will continue the IMSI paging, which may cause the UE to detach and re-attach repeatedly.
  • 3GPP does not specify how to avoid this repeated attach procedure with the MME pool being configured. In the worst case, this problem may be neglected when the repeated IMSI paging is stopped due to a paging attempt threshold is reached, as it usually happens in practical implementations.
  • FIG. 3 illustrates an interactive message flow of an existing network triggered service restoration procedure for the exemplary network of FIG. 2.
  • MME-2 initiates paging towards the UE using the IMSI at operation 1.
  • the UE sends an attach request to the eNB.
  • the eNB selects MME-3 for the UE to attach at operation 3.
  • MME-2 has no way to find out that the UE has attached to MME-3. Therefore, even though the UE is successfully attached to MME-3, MME-2 will initiate paging again at operation 5 using the IMSI.
  • MME-2 will keep paging the UE until a paging attempt threshold is reached. In this case, if the data to be transmitted is voice data, the user may experience a call drop, even though the voice service may continue via MME-3.
  • the call drop rate may be increased heavily. Also, it may trigger a signaling storm in EPC and IP Multimedia Subsystem (IMS) network in peak hours.
  • IMS IP Multimedia Subsystem
  • a method performed at a first mobility management entity, MME in an MME pool for network triggered service restoration comprises, upon receipt of a downlink data notification message including a permanent identity of a mobile subscriber from a serving gateway that has detected a connection failure to a second MME serving the mobile subscriber in the MME pool, sending a first message for requesting location update to a home subscriber server, HSS associated with the mobile subscriber and paging with the permanent identity of the mobile subscriber so that an attach procedure is initiated at the mobile subscriber in response to the paging.
  • the first message includes at least information indicative of the permanent identity of the mobile subscriber and information indicative of an identity of the first MME.
  • the method may further comprise stopping the paging in response that a second message from which information regarding attachment of the mobile subscriber to a third MME in the MME pool can be derived is received from the HSS.
  • the second message may be generated at the HSS based at least partially on information for a serving MME of the mobile subscriber that has been updated with the information included in the first message.
  • an apparatus at a first mobility management entity, MME in an MME pool for network triggered service restoration comprises a location update requesting unit and a paging unit.
  • the location update requesting unit is configured to, upon receipt of a downlink data notification message including a permanent identity of a mobile subscriber from a serving gateway that has detected a connection failure to a second MME serving the mobile subscriber in the MME pool, send a first message for requesting location update to a home subscriber server, HSS associated with the mobile subscriber.
  • the paging unit is configured to, upon receipt of said downlink data notification message, page with the permanent identity of the mobile subscriber so that an attach procedure is initiated at the mobile subscriber in response to the paging.
  • the first message includes at least information indicative of the permanent identity of the mobile subscriber and information indicative of an identity of the MME.
  • the apparatus may further comprise a paging stopping unit that is configured to stop the paging in response that a second message from which information regarding attachment of the mobile subscriber to a third MME in the MME pool can be derived is received from the HSS.
  • the second message may be generated at the HSS based at least partially on information for a serving MME of the mobile subscriber that has been updated with the information included in the first message.
  • an apparatus that may be embodied at or as a part of a mobility management entity in an MME pool.
  • the apparatus comprises a processor and a memory.
  • the memory containing instructions executable by the processor, whereby the apparatus is operative to perform the method according to the first aspect of the present disclosure.
  • a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to the first aspect of the present disclosure.
  • FIG. 1 represents an attach procedure as illustrated in Figure 5.3.2.1-1 of 3GPP TS 23.401;
  • FIG. 2 shows an exemplary network organized with an MME pool and multiple S-GWs
  • FIG. 3 illustrates an interactive message flow of an existing network triggered service restoration procedure for the exemplary network of FIG. 2;
  • FIG. 4 illustrates a flowchart of a method for restoring services according to an embodiment of the present disclosure
  • FIG. 5 illustrates an exemplary message flow of the method of FIG. 4 according to the embodiment that the first MME stops the paging in response that the second message is received;
  • FIG. 6 illustrates an exemplary message flow of the method of FIG. 4 according to the embodiment that the first MME stops the paging in response that an attach request is received from the mobile subscriber;
  • FIG. 7 illustrates an exemplary message flow of the method of FIG. 4 according to the embodiment that the first MME stops the paging in response that a preset paging threshold is reached;
  • FIG. 8 illustrates a schematic structure of an apparatus for restoring services according to an embodiment of the present disclosure.
  • FIG. 9 illustrates a schematic structure of another apparatus for restoring services according to an embodiment of the present disclosure.
  • references in the specification to “an embodiment, ” “another embodiment, ” “yet another embodiment, ” etc. indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the listed terms in association.
  • FIG. 4 illustrates a flowchart of a method 400 performed at a mobility management entity, MME (which will be referred to as a first MME) in an MME pool for restoring services for a mobile subscriber according to an embodiment of the present disclosure, when a connection failure to the MME (which will be referred to as a second MME) serving the mobile subscriber is detected by a S-GW currently serving the mobile subscriber.
  • the connection failure to the second MME may be caused by, for example, a hardware or software failure of the second MME, restart of the second MME or S11 interface between the S-GW and the second MME being broken.
  • the S-GW detects the connection failure to the serving MME (i.e. the second MME)
  • the S-GW will send a Downlink Data Notification, DDN message including a permanent identity of the mobile subscriber, e.g. IMSI, to another MME (e.g. the first MME in this embodiment) located in the same MME pool as the failed MME, i.e. the second MME.
  • a permanent identity of the mobile subscriber e.g. IMSI
  • the first MME Upon receipt of the DDN message including the permanent identity of the mobile subscriber from the S-GW that has detected the connection failure to the second MME, at block 410, the first MME sends a message for requesting location update (which will be referred to as a first message hereafter) to a home subscriber server, HSS associated with the mobile subscriber.
  • HSS home subscriber server
  • the term “associated” used herein means that the HSS may maintain data or information related to the UE, for example subscription data of the UE.
  • Information for a serving MME of the mobile subscriber may be maintained as a part of the subscription data of the mobile subscriber at the HSS.
  • the first message comprises at least information indicative of the permanent identity of the mobile subscriber and information indicative of an identity of the first MME.
  • the HSS may update the maintained information for the serving MME of the mobile subscriber with the information included in the first message. For example, before the HSS receives the first message, the identity of the serving MME maintained at the HSS identifies the failed MME, i.e. the second MME. Once the HSS receives the firs message for requesting location update, the HSS will replace the identity of the serving MME with the identity of the first MME who requests the location update.
  • the first message may be of the form of Update Location Request, URL as used in the attach procedure specified in clause 5.3.2 of 3GPP TS 23.401 V13.4.0.
  • the first message may preferably only include some mandatory parameters like IMSI, ULR Flags, Visited Public Land Mobile Network (PLMN) Identity, Radio Access Technology (RAT) Type, in addition to information indicative of the identity of the first MME. Additionally, the ULR Flags may be set to skip Subscription Data, SD so as to avoid unnecessary load on the S6a interface.
  • the first message plays the same or similar role as the ULR does in the attach procedure as specified in clause 5.3.2 of 3GPP TS 23.401 V13.4.0, depending on the information included in the first message. Therefore, in response to receipt of the first message, the HSS will also send an acknowledge message to the first MME.
  • the acknowledge message may be of the form of Update Location Ack, ULA as used in the attach procedure specified in clause 5.3.2 of 3GPP TS 23.401 V13.4.0, which will not be detailed herein for the purpose of conciseness.
  • the HSS may further send a message for requesting cancel location to the failed MME, i.e. the second MME. This message for requesting cancel location may be of the form of Cancel Location Request as used in the attach procedure specified in clause 5.3.2 of 3GPP TS 23.401 V13.4.0, which will not be detailed herein for the purpose of the conciseness.
  • the first MME pages with the permanent identity of the mobile subscriber so that an attach procedure is initiated at the mobile subscriber in response to the paging.
  • the mobile subscriber may initiate the attach procedure as specified in clause 5.3.2 of 3GPP TS 23.401 V13.4.0 by sending an attach request towards an MME other than the failed second MME in the MME pool.
  • the first MME may stop the paging in response that a second message from which information regarding attachment of the mobile subscriber to a third MME in the MME pool can be derived is received from the HSS at block 430.
  • the second message may be generated at the HSS based at least partially on information for a serving MME of the mobile subscriber that has been updated with the information included in the first message.
  • the second message may be a cancel location request message from the HSS, which may be received in response that the third MME has sent an Update Location Request to the HSS during the attach procedure for attachment of the mobile subscriber to the third MME.
  • FIG. 5 illustrates an exemplary message flow of the method 400 according to the embodiment that the first MME stops the paging in response that the second message is received.
  • the UE corresponds to the mobile subscriber of the method 400; MME-1 is serving the UE before it fails and corresponds to the second MME of the method 400; MME-2 corresponds to the first MME of the method 400; MME-3 corresponds to the third MME.
  • the S-GW detects the failure of MME-1, while a downlink data arrives at the S-GW. Accordingly, the S-GW sends a DDN message including the IMSI of the UE to MME-2 located in the same MME pool as MME-1.
  • MME-2 Upon receipt of the DDN message including the IMSI from the S-GW, on one hand, MME-2 sends to the S-W a DDN Ack message to confirm the receipt of the DDN message; and on the other hand, MME-2 sends a message for requesting location update to an HSS associated with the UE. Then, the HSS may perform a location update process with the message for requesting location update so that information for a serving MME of the mobile subscriber is updated at the HSS with information included in the message for requesting location update. Then the HSS sends a message for acknowledging the location update to MME-2. Furthermore, the HSS sends a cancel location request message to MME-1.
  • MME-2 initiates paging towards the UE using the IMSI obtained from the DDN message. For example, MME-2 may send a paging request to all connected eNBs in tracking areas of the UE. Then the eNB serving the UE may page the UE.
  • the UE may initiate an attach procedure to an MME other than the failed MME-1 in the same MME pool.
  • the serving eNB selects an MME different from MME-2, i.e. MME-3 for the UE to attach.
  • the UE then initiates an attach procedure to MME-3 by sending an attach request towards MME-3.
  • a normal attach procedure as specified in 3GPP TS 23.401 V13.4.0 may be performed to MME-3.
  • the HSS will send a Cancel Location Request, CLR to MME-2, since the currently maintained identity of the serving MME at the HSS is MME-2.
  • the CLR may be generated at the HSS according to existing 3GPP specifications, e.g. 3GPP TS 23.401 V13.4.0, which thus will not be detailed herein.
  • MME-2 Upon receipt of the CLR from the HSS, MME-2 knows that the UE has initiated attach to or attached to another MME in the MME pool and then stops the paging towards the UE.
  • the MME which initiates paging towards the UE can have an opportunity to get timely knowledge that the UE has initiated attach to or attached to another MME in the same MME pool so that the MME can stop the paging in time to avoid unnecessary and excessive paging, detaching, re-attaching procedures, thereby decreasing the call drop rate and improving user experience.
  • the first MME may stop the paging in response to receiving an attach request from the mobile subscriber at block 430.
  • FIG. 6 illustrates an exemplary message flow of the method 400 according to the embodiment that the first MME stops the paging in response that an attach request is received from the mobile subscriber.
  • the UE corresponds to the mobile subscriber of the method 400; MME-1 is serving the UE before it fails and corresponds to the second MME of the method 400; and MME-2 corresponds to the first MME of the method 400.
  • the difference between embodiments of FIGs. 5 and 6 lies in that the serving eNB selects MME-2 for the UE to attach. Due to this difference, the UE will send an attach request towards MME-2. Once MME-2 receives the attach request, it may immediately know that the UE has initiated an attach procedure. Since MME-2 itself is the MME which initiates the paging, MME-2 can stop the paging in response to the receipt of the attach request.
  • MME-2 also needs to send a ULR to the HSS, the HSS will confirm the receipt of the ULR by sending back a ULA. However, since the currently maintained identity of the serving MME at the HSS is MME-2, no cancel location request will be sent from the HSS to MME-2.
  • the first MME may stop the paging in response that a preset paging threshold is reached at block 430.
  • FIG. 7 illustrates an exemplary message flow of the method 400 according to the embodiment that the first MME stops the paging in response that a preset paging threshold is reached.
  • a paging threshold may be preset for the first MME. All paging processes will be attempted within the limit of the paging threshold.
  • This paging threshold may be a paging timer, which is started when the first paging is initiated. Alternatively, this paging threshold may be a maximum number of paging attempts.
  • the first MME may send a purging message to the HSS at block 440 and additionally delete information associated with the mobile subscriber at the first MME at block 450. Responsive to the purging message, information associated with the first MME may be removed from the HSS.
  • MME-2 may stop the paging in response that the preset paging threshold is reached, for example the preset paging timer expires or the preset maximum number of paging attempts is reached. Additionally, MME-2 may send a purging message to the HSS. Responsive to the purging message, information associated with the first MME may be removed from the HSS. For example, the identity of the first MME will be removed from being the identity of the serving MME as maintained at the HSS. As a response, the HSS may send a purging acknowledgement message to MME-2.
  • MME-2 may delete information associated with the mobile subscriber.
  • FIG. 7 may be combined with the embodiment of FIG. 5 or 6. That means, in the embodiment of FIG. 5 or 6, a paging threshold may also be set in advance. All paging attempts will be performed within the limit of the paging threshold. Before the paging threshold is reached, paging may possibly be stopped in response to receipt of the second message from the HSS or the attach request from the mobile subscriber; otherwise, the paging will be stopped in response that the paging threshold is reached.
  • FIG. 8 illustrates a schematic block diagram of an apparatus 800 that may be embodied at or as a part of a mobility management entity, MME (which will be referred to as a first MME) in an MME pool for restoring services for a mobile subscriber according to an embodiment of the present disclosure, when a connection failure to the MME (which will be referred to as a second MME) serving the mobile subscriber is detected by a S-GW currently serving the mobile subscriber.
  • the connection failure to the MME may be caused by, for example, a hardware or software failure of the MME, restart of the MME or S11 interface between the S-GW and the MME being broken.
  • the apparatus 800 comprises a location update requesting unit 810 and a paging unit 820.
  • the location update requesting unit 810 is configured to, upon receipt of a downlink data notification message including a permanent identity of a mobile subscriber, e.g. IMSI, from a serving gateway that has detected a connection failure to a second MME serving the mobile subscriber in the MME pool, send a first message for requesting location update to a home subscriber server, HSS associated with the mobile subscriber.
  • the paging unit 820 is configured to, upon receipt of said downlink data notification message, page with the permanent identity of the mobile subscriber so that an attach procedure is initiated at the mobile subscriber in response to the paging.
  • the first message includes at least information indicative of the permanent identity of the mobile subscriber and information indicative of an identity of the first MME. Additionally, the message for requesting location update may further include information indicative of skipping subscription data.
  • the apparatus 800 may also comprise a paging stopping unit 830.
  • the paging stopping unit 830 may be configured to stop the paging in response that a second message from which information regarding attachment of the mobile subscriber to a third MME in the MME pool can be derived is received from the HSS.
  • the second message is generated at the HSS based at least partially on information for a serving MME of the mobile subscriber that has been updated with the information included in the first message.
  • the second message may be a cancel location request message from the HSS.
  • the paging stopping unit 830 may be configured to stop the paging in response to receiving an attach request from the mobile subscriber.
  • the apparatus 800 may further comprise a purging unit 840.
  • the paging stopping unit 830 may be configured to stop the paging in response that a preset paging threshold is reached. That the preset paging threshold is reached may comprise a preset paging timer expiring since the preset paging timer was started at the first paging or a preset maximum number of paging attempts being reached.
  • the purging unit 840 may be configured to send a purging message to the HSS, responsive to which information associated with the first MME is removed from the HSS.
  • the apparatus 800 may further comprise a deleting unit 850 that may be configured to delete information associated with the mobile subscriber at the first MME.
  • units 810-850 may be configured to implement corresponding operations or steps in blocks 410-450 of FIG. 4 and to achieve corresponding technical effects as described with reference to FIG. 4-7. Thus, units 810-850 of FIG. 8 will not be detailed herein for the purpose of succinctness.
  • FIG. 9 illustrates a schematic block diagram of an apparatus 900 embodied at or as a part of a mobility management entity, MME in an MME pool for restoring services for a mobile subscriber according to an embodiment of the present disclosure, when a failure of the MME serving the mobile subscriber is detected by a S-GW currently serving the mobile subscriber.
  • the apparatus 900 comprises at least one processor 910, such as a data processor (DP) and at least one memory (MEM) 920 coupled to the processor 910.
  • the apparatus 900 may further comprise a transmitter TX and receiver RX 930 coupled to the processor 910 for establishing communications with other network nodes.
  • the MEM 920 stores a program (PROG) 940.
  • the PROG 940 may include instructions that, when executed on the associated processor 910, enable the apparatus 900 to operate in accordance with the embodiments of the present disclosure, for example to perform the method 400.
  • a combination of the at least one processor 910 and the at least one MEM 920 may form processing means 950 adapted to implement some embodiments of the present disclosure.
  • the MEM 920 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples.
  • the processors 910 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors DSPs and processors based on multicore processor architecture, as non-limiting examples.
  • the present disclosure may also provide a carrier containing the computer program as mentioned above, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • the computer readable storage medium can be, for example, an optical compact disk or an electronic memory device like a RAM (random access memory) , a ROM (read only memory) , Flash memory, magnetic tape, CD-ROM, DVD, Blue-ray disc and the like.
  • an apparatus implementing one or more functions of a corresponding apparatus described with an embodiment comprises not only prior art means, but also means for implementing the one or more functions of the corresponding apparatus described with the embodiment and it may comprise separate means for each separate function, or means that may be configured to perform two or more functions.
  • these techniques may be implemented in hardware (one or more apparatuses) , firmware (one or more apparatuses) , software (one or more modules) , or combinations thereof.
  • firmware or software implementation may be made through modules (e.g., procedures, functions, and so on) that perform the functions described herein.

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 procédé mis en œuvre au niveau d'une première entité de gestion de mobilité, MME, dans un pool de MME. Ledit procédé consiste, dès réception d'un message de notification de données de liaison descendante comprenant une identité permanente d'un abonné mobile en provenance d'une passerelle de service qui a détecté un incident de connexion à une seconde MME desservant l'abonné mobile dans le pool de MME, à envoyer un premier message de demande de mise à jour de localisation à un serveur HSS associé à l'abonné mobile et à rechercher l'identité permanente de l'abonné mobile de sorte qu'une procédure de rattachement soit lancée au niveau de l'abonné mobile en réponse à la recherche. Le premier message comprend au moins des informations indiquant l'identité permanente de l'abonné mobile et des informations indiquant une identité de la première MME. Par conséquent, l'invention concerne également un appareil mis en œuvre au niveau d'une MME dans un pool de MME, ou faisant partie de celle-ci, pour la restauration de service.
PCT/CN2015/094345 2015-11-11 2015-11-11 Procédé et appareil de restauration de service WO2017079926A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/094345 WO2017079926A1 (fr) 2015-11-11 2015-11-11 Procédé et appareil de restauration de service

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/094345 WO2017079926A1 (fr) 2015-11-11 2015-11-11 Procédé et appareil de restauration de service

Publications (1)

Publication Number Publication Date
WO2017079926A1 true WO2017079926A1 (fr) 2017-05-18

Family

ID=58694700

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/094345 WO2017079926A1 (fr) 2015-11-11 2015-11-11 Procédé et appareil de restauration de service

Country Status (1)

Country Link
WO (1) WO2017079926A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR3075527A1 (fr) * 2017-12-14 2019-06-21 Renault S.A.S. Methode et dispositif pour gestion de transfert de donnees ameliorant le debit
WO2020047855A1 (fr) * 2018-09-07 2020-03-12 Telefonaktiebolaget Lm Ericsson (Publ) Procédés et appareils de rétablissement de service déclenché par le réseau

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130188474A1 (en) * 2010-09-08 2013-07-25 Huawei Technologies Co., Ltd. Paging processing method and system, serving gateway
CN103329594A (zh) * 2010-11-14 2013-09-25 瑞典爱立信有限公司 移动性管理实体池的电路交换回退寻呼
US20140219178A1 (en) * 2012-01-20 2014-08-07 Verizon Patent And Licensing Inc. Optimizing user device context for mobility management entity (mme) resiliency

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130188474A1 (en) * 2010-09-08 2013-07-25 Huawei Technologies Co., Ltd. Paging processing method and system, serving gateway
CN103329594A (zh) * 2010-11-14 2013-09-25 瑞典爱立信有限公司 移动性管理实体池的电路交换回退寻呼
US20140219178A1 (en) * 2012-01-20 2014-08-07 Verizon Patent And Licensing Inc. Optimizing user device context for mobility management entity (mme) resiliency

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR3075527A1 (fr) * 2017-12-14 2019-06-21 Renault S.A.S. Methode et dispositif pour gestion de transfert de donnees ameliorant le debit
WO2020047855A1 (fr) * 2018-09-07 2020-03-12 Telefonaktiebolaget Lm Ericsson (Publ) Procédés et appareils de rétablissement de service déclenché par le réseau
US11582825B2 (en) 2018-09-07 2023-02-14 Telefonaktiebolagget LM Ericsson (Publ) Methods and apparatuses for network triggered service restoration

Similar Documents

Publication Publication Date Title
US9763281B2 (en) Communication method, mobile network system and device
JP6063530B2 (ja) 障害のあるサービング・ゲートウェイを介した接続の再配置及び復元並びにトラフィック・オフローディングのための方法及び装置
RU2569361C1 (ru) Система мобильной связи, sgw, способ связи в терминале и способ управления
KR101339044B1 (ko) 서빙 코어 네트워크 노드가 변경될 때의 모바일 장치의 접근성의 처리
US10477610B2 (en) Data transmission method, access network device, and communication system
KR101503762B1 (ko) 페이징 프로세스 방법 및 시스템, 서빙 게이트웨이
EP2836917B1 (fr) Procédé et appareil servant à effectuer une commande de surcharge pour une récupération hss
US9491732B2 (en) Paging processing method, user equipment and system
US20170195926A1 (en) Control node, network node, and methods performed therein
WO2012146747A1 (fr) Améliorations d'appel aboutissant à un mobile
US20140321365A1 (en) Mobile communication network system, communication control method, non-transitory computer readable medium storing program therefor
RU2543945C1 (ru) Способ мобильной связи, узел управления мобильными устройствами и устройство обслуживающего шлюза
WO2018053691A1 (fr) Procédé et appareil de rétablissement d'un service dans un système de communication sans fil
JP6195318B2 (ja) 移動通信システムにおける端末への着信処理方法
EP3758425A1 (fr) Appareil et procédé de recherche dans un système de communication sans fil
US10506486B2 (en) Wireless terminal and method of operating
US20120172066A1 (en) Communication method, mobile network system and device
WO2012016546A1 (fr) Procédé de traitement de radiomessagerie destiné à un équipement utilisateur et équipement
WO2017079926A1 (fr) Procédé et appareil de restauration de service
WO2017028637A1 (fr) Procédé et dispositif de traitement destinés à la récupération de passerelle
US20120178479A1 (en) Communication method, mobile network system and device
JP5896083B1 (ja) 移動通信システム、ｓｇｗ、移動通信システムの着信方法、及びｓｇｗの着信方法
CN111757401A (zh) 一种网关选择系统及方法

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

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

Country of ref document: EP

Kind code of ref document: A1