[go: up one dir, main page]

WO2012119377A1 - Procédé de traitement d'informations de contexte d'une connexion lipa pdn et dispositif de gestion des postes mobiles - Google Patents

Procédé de traitement d'informations de contexte d'une connexion lipa pdn et dispositif de gestion des postes mobiles Download PDF

Info

Publication number
WO2012119377A1
WO2012119377A1 PCT/CN2011/078152 CN2011078152W WO2012119377A1 WO 2012119377 A1 WO2012119377 A1 WO 2012119377A1 CN 2011078152 W CN2011078152 W CN 2011078152W WO 2012119377 A1 WO2012119377 A1 WO 2012119377A1
Authority
WO
WIPO (PCT)
Prior art keywords
management device
mobility management
pdn connection
information
lipa pdn
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2011/078152
Other languages
English (en)
Chinese (zh)
Inventor
王宁沈
舒林
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to PCT/CN2011/078152 priority Critical patent/WO2012119377A1/fr
Priority to CN201180001667.8A priority patent/CN102326442B/zh
Publication of WO2012119377A1 publication Critical patent/WO2012119377A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections

Definitions

  • the embodiments of the present invention relate to communication technologies, and in particular, to a local IP access (LIP) packet data network (PDN) connection context information processing method and a mobility management device.
  • LIP local IP access
  • PDN packet data network
  • the 3rd Generation Partner Project (3GPP) organization proposed a home access device based connection.
  • Incoming services for example: Providing access services by deploying home access devices in homes, malls, or businesses.
  • LIPA Local IP Access
  • UE User Equipment
  • the IP network can be accessed through the local packet data network gateway, for example: Internet (Internet) 0
  • the mobility management device may migrate the UE to other mobility management devices through the home access device, but other mobile management devices cannot obtain the LIPA established before the UE.
  • the context information of the PDN connection prevents the UE from using the previously established LIPA PDN connection to perform services, thereby reducing service reliability.
  • the embodiment of the present invention provides a method for processing context information of a LIPA PDN connection and a mobility management device, which are used to solve the problem that the target mobility management device cannot obtain the context information of the LIPA PDN connection when the mobility management device is overloaded in the prior art.
  • An aspect of the present invention provides a method for processing context information of a LIPA PDN connection, Includes:
  • the source mobility management device migrates the UE served by the source mobility management device, and marks the UE to indicate that the UE is migrated due to load balancing.
  • Another aspect of the present invention provides a method for processing context information of a LIPA PDN connection, including:
  • the target mobility management device to which the UE migrates receives indication information for indicating context information for requesting the LIPA PDN connection of the UE to the source mobility management device serving the UE;
  • the target mobility management device requests, according to the indication information, context information of the LIPA PDN connection of the UE to the source mobility management device;
  • Another aspect of the present invention provides a mobility management device, including:
  • a migration unit configured to perform migration on the UE served by the mobility management device, and mark the UE, to indicate that the UE is migrated due to load balancing;
  • a sending unit configured to send, according to the information marked by the migration unit, context information of a LIPA PDN connection of the UE to a mobility management device to which the UE migrates.
  • Another aspect of the present invention provides a mobility management device, including:
  • a receiving unit configured to receive indication information, where the indication information is used to indicate that the mobility management device serving the UE requests context information of the LIPA PDN connection of the UE;
  • a requesting unit configured to request, according to the indication information, context information of a LIPA PDN connection of the UE to the mobility management device serving the UE;
  • an obtaining unit configured to obtain context information of the LIPA PDN connection of the UE sent by the mobility management device served by the UE. It can be seen from the foregoing technical solutions that the foregoing embodiments of the present invention can avoid other mobile management devices that cannot be utilized by other mobile management devices that cannot be obtained due to the fact that other mobile management devices that the UE migrates to cannot obtain the context information of the LIPA PDN connection established before the UE.
  • the LIPA PDN connects to the business to improve the reliability of the service.
  • FIG. 1 is a schematic flowchart of a method for processing context information of a LIPA PDN connection according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of a method for processing context information of a LIPA PDN connection according to another embodiment of the present invention
  • FIG. 3 is a schematic flowchart of a method for processing context information of a LIPA PDN connection according to another embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a method for processing context information of a LIPA PDN connection according to another embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a method for processing context information of a LIPA PDN connection according to another embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a mobility management device according to another embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a mobility management device according to another embodiment of the present invention. detailed description
  • the local gateway (LGW) in the embodiment of the present invention is a gateway that transmits LIPA data.
  • FIG. 1 is a schematic flowchart of a method for processing context information of a LIPA PDN connection according to an embodiment of the present invention.
  • the method for processing context information of a LIPA PDN connection in this embodiment may include:
  • the source mobility management device migrates the UE served by the source mobility management device, and marks the UE to indicate that the UE is migrated due to load balancing.
  • the source mobility management device may add marking information to the context information of the UE to indicate that the UE is migrated due to load balancing.
  • the source mobility management device sends the context information of the LIPA PDN connection of the UE to the target mobility management device migrated by the UE according to the marked information.
  • the context information of the LIPA PDN connection of the UE may include address information of the LGW.
  • the target mobility management device may process the context information of the LIPA PDN connection of the UE according to the address information of the LGW included in the context information of the LIPA PDN connection of the UE. For example, when the address information of the LGW obtained by the target mobility management device from the home access device does not match the address information of the LGW included in the context information of the LIPA PDN connection of the UE, the target mobility management device may delete the UE.
  • the context information of the LIPA PDN connection indicates that the location of the UE has indeed changed.
  • the target mobility management device may further interact with other network elements (for example, SGW or LGW, etc.), so that other network elements delete the context information of the LIPA PDN connection of the UE, so that the LIPA PDN connection of the UE is deactivated.
  • other network elements for example, SGW or LGW, etc.
  • the migration by the source mobility management device is performed.
  • the UE performs marking, so that the source mobility management device can move to the UE according to the information marked above.
  • the moved to the target mobility management device sends the context information of the LIPA PDN connection of the UE, so that the UE can use the previously established LIPA PDN connection to perform the service, and the other mobile management devices that are migrated to the UE cannot be acquired in the prior art.
  • Other mobile management devices caused by the context information of the previously established LIPA PDN connection cannot utilize the previously established LIPA PDN connection for service problems, thereby improving service reliability.
  • Evolved Universal Mobile Telecommunication System UMTS
  • E-UTRAN Evolved Universal Mobile Telecommunication System Territorial Radio Access Network
  • UTRAN UMTS Territorial Radio Access Network
  • the mobility management device may be a Mobility Management Entity (MME) in the E-UTRAN, or may be a General Packet Radio Service (GPRS) support node in the UTRAN (Serving GPRS). Supporting Node, referred to as SGSN).
  • MME Mobility Management Entity
  • GPRS General Packet Radio Service
  • SGSN Supporting Node
  • the home access device may be a home evolved node B in E-UTRAN (Home)
  • the Evolved NodeB can also be a Home NodeB (HNB) device in the UTRAN.
  • HNB Home NodeB
  • E-UTRAN is taken as an example below.
  • 2 is a schematic flowchart of a method for processing context information of a LIPA PDN connection according to another embodiment of the present invention.
  • the method for processing context information of a LIPA PDN connection in this embodiment may include:
  • the UE interacts with the source MME (old MME) to perform a process of establishing a PDN connection. Specifically, first, the UE may access the source MME by performing an attach procedure. Then, the UE may establish a new PDN connection by performing a UE Requested PDN Connectivity process, in which the UE simultaneously establishes a corresponding LIPA PDN connection. 202.
  • the source MME is overloaded.
  • the overload phenomenon of the source MME may occur before, during or after the UE accesses the MME, or may also appear in the PDN of the UE. Before, during, or after the connection is established.
  • some or all of the served UEs may be migrated (also referred to as offloading, ie, off-load) to other MMEs, ie, the target MME (new MME), according to the Load Rebalancing policy.
  • the source MME interacts with a Serving Gateway (SGW) to release the access bearer.
  • SGW Serving Gateway
  • the source MME sends a release access request to the SGW (Release Access Bearers)
  • the Request message, and the SGW returns a Release Access Bearers Response message to the source MME.
  • the source MME performs marking on the UE, and is used to indicate that the UE is migrated due to load balancing.
  • the source MME may specifically add flag information to the context information of the UE to indicate that the UE is migrated due to load balancing of the source MME. .
  • the source MME may first mark the UE and then release the access bearer; or may release the access bearer first, and then perform the UE on the access bearer. mark.
  • the source MME sends an S1 interface UE context release command (S1 UE Context Release Command) message to the HeNB, where the message carries a cause value, where the cause value is required for load balancing.
  • S1 interface UE context release command S1 UE Context Release Command
  • TAU Tracking Area Update
  • the HeNB sends an RRC Connection Release message to the UE, where the message carries a cause value, and the cause value is load balancing TAU Required;
  • the HeNB sends the S1 interface UE context release completion to the source MME (S1 UE Context). Release Complete ) message;
  • the UE sends a TAU Request (TAU Request) message to the HeNB.
  • TAU Request TAU Request
  • the HeNB selects, for the UE, the MME to be migrated, that is, the target MME, and the HeNB sends an initial UE message or an Up Non-Access Stratum (NAS) message to the target MME.
  • the message includes a TAU request message and address information of the LGW corresponding to the HeNB (for example: an IP address of the LGW);
  • the target MME sends a context request (Context Request) message to the source MME.
  • Context Request Context Request
  • the source MME sends a context response (Context Response) message to the target MME according to the marking performed by the UE in the 204, where the message includes the context information of the LIPA PDN connection of the UE;
  • the context information of the LIPA PDN connection of the UE includes the address information of the LGW (for example, the IP address of the LGW).
  • the target MME sends a context acknowledgment (Context Acknowledge) message to the source MME.
  • Context Acknowledge Context Acknowledge
  • the target MME sends a Modify Bearer Request message to the PGW through the SGW.
  • the PGW sends a Modify Bearer Response message to the target MME by using the SGW.
  • the target MME sends a TAU Accepted (Accepted) message to the UE.
  • the UE can perform services using the previously established LIPA PDN connection.
  • the target MME is deactivated.
  • the LIPA PDN connection of the UE indicates that the location of the UE has indeed changed, so that the previously established LIPA PDN connection cannot be used for service.
  • the source MME is overloaded, the UE that migrates the source MME is marked, so that the source MME can send the context information of the LIPA PDN connection of the UE to the target MME to which the UE migrates according to the marked information.
  • the PDN connection carries out business problems, thereby improving service reliability.
  • FIG. 3 is a schematic flowchart of a method for processing context information of a LIPA PDN connection according to another embodiment of the present invention. As shown in FIG. 3, the method for processing context information of a LIPA PDN connection in this embodiment may include:
  • the target mobility management device to which the UE migrates receives the indication information, where the indication information is used to indicate that the source mobility management device serving the UE requests the context information of the LIPA PDN connection of the UE.
  • the indication information may be sent by the UE, where the indication information is carried in a location update request message sent by the UE, where the location update request message is carried by an initial UE sent by the home access device to the target mobility management device. In the message.
  • the indication information may be sent by the home access device, where the indication information and the location update request message sent by the UE are carried in an initial UE message sent by the home access device to the target mobility management device.
  • the home access device sends the initial to the target mobility management device.
  • the temporary identifier of the UE may include, but is not limited to, a Globally Unique MME Identifier (GUMMEI) or a Packet Temporary Mobile Subscriber Indentity (P-TMSI).
  • GUMMEI Globally Unique MME Identifier
  • P-TMSI Packet Temporary Mobile Subscriber Indentity
  • the target mobility management device requests, according to the foregoing indication information, context information of the LIPA PDN connection of the UE to the source mobility management device.
  • the foregoing target mobility management device obtains the foregoing UE sent by the source mobility management device. Context information for the LIPA PDN connection.
  • the target mobility management device when the source mobility management device is overloaded, the target mobility management device requests and obtains context information of the LIPA PDN connection of the UE from the source mobility management device according to the received indication information, so that the UE can utilize the previously established LIPA.
  • the PDN connection is used for the service, and the other mobile management devices in the prior art that cannot obtain the context information of the LIPA PDN connection established before the UE cannot be obtained by using the previously established LIPA PDN connection. The problem, which improves the reliability of the business.
  • Evolved Universal Mobile Telecommunication System UMTS
  • E-UTRAN Evolved Universal Mobile Telecommunication System Territorial Radio Access Network
  • UTRAN UMTS Territorial Radio Access Network
  • the mobility management device may be a Mobility Management Entity (MME) in the E-UTRAN, or may be a General Packet Radio Service (GPRS) support node in the UTRAN (Serving GPRS). Supporting Node, referred to as SGSN).
  • MME Mobility Management Entity
  • GPRS General Packet Radio Service
  • SGSN Supporting Node
  • the home access device may be a Home Evolved Node B (HeNB) in the E-UTRAN, or may be a Home NodeB (HNB) device in the UTRAN.
  • HeNB Home Evolved Node B
  • HNB Home NodeB
  • E-UTRAN is taken as an example below.
  • 4 is a schematic flowchart of a method for processing context information of a LIPA PDN connection according to another embodiment of the present invention. As shown in FIG. 4, the method for processing context information of a LIPA PDN connection in this embodiment may include:
  • the UE interacts with the source MME (old MME) to perform a process of establishing a PDN connection. Specifically, first, the UE may access the source MME by performing an attach procedure. Then, the UE can request a PDN connection by performing UE (UE Requested PDN) The Connectivity process establishes a new PDN connection. In this process, the UE also establishes a corresponding LIPA PDN connection.
  • the source MME old MME
  • the source MME is overloaded.
  • the overload phenomenon of the source MME may occur before, during or after the UE accesses the MME, or may also appear in the PDN of the UE. Before, during, or after the connection is established.
  • some or all of the served UEs may be migrated (or may be offloaded, that is, off-load) to other MMEs, ie, the target MME (new MME), according to the Load Rebalancing policy.
  • the source MME interacts with a Serving Gateway (SGW) to release the access bearer.
  • SGW Serving Gateway
  • the source MME sends a Release Access Bearers Request message to the SGW, and the SGW returns a Release Access Bearers Response (Release Access Bearers Response) message to the source MME.
  • a Release Access Bearers Response Release Access Bearers Response
  • the source MME sends an S1 interface UE context release command to the HeNB (S1 UE Context).
  • the message carries the cause value, and the cause value is a load balancing area update (TAU) (load balancing TAU Required);
  • TAU load balancing area update
  • the HeNB sends an RRC Connection Release message to the UE, where the message carries a cause value, where the cause value is TAU (load balancing).
  • the HeNB sends an S1 interface UE context release complete (S1 UE Context Release Complete) message to the source MME.
  • S1 interface UE context release complete S1 UE Context Release Complete
  • the UE sends a TAU Request (TAU Request) message to the HeNB, where the message includes indication information, and is used to indicate that the TAU request message is a load balancing trigger of the source MME.
  • TAU Request TAU Request
  • the HeNB sends an initial UE message to the target MME.
  • the NAS transmits a message, where the message includes the foregoing TAU request message;
  • the target MME sends a context request (Context Request) message to the source MME according to the indication information included in the TAU request message, where the message includes indication information for requesting context information of the LIPA PDN connection of the UE.
  • Context Request a context request
  • the source MME sends a context response (Context Response) message to the target MME according to the indication information included in the context request message, where the message includes context information of the LIPA PDN connection of the UE;
  • Context Response Context Response
  • the context information of the LIPA PDN connection of the UE includes the address information of the LGW (for example, the IP address of the LGW).
  • the target MME sends a context acknowledgment (Context Acknowledge) message to the source MME.
  • Context Acknowledge Context Acknowledge
  • the target MME sends a Modify Bearer Request message to the PGW through the SGW.
  • the PGW sends a Modify Bearer Response message to the target MME by using the SGW.
  • the target MME sends a TAU Accepted (Accepted) message to the UE.
  • the UE can perform services using the previously established LIPA PDN connection.
  • the target MME when the source MME is overloaded, the target MME receives the indication information sent by the UE, and the target MME requests and obtains the context information of the LIPA PDN connection of the UE from the source MME according to the indication information, so that the UE can establish the previously used context.
  • the LIPA PDN connection is used for the service, and the problem that other MMEs cannot use the previously established LIPA PDN connection to perform services due to the fact that other MMEs migrated by the UE cannot obtain the context information of the LIPA PDN connection established before the UE in the prior art can be avoided. , thereby improving business reliability.
  • FIG. 5 is a schematic flowchart of a method for processing context information of a LIPA PDN connection according to another embodiment of the present invention.
  • the method for processing context information of a LIPA PDN connection in this embodiment may include: 501.
  • the UE interacts with the source MME (old MME) to perform a process of establishing a PDN connection. Specifically, first, the UE may access the source MME by performing an attach procedure. Then, the UE may establish a new PDN connection by performing a UE Requested PDN Connectivity process, in which the UE simultaneously establishes a corresponding LIPA PDN connection.
  • the source MME is overloaded.
  • the overload phenomenon of the source MME may occur before, during or after the UE accesses the MME, or may also appear in the PDN of the UE. Before, during, or after the connection is established.
  • some or all of the served UEs may be migrated (or may be offloaded, that is, off-load) to other MMEs, ie, the target MME (new MME), according to the Load Rebalancing policy.
  • the source MME interacts with a Serving Gateway (SGW) to release the access bearer.
  • SGW Serving Gateway
  • the source MME sends a release access request to the SGW (Release Access Bearers)
  • the Request message, and the SGW returns a Release Access Bearers Response message to the source MME.
  • the source MME sends an S1 interface UE context release command (S1 UE Context Release Command) message to the HeNB, where the message carries a cause value, where the cause value requires a Tracking Area Update (TAU) for load balancing.
  • S1 UE Context Release Command S1 interface UE context release command
  • TAU Tracking Area Update
  • the HeNB sends an RRC Connection Release message to the UE, where the message carries a cause value, where the cause value is load balancing TAU Required;
  • the HeNB sends the S1 interface to the source MME, and the UE context release is complete (S1 UE Context).
  • the UE sends a Radio Resource Control (RRC) Connection Request (RRC Connection Request) message to the HeNB.
  • RRC Radio Resource Control
  • the HeNB sends an RRC Connection Setup message to the UE.
  • the UE sends an RRC Connection Setup Complete message to the HeNB, where the message includes a TAU Request message.
  • the eNB sends an initial UE message (Initial UE message) to the target MME, where the RRC parameter in the RRC connection setup complete message does not include a Globally Unique MME Identifier (GUMMEI), and the message includes the foregoing TAU request.
  • the target MME sends a context request (Context Request) message to the source MME according to the indication information included in the initial UE message, where the message includes indication information for requesting context information of the LIPA PDN connection of the UE;
  • the source MME sends a context response (Context Response) message to the target MME according to the indication information included in the context request message, where the message includes context information of the LIPA PDN connection of the UE.
  • Context Response Context Response
  • the context information of the LIPA PDN connection of the UE includes the address information of the LGW (for example, the IP address of the LGW).
  • the target MME sends a context acknowledgment (Context Acknowledge) message to the source MME.
  • Context Acknowledge Context Acknowledge
  • the target MME sends a Modify Bearer Request message to the PGW through the SGW.
  • the PGW sends a Modify Bearer Response message to the target MME by using the SGW.
  • the target MME sends a TAU Accepted (Accepted) message to the UE.
  • the UE can perform services using the previously established LIPA PDN connection.
  • the target MME receives the indication information sent by the HeNB, and the target MME requests and obtains the context information of the LIPA PDN connection of the UE from the source MME according to the indication information, so that the UE can establish the previously used context.
  • the LIPA PDN connection performs the service, and can avoid the problem that other MMEs cannot use the previously established LIPA PDN connection to perform services due to the fact that other MMEs migrated by the UE cannot obtain the context information of the LIPA PDN connection established before the UE in the prior art. , thereby improving business reliability.
  • FIG. 6 is a schematic structural diagram of a mobility management device according to another embodiment of the present invention.
  • the mobility management device of this embodiment may include a migration unit 61 and a sending unit 62.
  • the migration unit 61 is configured to perform migration on the UE served by the mobility management device, and mark the UE to indicate that the UE is migrated due to load balancing.
  • the sending unit 62 is configured to use the information marked by the migration unit 61.
  • the mobility management device to which the UE migrates transmits the context information of the LIPA PDN connection of the UE.
  • the functions of the MME can be implemented by the mobility management device provided by this embodiment.
  • the migration unit 61 in this embodiment may add flag information to the context information of the UE to indicate that the UE is migrated due to load balancing.
  • the context information of the LIPA PDN connection of the UE includes the address information of the LGW for the mobility management device to which the UE migrates to the UE according to the address information of the LGW included in the context information of the LIPA PDN connection of the UE.
  • Context information for LIPA PDN connections Process it. For example, when the address information of the LGW obtained by the mobility management device migrated by the UE from the home access device is different from the address information of the LGW included in the context information of the LIPA PDN connection of the UE, the mobility management device migrated by the UE The context information of the LIPA PDN connection of the UE may be deleted, indicating that the location of the UE does change.
  • the UE migrated by the mobility management device is marked by the migration unit, so that the sending unit can send the LIPA of the UE to the mobility management device migrated by the UE according to the information marked by the migration unit.
  • the context information of the PDN connection enables the UE to perform the service by using the previously established LIPA PDN connection, which can avoid the situation in the prior art that the other mobility management devices migrated by the UE cannot obtain the context information of the LIPA PDN connection established before the UE.
  • Other mobile management devices are unable to take advantage of the previously established LIPA PDN connection for service problems, thereby improving service reliability.
  • FIG. 7 is a schematic structural diagram of a mobility management device according to another embodiment of the present invention.
  • the mobility management device of this embodiment may include a receiving unit 71, a requesting unit 72, and an obtaining unit 73.
  • the receiving unit 71 is configured to receive indication information, where the indication information is used to indicate context information of requesting the LIPA PDN connection of the UE to the mobility management device serving the UE, and the requesting unit 72 is configured to use the foregoing indication received by the receiving unit 71.
  • the functions of the target mobility management device in the embodiment corresponding to the foregoing FIG. 3 and the target MME in the embodiment corresponding to FIG. 4 and FIG. 5 can be implemented by the mobility management device provided in this embodiment.
  • the indication information may be sent by the UE, where the indication information is carried in a location update request message sent by the UE, where the location update request message carries an initial UE message sent by the home access device to the mobility management device. in.
  • the foregoing indication information may be further sent by the home access device, where the indication information and the location update request message sent by the UE are carried in the home access device to the mobile tube.
  • the initial UE message sent by the device. For example, if the RRC parameter in the Radio Resource Control (RRC) connection establishment complete message received by the home access device does not include the temporary identifier of the UE, the home access device sends the initial to the mobility management device. UE message.
  • the temporary identifier of the UE may include, but is not limited to, a Globally Unique MME Identifier (GUMMEI) or a Packet Temporary Mobile Subscriber Indentity (P-TMSI).
  • GUMMEI Globally Unique MME Identifier
  • P-TMSI Packet Temporary Mobile Subscriber Indentity
  • the requesting unit when the mobility management device serving the UE is overloaded, the requesting unit requests and obtains context information of the LIPA PDN connection of the UE from the mobility management device serving the UE according to the indication information received by the receiving unit, so that the UE
  • the service can be performed by using the previously established LIPA PDN connection, and the other mobile management devices in the prior art that cannot be obtained by the other mobile management devices that the UE migrates to cannot obtain the context information of the LIPA PDN connection established before the UE cannot be used.
  • the LIPA PDN connection carries out business problems, thereby improving business reliability.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not executed.
  • the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical, mechanical or otherwise.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. You can choose some of them according to actual needs or All units are used to achieve the objectives of the solution of this embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium.
  • the above software functional units are stored in a storage medium and include a number of instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform some of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. Medium.

