WO2009121255A1 - 承载挂起的方法、承载恢复的方法及网关代理 - Google Patents

承载挂起的方法、承载恢复的方法及网关代理 Download PDF

Info

Publication number
WO2009121255A1
WO2009121255A1 PCT/CN2009/070654 CN2009070654W WO2009121255A1 WO 2009121255 A1 WO2009121255 A1 WO 2009121255A1 CN 2009070654 W CN2009070654 W CN 2009070654W WO 2009121255 A1 WO2009121255 A1 WO 2009121255A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
request
mme
suspension
recovery
Prior art date
Application number
PCT/CN2009/070654
Other languages
English (en)
French (fr)
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 华为技术有限公司
Priority to JP2010516358A priority Critical patent/JP5031899B2/ja
Priority to EP09727131A priority patent/EP2146539A4/en
Publication of WO2009121255A1 publication Critical patent/WO2009121255A1/zh
Priority to US12/618,117 priority patent/US20100056147A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1043—Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H04W36/00224—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between packet switched [PS] and circuit switched [CS] network technologies, e.g. circuit switched fallback [CSFB]
    • H04W36/00226—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between packet switched [PS] and circuit switched [CS] network technologies, e.g. circuit switched fallback [CSFB] wherein the core network technologies comprise IP multimedia system [IMS], e.g. single radio voice call continuity [SRVCC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off

Definitions

  • the present invention relates to the field of mobile communication technologies, and in particular, to a method and a gateway agent for carrying suspend and resume.
  • the network side may suspend certain specific services or related bearers in the service processing process according to the operator policies in combination with user characteristics or service characteristics; When the network resources are restored, the corresponding service or bearer is restored to continue to use.
  • EUTRAN Evolved UMTS Terrestrial Radio Access Network
  • GERAN GSM/EDGE Radio Access Network
  • voice service is required.
  • Switching to the GERAN network ensures voice continuity, and the non-voice bearer resources of the user in the EUTRAN network need to be reserved to ensure that the user can continue the original service when switching back from the GERAN network to the EUTRAN network.
  • the embodiment of the present invention provides a method for bearer suspension, a method for bearer recovery, a gateway proxy, and a mobile communication system, so as to implement suspension and recovery of bearer resources.
  • the technical solution is as follows:
  • a method for carrying a suspension comprising: when a user equipment UE is switched by an evolved UMTS terrestrial radio access network EUTRAN to a GSM/EDGE radio access network GERAN, the gateway proxy receives a bearer suspension request sent by the mobility management entity MME, where The bearer suspension request carries the bearer identifier or the user identifier. According to the bearer suspension request, the bearer corresponding to the bearer identifier or the bearer corresponding to the user identifier is suspended.
  • a gateway agent including: a bearer suspension request receiving unit, configured to receive a bearer suspension request sent by the MME, where the bearer suspension request carries a bearer identifier or a user identifier;
  • the bearer suspension processing unit is configured to suspend the bearer corresponding to the bearer identifier or the bearer corresponding to the user identifier according to the bearer identifier or the user identifier carried in the bearer suspension request received by the bearer suspension request receiving unit.
  • a bearer recovery method includes: a gateway proxy receiving a bearer recovery request sent by an MME during a handover process of the UE from the GERAN to the EUTRAN or a tracking area update process or a service request process, where the bearer recovery request carries a bearer identifier or And the bearer corresponding to the bearer identifier or the bearer corresponding to the user identifier is restored according to the bearer recovery request.
  • a gateway agent including:
  • a bearer recovery request receiving unit configured to receive a bearer recovery request sent by the MME, where the bearer recovery request carries a bearer identifier or a user identifier;
  • the bearer recovery processing unit is configured to recover the bearer corresponding to the bearer identifier or the user identifier according to the bearer identifier or the user identifier carried in the bearer recovery request received by the bearer recovery request receiving unit.
  • a mobile communication system including an MME and a gateway agent
  • the MME is configured to send a bearer suspension request or a bearer recovery request to the gateway proxy, where the bearer suspension request or the bearer recovery request carries the bearer identifier or the user identifier;
  • gateway proxy is configured to suspend or restore the bearer corresponding to the bearer identifier or the bearer corresponding to the user identifier according to the bearer suspension request or the bearer recovery request sent by the MME.
  • the gateway agent When the network switching is performed, the gateway agent receives the bearer suspension request sent by the mobility management entity MME, and suspends the bearer corresponding to the specific service or the user identifier; when the network resource is restored, the gateway The proxy receives the bearer recovery request sent by the MME, and restores the bearer corresponding to the bearer or the user identifier of the specific service to continue to use, which solves the problem that the bearer suspension and recovery cannot be implemented in the prior art EUTRAN network.
  • FIG. 1 is a flow chart of a first embodiment of a method for implementing the present invention
  • 3 is a flow chart of implementing the third embodiment of the method of the present invention
  • 4 is a flow chart of implementing the fourth embodiment of the method of the present invention.
  • Figure 5 is a flow chart of implementing the fifth embodiment of the method of the present invention.
  • FIG. 6 is a flow chart of implementing the sixth embodiment of the method of the present invention.
  • FIG. 7 is a schematic structural diagram of a gateway proxy according to an embodiment of the present invention.
  • FIG. 8 is a flow chart of implementing the seventh embodiment of the method of the present invention.
  • FIG. 9 is a flow chart of implementing the eighth embodiment of the method of the present invention.
  • Figure 10 is a flow chart showing a specific embodiment 9 of the method of the present invention.
  • Figure 11 is a flow chart showing a tenth embodiment of the method of the present invention.
  • Figure 12 is a flow chart showing a specific embodiment 11 of the method of the present invention.
  • FIG. 13 is another schematic structural diagram of a gateway proxy according to an embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of a mobile communication system according to an embodiment of the present invention.
  • the method for implementing bearer suspension in the embodiment of the present invention includes: when the user equipment UE is switched by the evolved UMTS terrestrial radio access network EUTRAN to the GSM/EDGE radio access network GERAN, the gateway proxy receives the mobility management entity (MME). And a bearer suspension request sent by the Mobility Management Entity, where the bearer suspension request carries a bearer identifier or a user identifier, and the bearer corresponding to the bearer identifier or the bearer corresponding to the user identifier is suspended according to the bearer suspension request. .
  • MME mobility management entity
  • the MME may send a bearer suspension request to the gateway proxy according to the target network type and/or the user bearer type. For example, when the network side or the user needs to perform bearer suspension or bearer recovery operation for the bearer of different services, the MME is different.
  • the service maps different user bearer types, and determines which bearers need to be suspended or restored in combination with the target side network type, so that the bearer identification information of the bearers is included in the bearer suspension request; when all the bearers of the user need to be suspended,
  • the MME may also carry the user identification information in the bearer suspension request to indicate that all the bearers corresponding to the user identifier are suspended.
  • the gateway agent After receiving the bearer suspension request, when the gateway agent receives the data packets of the bearer, it caches or discards the data packet, and does not page the UE until the bearer is restored.
  • the MME may send a bearer suspension request to the gateway proxy after receiving the handover request message or after receiving the handover response message or after receiving the handover complete message, or may receive the voice continuity of the single access system.
  • the bearer pending request sent by the functional entity S-IWF, SR VCC - Inter Working Function
  • the request is forwarded to the gateway proxy.
  • the gateway agent may be a serving gateway (SGW, Serving Gateway) or packet data gateway (PGW, Packet Data Network Gateway) 0 when the gateway agent is a PGW, PGW receives MME through the SGW forwards the request to suspend the bearer.
  • SGW serving gateway
  • PGW Packet Data Network Gateway
  • the gateway agent may send a bearer pending response to the MME after the bearer is suspended.
  • the MME sends a bearer suspension response to the UE, and the UE does not send the uplink data of the suspended bearer according to the bearer suspension response.
  • the CSCF, ICCF/DTF, MGCF, and VCC-AS entities involved in the following embodiments are all network entities in the IP Multimedia Subsystem (IMS) domain.
  • IMS IP Multimedia Subsystem
  • the voice call can be anchored in the In the VCC-AS within the IMS domain.
  • the domain switching performed when the call is anchored in the IMS domain and switched is a prior art, and will not be described in the process description.
  • the gateway agent mentioned in the embodiment represents a gateway that can buffer a data packet for a user and can instruct the mobility management entity to page the user, and can also forward the data as a proxy.
  • the MME sends a message to notify the gateway proxy SGW to suspend the relevant bearer. After receiving the message, the SGW suspends the corresponding bearer, and then receives the corresponding data packet to be cached or discarded and no longer sends the page; when it needs to be suspended When the bearer resource is restored, the MME notifies the SGW to restore the corresponding bearer resource usage and can send a page.
  • the specific steps of the first embodiment are as follows:
  • the user equipment (UE, User Equipment) sends a measurement report to the eNodeB (evolved Node Base).
  • UE User Equipment
  • eNodeB evolved Node Base
  • the eNodeB decides to initiate the handover process based on the measurement report. Then, the handover request is sent to the source MME, and the message includes a source to target container, a target access network identifier, and the like from the source side to the target side.
  • the MME initiates a standard PS-PS handover procedure, and sends a forwarding handover request to the single-access system voice continuity function entity S-IWF (SR VCC - Inter Working Function), where the message carries the UE context information including the PGW address and the PGW. Tunnel ID (PGW TEID), SGW address, SGW tunnel ID (SGW TEID). 4.
  • S-IWF switches the voice bearer of the user and sends a preparation handover request to the target mobile switching center (VMSC, Visited Mobile Switching Center).
  • VMSC Visited Mobile Switching Center
  • the VMSC sends a handover request to the GERAN requesting resource allocation.
  • the GERAN sends a handover request response notification after the resource preparation is completed.
  • the VMSC resource preparation is completed.
  • the VMSC sends a ready to switch response to the S-IWF.
  • the S-IWF sends an Initial Address Message (IAM) to the VMSC. After receiving the IAM message, the VMSC sends an ACM (Address Complete Message) message to the S-IWF.
  • IAM Initial Address Message
  • ACM Address Complete Message
  • the S-IWF sends an IAM message carrying the VDN (VCC Domain Transfer Number) to establish an anchor to the IMS domain.
  • VDN VCC Domain Transfer Number
  • the Media Gateway Control Function MGCF, Media Gateway Control Function
  • ANM Answer Message
  • S-IWF sends and forwards the handover response notification.
  • the MME target side resource establishment is completed.
  • the MME sends a handover response notification to the eNodeB target side resource preparation.
  • the eNodeB sends a handover command to inform the UE to switch to the target network.
  • the UE switches to the target network and is detected by the target network.
  • the GERAN notifies the S-IWF that the handover is completed through the VMSC.
  • This step is optional. If the user is not registered to the HSS/HLR, the S-IWF needs to update the location information of the user in the HSS/HLR.
  • the S-IWF learns that the user handover is complete according to the step 12, and then sends a bearer suspension request to notify the MME to suspend the bearer, and the message carries the bearer identifier or the user identifier that needs to be suspended.
  • the MME After receiving the bearer suspension request, the MME forwards the request to the SGW, carrying the bearer identifier or user identifier that needs to be suspended. After receiving the request, the SGW places all the bearers corresponding to the bearer or the user identifier corresponding to the bearer identifier in a suspended state. After receiving the data packet of the corresponding bearer, the SGW caches or discards the data packet, and the user equipment The SGW does not send a paging procedure to page the user until the bearer is restored.
  • the SGW After the SGW suspends the corresponding bearer, it sends a bearer suspension response notification to the MME, and the message carries the cause value, indicating that the suspension is successful.
  • the MME sends a bearer suspension response to notify the S-IWF that the bearer suspension operation is complete, and the message carries the cause value, indicating that the suspension is successful.
  • Embodiment 2
  • the difference between this embodiment and the first embodiment is that after receiving the handover complete message sent by the S-IWF, the MME initiates a process of suspending the bearer. Specific steps are as follows:
  • the S-IWF notifies the MME that the user has switched to the target side.
  • the MME sends a handover complete response to the S-IWF.
  • the MME After the MME learns that the user has switched to the target network, the MME sends a bearer suspension request to the gateway proxy SGW, and the message carries the bearer identifier or user identifier that needs to be suspended. After receiving the request, the SGW suspends the corresponding bearer. After receiving the data packet, the SGW caches or discards the data packet, and for the user, the SGW does not send a paging procedure to page the user until the bearer recovers. until.
  • the SGW sends a bearer pending response, notifying the MME that the suspend operation is complete.
  • the gateway proxy in the system is
  • the bearer suspension request needs to be notified to the PGW, and the PGW suspends the relevant bearer.
  • the PGW caches or discards the data packet. Specific steps are as follows:
  • the MME sends a bearer suspension request to the SGW, and the message carries the bearer identifier or the user identifier that needs to be suspended.
  • the SGW After receiving the bearer suspension request, the SGW sends a bearer suspension request to the corresponding PGW, and the message carries the bearer identifier or user identifier that needs to be suspended. After receiving the request, the PGW suspends all the bearers corresponding to the bearer or the user identifier corresponding to the bearer identifier, and notifies the SGW that the bearer suspension operation is completed. The message carries the cause value, indicating that the bearer suspension succeeds.
  • the SGW sends a bearer suspension response message to notify that the MME bearer suspension operation is complete, and the message carries the cause value, indicating that the bearer suspension is successful.
  • the MME in this embodiment after receiving the forwarding handover response, the MME in this embodiment sends a message to the SGW. Host a pending request. There is no context relationship between this process and the subsequent processes. The specific steps are as follows: 1 - 8. The same as steps 1 - 8 in the first embodiment.
  • the MME After receiving the forwarding handover response message, the MME sends a bearer suspension request, and the message carries the bearer identifier or user identifier that needs to be suspended.
  • the SGW suspends all the bearers corresponding to the bearer or the user identifier corresponding to the bearer identifier, that is, after receiving the data packet of the bearer, the data packet is cached or discarded, and the process does not initiate a process search. Call the user.
  • the MME sends a handover response to the eNodeB, and carries a circuit domain coverage CS coverage indication to the UE in the non-access stratum message (NAS, Non Access stratum) message, and indicates that other service bearers of the UE have been suspended by the circuit domain coverage indication. Or carry the bearer ID that needs to be suspended, and inform the UE that the relevant bearer has been suspended.
  • NAS Non Access stratum
  • the eNodeB sends a handover command to the UE, and the message carries the CS coverage indication or the bearer identifier. After receiving the message, the UE does not send the uplink data of the suspended bearer. It should be noted that: Notifying the UE that the bearer is suspended is an option, because the UE can know whether the current network is GERAN or UTRAN or EUTRAN, and combines its own network processing capability to determine whether an uplink packet can be sent.
  • Embodiment 5 Same as steps 11 - 13 in the first embodiment. Embodiment 5
  • the difference between this embodiment and the fourth embodiment is that the time points at which the bearer suspension process occurs are different.
  • the MME when the MME receives the handover request sent by the eNodeB, the MME initiates a bearer suspension request to the SGW, and the SGW performs a corresponding operation according to the received bearer suspension request, and suspends the bearer. Specific steps are as follows:
  • MME initiated bearer suspend operation which is the same as 9 and 10 in the fourth embodiment. It should be noted that: If the PGW acts as a gateway proxy, that is, for the user in the idle state, the data is cached on the PGW, and the bearer suspension request needs to notify the PGW at this time.
  • the function of the 5-IFF is integrated in the VMSC and becomes the new network entity IMSC (target side).
  • the MME informs the SGW to suspend the bearer that needs to be suspended.
  • This embodiment is basically the same as the first embodiment. Referring to FIG. 6, the message processing between the S-IWF and the VMSC is internal processing, which is not shown in the figure. Specific steps are as follows:
  • the IMSC needs to anchor the call in the domain function entity (DFF, Domain Transfer Function) of the IMS domain.
  • DFF Domain Transfer Function
  • the corresponding steps in the first embodiment are different in that the interaction between the S-IWF and the VMSC is not described in the internal interaction, and the interaction between the S-IWF and the MME is converted into an interaction process between the IMSC and the MME.
  • the S-IWF can also be integrated in the source side MSC or integrated on the source side.
  • An embodiment of the present invention provides a gateway proxy, as shown in FIG. 7, including:
  • the bearer suspension request receiving unit 701 is configured to receive a bearer suspension request sent by the MME, where the bearer suspension request carries a bearer identifier or a user identifier.
  • the bearer suspending processing unit 702 is configured to suspend the bearer corresponding to the bearer or the user identifier corresponding to the bearer identifier or the user identifier carried in the received bearer suspension request.
  • the bearer suspension unit may further include:
  • a bearer receiving subunit configured to receive a data packet that is carried
  • a determining subunit configured to determine whether the received bearer is a bearer corresponding to the bearer suspension request received by the bearer suspension request receiving unit, and notifying the processing subunit of the determination result;
  • the processing sub-unit is configured to cache or discard the data packet of the bearer when the received bearer is the bearer corresponding to the bearer request, and no longer page the user equipment UE.
  • the gateway proxy may further include a bearer suspension response sending unit 703, configured to After the suspend is completed, a 7
  • a bearer suspension response sending unit 703 configured to After the suspend is completed, a 7
  • the MME when the user equipment is switched from EUTRAN to GERAN, the MME sends a bearer suspension request to the gateway proxy, suspending the bearer that needs to be suspended, so that the user's network resources in the EUTRAN can be reserved, so that the user equipment is When switching from GERAN back to EUTRAN, the corresponding bearer can be quickly restored, thereby continuing the service in EUTRAN faster.
  • the embodiment of the present invention further provides a method for implementing bearer recovery, including: when a UE is switched from GERAN to EUTRAN or during a tracking area update process or a service request, the gateway proxy receives the MME sending
  • the bearer recovery request carries the bearer identifier or the user identifier, and the bearer corresponding to the bearer identifier or the user identifier is restored according to the bearer recovery request.
  • the MME may send a bearer recovery request to the gateway proxy according to the target network type and/or the user bearer type. For example, when the network side or the user needs to perform bearer suspension or bearer recovery operation for the bearer of different services, the MME performs different services according to different services. Mapping different user bearer types, and determining which bearers need to be suspended or restored in combination with the target side network type, so that the bearer identification information of the bearers is included in the bearer recovery request; when all the bearers of the user need to be restored, the MME may also The bearer recovery request carries the user identifier information to indicate that all bearers corresponding to the user identifier are restored.
  • the MME may send a bearer recovery request to the gateway proxy after receiving the handover preparation message or after receiving the tracking area update request message or the service request message.
  • the gateway agent may be an SGW or a PGW.
  • the gateway proxy is PGW, the PGW receives
  • the bearer resumes the request that the MME forwards through the SGW.
  • the gateway agent may send a bearer recovery response to the MME after the bearer is recovered.
  • the MME sends a bearer recovery response to the UE, notifying the UE that the bearer has been recovered.
  • the S-IWF notifies the MME to perform handover resource preparation, and the MME then notifies the SGW to restore the suspended bearer, and then the user switches to the EUTRAN network, and the resumed bearer can continue the service. See Figure 8, the specific steps are as follows: 1. The UE reports the measurement report to GERAN.
  • the GERAN decides to initiate a handover according to the measurement report reported by the UE, and then sends a handover request to the VMSC.
  • the VMSC sends a sub-switch preparation request to the S-IWF according to the target cell identity, and notifies the CS-CS handover process.
  • the S-IWF sends a handover request notification.
  • the MME performs handover resource preparation.
  • the MME finds that the bearer of the user is in a suspended state, and then sends a bearer recovery request to the SGW, carrying the bearer identifier or user identifier that needs to be restored, and notifying the SGW to resume the bearer.
  • the SGW restores the related bearer according to the bearer identifier or the user identifier sent by the MME, and sends a bearer recovery response to notify the MME that the bearer recovery is successful.
  • the MME sends a handover preparation response notification.
  • the S-IWF source side resource preparation is completed.
  • the S-IWF notifies GERAN through the VMSC that the target side resources are ready to be completed.
  • the GERAN sends a handover command to inform the user to switch to the EUTRAN network.
  • the call is anchored to the IMS network.
  • this embodiment implements a bearer recovery operation when a user switches from the GERAN network back to the EUTRAN network through a Tracking Area Update (TAU) process.
  • TAU Tracking Area Update
  • the UE switches back from the GERAN network to the EUTRAN network.
  • the user sends a TAU request to the eNodeB.
  • the eNodeB forwards the TAU request to the MME according to the Globally Unique Temporary Identity (GUTI).
  • GUI Globally Unique Temporary Identity
  • Part of the non-critical process is omitted in the middle.
  • the MME sends a bearer recovery request to the SGW, and the message carries the user identifier, and the identifier confirms that all bearers related to the user identifier need to be restored (or the bearer identifier is carried in the message), and the SGW identifies all bearers that need to be restored by using the identifier.
  • the SGW recovers the corresponding bearer and sends a bearer recovery response to the MME.
  • the network side MME sends a tracking area update accept message to the UE, where the message carries the GUTI and the tracking area list (TAList).
  • the UE sends a tracking area update complete message to the network side MME, indicating that the GUTI value has been received.
  • a bearer recovery operation when a user is switched back to the EUTRAN network by the GERAN network is completed through a service request (Service Request) process.
  • Service Request Service Request
  • the UE is switched back to the EUTRAN network by the GERAN network.
  • the UE sends a service request message to the eNodeB, and the message carries the bearer recovery flag ( Resume
  • the flag indicates that the MME initiates a recovery bearer operation.
  • the eNodeB forwards the request to the MME, and the message also carries a bearer recovery flag, by which the MME is instructed to restore all suspended bearers.
  • the authentication process is completed between the UE, the MME, and the HSS. This step is optional.
  • the MME sends a bearer recovery request to the SGW, and the message carries the bearer identifier (or the user identifier, and the SGW is mapped to all the bearer identifiers associated with the user), and the SGW is notified to restore the bearer corresponding to the identifier.
  • the SGW restores all the bearers related to the user, that is, the user data packet or the paging user is accepted, and the bearer recovery response is sent to the MME, and the MME is notified that the bearer recovery operation is completed.
  • the MME sends an initial context setup request message to the eNodeB, where the message carries bearer context information and Bearer Resume Complete Indication.
  • the eNodeB initiates a radio bearer setup process, and carries the bearer recovery completion identifier in the process, and informs the UE that the bearer has been restored, and the uplink route is already opened.
  • the user sends the upstream data to the SGW (or PGW).
  • the eNodeB sends an initial context setup complete message to the MME, where the message carries the bearer context information.
  • the MME sends an update bearer context request to the SGW, where the message carries bearer context information and a radio access type (RAT, Radio Access Type) o
  • RAT Radio Access Type
  • the SGW compares the last RAT Type with the current RAT Type. If a change occurs, it is required. Notify the PGW to update the RAT Type.
  • the SGW sends an Update Bearer Context Response to the MME.
  • this embodiment performs the bearer recovery operation when the user switches from the GERAN network back to the EUTRAN network through the Service Request process.
  • the difference from the ninth embodiment is that the recovery operation needs to notify the PGW, so that the PGW does not send downlink data. Packet or accept upstream packets. Specific steps are as follows:
  • the MME sends a bearer recovery request to the SGW, where the message carries a PGW address, a bearer identifier, or a user identifier.
  • the message is used to inform the SGW to resume the use of the corresponding bearer and accept the paging.
  • the SGW continues to send a bearer recovery request to the PGW, where the message carries the bearer identifier or the user identifier, and the PGW is notified to resume the use of the corresponding bearer.
  • the SGW notifies the MME that the bearer recovery is complete, and the message carries the bearer recovery complete identifier.
  • the function of the S-IWF is integrated in the VMSC and becomes the new network entity IMSC.
  • this embodiment is basically the same as the seventh embodiment. The difference is that the interaction between the S-IWF and the VMSC is not described in the internal interaction, and the interaction between the S-IWF and the MME is transformed into an interaction between the IMSC and the MME.
  • the S-IWF may also be integrated in the source side MSC or integrated in the source side MSC and the target side MSC, which do not affect the implementation of the present invention.
  • the solution in this embodiment can be extended to any of the above bearer recovery embodiments.
  • the embodiment of the present invention provides a gateway proxy, see As shown in Figure 13, it includes:
  • the bearer recovery request receiving unit 1301 is configured to receive a bearer recovery request sent by the MME, where the bearer recovery request carries a bearer identifier or a user identifier.
  • the bearer recovery processing unit 1302 is configured to restore, according to the bearer identifier or the user identifier carried in the received bearer recovery request, the bearer corresponding to the bearer or the user identifier corresponding to the bearer identifier.
  • the gateway proxy may further include a bearer recovery response sending unit 1303, configured to send a bearer recovery response to the MME after the bearer recovery is completed.
  • a bearer recovery response sending unit 1303 configured to send a bearer recovery response to the MME after the bearer recovery is completed.
  • the embodiment of the present invention further provides a mobile communication system, as shown in FIG. 14, which is composed of the following parts:
  • the MME 1401 is configured to send a bearer suspension request or a bearer recovery request, where the request message carries a bearer identifier or a user identifier.
  • the gateway proxy 1402 suspends or restores the bearer corresponding to the bearer identifier or the bearer corresponding to the user identifier according to the bearer suspension request or the bearer recovery request sent by the MME. After the bearer is suspended or resumed, a response message is sent to the MME.
  • the gateway agent can be either an SGW or a PGW.
  • the operator may suspend certain services or bearers according to the policy or the service requirement, but does not release the network resources of the user in the EUTRAN, so that the service or the bearer needs to be restored. It can be quickly restored to give users a better experience.
  • the non-voice bearer resources of the EUTRAN network are reserved, so that when the user switches back from the GERAN network to the EUTRAN network, the network resources can be re-established in the EUTRAN network.
  • the corresponding bearer resources are restored more quickly, thereby continuing the service originally in the EUTRAN network and ensuring the continuity of the voice service.
  • the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed.
  • the foregoing steps include the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

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

Description

承载挂起的方法、 承载恢复的方法及网关代理
本申请要求于 2008 年 4 月 3 日提交中国专利局、 申请号为 200810091609.9、发明名称为 "承载挂起的方法、承载恢复的方法及网关代理" 的中国专利申请的优先权， 其全部内容通过引用结合在本申请中。
技术领域
本发明涉及移动通信技术领域，特别是涉及承载挂起和恢复的方法及网关 代理。
背景技术
在无线演进网络中， 为了给终端用户带来更优的体验和服务， 网络侧可以 根据运营商策略结合用户特点或者业务特点，在业务处理过程中，将某些特定 业务或者相关承载挂起； 在网络资源恢复时，将相应业务或者承载恢复以继续 使用。如单接入系统语音连续性 ( SR VCC, Single Radio Voice Call Continuity ) 业务。
当正在进行语音业务的用户从演进 UMTS陆地无线接入网 （ EUTRAN, Evolved UMTS Terrestrial Radio Access Network )切换到 GSM/EDGE无线接入 网 （GERAN, GSM/EDGE Radio Access Network )时， 需要将语音业务切换到 GERAN网络保证语音连续性， 同时用户在 EUTRAN网络的非语音承载资源 需要保留 , 以保证用户后续从 GERAN网络切换回 EUTRAN网络时可以继续 原来的业务。 但是在现有技术中， 暂时还没有将 EUTRAN网络中承载挂起和 恢复的解决方法。
发明内容
有鉴于此， 本发明实施例提供了承载挂起的方法、承载恢复的方法、 网关 代理和移动通信系统， 以实现承载资源的挂起和恢复， 技术方案如下：
一种承载挂起的方法， 包括： 当用户设备 UE由演进 UMTS陆地无线接入 网 EUTRAN向 GSM/EDGE无线接入网 GERAN切换时 ,网关代理接收移动管 理实体 MME发送的承载挂起请求，所述承载挂起请求中携带承载标识或用户 标识；根据所述承载挂起请求，将所述承载标识对应的承载或用户标识对应的 承载挂起。
一种网关代理， 包括： 承载挂起请求接收单元， 用于接收 MME发送的承载挂起请求， 所述承载 挂起请求中携带承载标识或用户标识；
承载挂起处理单元，用于根据所述承载挂起请求接收单元接收到的承载挂 起请求中携带的承载标识或用户标识，将所述承载标识对应的承载或用户标识 对应的承载挂起。
一种承载恢复的方法， 包括： 在 UE由 GERAN向 EUTRAN切换过程中 或跟踪区更新过程中或服务请求过程中 , 网关代理接收 MME发送的承载恢复 请求，所述承载恢复请求中携带承载标识或用户标识；根据所述承载恢复请求， 将所述承载标识对应的承载或用户标识对应的承载恢复。
一种网关代理， 包括：
承载恢复请求接收单元， 用于接收 MME发送的承载恢复请求， 所述承载 恢复请求中携带承载标识或用户标识；
承载恢复处理单元，用于根据所述承载恢复请求接收单元接收到的承载恢 复请求中携带的承载标识或用户标识，将所述承载标识对应的承载或用户标识 对应的 载恢复。
一种移动通信系统， 包括 MME及网关代理；
所述 MME, 用于向网关代理发送承载挂起请求或承载恢复请求， 所述承 载挂起请求或承载恢复请求中， 携带承载标识或用户标识；
所述网关代理， 用于根据 MME发送的承载挂起请求或承载恢复请求， 将 所述承载标识对应的承载或用户标识对应的承载挂起或恢复。
应用上述技术方案，可以在用户进行网络切换时， 网关代理接收移动管理 实体 MME发送的承载挂起请求，将某些特定业务的承载或者用户标识对应的 承载挂起； 在网络资源恢复时， 网关代理接收 MME发送的承载恢复请求， 将 某些特定业务的承载或者用户标识对应的承载恢复以继续使用，解决了现有技 术 EUTRAN网络中不能实现承载挂起和恢复的问题。
附图说明
图 1为实现本发明方法具体实施例一的流程图；
图 2为实现本发明方法具体实施例二的流程图；
图 3为实现本发明方法具体实施例三的流程图； 图 4为实现本发明方法具体实施例四的流程图
图 5为实现本发明方法具体实施例五的流程图
图 6为实现本发明方法具体实施例六的流程图
图 7为本发明实施例的网关代理的一种结构示意图；
图 8为实现本发明方法具体实施例七的流程图
图 9为实现本发明方法具体实施例八的流程图
图 10为实现本发明方法具体实施例九的流程图；
图 11为实现本发明方法具体实施例十的流程图；
图 12为实现本发明方法具体实施例十一的流程图；
图 13为本发明实施例的网关代理的另一种结构示意图；
图 14为本发明实施例的移动通信系统的架构示意图。
具体实施方式
首先对本发明实施例的承载挂起的实现方法进行说明， 包括： 当用户设备 UE 由演进 UMTS 陆地无线接入网 EUTRAN 向 GSM/EDGE 无线接入网 GERAN切换时， 网关代理接收移动管理实体 （MME， Mobility Management Entity)发送的承载挂起请求， 所述承载挂起请求中携带承载标识或用户标识； 根据所述承载挂起请求 ,将所述承载标识对应的承载或用户标识对应的承载挂 起。
其中， MME可以根据目标网络类型和 /或用户承载类型， 向网关代理发送 承载挂起请求， 例如， 当网络侧或者用户需要针对不同业务的承载做承载挂起 或者承载恢复操作时， MME根据不同业务映射不同的用户承载类型， 再结合 目标侧网络类型判断需要将哪些承载挂起或者恢复，从而在承载挂起请求中包 括这些承载的承载标识信息； 当用户所有的承载均需要挂起时， MME也可以 在承载挂起请求中携带用户标识信息， 以表示将用户标识对应的所有承载挂 起。
在收到承载挂起请求后， 当网关代理收到这些承载的数据包后，緩存或者 丢弃该数据包， 并且不再寻呼 UE, 直到承载恢复为止。
MME可以在收到切换请求消息后或收到切换响应消息后或收到切换完成 消息后， 向网关代理发送承载挂起请求，也可以在收到单接入系统语音连续性 功能实体（ S-IWF , SR VCC - Inter Working Function )发送的承载挂起请求之 后， 向网关代理转发该请求。
所述网关代理可以是服务网关 （SGW, Serving Gateway )或分组数据网 关 （PGW， Packet Data Network Gateway )0 当网关代理为 PGW时， PGW接 收 MME经过 SGW转发的承载挂起请求。
网关代理可以在承载挂起之后 , 向 MME发送承载挂起响应。 MME将承 载挂起响应发送至 UE, UE根据所述承载挂起响应， 不再发送已经挂起的承 载的上行数据。
以下实施例附图中涉及到的 CSCF、 ICCF/DTF、 MGCF、 VCC-AS实体都 属于 IP多媒体子系统（IMS, IP Multimedia Subsystem )域的网络实体， 本发 明实施例中语音呼叫可以锚定在 IMS域内的 VCC-AS中。而将呼叫锚定在 IMS 域和切换时进行的域切换都是现有技术， 流程说明中不做赘述。
实施例中提到的网关代理，表示可为用户緩存数据包并可指示移动性管理 实体寻呼用户的网关， 也可以作为代理转发数据。
下面结合图 1至图 6, 介绍承载挂起的几种实施例。
实施例一
MME发送消息通知网关代理 SGW挂起相关承载， SGW收到该消息后将 相应的承载挂起， 此后收到相应的数据包会被緩存或丢弃并且不再发送寻呼； 当需要将挂起的承载资源恢复时， MME通知 SGW恢复相应的承载资源使用 并可以发送寻呼。 参见图 1所示， 实施例一的具体步骤如下：
1. 用户设备 ( UE , User Equipment )发送测量报告给演进基站（ eNodeB , Evolved Node Base )。
2. eNodeB根据测量报告决定发起切换流程。 于是发送切换请求给源侧 MME, 消息中包含源侧给目标侧的内容容器（ source to target container )， 目标 接入网标识等。
3. MME发起标准的 PS - PS切换流程， 向单接入系统语音连续性功能实 体 S-IWF ( SR VCC - Inter Working Function )发送转发切换请求 , 消息中携带 UE的上下文信息包括 PGW地址、 PGW隧道标识（ PGW TEID )、 SGW地址、 SGW隧道标识（ SGW TEID )。 4. S-IWF切换用户的语音承载并发送准备切换请求给目标侧移动交换中 心 ( VMSC, Visited Mobile Switching Center )„
5. VMSC发送切换请求给 GERAN请求资源分配。 GERAN在资源准备 结束后发送切换请求应答通知 VMSC资源准备结束。
6. VMSC发送准备切换响应给 S-IWF。
7. S-IWF发送初始地址消息（IAM, Initial Address Message )到 VMSC, VMSC收到 IAM消息后回发地址全消息 （ ACM, Address Complete Message ) 消息给 S-IWF。
7a. S-IWF发送 IAM消息 , 携带 VDN ( VCC Domain Transfer Number )建 立到 IMS 域的锚定。 媒体网关控制功能 （MGCF , Media Gateway Control Function )转发 IAM和应答消息（ ANM, Answer Message )给 VCC-AS和 S-IWF。
8. S-IWF发送转发切换响应通知 MME目标侧资源建立完成。
9. MME发送切换响应通知 eNodeB目标侧资源准备完成。
10. eNodeB发送切换命令通知 UE切换到目标网络。
11. UE切换到目标网络并被目标网络检测。
12. GERAN通过 VMSC通知 S-IWF切换完成。
13. 该步骤可选， 如果用户没有注册到 HSS/HLR中， 此时 S-IWF需要更 新 HSS/HLR中用户的位置信息。
14. S-IWF根据步骤 12得知用户切换完成， 于是发送承载挂起请求通知 MME挂起承载， 该消息中携带需要挂起的承载标识或用户标识。
15. MME收到 S-IWF发送承载挂起请求后， 转发该请求给 SGW, 携带 需要挂起的承载标识或用户标识。 SGW收到该请求后， 将承载标识对应的承 载或者用户标识对应的全部承载置于挂起状态 , 当收到相应承载的数据包后 , SGW会緩存或者丢弃该数据包， 并且对于该用户来讲 SGW不会发送寻呼流 程来寻呼用户一直到承载恢复为止。
16. SGW将相应的承载挂起后发送承载挂起响应通知 MME, 消息中携带 原因值， 告知挂起成功。
17. MME发送承载挂起响应通知 S-IWF承载挂起操作完成， 消息中携带 原因值， 告知挂起成功。 实施例二
参见图 2所示， 本实施例与实施例一的不同之处在于 MME收到 S-IWF 发送的切换完成消息之后， 发起将承载挂起的流程。 具体步骤如下：
1 - 13. 同实施例一中步骤 1 - 13所述。
14. S-IWF通知 MME用户已经切换到目标侧。
15. MME发送切换完成响应给 S-IWF。
16. MME得知用户切换到目标网络后， 于是发送承载挂起请求给网关代 理 SGW, 消息中携带需要挂起的承载标识或用户标识。 SGW收到该请求后， 将相应的承载挂起， 当收到数据包后， SGW緩存或者丢弃该数据包， 并且对 于该用户来讲 SGW不会发送寻呼流程来寻呼用户， 直到承载恢复为止。
17. SGW发送承载挂起响应， 通知 MME挂起操作完成。 实施例三
参见图 3所示，本实施例与实施例二的不同之处在于， 系统中网关代理为
PGW, 则承载挂起请求需要通知到 PGW, 由 PGW将相关承载挂起， PGW收 到数据包后会緩存或者丢弃。 具体步骤如下：
1 - 15. 同实施例二中步骤 1 - 15所述。
16. MME发送承载挂起请求至 SGW, 消息中携带需要挂起的承载标识或 用户标识。
17. SGW接收到承载挂起请求后， 发送承载挂起请求到相应的 PGW, 消 息中携带需要挂起的承载标识或用户标识。 PGW收到该请求后， 将承载标识 对应的承载或者用户标识对应的全部承载挂起， 并通知 SGW承载挂起操作完 成， 消息中携带原因值， 表示承载挂起成功。
18. SGW发送承载挂起响应消息通知 MME承载挂起操作完成， 消息中 携带原因值， 表示承载挂起成功。 实施例四
参见图 4所示， 本实施例 MME在收到转发切换响应后， 向 SGW发送将 承载挂起的请求。 该过程和后面的流程没有前后时序关系。 具体步骤如下： 1 - 8. 同实施例一中步骤 1 - 8所述。
9. MME 收到转发切换响应消息后， 发送承载挂起请求， 消息中携带需 要挂起的承载标识或用户标识。
10. SGW收到承载挂起请求后， 于是将承载标识对应的承载或者用户标 识对应的全部承载挂起， 即收到上述承载的数据包后会緩存或者丢弃数据包， 同时不会发起流程寻呼该用户。
11. MME发送切换响应给 eNodeB,并在非接入层消息（NAS， Non Access stratum )消息中携带电路域覆盖 CS covered指示给 UE, 通过电路域覆盖指示 表明该 UE 的其他业务承载已经挂起； 或者携带需要挂起的承载标识， 告知 UE相关承载已经挂起。
12. eNodeB发送切换命令给 UE, 消息中携带 CS covered指示或者挂起 承载标识， UE收到该消息后不会再发送已经挂起的承载的上行数据。 需要说 明的是： 通知 UE承载挂起属于可选项， 因为 UE可以通过广 ^言息获知当前 的网络是 GERAN还是 UTRAN又或者是 EUTRAN , 结合自己的网络处理能 力， 判断是否可以发送上行数据包。
13 - 15. 同实施例一中步骤 11 - 13所述。 实施例五
参见图 5所示，本实施例与实施例四的区别在于发生承载挂起的流程的时 间点不同。 本实施例在 MME收到 eNodeB发送的切换请求时即向 SGW发起 承载挂起请求， SGW根据收到的承载挂起请求做相应操作， 将承载挂起。 具 体步骤如下：
I - 2. 同实施例一中步骤 1 - 2所述。
3 - 4. MME发起的承载挂起操作， 该步骤和实施例四中的 9和 10所作 的操作相同。 需要说明的是： 如果 PGW作为网关代理， 即对于空闲态的用户 来讲数据緩存在 PGW上， 则此时承载挂起请求需要通知 PGW。
5 - 10. 同实施例一中步骤 3 - 8所述。
II - 12. 同实施例四中步骤 11 - 12所述。 13 - 15. 同实施例一中步骤 11 - 13所述。 实施例六
5- IWF的功能集成在 VMSC中， 成为新的网络实体 IMSC (目标侧）， 则 当 IMSC发送切换完成命令时， MME通知 SGW将需要挂起的承载挂起。本 实施例与实施例一基本相同， 参见图 6所示， S-IWF和 VMSC之间的消息处 理属于内部处理， 在图中没有体现。 具体步骤如下：
1 - 3. 同实施例一中步骤 1 - 3所述。
4. 为用户接入， 目标侧做资源准备。
5. 在目标侧资源准备完成后， IMSC需要将呼叫锚定在 IMS域的域功能 实体 ( DTF, Domain Transfer Function ) 中。
6 - 13. 同实施例一中的相应步骤， 不同之处在于 S-IWF和 VMSC的交互 属于内部交互不做描述，并且 S-IWF与 MME的交互转化为 IMSC和 MME的 交互处理。
需要说明的是， S-IWF也可以集成于源侧 MSC中， 或者同时集成于源侧
MSC和目标侧 MSC中， 这些都不影响本发明的实现。本实施例所述方案可以 推广到以上任意承载挂起实施例中。
本发明实施例提供了一种网关代理， 参见图 7所示， 包括：
承载挂起请求接收单元 701 , 用于接收 MME发送的承载挂起请求， 承载 挂起请求中携带有承载标识或用户标识。
承载挂起处理单元 702, 用于根据接收到的承载挂起请求中携带的承载标 识或用户标识， 将所述 载标识对应的^载或用户标识对应的^载挂起。
其中， 承载挂起单元还可以进一步包括：
承载接收子单元， 用于接收承载的数据包；
判断子单元，用于判断接收到的承载是否为承载挂起请求接收单元接收到 的承载挂起请求中对应的承载， 并将判断结果通知处理子单元；
处理子单元， 用于当接收到的承载是承载挂起请求中对应的承载时，緩存 或者丢弃该承载的数据包， 并且不再寻呼用户设备 UE。
优选地， 所述网关代理还可以包括承载挂起响应发送单元 703， 用于在承 载挂起完成之后， 向 MME发送 7|载挂起响应。
通过以上技术方案， 当用户设备由 EUTRAN到 GERAN切换时 , 由 MME 向网关代理发送承载挂起请求，将需要挂起的承载挂起，这样就可以保留用户 在 EUTRAN的网络资源 ,使得用户设备在从 GERAN切换回 EUTRAN时 , 能 够迅速将相应的承载恢复 , 从而更快地继续原来在 EUTRAN的业务。
除上述承载挂起的实施例外 , 本发明实施例还提供承载恢复的实现方法， 包括： 在 UE由 GERAN向 EUTRAN切换过程中或跟踪区更新过程中或服务 请求过程中， 网关代理接收 MME发送的承载恢复请求， 所述承载恢复请求中 携带承载标识或用户标识；根据所述承载恢复请求，将所述承载标识对应的承 载或用户标识对应的^载恢复。
其中， MME可以根据目标网络类型和 /或用户承载类型， 向网关代理发送 承载恢复请求， 例如， 当网络侧或者用户需要针对不同业务的承载做承载挂起 或者承载恢复操作时， MME根据不同业务映射不同的用户承载类型， 再结合 目标侧网络类型判断需要将哪些承载挂起或者恢复，从而在承载恢复请求中包 括这些承载的承载标识信息； 当用户所有的承载均需要恢复时， MME也可以 在承载恢复请求中携带用户标识信息，以表示将用户标识对应的所有承载进行 恢复。
MME可以在收到切换准备消息后或收到跟踪区更新请求消息后或服务请 求消息后， 向网关代理发送承载恢复请求。
所述网关代理可以是 SGW或 PGW。 当网关代理为 PGW时， PGW接收
MME经过 SGW转发的承载恢复请求。
网关代理可以在承载恢复之后 , 向 MME发送承载恢复响应。 MME将承 载恢复响应发送至 UE, 通知 UE承载已恢复。
下面结合图 8至图 12, 介绍承载恢复的几个实施例。
实施例七
当用户由 GERAN网络切换回 EUTRAN网络时， 在切换资源准备阶段，
S-IWF通知 MME做切换资源准备， MME于是通知 SGW将挂起的承载恢复， 随后用户切换到 EUTRAN网络， 即可利用已恢复的承载继续业务。 参见图 8 所示， 具体步骤如下： 1. UE上报测量报告给 GERAN。
2. GERAN根据 UE上报的测量报告决定发起切换， 于是发送切换请求给 VMSC。
3. VMSC根据目标小区标识发送子切换准备请求给 S-IWF,通知进行 CS - CS的切换流程。
4. S-IWF发送切换请求通知 MME做切换资源准备。
5. MME发现该用户的承载处于挂起状态， 于是发送承载恢复请求给 SGW, 携带需要恢复的承载标识或用户标识， 通知 SGW恢复承载。
6. SGW根据 MME发送的承载标识或者用户标识， 将相关承载恢复正常 并发送承载恢复响应， 通知 MME承载恢复成功。
7. MME发送切换准备响应通知 S-IWF源侧资源准备完成。
8 - 9. S-IWF通过 VMSC通知 GERAN, 目标侧资源准备完成。
10. GERAN发送切换命令通知用户切换到 EUTRAN网络。
11. 用户切换到 EUTRAN网络后 , 将呼叫锚定在 IMS网络。
12. S-IWF释放源侧资源。 实施例八
参见图 9所示， 本实施例通过跟踪区更新（TAU, Tracking Area Update ) 流程完成用户由 GERAN网络切换回 EUTRAN网络时的承载恢复操作。 具体 步骤如下：
1. UE从 GERAN网络切换回 EUTRAN网络。
2a. 用户发送 TAU请求给 eNodeB。
2b. eNodeB才艮据全局唯一临时标识（GUTI, Globally Unique Temporary Identity )转发该 TAU请求到 MME。
中间省略部分非关键流程。
3. MME发送承载恢复请求到 SGW, 消息中携带该用户标识， 通过该标 识确认需要恢复该用户标识相关的所有承载 （或者消息中携带承载标识）， SGW通过该标识确认需要恢复的全部承载。
4. SGW将相应承载恢复， 并发送承载恢复响应到 MME。 5. 网络侧 MME发送跟踪区更新接受消息给 UE, 消息中携带 GUTI和跟 踪区列表（TAList )。
6. UE发送跟踪区更新完成消息给网络侧 MME, 表示已经接收到 GUTI 值。 实施例九
参见图 10所示， 本实施例通过服务请求（Service Request )流程完成用户 由 GERAN网络切换回 EUTRAN网络时的承载恢复操作。 具体步骤如下：
I. UE由 GERAN网络切换回 EUTRAN网络。
2a. UE发送服务请求消息给 eNodeB, 消息中携带承载恢复标志（ Resume
Bearer Indication )， 通过该标志指示 MME发起恢复承载操作。
2b. eNodeB转发该请求到 MME, 消息中同样携带承载恢复标志， 通过 该标志指示 MME恢复所有被挂起的承载。
3. UE、 MME和 HSS之间完成认证过程， 该步骤可选。
4. MME发送承载恢复请求到 SGW, 消息中携带承载标识（或者用户标 识， SGW ^居用户标识映射到所有跟该用户相关的承载标识）， 通知 SGW恢 复标识对应的承载。
5. SGW将该用户相关的承载全部恢复， 即可接受该用户数据包或寻呼用 户， 发送承载恢复响应给 MME, 通知 MME承载恢复操作完成。
6. MME发送初始上下文建立请求消息给 eNodeB, 消息中携带承载上下 文信息和承载恢复完成标识 ( Bearer Resume Complete Indication)。
7. eNodeB发起无线承载建立流程， 在该流程中携带承载恢复完成标识， 告知 UE承载已经恢复， 此时上行路线已经打通。
8. 用户发送上行数据到 SGW (或 PGW )。
9. eNodeB发送初始上下文建立完成消息给 MME, 消息中携带承载上下 文信息。
10. MME发送更新承载上下文请求给 SGW, 消息中携带承载上下文信息 和无线接入类型 （RAT, Radio Access Type )o
II. SGW比较上次 RAT Type和本次 RAT Type, 如果发生改变， 则需要 通知 PGW更新 RAT Type。
12. SGW发送更新承载上下文响应给 MME。 实施例十
参见图 11所示， 本实施例通过 Service Request流程完成用户由 GERAN 网络切换回 EUTRAN网络时的承载恢复操作， 与实施例九的不同之处在于恢 复操作需要通知 PGW, 从而 PGW不会发送下行数据包或者接受上行数据包。 具体步骤如下：
1 - 3. 同实施例九中步骤 1 - 3所述。
4. MME发送承载恢复请求给 SGW, 消息中携带 PGW地址、 承载标识 或者用户标识。 通过该消息告知 SGW恢复相应承载的使用， 并可接受寻呼。
5. SGW继续向 PGW发送承载恢复请求， 消息中携带承载标识或者用户 标识， 通知 PGW恢复相应承载的使用。
6. PGW恢复相关承载使用后， 通知 SGW承载恢复完成， 消息中携带承 载恢复完成标识。
7. SGW通知 MME承载恢复完成， 消息中携带承载恢复完成标识。
8 - 14. 同实施例九中的步骤 6 - 12。 实施例十一
S-IWF的功能被集成在 VMSC中，成为新的网络实体 IMSC, 则当用户由
GERAN网络切换回 EUTRAN网络时 , 在切换资源准备阶段， 由 IMSC通知 MME做切换资源准备， MME于是通知 SGW将挂起的承载恢复， 随后用户切 换到 EUTRAN网络， 即可利用已恢复的承载继续业务。 参见图 12所示， 本实 施例与实施例七基本相同。 不同之处在于 S-IWF和 VMSC的交互属于内部交 互不做描述， 并且 S-IWF与 MME的交互转化为 IMSC和 MME的交互处理。
需要说明的是， S-IWF也可以集成于源侧 MSC中， 或者同时集成于源侧 MSC和目标侧 MSC中， 这些都不影响本发明的实现。本实施例所述方案可以 推广到以上任意承载恢复实施例中。
对应上述承载恢复的实现方法，本发明实施例提供了一种网关代理， 参见 图 13所示， 包括：
承载恢复请求接收单元 1301 , 用于接收 MME发送的承载恢复请求， 承 载恢复请求中携带有承载标识或用户标识；
承载恢复处理单元 1302, 用于根据接收到的承载恢复请求中携带的承载 标识或用户标识， 将所述 载标识对应的^载或用户标识对应的^载恢复。
优选地， 所述网关代理还可以包括承载恢复响应发送单元 1303 , 用于在 承载恢复完成之后， 向 MME发送承载恢复响应。
本发明实施例还提供一种移动通信系统， 参见图 14所示， 由以下部分构 成：
MME 1401 , 用于发送承载挂起请求或承载恢复请求， 请求消息中携带承 载标识或用户标识；
网关代理 1402, 根据 MME发送的承载挂起请求或承载恢复请求， 将所 述承载标识对应的承载或用户标识对应的承载挂起或恢复。承载挂起或恢复之 后， 向 MME发送响应消息。 网关代理可以是 SGW或 PGW。
通过应用上述技术方案， 当用户在 EUTRAN网络时， 运营商可根据策略 或者业务需求将某些业务或者承载挂起， 但是不释放用户在 EUTRAN的网络 资源，使得在需要恢复使用所述业务或者承载时能够很快地恢复，给用户带来 更好的体验。 在 SR VCC业务使用过程中， 当用户从 EUTRAN 网络切换到 GERAN 网络时， 保留在 EUTRAN 网络的非语音承载资源， 从而当用户从 GERAN网络切换回 EUTRAN网络时 , 能够避免在 EUTRAN网络重新建立网 络资源， 更快地恢复相应的承载资源， 从而更快地继续原来在 EUTRAN网络 的业务， 并且保证了语音业务的连续性。
本领域普通技术人员可以理解：实现上述方法实施例的全部或部分步骤可 以通过程序指令相关的硬件来完成，前述的程序可以存储于一计算机可读取存 储介质中， 该程序在执行时， 执行包括上述方法实施例的步骤； 而前述的存储 介质包括： ROM、 RAM, 磁碟或者光盘等各种可以存储程序代码的介质。 以上所述仅是本发明的优选实施方式，应当指出，对于本技术领域的普通技术 人员来说， 在不脱离本发明原理的前提下， 还可以做出若干改进和润饰， 这些 改进和润饰也应视为本发明的保护范围。

