WO2015024424A1 - Procédés d'activation et de désactivation d'isr - Google Patents

Procédés d'activation et de désactivation d'isr Download PDF

Info

Publication number
WO2015024424A1
WO2015024424A1 PCT/CN2014/082649 CN2014082649W WO2015024424A1 WO 2015024424 A1 WO2015024424 A1 WO 2015024424A1 CN 2014082649 W CN2014082649 W CN 2014082649W WO 2015024424 A1 WO2015024424 A1 WO 2015024424A1
Authority
WO
WIPO (PCT)
Prior art keywords
management unit
mobility management
isr
service
gateway
Prior art date
Application number
PCT/CN2014/082649
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 WO2015024424A1 publication Critical patent/WO2015024424A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the present invention relates to the field of communications, and in particular to a method for activation and deactivation of Idle mode signaling reduction (ISR) in an idle state.
  • ISR Idle mode signaling reduction
  • 3GPP 3rd Generation
  • the Partnership Project, the 3rd Generation Partnership Project is working on the Evolved Packet System (EPS).
  • EPS Evolved Packet System
  • a Home Subscriber Server In the core network, a Home Subscriber Server (HSS), a Mobility Management Entity (MME), a Serving GPRS Support Node (SGSN), and a policy are included. Policy and Charging Rule Function (PCRF), Serving Gateway (S-GW), Packet Data Gateway (PDN Gateway, P-GW for short), and Packet Data Network (Packet Data Network) , referred to as PDN).
  • the functions of each part are described in detail below:
  • the Home Subscriber Server which contains all the functions of the Home Location Register (HLR), is the permanent storage location for the user's subscription data, and is located in the home network to which the user subscribes.
  • HLR Home Location Register
  • the mobility management entity is the location where the subscriber subscription data is stored in the current network, responsible for UE-to-network non-access stratum signaling management, UE security verification function, UE mobility management, user idle mode tracking and paging. Management functions and bearer management.
  • the Serving GPRS Support Node is a service support point for GERAN and UTRAN users to access the core network. It is similar in function to the mobility management entity and is responsible for user location update, paging management, and bearer management.
  • the service gateway is a gateway of the core network to the wireless system, and is responsible for the user plane bearer of the UE to the core network, the data buffer in the UE idle mode, the function of initiating a service request by the network side, the lawful interception and the packet data routing and forwarding function; It is responsible for counting the situation in which the user UE uses the wireless network, and generates a CDR that the UE uses the wireless network to transmit to the charging gateway.
  • the packet data gateway is a gateway of the evolved system and the external packet data network of the system. It is connected to the Internet and the packet data network, and is responsible for the Internet Protocol (IP) address allocation, charging function, and packet filtering of the UE. , policy control and other functions.
  • IP Internet Protocol
  • the GPRS gateway support node (Gateway GPRS Support Node, referred to as GGSN) supports the edge routing function of the GPRS network. That is, the GGSN is responsible for routing and forwarding data of the GPRS network, and protecting the integrity of the GPRS network data through the firewall and filtering functions.
  • the GGSN also has a charging function.
  • the PGW contains all the functions of the GGSN, and the GGSN can be considered as a sub-function of the PGW and embedded in the PGW. Therefore, the SGSN can be directly connected to the PGW, using the Gn/Gp interface.
  • the packet data network is the operator's IP service network, which provides IP services to users through the operator's core network.
  • the policy charging rule function entity is a server in the evolution system that is responsible for providing rules for charging control, online credit control, threshold control, and quality of service (QoS) policies.
  • the radio access network is composed of an E-UTRAN NodeB (eB) and a 3G radio network controller (RNC), which is mainly responsible for transmitting and receiving wireless signals and contacting the UE through the air interface.
  • eB E-UTRAN NodeB
  • RNC 3G radio network controller
  • a Home NodeB (HNB for short) or an evolved Home eNodeB (HeNB) is a small, low-power base station that is deployed as a dedicated resource for certain users in a home, group, company, or school.
  • the use of private places is mainly to provide users with higher service rates and lower the cost of using high-speed services, while making up for the lack of coverage of existing distributed cellular wireless communication systems.
  • the advantages of a home base station are affordability, convenience, low power output, plug and play, broadband access, use of single mode UE, and the like.
  • the home base station can be applied in a 3G (3 Generation, 3rd Generation) or LTE (Long Term Evolution) mobile communication network.
  • a new network element that is, a home base station gateway, is introduced in the network.
  • the main functions performed by the home base station gateway are: verifying the security of the home base station, performing maintenance and management on the operation of the home base station, configuring and controlling the home base station according to the operator's requirements, and exchanging data information of the core network and the home base station.
  • it is allowed to form a local network.
  • the local network deploys the local gateway, the UE is allowed to access the local service, including the internet service from the local access.
  • Figures 2 and 3 show the flow of data for different local network deployment scenarios.
  • FIG. 2 is an architectural diagram of a local network in which a local network is deployed in a related art.
  • a UE accesses a local service through the gateway, If the UE also has a core network service, it can be considered that the local gateway integrates the functions of the original SGW, and then the data flow of the core network needs to pass through the local gateway. If there is only the core network service at this time, the data flow of the core network does not need to go through the local gateway, but is sent to the PGW of the core network through the SGW of the core network.
  • FIG. 3 is an architectural diagram of a local network in which the local network does not have a separate local gateway. As shown in FIG.
  • FIG. 4 is a schematic diagram of a process for a UE to activate an ISR according to the related art. As shown in FIG. 4, it is assumed that the UE starts to access the network through the UTRAN/GERAN. If the network is first accessed from the E-UTRAN, the details are not described. S400: The UE accesses through the UTRAN/GERAN, and completes registration and corresponding bearer activation.
  • Inter-RAT Radio Access Technology Routing Area Update
  • RAU Tracking Area Update
  • TAU Tracking Area Update
  • step S401 the UE moves to the EUTRAN to initiate the TAU to the MME, where the information carries the valid PTMSI, RAI, etc., step S402, and the MME obtains the context information of the UE from the SGSN according to the PTMSI provided by the UE.
  • Step S403 After completing various checks on the UE, the SGSN returns the context information of the UE to the MME. If the SGSN supports the ISR function, the response contains the parameter "ISR Capability" indicating that the ISR is supported.
  • Step S404 the MME checks whether the S-GW needs to be reselected. If not, and the MME also supports ISR, the MME considers that the ISR function can be activated.
  • Step S405 The MME sends a bearer update request to the S-GW, where the request carries a parameter ISR, and is used to notify the S-GW that the ISR has been activated.
  • Step S406 to step S407 if it is necessary to update the location information or the like, the SGW also needs to send a bearer update request to the PGW, and the PGW receives a bearer update response to the SGW.
  • Step S408 the S-GW sets the ISR activation identifier locally, and sends a bearer update response to the MME.
  • the MME sends a location update request to the HSS.
  • the HSS sends a location update response, which carries the subscription data of the UE.
  • Step S411 The MME sends a TAU accept message to the UE, where the MME includes an ISR activation indication, and information such as a GTUI and a TA list allocated for the UE.
  • Step S412 the UE returns a TAU Complete message to the MME.
  • the SGW is required to be able to simultaneously access EUTRAN access and UTRAN/GERAN access services. If the two access technologies are not able to use the same SGW, the BJ ISR cannot be activated.
  • the UE When the UE initiates service establishment, the UE only cares whether the related service can be established, and the data flow direction of the service, that is, access through the local gateway or the core network gateway, so the UE does not notify the UE when the network selects the gateway. The location of the selected gateway.
  • the prior art if the re-selection of the SGW in the non-mobile state may cause the network to be out of synchronization with the UE-side ISR state, the prior art requires that the local network be different from the TA settings of other networks. This approach will bring certain difficulties to the operator's network planning. Because many times the local network and the base station of the ordinary network overlap in coverage.
  • the present invention provides a method for ISR activation and deactivation to at least solve the problem that the network supports reselection of the SGW in a non-mobile state, which may cause the network to be out of synchronization with the UE side ISR state.
  • a method for activating an ISR including: when a UE moves from a first access network to a second access network, a first mobility management unit corresponding to the first access network and And the second mobility management unit corresponding to the second access network performs IS activation according to the network capability and/or the local offload service information of the UE; where the network capability includes: the mobility management unit supports the non-mobile situation The ability of the serving gateway to reselect, and/or the ability of the mobility management unit and the serving gateway to support the ISR; the local offloading service information of the UE includes: whether the UE is allowed to establish a local offloading service and/or whether the UE is A local offloaded service connection with a separate gateway is established.
  • the first mobility management unit and/or the second mobility management unit performs ISR activation according to the network capability and/or the local offload service information of the UE, including: the first mobility management one by one '"
  • the second mobility management unit sends the first information, where the first information is used to indicate the network capability of the first mobility management unit and/or local offload service information of the UE; the second mobility management unit receives The first information management unit performs signaling optimization ISR activation in an idle state according to the first information and the network capability of the second mobility management unit.
  • the second mobility management unit performs signaling optimization ISR activation in an idle state according to the first information and the network capability of the second mobility management unit, including: if the first information indicates The first mobility management unit supports the ISR and does not support the serving gateway reselection in the non-mobile case, and allows the UE to establish a local offload service or the UE establishes a gateway separate local offload service connection, then the second mobile The management determines whether the service gateway reselection in the non-mobile case is supported. When the second mobility management determines that the serving gateway reselection in the non-mobile case is supported, the second mobility management unit does not activate the ISR.
  • the first mobility management unit respectively indicates the network capability of the first mobility management unit and the local offload service information of the UE by using different IEs.
  • the first mobility management unit and/or the second mobility management unit performs ISR activation according to the network capability and/or the local offload service information of the UE, including: the first mobility management unit according to Determining whether to perform ISR activation by the network capability of the first mobility management unit and/or local offload service information of the UE; the first mobility management unit transmitting a result of the decision to the second mobility a management unit; the second mobility management unit performs ISR activation according to a result of the decision and the network capability of the second mobility management unit.
  • the first mobility management unit determines whether to perform ISR activation according to the network capability of the first mobility management unit and/or the local offload service information of the UE, including: if the first mobility management The unit and/or the serving gateway does not support ISR, then the first mobility management unit indicates that the ISR is not supported; if the first mobility management unit and/or the serving gateway does not support the ISR, the first mobile The management unit indicates that the ISR is not supported; if the first mobility management unit and the serving gateway support the ISR, the method is processed as follows: the first mobility management unit determines that the first mobility management unit supports the non-mobile case The ability of the serving gateway to reselect, when the first mobility management unit supports the capability of the serving gateway reselection in the non-mobile case, indicating that the ISR is not supported; or the first mobility management unit determines the local offloading service of the UE The information indicates that the ISR is not supported when the UE is allowed to establish a local offload service or the UE establishes
  • the ability to support service gateway reselection in the non-mobile case indicates that the ISR is not supported.
  • the second mobility management unit performs ISR activation according to the result of the decision and the network capability of the second mobility management unit, including: if the result of the decision indicates that the ISR or the second is not supported The mobility management unit does not support the ISR, and the second mobility management unit does not activate the ISR; if the result of the decision indicates that the ISR is supported and the second mobility management unit supports the ISR, the second mobility management unit determines that the Whether the second mobility management unit supports the serving gateway reselection in the non-mobile case, the second mobility management unit supports the serving gateway reselection in the non-mobile case and allows the UE to establish a local offload service or the UE has been established When the gateway separates the offloaded service connection, the second mobility management unit does not activate the ISR.
  • the first mobility management unit and/or the second mobility management unit performs ISR activation according to the network capability and/or the local offload service information of the UE, including: if the first mobility management unit And the second mobility management unit and the serving gateway support the ISR, while allowing the UE to establish a local offload service or the UE has established a gateway offloaded service connection, and the first mobility management unit or the first The second mobility management unit supports the service gateway reselection in the non-mobile case, and the second mobility management unit does not activate the ISR.
  • the first mobility management unit and/or the second mobility management unit performs ISR activation according to the network capability and/or the local offload service information of the UE, including: allowing the UE to establish a local offload
  • the second mobility management unit is configured when the service or the UE has established a split service connection with a gateway separation, and the first mobility management unit or the second mobility management unit supports the service gateway reselection in the non-mobile case.
  • a method for indicating an ISR including: when a mobility management unit detects that a serving gateway is reselected for a UE, and the UE is required to re-establish a connection, the mobility management unit indicates The UE deactivates the ISR or does not activate the ISR.
  • the case of reselecting the serving gateway for the UE includes: if the UE establishes a local offloaded service connection with a gateway, when the UE moves out of the local network, the service gateway is reselected for the UE; or If the UE establishes a core network connection, when the UE establishes a separate local offload service connection, the UE reselects the serving gateway; or, if the UE is currently connected, the service gateway is not located insufficiently optimized. And reselecting the serving gateway for the UE.
  • the mobility management unit instructing the UE to deactivate the ISR or not to activate the ISR includes: the mobility management unit carrying the indication information in the deactivation bearer request, indicating that the UE deactivates the ISR or does not activate the ISR;
  • the mobility management unit carries the indication information in the default bearer activation request, indicating that the UE deactivates or does not activate the ISR; or the mobility management unit initiates an identity re-allocation process, and allocates a non-broadcast location area to the UE, triggering the location
  • the UE initiates a location update procedure, instructing the UE to deactivate or disable the ISR in the location update accept message.
  • a method for indicating a network capability including: In a mobility management process, the mobility management unit notifies a UE of a capability of a network to support a service gateway reselection in a non-mobile scenario. Preferably, before the mobile management unit notifies the UE of the ability of the network to support the serving gateway reselection in the non-mobile situation, the method further includes: the mobility management unit determines that the network supports the ISR function. Preferably, before the mobile management unit notifies the UE of the ability of the network to support the re-selection of the serving gateway in the non-mobile situation, the method further includes: the mobility management unit determining that the ISR is currently required to be activated.
  • the mobility management unit notifying the UE of the ability of the network to support the re-selection of the serving gateway in the non-mobile case includes: indicating, in the Attach/TAU/RAU completion message, the service gateway of the network supporting the non-mobile situation in the Attach/TAU/RAU completion message Ability to choose.
  • a method for ISR deactivation including: receiving, by a UE, a deactivation bearer request sent by a mobility management unit, where the deactivation bearer request is used to request the UE to re-establish a connection;
  • the UE has activated the ISR, and then deactivates the ISR upon detecting that the cause value of the deactivation is that the connection needs to be reactivated and/or the mobility management unit indicates that the network supports the serving gateway reselection in the non-mobile case.
  • an activation system for an ISR comprising: a first mobility management unit and/or a second mobility management unit, wherein the first mobility management unit and/or the second mobility management a unit, configured to be based on network capabilities and/or locality of the UE when the UE moves from the first access network corresponding to the first mobility management unit to the second access network corresponding to the second mobility management unit
  • the offloading service information is used for ISR activation; wherein the network capability includes: a capability of the mobility management unit to support service gateway reselection in a non-mobile situation, and/or an ability of the mobility management unit and the serving gateway to support ISR;
  • the local offload service information includes: whether the UE is allowed to establish a local offload service and/or whether the UE establishes a local offloaded service connection with a gateway.
  • the first mobility management unit is configured to send first information to the second mobility management unit, where the first information is used to indicate the network capability and/or location of the first mobility management unit. Localization of the UE And the second mobility management unit is configured to receive the first information, and perform signaling optimization ISR in an idle state according to the first information and the network capability of the second mobility management unit. activation.
  • the second mobility management unit is configured to: when the first information indicates that the first mobility management unit supports ISR and does not support serving gateway reselection in a non-mobile situation, and allows the UE to establish a local offload If the service or the UE establishes a local offloaded service connection with a separate gateway, it is determined whether the service gateway reselection in the non-mobile case is supported, and if so, the ISR is not activated.
  • the first mobility management unit is configured to decide whether to perform ISR activation according to the network capability of the first mobility management unit or the local offload service information of the UE, and the result of the decision Sending to the second mobility management unit; the second mobility management unit is configured to perform ISR activation according to the result of the decision and the network capability of the second mobility management unit.
  • the first mobility management unit is configured to indicate that the ISR is not supported if the first mobility management unit and/or the serving gateway does not support the ISR; if the first mobility management unit and/or the If the service gateway does not support the ISR, the ISR is not supported; if the first mobility management unit and the serving gateway support the ISR, the method is as follows: determining that the first mobility management unit supports the service in the non-mobile situation The capability of the gateway reselection, when the first mobility management unit supports the capability of the serving gateway reselection in the non-mobile case, indicating that the ISR is not supported; or determining the local offloading service information of the UE, allowing the UE to establish When the local offload service or the UE establishes a local offloaded service connection with a gateway, the indication does not support the ISR; or the local offload service information of the UE is determined, the local offload service is allowed to be established by the UE, or the gateway is established by the UE.
  • the separate local offload service connection When the separate local offload service connection is connected, further determining, by the first mobility management unit, the capability of the service gateway reselection in the non-mobile case If the first mobility management unit supports the capability of the serving gateway reselection in the non-mobile case, indicating that the ISR is not supported.
  • the second mobility management unit is configured to: if the result of the decision indicates that the ISR is not supported or the second mobility management unit does not support the ISR, the second mobility management unit does not activate the ISR; The result of the decision indicates that the ISR is supported and the second mobility management unit supports the ISR, and the second mobility management unit determines whether the second mobility management unit supports the serving gateway reselection in the non-mobile case, in the second The second mobility management unit does not activate the ISR when the mobility management unit supports the serving gateway reselection in the non-mobile case and allows the UE to establish a local offload service or the UE has established a gateway offloaded offload service connection.
  • the second mobility management unit is configured to allow the UE to establish a local offload service or the offloaded service connection in which the UE has established a gateway separation, and the first mobility management unit or the second mobility management When the unit supports service gateway reselection in non-mobile situations, the ISR is not activated.
  • a mobility management unit including: a detection module, configured to detect whether a service gateway is reselected for a UE, and whether the UE is required to re-establish a connection; and an indication module configured to detect The UE reselects the serving gateway, and when the UE is required to re-establish a connection, instructs the UE to deactivate the ISR or not to activate the ISR.
  • the detecting module is configured to: if the UE establishes a local offloaded service connection with a gateway separation, when the UE moves out of the local network, reselect the serving gateway for the UE; or if the UE is established The core network is connected, and when the UE establishes a local offloaded service connection with a separate gateway, the UE is reselected for the serving gateway; or if the currently connected serving gateway of the UE is not sufficiently optimized, the UE is heavy Select the service gateway.
  • the activation module is configured to carry the indication information in the deactivation bearer request, indicating that the UE deactivates the ISR or does not activate the ISR; or carries the indication information in the default bearer activation request, indicating that the UE is deactivated or The ISR is not activated; or the identity re-allocation process is initiated, the UE is allocated a non-broadcast location area, and the UE is triggered to initiate a location update process, and the UE is inactivated or not activated in the location update accept message.
  • a mobility management unit including: a notification module, configured to notify a user equipment of a capability of a network to support a service gateway reselection in a non-mobile state in a mobility management process
  • the foregoing mobility management unit further includes: a first determining module, configured to determine that the network supports the ISR function before notifying the UE of the capability of the serving gateway reselection in the case of the network supporting non-mobile.
  • the foregoing mobility management unit further includes: a second determining module, configured to determine that the ISR is currently required to be activated after determining that the network supports the ISR function.
  • a UE including: a receiving module, configured to receive a deactivation bearer request sent by a mobility management unit, where the deactivation bearer request is used to request the UE to re-establish a connection; Provided that, in the case that the UE has activated the ISR, if the cause value of the deactivation is detected, the connection needs to be reactivated and/or the mobility management unit indicates that the network supports the service gateway in the non-mobile case. Select to activate the ISR.
  • the first mobility management unit corresponding to the first access network and/or the second mobility management unit corresponding to the second access network according to the network
  • the capability and/or the local offloading service information of the UE is used for ISR activation, which solves the problem that the network side and the UE side have different ISR status, and cancels the limitation that "requires the local network to be different from the TA settings of other networks", thereby saving the network. Resources.
  • FIG. 1 is an architectural diagram of an evolved packet domain system according to the related art
  • FIG. 2 is an architectural diagram of a related local network deployed with a separate local gateway
  • FIG. 3 is a related art local network not deployed separately
  • FIG. 4 is a flow chart of a related art UE activation ISR
  • FIG. 5 is a flowchart of implementing ISR inactivity in a mobility management process according to an embodiment of the present invention
  • FIG. 6 is a flowchart according to an embodiment of the present invention.
  • a flowchart for implementing ISR inactivation when a local connection is reactivated is a flowchart 1 for implementing ISR inactivity when connection reactivation is performed according to an embodiment of the present invention
  • FIG. 8 is a reactivation of a connection according to an embodiment of the present invention.
  • FIG. 9 is a block diagram showing a structure of a mobility management unit according to an embodiment of the present invention.
  • FIG. 10 is a flowchart of a method for deactivating an ISR according to an embodiment of the present invention
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. The invention will be described in detail below with reference to the drawings in conjunction with the embodiments.
  • Embodiment 1 An embodiment of the present invention provides a method for activating an ISR, the method comprising the following steps: when a UE moves from a first access network to a second access network, a first mobility management unit corresponding to the first access network and And the second mobility management unit corresponding to the second access network performs ISR activation according to the network capability and/or the local offload service information of the UE.
  • the network capability includes: the mobility management unit supports the service gateway reselection in the non-mobile situation.
  • the capability, and/or the mobility management unit and the service gateway support the ISR capability;
  • the local offload service information of the UE includes: whether the UE is allowed to establish a local offload service and/or whether the UE establishes a gateway separate local offload service connection.
  • the first mobility management unit and the second management unit may negotiate whether to activate the ISR.
  • the UE is allowed to establish a local offload service or the UE has established a gateway offloaded service connection, and the first mobility management unit or the second mobile
  • the management unit supports the service gateway reselection in the non-mobile case, and the second mobility management unit does not activate the ISR.
  • the ISR activation may be performed in two ways: 1) the first mobility management unit indicates to the second mobility management unit the network capability of the first mobility management unit and/or the local offload service information of the UE.
  • the second management unit determines to perform ISR activation; 2) the first mobility management unit decides whether to perform ISR activation according to the network capability of the first mobility management unit and/or the local offload service information of the UE, and the second mobility management unit determines the result according to the decision And network capabilities for ISR activation.
  • the first mobile management unit sends the first information to the second mobility management unit, where the first information is used to indicate the network capability of the first mobility management unit and/or the local offload service information of the UE; Receiving the first information; the second mobility management unit performs signaling optimization ISR activation of the idle state according to the first information and the network capability of the second mobility management unit.
  • the second mobility management unit performs signaling optimization ISR activation of the idle state according to the first information and the network capability of the second mobility management unit, including: if the first information indicates that the first mobility management unit supports the ISR and does not Supporting the service gateway reselection in the non-mobile case, and allowing the UE to establish a local offload service or the UE establishes a local offloaded service connection with the gateway separated, then the second mobility management determines whether to support the service gateway reselection in the non-mobile case, When the mobile management judges that the service gateway reselection in the non-mobile case is supported, the second mobility management unit does not activate the ISR.
  • the first mobility management unit may respectively indicate the network capability of the first mobility management unit and the local offload service information of the UE by using different IEs.
  • Way two The first mobility management unit determines whether to perform ISR activation according to the network capability of the first mobility management unit and/or the local offload service information of the UE; the first mobility management unit sends the result of the decision to the second mobility management unit; the second mobility The management unit performs ISR activation based on the result of the decision and the network capabilities of the second mobility management unit.
  • the first mobility management unit determines whether to perform ISR activation according to the network capability of the first mobility management unit and/or the local offload service information of the UE, including: if the first mobility management unit and/or the service gateway does not support ISR, the first mobility management unit indicates that the ISR is not supported; if the first mobility management unit and the serving gateway support the ISR, the method is processed as follows: The first mobility management unit determines that the first mobility management unit supports the service gateway in the non-mobile case The ability to reselect, when the first mobility management unit supports the capability of the serving gateway reselection in the non-mobile case, indicating that the ISR is not supported; or the first mobility management unit determines the local offloading service information of the UE, and allows the UE to establish a local offloading When the service or the UE establishes the local offloaded service connection of the gateway, the indication does not support the ISR; or the first mobility management unit determines the local offload service information of the UE, and allows the UE to
  • the second mobility management unit performs ISR activation according to the result of the decision and the network capability of the second mobility management unit, including: if the result of the decision indicates that the ISR is not supported or the second mobility management unit does not support the ISR, the second The mobility management unit does not activate the ISR; if the result of the decision indicates that the ISR is supported and the second mobility management unit supports the ISR, the second mobility management unit determines whether the second mobility management unit supports the serving gateway reselection in the non-mobile case, in the second The second mobility management unit does not activate the ISR when the mobility management unit supports the serving gateway reselection in the non-mobile case and allows the UE to establish a local offload service or the UE has established a gateway offloaded offload service connection.
  • FIG. 5 is a flowchart of implementing ISR inactivity in a mobility management process according to an embodiment of the present invention. As shown in FIG.
  • Step S500 A UE accesses through UTRAN/GERAN, and completes registration and corresponding The bearer is activated.
  • Step S501 The UE moves to the EUTRAN to initiate a TAU to the MME, where the information carries valid PTMSI, RAI, and the like.
  • Step S502 The MME acquires context information of the UE from the SGSN according to the PTMSI provided by the UE.
  • Steps S503 to S504 after the SGSN completes various verifications on the UE, if both the self and the corresponding SGW support the ISR function, further determine their own support for the service gateway reselection capability in the non-mobile case, and the local connection of the UE. happening.
  • the UE's subscription allows the use of the local offload service, or the UE has established a split service connection for the gateway, it notifies the MME when the UE context is returned to the MME.
  • the MME is notified when the UE context is returned to the MME.
  • the specific notification process in the foregoing case may be: if the UE's subscription allows the use of the local offload service, or the UE has established a separate offload service connection, the SGSN uses a separate IE notification to the MME, or in this case, in step S504, The inclusion of ISR support IE indicates that the ISR function is not supported.
  • the SGSN uses a separate IE notification to the MME, or in this case, in step S504, the ISR support IE is not included to indicate that the ISR function is not supported. If the SGSN does not support the service gateway reselection in the non-mobile case, the SGSN determines that if the UE's subscription allows the use of the local offload service, or the UE has established a separate offload service connection, the SGSN uses two separate IE notifications respectively. The MME, or in this case, does not include the ISR support IE in step S504, indicating that the ISR function is not supported.
  • the local connection situation for the UE may be indicated by two new IEs respectively or by an IE, and if the latter is one of the conditions, the IE is filled.
  • Steps S505 to S506 the MME supports the ISR according to whether the SGSN indicates in step S504. If the SGSN indicates that the ISR is not supported, the determination of the ISR in the subsequent steps does not need to be performed. If the MME determines that the SGW needs to be reselected, the determination of the ISR in the subsequent steps does not need to be performed. If both MME and SGSN support The ISR and the SGW do not need to be reselected, and further judgment is required.
  • the MME selects whether to support the SGW reselection in the non-mobile case. Determine whether the ISR function is activated. If the MME supports SGW reselection in the non-mobile case, the ISR function is not activated, otherwise the MME determines that the ISR function can be activated. If the MME finally determines that the ISR function can be activated, the ISR indication is added to the context confirmation response in step S506, informing the SGSN that the context of the UE can be maintained.
  • Step S507 The MME sends a bearer update request to the S-GW, where the ISR is not carried.
  • Step S508 to step S509 if it is necessary to update the location information or the like, the SGW also needs to send a bearer update request to the PGW, and the PGW receives a bearer update response to the SGW.
  • Step S510 S511 if the ISR is not activated, the SGW deletes the resource related to the ISR, and sends a delete bearer request to the previously registered SGSN.
  • step S508 has no clear sequential relationship with step S510.
  • Step S512 the SGW sends a bearer update response to the MME.
  • the HSS sends a location update response, which carries the subscription data of the UE.
  • Step S515 The MME sends a TAU accept message to the UE, where the information including the GTUI and the TAlist allocated for the UE does not include the ISR activation indication.
  • FIG. 6 is a flowchart of implementing ISR inactivation when a local connection is reactivated according to an embodiment of the present invention. As shown in FIG.
  • Step S600 The UE accesses through UTRAN/GERAN, and completes registration and registration.
  • the corresponding bearer is activated.
  • step S601 the UE moves to the edge regions of the EUTRAN and the UTRAN/GERAN.
  • the RNC sends a relocation request to the SGSN, where the TA and the cell of the target are carried, and the relevant bearer information that needs to be switched.
  • the source base station is an RNC. If the message sent by the BSC to the SGSN is a data domain handover request, the information carried is similar.
  • Steps S602 to S603 the SGSN checks its own ISR capability and the local connection status of the UE.
  • both the user and the corresponding SGW support the ISR function, further judge their own support for the ability of the service gateway to reselect in the non-mobile case, and the local connection of the UE. If the subscription of the UE allows the use of the local offload service, or the UE has established a split service connection with the gateway, the MME is notified in the context of the UE when the forward redirect request is sent to the MME. If the SGSN supports the serving gateway reselection in the non-mobile case, the MME is notified to the MME when transmitting the forwarding redirection request to the MME.
  • the specific notification process may be: if the UE's subscription allows the use of the local offload service, or the UE has established a separate offload service connection, the SGSN uses a separate IE notification to the MME, or in step S603, does not include The ISR support IE indicates that the ISR function is not supported. If the SGSN supports the service gateway reselection in the case of non-mobile, the SGSN uses a separate IE notification to the MME, or in this case, in step S603, the ISR support IE is not included to indicate that the ISR function is not supported.
  • the SGSN determines that if the UE's subscription allows the use of the local offload service, or the UE has established a separate offload service connection, the SGSN uses two separate IE notifications respectively.
  • the MME or in this case, does not include the ISR support IE in step S603, indicating that the ISR function is not supported.
  • the local connection situation for the UE may be indicated by two new IEs respectively indicating that the same IE may be indicated, and if the latter is one of the conditions, the IE is filled.
  • Steps S604 to S605 if the MME determines that the SGW needs to be reselected, the determination of the ISR in the subsequent steps does not need to be performed. It is assumed here that the MME determines that it is not necessary to reselect the SGW.
  • the MME sends a handover request to the e B, which carries information such as a bearer to be handed over, a target cell, and the like. After receiving the resource reservation, the eNB performs resource reservation, and returns a handover request response message to the MME, where the bearer carrying the resource reservation is successfully carried.
  • Steps S606 ⁇ S607 the MME determines whether to support the ISR according to whether the SGSN indicates in step S603.
  • the MME determines whether the ISR function is activated. If the MME supports SGW reselection in the non-mobile case, the ISR function is not activated, otherwise the MME determines that the ISR function can be activated.
  • step S607 If the MME finally determines that the ISR function can be activated, the ISR activation indication is added to the forwarding relocation response in step S607, and the SGSN is notified to continue to maintain the context of the UE.
  • Step S608 performing the remaining flow of the handover, similar to the related art.
  • step S609 the UE initiates a TAU process, and the ISR determination is not required in the process, but in the TAU complete message, the MME needs to notify the UE whether the ISR is activated. According to the judgment of step S607, it is notified whether the UE activates the ISR.
  • the steps shown in the flowchart of the accompanying drawings may be performed in a computer system such as a set of computer executable instructions, and, although the logical order is shown in the flowchart, in some cases, The steps shown or described may be performed in an order different than that herein.
  • the embodiment of the invention also provides an activation system for an ISR, which system can be used to implement the above method.
  • the system includes a first mobility management unit and/or a second mobility management unit, wherein the first mobility management unit and/or the second mobility management unit are configured to be in a first access network corresponding to the UE from the first mobility management unit
  • the ISR activation is performed according to the network capability and/or the local offload service information of the UE.
  • the network capability includes: the mobility management unit supports the service gateway in the non-mobile case.
  • the selected capabilities, and/or the capabilities of the mobility management unit and the serving gateway to support the ISR; the local offloading service information of the UE includes: whether the UE is allowed to establish a local offloading service and/or whether the UE establishes a gateway-separated local offloading service connection.
  • the first mobility management unit and the second management unit may negotiate whether to activate the ISR.
  • the UE is allowed to establish a local offload service or the UE has established a gateway offloaded service connection, and the first mobility management unit or the second mobile
  • the management unit supports the service gateway reselection in the non-mobile case, and the second mobility management unit does not activate the ISR.
  • the ISR activation may be performed in two ways: 1) the first mobility management unit indicates to the second mobility management unit the network capability of the first mobility management unit and/or the local offload service information of the UE.
  • the second management unit determines to perform ISR activation; 2) the first mobility management unit decides whether to perform ISR activation according to the network capability of the first mobility management unit and/or the local offload service information of the UE, and the second mobility management unit determines the result according to the decision And network capabilities for ISR activation.
  • the first mobile management unit is configured to send the first information to the second mobility management unit, where the first information is used to indicate the network capability of the first mobility management unit and/or the local traffic distribution service information of the UE.
  • the mobility management unit is configured to receive the first information, and perform signaling optimization ISR activation of the idle state according to the first information and the network capability of the second mobility management unit.
  • the second mobility management unit is configured to: when the first information indicates that the first mobility management unit supports the ISR and does not support the serving gateway reselection in the case of non-mobile, and allows the UE to establish a local offload service or the UE establishes a gateway separation. In the case of a local offload service connection, it is determined whether the service gateway reselection in the case of non-mobile is supported, and if so, the ISR is not activated.
  • the second mobility management unit is configured to: determine whether to perform ISR activation according to the network capability of the first mobility management unit and/or the local offload service information of the UE, and send the result of the decision to the second mobility management unit;
  • the mobility management unit is configured to perform ISR activation based on the result of the decision and the network capabilities of the second mobility management unit.
  • the first mobility management unit is configured to not support if the first mobility management unit and/or the service gateway
  • the ISR the first mobility management unit indicates that the ISR is not supported; if the first mobility management unit and the serving gateway support the ISR, the method is as follows: determining that the first mobility management unit supports the service gateway reselection in the non-mobile case, When the first mobility management unit supports the capability of the service gateway reselection in the non-mobile case, indicating that the ISR is not supported; or determining the local offload service information of the UE, allowing the UE to establish a local offload service or the UE establishes a local offload of the gateway. When the service is connected, the indication is that the ISR is not supported; or the local offloading service information of the UE is determined.
  • the first mobility management unit When the UE is allowed to establish a local offload service or the UE establishes a local offloaded service connection with a gateway, the first mobility management unit is further determined to support non-mobile.
  • the ability of the serving gateway to reselect if the first mobility management unit supports the ability of the serving gateway to reselect in the non-mobile case, indicates that the ISR is not supported.
  • the second mobility management unit is configured to: if the result of the decision indicates that the ISR is not supported or the second mobility management unit does not support the ISR, the second mobility management unit does not activate the ISR; if the result of the decision indicates that the ISR is supported and the second mobile The management unit supports the ISR, and the second mobility management unit determines whether the second mobility management unit supports the service gateway reselection in the non-mobile case, and when the second mobility management unit supports the service gateway reselection in the non-mobile case, the second mobility The snap-in does not activate the ISR.
  • the system described in the device embodiment corresponds to the foregoing method embodiment, and the specific implementation process has been described in detail in the method embodiment, and details are not described herein again.
  • Embodiment 2 An embodiment of the present invention provides a method for indicating an ISR, including the following steps: When the mobility management unit detects that the serving gateway is reselected for the UE, and the UE is required to re-establish the connection, the mobility management unit instructs the UE to deactivate the ISR or not to activate the ISR. .
  • the case of reselecting the serving gateway for the UE includes, but is not limited to, one of the following: 1) if the UE establishes a gateway-separated local offload service connection, when the UE moves out of the local network, the UE is reselected to serve the gateway; 2) If the UE establishes a core network connection, when the UE establishes a local offloaded service connection with a separate gateway, the UE reselects the serving gateway; 3) if the currently connected service gateway of the UE is not sufficiently optimized, the UE is reselected for the serving gateway. .
  • the mobility management unit instructs the UE to deactivate the ISR or not to activate the ISR, including but not limited to one of the following: the mobility management unit carries the indication information in the deactivation bearer request, instructing the UE to deactivate the ISR or not to activate the ISR; or, the mobility management The unit carries the indication information in the default bearer activation request, indicating that the UE deactivates or does not activate the ISR; or, the mobility management unit initiates an identity re-allocation process, allocates a non-broadcast location area to the UE, triggers the UE to initiate a location update process, and updates the location.
  • the accept message indicates that the UE deactivates or does not activate the ISR.
  • FIG. 7 is a flowchart 1 of implementing ISR inactivity when a connection is reactivated according to an embodiment of the present invention. As shown in FIG.
  • Step S701 The MME finds that the UE moves out of the local network, and the original local network
  • the gateway is set up or the MME finds that the serving gateway to which the UE is currently connected is not optimized enough, and it is desirable that the subsequent process reselects a local gateway for the UE.
  • the subsequent connection re-establishment triggers the gateway re-selection process, and the MME locally deactivates (also referred to as deactivated) the ISR.
  • Step S702 The MME sends a deactivation bearer request to the UE, where the ISR deactivation indication is carried.
  • Step S703 after receiving the UE, the UE deletes the corresponding PDN connection, and returns a bearer deactivation response.
  • Step S704 the MME initiates recovery of the network resource, and initiates a bearer release process to the LGW.
  • step S704 and step S702 S703 do not have a necessary order relationship.
  • the UE after receiving the step S702, the UE locally deactivates the ISR. If the operation is not performed, it is performed after step S705 or after step S707 in step S704.
  • Step S706 the MME initiates a related process of SGW reselection and a PDN connection establishment process, in the process
  • FIG. 8 is a flow chart 2 of implementing ISR inactivity when a connection is reactivated according to an embodiment of the present invention, as shown in FIG.
  • Step S801 The MME finds that the UE moves out of the local network or the MME finds that the serving gateway that the UE is currently connected to is not optimized enough, and hopes that the subsequent process reselects a local gateway for the UE, and initiates a PDN connection. live.
  • Step S802 The MME sends a deactivated bearer request to the UE.
  • Step S803 after receiving the UE, the UE deletes the corresponding PDN connection, and returns a bearer deactivation response.
  • Step S804 the MME initiates recovery of the network resource, and initiates a bearer release process to the LGW.
  • step S804 and step S802 S803 do not have a necessary order relationship.
  • Step S805 The UE initiates a reestablishment of the corresponding PDN connection, and initiates a PDN connection establishment request to the MME, where the PDN associated with the previously deactivated PDN is carried.
  • Step S806 the MME determines whether to perform SGW reselection and whether the ISR is activated, if it needs to be executed.
  • the MME When the SGW is reselected, the MME locally deactivates the ISR function.
  • the MME initiates a related process of SGW reselection and a PDN connection establishment process. In this process, the MME sends an old SGW (LGW) to initiate a delete session request, where the SGSN carrying the relevant reason instructs the GW to delete the associated resource.
  • LGW old SGW
  • the MME returns a default bearer setup request to the UE, where the ISR deactivation indication is carried.
  • the UE returns a default bearer establishment corresponding to the MME.
  • the implementation manner is similar to that of FIG. 8.
  • Step 909 The MME initiates an identity re-allocation request, which includes a new TAI list, which may be a non-broadcast location area, where the guarantee triggers the UE to initiate a TAU procedure.
  • Step 910 The UE returns an identifier redistribution response.
  • Step 911 The UE initiates a TAU process, and the MME indicates that the ISR is not activated in the TAU accept message of the process. If the identification reassignment procedure is initiated after step S802, the reselection of the SGW may be triggered by the TAU procedure.
  • step S804 After the TAU is completed, the subsequent steps of step S804 are performed. Similarly, similar to FIG. 7 and FIG. 8 , the implementation manner is also applicable to UTRAN/GERAN access.
  • the MME completes the determining function by the SGSN, and the SGSN sends an identifier redistribution request to the UE, including a non-broadcast routing area. The guarantee guarantees that the UE initiates the RAU process, and indicates that the ISR is not activated in the subsequent RAU process.
  • FIG. 9 is a structural block diagram of a mobility management unit according to an embodiment of the present invention. As shown in FIG.
  • the method includes: a detection module 10 configured to detect whether a service gateway is reselected for a UE, and whether the UE is required to re-establish a connection; And being configured to, when detecting that the serving gateway is reselected for the UE, and requesting the UE to re-establish the connection, instructing the UE to deactivate the signaling optimized ISR or the inactive ISR of the idle state.
  • the detecting module 10 may be configured to: if the UE establishes a gateway-separated local offload service connection, when the UE moves out of the local network, reselect the serving gateway for the UE; or if the UE establishes a core network connection, establish a gateway at the UE.
  • the service gateway is reselected for the UE; or if the service gateway currently connected by the UE is not sufficiently optimized, the service gateway is reselected for the UE.
  • the activation module 20 is configured to carry the indication information in the deactivation bearer request, instructing the UE to deactivate the ISR or not to activate the ISR; or carrying the indication information in the default bearer activation request, instructing the UE to deactivate or not to activate the ISR; or Initiating an identity re-allocation process, assigning a non-broadcast location area to the UE, triggering the UE to initiate a location update procedure, and instructing the UE to deactivate or disable the ISR in the location update accept message.
  • the mobility management unit described in the device embodiment corresponds to the foregoing method embodiment, and the specific implementation process has been described in detail in the method embodiment, and details are not described herein again.
  • Embodiment 3 The embodiment of the present invention provides a method for indicating a network capability, including the following steps: In the mobility management process, the mobility management unit notifies the UE of the capability of the network to support the reselection of the serving gateway in the non-mobile state. Preferably, before the mobile management unit notifies the UE of the ability of the network to support the serving gateway reselection in the non-mobile situation, the method further includes: the mobility management unit determines that the network supports the ISR function. Preferably, before the mobile management unit notifies the UE of the ability of the network to support the re-selection of the serving gateway in the non-mobile situation, the method further includes: the mobility management unit determines that the ISR is currently required to be activated.
  • the implementation of the network capability is obtained in the Attach/TAU/RAU process.
  • the specific procedure is similar to that in FIG. 4.
  • the mobility management unit In the TAU/RAU completion message, the mobility management unit notifies the UE whether it supports SGW reselection in the non-mobile case.
  • Specific notification methods may include but are not limited to the following:
  • the Attach/TAU/RAU completion message uses a separate IE to indicate whether the current network has the ability to support SGW reselection in non-mobile situations; 2) In the Attach/TAU/RAU procedure, if the current network has ISR capability and Support for SGW reselection in non-mobile situations, using a separate IE in the Attach/TAU/RAU completion message to indicate whether the current network has the ability to support SGW reselection in non-mobile situations;
  • the mobility management unit determines whether it supports non-mobile.
  • SGW reselection if supported, a separate IE is used to indicate whether the current network has the capability of supporting SGW reselection in the case of non-mobile, or the ISR function is not activated at this time, that is, the network side does not activate the ISR function on the UE side.
  • the embodiment of the present invention further provides a method for deactivating an ISR, and FIG.
  • Step S1002 The UE receives a deactivation bearer request sent by the mobility management unit, and the deactivated bearer request is used to request the UE to re-establish the connection.
  • Step S1004 If the UE has activated the ISR, the ISR is deactivated when it is detected that the cause value of the deactivation is that the connection needs to be reactivated and/or the mobility management unit indicates that the network supports the service gateway reselection in the case of non-mobile.
  • the embodiment of the invention further provides a mobility management unit, which can be used to implement the above method.
  • the mobility management unit of the embodiment of the present invention includes: a notification module, configured to notify the UE of the ability of the network to support the reselection of the serving gateway in the non-mobile case in the mobility management process.
  • the mobility management unit further includes: a first determining module, configured to determine, before notifying the UE of the capability of the serving gateway reselection in the case that the network supports non-mobile, determining the signaling optimization ISR function of the network supporting the idle state.
  • the foregoing mobility management unit further includes: a second determining module, configured to determine that the ISR is currently required to be activated after determining that the network supports the ISR function.
  • the embodiment of the present invention further provides a UE.
  • FIG. 11 is a structural block diagram of a UE according to an embodiment of the present invention. As shown in FIG. 11, the method includes: a receiving module 30, configured to receive a deactivation sent by a mobility management unit.
  • the deactivated bearer request is used to request the UE to re-establish the connection; the deactivation module 40 is set to, if the UE has activated the ISR, if the cause value of the deactivation is detected, the connection needs to be reactivated and/or
  • the mobility management unit instructs the network to support the serving gateway reselection in the non-mobile case, then deactivates the ISR. It should be noted that the mobility management unit and the UE described in the device embodiment correspond to the foregoing method embodiments, and the specific implementation process is described in detail in the method embodiment, and details are not described herein again.
  • the UE moves from the first access network to the second access network, and the first mobility management unit corresponding to the first access network and/or the second access network corresponds to
  • the second mobility management unit performs ISR activation according to the network capability and/or the local offload service information of the UE, and solves the problem that the network side and the UE side have different ISR status, and cancels the requirement that the local network be different from the TA settings of other networks.
  • This limitation saves network resources.
  • the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices.
  • the invention is not limited to any specific combination of hardware and software.
  • the above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Landscapes

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