Landscapes

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

Abstract

La présente invention concerne un procédé de traitement d'informations de contexte d'une connexion LIPA PDN et un dispositif de gestion des postes mobiles. Le procédé consiste en ce qui suit : un dispositif de gestion des postes mobiles source fait migrer un équipement d'utilisateur UE desservi par le dispositif de gestion de postes mobiles source, et marque l'UE pour indiquer que l'UE est migré en raison de l'équilibrage de charge ; et le dispositif de gestion des postes mobiles source, selon les informations marquées, envoie des informations de contexte d'une connexion LIPA PDN de l'UE à un dispositif de gestion de postes mobiles cible vers lequel l'UE est migré. Les modes de réalisation de la présente invention permettent ainsi d'éviter le problème de l'art antérieur selon lequel, étant donné qu'un autre dispositif de gestion de postes mobiles vers lequel un UE est migré ne peut pas acquérir d'informations de contexte d'une connexion LIPA PDN précédemment établie de l'UE, l'autre dispositif de gestion des postes mobiles ne peut pas accomplir un service en utilisant la connexion LIPA PDN précédemment établie, d'où une amélioration de la fiabilité du service.
PCT/CN2011/078152 2011-08-09 2011-08-09 Procédé de traitement d'informations de contexte d'une connexion lipa pdn et dispositif de gestion des postes mobiles Ceased WO2012119377A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2011/078152 WO2012119377A1 (fr) 2011-08-09 2011-08-09 Procédé de traitement d'informations de contexte d'une connexion lipa pdn et dispositif de gestion des postes mobiles
CN201180001667.8A CN102326442B (zh) 2011-08-09 2011-08-09 Lipa pdn连接的上下文信息的处理方法及移动管理设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/078152 WO2012119377A1 (fr) 2011-08-09 2011-08-09 Procédé de traitement d'informations de contexte d'une connexion lipa pdn et dispositif de gestion des postes mobiles