Claims

权 利 要 求
1、 一种承载挂起的方法， 其特征在于， 包括：
当用户设备 UE由演进 UMTS陆地无线接入网 EUTRAN向 GSM/EDGE 无线接入网 GERAN切换时， 网关代理接收移动管理实体 MME发送的承载挂 起请求， 所述承载挂起请求中携带承载标识或用户标识；根据所述承载挂起请 求， 将所述承载标识对应的承载或用户标识对应的承载挂起。
2、 根据权利要求 1所述的方法， 其特征在于， 将所述承载标识对应的承 载或用户标识对应的承载挂起包括： 当收到所述承载的数据包后，緩存或者丢 弃该数据包， 并且停止寻呼 UE。
3、 根据权利要求 1 所述的方法， 其特征在于， MME根据目标网络类型 和 /或用户承载类型， 发送承载挂起请求。
4、 根据权利要求 1、 2或 3所述的方法， 其特征在于， MME在收到切换 请求消息后， 或收到切换响应消息后， 或收到切换完成消息后， 发送承载挂起 请求。
5、 根据权利要求 1所述的方法， 其特征在于， 所述网关代理为服务网关
SGW或分组数据网关 PGW。
6、 根据权利要求 5 所述的方法， 其特征在于， 当所述网关代理为 PGW 时， PGW接收经 SGW转发的 MME发送的承载挂起请求。
7、根据权利要求 1所述的方法， 其特征在于， 网关代理将承载挂起之后， 还包括： 网关代理向 MME发送承载挂起响应。
8、 根据权利要求 7所述的方法， 其特征在于， 网关代理向 MME发送承 载挂起响应之后， 还包括： MME将承载挂起响应发送至 UE, UE根据所述承 载挂起响应， 停止发送已经挂起的承载的上行数据。
9、 根据权利要求 1 所述的方法， 其特征在于， MME在收到单接入系统 语音连续性功能实体 S-IWF发送的承载挂起请求后， 将所述承载挂起请求发 送至网关代理。
10、 一种网关代理， 其特征在于， 包括：
承载挂起请求接收单元， 用于接收 MME发送的承载挂起请求， 所述承载 挂起请求中携带承载标识或用户标识； 承载挂起处理单元，用于根据所述承载挂起请求接收单元接收到的承载挂 起请求中携带的承载标识或用户标识，将所述承载标识对应的承载或用户标识 对应的承载挂起。
11、 根据权利要求 10所述的网关代理， 其特征在于， 所述承载挂起处理 单元， 包括：
承载接收子单元， 用于接收数据包；
判断子单元，用于判断接收到的数据包对应的承载是否为所述承载挂起请 求接收单元接收到的承载挂起请求所对应的承载；
处理子单元， 用于当所述判断子单元的判断结果为是时，緩存或者丢弃该 承载的数据包， 并且停止寻呼 UE。
12、 根据权利要求 10或 11所述的网关代理， 其特征在于， 还包括： 承载挂起响应发送单元 , 用于在所述承载挂起处理单元将承载挂起之后 , 向 MME发送承载挂起响应。
13、 根据权利要求 10所述的网关代理， 其特征在于， 所述网关代理为服 务网关 SGW或分组数据网关 PGW。
14、一种承载恢复的方法，其特征在于，包括：在 UE由 GERAN向 EUTRAN 切换过程中或跟踪区更新过程中或服务请求过程中 , 网关代理接收 MME发送 的承载恢复请求， 所述承载恢复请求中携带承载标识或用户标识；根据所述承 载恢复请求， 将所述承载标识对应的承载或用户标识对应的承载恢复。
15、 根据权利要求 14所述的方法， 其特征在于， MME根据目标网络类 型和 /或用户承载类型， 发送承载恢复请求。
16、 根据权利要求 14或 15所述的方法， 其特征在于， MME在收到切换 准备消息后， 或收到跟踪区更新请求消息后， 或收到服务请求消息后， 发送承 载恢复请求。
17、 根据权利要求 16所述的方法， 其特征在于， 所述跟踪区更新请求消 息或服务请求消息中包含承载恢复标志 , 当所述 MME在收到跟踪区更新请求 消息后或服务请求消息后， 根据所述承载恢复标志， 发送承载恢复请求。
18、 根据权利要求 14所述的方法， 其特征在于， 所述网关代理为 SGW 或 PGW。
19、根据权利要求 18所述的方法， 其特征在于， 当所述网关代理为 PGW 时， PGW接收经 SGW转发 MME发送的承载恢复请求。
20、 根据权利要求 14所述的方法， 其特征在于， 网关代理将承载恢复之 后， 还包括： 网关代理向 MME发送承载恢复响应。
21、 根据权利要求 20所述的方法， 其特征在于， 网关代理向 MME发送 承载恢复响应， 还包括： MME将承载恢复响应发送至 UE。
22、 一种网关代理， 其特征在于， 包括：
承载恢复请求接收单元， 用于接收 MME发送的承载恢复请求， 所述承载 恢复请求中携带承载标识或用户标识；
承载恢复处理单元，用于根据所述承载恢复请求接收单元接收到的承载恢 复请求中携带的承载标识或用户标识，将所述承载标识对应的承载或用户标识 对应的 载恢复。
23、 根据权利要求 22所述的网关代理， 其特征在于， 还包括：
承载恢复响应发送单元， 用于在所述承载恢复处理单元将承载恢复之后 , 向 MME发送承载恢复响应。
24、根据权利要求 22所述的网关代理，其特征在于，所述网关代理为 SGW 或 PGW。
25、 一种移动通信系统， 其特征在于， 包括 MME及网关代理；
所述 MME, 用于向网关代理发送承载挂起请求或承载恢复请求， 所述承 载挂起请求或承载恢复请求中， 携带承载标识或用户标识；
所述网关代理， 用于根据 MME发送的承载挂起请求或承载恢复请求， 将 所述承载标识对应的承载或用户标识对应的承载挂起或恢复。
26、 根据权利要求 25所述的系统， 其特征在于， 该系统还包括：
S-IWF , 用于向 MME发送承载挂起请求或承载恢复请求。
27、 根据权利要求 25 所述的系统， 其特征在于， 所述网关代理为 SGW 或 PGW。
28、根据权利要求 25或 27所述的系统， 其特征在于， 所述网关代理还用 于在承载挂起或承载恢复之后， 向 MME发送承载挂起响应或承载恢复响应。
PCT/CN2009/070654 2008-04-03 2009-03-05 承载挂起的方法、承载恢复的方法及网关代理 WO2009121255A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2010516358A JP5031899B2 (ja) 2008-04-03 2009-03-05 ベアラ中断の方法、ベアラ再開の方法、及びゲートウェイエージェント
EP09727131A EP2146539A4 (en) 2008-04-03 2009-03-05 Carrier SUSPENSION METHOD, CARRIER RECORDING METHOD AND GATEWAY AGENT
US12/618,117 US20100056147A1 (en) 2008-04-03 2009-11-13 Bearer suspension method, bearer resumption method, and gateway agent

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810091609.9A CN101472256B (zh) 2008-04-03 2008-04-03 承载挂起的方法、承载恢复的方法、网关代理及通信系统
CN200810091609.9 2008-04-03

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/618,117 Continuation US20100056147A1 (en) 2008-04-03 2009-11-13 Bearer suspension method, bearer resumption method, and gateway agent