Abstract

La présente invention concerne des procédés d'activation et de désactivation d'ISR. Le procédé de désactivation d'ISR comprend les étapes suivantes dans lesquelles : un UE reçoit une requête de support de désactivation envoyée par une unité de gestion mobile, la requête de support de désactivation étant utilisée pour demander à l'UE de rétablir une connexion ; et, si l'UE a activé l'ISR, celui-ci désactive l'ISR lorsqu'il est détecté qu'une valeur de cause de désactivation consiste en ce qu'une connexion doit être réactivée et/ou en ce que l'unité de gestion mobile indique qu'un réseau prend en charge le service de résélection de passerelle en cas d'immobilité. La présente invention fournit une solution à un problème lié au fait que les états d'ISR d'un côté réseau et d'un côté UE sont différents, et supprime une limitation selon laquelle « il est obligatoire que la configuration TA d'un réseau local soit différente de celle d'un autre réseau », ce qui permet d'économiser une ressource réseau.
PCT/CN2014/082649 2013-08-19 2014-07-21 Procédés d'activation et de désactivation d'isr WO2015024424A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310363009.4 2013-08-19
CN201310363009.4A CN104427525A (zh) 2013-08-19 2013-08-19 Isr激活及去激活的方法

Publications (1)

Publication Number Publication Date
WO2015024424A1 true WO2015024424A1 (fr) 2015-02-26