Publications (1)

Publication Number Publication Date
WO2012119377A1 true WO2012119377A1 (fr) 2012-09-13

Family

ID=45453096

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/078152 Ceased WO2012119377A1 (fr) 2011-08-09 2011-08-09 Procédé de traitement d'informations de contexte d'une connexion lipa pdn et dispositif de gestion des postes mobiles

Country Status (2)

Country Link
CN (1) CN102326442B (fr)
WO (1) WO2012119377A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
RU2630418C1 (ru) * 2014-03-13 2017-09-07 Интердиджитал Пэйтент Холдингз, Инк. Локальная разгрузка и архитектура малых сот (sca)
CN106879023B (zh) * 2015-12-10 2019-06-07 中兴通讯股份有限公司 一种实现负荷分担的方法和装置
CN110140416B (zh) 2016-07-27 2021-02-23 华为技术有限公司 用户设备上下文管理方法、装置和设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101583155A (zh) * 2008-05-16 2009-11-18 大唐移动通信设备有限公司 移动性管理实体上的负载迁移方法及通信设备
CN101998367A (zh) * 2009-08-21 2011-03-30 中兴通讯股份有限公司 本地网络协议访问连接的管理方法以及移动性管理实体
WO2011054320A1 (fr) * 2009-11-09 2011-05-12 华为终端有限公司 Procédé, dispositif et système permettant de transférer un service de protocole internet du réseau fédérateur
WO2011085373A2 (fr) * 2010-01-11 2011-07-14 Research In Motion Limited Système et procédé pour permettre une continuité de contexte de session pour la disponibilité de service local dans une couverture cellulaire locale

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101291536B (zh) * 2008-05-30 2011-12-28 中兴通讯股份有限公司 一种移动性管理实体负载重平衡的切换方法
CN101998370B (zh) * 2009-08-21 2014-01-01 中兴通讯股份有限公司南京分公司 一种本地ip访问连接的释放系统及方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101583155A (zh) * 2008-05-16 2009-11-18 大唐移动通信设备有限公司 移动性管理实体上的负载迁移方法及通信设备
CN101998367A (zh) * 2009-08-21 2011-03-30 中兴通讯股份有限公司 本地网络协议访问连接的管理方法以及移动性管理实体
WO2011054320A1 (fr) * 2009-11-09 2011-05-12 华为终端有限公司 Procédé, dispositif et système permettant de transférer un service de protocole internet du réseau fédérateur
WO2011085373A2 (fr) * 2010-01-11 2011-07-14 Research In Motion Limited Système et procédé pour permettre une continuité de contexte de session pour la disponibilité de service local dans une couverture cellulaire locale

