WO2014082572A1 - Procédé et dispositif de rapport d'informations de capacité dans un scénario de pool de mme - Google Patents

Procédé et dispositif de rapport d'informations de capacité dans un scénario de pool de mme Download PDF

Info

Publication number
WO2014082572A1
WO2014082572A1 PCT/CN2013/087899 CN2013087899W WO2014082572A1 WO 2014082572 A1 WO2014082572 A1 WO 2014082572A1 CN 2013087899 W CN2013087899 W CN 2013087899W WO 2014082572 A1 WO2014082572 A1 WO 2014082572A1
Authority
WO
WIPO (PCT)
Prior art keywords
mme
user terminal
request
tau
information
Prior art date
Application number
PCT/CN2013/087899
Other languages
English (en)
Chinese (zh)
Inventor
陈霞云
倪国瑜
孙晓锋
席国宝
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2014082572A1 publication Critical patent/WO2014082572A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/186—Processing of subscriber group data

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for reporting MME pool scenario capability information. Background technique
  • CS Packet Switched
  • 3GPP 3rd Generation Partnership Project
  • CSFB Circuit Switched Fallback
  • VOLTE Voice over Long Term Evolution
  • the user In the VoLTE solution, the user directly conducts voice calls over the LTE network through Long Term Evolution (LTE) bearers.
  • LTE Long Term Evolution
  • the continuity of the voice call needs to be maintained by a Single Radio Voice Call Continuity (SRVCC) technology.
  • SRVCC Single Radio Voice Call Continuity
  • the PS to CS is switched through the network side and the terminal, and the traditional CS device is used for the voice call.
  • a Mobility Management Entity (MME) pool is deployed to increase network reliability.
  • the MME pool refers to an evolved base station in the pool area, and may also be referred to as an evolved Node B (eNB) connected to multiple MMEs.
  • eNB evolved Node B
  • UE User Equipment
  • An area where the MME does not change, the eNB in the MME pool and the MME in the MME pool area are fully interconnected.
  • the user supports the SRVCC capability and makes a voice call through VoLTE.
  • the relevant capabilities such as MS Classmark 2, MS Classmark 3, and Supported Codec, are notified to the network side.
  • the above cell is the information necessary for SRVCC.
  • the UE initiates a periodic Tracking Area Update (TAU) procedure. Specifically, the UE first sends a message to the serving eNB, and informs the serving eNB that the core network node information that the UE accessed last time is the first MME; the serving eNB finds an interface failure with the first MME, so the serving eNB re-receives the UE.
  • TAU Tracking Area Update
  • a normal new MME (hereinafter referred to as a second MME) for serving in the MME pool area, and forwarding the message to the second MME; after receiving the message, the second MME finds that the MME changes the TAU flow, so the user is last registered.
  • the first MME of the core network node obtains the context information of the user from the first MME, and the second MME performs a location update operation on the Home Subscriber Server (HSS), and the HSS also sends a user logout operation to the first MME. ;
  • HSS Home Subscriber Server
  • the core network node changes (the periodic TAU is a special TAU process, when the UE enters the evolved packet system connectivity management idle state) After that, the periodic TAU timer starts to count; after the UE enters the evolved packet system connection management connection state, the timer stops counting; after the timer expires, the UE actively initiates a periodic TAU procedure. Under normal circumstances, for the period Sexual TAU process, the core network node does not change).
  • the second MME rejects the processing, which in turn causes the voice service to be interrupted.
  • the user supports the CSFB capability and needs to make a voice call through the CSFB technology.
  • the user first performs the joint attach, and the UE is jointly registered to the first MME and the Mobile Switching Center (MSC) under the serving eNB.
  • MSC Mobile Switching Center
  • the MME interface of the first MME and the MSC is normal, and the user is in the scenario.
  • Voice telephony and short message services are available.
  • the S1 interface between the first MME and the serving eNB is faulty, the UE initiates a periodic TAU process, and the process steps are similar to the process steps in the prior art 1, and are not described here.
  • the core network node changes, which causes all subsequent voice calls and short message services of the user to be unavailable. Summary of the invention
  • the technical problem to be solved by the embodiments of the present invention is to provide a method and a device for reporting the MME pool scenario capability information, which is used to solve the problem in the prior art, when the serving MME is faulty, the voice service is interrupted, or the voice service and the short message service are unavailable.
  • the first aspect provides a mobility management entity pool scenario voice service maintenance method, including:
  • the second MME in the MME pool receives the first tracking area update TAU request initiated by the user terminal, where the first MME is the original of the user terminal. Serving the MME, the second MME is a serving MME after the first MME fails;
  • the second MME acquires capability information of the user terminal from the first MME, or ends the tracking area update initiated by the first TAU request, in the tracking area update process initiated by the first TAU request.
  • the capability information of the user terminal includes: a single wireless voice call continuity SRVCC related information of the user terminal, or the user terminal The circuit switched back CSFB capability information.
  • the first TAU request does not carry capability information of the user terminal, and the first TAU request includes: a periodic TAU request.
  • the tracking initiated by the first TAU request During the area update process, the acquiring, by the second MME, the capability information of the user terminal from the first MME includes:
  • a third possible implementation manner of the first aspect is further provided, where the method further includes:
  • the second MME When the context response includes the SRVCC related information of the user terminal, the second MME saves the SRVCC related information of the user terminal, so that the second MME performs SRVCC processing, and sends an update location request to the home subscriber server. For performing location update; or, when the context response includes CSFB joint registration information of the user terminal, the second MME sends an update location request to the home subscriber server for location update, and sends the location to the mobile switching center. Update the request for the SGs interface update.
  • a fourth possible implementation manner of the first aspect is further provided, where the tracking initiated by the first TAU request After the area update is complete, the acquiring, by the second MME, the capability information of the user terminal from the user terminal includes:
  • the fifth possible implementation manner of the first aspect is further provided, where the method further includes: Sending, by the second MME, a context request to the first MME to request context information of the user terminal, and receiving a context response that is sent by the first MME after receiving the context request, and acquiring the context information, to obtain The context information; sending an update location request to the home subscriber server for location update; if the second TAU request carries CSFB capability information of the user terminal, the method further comprises: sending a location update request to the mobile switching center To update the SGs interface.
  • a sixth possible implementation manner of the first aspect is further provided, where the tracking initiated by the first TAU request After the area update is complete, the acquiring, by the second MME, the capability information of the user terminal from the user terminal includes:
  • the CSFB of the user terminal jointly attaches information, or carries SRVCC related information of the user terminal; receives the attach request and performs attach processing of the user terminal.
  • the second aspect provides a method for reporting capability information of a mobility management entity pool scenario user terminal, including:
  • the user terminal initiates a first TAU request, the first MME of the original MME of the user terminal is faulty, the first TAU request is received by the second MME, and the second MME is the serving MME after the first MME fails.
  • the first MME and the second MME are deployed in the same MME pool;
  • the capability information of the user terminal includes: SRVCC related information of the user terminal, or CSFB capability information of the user terminal.
  • the first TAU request is not carried
  • the capability information of the user terminal, the first TAU request includes: a periodic TAU request.
  • a second possible implementation manner of the second aspect is further provided, where the tracking initiated by the first TAU request After the area update is complete, sending the message including the capability information of the user terminal to the second MME includes:
  • a TAU accept message or a TAU reject message sent by the second MME after receiving the first TAU request where the TAU reject message carries a status that keeps the registration status of the user terminal unchanged.
  • a RRC release message carrying a special cause value where the eNB receives the user context release command that is sent by the second MME and carries the special cause value.
  • a third possible implementation manner of the second aspect is further provided, where the tracking initiated by the first TAU request After the area update is complete, sending the message including the capability information of the user terminal to the second MME includes:
  • TAU reject message sent by the second MME after receiving the first TAU request, where the TAU reject message carries a reject cause value that changes a registration status of the user terminal;
  • the second MME initiates an attach request, so that the second MME performs the attach process of the user terminal, where the attach request carries the CSFB joint attach information of the user terminal, or the SRVCC related information of the user terminal.
  • the third aspect provides a method for reporting capability information of a user terminal in a mobility management entity pool scenario, including:
  • the CSFB capability information of the user terminal includes: CSFB joint registration information of the user terminal.
  • a mobility management entity MME including:
  • a first receiving unit configured to: when the first MME in the MME pool of the mobility management entity fails, receive a first tracking area update TAU request initiated by the user terminal, where the first MME is an original MME of the user terminal;
  • a first processing unit configured to acquire capability information of the user terminal from the first MME, or a tracking area initiated by the first TAU request, in a tracking area update process initiated by the first TAU request After the end of the update, the capability information of the user terminal is obtained from the user terminal, where the capability information of the user terminal includes: single wireless voice call continuity SRVCC related information of the user terminal, or circuit switching of the user terminal. Fall back CSFB capability information.
  • the first TAU request does not carry capability information of the user terminal, and the first TAU request includes: a periodic TAU request.
  • the MME further includes: a determining unit, configured to After receiving the first TAU request, the first receiving unit determines whether the user terminal is a registered user terminal of the MME, and if not, triggers the first processing unit.
  • the first processing unit includes:
  • a first sending subunit configured to send a context request to the first MME to request context information of the user terminal
  • the first receiving subunit is configured to receive, after receiving the context request, the first MME sends a context response including the context information of the user terminal, the context response further comprising: SRVCC related information of the user terminal, or the user terminal CSFB joint registration information.
  • a fourth possible implementation manner of the fourth aspect is further provided, where the MME further includes:
  • a storage unit configured to: when the context information in the context response includes SRVCC related information of the user terminal, store SRVCC related information of the user terminal to facilitate SRVCC processing; and a second processing unit, configured to send to the home user
  • the server sends an update location request for location update.
  • a fifth possible implementation manner of the foregoing fourth aspect is further provided, where the MME further includes:
  • a third processing unit configured to: when the context information in the context response includes the CSFB joint registration information of the user terminal, send an update location request to the home subscriber server to perform location update; and a fourth processing unit, configured to move to The switching center sends a location update request for the SGs interface update.
  • the first processing unit includes:
  • a second sending subunit configured to send a TAU accept message to the user terminal, or send a TAU reject message to the user terminal, where the TAU reject message carries a registration state that keeps the user terminal unchanged a third transmission subunit, configured to send, to the evolved base station eNB, a user terminal context release command carrying a special cause value, so that the eNB notifies the user terminal of the special cause value, so that the The user terminal initiates a second TAU request to the MME, where the second TAU request carries the capability information of the user terminal, and the second receiving subunit is configured to receive the second TAU request to obtain the capability of the user terminal. information.
  • the seventh possible implementation of the fourth aspect is further provided, where the MME further includes:
  • a first sending unit configured to send a context request to the first MME to request context information of the user terminal
  • a second receiving unit configured to receive, by the first MME, the a context response that includes the context information sent after the context request
  • a fifth processing unit configured to send an update location request to the home subscriber server for location update.
  • the eighth possible implementation manner of the fourth aspect is further provided, where the MME further includes: a sixth processing unit, configured to send to the mobile switching center Location update request for SGs interface update.
  • the ninth possible implementation manner of the fourth aspect is further provided, where the first processing unit includes:
  • a fourth sending subunit configured to send a TAU reject message to the user terminal, so that the user terminal initiates an attach request to the second MME, where the attach request carries the CSFB joint attach information of the user terminal, or carries the The SRVCC related information of the user terminal; the third receiving subunit, configured to receive the attach request; and the processing subunit, configured to perform attach processing of the user terminal.
  • a fifth aspect provides a capability information reporting apparatus for a user terminal, including:
  • a sending unit configured to send a first TAU request, where the first serving MME of the user terminal fails, the first TAU request is received by the second MME, and the second MME is after the first MME is faulty
  • the serving MME, the first MME and the second MME are deployed in the same MME pool;
  • a first processing unit configured to send, after the end of the tracking area update initiated by the first TAU request, a message including the capability information of the user terminal to the second MME, so that the second MME acquires the user
  • the capability information of the terminal where the capability information of the user terminal includes: SRVCC related information of the user terminal, or CSFB capability information of the user terminal.
  • the first TAU request does not carry capability information of the user terminal, and the first TAU request includes: a periodic TAU request.
  • the first processing unit includes:
  • a first receiving subunit configured to receive, by the second MME, the first TAU request a TAU accept message or a TAU reject message, where the TAU reject message carries a reject cause value that keeps the registration status of the user terminal unchanged;
  • the second receiving subunit is configured to receive the evolved base station eNB to send a radio resource control protocol RRC release message carrying a special cause value, wherein the eNB sends the RRC release to the user terminal after receiving a user context release command that is sent by the second MME and carrying the special cause value a first sending sub-unit, configured to initiate a second TAU request to the second MME, where the second TAU request carries capability information of the user terminal.
  • the first processing unit includes:
  • a third receiving subunit configured to receive a TAU reject message sent by the second MME after receiving the first TAU request, where the TAU reject message carries a reject cause value that changes a registration status of the user terminal
  • a second sending subunit configured to send an attach request to the second MME, so that the second MME performs an attach process of the user terminal, where the attach request carries the CSFB joint attach information of the user terminal, or SRVCC related information of the user terminal.
  • a sixth aspect provides a capability information reporting apparatus for a user terminal, including:
  • a receiving unit configured to receive a context request for requesting context information of the user terminal sent by the second MME, where the second MME is a serving MME after the fault occurs in the original serving MME of the user terminal, and the capability information reporting device
  • the original serving MME and the second MME are deployed in the same MME pool;
  • a sending unit configured to send a context response to the second MME, where the context response includes context information and capability information of the user terminal, where the capability information of the user terminal includes: SRVCC related information of the user terminal, or CSFB capability information of the user terminal.
  • the CSFB capability information of the user terminal includes: CSFB joint registration information of the user terminal.
  • the seventh aspect provides a mobility management entity pool system, including: a first MME and a second MME, where the second MME is the MME provided by the fourth aspect of the embodiment of the present invention,
  • the first MME includes the capability information reporting apparatus provided in the sixth aspect of the embodiment of the present invention.
  • the eighth aspect provides a user terminal capability information reporting system, including: a second MME and a user terminal, where the second MME is the MME provided by the fourth aspect of the embodiment of the present invention, where the user terminal includes the MME A capability information reporting apparatus provided by the fifth aspect of the invention.
  • the second MME may obtain the capability information of the user terminal from the first MME in the TAU process initiated by the first TAU request, or After the end of the TAU initiated by the TAU, the capability information of the user terminal is obtained from the user terminal, and then the SRVCC processing or the CSFB processing can be performed according to the capability information of the user terminal, so that the circuit domain service availability and the voice service sustainability of the user terminal can be ensured.
  • FIG. 1 is a schematic flowchart of a method for maintaining a voice service of an MME pool scenario according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of a method for maintaining a voice service of an MME pool scenario according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of a method for maintaining a voice service of an MME pool scenario according to an embodiment of the present invention
  • FIG. 4 is a schematic flowchart of a method for maintaining a voice service of an MME pool scenario according to an embodiment of the present invention
  • FIG. 5 is a schematic flowchart of a method for maintaining an MME pool scenario voice service according to an embodiment of the present invention
  • FIG. 6 is a schematic flowchart of a method for reporting capability information of a mobility management entity pool scenario user terminal according to an embodiment of the present invention
  • FIG. 7 is a schematic flowchart of a method for reporting capability information of a mobility management entity pool scenario user terminal according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of an MME according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of an MME according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of an MME according to an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of an MME according to an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of an MME according to an embodiment of the present invention.
  • FIG. 13A is a schematic structural diagram of a capability information reporting apparatus of a user terminal according to an embodiment of the present invention.
  • FIG. 13B is a schematic structural diagram of a first processing unit of a capability information reporting apparatus of a user terminal according to an embodiment of the present invention.
  • FIG. 13C is a schematic structural diagram of a first processing unit of a capability information reporting apparatus of a user terminal according to an embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of a capability information reporting apparatus of a user terminal according to an embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram of a capability information reporting apparatus of a user terminal according to an embodiment of the present invention.
  • 16 is a schematic structural diagram of a capability information reporting apparatus of a user terminal according to an embodiment of the present invention.
  • FIG. 17 is a schematic diagram of an MME pool system in accordance with an embodiment of the present invention.
  • FIG. 18 is a schematic diagram of a user terminal capability information reporting system according to an embodiment of the present invention. detailed description
  • FIG. 1 is a schematic flowchart of a method for maintaining a voice service of an MME pool scenario according to an embodiment of the present invention. Referring to FIG. 1, the method includes:
  • the first MME in the MME pool receives the first tracking area update TAU request sent by the user equipment, where the first MME is the user terminal, when the first MME in the MME pool is faulty.
  • the original MME, the second MME is a serving MME after the first MME fails.
  • the serving eNB of the user equipment after receiving the first TAU request sent by the user terminal, finds that the S1 interface between the eNB and the first MME is faulty, and is in the MME pool. Selecting a normal MME (in this embodiment, the second MME) for the user terminal to reproduce, and transparently transmitting the first TAU request to the normal MME.
  • a normal MME in this embodiment, the second MME
  • the first TAU request does not carry the capability information of the user terminal, and the first TAU request includes: a periodic TAU request.
  • the second MME acquires the capability information of the user terminal from the first MME, or the tracking area initiated by the first TAU request, in the tracking area update process initiated by the first TAU request. After the update is complete, the second MME obtains the capability information of the user terminal from the user terminal, where the capability information of the user terminal includes: a single wireless voice call continuity SRVCC related information of the user terminal, or the The circuit switching of the user terminal drops CSFB capability information.
  • the capability information of the user terminal can reflect that the user terminal supports CSFB capability or supports SRVCC capability.
  • the SRVCC related information of the user terminal includes: SRVCC capability information, MS Classmark 2, MS Classmark 3, and Supported Codec information.
  • the circuit switched fallback CSFB capability information of the user terminal includes: CSFB joint registration information or CSFB joint attachment information.
  • the second MME may acquire the user terminal in the TAU process initiated by the first TAU request or after the TAU initiated by the first TAU request ends.
  • Ability information The problem that the second MME cannot obtain the capability information of the UE when the first MME fails, and the availability of the circuit domain service and the sustainability of the voice service can be ensured.
  • the second MME determines that the user terminal is not a registered user of the second MME.
  • the terminal (for example, determining according to the MME global identifier carried in the first TAU request), sending a context request to the first MME to request context information of the user terminal; receiving the first MME receiving a context response that includes the context information of the user terminal that is sent after the context request, the context response further includes: SRVCC related information of the user terminal, or CSFB joint registration information of the user terminal (for example: location Location Area ID (LAI) and Visitor Location Register Number (VLR Number).
  • LAI location Location Area ID
  • VLR Number Visitor Location Register Number
  • the second MME when the context response includes the SRVCC related information of the user terminal, the second MME saves the SRVCC related information of the user terminal, so that the second MME performs SRVCC processing. And send an update location request to the home subscriber server for location update.
  • the home subscriber server for location update.
  • it may include:
  • the second MME saves SRVCC related information of the user terminal; and sends an update location request to the home subscriber server, so that the home subscriber server updates location information related to the second MME (for example: MME-ID and An international mobile subscriber identity code) and deleting location information associated with the first MME; thereafter, the second MME sends a TAU accept message to the user terminal and receives a TAU Complete message returned by the user terminal.
  • location information related to the second MME for example: MME-ID and An international mobile subscriber identity code
  • the second MME sends a TAU accept message to the user terminal and receives a TAU Complete message returned by the user terminal.
  • the present invention is not limited to the specific signaling flow involved, the bearer context update procedure, and the like.
  • the second MME when the context response includes the CSFB joint registration information of the user terminal, the second MME sends an update location request to the home subscriber server. For location update, and sending a location update request to the mobile switching center MSC for SGs interface update to complete the joint registration.
  • the first MME may insert the CSFB joint registration information in an extension field of the context response.
  • the update of the SGs interface may adopt an existing protocol, which is not limited by the present invention.
  • the second MME may acquire the capability information of the UE in the TAU process initiated by the first TAU request, and further perform location update, Performing SRVCC processing or CSFB processing according to the capabilities supported by the UE ensures the availability of circuit domain services and the sustainability of voice services.
  • the second MME determines that the user terminal is not a registered user of the second MME. Terminal, perform the following steps:
  • TAU reject message carries a reject cause value that does not change the UE mobility management (EMM) registration status, for example: conditional IE error.
  • EMM UE mobility management
  • the special cause value may be Load Balancing TAU Required.
  • the TAU process initiated by the second TAU request is a TAU process in which a tracking area (TA) is changed, and the second TAU request carries the SRVCC of the user terminal.
  • the second MME After receiving the second TAU request, the second MME sends a context request to the first MME to request a context information of the user terminal. Receiving a context response including the context information sent by the first MME after receiving the context request to obtain the context information; and sending an update location request to the home subscriber server for location update.
  • the TAU process initiated by the second TAU request is a joint TA (tracking area) / LA (location area) update process (at this time, the second TAU request is The TAU type is "combined TA/LA updating", indicating that the user terminal supports or needs to execute CSFB).
  • the second MME After receiving the second TAU request, the second MME sends a context request to the first MME to request context information of the user terminal, and receives the first MME sends the context request after receiving the context request.
  • Context response containing the context information to obtain the context information; sending an update location request to the home subscriber server for location update; sending a location update request to the mobile switching center for SGs interface update.
  • the second MME acquires capability information of the UE, performs location update, and can perform SRVCC according to the capability supported by the UE.
  • Processing or CSFB processing ensures the availability of circuit domain services and the sustainability of voice services.
  • the second MME receives the
  • the TAU reject message carries a special cause value (such as: Implicitly detached, or UE identity cannot be derived by the network), so that the EMM status of the UE changes. .
  • FIG. 2 is a schematic flowchart of a method for maintaining a voice service of a MME pool scenario according to an embodiment of the present invention. Referring to FIG. 2, taking a CSFB capability of a user terminal as an example, the method includes:
  • the UE sends a first TAU request to the serving eNB to initiate a periodic TAU procedure and informs the serving eNB that the core network node that the UE last accessed is the first MME.
  • the serving eNB finds that the S1 interface with the first MME is faulty, and then reselects the normal second MME to serve in the MME pool, and forwards the first TAU request to the second MME.
  • the second MME determines that the TAU procedure initiated by the user equipment is a periodic TAU procedure changed by the MME, and sends a TAU accept message to the UE (2c-1 in the figure); or, the second The MME determines that the TAU procedure initiated by the user equipment is a periodic TAU procedure changed by the MME, and then sends a TAU reject message (2c-2 in the figure) to the UE, thereby ending the current periodic TAU procedure.
  • the TAU reject message carries a reason value that does not change the EMM registration status of the UE, for example: 3 ⁇ 4 port: conditional IE error.
  • the second MME sends a UE context release command to the serving eNB to release an S1 interface with the serving eNB.
  • the UE context release command carries a special cause value: Load Balancing TAU Required.
  • the serving eNB notifies the UE of the cause value by using a Radio Resource Control (RRC) release message.
  • RRC Radio Resource Control
  • the UE After receiving the message carrying the cause value, the UE sends a second TAU request to the serving eNB to initiate a joint TA/LA location update.
  • the serving eNB sends the second TAU request to the second MME.
  • the second MME performs a location update process.
  • the second MME sends a location update request to the MSC for location update.
  • the MSC sends a location update accept message to the second MME to establish the MSC Associated with an SGs interface between the second MME.
  • FIG. 3 is a schematic diagram of a method for maintaining a voice service of an MME pool scenario according to an embodiment of the present invention.
  • an example of a user terminal supporting SRVCC capability is as follows:
  • the UE After receiving the RRC release message carrying the cause value, the UE sends a second TAU request to the serving eNB to initiate a TA changed TAU, where the second TAU carries the SRVCC related information of the user, for example: MS Classmark2. MS Classmark3 and Support Code, etc.
  • the serving eNB sends the second TAU request to the second MME.
  • step 2h Please refer to the description of step 2h in the embodiment shown in FIG. 2.
  • the embodiment shown in Figure 3 is capable of guaranteeing the continuity of the voice telephone service of the SRVCC subscriber.
  • FIG. 4 is a schematic flowchart of a method for maintaining a voice service of an MME pool scenario according to an embodiment of the present invention. Referring to FIG. 4, the method includes:
  • the second MME determines that the TAU process initiated by the user terminal is a periodic TAU process changed by the MME, and sends a context request to the first MME to request context information of the user terminal.
  • the first MME sends a context response including the context information of the user terminal to the second MME after receiving the context request, where the context response further includes: SRVCC related information of the user terminal, or The CSFB joint registration information of the user terminal.
  • the second MME sends an update location request to the home subscriber server to perform location update.
  • the context response includes SRVCC related information of the user terminal
  • the second MME saves the user terminal.
  • the SRVCC related information facilitates the SRVCC processing by the second MME.
  • the home subscriber server sends a cancel location request to the first MME.
  • the first MME sends a cancel location response to the home subscriber server.
  • the home subscriber server sends an update location response to the second MME.
  • steps 4i and 4j are also required, otherwise steps 4i and 4j need not be performed.
  • FIG. 5 is a schematic flowchart of a method for maintaining a voice service of an MME pool scenario according to an embodiment of the present invention. Referring to FIG. 5, the method includes:
  • the second MME determines that the user terminal is not the registered user terminal of the second MME, and sends a TAU reject message to the user terminal, where the TAU reject message carries a change of the registration status of the user terminal.
  • the reject reason value (for example: Implicitly detached, or UE identity cannot be derived by the network) causes the EMM state of the UE to change.
  • the user terminal After the user terminal receives the TAU reject message, the user terminal initiates an attach request to the second MME, where the attach request carries the CSFB joint attach information of the user terminal, or the SRVCC related information of the user terminal. .
  • the attach request is transparently transmitted to the second MME via the serving eNB, step 5e.
  • the serving eNB receives the attach request and sends the attach request to the second MME for the second MME to perform attach processing of the user terminal.
  • FIG. 6 is a schematic flowchart of a method for reporting capability information of a mobility management entity pool scenario user terminal according to an embodiment of the present invention. Referring to FIG. 6, the method includes:
  • the user terminal initiates a first TAU request, where the original serving MME of the user terminal is first.
  • the MME is faulty
  • the first TAU request is received by the second MME
  • the second MME is the serving MME after the first MME is faulty
  • the first MME and the second MME are deployed in the same MME pool.
  • the first TAU request does not carry capability information of the user terminal, for example, the first TAU request may be a periodic TAU request.
  • the capability information of the user terminal includes: SRVCC related information of the user terminal, or CSFB capability information of the user terminal.
  • the method for reporting the user terminal capability information provided in this embodiment, when the first MME is faulty, the capability information of the user terminal is sent to the second MME by using a corresponding message, so that the second MME is used.
  • the capability information of the user terminal is obtained in time to ensure the availability of the circuit domain service and the sustainability of the voice service.
  • 602 can include the following implementation manners:
  • Implementation 1 includes the following steps:
  • the user terminal receives a TAU accept message or a TAU reject message sent by the second MME after receiving the first TAU request, where the TAU reject message carries a registration state of the user terminal. Constant rejection reason value.
  • the user terminal receives the RRC release message carrying the special cause value sent by the evolved base station eNB, where the eNB receives the user context release that is sent by the second MME and carries the special cause value.
  • the RRC release message is sent to the user terminal after the command.
  • the user terminal initiates a second TAU request to the second MME, where the second TAU request carries capability information of the user terminal.
  • Implementation 2 includes the following steps:
  • the user terminal receives a TAU reject message sent by the second MME after receiving the first TAU request, and the TAU reject message carries a reject cause value that changes a registration status of the user terminal.
  • the operation performed by the user terminal in the second implementation manner is referred to the corresponding description in the embodiment shown in FIG. 5.
  • FIG. 7 is a schematic flowchart of a method for reporting capability information of a mobility management entity pool scenario user terminal according to an embodiment of the present invention. Referring to FIG. 7, the method includes:
  • the first MME After receiving the fault, the first MME receives a context request for requesting context information of the user terminal, where the first MME is the original MME of the user terminal, and the second MME is the The serving MME after the failure of the first MME.
  • the context response includes context information and capability information of the user terminal, where the capability information of the user terminal includes: SRVCC related information of the user terminal, or the user CSFB capability information of the terminal.
  • the CSFB capability information of the user terminal includes: CSFB joint registration information of the user terminal.
  • the method for reporting the user terminal capability information provided in this embodiment, when the first MME is faulty, the capability information of the user terminal is sent to the second MME by using a corresponding message, so that the second MME is used.
  • the capability information of the user terminal is obtained in time to ensure the availability of the circuit domain service and the sustainability of the voice service.
  • FIG. 8 is a schematic structural diagram of an MME according to an embodiment of the present invention.
  • MME 80 include:
  • the first receiving unit 81 is configured to: when the first MME in the MME pool of the mobility management entity fails, receive a first tracking area update TAU request sent by the user terminal, where the first MME is the original month of the user terminal MME.
  • the first TAU request does not carry the capability information of the user terminal, and the first TAU request includes: a periodic TAU request.
  • the first processing unit 82 is configured to acquire capability information of the user terminal from the first MME, or a tracking initiated by the first TAU request, in a tracking area update process initiated by the first TAU request After the area is updated, the capability information of the user terminal is obtained from the user terminal, and the capability information of the user terminal includes: a single wireless voice call continuity SRVCC related information of the user terminal, or a circuit of the user terminal. Exchange the CSFB capability information.
  • the MME 80 may further include a determining unit 83, configured to determine, after the first receiving unit 81 receives the first TAU request, whether the user terminal is a registered user terminal of the MME, if not, triggering The first processing unit 82.
  • a determining unit 83 configured to determine, after the first receiving unit 81 receives the first TAU request, whether the user terminal is a registered user terminal of the MME, if not, triggering The first processing unit 82.
  • the MME 80 provided in this embodiment can obtain the capability information of the user terminal when the first MME is faulty, and avoids the problem that the MME 80 cannot obtain the user capability information. Therefore, the MME 80 can perform SRVCC processing or CSFB processing according to the capabilities of the user terminal, ensuring the availability of the circuit domain service and the sustainability of the voice service.
  • FIG. 9 is a schematic structural diagram of an MME according to an embodiment of the present invention, where the first processing unit 92 includes:
  • a first sending subunit 922 configured to send a context request to the first MME to request context information of the user terminal
  • a first receiving sub-unit 924 configured to receive a context response that includes the context information of the user terminal that is sent by the first MME after receiving the context request, where the context response further includes: an SRVCC of the user terminal Related information, or CSFB joint registration information of the user terminal.
  • the MME 90 includes the first receiving unit 91, the first processing unit 92, and the determining unit 93 (wherein the labels of the first receiving unit and the determining unit are different in the specification, but the functions are the same, as shown in FIG.
  • a storage unit 94 configured to store capability information of the user terminal, for example: when the context information in the context response includes the SRVCC of the user terminal When the information is related, the SRVCC related information of the user terminal is stored to facilitate the SRVCC processing by the MME.
  • the second processing unit 95 is configured to send an update location request to the home subscriber server for location update.
  • the MME 90 includes, in addition to the first receiving unit 91, the first processing unit 92, and the determining unit 93, the following:
  • the third processing unit 96 is configured to: when the context information in the context response includes CSFB joint registration information of the user terminal, send an update location request to the home subscriber server to perform location update;
  • the fourth processing unit 97 is configured to send a location update request to the mobile switching center to perform an SGs interface update.
  • FIG. 10 is a schematic structural diagram of an MME according to an embodiment of the present invention, where the first processing unit 102 includes:
  • a second sending sub-unit 1022 configured to send a TAU accept message to the user terminal, or send a TAU reject message to the user terminal, where the TAU reject message carries a status that keeps the registration status of the user terminal unchanged. Rejection reason value;
  • a third sending subunit 1024 configured to send, to the eNB, a user terminal context release command carrying a special cause value, so that the eNB notifies the user terminal of the special cause value, so that the user terminal is located at the user terminal
  • the MME initiates a second TAU request, where the second TAU request carries capability information of the user terminal;
  • the second receiving subunit 1026 is configured to receive the second TAU request to obtain capability information of the user terminal.
  • the MME 100 includes, in addition to the first receiving unit 101, the first processing unit 102, and the determining unit 103, the following:
  • a first sending unit 104 configured to send a context request to the first MME to request context information of the user terminal
  • the second receiving unit 105 is configured to receive a context response that is sent by the first MME after receiving the context request, and includes the context information.
  • the fifth processing unit 106 is configured to send an update location request to the home subscriber server for location update.
  • the MME 100 further includes:
  • the sixth processing unit 107 is configured to send a location update request to the mobile switching center to perform an SGs interface update.
  • FIG. 11 is a schematic structural diagram of an MME according to an embodiment of the present invention.
  • the MME 110 includes a first receiving unit 111, a first processing unit 112, and a determining unit 113, where the first processing unit 112 includes:
  • a fourth sending sub-unit 1122 configured to send a TAU reject message to the user terminal, so that the user terminal initiates an attach request to the second MME, where the attach request carries the CSFB joint attach information of the user terminal, or carries the SRVCC related information of the user terminal.
  • a third receiving subunit 1124 configured to receive the attach request
  • the processing subunit 1126 is configured to perform an attach process of the user terminal.
  • the MME 120 includes a transmitter 121, a receiver 122, a memory 123, and a processor connected to the transmitter 121, the receiver 122, and the memory 123, respectively. 124.
  • the program 123 stores various programs or applications to be called by the processor 124 to perform the following operations: When the first MME in the pool of the mobility management entity MME fails, the user is received by the receiver 122.
  • the first tracking area initiated by the terminal updates the TAU request, where the first MME is the original serving MME of the user terminal; Obtaining the capability information of the user terminal, including: acquiring the capability information of the user terminal from the first MME by using the receiver 122, in the tracking area update process initiated by the first TAU request, or After the tracking area update initiated by the first TAU request is completed, the capability information of the user terminal is obtained from the user terminal by using the receiver 122, and the capability information of the user terminal includes: a single wireless voice call continuity of the user terminal. SRVCC related information, or circuit switched fallback CSFB capability information of the user terminal.
  • the first TAU request does not carry the capability information of the user terminal, and the first TAU request includes: a periodic TAU request.
  • the processor 124 is configured to determine, after receiving the first TAU request by the receiver 122, whether the user terminal is a registered user terminal of the MME, and if not, performing acquiring the user terminal. The operation of the capability information.
  • the processor 124 is configured to send a context request to the first MME by using the transmitter 121 to request context information of the user terminal, and receive, by the receiver 122, the first MME, after receiving the context request. And a context response that includes the context information of the user terminal, where the context response further includes: SRVCC related information of the user terminal, or CSFB joint registration information of the user terminal.
  • the processor 124 is further configured to: when the context information in the context response includes the SRVCC related information of the user terminal, store the SRVCC related information of the user terminal to the memory 123 to facilitate SRVCC processing;
  • the processor 124 is further configured to send an update location request to the home subscriber server via the transmitter 121 and perform a corresponding location update process.
  • the processor 124 is further configured to: when the context information in the context response includes the CSFB joint registration information of the user terminal, send an update location request to the home subscriber server by using the transmitter 121 to perform location update.
  • a location update request is sent to the mobile switching center via the transmitter 121 for SGs interface update.
  • the processor 124 is configured to send a TAU accept message to the user terminal by using the transmitter 121, or send a TAU reject message to the user terminal, where the TAU rejects the message carrying Having a rejection reason value that keeps the registration status of the user terminal unchanged; transmitting, by the transmitter 121, a user terminal context release command carrying a special cause value to the evolved base station eNB, so that the eNB may use the special cause value Notifying the user terminal, so that the user terminal initiates a second TAU request to the MME, where the second TAU request carries capability information of the user terminal; receiving, by the receiver 122, a second TAU request to obtain the User terminal capability information.
  • the processor 124 is further configured to send a context request to the first MME by using the transmitter 121 to request context information of the user terminal, and receive, by the receiver 122, the first MME to receive the context.
  • a context response containing the context information sent after the request; an update location request is sent by the transmitter 121 to the home subscriber server for location update.
  • the processor 124 is further configured to send a location update request to the mobile switching center through the transmitter 121 to perform an SGs interface update process.
  • the processor 124 is configured to send, by using the transmitter 121, a TAU reject message to the user terminal, so that the user terminal initiates an attach request to the second MME, where the attach request carries the CSFB joint attachment of the user terminal.
  • FIG. 13A is a schematic structural diagram of a capability information reporting apparatus of a user terminal according to an embodiment of the present invention.
  • the capability information reporting apparatus 130 may be disposed on an access network side, for example, on the user terminal, and includes:
  • the sending unit 131 is configured to send a first TAU request, where the original serving MME first MME of the user terminal fails, the first TAU request is received by the second MME, and the second MME is the first MME fault.
  • the serving MME, the first MME and the second MME are deployed in the same MME pool.
  • the first TAU request does not carry the capability information of the user terminal, and the first TAU request includes: a periodic TAU request.
  • the first processing unit 132 is configured to send, after the end of the tracking area update initiated by the first TAU request, a message including the capability information of the user terminal to the second MME, so that the second The MME obtains the capability information of the user terminal, where the capability information of the user terminal includes: SRVCC related information of the user terminal, or CSFB capability information of the user terminal.
  • the capability information reporting device 130 which is provided by the embodiment, can send the capability information of the user terminal to the second MME by using a corresponding message, so that the second MME acquires the The capability information of the user terminal ensures the availability of the circuit domain service and the sustainability of the voice service.
  • the first processing unit 132 includes:
  • a first receiving sub-unit 1322 configured to receive a TAU accept message or a TAU reject message sent by the second MME after receiving the first TAU request, where the TAU reject message carries the user terminal The reject reason value for which the registration status remains unchanged.
  • the second receiving sub-unit 1324 is configured to receive a radio resource control protocol RRC release message that carries the special cause value, which is sent by the eNodeB eNB, where the eNB receives the value of the special cause that is sent by the second MME.
  • the RRC release message is sent to the user terminal after the user context release command.
  • the first sending sub-unit 1326 is configured to initiate a second TAU request to the second MME, where the second TAU request carries capability information of the user terminal.
  • the first processing unit 132 includes:
  • the third receiving sub-unit 1328 is configured to receive a TAU reject message sent by the second MME after receiving the first TAU request, where the TAU reject message carries a reason for rejecting the registration status of the user terminal. value.
  • a second sending sub-unit 1330 configured to send an attach request to the second MME, where the second MME performs an attach process of the user terminal, where the attach request carries the CSFB joint attach information of the user terminal, or SRVCC related information of the user terminal.
  • FIG. 14 is a diagram showing the structure of a capability information reporting apparatus of a user terminal according to an embodiment of the present invention.
  • the capability information reporting device 140 may be disposed on the access network side, for example, on the user terminal, and includes: a transmitter 141, a receiver 142, a memory 143, and a transmitter 141, a receiver 142, and a memory 143, respectively.
  • the memory 143 stores various programs or applications for invoking the corresponding program or application by the processor 144 to perform the following operations:
  • the processor 144 sends a first TAU request through the transmitter 141, and the original service MME of the user terminal is first.
  • the MME is faulty, the first TAU request is received by the second MME, and the second MME is the serving MME after the first MME is faulty, and the first MME and the second MME are deployed in the same MME pool;
  • the processor 144 sends a message including the capability information of the user terminal to the second MME by using the transmitter 141, so that the second MME acquires the user.
  • the capability information of the terminal, the capability information of the user terminal includes: SRVCC related information of the user terminal, or CSFB capability information of the user terminal.
  • the message including the capability information of the user terminal may be transparently transmitted to the second MME via the serving eNB of the user terminal.
  • the first TAU request does not carry the capability information of the user terminal, and the first TAU request includes: a periodic TAU request.
  • the processor 144 is configured to receive, by the receiver 142, a TAU accept message or a TAU reject message sent by the second MME after receiving the first TAU request, where the TAU reject message carries a
  • the RRC release message carrying the special cause value sent by the eNB is received by the receiver 142, where the eNB receives the bearer sent by the second MME.
  • the processor 144 is configured to receive, by the receiver 142, a TAU reject message sent by the second MME after receiving the first TAU request, where the TAU reject message carries a Determining the value of the rejection of the registration status of the user terminal; sending an attach request to the second MME by the transmitter 141, so that the second MME performs the attach processing of the user terminal, where the attach request carries the user terminal CSFB joint attachment information, or SRVCC related information of the user terminal.
  • FIG. 15 is a schematic structural diagram of a capability information reporting apparatus of a user terminal according to an embodiment of the present invention.
  • the capability information reporting apparatus 150 may be disposed on a core network side, for example, on a mobility management entity, including:
  • the receiving unit 151 is configured to receive a context request that is sent by the second MME to request context information of the user terminal, where the second MME is a serving MME after the original serving MME of the user terminal fails, and the capability information is reported.
  • the device 150 is disposed in the original serving MME, and the original serving MME and the second MME are deployed in the same MME pool.
  • the sending unit 152 is configured to send a context response to the second MME, where the context response includes context information and capability information of the user terminal, where the capability information of the user terminal includes: SRVCC related information of the user terminal, Or CSFB capability information of the user terminal.
  • the CSFB capability information of the user terminal includes: CSFB joint registration information of the user terminal.
  • the capability information reporting device 150 provided in this embodiment can send the capability information of the user terminal to the second MME by using a corresponding message when the first MME is faulty, so that the second MME acquires the current MME in time.
  • the capability information of the user terminal ensures the availability of the circuit domain service and the sustainability of the voice service.
  • FIG. 16 is a schematic structural diagram of a capability information reporting apparatus of a user terminal according to an embodiment of the present invention.
  • the capability information reporting apparatus 160 may be disposed on a core network side, for example, disposed on a mobility management entity, and includes: a transmitter 161, A receiver 162, a memory 163, and a processor 164 coupled to the transmitter 161, the receiver 162, and the memory 163, respectively.
  • the memory 163 stores various programs or applications for invoking the corresponding programs or applications by the processor 164 to perform the following operations:
  • the processor 164 receives, by the receiver 162, the second MME for requesting the user terminal.
  • the second MME is a serving MME after the failure of the original MME of the user terminal, and the capability information reporting device 160 is disposed in the original serving MME, the original serving MME and the second The MME is deployed in the same MME pool;
  • the transmitter 161 Sending, by the transmitter 161, a context response to the second MME, where the context response includes context information and capability information of the user terminal, where the capability information of the user terminal includes: SRVCC related information of the user terminal, or The CSFB capability information of the user terminal.
  • the CSFB capability information of the user terminal includes: CSFB joint registration information of the user terminal.
  • FIG. 17 is a schematic diagram of an MME pool system according to an embodiment of the present invention.
  • the MME pool system includes: a first MME 171 and a second MME 172.
  • the first MME 171 includes the capability information reporting device.
  • the capability information reporting device refer to the corresponding description in the embodiment shown in FIG. 15 or FIG. 16 , and details are not described herein.
  • the MME pool system may also include other MMEs, eNBs, and interconnection relationships between the MMEs, and the like.
  • the MME pool system provided by the present invention can acquire the capability information of the user terminal from the first MME 171 in a timely manner by the second MME 172, thereby ensuring the availability of the circuit domain service and the sustainability of the voice service.
  • FIG. 18 is a schematic diagram of a user terminal capability information reporting system according to an embodiment of the present invention.
  • the system includes: a second MME 181 and a user terminal 182, wherein, for the structure description of the second MME 181, refer to FIG. The corresponding description in the embodiment shown in any one of -12 is not described herein.
  • the user terminal 182 includes the capability information reporting device.
  • the capability information reporting device refer to the corresponding description in the embodiment shown in any one of FIG. 13A to FIG. 14 , and details are not described herein.
  • the user terminal capability information reporting system provided in this embodiment enables the second MME 181 to obtain the capability information of the user terminal 182 in a timely manner, thereby ensuring that the circuit domain service is available. Sustainability of sexual and voice business.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

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

Abstract

La présente invention porte sur un procédé, un dispositif et un système de traitement d'une requête de données d'abonnement de groupe fermé d'abonnés (CSG), le procédé comprenant les opérations suivantes : un serveur d'abonnés CSG reçoit une requête de données d'abonnement CSG transmise par une entité de gestion de mobilité (MME), la requête de données d'abonnement CSG contenant l'identificateur de la MME et l'identificateur d'un équipement utilisateur (UE), et étant utilisée pour acquérir les données d'abonnement CSG de l'UE ; et si les données d'abonnement CSG de l'UE n'existent pas, alors le serveur d'abonnés CSG sauvegarde l'identificateur de la MME et l'identificateur de l'UE. Le procédé évite qu'une MME soit incapable d'acquérir les données d'abonnement CSG mises à jour d'un UE.
PCT/CN2013/087899 2012-11-27 2013-11-27 Procédé et dispositif de rapport d'informations de capacité dans un scénario de pool de mme WO2014082572A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210489096.3 2012-11-27
CN201210489096.3A CN103841545B (zh) 2012-11-27 2012-11-27 一种mme池场景能力信息上报的方法及装置

Publications (1)

Publication Number Publication Date
WO2014082572A1 true WO2014082572A1 (fr) 2014-06-05

Family

ID=50804586

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/087899 WO2014082572A1 (fr) 2012-11-27 2013-11-27 Procédé et dispositif de rapport d'informations de capacité dans un scénario de pool de mme

Country Status (2)

Country Link
CN (1) CN103841545B (fr)
WO (1) WO2014082572A1 (fr)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016119262A1 (fr) * 2015-01-30 2016-08-04 华为技术有限公司 Procédé de reprise sur sinistre de service, dispositif associé et système de communication
JP6487563B2 (ja) * 2015-01-30 2019-03-20 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． サービス冗長方法および関係付けられた装置
CN107205232A (zh) * 2016-03-17 2017-09-26 中兴通讯股份有限公司 寻呼方法及通信系统
CN108200571B (zh) * 2016-12-08 2021-03-05 中国移动通信集团四川有限公司 一种跟踪区更新方法、装置及移动管理实体
CN108271151B (zh) * 2016-12-31 2021-07-09 中国移动通信集团辽宁有限公司 用于移动互联网终端识别的方法及装置
CN109788511B (zh) * 2017-11-10 2021-05-18 华为技术有限公司 终端的网络变更方法及核心网设备
CN109996268B (zh) * 2017-12-29 2022-05-31 中国移动通信集团四川有限公司 通信链路连接方法、装置、设备及介质
CN110798853B (zh) * 2018-08-02 2023-04-25 成都鼎桥通信技术有限公司 通信方法、装置及系统
CN113923613B (zh) * 2021-10-14 2022-09-16 维沃移动通信有限公司 通话处理方法、装置、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101472332A (zh) * 2007-12-29 2009-07-01 华为技术有限公司 一种CSoPS能力协商方法、系统和装置
CN101521871A (zh) * 2008-02-26 2009-09-02 大唐移动通信设备有限公司 一种跟踪区更新的方法、装置和系统
CN101646270A (zh) * 2008-08-06 2010-02-10 华为技术有限公司 保持业务连续的方法、系统、移动性管理实体和存储设备
CN101848515A (zh) * 2009-03-25 2010-09-29 华为技术有限公司 一种切换方法、通信系统及相关设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9392626B2 (en) * 2009-11-09 2016-07-12 Samsung Electronics Co., Ltd. Method and system to support single radio video call continuity during handover
CN103139854B (zh) * 2010-06-28 2016-03-30 华为技术有限公司 切换方法、通信装置和通信系统
CN102378148B (zh) * 2010-08-23 2016-06-01 中兴通讯股份有限公司 终端、hss、及核心网网元获知终端能力的方法和系统
JP5655958B2 (ja) * 2011-01-19 2015-01-21 ▲ホア▼▲ウェイ▼技術有限公司 ハンドオーバ方法およびモビリティ管理ネットワーク要素
CN102647693B (zh) * 2011-02-18 2016-11-23 中兴通讯股份有限公司 语音业务呼叫连续性实现方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101472332A (zh) * 2007-12-29 2009-07-01 华为技术有限公司 一种CSoPS能力协商方法、系统和装置
CN101521871A (zh) * 2008-02-26 2009-09-02 大唐移动通信设备有限公司 一种跟踪区更新的方法、装置和系统
CN101646270A (zh) * 2008-08-06 2010-02-10 华为技术有限公司 保持业务连续的方法、系统、移动性管理实体和存储设备
CN101848515A (zh) * 2009-03-25 2010-09-29 华为技术有限公司 一种切换方法、通信系统及相关设备

Also Published As

Publication number Publication date
CN103841545A (zh) 2014-06-04
CN103841545B (zh) 2017-12-29

Similar Documents

Publication Publication Date Title
WO2014082572A1 (fr) Procédé et dispositif de rapport d'informations de capacité dans un scénario de pool de mme
TWI469659B (zh) 用於服務核心網路節點變更時處理一行動裝置之可聯繫性之方法
JP5646647B2 (ja) 通信ネットワークで用いる方法および装置
JP4968408B2 (ja) 移動端末と移動端末の移動通信ネットワークへの登録方法
WO2019024934A1 (fr) Procédé de récupération de défaillance de fonction de commande de session d'appel proxy, appareil et système
WO2009100609A1 (fr) Procédé de transfert de domaine de la continuité d'appel vocal radio unique
WO2015062098A1 (fr) Procédé de sélection de réseau et dispositif de réseau central
WO2010003374A1 (fr) Procédé et terminal correspondant pour une mise à jour de relation d'association
JP6480011B2 (ja) 通信を確立するための方法及び移動無線通信ネットワーク構成要素
WO2011098040A1 (fr) Procédé de reprise de réseau 2g/3g, appareils associés et système de communication
WO2014194500A1 (fr) Méthode de transmission d'informations, méthode et appareil de modification d'informations
WO2012025001A1 (fr) Procédé et système de traitement de services antérieurs
WO2012055093A1 (fr) Procédé et dispositif de traitement d'appel dans une réserve de centres de commutation de communications mobiles
WO2014005444A1 (fr) Procédé d'accès, système, entité de gestion de mobilité et équipement utilisateur pour mise en dérivation de réseau local sans fil
WO2014029065A1 (fr) Procédé et dispositif d'affichage de nom de réseau
WO2019029228A1 (fr) Procédé et dispositif de traitement de service vocal et support de stockage
CN109089289B (zh) 切换到电路交换域的方法和装置
WO2011113207A1 (fr) Procédé et dispositif destinés à un commutateur d'accès aux services
WO2014029059A1 (fr) Procédé et dispositif d'affichage de nom de réseau
WO2012152129A1 (fr) Procédé et système de traitement de réinitialisation d'un enregistreur de localisation nominal
WO2015085545A1 (fr) Procédé de récupération de service de commutation de paquets (ps), centre de commutation mobile (msc)/enregistreur de localisation de visiteurs (vlr) et entité de gestion de mobilité (mme)
WO2011044815A1 (fr) Procédé, commutateur de service mobile(msc)/enregistreur de localisation de visiteurs(vlr), entité de gestion de mobilité (mme) et noeud b évolué (enodeb) pour la mise en oeuvre d'un service avec priorité
WO2014048142A1 (fr) Procédé de traitement de défaillance d'enregistreur de localisation des visiteurs, et élément de réseau de gestion de mobilité
WO2015010516A1 (fr) Procédé de gestion d'itinérance dans un service de repli en mode circuit, et élément de réseau
WO2014180405A1 (fr) Procédé de téléavertissement et centre de commutation mobile

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

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

Country of ref document: EP

Kind code of ref document: A1