Family

ID=52483042

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/082649 WO2015024424A1 (fr) 2013-08-19 2014-07-21 Procédés d'activation et de désactivation d'isr

Country Status (2)

Country Link
CN (1) CN104427525A (fr)
WO (1) WO2015024424A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021203375A1 (fr) * 2020-04-09 2021-10-14 Qualcomm Incorporated Connectivité avec des cellules non autonomes
CN112911706B (zh) * 2021-02-20 2023-02-17 中国联合网络通信集团有限公司 一种isr去激活方法、数据业务寻呼方法、msc以及sgw

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101282582A (zh) * 2008-05-16 2008-10-08 中兴通讯股份有限公司 一种跨无线接入技术的切换方法
CN101448320A (zh) * 2008-03-26 2009-06-03 中兴通讯股份有限公司 注销网络方法及双模用户设备
CN101562854A (zh) * 2008-04-18 2009-10-21 大唐移动通信设备有限公司 用户设备的服务网关重选方法、设备及系统
US20110170517A1 (en) * 2010-01-11 2011-07-14 Research In Motion Limited System and method for enabling session context continuity of local service availability in local cellular coverage

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101500223B (zh) * 2008-02-01 2012-08-29 华为技术有限公司 终端跨接入网元切换的方法及移动性管理网元
CN100581297C (zh) * 2008-02-04 2010-01-13 华为技术有限公司 Isr机制下处理承载的方法及系统
WO2011049370A2 (fr) * 2009-10-21 2011-04-28 Lg Electronics Inc. Procédé de détermination de l'activation d'isr dans un système de communications entre mobiles
CN103313284B (zh) * 2010-06-18 2016-05-18 电信科学技术研究院 一种激活/去激活isr优化方法及网络侧设备
CN102469619B (zh) * 2010-11-12 2016-12-28 中兴通讯股份有限公司 一种移动通信系统及其服务网关重定位的方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101448320A (zh) * 2008-03-26 2009-06-03 中兴通讯股份有限公司 注销网络方法及双模用户设备
CN101562854A (zh) * 2008-04-18 2009-10-21 大唐移动通信设备有限公司 用户设备的服务网关重选方法、设备及系统
CN101282582A (zh) * 2008-05-16 2008-10-08 中兴通讯股份有限公司 一种跨无线接入技术的切换方法
US20110170517A1 (en) * 2010-01-11 2011-07-14 Research In Motion Limited System and method for enabling session context continuity of local service availability in local cellular coverage