Also Published As

Publication number Publication date
CN102326442B (zh) 2014-04-02
CN102326442A (zh) 2012-01-18

Similar Documents

Publication Publication Date Title
KR101519547B1 (ko) 사용자 장비의 위치 정보를 갱신하기 위한 방법 및 장치
US9307388B2 (en) Method and apparatus for supporting user equipment mobility in a wireless communication system
JP5904206B2 (ja) 通信システム、通信方法及び通信プログラム
CN110431881A (zh) 用于在5g网络中处理切换的方法和节点
WO2018126535A1 (fr) Procédé et appareil de gestion de session
CN101686498B (zh) 一种实现负载转移的方法及装置
WO2009135431A1 (fr) Procédé, système et équipement pour notifier des données d'utilisateur
JP2019521588A (ja) 通信制御方法および関連するネットワーク要素
JP6198940B2 (ja) デフォルト・ベアラなしのハンドオーバのための方法および装置
CN106332222A (zh) 一种网络选择的方法和基站
WO2012100684A1 (fr) Procédé et dispositif de commande d'accès à un réseau local
WO2010130207A1 (fr) Procédé, système et dispositif d'élément de réseau, dispositif de passerelle pour traiter des informations de restriction de nom de point d'accès
KR101659986B1 (ko) 메시지 송신 방법 및 범용 무선 패킷 서비스 지원 노드
CN105359591A (zh) 一种网络故障的处理方法和设备
JP2024123131A (ja) インジケーション情報送信方法、装置およびシステム、および記憶媒体
CN103959861A (zh) 用于支持本地网络中的本地接入和语音通信的方法和装置
CN101730073B (zh) 一种获取用户签约数据的方法及系统
WO2013004121A1 (fr) Procédé et dispositif de traitement d'informations de passerelle locale
WO2012130018A1 (fr) Procédé et système pour la prise en charge de mobilité de connexion de déchargement ip
JP2023549629A (ja) Ｐｇｗ失敗におけるｐｄｎ接続の復元
CN108307429A (zh) 一种基站用户数据恢复的方法及装置
WO2016019559A1 (fr) Appareil, système, et procédé d'identification d'équipement d'utilisateur de réseau partagé
WO2012119377A1 (fr) Procédé de traitement d'informations de contexte d'une connexion lipa pdn et dispositif de gestion des postes mobiles
WO2016101616A1 (fr) Procédé, dispositif et système d'accès au service de campus
WO2010124644A1 (fr) Procédé de mise en oeuvre de services d'urgence, système de mise en oeuvre de services d'urgence et dispositif réseau

Legal Events

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

Ref document number: 201180001667.8

Country of ref document: CN

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

Ref document number: 11860643

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

Country of ref document: EP

Kind code of ref document: A1