Publications (1)

Publication Number Publication Date
WO2009121255A1 true WO2009121255A1 (zh) 2009-10-08

Family

ID=40829308

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/070654 WO2009121255A1 (zh) 2008-04-03 2009-03-05 承载挂起的方法、承载恢复的方法及网关代理

Country Status (5)

Country Link
US (1) US20100056147A1 (zh)
EP (1) EP2146539A4 (zh)
JP (1) JP5031899B2 (zh)
CN (1) CN101472256B (zh)
WO (1) WO2009121255A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011136248A1 (ja) * 2010-04-27 2011-11-03 日本電気株式会社 通信方法とモバイルネットワークシステムと装置
WO2012002392A1 (ja) * 2010-06-30 2012-01-05 株式会社エヌ・ティ・ティ・ドコモ 移動通信方法
US9060374B2 (en) 2010-04-27 2015-06-16 Nec Corporation Communication method, mobile network system and device

Families Citing this family (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9015740B2 (en) 2005-12-12 2015-04-21 The Nielsen Company (Us), Llc Systems and methods to wirelessly meter audio/visual devices
EP3592036B1 (en) * 2008-05-13 2021-10-06 Samsung Electronics Co., Ltd. Methods and apparatuses for providing voice call over a circuit switched domain to a ue
CN101945485B (zh) * 2009-07-10 2014-09-10 中兴通讯股份有限公司 一种核心网进行接入控制判断的方法、装置及系统
CN102238658A (zh) * 2010-04-30 2011-11-09 北京三星通信技术研究有限公司 一种支持网关节点重选的方法
EP2586263B8 (en) * 2010-06-28 2016-02-24 Telefonaktiebolaget LM Ericsson (publ) Methods and apparatuses for supporting handover of a ps voice call to a cs voice call by using srvcc function
CN102487499B (zh) * 2010-12-01 2015-05-27 华为技术有限公司 隧道重定向的方法及互通功能实体
KR101752707B1 (ko) * 2011-01-03 2017-07-03 삼성전자 주식회사 이동통신 시스템에서 혼잡 제어 방법
JP5011439B2 (ja) * 2011-01-07 2012-08-29 株式会社エヌ・ティ・ティ・ドコモ 移動通信方法、移動管理ノード及びサービングゲートウェイ装置
CN102761825B (zh) * 2011-04-25 2017-11-07 中兴通讯股份有限公司 信息通知方法及基站、业务获取方法、系统及ue
WO2013023975A1 (en) * 2011-08-12 2013-02-21 Research In Motion Limited Suspending a connection in a wireless communication system
EP2557890B1 (en) 2011-08-12 2019-07-17 BlackBerry Limited Simplified ue + enb messaging
TWI469599B (zh) * 2012-06-08 2015-01-11 Arcadyan Technology Corp 無線行動通訊方法
JP6007321B2 (ja) * 2012-06-28 2016-10-12 アップル インコーポレイテッド ページメッセージへの応答
US9544927B2 (en) * 2012-07-02 2017-01-10 Alcatel Lucent System, method and computer readable medium for bearer activation in a core network for wireless devices
WO2014012227A1 (zh) 2012-07-18 2014-01-23 华为技术有限公司 一种数据连接管理的方法、装置及系统
CN103582172B (zh) * 2012-07-31 2018-03-27 中兴通讯股份有限公司 挂起方法、装置及系统
US8923880B2 (en) * 2012-09-28 2014-12-30 Intel Corporation Selective joinder of user equipment with wireless cell
WO2014056130A1 (en) 2012-10-08 2014-04-17 Broadcom Corporation Method and apparatus for managing dual connection establishment
EP2996388B1 (en) * 2013-06-03 2018-02-28 Huawei Technologies Co., Ltd. Handover adapted to machine type communication with forwarding of data with a signalling plane
CN106714133B (zh) * 2015-08-14 2020-09-15 中兴通讯股份有限公司 网关的恢复处理方法及装置
CN107295452B (zh) * 2016-03-30 2021-06-08 中兴通讯股份有限公司 一种信息通知方法和装置
CN108901049B (zh) * 2018-06-28 2021-02-02 武汉虹信科技发展有限责任公司 一种用于sr过程恢复专有承载的方法
CN108990124B (zh) * 2018-09-26 2021-06-29 中国联合网络通信集团有限公司 语音通话与数据业务切换方法及装置
CN112218283B (zh) * 2019-07-12 2023-06-02 中国电信股份有限公司 业务挂起和恢复方法和系统、多卡终端和存储介质
WO2023153801A1 (en) * 2022-02-11 2023-08-17 Samsung Electronics Co., Ltd. Method and apparatus for handling user plane in wireless communication system supporting mr-mc

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007103496A1 (en) * 2006-03-09 2007-09-13 Interdigital Technology Corporation Wireless communication method and system for performing handover between two radio access technologies
CN101072431A (zh) * 2006-05-08 2007-11-14 中兴通讯股份有限公司 一种防止无线承载数据丢失的方法
CN101128043A (zh) * 2006-08-15 2008-02-20 华为技术有限公司 系统间切换或者改变时的数据处理方法

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6269402B1 (en) * 1998-07-20 2001-07-31 Motorola, Inc. Method for providing seamless communication across bearers in a wireless communication system
FI107864B (fi) * 1998-11-23 2001-10-15 Nokia Mobile Phones Ltd Menetelmä ja järjestelmä virhekriittisen, ei-reaaliaikaisen datan häviämisen estämiseksi eräissä solunvaihtotilanteissa
JP2999470B1 (ja) * 1999-02-04 2000-01-17 株式会社ワイ・アール・ピー移動通信基盤技術研究所 フロ―制御方法、フロ―制御機能を有する交換網および端末装置
US6963745B2 (en) * 2002-01-23 2005-11-08 Samsung Electronics Co., Ltd. Method for performing inter system handovers in mobile telecommunication system
JP2008547289A (ja) * 2005-06-15 2008-12-25 アゼール ネットワークス， インコーポレイテッド Ｉｐ−ｃａｎとｃｓネットワークとの間のボイスコールコンティニュイティアプリケーションサーバー
WO2007103369A2 (en) * 2006-03-07 2007-09-13 Interdigital Technology Corporation Method and apparatus for supporting handoff in an lte gtp based wireless communication system
CN100499909C (zh) * 2006-03-22 2009-06-10 华为技术有限公司 长期演进网络中用户设备切换方法及其系统
CN100563394C (zh) * 2006-03-29 2009-11-25 华为技术有限公司 一种演进网络系统及该系统切换时数据传输方法
CN100571441C (zh) * 2006-08-21 2009-12-16 中兴通讯股份有限公司 演进的无线系统与传统的无线系统间的切换方法
KR101167434B1 (ko) * 2008-03-21 2012-07-23 인터디지탈 패튼 홀딩스, 인크 패킷 교환 도메인으로부터 회선 교환 도메인으로의 폴백 방법 및 장치

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007103496A1 (en) * 2006-03-09 2007-09-13 Interdigital Technology Corporation Wireless communication method and system for performing handover between two radio access technologies
CN101072431A (zh) * 2006-05-08 2007-11-14 中兴通讯股份有限公司 一种防止无线承载数据丢失的方法
CN101128043A (zh) * 2006-08-15 2008-02-20 华为技术有限公司 系统间切换或者改变时的数据处理方法

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Radio interface protocol aspects (Release 7)", 3GPP TR 25.813 V7.1.0 3RD GENERATION PARTNERSHIP PROJECT; TECHNICAL SPECIFICATION GROUP, September 2006 (2006-09-01), XP002434322 *
"Services and System Aspects; General Packet Radio Service (GPRS); Service description; Stage 2 (Release 8)", 3GPP TS 23.060 V8.0.0 3RD GENERATION PARTNERSHIP PROJECT; TECHNICAL SPECIFICATION GROUP, March 2008 (2008-03-01), XP050362320 *
See also references of EP2146539A4 *

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2448299A4 (en) * 2010-04-27 2012-08-22 Nec Corp COMMUNICATION PROCESS, MOBILE NETWORK SYSTEM AND DEVICE THEREFOR
US8923194B2 (en) 2010-04-27 2014-12-30 Nec Corporation Communication method, mobile network system and device
EP2448299A1 (en) * 2010-04-27 2012-05-02 Nec Corporation Communication method, mobile network system and apparatus
EP2472992A1 (en) * 2010-04-27 2012-07-04 Nec Corporation Accelerating restoration of communication services upon MME restarting
EP2466983A3 (en) * 2010-04-27 2012-07-04 Nec Corporation Communication method, mobile network system and device
JP4985880B2 (ja) * 2010-04-27 2012-07-25 日本電気株式会社 通信方法とモバイルネットワークシステムと装置
US10595189B2 (en) 2010-04-27 2020-03-17 Nec Corporation Communication method, mobile network system and device
US8514786B2 (en) 2010-04-27 2013-08-20 Nec Corporation Communication method, mobile network system and device
WO2011136248A1 (ja) * 2010-04-27 2011-11-03 日本電気株式会社 通信方法とモバイルネットワークシステムと装置
US10231114B2 (en) 2010-04-27 2019-03-12 Nec Corporation Communication method, mobile network system and device
US9060374B2 (en) 2010-04-27 2015-06-16 Nec Corporation Communication method, mobile network system and device
US9451583B2 (en) 2010-04-27 2016-09-20 Nec Corporation Communication method, mobile network system and device
US9763281B2 (en) 2010-04-27 2017-09-12 Nec Corporation Communication method, mobile network system and device
US8953561B2 (en) 2010-06-30 2015-02-10 Ntt Docomo, Inc. Mobile communication method
WO2012002392A1 (ja) * 2010-06-30 2012-01-05 株式会社エヌ・ティ・ティ・ドコモ 移動通信方法

Also Published As

Publication number Publication date
JP2011501481A (ja) 2011-01-06
JP5031899B2 (ja) 2012-09-26
EP2146539A4 (en) 2010-08-11
EP2146539A1 (en) 2010-01-20
US20100056147A1 (en) 2010-03-04
CN101472256B (zh) 2011-04-20
CN101472256A (zh) 2009-07-01

Similar Documents

Publication Publication Date Title
WO2009121255A1 (zh) 承载挂起的方法、承载恢复的方法及网关代理
US11997697B2 (en) Method and network device for creating and deleting resources
US10721780B2 (en) Method, system and device for recovering invalid downlink data tunnel between networks
KR101175217B1 (ko) 자원 처리 방법, 통신 시스템, 및 이동성 관리 요소
US9491665B2 (en) Data processing method and device
EP2339785B1 (en) Method, apparatus and system for processing service request
WO2009082936A1 (fr) Procédé et appareil pour un appel d'urgence
CN107277868B (zh) 一种电路域回退方法和设备
WO2011003354A1 (zh) 移动网络用户面数据路由的方法、装置和系统
WO2009100609A1 (zh) 一种单无线信道语音业务连续性的域切换方法
WO2011116722A2 (zh) Isr激活场景中移动管理设备故障的处理方法及设备
WO2011098040A1 (zh) 回退到2g/3g网络的方法和相关设备及通信系统
WO2009132550A1 (zh) 一种切换方法及通讯系统以及相关设备
WO2009121237A1 (zh) 一种激活状态下用户设备跨接入网切换的实现方法
WO2009097733A1 (zh) 分组域业务处理方法、装置及系统
WO2009117886A1 (zh) 设备复位通知方法及系统、服务及分组数据网关和移动管理网元
WO2011095256A1 (en) Restart of peer node
WO2009149656A1 (zh) 一种实现业务切换的方法、装置及系统
WO2013064065A1 (zh) 应用数据处理方法及装置
WO2012103773A1 (zh) 中继系统的过载控制方法及系统
WO2010020196A1 (zh) 一种isr场景下电路交换域业务处理方法及装置
WO2010081435A1 (zh) 寻呼系统、寻呼方法和设备
WO2015085545A1 (zh) 一种ps业务恢复方法、msc/vlr及mme
WO2011109998A1 (zh) 一种承载处理方法、系统及移动管理网元
WO2014019522A1 (zh) 挂起方法、装置及系统

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2010516358

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 2009727131

Country of ref document: EP

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09727131

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 3506/CHENP/2010

Country of ref document: IN

NENP Non-entry into the national phase

Ref country code: DE