Also Published As

Publication number Publication date
CN104427525A (zh) 2015-03-18

Similar Documents

Publication Publication Date Title
US10674420B2 (en) Method, apparatus, and system for routing user plane data in mobile network
RU2749750C1 (ru) Управление разрывом услуги для беспроводного устройства
EP3979707B1 (fr) Procédé de déclenchement de la modification de trajet dans le plan d'utilisateur d'un système de communication
US8331938B2 (en) Moving user equipment without service interruption
US9504005B2 (en) Method for processing data associated with location area update in a wireless communication system
US8855045B2 (en) Method and system for controlling establishment of local IP access
CA3064904A1 (fr) Reglage de connexion et deconnexion assistes par reseau
EP3788826A1 (fr) Gestion de radiomessagerie centrale
US8842636B2 (en) Method and device for managing Internet Protocol offload connection
TW201320696A (zh) 支援區域ip存取及選出ip訊務卸載方法及裝置
US20120100823A1 (en) Method, system, network side device, and ue of managing csg membership
EP2761904B1 (fr) Procédé de traitement de données associées à une mise à jour de zone de localisation dans un système de communication sans fil
WO2009097772A1 (fr) Procédé de commande, système de communication et dispositif correspondant pour une libération de ressource
JP2022524165A (ja) Ｒａｎページング処理
JP5859680B2 (ja) ローカルアクセス接続の処理方法及び装置
WO2011076063A1 (fr) Procédé, dispositif, et système pour gérer un accès par protocole internet local ou un transfert de trafic par protocole internet sélectionné
WO2012130018A1 (fr) Procédé et système pour la prise en charge de mobilité de connexion de déchargement ip
WO2013107240A1 (fr) Procédé de compte-rendu de capacité d'accès sans fil, station de base et procédé et système de contrôle de règle
WO2012103773A1 (fr) Procédé de régulation de surcharge et système de système de relais
WO2015024424A1 (fr) Procédés d'activation et de désactivation d'isr
WO2011157100A1 (fr) Procédé et système de mise en cache de données
WO2011097813A1 (fr) Procédé de désactivation de la réduction de la signalisation en mode veille (isr), procédé de modification des paramètres de support et système de réseau
WO2015176256A1 (fr) Procédé et appareil de traitement d'informations pour une mise à jour de zone d'emplacement
WO2018001247A1 (fr) Procédé, appareil, et système de commande d'équipement utilisateur, et passerelle de réseau
WO2012129997A1 (fr) Procédé et dispositif pour traiter une connexion d'accès à un réseau local

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

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

Country of ref document: EP

Kind code of ref document: A1