WO2013029245A1 - 一种承载的处理方法、系统及装置 - Google Patents

一种承载的处理方法、系统及装置 Download PDF

Info

Publication number
WO2013029245A1
WO2013029245A1 PCT/CN2011/079153 CN2011079153W WO2013029245A1 WO 2013029245 A1 WO2013029245 A1 WO 2013029245A1 CN 2011079153 W CN2011079153 W CN 2011079153W WO 2013029245 A1 WO2013029245 A1 WO 2013029245A1
Authority
WO
WIPO (PCT)
Prior art keywords
network side
bearer
information
target network
created
Prior art date
Application number
PCT/CN2011/079153
Other languages
English (en)
French (fr)
Inventor
陆峰
银宇
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2011/079153 priority Critical patent/WO2013029245A1/zh
Priority to CN201180001575.XA priority patent/CN103155688B/zh
Publication of WO2013029245A1 publication Critical patent/WO2013029245A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a processing method, system, and apparatus for a bearer.
  • E-UTRAN Long Term Evolution
  • SAE System Architecture Evolution
  • EPC Evolved Packet Core
  • Packet core network Evolved Packet System
  • UE User Equipment
  • UTRAN Universal Mobile Telecommunication System Territorial Radio Access Network
  • GERAN GSM EDGE Radio Access Network, GSM/EDGE wireless connection
  • Any access mode in the access network is connected to the EPC.
  • Figure 1 is a current wireless evolution network architecture diagram.
  • the EPC specifically includes but is not limited to an MME (Mobility Management Entity), an SGSN (Serving GPRS Support Node), an SGW (Serving Gateway, a Serving Gateway), and a PGW (PDN Gateway). , packet domain data network gateway).
  • MME Mobility Management Entity
  • SGSN Serving GPRS Support Node
  • SGW Serving Gateway
  • PGW Packet Data Network Gateway
  • packet domain data network gateway The MME/SGSN is mainly responsible for NAS (Non-Access Stratum) signaling management, bearer management, and tracking and paging management in the user idle mode
  • the SGW is mainly responsible for the local mobility anchor and the 3GPP system.
  • PGW is mainly responsible for policy enforcement and billing and legal interception related functions.
  • MME and The SGSN is collectively referred to as a mobility management network element.
  • the wireless access part of the 2G network is GERAN, which is composed of BTS (Base Transceiver Station) and BSC (Base Station Controller).
  • the wireless access part of the 3G network is UTRAN. It is composed of an RNC (Radio Network Controller) and a NodeB (Node B); the radio access part of the LTE network is E-UTRAN, and is composed of an eNodeB (Evolved NodeB).
  • the UE in idle state may trigger a TAU (Tracking Area Update) process or RAU (Routing) Area Update, Routing Area Location Update) Process;
  • a connected UE can trigger a Handover process.
  • the TAU process, the RAU process, and the Handover process are collectively referred to as a mobility management process.
  • the mobility management process may trigger a change of the MME/SGSN corresponding to the UE, and may trigger a change of the SGW corresponding to the UE.
  • the bearer context of the UE needs to be established on the target network side, and the bearer context of the UE is deleted on the source network side.
  • the network where the UE moves before is referred to as the source network side
  • the network where the UE moves is referred to as the target network side.
  • FIG. 2 is a schematic diagram of an implementation process of a UE triggering a TAU process, where:
  • Step S202 - Step S203 The UE sends a TAU request message to the target network side MME.
  • Step S208-Step S211 Create a bearer context of the UE on the target network side, and update the bearer between the target network side SGW and the PGW.
  • Step S218-Step S219 Delete the bearer context of the UE on the source network side MME and the source network side SGW.
  • the prior art only the source network side MME and the source network side SGW delete the bearer context created by the UE on the source network side, and the default packet domain data network gateway PGW will continue to be created by the UE.
  • Bearer context when a mobility management process occurs, some bearers may not be created or reserved on the target network side due to local policies or other reasons, so that the information of these bearers may be stored in the PGW for a long time, resulting in the EPC network. The waste of carrying context resources.
  • the embodiment of the invention provides a method, a system and a device for processing a bearer, so that when the mobility management process occurs, the packet domain data network gateway PGW can delete the bearer information that cannot be created or reserved on the target network side.
  • a method for processing a bearer according to an embodiment of the present invention includes:
  • the source network side mobility management network element learns the bearer information that cannot be created or reserved on the target network side; the source network side mobility management network element triggers the source network side service gateway to send the second delete session request message to the packet domain data network gateway.
  • the second deletion session request message carries the information of the bearer that cannot be created or reserved by the target network side, so that the packet domain data network gateway deletes the bearer information that cannot be created or reserved by the target network side.
  • the source network side service gateway receives the triggering indication sent by the source network side mobility management network element, and the triggering indication is sent after the source network side mobility management network element learns the information about the bearer that cannot be created or reserved by the target network side;
  • the source network side service gateway sends a second delete session request message to the packet domain data network gateway according to the trigger indication, where the second delete session request message carries the target network side cannot be created or
  • the learning unit is configured to learn information about bearers that cannot be created or reserved on the target network side; a sending unit, configured to: after the learning unit learns information about a bearer that cannot be created or reserved on the target network side, trigger the source network side serving gateway to send a second delete session request message to the packet domain data network gateway, where the second delete session The request message carries the information of the bearer that cannot be created or reserved by the target network side, so that the packet domain data network gateway deletes the bearer information that cannot be created or reserved by the target network side.
  • a receiving unit configured to receive a triggering indication sent by the source network side mobility management network element, where the triggering indication is sent by the source network side mobility management network element after the information about the bearer that cannot be created or reserved by the target network side is obtained;
  • a sending unit configured to send, according to the trigger indication received by the receiving unit, a second delete session request message to the packet domain data network gateway, where the second delete session request message carries a bearer that cannot be created or reserved by the target network side
  • the information is such that the packet domain data network gateway deletes the bearer information that cannot be created or retained by the target network side.
  • a processing system for a bearer provided by the embodiment of the present invention includes: a source network side mobility management network element, a source network side service gateway, and a packet domain data network gateway, where
  • the source network side mobility management network element is configured to: after the information about the bearer that cannot be created or reserved on the target network side is learned, trigger the source network side service gateway to send a second delete session request message to the packet domain data network gateway;
  • the source network side service gateway is configured to receive a trigger indication sent by the source network side mobility management network element, and send a second deletion session request message to the packet domain data network gateway according to the trigger indication, where the second deletion session
  • the request message carries information about bearers that cannot be created or reserved by the target network side;
  • a packet domain data network gateway configured to: after receiving the second deletion session request message sent by the source network side service gateway, according to the bearer information that cannot be created or retained by the target network side carried in the second deletion session request message, The information of the bearer that cannot be created or reserved on the target network side is deleted.
  • the information and the PGW are deleted to delete the bearer information that cannot be created or reserved on the target network side, so that the redundant bearer information is no longer reserved in the PGW, and the network side bearer context resource is saved.
  • FIG. 2 is a schematic diagram of an implementation process of a UE triggering a TAU process
  • Embodiment 3 is a processing method of a bearer according to Embodiment 1 of the present invention.
  • FIG. 5 is a processing method of a bearer according to Embodiment 3 of the present invention.
  • FIG. 7 is a flowchart of an implementation manner of Embodiment 5 of a method according to an embodiment of the present disclosure.
  • FIG. 8 is a flowchart of an implementation manner of Embodiment 6 of a method according to an embodiment of the present disclosure.
  • FIG. 9 is a flowchart of implementing Embodiment 7 of a method according to an embodiment of the present disclosure.
  • FIG. 10 is a flowchart of an implementation manner of Embodiment 8 of a method according to an embodiment of the present disclosure.
  • FIG. 11 is a flowchart of an implementation manner of Embodiment 9 of a method according to an embodiment of the present disclosure.
  • FIG. 12 is a flowchart of implementing Embodiment 10 of a method according to an embodiment of the present disclosure
  • FIG. 13 is a mobile management network element according to an embodiment of the present invention.
  • FIG. 14 is another mobile management network element according to an embodiment of the present invention.
  • FIG. 15 is a service gateway according to an embodiment of the present invention.
  • FIG. 16 is a processing system of a bearer according to an embodiment of the present invention.
  • a method for processing a bearer according to Embodiment 1 of the present invention includes: S301: A source network side mobility management network element learns information about a bearer that cannot be created or reserved on a target network side. The information of the bearer that cannot be created or retained on the standard network side:
  • the target network side notification is: the source network side mobility management network element receives the notification message sent by the target network side mobility management network element, and learns, according to the notification message, information about the bearer that cannot be created or retained by the target network side, More specific implementations The following embodiments will be described in detail.
  • the source network side mobility management network element determines: the source network side mobility management network element determines the bearer information that cannot be created or retained by the target network side according to the information about the destination network side to create or retain the bearer.
  • the basis information for creating or retaining the bearer on the target network side includes one of the following information or any combination thereof: bearer context information of the UE, EPS bearer status cell, local policy on the target network side, and whether the target network side supports creation of LIPA (Local IP Access) , local IP access) PDN (Packet Data Network) connection information; wherein, when the mobility management process network element is the same mobility management network element, the context information of the UE and the local policy of the target network side And the information about whether the target network side supports the creation of the LIPA PDN connection is saved by the source network side mobility management network element, and the EPS bearer status information is sent by the UE; when the mobility management network element changes in the mobility management process, That is, the source network side mobility management network element and the target network side mobility
  • the bearer context information of the UE is saved by the source network side mobility management network element, and the EPS bearer status cell is sent by the UE to the target network side mobility management network element. Forwarded by the target network side mobility management network element to the source network side
  • the information about the base station side to create or retain the bearer does not include the EPS bearer status cell when the handover process is triggered.
  • the source network side mobility management network element triggers the source network side service gateway to send a second deletion session request message to the packet domain data network gateway, where the second deletion session request message carries the target network side cannot create or reserve. Carrying information, so that the packet domain data network gateway deletes the bearer information that cannot be created or reserved by the target network side.
  • the second deletion session request message may be sent by the source network side mobility management network element to the source network side service gateway SGW, and the first deletion session request carrying an operation indication (ordination indication) The message is implemented.
  • the source network side service gateway SGW triggers the second deletion session request message to be sent to the packet domain data network gateway PGW according to the operation identifier.
  • One specific implementation manner is to set the operation identifier to a specific value, for example, 1 Further, if the first deletion session request message does not set an operation identifier or the operation identifier is set to a non-specific value, the source network side SGW does not send a second deletion session request message to the PGW.
  • the first deletion session request message carries information about a bearer that cannot be created or reserved on the target network side, and the source network side SGW sends a second delete session request message to the PGW according to the received first deletion session request message. After the PGW receives the second delete session request message, the information of the bearer that cannot be created or reserved on the target network side is deleted.
  • a method for processing a bearer according to Embodiment 2 of the present invention includes: S401: A target network side mobility management network element determines information about a bearer that cannot be created or reserved on a target network side.
  • the target network side mobility management network element creates or retains the bearer according to the target network side.
  • the information about the bearer that cannot be created or reserved on the target network side is determined according to the information, and the basis information of the target network side to create or retain the bearer includes one of the following information or any combination thereof: the bearer context of the user equipment establishes the LIPA PDN connection information. If the mobile management network element does not change, that is, the target network side mobility management network element and the source network side mobility management network element are the same mobility management network element, the target network side mobility management network element obtains the bearer context of the user equipment saved by itself.
  • the information, the local policy on the target network side, and the target network side support the information of creating the LIPA PDN connection, and obtain the EPS bearer status information sent by the user equipment; if the mobility management network element changes, that is, the target network side mobility management network element and The source network side mobility management network element is a different mobility management network element, and the target network side mobility management network element obtains the local policy of the target network side saved by itself and whether the target network side supports the information for creating the LIPA PDN connection, and the source of the acquisition.
  • the embodiment of the present invention provides another processing method of the bearer, as shown in FIG. 5, except that the source network side mobile management network element obtains the information of the bearer that cannot be created or guaranteed by the target network side by using the notification message.
  • the information about the bearer that can be created or reserved on the target network side is determined by the information of the bearer or the reserved bearer. Specifically, the method includes:
  • the target network side mobility management network element determines the basis information of the target network side to create or retain the bearer; the standard network side creates or retains the bearer according to the information, and indicates that the source network side mobility management network element determines that the target network side cannot create or retain the bearer.
  • the processing method of the bearer provided by the above two embodiments causes the source network side mobile management network to send a notification message to the source network side mobility management network element or create or retain the bearer according to the source network side when the mobility management process occurs.
  • the element can know the information of the bearer that cannot be created or reserved on the target network side.
  • a method for processing a bearer according to Embodiment 4 of the present invention includes:
  • the source network side service gateway receives the triggering indication sent by the source network side mobility management network element, and the triggering indication is sent after the source network side mobility management network element learns the bearer information that cannot be created or reserved by the target network side.
  • the triggering indication sent by the source network side service gateway to receive the source network side mobility management network element includes: a first deletion session request message that carries an operation identifier sent by the source network side mobility management network element, where the operation identifier is set to A specific value, such as 1.
  • the source network side serving gateway sends a second delete session request message to the packet domain data network gateway according to the trigger indication, where the second delete session request message carries a bearer that cannot be created or reserved on the target network side. Information, so that the packet domain data network gateway deletes the bearer information that cannot be created or reserved by the target network side.
  • the source network side serving gateway determines whether the trigger indication carries an operation identifier set to a specific value, and if yes, sends a second deletion session request message to the packet domain data network gateway.
  • the packet domain data network gateway After receiving the second deletion session request message sent by the source network side service gateway, the packet domain data network gateway deletes the bearer information that cannot be created or reserved on the target network side.
  • a method for processing a bearer when a mobility management process occurs, the source network side SGW triggers the PGW to delete the bearer that cannot be created or reserved on the target network side according to the trigger indication sent by the source network side mobility management network element.
  • the information makes the redundant bearer information not retained in the PGW, which saves the bearer context resources on the network side.
  • Embodiments of the present invention are applicable to all types of wireless access networks, and all mobile management processes Types of. In order to enable those skilled in the art to understand the technical solutions of the present invention clearly and completely, the following describes the TAU process and the Handover process as an example.
  • the application scenario is that the MME and the SGW change simultaneously when the TAU process occurs, that is, the target network side MME and the source network side MME.
  • the application scenario is not the same MME, and the target network side SGW and the source network side SGW are not the same SGW.
  • the embodiment includes:
  • S701 The UE sends a tracking area location update request (TAU Request) message to the target network side MME.
  • TAU Request tracking area location update request
  • the TAU Request message includes a GUTI (Globally Unique Temporary Identity) identifier and an EPS bearer status (UE) message, and the GUTI identifier is used to locate the source network side MME, and the EPS bearer status cell Used to describe EPS bearer context activation status information in the UE;
  • GUTI Globally Unique Temporary Identity
  • UE EPS bearer status
  • the EPS bearer status cell uses 16 EBI (EPS Bearer Identity) identifiers to describe the bearer context activation status, and each EBI occupies one bit, where EBI(O) - EBI(4) is set to "0". " , in standby, EBI (5) - EBI (15) with "0" indicates that the corresponding EPS bearer context is deactivated, with " ⁇ indicates that the corresponding EPS bearer context is active;
  • EBI EPS Bearer Identity
  • the target network side MME sends a context request (Context Request) message to the source network side MME.
  • the Context Response message includes bearer context information of the UE, and the bearer context information of the UE is described by an EPS PDN Connections cell, and specifically includes a bearer context (bearer Context M language, default bearer identifier ( Linked EPS Bearer ID) and access point name (Access Point Name, APN), the bearer context information includes a bearer identifier (EPS Bearer ID), bearer level QoS, and a service network. Information such as the IP address of the user name and the tunnel endpoint identifier (TEID). Each PDN connection is uniquely identified by its corresponding default bearer (Default Bearer).
  • the context includes all bearer contexts of the PDN connection, specifically, a bearer context corresponding to a default bearer, and a bearer context corresponding to zero to multiple dedicated bearers, where each bearer context is uniquely identified by a bearer identifier;
  • the target network side MME determines the information of the bearer that cannot be created or reserved on the target network side.
  • the target network side MME determines the bearer information that cannot be created or reserved by the target network side according to the information about the destination network side created or reserved.
  • the situation that the target network side cannot create or retain bearers can be divided into the following ways:
  • the target network side MME determines, according to the inconsistency between the EPS bearer status information learned from the UE and the bearer context information of the UE that is learned from the source network side MME, the bearer information that cannot be created or retained by the target network side is determined, where
  • the inconsistency is: the EPS bearer status cell obtained from the UE indicates that the activated bearer and the bearer transmitted by the source network side MME do not correspond to each other; for example, the EPS bearer status cell indicates that the default bearer 5 exists, and the source network side MME
  • the bearer context of the bearer includes the default bearer 5 and the default bearer 6.
  • the target network side MME determines that the target network side cannot create or retain the default bearer 6;
  • the target network side MME determines information about bearers that cannot be created or reserved by the target network side according to the local policy, where the local policy may include an access PDN connection quantity and/or a bearer context quantity control policy, and the target network at this time
  • the MME may not successfully create all the bearers of the UE due to the foregoing control policy, and the part of the bearer may not be created or reserved on the target network side.
  • the bearer context delivered by the source network side MME includes the default bearer 5 and the default bearer 6. Context, but the target network side MME can only create a default bearer 5 because the number of bearer contexts that have been created has reached the upper limit of the number of bearer contexts. At this time, the target network side MME can determine the target network. The side cannot create or retain the default bearer 6;
  • the target network side determines that the created LIPA PDN connection cannot be reserved on the target network side; for example, the bearer context information transmitted by the source network side MME includes the context of the default bearer 5 and the default bearer 6, where the default bearer 6 is LIPA.
  • the PDN connection, the default bearer 5 is a regular PDN connection, and the source network side HeNB (Home Evolved NodeB, the home evolved base station) and the target network side HeNB are not in the same local home base station network.
  • HeNB Home Evolved NodeB, the home evolved base station
  • the target network side MME sends a notification message to the source network side MME.
  • the notification message may adopt a context response (Context Ack) message;
  • the Context Ack message may explicitly (directly) indicate the bearer information that cannot be created or reserved on the target network side, or may implicitly (indirectly) indicate the bearer information that the target network side cannot create or retain, and the specific implementation manner thereof. It can be implemented in one of the following ways or a combination thereof:
  • the Context Ack message carries a Linked EPS Bearer ID or an Access Point Name (APN) information, where the default bearer identifier or access point name can directly correspond to the target network.
  • the identifier of the bearer that cannot be created or reserved on the side for example, the default bearer identifier or the access point name may be included in the context "Context to be removed" cell to be deleted, and directly indicates the identifier of the bearer that cannot be created or reserved on the target network side.
  • the default bearer identifier or the access point name corresponds to the bearer identifier that can be created or reserved on the target network side, and implicitly indicates the bearer information that cannot be created or reserved on the target network side, and the source network side passes the locally stored user.
  • the bearer context information of the device and the bearer information that can be created or reserved by the learned target network side, and information about the bearer that cannot be created or retained by the remaining target network side is obtained; or
  • the Context Ack message carries an EPS bearer status cell, and different values (for example, 1 or 0) in the corresponding bits in the EPS bearer status cell respectively indicate the bearer and target network that the target network side can create or reserve.
  • Context Ack message carries LIPA PDN connection does not support identity ( LIPA PDN Connection Not Support Indication, said: LPCNSI), to indicate that the LIPA PDN connection cannot be created or retained on the target network side;
  • the Context Ack message carries a SGW Change Indication (SGWCI) identifier to indicate that the TAU process has selected a new SGW;
  • SGWCI SGW Change Indication
  • the target network side MME sends a Create Session Request message to the target network side SGW.
  • the Create Session Request message carries the default bearer identifier of the bearer that can be created or reserved by the target network side.
  • the step S706 triggers the execution of step S707;
  • the step is a PDN granularity. If multiple PDN connections (bearers) can be created or reserved on the target network side, multiple Create Session Request messages are triggered accordingly, and each Create Session Request message corresponds to a related PDN connection. A PDN connection that cannot be created or reserved on the target network side does not trigger this step;
  • the target network side SGW sends a Modify Bearer Request message to the PGW.
  • the step is PDN granularity
  • the target network side SGW receives the Modify Bearer Response message sent by the PGW.
  • the target network side MME receives a Create Session Response message sent by the target network side SGW.
  • the source network side MME learns the bearer information that cannot be created or reserved on the target network side according to the Context Ack message sent by the target network side MME received in the foregoing step S705.
  • step S710 may occur before, after, or concurrently with the step S706, and there is no sequence.
  • the source network side MME may Perform this step;
  • the source network side MME sends a first delete session request to the source network side SGW (Delete Session Request ) message;
  • the source network side MME may be configured to send the first delete session request message carrying the operation identifier 01 to the source network side SGW.
  • the 01 identifier is set to The identifier of the 01 is used to indicate that the source network side SGW sends a second delete session request message to the PGW.
  • the step is a PDN granularity. If multiple PDN connections cannot be created or reserved on the target network side, multiple first deletion session request messages are triggered correspondingly, and each first deletion session request message corresponds to a related PDN connection. Each first deletion session request message carries a default bearer identifier;
  • the source network side SGW sends a second delete session request (Delete Session Request) message to the PGW according to the received first deletion session request message carrying the operation identifier.
  • Delete Session Request a second delete session request
  • the second deletion session request message carries information about a bearer that cannot be created or reserved on the target network side;
  • the PGW After receiving the second deletion session request message sent by the source network side SGW, the PGW deletes the target network side according to the information about the bearer that cannot be created or retained by the target network side carried in the second deletion session request message. The information of the bearer created or reserved, and then sends a second delete session response (Delete Session Response) message to the source network side SGW;
  • Delete Session Response Delete Session Response
  • the source network side MME receives a first delete session response (Delete Session Response) message sent by the source network side SGW.
  • the source network side MME sends a third delete session request (Delete Session Request) message to the source network side SGW.
  • the source network side MME After deleting the bearer information that cannot be created or reserved on the target network side, the source network side MME initiates a deletion process for the remaining bearer context of the UE in the source network side SGW;
  • the step is a UE granularity
  • the third deletion session request message carries a Scope Indication (SI Indication)
  • SI Indication Scope Indication
  • the SI identifier is set to 1, indicating the source network side.
  • the SGW releases all PDN connection contexts of the UE, and the 01 flag is set to 0 at this time, so that the source network side SGW does not send a delete session request message to the PGW;
  • the source network side MME receives a third delete session response (Delete Session Response) message sent by the source network side SGW.
  • Delete Session Response Delete Session Response
  • the source network side MME may determine, according to the information about the bearer that cannot be created or reserved by the target network side, the source network side MME may also determine the basis information of the target network side created or reserved by the target network side MME.
  • the information of the bearer that cannot be created or retained on the target network side Specifically, the EPS bearer status cell, the local policy on the target network side, and the information about whether the target network side supports the creation of the LIPA PDN connection may be forwarded to the source network side MME through the context response message, and the source network side MME receives the bearer target network side to create Or, after retaining the context response message of the bearer according to the information, determine the bearer information that the target network side cannot create or retain.
  • the source network side MME instructs the source network side serving gateway to send a second delete session request message to the PGW, which may trigger the PGW deletion target network side to fail to be created. Or the reserved bearer information, so that the redundant bearer information is not reserved in the PGW, and the network side bearer context resource is saved.
  • the source network side MME can learn or retain the bearer according to the notification message or the target network side. The information about the bearer that cannot be created or reserved on the target network side makes the source network side MME more flexible in knowing the information of the bearer that cannot be created or reserved on the target network side.
  • the deletion session request operation is classified, the source network side and the packet.
  • the data gateway deletes the bearer information that cannot be created or reserved on the target network side, and then deletes the bearer information that can be created or reserved on the source network side of the user equipment on the source network side, and enhances the bearer of the UE created by the source network side.
  • the operability and flexibility of contextual information As shown in FIG. 8 , it is an implementation flowchart of Embodiment 6 of the method according to the embodiment of the present invention.
  • the application scenario is that the MME does not change and the SGW changes, that is, the target network side MME and the source network, when the TAU process occurs.
  • the side MME is the same MME, the target network side SGW and the source network side.
  • the SGW is not an application scenario of the same SGW.
  • the embodiment includes:
  • S801 The UE sends a TAU Request message carrying the EPS bearer status cell to the MME.
  • the MME determines the bearer information that cannot be created or reserved on the target network side according to the information about the bearer created or retained by the target network side.
  • the situation that the target network side cannot create or retain the bearer may be classified into the following manners:
  • the MME determines, according to the inconsistency between the EPS bearer status information learned from the UE and the bearer context information of the UE that is saved by the UE, the information about the bearer that cannot be created or reserved on the target network side is determined, where the inconsistency is: obtained from the UE.
  • the EPS bearer status cell indicates that the active bearer and the self-supplied bearer do not correspond to each other. For example, the EPS bearer status cell indicates that the default bearer 5 exists, and the bearer context of the UE that is saved by itself includes the default bearer 5 and the default bearer. 6 Context, at this time, after the MME is judged, it can be determined that the target network side cannot create or retain the default bearer 6;
  • the MME determines that the created LIPA PDN connection cannot be reserved on the target network side; for example, the bearer context information of the UE saved by the MME itself includes the default.
  • the context of the bearer 5 and the default bearer 6 is: the default bearer 6 is a LIPA PDN connection, the default bearer 5 is a regular PDN connection, and the source network side HeNB and the target network side HeNB are not in the same local home base station network. After the MME determines, it can be determined that the target network side cannot create or retain the default bearer 6;
  • the MME may further determine, according to a local policy, information about a bearer that cannot be created or retained by the target network side, where the local policy may include an access PDN connection quantity and/or a bearer quantity control policy;
  • the MME sends a Create Session Request message to the target network side SGW;
  • the Create Session Request message carries the default bearer identifier of the bearer that can be created or reserved by the target network side, and the step S803 triggers the execution of step S804;
  • the step is PDN granularity, if multiple PDN connections (bearers) are available on the target network side If the creation or the reservation is performed, the multiple Create Session Request messages are triggered accordingly. Each Create Session Request message corresponds to the related PDN connection. This step is not triggered for the PDN connection that cannot be created or reserved on the target network side.
  • the target network side SGW sends a Modify Bearer Request message to the PGW, where the step is PDN granularity;
  • S805 The target network side SGW receives the Modify Bearer Response message sent by the PGW.
  • S806 The MME receives the Create Session Response message sent by the target network side SGW.
  • S807 The MME sends a first delete session request message to the source network side SGW.
  • the MME may be configured to send the first delete session request message carrying the operation identifier 01 to the source network side SGW.
  • the 01 identifier is set to 1.
  • the 01 identifier is used to indicate that the source network side SGW sends a second delete session request message to the PGW.
  • the step is a PDN granularity. If multiple PDN connections cannot be created or reserved on the target network side, multiple first deletion session request messages are triggered correspondingly, and each first deletion session request message corresponds to a related PDN connection. Each first deletion session request message carries a default bearer identifier;
  • the source network side SGW sends a second delete session request message to the PGW according to the received first deletion session request message carrying the operation identifier.
  • the second deletion session request message carries information about a bearer that cannot be created or reserved on the target network side;
  • the PGW After receiving the second deletion session request message sent by the source network side SGW, the PGW deletes the target network side according to the information about the bearer that cannot be created or reserved on the target network side that is carried in the second deletion session request message.
  • S810 The MME receives a first delete session response message sent by the source network side SGW.
  • S811 The MME sends a third delete session request message to the source network side SGW.
  • the MME After deleting the bearer information that cannot be created or reserved on the target network side, the MME will initiate a deletion process for the remaining bearer context of the UE in the source network side SGW;
  • the step is the UE granularity.
  • the third delete session request message carries the SI identifier, and the SI identifier is set to 1, indicating that the source network side SGW releases all PDN connection contexts of the UE, and the 01 identifier is displayed at this time. Set to 0, so that the source network side SGW does not send a delete session request message to the PGW;
  • the MME receives a third delete session response message sent by the source network side SGW.
  • the source network side service gateway when the tracking area location update process occurs, is configured to send a second deletion session request message to the PGW, which may trigger the PGW to delete the bearer that cannot be created or reserved on the target network side.
  • the information is such that the redundant bearer information is not reserved in the PGW, and the network side bearer context resource is saved.
  • the source network side MME and the target network side MME are the same MME, which reduces the communication overhead between the network elements. The deletion of the session request operation is performed.
  • the source network side and the packet data gateway delete the bearer information that cannot be created or reserved on the target network side, and then delete the bearer information that can be created or retained by the remaining target network side of the user equipment on the source network side.
  • the operability and flexibility of deleting the bearer context information of the UE created by the source network side is enhanced.
  • FIG. 9 it is a flowchart of an implementation manner of Embodiment 7 of the method provided by the embodiment of the present invention.
  • the application scenario is that the MME changes and the SGW does not change when the TAU process occurs, that is, the target network side MME and the source network.
  • the MME is not the same MME, and the target network side SGW and the source network side SGW are the application scenarios of the same SGW.
  • the embodiment includes:
  • S901 The UE sends a TAU Request message carrying the EPS bearer status cell to the target network side MME.
  • S902 The target network side MME sends a Context Request message to the source network side MME.
  • S903 The source network side MME receives the Context Request message sent by the target network side MME. After the message, the Context Response message is sent to the target network side MME;
  • the Context Response message includes bearer context information of the UE, and the context information of the UE is described by an EPS PDN Connections cell;
  • the target network side MME determines the information of the bearer that cannot be created or reserved on the target network side.
  • the target network side MME determines the bearer information that cannot be created or retained by the target network side according to the basis information of the target network side to create or retain the bearer.
  • the situation that the target network side cannot create or retain bearers can be divided into the following ways:
  • the target network side MME determines, according to the inconsistency between the EPS bearer status information learned from the UE and the bearer context information of the UE that is learned from the source network side MME, the bearer information that cannot be created or retained by the target network side is determined, where
  • the inconsistency is: the EPS bearer status cell obtained from the UE indicates that the activated bearer and the bearer transmitted by the source network side MME do not correspond to each other; for example, the EPS bearer status cell indicates that the default bearer 5 exists, and the source network side MME
  • the bearer context of the bearer includes the default bearer 5 and the default bearer 6.
  • the target network side MME determines that the target network side cannot create or retain the default bearer 6;
  • the target network side MME determines information about bearers that cannot be created or reserved by the target network side according to the local policy, where the local policy may include an access PDN connection quantity and/or a bearer context quantity control policy, and the target network at this time
  • the MME may not be able to successfully create all the bearers of the UE due to the foregoing control policy, and the part of the bearer may not be created or reserved on the target network side.
  • the bearer context delivered by the source network side MME includes the default bearer 5 and the default bearer 6. Context, but the target network side MME can only create a default bearer 5 because the number of bearer contexts that have been created has reached the upper limit of the number of bearer contexts. At this time, the target network side MME can determine the target network. The side cannot create or retain the default bearer 6;
  • the target network side MME determines that the created LIPA PDN connection cannot be reserved on the target network side; for example, the bearer context information transmitted by the source network side MME includes The context of the default bearer 5 and the default bearer 6,
  • the default bearer 6 is a LIPA PDN connection
  • the default bearer 5 is a regular PDN connection.
  • the source network side HeNB target network side HeNB is not in the same local home base station network. At this time, after the target network side MME is judged, Determine that the target network side cannot create or retain the default bearer 6;
  • the target network side MME sends a notification message to the source network side MME.
  • the notification message may adopt a Context Ack message.
  • the Context Ack message may explicitly (directly) indicate the bearer information that cannot be created or reserved on the target network side, or may implicitly (indirectly) indicate the bearer information that the target network side cannot create or retain, and the specific implementation manner thereof. It can be implemented in one of the following ways or a combination thereof:
  • the Context Ack message carries the default bearer identifier or the access point name information, where the default bearer identifier or the access point name may directly correspond to the identifier of the bearer that cannot be created or reserved by the target network side, for example, the default bearer.
  • the identifier or the access point name may be included in the context-to-be-removed cell to be deleted, and directly indicates the identifier of the bearer that cannot be created or reserved by the target network side; or the default bearer identifier or the access point name corresponds to the target network.
  • the identifier of the bearer that can be created or reserved by the side, and the bearer information that cannot be created or reserved by the target network side is implicitly indicated.
  • the source network side MME can create or pass the bearer context information of the locally stored user equipment and the learned target network side. The information of the reserved bearer, and the information about the bearer that cannot be created or retained by the remaining target network side; or
  • the Context Ack message carries an EPS bearer status cell, and different values (for example, 1 or 0) in the corresponding bits in the EPS bearer status cell respectively indicate the bearer and target network that the target network side can create or reserve.
  • the Context Ack message carries the LPCNSI identifier to indicate that the LIPA PDN connection cannot be created or retained on the target network side;
  • Context Ack message will not carry the SGWCI identifier to indicate that the SGW in the TAU process has not changed;
  • the target network side MME sends a Modify Bearer Request message to the SGW.
  • the Modify Bearer Request message carries the default bearer identifier of the bearer that can be created or reserved by the target network side.
  • the step S906 triggers the execution of step S907;
  • the step is a PDN granularity. If multiple PDN connections (bearers) can be created or reserved on the target network side, multiple Modify Bearer Request messages are triggered accordingly, and each Modify Bearer Request message corresponds to the related PDN connection. A PDN connection that cannot be created or reserved on the target network side does not trigger this step;
  • S907 The SGW sends a Modify Bearer Request message to the PGW.
  • the modify bearer request message sent by the SGW to the PGW is implemented by using a modify bearer request message sent by the target network side MME to the SGW.
  • S908 The SGW receives the Modify Bearer Response message sent by the PGW.
  • the target network side MME receives the Modify Bearer Response message sent by the SGW.
  • the source network side MME learns, according to the Context Ack message sent by the target network side MME, which is received in the foregoing step S905, the information about the bearer that cannot be created or reserved on the target network side.
  • the step S910 may occur in this step. Before, after, or concurrently with the step S906, there is no sequence. After receiving the Context Ack message sent by the target network side MME, the source network side MME can perform this step;
  • S911 The source network side MME sends a first delete session request message to the SGW.
  • the source network side MME may be configured to send the first delete session request message carrying the operation identifier 01 to the SGW.
  • the 01 identifier is set to 1.
  • the 01 identifier is used to instruct the SGW to send a second delete session request message to the PGW;
  • the step is a PDN granularity. If multiple PDN connections cannot be created or reserved on the target network side, multiple first deletion session request messages are triggered correspondingly, and each first deletion session request message corresponds to a related PDN connection.
  • Each first deletion session request message carries a default bearer S912: The SGW sends a second deletion session request message to the PGW according to the received first deletion session request message that carries the operation identifier.
  • the second deletion session request message carries information about a bearer that cannot be created or reserved on the target network side;
  • the PGW After receiving the second deletion session request message sent by the SGW, the PGW deletes, according to the information about the bearer that cannot be created or retained by the target network side carried in the second deletion session request message, the target network side cannot be created or retained. After the information is carried, the second delete session response message is sent to the SGW;
  • the source network side MME receives the first delete session response message sent by the SGW.
  • the source network side MME may determine, according to the information about the bearer that cannot be created or reserved by the target network side, the source network side MME may also determine the basis information of the target network side created or reserved by the target network side MME.
  • the information of the bearer that cannot be created or retained on the target network side Specifically, the EPS bearer status cell, the local policy on the target network side, and the information about whether the target network side supports the creation of the LIPA PDN connection may be forwarded to the source network side MME through the context response message, and the source network side MME receives the bearer target network side to create Or, after retaining the context response message of the bearer according to the information, determine the bearer information that the target network side cannot create or retain.
  • the source network side MME instructs the serving gateway to send a second delete session request message to the PGW, which may trigger the PGW to delete the target network side that cannot be created or retained.
  • the bearer information is such that the redundant bearer information is not reserved in the PGW, and the network side bearer context resource is saved.
  • the source network side MME can obtain or retain the bearer according to the notification message or the target network side to learn the target network side. The information of the bearer that cannot be created or reserved makes the source network side MME more flexible in knowing the information of the bearer that cannot be created or reserved on the target network side.
  • the deletion session request operation is classified, and the source network side and the packet data gateway are first.
  • the bearer information that cannot be created or retained on the target network side is deleted, and then the bearer information that can be created or retained on the target network side of the user equipment is deleted on the source network side.
  • FIG. 10 it is an implementation flowchart of Embodiment 8 of the method provided by the embodiment of the present invention.
  • the embodiment is applicable to an application scenario in which the MME and the SGW are changed at the same time when the Handover process occurs.
  • the embodiment includes:
  • S 1001 The source network side HeNB triggers a Handover process
  • the source network side HeNB sends a handover request (Handover Required) message to the source network side MME;
  • the MME After receiving the Handover Required message sent by the HeNB on the source network side, the MME sends a Forward Relocation Request message to the target network side MME.
  • the Forward Relocation Request message includes bearer context information of the UE, and the bearer context information of the UE is described by an EPS PDN Connections cell;
  • the target network side MME determines the information of the bearer that cannot be created or reserved on the target network side.
  • the target network side MME determines the bearer information that cannot be created or reserved by the target network side according to the basis information of the target network side to create or retain the bearer.
  • the situation that the target network side cannot create or retain bearers can be divided into the following ways:
  • the target network side MME determines information about bearers that cannot be created or reserved by the target network side according to the local policy, where the local policy may include an access PDN connection quantity and/or a bearer context quantity control policy, and the target network at this time
  • the MME may not successfully create all the bearers of the UE due to the foregoing control policy, and the part of the bearer may not be created or reserved on the target network side.
  • the bearer context delivered by the source network side MME includes the default bearer 5 and the default bearer 6. Context, but the target network side MME can only create a default bearer 5 because the number of bearer contexts that have been created has reached the upper limit of the number of bearer contexts. At this time, the target network side MME can determine the target network. The side cannot create or retain the default bearer 6;
  • the target network side determines that the created LIPA PDN connection cannot be reserved on the target network side; for example, the bearer context information transmitted by the source network side MME includes the context of the default bearer 5 and the default bearer 6, where the default bearer 6 is LIPA.
  • the PDN connection, the default bearer 5 is a regular PDN connection, and the source network side HeNB and the target network side HeNB are not in the same local home base station network. At this time, after the target network side MME is judged, it can be determined that the target network side cannot be created or Keep the default bearer 6;
  • the target network side MME sends the notification information to the source network side MME.
  • the notification information may be a Forward Relocation Response message, where the Forward Relocation Response message may be explicit ( Directly indicating the information of the bearer that cannot be created or reserved on the target network side, and also implicitly (indirectly) indicating the information of the bearer that cannot be created or reserved on the target network side.
  • the specific implementation manner can be implemented by one of the following methods or a combination thereof:
  • the Forward Relocation Response message carries the default bearer identifier or the access point name information, where the default bearer identifier or the access point name may directly correspond to the identifier of the bearer that cannot be created or reserved on the target network side, for example, the default.
  • the bearer identifier or the access point name may be included in the to-be-deleted context "Context to be removed" cell, and directly indicate the identifier of the bearer that the target network side cannot create or retain; or the default bearer identifier or the access point name corresponds to the target
  • the identifier of the bearer that can be created or reserved on the network side and implicitly indicates the bearer information that cannot be created or reserved on the target network side.
  • the source network side MME can create the bearer context information of the locally stored user equipment and the learned target network side. Or the information of the carried bearer, and the information about the bearer that cannot be created or retained by the remaining target network side; or
  • the Forward Relocation Response message carries an EPS bearer status cell, and different values (for example, 1 or 0) in the corresponding bits in the EPS bearer status cell respectively indicate the bearer and target that the target network side can create or reserve.
  • the Forward Relocation Response message carries an LPCNSI identifier to indicate a LIPA PDN connection that cannot be created or reserved on the target network side;
  • the Forward Relocation Response message carries the SGWCI identifier to indicate that the new SGW has been selected by the Handover process
  • the target network side MME sends a Create Session Request message to the target network side SGW.
  • the Create Session Request message carries the default bearer identifier of the bearer that can be created or reserved on the target network side.
  • the difference from the method embodiment 5 and the method embodiment 6 is that the step S1006 does not trigger the target network side SGW to send the Modify to the PGW.
  • a Bearer Request message in the following message of the process, to trigger the target network side SGW to send a Modify Bearer Request message to the PGW;
  • the step is a PDN granularity. If multiple PDN connections (bearers) can be created or reserved on the target network side, multiple Create Session Request messages are triggered accordingly, and each Create Session Request message corresponds to a related PDN connection. A PDN connection that cannot be created or reserved on the target network side does not trigger this step;
  • the target network side MME receives a Create Session Response message sent by the target network side SGW.
  • the source network side MME obtains the information about the bearer that cannot be created or retained by the target network side according to the forwarding redirection response message sent by the target network side MME received in the foregoing step S1005. In this case, the step S1008 may be performed. The source network side MME can perform this step after receiving the forwarding redirect response message sent by the target network side MME after the step S1006 occurs before, after, or concurrently with the sequence.
  • the source network side MME sends a first delete session request (Delete Session Request) message to the source network side SGW.
  • a bearer that cannot be created or reserved on the target network side may trigger the source network side MME to the source network side.
  • the SGW sends a first deletion session request message carrying the operation identifier 01.
  • the 01 identifier is set to 1.
  • the 01 identifier is used to indicate that the source network side SGW sends a second deletion session request to the PGW.
  • the step is a PDN granularity. If multiple PDN connections cannot be created or reserved on the target network side, multiple first deletion session request messages are triggered correspondingly, and each first deletion session request message corresponds to a related PDN connection. Each first deletion session request message carries a default bearer identifier;
  • the source network side SGW sends a second delete session request (Delete Session Request) message to the PGW according to the received first deletion session request message carrying the operation identifier.
  • Delete Session Request a second delete session request
  • the second deletion session request message carries information about a bearer that cannot be created or reserved on the target network side;
  • the PGW may delete the target network side according to the information about the bearer that cannot be created or reserved on the target network side that is carried in the second deletion session request message. The information of the bearer created or reserved, and then sending a second delete session response (Delete Session Response) message to the source network side SGW;
  • the source network side MME receives a first delete session response (Delete Session Response) message sent by the source network side SGW.
  • Delete Session Response a delete session response
  • the source network side MME sends a third Delete Session Request message to the source network side SGW.
  • the source network side MME After deleting the bearer information that cannot be created or reserved on the target network side, the source network side MME initiates a deletion process for the remaining bearer context of the UE in the source network side SGW;
  • the step is the UE granularity.
  • the third delete session request message carries the SI identifier, and the SI identifier is set to 1, indicating that the source network side SGW releases all PDN connection contexts of the UE, and the 01 identifier is displayed at this time. Set to 0, so that the source network side SGW does not send a delete session request message to the PGW; S1014: The source network side MME receives a third delete session response (Delete Session Response) message sent by the source network side SGW.
  • Delete Session Response a third delete session response
  • the source network side MME may determine, according to the information about the bearer that cannot be created or reserved by the target network side, the source network side MME may also determine the basis information of the target network side created or reserved by the target network side MME. The information of the bearer that cannot be created or retained on the target network side. The information may be forwarded to the source network side MME by using the forwarding redirect response message, and the source network side MME determines that the target network side cannot create or reserve after receiving the forwarding redirect response message carrying the basis information of the destination network side to create or retain the bearer information. The information carried.
  • the source network side MME instructs the source network side service gateway to send a second deletion session request message to the PGW, which may trigger the PGW to delete the target network side that cannot be created or retained.
  • the bearer information is such that the redundant bearer information is not reserved in the PGW, and the network side bearer context resource is saved.
  • the source network side MME can obtain or retain the bearer according to the notification message or the target network side to learn the target network side.
  • the information of the bearer that cannot be created or reserved makes the source network side MME more flexible in knowing the information of the bearer that cannot be created or reserved on the target network side.
  • the deletion session request operation is classified, and the source network side and the packet data gateway are first.
  • the bearer information that cannot be created or reserved on the target network side is deleted, and then the bearer information that can be created or reserved on the source network side of the user equipment is deleted on the source network side, and the source network side deletes the bearer context information of the UE created by the source network side.
  • Operability and flexibility As shown in FIG. 11, the flowchart of the implementation of the ninth embodiment of the present invention is provided.
  • the embodiment is applicable to an application scenario in which the MME does not change and the SGW changes when the Handover process occurs.
  • the embodiment includes:
  • S 1101 The source network side HeNB triggers a Handover process
  • S1102 The source network side HeNB sends a Handover Required message to the MME.
  • the MME determines information about bearers that cannot be created or reserved on the target network side; The MME determines, according to the information about the bearer created or reserved by the target network side, the information about the bearer that cannot be created or reserved on the target network side, and the situation that the target network side cannot create or retain the bearer includes:
  • the MME determines that the created LIPA PDN connection cannot be reserved on the target network side; for example, the bearer context information of the UE saved by the MME itself includes the default bearer 5 and The context of the default bearer 6 is: the default bearer 6 is a LIPA PDN connection, the default bearer 5 is a regular PDN connection, and the source network side HeNB and the target network side HeNB are not in the same local home base station network. After the judgment, it can be determined that the target network side cannot create or retain the default bearer 6;
  • the MME may further determine, according to a local policy, information about a bearer that cannot be created or retained by the target network side, where the local policy may include an access PDN connection quantity and/or a bearer quantity control policy;
  • the MME sends a Create Session Request message to the target network side SGW.
  • the Create Session Request message carries the default bearer identifier of the bearer that can be created or reserved by the target network, and the S1104 does not trigger the target network side SGW to the PGW.
  • Sending a Modify Bearer Request message in the subsequent operation of the process, the MME sends a Modify Bearer Request message to the target network side SGW to trigger the target network side SGW to send a Modify Bearer Request message to the PGW;
  • S1106 The MME sends a first delete session request message to the source network side SGW.
  • the MME may be configured to send a first delete session request message carrying the operation identifier 01 to the source network side SGW.
  • the 01 flag is set to 1;
  • the step is a PDN granularity. If multiple PDN connections cannot be created or reserved on the target network side, multiple first deletion session request messages are triggered correspondingly, and each first deletion session request message corresponds to a related PDN connection. Each first deletion session request message carries a default bearer identifier;
  • the source network side SGW sends a second deletion session request message to the PGW according to the received first deletion session request message carrying the operation identifier.
  • the second deletion session request message carries information about bearers that cannot be created or reserved by the target network side
  • the PGW After receiving the second deletion session request message sent by the source network side SGW, the PGW deletes the target network side according to the information about the bearer that cannot be created or reserved on the target network side that is carried in the second deletion session request message. The information of the bearer created or reserved, and then sending a second delete session response message to the source network side SGW;
  • the MME receives a first deletion session response message sent by the source network side SGW.
  • the MME sends a third delete session request message to the source network side SGW.
  • the MME After deleting the bearer information that cannot be created or reserved on the target network side, the MME will initiate a deletion process for the remaining bearer context of the UE in the source network side SGW;
  • the step is the UE granularity.
  • the third delete session request message carries the SI identifier, and the SI identifier is set to 1, indicating that the source network side SGW releases all PDN connection contexts of the UE, and the 01 identifier is displayed at this time. Set to 0, so that the source network side SGW does not send a delete session request message to the PGW;
  • the MME receives the third delete session response message sent by the source network side SGW.
  • the ninth embodiment of the method provided by the embodiment of the present invention when the handover process occurs, by instructing the source network side service gateway to send a second deletion session request message to the PGW, triggering the PGW to delete the bearer information that cannot be created or reserved on the target network side. So that redundant bearer information is no longer reserved in the PGW.
  • the network side load Context resource is saved.
  • the source network side MME and the target network side MME are the same MME, which reduces the communication overhead between the network elements.
  • the deletion session request operation is classified, the source network side and The packet data gateway deletes the bearer information that cannot be created or reserved on the target network side, and then deletes the bearer information that can be created or reserved on the source network side of the user equipment on the source network side, and enhances the source network side to delete the UE created by the source network side.
  • the operability and flexibility of carrying context information As shown in FIG. 12, it is an implementation flowchart of Embodiment 10 of the method provided by the embodiment of the present invention. The embodiment is applicable to an application scenario in which the MME changes and the SGW does not change when the Handover process occurs.
  • the embodiment includes:
  • S1201 The source network side HeNB triggers a Handover process
  • S1202 The source network side HeNB sends a Handover Required message to the source network side MME.
  • S1203 After receiving the Handover Required message sent by the source network side HeNB, the source network side MME sends a Forward Relocation Request message to the target network side MME, where the Forward Relocation Request message is sent.
  • the Request message carries an EPS PDN Connections cell describing the bearer context information of the UE;
  • the target network side MME determines the information of the bearer that cannot be created or reserved on the target network side.
  • the target network side MME determines, according to the information about the bearer created or retained by the target network side, that the target network side cannot create or retain the bearer.
  • Information, the situation where the target network side cannot create or retain bearers can be divided into the following ways:
  • the target network side MME determines information about bearers that cannot be created or reserved by the target network side according to the local policy, where the local policy may include an access PDN connection quantity and/or a bearer context quantity control policy, and the target network at this time
  • the MME may not be able to successfully create all the bearers of the UE due to the foregoing control policy, and the part of the bearer may not be created or reserved on the target network side.
  • the bearer context delivered by the source network side MME includes the default bearer 5 and the default bearer 6. Context, but the target network side MME has created a bearer context due to the number of bearer contexts that have been created on it. The upper limit of the number can only create the default bearer 5. In this case, after the target network side MME judges, it can be determined that the target network side cannot create or retain the default bearer 6;
  • the target network side MME determines that the created LIPA PDN connection cannot be reserved on the target network side; for example, the bearer context information transmitted by the source network side MME includes
  • the default bearer 6 is a LIPA PDN connection
  • the default bearer 5 is a regular PDN connection
  • the source network side HeNB and the target network side HeNB are not in the same local home base station network.
  • the target network side MME sends a notification message to the source network side MME.
  • the notification message may be a Forward Relocation Response message
  • the Forward Relocation Response message may explicitly (directly) indicate the bearer information that cannot be created or reserved on the target network side, or may implicitly (indirectly) indicate the bearer information that cannot be created or reserved on the target network side.
  • the method can be implemented in one of the following ways or a combination thereof:
  • the Forward Relocation Response message carries the default bearer identifier or the access point name information, where the default bearer identifier or the access point name may directly correspond to the identifier of the bearer that cannot be created or reserved on the target network side, for example, the default.
  • the bearer identifier or the access point name may be included in the to-be-deleted context "Context to be removed" cell, and directly indicate the identifier of the bearer that the target network side cannot create or retain; or the default bearer identifier or the access point name corresponds to the target
  • the identifier of the bearer that can be created or reserved on the network side and implicitly indicates the bearer information that cannot be created or reserved on the target network side.
  • the source network side MME can create the bearer context information of the locally stored user equipment and the learned target network side. Or the information of the carried bearer, and the information about the bearer that cannot be created or retained by the remaining target network side; or
  • the Forward Relocation Response message carries an EPS bearer status cell, and different values (for example, 1 or 0) in the corresponding bits in the EPS bearer status cell respectively indicate the target.
  • the MME learns, according to the EPS bearer status cell, information about a bearer that cannot be created or retained by the target network side; or
  • the Forward Relocation Response message carries an LPCNSI identifier to indicate a LIPA PDN connection that cannot be created or reserved on the target network side;
  • the target network side MME sends a Modify Bearer Request message to the SGW to instruct the SGW to send a Modify Bearer Request message to the PGW.
  • the Forward Relocation Response message will not carry the SGWCI identifier to indicate that the SGW in the Handover process has not changed;
  • the source network side MME learns, according to the received Forward Relocation Response message sent by the target network side MME, information about the bearer that cannot be created or reserved on the target network side;
  • S 1207 The source network side MME sends a first delete session request message to the SGW.
  • the source network side MME may be configured to send the first delete session request message carrying the operation identifier 01 to the SGW.
  • the 01 identifier is set to 1.
  • the 01 identifier is used to instruct the SGW to send a second delete session request message to the PGW.
  • the step is a PDN granularity. If multiple PDN connections cannot be created or reserved on the target network side, multiple first deletion session request messages are triggered correspondingly, and each first deletion session request message corresponds to a related PDN connection. Each first deletion session request message carries a default bearer identifier;
  • the SGW sends a second deletion session request message to the PGW according to the received first deletion session request message that carries the operation identifier.
  • the second deletion session request message carries information about bearers that cannot be created or reserved by the target network side
  • the PGW After receiving the second deletion session request message sent by the SGW, the PGW is configured according to the Deleting the bearer information that cannot be created or reserved by the target network side carried in the session request message, deleting the bearer information that cannot be created or reserved by the target network side, and then sending a second delete session response message to the SGW;
  • the source network side MME receives the first delete session response message sent by the SGW.
  • the source network side MME may determine, according to the information about the bearer that cannot be created or reserved by the target network side, the source network side MME may also determine the basis information of the target network side created or reserved by the target network side MME. The information of the bearer that cannot be created or retained on the target network side. The information may be forwarded to the source network side MME by using the forwarding redirect response message, and the source network side MME determines that the target network side cannot create or reserve after receiving the forwarding redirect response message carrying the basis information of the destination network side to create or retain the bearer information. The information carried.
  • the source network side MME instructs the serving gateway to send a second deletion session request message to the PGW, which may trigger the PGW to delete the bearer information that cannot be created or reserved on the target network side. Therefore, the redundant bearer information is not reserved in the PGW, and the network side bearer context resource is saved.
  • the source network side MME can create or retain the bearer according to the notification message or the target network side, and learn that the target network side cannot be created or The information of the reserved bearer makes the source network side MME more flexible in knowing the information of the bearer that cannot be created or reserved on the target network side.
  • the deletion session request operation is classified, and the source network side and the packet data gateway delete the target network first.
  • the bearer information that can be created or reserved on the side of the source network, and the bearer information that can be created or reserved on the source network side of the user equipment is deleted on the source network side, and the operability of deleting the bearer context information of the UE created by the source network side is enhanced. flexibility. As shown in FIG.
  • a mobility management network element includes: a learning unit 1301, configured to learn information about a bearer that cannot be created or reserved on a target network side; and a sending unit 1302, configured to After the learning unit 1301 knows the information of the bearer that cannot be created or guaranteed by the target network side, the trigger source network side service gateway sends the second deletion to the packet domain data network gateway.
  • the second delete session request message carries information of a bearer that cannot be created or created or reserved by the target network side.
  • the learning unit 1301 may be implemented in the following two manners: Configuration mode 1: The learning unit 1301 includes:
  • a first receiving unit configured to receive a notification message sent by the target network side mobility management network element, where the notification message carries an identifier or an access point name of the bearer that cannot be created or reserved by the target network side;
  • a first determining unit configured to: after the first receiving unit receives the notification message of the identifier or the access point name of the bearer that cannot be created or reserved on the target network side, directly learn, according to the notification message, that the target network side cannot Information about the bearer created or retained; or
  • a second receiving unit configured to receive a notification message sent by the target network side mobility management network element, where the notification message carries an identifier or an access point name of the bearer that can be created or reserved by the target network side;
  • a second determining unit configured to: after the second receiving unit receives the notification message of the identifier or the access point name of the bearer that can be created or reserved by the target network, according to the bearer context information of the locally stored user equipment, and the The identifier of the bearer or the name of the access point that can be created or reserved on the target network side to determine the bearer information that cannot be created or reserved on the target network side; or
  • a third receiving unit configured to receive a notification message sent by the target network side mobility management network element, where the notification message carries an EPS bearer status cell, where the EPS bearer status cell respectively indicates a bearer that the target network side can create or reserve And bearers that cannot be created or retained on the target network side;
  • a third determining unit configured to: after the third receiving unit receives the notification message carrying the EPS bearer status cell, learn, according to the EPS bearer status cell, information about the bearer that cannot be created or retained by the target network side; or
  • a fourth receiving unit configured to receive a notification message sent by the target network side mobility management network element, where the notification message carries a LIPA PDN connection unsupported identifier
  • a fourth determining unit configured to receive, at the fourth receiving unit, the LIPA carrying the PDN connection After the identifier notification message is received, the LIPA PDN connection that cannot be created or reserved by the target network side is obtained according to the LIPA PDN connection.
  • the configuration unit 1301 is specifically configured to determine, according to the information about the bearer created or retained by the target network side, information about the bearer that cannot be created or reserved on the target network side, and the basis information of the target network side to create or retain the bearer includes the following information.
  • the learning unit 1301 specifically includes:
  • a fifth determining unit configured to determine, according to whether the bearer context information of the user equipment is consistent with an EPS bearer status cell, information about a bearer that cannot be created or retained by the target network side; or information that can be created or retained, where
  • the local policy of the target network side includes an access PDN connection quantity and/or a bearer context quantity control policy; or
  • a seventh determining unit configured to determine, according to the information about whether the target network side supports creating a LIPA PDN connection, to determine a LIPA PDN connection that cannot be created or retained by the target network side.
  • the sending unit 1302 is specifically configured to: after the learning unit 1301 learns the information about the bearer that cannot be created or reserved on the target network side, send the first delete session request message carrying the operation identifier to the source network side serving gateway, where the first The delete session request message carries the bearer information that cannot be created or reserved by the target network side, and the operation identifier triggers the source network side service gateway to send a second delete session request message to the packet domain data network gateway.
  • the sending unit 1302 is further configured to: after deleting the bearer information that cannot be created or reserved on the target network side, send a third delete session request message to the source network side serving gateway, where the third delete session request message indicates the The source network side service gateway deletes the bearer information that can be created or reserved by the remaining target network side of the user equipment.
  • the mobility management network element provided by the embodiment of the present invention may be notified by the notification unit or the target network.
  • the information about the bearer that the network side cannot create or retain is obtained by the network side to create or retain the bearer information, so that the manner of obtaining the bearer information that cannot be created or retained by the target network side is more flexible, and further, the sending unit is used to delete the information to be sent.
  • the session request operation is classified, and the source network side and the packet data gateway delete the bearer information that cannot be created or reserved on the target network side, and then delete the bearer information that can be created or retained by the remaining target network side of the user equipment on the source network side.
  • the source network side deletes the operability and flexibility of the bearer context information of the UE it creates. As shown in FIG.
  • another mobility management network element includes: a determining unit 1401, configured to determine information about a bearer that cannot be created or reserved on a target network side; and a sending unit 1402, configured to determine a unit After determining the bearer information that cannot be created or reserved on the target network side, the 1401 sends a notification message to the source network side mobility management network element, indicating that the source network side mobility management network element learns the bearer information that cannot be created or reserved by the target network side.
  • the embodiment of the present invention further provides a mobility management network element, so that the target network side is provided, except that the source network side mobility management network element obtains the information of the bearer that cannot be created or retained by the target network side by using the notification message.
  • the mobility management network element includes:
  • the determining unit 140 is configured to determine the basis information of the target network side to create or retain the bearer.
  • the sending unit 1402 is configured to determine the unit 1401, and after determining the basis information of the target network side to create or retain the bearer, move the management network element to the source network side. Sending the base information of the target network side to create or retain the bearer, and instructing the source network side mobility management network element to determine the bearer information that the target network side cannot create or retain.
  • the basis information for creating or retaining the bearer on the target network side includes one of the following information or any combination thereof: bearer context information of the UE, an EPS bearer status cell, a local policy on the target network side, and whether the target network side supports the creation of the LIPA.
  • the mobile management network element provided by the above two embodiments sends a notification message to the source network side mobility management network element by the sending unit or the basis information of the target network side to create or retain the bearer, so that the source network side mobility management network element learns the target network side. Information about bearers that cannot be created or retained. As shown in FIG.
  • a serving gateway SGW includes: a receiving unit 1501, configured to receive a trigger indication sent by a source network side mobility management network element, where the trigger indication is the source network side
  • the mobile management network element obtains information about the bearer that cannot be created or retained by the target network side, and then sends the information;
  • the sending unit 1502 is configured to send, according to the trigger indication received by the receiving unit, a second delete session request message to the packet domain data network gateway, where the second delete session request message carries the target network side cannot create or reserve Carrying information, so that the packet domain data network gateway deletes the bearer information that cannot be created or reserved by the target network side.
  • the receiving unit 1501 is specifically configured to receive a first deletion session request message that is sent by the source network side mobility management network element and that carries the operation identifier.
  • the sending unit 1502 is specifically configured to be used according to the first deletion session request message. And an operation identifier, sending a second deletion session request message to the packet domain data network gateway.
  • a processing system for a bearer includes: a source network side mobility management network element 1601, a source network side service gateway 1602, and a packet domain data network gateway 1603, where
  • the source network side mobility management network element 1601 is configured to send the source network side service gateway 1602 to the packet domain data network gateway 1603 after obtaining the bearer information that cannot be created or reserved on the target network side. Sending a second delete session request message;
  • the source network side service gateway 1602 is configured to receive a trigger indication sent by the source network side mobility management network element 1601, and send a second deletion session request message to the packet domain data network gateway 1603 according to the trigger indication, where the The second delete session request message carries information about bearers that cannot be created or reserved by the target network side;
  • the packet domain data network gateway 1603 is configured to: after receiving the second deletion session request message sent by the source network side service gateway 1602, according to the bearer that cannot be created or reserved by the target network side carried in the second deletion session request message Information, deleting the information of the bearer that cannot be created or reserved on the target network side.
  • the source network side mobility management network element 1601 includes:
  • the obtaining unit is configured to learn information about the bearer that cannot be created or reserved on the target network side
  • the sending unit is configured to: after the learned unit learns the information about the bearer that cannot be created or reserved on the target network side, trigger the source network side service gateway to the grouping
  • the domain data network gateway sends a second delete session request message
  • the source network side serving gateway 1602 includes:
  • a receiving unit configured to receive a trigger indication sent by the source network side mobility management network element, where the trigger indication is sent after the source network side mobility management network element learns the bearer information that cannot be created or reserved by the target network side;
  • a sending unit configured to send, according to the trigger indication received by the receiving unit, a second delete session request message to the packet domain data network gateway.
  • system further includes a target network side mobility management network element, and the target network side mobility management network element is configured to send a notification message to the source network side mobility management network element 1601, so that the source network side mobility management network
  • the element 1601 learns, according to the notification message, information about a bearer that cannot be created or retained by the target network side; or
  • Mobile management network element 1601 The source network side creates or retains the bearer according to the information, so that the source network side mobile management network element
  • the information about the bearer that cannot be created or reserved on the target network side is determined according to the information about the bearer created or reserved by the target network side, where the information about the base station side to create or retain the bearer includes one of the following information or any combination thereof. : Bearer context information and EPS bearer status information of the user equipment.
  • the source network side mobility management network element 1601 and the target network side mobility management network element may be the same mobility management network element. In this case, the target network side mobility management network element cannot be created or reserved on the target network side.
  • the first delete session request message may be sent to the source network side service gateway.
  • Deleting the session request message may trigger the PGW to delete the bearer information that cannot be created or reserved on the target network side, so that the redundant bearer information is not retained in the PGW, and the network side bearer context resource is saved.
  • the source network side mobile management network element The information about the bearer that cannot be created or reserved on the target network side can be obtained through the notification message sent by the target network side mobility management network element, or the information about the bearer that cannot be created or reserved on the target network side can be determined, so that the source network side mobile management network element is known.
  • the manner of the bearer information that cannot be created or retained on the target network side is more flexible.
  • the delete session request operation is classified.
  • the source network side and the packet data gateway delete the bearer information that cannot be created or reserved on the target network side, and then Source network side deletes user equipment remaining

Landscapes

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

Abstract

本发明涉及通信技术领域，尤其涉及一种承载的处理方法、系统及装置。本发明提供的一种承载的处理方法，在源网络侧移动管理网元获知目标网络侧不能创建或保留的承载的信息后，所述源网络侧移动管理网元触发源网络侧服务网关向分组域数据网络网关发送第二删除会话请求消息，所述第二删除会话请求消息携带所述目标网络侧不能创建或保留的承载的信息。通过本发明提供的方法，使得在发生移动管理流程时，分组域数据网络网关可以删除目标网络侧不能创建或保留的承载的信息。

Description

说 明 书
一种承载的处理方法、 系统及装置 技术领域
本发明涉及通信技术领域， 尤其涉及一种承载的处理方法、 系统及装置。
背景技术
在网络向宽带化、 移动化发展的过程中， 3GPP ( The 3rd Generation Partnership Program, 第三代合作伙伴计划）在移动接入网侧提出了 LTE ( Long Term Evolution, 长期演进）计划， 即 E-UTRAN ( Evolved Universal Mobile Telecommunication System Territorial Radio Access Network , 演进通用移动通信 系统陆地无线接入网）；在核心网侧提出了 SAE ( System Architecture Evolution, 系统架构演进）计划，即 EPC( Evolved Packet Core,演进分组核心网 )。 E-UTRAN 和 EPC 构成了 EPS ( Evolved Packet System, 演进分组系统）。 UE ( User Equipment , 用户设备） 可通过 E-UTRAN , UTRAN ( Universal Mobile Telecommunication System Territorial Radio Access Network , 通用移动通信系统 陆地无线接入网；)， GERAN( GSM EDGE Radio Access Network, GSM/EDGE 无 线接入网）中的任意一种接入方式接入 EPC。图 1为当前无线演进网络架构图。
如图 1所示， EPC具体包括但不限于 MME ( Mobility Management Entity, 移动性管理实体）、 SGSN ( Serving GPRS Support Node,服务 GPRS支持节点 )、 SGW ( Serving Gateway, 服务网关 )和 PGW ( PDN Gateway, 分组域数据网网 关）。 其中， MME/SGSN主要负责 NAS ( Non Access Stratum, 非接入层 )信令 管理、 承载管理以及用户空闲模式下的跟踪和寻呼管理等功能； SGW 主要负 责本地的移动性锚点和 3GPP系统内部的移动性锚点以及合法监听相关信息等 功能； PGW主要负责策略执行和计费以及合法监听相关功能。 其中， MME和 S G S N统称为移动管理网元。
如图 1所示， 2G网络的无线接入部分为 GERAN,由 BTS( Base Transceiver Station, 基站收发台 )和 BSC ( Base Station Controller, 基站控制器 )构成； 3G 网络的无线接入部分为 UTRAN, 由 RNC ( Radio Network Controller, 无线网 络控制器 )和 NodeB (节点 B )构成； LTE网络的无线接入部分为 E-UTRAN, 由 eNodeB ( Evolved NodeB, 演进型基站）构成。
当从一个无线接入网网元的服务范围移动到另一无线接入网网元的服务 范围时， 处于空闲状态的 UE可触发 TAU ( Tracking Area Update, 跟踪区位置 更新 ) 流程或 RAU ( Routing Area Update, 路由区位置更新 ) 流程； 处于连接 状态的 UE可触发 Handover (切换 ) 流程。 其中， 上述 TAU流程、 RAU流程 以及 Handover流程统称为移动管理流程。该移动管理流程可能触发 UE对应的 MME/SGSN发生变化， 以及可能触发该 UE对应的 SGW发生变化。 当触发上 述网元发生变化时， 则需在目标网络侧建立该 UE的承载上下文， 并在源网络 侧删除该 UE的承载上下文。 本发明实施例， 将 UE移动前所在的网络称为源 网络侧， 将 UE移动后所在的网络称为目标网络侧。
图 2为 UE触发 TAU流程的实现过程示意图， 其中：
步骤 S202-步骤 S203： UE向目标网络侧 MME发送 TAU请求消息； 步骤 S204-步骤 S207: 目标网络侧 MME通过上下文响应消息从源网络侧 MME获取 UE的 7|载上下文信息， 并通过上下文确认消息指示源网络侧 MME 该 TAU流程中的 SGW已发生改变；
步骤 S208-步骤 S211 : 在目标网络侧创建 UE的承载上下文， 并更新目标 网络侧 SGW和 PGW之间的承载；
步骤 S218-步骤 S219:删除源网络侧 MME和源网络侧 SGW上该 UE的承 载上下文。
通过对现有技术的分析， 发明人认为现有技术至少存在以下问题： 在发生移动管理流程时，现有技术中只在源网络侧 MME与源网络侧 SGW 删除源网络侧为 UE所创的承载上下文， 而默认分组域数据网络网关 PGW将 继续保留为 UE所创的承载上下文， 然而， 在发生移动管理流程时， 由于本地 策略或其他原因， 某些承载可能在目标网络侧不能创建或保留， 使得这些承载 的信息可能长时间地存储在 PGW中，造成 EPC网络中承载上下文资源的浪费。
发明内容
本发明实施例提供了一种承载的处理方法、 系统及装置， 使得在发生移动 管理流程时， 分组域数据网络网关 PGW可以删除目标网络侧不能创建或保留 的承载的信息。
本发明实施例提供的一种承载的处理方法， 该方法包括：
源网络侧移动管理网元获知目标网络侧不能创建或保留的承载的信息； 所述源网络侧移动管理网元触发源网络侧服务网关向分组域数据网络网 关发送第二删除会话请求消息， 所述第二删除会话请求消息携带所述目标网络 侧不能创建或保留的承载的信息， 以便于所述分组域数据网络网关删除所述目 标网络侧不能创建或保留的承载的信息。 本发明实施例提供的另一种承载的处理方法， 该方法包括：
源网络侧服务网关接收源网络侧移动管理网元发送的触发指示， 所述触发 指示是所述源网络侧移动管理网元获知目标网络侧不能创建或保留的承载的 信息之后发送的；
源网络侧服务网关根据所述触发指示， 向分组域数据网络网关发送第二删 除会话请求消息， 所述第二删除会话请求消息携带所述目标网络侧不能创建或
创建或保留的承载的信息。
本发明实施例提供的一种移动管理网元， 包括：
获知单元， 用于获知目标网络侧不能创建或保留的承载的信息； 发送单元， 用于在所述获知单元获知目标网络侧不能创建或保留的承载的 信息后， 触发源网络侧服务网关向分组域数据网络网关发送第二删除会话请求 消息， 所述第二删除会话请求消息携带所述目标网络侧不能创建或保留的承载 的信息， 以便于所述分组域数据网络网关删除所述目标网络侧不能创建或保留 的承载的信息。
本发明实施例提供的一种服务网关， 包括：
接收单元， 用于接收源网络侧移动管理网元发送的触发指示， 所述触发指 示是源网络侧移动管理网元获知目标网络侧不能创建或保留的承载的信息之 后发送的；
发送单元， 用于根据所述接收单元接收到的触发指示， 向分组域数据网络 网关发送第二删除会话请求消息， 所述第二删除会话请求消息携带所述目标网 络侧不能创建或保留的承载的信息， 以便于所述分组域数据网络网关删除所述 目标网络侧不能创建或保留的承载的信息。
本发明实施例提供的一种承载的处理系统， 包括： 源网络侧移动管理网元， 源网络侧服务网关， 分组域数据网络网关， 其中，
所述源网络侧移动管理网元， 用于在获知目标网络侧不能创建或保留的承 载的信息后， 触发源网络侧服务网关向分组域数据网络网关发送第二删除会话 请求消息；
所述源网络侧服务网关， 用于接收源网络侧移动管理网元发送的触发指 示，并根据所述触发指示，向分组域数据网络网关发送第二删除会话请求消息， 所述第二删除会话请求消息携带所述目标网络侧不能创建或保留的承载的信 息；
分组域数据网络网关， 用于在接收到源网络侧服务网关发送的第二删除会 话请求消息后， 根据所述第二删除会话请求消息中携带的目标网络侧不能创建 或保留的承载的信息， 删除所述目标网络侧不能创建或保留的承载的信息。 本发明实施例提供的一种承载的处理方法和系统， 以及移动管理网元和服 务网关， 在发生移动管理流程时， 源网络侧移动管理网元可以获知目标网络侧 不能创建或保留的承载的信息， 并触发 PGW删除目标网络侧不能创建或保留 的承载的信息， 使得 PGW中不再保留冗余的承载信息， 节省了网络侧承载上 下文资源。
附图说明
图 1为当前无线演进网络架构图；
图 2为 UE触发 TAU流程的实现过程示意图；
图 3为本发明实施例一提供的一种承载的处理方法；
图 4为本发明实施例二提供的一种承载的处理方法；
图 5为本发明实施例三提供的一种承载的处理方法；
图 6为本发明实施例四提供的一种承载的处理方法；
图 7为本发明实施例提供的方法实施例五的实现流程图；
图 8为本发明实施例提供的方法实施例六的实现流程图；
图 9为本发明实施例提供的方法实施例七的实现流程图；
图 10为本发明实施例提供的方法实施例八的实现流程图；
图 11为本发明实施例提供的方法实施例九的实现流程图；
图 12为本发明实施例提供的方法实施例十的实现流程图；
图 13为本发明实施例提供的一种移动管理网元；
图 14为本发明实施例提供的另一种移动管理网元；
图 15为本发明实施例提供的一种服务网关；
图 16为本发明实施例提供的一种承载的处理系统。
具体实施方式
下面将结合本发明实施例中的附图， 对本发明实施例中的技术方案进行清 楚、 完整地描述。
如图 3所示，为本发明实施例一提供的一种承载的处理方法，该方法包括： S301 : 源网络侧移动管理网元获知目标网络侧不能创建或保留的承载的信 息。 标网络侧不能创建或保留的承载的信息：
方式一， 由目标网络侧通知： 所述源网络侧移动管理网元接收目标网络侧 移动管理网元发送的通知消息， 根据所述通知消息获知目标网络侧不能创建或 保留的承载的信息， 其更为具体的实现方式下述实施例将详细描述。
方式二， 源网络侧移动管理网元自身确定： 所述源网络侧移动管理网元才艮 据目标网络侧创建或保留承载的依据信息确定目标网络侧不能创建或保留的 承载的信息， 所述目标网络侧创建或保留承载的依据信息包括以下信息之一或 其任意组合： UE的承载上下文信息、 EPS承载状态信元、 目标网络侧的本地 策略以及目标网络侧是否支持创建 LIPA ( Local IP Access ,本地 IP接入 ) PDN ( Packet Data Network, 分组数据网络）连接的信息； 其中， 当移动管理流程 网元为同一移动管理网元时， 所述 UE的 载上下文信息、 目标网络侧的本地 策略以及目标网络侧是否支持创建 LIPA PDN连接的信息为所述源网络侧移动 管理网元自身保存的， 所述的 EPS承载状态信元为 UE发送的； 当移动管理流 程中移动管理网元发生变化， 即源网络侧移动管理网元与目标网络侧移动管理 网元为不同的移动管理网元时， 所述 UE的承载上下文信息为所述源网络侧移 动管理网元自身保存的， 所述的 EPS承载状态信元为所述 UE发送给所述目标 网络侧移动管理网元并由所述目标网络侧移动管理网元转发给所述源网络侧 动管理网元的， 需要注意的是， 在触发切换流程时， 所述目标网络侧创建或保 留承载的依据信息不包括 EPS承载状态信元。
S302: 所述源网络侧移动管理网元触发源网络侧服务网关向分组域数据网 络网关发送第二删除会话请求消息， 所述第二删除会话请求消息携带所述目标 网络侧不能创建或保留的承载的信息， 以便于所述分组域数据网络网关删除所 述目标网络侧不能创建或保留的承载的信息。
其中， 所述第二删除会话请求消息可以通过所述源网络侧移动管理网元向 所述源网络侧服务网关 SGW发送的携带操作标识（ Operation Indication,筒称： 01 ) 的第一删除会话请求消息来实现。 所述源网络侧服务网关 SGW根据所述 操作标识， 触发向分组域数据网络网关 PGW发送第二删除会话请求消息， 其 中一个具体的实施方式是将所述操作标识的设置为特定值， 例如 1; 进一步地， 若所述第一删除会话请求消息未设置操作标识或者操作标识设置为非特定值 时， 所述源网络侧 SGW不会向所述 PGW发送第二删除会话请求消息。
其中， 所述第一删除会话请求消息携带所述目标网络侧不能创建或保留的 承载的信息， 所述源网络侧 SGW根据接收的第一删除会话请求消息， 向 PGW 发送第二删除会话请求消息， 当 PGW接收第二删除会话请求消息后， 删除所 述目标网络侧不能创建或保留的承载的信息。
本发明实施例提供的一种承载的处理方法， 在发生移动管理流程时， 源网 络侧移动管理网元可以获知目标网络侧不能创建或保留的承载的信息， 并可以 通过源网络侧触发 PGW删除目标网络侧不能创建或保留的承载的信息， 使得 PGW中不再保留冗余的承载信息， 节省了网络侧的承载上下文资源。 如图 4所示，为本发明实施例二提供的一种承载的处理方法，该方法包括： S401: 目标网络侧移动管理网元确定目标网络侧不能创建或保留的承载的 信息。
其中， 所述目标网络侧移动管理网元根据目标网络侧创建或保留承载的依 据信息确定目标网络侧不能创建或保留的承载的信息， 所述目标网络侧创建或 保留承载的依据信息包括以下信息之一或其任意组合： 用户设备的承载上下文 建 LIPA PDN连接的信息。 若移动管理网元未发生变化， 即目标网络侧移动管 理网元和源网络侧移动管理网元为同一移动管理网元， 所述目标网络侧移动管 理网元获取自身保存的用户设备的承载上下文信息、 目标网络侧的本地策略和 目标网络侧是否支持创建 LIPA PDN 连接的信息， 以及获取用户设备发送的 EPS承载状态信元； 若移动管理网元发生变化， 即目标网络侧移动管理网元和 源网络侧移动管理网元为不同的移动管理网元， 所述目标网络侧移动管理网元 获取自身保存的目标网络侧的本地策略和目标网络侧是否支持创建 LIPA PDN 连接的信息， 以及获取源网络侧移动管理网元发送的用户设备的承载上下文信 息和用户设备发送的 EPS承载状态信元。
Figure imgf000009_0001
除通过通知消息使源网络侧移动管理网元获知目标网络侧不能创建或保 的承载的信息外，本发明实施例还提供另一种承载的处理方法，如图 5所示，
Figure imgf000009_0002
建或保留承载的依据信息确定目标网络侧不能创建或保留的承载的信息， 具体 地， 该方法包括：
S501 : 目标网络侧移动管理网元确定目标网络侧创建或保留承载的依据信 息； 标网络侧创建或保留承载的依据信息， 指示源网络侧移动管理网元确定目标网 络侧不能创建或保留的承载的信息。 以上两个实施例提供的承载的处理方法， 在发生移动管理流程时， 通过向 源网络侧移动管理网元发送通知消息或者目标网络侧创建或保留承载的依据 信息， 使得源网络侧移动管理网元可以获知目标网络侧不能创建或保留的承载 的信息。 如图 6所示，为本发明实施例四提供的一种承载的处理方法，该方法包括：
S601 : 源网络侧服务网关接收源网络侧移动管理网元发送的触发指示， 所 述触发指示是所述源网络侧移动管理网元获知目标网络侧不能创建或保留的 承载的信息之后发送的。
其中， 所述源网络侧服务网关接收源网络侧移动管理网元发送的触发指示 包括： 源网络侧移动管理网元发送的携带操作标识的第一删除会话请求消息， 其中， 该操作标识设置为特定值， 例如 1。
S602: 所述源网络侧服务网关根据所述触发指示， 向分组域数据网络网关 发送第二删除会话请求消息， 所述第二删除会话请求消息携带所述目标网络侧 不能创建或保留的承载的信息， 以便于所述分组域数据网络网关删除所述目标 网络侧不能创建或保留的承载的信息。
其中， 所述源网络侧服务网关判断所述触发指示是否携带设置为特定值的 操作标识， 如果是， 则向分组域数据网络网关发送第二删除会话请求消息。
所述分组域数据网络网关在接收到源网络侧服务网关发送的第二删除会 话请求消息后， 删除目标网络侧不能创建或保留的承载的信息。
本发明实施例提供的一种承载的处理方法， 在发生移动管理流程时， 源网 络侧 SGW根据源网络侧移动管理网元发送的触发指示， 触发 PGW删除目标 网络侧不能创建或保留的承载的信息，使得 PGW中不再保留冗余的承载信息， 节省了网络侧的承载上下文资源。 本发明实施例适用于所有的无线接入网络类型， 以及所有的移动管理流程 类型。 为使本领域普通技术人员清楚、 完整地理解本发明的技术方案， 以下分 别以 TAU流程和 Handover流程为例进行说明。
如图 7所示， 为本发明实施例提供的方法实施例五的实现流程图， 该实施 例针对发生 TAU流程时 MME和 SGW同时发生变化的应用场景， 即目标网络 侧 MME和源网络侧 MME不是同一 MME,目标网络侧 SGW和源网络侧 SGW 不是同一 SGW的应用场景， 该实施例包括：
S701 : UE向目标网络侧 MME发送跟踪区位置更新请求（ TAU Request ) 消息；
所述 TAU Request消息包含 GUTI ( Globally Unique Temporary Identity, 全 局唯一的临时标识）标识和 EPS 7 载状态（ EPS bearer status )信元， GUTI标 识用于对源网络侧 MME进行定位， EPS承载状态信元用于描述 UE中的 EPS 承载上下文激活状态信息；
其中， EPS bearer status信元用 16个 EBI ( EPS Bearer Identity, EPS承载 标识） 标识来描述承载上下文激活状态， 每个 EBI 占一个比特， 其中， EBI(O)— EBI(4)置为 "0" , 以备用， EBI(5)— EBI(15)用 "0" 表示对应的 EPS 承载上下文是去激活的， 用 "Γ 表示对应的 EPS承载上下文是激活的；
S702: 目标网络侧 MME 向源网络侧 MME发送上下文请求 （Context Request ) 消息；
S703: 源网络侧 MME在收到目标网络侧 MME发送的 Context Request消 息后， 向目标网络侧 MME发送上下文响应 （ Context Response ) 消息；
其中， 所述 Context Response消息包含 UE的承载上下文信息， 所述 UE 的承载上下文信息通过 EPS PDN Connections信元描述，具体包括与 PDN连接 相关的 载上下文（ Bearer Context M言元、缺省承载标识（ Linked EPS Bearer ID ) 以及接入点名 （Access Point Name, 筒称： APN )等信息， 所述承载上下文信 元包含承载标识（ EPS Bearer ID )、 承载服务质量（ Bearer Level QoS )、 服务网 关用户名 IP地址以及隧道断点标识（ Tunnel Endpoint Identifier, 筒称： TEID ) 等信息； 其中， 每个 PDN连接通过其对应的缺省承载（Default Bearer )的标识 来唯一标识， 每个 PDN连接的上下文包含该 PDN连接所有的承载上下文， 具 体地， 包含一个缺省承载对应的承载上下文， 以及零到多个专有承载对应的承 载上下文， 其中每个承载上下文通过承载标识来唯一标识；
S704： 目标网络侧 MME确定目标网络侧不能创建或保留的承载的信息； 其中， 所述目标网络侧 MME根据目标网络侧创建或保留承载的依据信息 确定目标网络侧不能创建或保留的承载的信息， 目标网络侧不能创建或保留承 载的情形可分为以下几种方式：
( 1 )所述目标网络侧 MME根据其从 UE获知的 EPS 承载状态信元和从 源网络侧 MME获知的 UE的承载上下文信息不一致， 确定目标网络侧不能创 建或保留的承载的信息， 其中， 不一致的情形为： 从 UE获得的 EPS承载状态 信元指示激活的承载和源网络侧 MME传递过来的承载不——对应；例如， EPS 承载状态信元指示缺省承载 5存在， 源网络侧 MME传递过来的承载上下文中 包含缺省承载 5和缺省承载 6的上下文， 此时， 目标网络侧 MME经判断后， 即可确定目标网络侧不能创建或保留缺省承载 6;
( 2 )所述目标网络侧 MME根据本地策略确定目标网络侧不能创建或保留 的承载的信息， 其中所述本地策略可以包含接入 PDN连接数量和 /或承载上下 文数量控制策略， 此时目标网络侧 MME可能由于上述控制策略， 不能成功创 建 UE的所有承载， 导致部分承载在目标网络侧不能创建或保留； 例如， 源网 络侧 MME传递的承载上下文包含了缺省承载 5和缺省承载 6的上下文， 但目 标网络侧 MME由于其上已经创建的承载上下文数目已达许可创建承载上下文 数目的上限， 只能创建缺省承载 5 , 此时， 目标网络侧 MME经判断后， 即可 确定目标网络侧不能创建或保留缺省承载 6;
( 3 ) 当在源网络侧创建 LIPA PDN连接的 UE发生移动时， 目标网络侧 MME判断所述创建的 LIPA PDN连接在目标网络侧不能保留； 例如， 源网络 侧 MME传递的承载上下文信息中包含了缺省承载 5和缺省承载 6的上下文， 其中， 缺省承载 6为 LIPA PDN连接， 缺省承载 5为常规 PDN连接， 源网络侧 HeNB ( Home Evolved NodeB , 家庭演进基站 )和目标网络侧 HeNB不在同一 个本地家庭基站网络中， 此时， 目标网络侧 MME经判断后， 即可确定目标网 络侧不能创建或保留缺省承载 6;
S705: 目标网络侧 MME向源网络侧 MME发送通知消息， 本实施例中， 所述通知消息可以采用上下文应答（Context Ack ) 消息；
其中， 所述 Context Ack消息可以显式（直接）指示目标网络侧不能创建 或保留的承载的信息， 也可以隐式（间接）指示目标网络侧不能创建或保留的 承载的信息， 其具体实现方式可以通过以下方式之一或其组合实现：
( 1 ) Context Ack消息携带缺省承载标识（ Linked EPS Bearer ID )或接入 点名 （Access Point Name, 筒称： APN )信息， 其中， 该缺省承载标识或接入 点名可以直接对应于目标网络侧不能创建或保留的承载的标识， 例如所述缺省 承载标识或接入点名可以包含在待删除上下文 "Context to be removed"信元中， 直接指示目标网络侧不能创建或保留的承载的标识； 或者， 该缺省承载标识或 接入点名对应于目标网络侧可以创建或保留的承载的标识， 隐式指示目标网络 侧不能创建或保留的承载的信息， 源网络侧 ΜΜΕ通过本地存储的用户设备的 承载上下文信息和所述获知的目标网络侧可以创建或保留的承载的信息， 获知 剩余的目标网络侧不能创建或保留的承载的信息； 或者，
( 2 ) Context Ack消息携带 EPS bearer status信元， 该 EPS bearer status信 元中对应的比特位中的不同取值（例如 1或 0 )分别指明了目标网络侧能创建 或保留的承载和目标网络侧不能创建或保留的承载， 源网络侧 MME根据所述 EPS bearer status信元获知目标网络侧不能创建或保留的承载的信息； 或者，
( 3 ) Context Ack 消息携带 LIPA PDN 连接不支持标识 （ LIPA PDN Connection Not Support Indication, 筒称： LPCNSI ), 以指示所述 LIPA PDN 连接在目标网络侧不能创建或保留；
此外， Context Ack 消息还携带了服务网关变化标识 （ SGW Change Indication, 筒称： SGWCI )标识， 以指示该 TAU流程已选择了新的 SGW;
S706: 目标网络侧 MME向目标网络侧 SGW发送创建会话请求（ Create Session Request ) 消息；
所述 Create Session Request消息携带目标网络侧能够创建或保留的承载的 缺省承载标识， 此外， 该步骤 S706将触发执行步骤 S707;
其中， 该步骤为 PDN粒度的， 若多个 PDN连接（承载） 能够在目标网络 侧创建或保留， 则相应地触发多条 Create Session Request 消息， 每条 Create Session Request消息对应相关的 PDN连接，对于目标网络侧不能创建或保留的 PDN连接不会触发该步骤；
S707:目标网络侧 SGW向 PGW发送修改承载请求（ Modify Bearer Request ) 消息；
其中， 该步骤为 PDN粒度的；
S708: 目标网络侧 SGW接收 PGW发送的修改承载响应 （ Modify Bearer Response ) 消息；
S709:目标网络侧 MME接收目标网络侧 SGW发送的创建会话响应（ Create Session Response ) 消息；
S710: 源网络侧 MME根据前述步骤 S705 中接收到的目标网络侧 MME 发送的 Context Ack消息， 获知目标网络侧不能创建或保留的承载的信息；
在此需要说明的是， 本步骤 S710可以发生在步骤 S706之前、 之后、 或者 与其同时发生， 并不存在先后顺序， 在接收到目标网络侧 MME发送的 Context Ack消息后， 源网络侧 MME即可执行本步骤；
S711 : 源网络侧 MME向源网络侧 SGW发送第一删除会话请求 ( Delete Session Request ) 消息；
对目标网络侧不能创建或保留的承载， 可触发源网络侧 MME向源网络侧 SGW发送携带操作标识 01的第一删除会话请求消息， 其中的具体的一种实施 方式中， 该 01标识设置为 1 , 所述 01标识用以指示源网络侧 SGW向 PGW发 送第二删除会话请求消息；
其中， 该步骤为 PDN粒度的， 若有多条 PDN连接在目标网络侧不能创建 或者保留， 则相应地触发多条第一删除会话请求消息， 每条第一删除会话请求 消息对应相关的 PDN连接， 每条第一删除会话请求消息均携带了缺省承载标 识；
S712: 源网络侧 SGW根据接收到的携带操作标识的第一删除会话请求消 息向 PGW发送第二删除会话请求（ Delete Session Request ) 消息；
其中， 所述第二删除会话请求消息携带目标网络侧不能创建或保留的承载 的信息；
S713: PGW接收到源网络侧 SGW发送的第二删除会话请求消息后， 根据 所述第二删除会话请求消息中携带的目标网络侧不能创建或保留的承载的信 息，删除所述目标网络侧不能创建或保留的承载的信息，之后，向源网络侧 SGW 发送第二删除会话响应 （ Delete Session Response ) 消息；
S714:源网络侧 MME接收源网络侧 SGW发送的第一删除会话响应（ Delete Session Response ) 消息；
S715: 源网络侧 MME向源网络侧 SGW发送第三删除会话请求（Delete Session Request ) 消息；
删除完所述目标网络侧不能创建或者保留的承载的信息后， 源网络侧 MME将发起对源网络侧 SGW中 UE的剩余承载上下文的删除流程；
其中， 该步骤为 UE粒度的， 此时所述第三删除会话请求消息中携带范围 标识（ Scope Indication, 筒称 SI标识）， 且该 SI标识设置为 1 , 指示源网络侧 SGW释放 UE的所有 PDN连接上下文， 且此时 01标识设置为 0, 使得源网络 侧 SGW不用向 PGW发送删除会话请求消息；
S716:源网络侧 MME接收源网络侧 SGW发送的第三删除会话响应（ Delete Session Response ) 消息。
在本实施例中， 除通过通知消息获知目标网络侧不能创建或保留的承载的 信息外， 源网络侧 MME还可以通过接收目标网络侧 MME发送的目标网络侧 创建或保留承载的依据信息， 确定目标网络侧不能创建或保留的承载的信息。 具体地， EPS承载状态信元、 目标网络侧的本地策略以及目标网络侧是否支持 创建 LIPA PDN连接的信息可通过上下文应答消息转发给源网络侧 MME, 源 网络侧 MME接收到携带目标网络侧创建或保留承载的依据信息的上下文应答 消息后， 确定目标网络侧不能创建或保留的承载的信息。
本发明实施例提供的方法实施例五， 在发生跟踪区位置更新流程时， 通过 源网络侧 MME指示源网络侧服务网关向 PGW发送第二删除会话请求消息， 可触发 PGW删除目标网络侧不能创建或保留的承载的信息， 使得 PGW中不 再保留冗余的承载信息，节省了网络侧承载上下文资源，另外， 源网络侧 MME 可通过通知消息或者目标网络侧创建或保留承载的依据信息， 获知目标网络侧 不能创建或保留的承载的信息， 使得源网络侧 MME获知目标网络侧不能创建 或保留的承载的信息的方式更加灵活，其次，对删除会话请求操作进行了分类， 源网络侧以及分组数据网关先删除目标网络侧不能创建或保留的承载信息， 之 后才在源网络侧删除用户设备剩余的目标网络侧能够创建或保留的承载信息， 增强了源网络侧删除其所创建的 UE 的承载上下文信息的可操作性以及灵活 性。 如图 8所示， 为本发明实施例提供的方法实施例六的实现流程图， 该实施 例针对发生 TAU流程时 MME未发生变化， SGW发生变化的应用场景， 即目 标网络侧 MME和源网络侧 MME是同一 MME， 目标网络侧 SGW和源网络侧 SGW不是同一 SGW的应用场景， 该实施例包括：
S801 : UE向 MME发送携带 EPS承载状态信元的 TAU Request消息； S802: MME确定目标网络侧不能创建或保留的承载的信息；
其中， 所述 MME根据目标网络侧创建或保留承载的依据信息确定目标网 络侧不能创建或保留的承载的信息， 目标网络侧不能创建或保留承载的情形可 分为以下几种方式：
( 1 )MME根据其从 UE获知的 EPS 承载状态信元和自身保存的 UE的承 载上下文信息不一致， 确定目标网络侧不能创建或保留的承载的信息， 其中， 不一致的情形为： 从 UE获得的 EPS承载状态信元指示激活的承载和自身保存 的承载不——对应； 例如， EPS承载状态信元指示缺省承载 5存在， 自身保存 的 UE的承载上下文中包含缺省承载 5和缺省承载 6的上下文， 此时， MME 经判断后， 即可确定目标网络侧不能创建或保留缺省承载 6;
( 2 ) 当在源网络侧创建 LIPA PDN连接的 UE发生移动时， MME判断所 述创建的 LIPA PDN连接在目标网络侧不能保留； 例如， MME自身保存的 UE 的承载上下文信息中包含了缺省承载 5和缺省承载 6的上下文， 其中， 缺省承 载 6为 LIPA PDN连接，缺省承载 5为常规 PDN连接， 源网络侧 HeNB和目标 网络侧 HeNB不在同一个本地家庭基站网络中， 此时， MME经判断后， 即可 确定目标网络侧不能创建或保留缺省承载 6;
在本实施例中， MME还可以根据本地策略确定目标网络侧不能创建或保 留的承载的信息， 其中所述本地策略可以包含接入 PDN连接数量和 /或承载上 下文数量控制策略；
S803： MME向目标网络侧 SGW发送 Create Session Request消息； 所述 Create Session Request消息携带目标网络侧能够创建或保留的承载的 缺省承载标识， 此外， 该步骤 S803将触发执行步骤 S804;
其中， 该步骤为 PDN粒度的， 若多个 PDN连接（承载）可在目标网络侧 创建或保留，则相应地触发多条 Create Session Request消息，每条 Create Session Request消息对应相关的 PDN连接， 对于目标网络侧不能创建或保留的 PDN 连接不会触发该步骤；
S804: 目标网络侧 SGW向 PGW发送 Modify Bearer Request消息； 其中， 该步骤为 PDN粒度的；
S805: 目标网络侧 SGW接收 PGW发送的 Modify Bearer Response消息； S806: MME接收目标网络侧 SGW发送的 Create Session Response消息； S807： MME向源网络侧 SGW发送第一删除会话请求消息；
对目标网络侧不能创建或保留的承载， 可触发 MME向源网络侧 SGW发 送携带操作标识 01的第一删除会话请求消息， 其中的具体的一种实施方式中， 该 01标识设置为 1 ,所述 01标识用以指示源网络侧 SGW向 PGW发送第二删 除会话请求消息；
其中， 该步骤为 PDN粒度的， 若有多条 PDN连接在目标网络侧不能创建 或者保留， 则相应地触发多条第一删除会话请求消息， 每条第一删除会话请求 消息对应相关的 PDN连接， 每条第一删除会话请求消息均携带了缺省承载标 识；
S808: 源网络侧 SGW根据接收到的携带操作标识的第一删除会话请求消 息向 PGW发送第二删除会话请求消息；
其中， 所述第二删除会话请求消息携带目标网络侧不能创建或保留的承载 的信息；
S809: PGW接收到源网络侧 SGW发送的第二删除会话请求消息后， 根据 所述第二删除会话请求消息中携带的目标网络侧不能创建或保留的承载的信 息，删除所述目标网络侧不能创建或保留的承载的信息，之后，向源网络侧 SGW 发送第二删除会话响应消息；
S810: MME接收源网络侧 SGW发送的第一删除会话响应消息； S811 : MME向源网络侧 SGW发送第三删除会话请求消息；
删除完所述目标网络侧不能创建或者保留的承载的信息后， MME将发起 对源网络侧 SGW中 UE的剩余承载上下文的删除流程；
其中， 该步骤为 UE粒度的， 此时所述第三删除会话请求消息中携带 SI 标识， 且该 SI标识设置为 1 , 指示源网络侧 SGW释放 UE的所有 PDN连接上 下文， 且此时 01标识设置为 0, 使得源网络侧 SGW不用向 PGW发送删除会 话请求消息；
S812: MME接收源网络侧 SGW发送的第三删除会话响应消息。
本发明实施例提供的方法实施例六， 在发生跟踪区位置更新流程时， 通过 指示源网络侧服务网关向 PGW发送第二删除会话请求消息， 可触发 PGW删 除目标网络侧不能创建或保留的承载的信息， 使得 PGW中不再保留冗余的承 载信息， 节省了网络侧承载上下文资源， 另外， 源网络侧 MME和目标网络侧 MME为同一 MME, 减少了网元之间的通讯开销， 其次， 对删除会话请求操作 进行了分类， 源网络侧以及分组数据网关先删除目标网络侧不能创建或保留的 承载信息， 之后才在源网络侧删除用户设备剩余的目标网络侧能够创建或保留 的承载信息， 增强了源网络侧删除其所创建的 UE的承载上下文信息的可操作 性以及灵活性。 如图 9所示， 为本发明实施例提供的方法实施例七的实现流程图， 该实施 例针对发生 TAU流程时 MME发生变化， SGW未发生变化的应用场景， 即目 标网络侧 MME和源网络侧 MME不是同一 MME， 目标网络侧 SGW和源网络 侧 SGW是同一 SGW的应用场景， 该实施例包括：
S901 : UE向目标网络侧 MME发送携带 EPS承载状态信元的 TAU Request 消息；
S902: 目标网络侧 MME向源网络侧 MME发送 Context Request消息； S903: 源网络侧 MME在收到目标网络侧 MME发送的 Context Request消 息后， 向目标网络侧 MME发送 Context Response消息；
其中， 所述 Context Response消息包含 UE的承载上下文信息， 所述 UE 的 载上下文信息通过 EPS PDN Connections信元描述；
S904: 目标网络侧 MME确定目标网络侧不能创建或保留的承载的信息； 其中， 所述目标网络侧 MME根据目标网络侧创建或保留承载的依据信息 确定目标网络侧不能创建或保留的承载的信息， 目标网络侧不能创建或保留承 载的情形可分为以下几种方式：
( 1 )所述目标网络侧 MME根据其从 UE获知的 EPS 承载状态信元和从 源网络侧 MME获知的 UE的承载上下文信息不一致， 确定目标网络侧不能创 建或保留的承载的信息， 其中， 不一致的情形为： 从 UE获得的 EPS承载状态 信元指示激活的承载和源网络侧 MME传递过来的承载不——对应；例如， EPS 承载状态信元指示缺省承载 5存在， 源网络侧 MME传递过来的承载上下文中 包含缺省承载 5和缺省承载 6的上下文， 此时， 目标网络侧 MME经判断后， 即可确定目标网络侧不能创建或保留缺省承载 6;
( 2 )所述目标网络侧 MME根据本地策略确定目标网络侧不能创建或保留 的承载的信息， 其中所述本地策略可以包含接入 PDN连接数量和 /或承载上下 文数量控制策略， 此时目标网络侧 MME可能由于上述控制策略， 不能成功创 建 UE的所有承载， 导致部分承载不能在目标网络侧创建或保留； 例如， 源网 络侧 MME传递的承载上下文包含了缺省承载 5和缺省承载 6的上下文， 但目 标网络侧 MME由于其上已经创建的承载上下文数目已达许可创建承载上下文 数目的上限， 只能创建缺省承载 5 , 此时， 目标网络侧 MME经判断后， 即可 确定目标网络侧不能创建或保留缺省承载 6;
( 3 ) 当在源网络侧创建 LIPA PDN连接的 UE发生移动时， 目标网络侧 MME判断所述创建的 LIPA PDN连接在目标网络侧不能保留； 例如， 源网络 侧 MME传递的承载上下文信息中包含了缺省承载 5和缺省承载 6的上下文， 其中， 缺省承载 6为 LIPA PDN连接， 缺省承载 5为常规 PDN连接， 源网络侧 HeNB目标网络侧 HeNB不在同一个本地家庭基站网络中， 此时， 目标网络侧 MME经判断后， 即可确定目标网络侧不能创建或保留缺省承载 6;
S905: 目标网络侧 MME向源网络侧 MME发送通知消息， 本实施例中， 所述通知消息可以采用 Context Ack消息；
其中， 所述 Context Ack消息可以显式（直接）指示目标网络侧不能创建 或保留的承载的信息， 也可以隐式（间接）指示目标网络侧不能创建或保留的 承载的信息， 其具体实现方式可以通过以下方式之一或其组合实现：
( 1 ) Context Ack消息携带缺省承载标识或接入点名信息， 其中， 该缺省 承载标识或接入点名可以直接对应于目标网络侧不能创建或保留的承载的标 识，例如所述缺省承载标识或接入点名可以包含在待删除上下文 "Context to be removed" 信元中， 直接指示目标网络侧不能创建或保留的承载的标识； 或者， 该缺省承载标识或接入点名对应于目标网络侧可以创建或保留的承载的标识， 隐式指示目标网络侧不能创建或保留的承载的信息， 源网络侧 MME通过本地 存储的用户设备的承载上下文信息和所述获知的目标网络侧可以创建或保留 的承载的信息， 获知剩余的目标网络侧不能创建或保留的承载的信息； 或者，
( 2 ) Context Ack消息携带 EPS bearer status信元， 该 EPS bearer status信 元中对应的比特位中的不同取值（例如 1或 0 )分别指明了目标网络侧能创建 或保留的承载和目标网络侧不能创建或保留的承载， 源网络侧 MME根据所述 EPS bearer status信元获知目标网络侧不能创建或保留的承载的信息； 或者，
( 3 ) Context Ack消息携 LPCNSI标识， 以指示所述 LIPA PDN连接在目 标网络侧不能创建或保留；
此外， Context Ack消息将不携带 SGWCI标识， 以指示该 TAU流程中的 SGW未发生改变；
S906: 目标网络侧 MME向 SGW发送 Modify Bearer Request消息； 所述 Modify Bearer Request消息携带目标网络侧能够创建或保留的承载的 缺省承载标识， 此外， 该步骤 S906将触发执行步骤 S907;
其中， 该步骤为 PDN粒度的， 若多个 PDN连接（承载）可在目标网络侧 创建或保留，则相应地触发多条 Modify Bearer Request消息，每条 Modify Bearer Request消息对应相关的 PDN连接， 对于目标网络侧不能创建或保留的 PDN 连接不会触发该步骤；
S907: SGW向 PGW发送 Modify Bearer Request消息；
其中， 所述 SGW向 PGW发送的修改承载请求消息通过目标网络侧 MME 向所述 SGW发送的修改承载请求消息实现；
S908: SGW接收 PGW发送的 Modify Bearer Response消息；
S909: 目标网络侧 MME接收 SGW发送的 Modify Bearer Response消息；
S910: 源网络侧 MME根据前述步骤 S905 中接收到的目标网络侧 MME 发送的 Context Ack消息， 获知目标网络侧不能创建或保留的承载的信息； 在此需要说明的是， 本步骤 S910可以发生在步骤 S906之前、 之后、 或者 与其同时发生， 并不存在先后顺序， 在接收到目标网络侧 MME发送的 Context Ack消息后， 源网络侧 MME即可执行本步骤；
S911 : 源网络侧 MME向 SGW发送第一删除会话请求消息；
对目标网络侧不能创建或保留的承载， 可触发源网络侧 MME向 SGW发 送携带操作标识 01的第一删除会话请求消息， 其中的具体的一种实施方式中， 该 01标识设置为 1 ,所述 01标识用以指示 SGW向 PGW发送第二删除会话请 求消息；
其中， 该步骤为 PDN粒度的， 若有多条 PDN连接在目标网络侧不能创建 或者保留， 则相应地触发多条第一删除会话请求消息， 每条第一删除会话请求 消息对应相关的 PDN连接， 每条第一删除会话请求消息均携带了缺省承载标 S912: SGW根据接收到的携带操作标识的第一删除会话请求消息向 PGW 发送第二删除会话请求消息；
其中， 所述第二删除会话请求消息携带目标网络侧不能创建或保留的承载 的信息；
S913: PGW接收到 SGW发送的第二删除会话请求消息后，根据所述第二 删除会话请求消息中携带的目标网络侧不能创建或保留的承载的信息， 删除所 述目标网络侧不能创建或保留的承载的信息， 之后， 向 SGW发送第二删除会 话响应消息；
S914: 源网络侧 MME接收 SGW发送的第一删除会话响应消息。
在本实施例中， 除通过通知消息获知目标网络侧不能创建或保留的承载的 信息外， 源网络侧 MME还可以通过接收目标网络侧 MME发送的目标网络侧 创建或保留承载的依据信息， 确定目标网络侧不能创建或保留的承载的信息。 具体地， EPS承载状态信元、 目标网络侧的本地策略以及目标网络侧是否支持 创建 LIPA PDN连接的信息可通过上下文应答消息转发给源网络侧 MME, 源 网络侧 MME接收到携带目标网络侧创建或保留承载的依据信息的上下文应答 消息后， 确定目标网络侧不能创建或保留的承载的信息。
本发明实施例提供的方法实施例七， 在发生跟踪区位置更新流程时， 通过 源网络侧 MME指示服务网关向 PGW发送第二删除会话请求消息， 可触发 PGW删除目标网络侧不能创建或保留的承载的信息，使得 PGW中不再保留冗 余的承载信息， 节省了网络侧承载上下文资源， 另外， 源网络侧 MME可通过 通知消息或者目标网络侧创建或保留承载的依据信息， 获知目标网络侧不能创 建或保留的承载的信息， 使得源网络侧 MME获知目标网络侧不能创建或保留 的承载的信息的方式更加灵活， 其次， 对删除会话请求操作进行了分类， 源网 络侧以及分组数据网关先删除目标网络侧不能创建或保留的承载信息， 之后才 在源网络侧删除用户设备剩余的目标网络侧能够创建或保留的承载信息， 增强 了源网络侧删除其所创建的 UE的承载上下文信息的可操作性以及灵活性。 如图 10所示， 为本发明实施例提供的方法实施例八的实现流程图， 该实 施例针对发生 Handover流程时 MME和 SGW同时发生变化的应用场景， 该实 施例包括：
S 1001： 源网络侧 HeNB触发 Handover流程；
S1002 : 源网络侧 HeNB 向源网络侧 MME 发送切换要求 （Handover Required ) 消息；
SI 003: 源网络侧 MME接收到源网络侧 HeNB发送的 Handover Required 消息后，向目标网络侧 MME发送转发重定向请求（ Forward Relocation Request ) 消息；
其中， 所述 Forward Relocation Request消息包含 UE的承载上下文信息， 所述 UE的 载上下文信息通过 EPS PDN Connections信元描述；
S1004: 目标网络侧 MME确定目标网络侧不能创建或保留的承载的信息； 其中， 所述目标网络侧 MME根据目标网络侧创建或保留承载的依据信息 确定目标网络侧不能创建或保留的承载的信息， 目标网络侧不能创建或保留承 载的情形可分为以下几种方式：
( 1 )所述目标网络侧 MME根据本地策略确定目标网络侧不能创建或保留 的承载的信息， 其中所述本地策略可以包含接入 PDN连接数量和 /或承载上下 文数量控制策略， 此时目标网络侧 MME可能由于上述控制策略， 不能成功创 建 UE的所有承载， 导致部分承载在目标网络侧不能创建或保留； 例如， 源网 络侧 MME传递的承载上下文包含了缺省承载 5和缺省承载 6的上下文， 但目 标网络侧 MME由于其上已经创建的承载上下文数目已达许可创建承载上下文 数目的上限， 只能创建缺省承载 5 , 此时， 目标网络侧 MME经判断后， 即可 确定目标网络侧不能创建或保留缺省承载 6;
( 2 ) 当在源网络侧创建 LIPA PDN连接的 UE发生移动时， 目标网络侧 MME判断所述创建的 LIPA PDN连接在目标网络侧不能保留； 例如， 源网络 侧 MME传递的承载上下文信息中包含了缺省承载 5和缺省承载 6的上下文， 其中， 缺省承载 6为 LIPA PDN连接， 缺省承载 5为常规 PDN连接， 源网络侧 HeNB和目标网络侧 HeNB不在同一个本地家庭基站网络中， 此时， 目标网络 侧 MME经判断后， 即可确定目标网络侧不能创建或保留缺省承载 6;
S 1005： 目标网络侧 MME向源网络侧 MME发送通知信息， 本实施例中， 所述通知信息可以采用转发重定向响应 （ Forward Relocation Response ) 消息； 其中， 所述 Forward Relocation Response消息可以显式（直接 )指示目标 网络侧不能创建或保留的承载的信息， 也可以隐式（间接）指示目标网络侧不 能创建或保留的承载的信息， 其具体实现方式可以通过以下方式之一或其组合 实现：
( 1 ) Forward Relocation Response消息携带缺省承载标识或接入点名信息， 其中， 该缺省承载标识或接入点名可以直接对应于目标网络侧不能创建或保留 的承载的标识， 例如所述缺省承载标识或接入点名可以包含在待删除上下文 "Context to be removed"信元中， 直接指示目标网络侧不能创建或保留的承载 的标识； 或者， 该缺省承载标识或接入点名对应于目标网络侧可以创建或保留 的承载的标识， 隐式指示目标网络侧不能创建或保留的承载的信息， 源网络侧 MME通过本地存储的用户设备的承载上下文信息和所述获知的目标网络侧可 以创建或保留的承载的信息， 获知剩余的目标网络侧不能创建或保留的承载的 信息； 或者，
( 2 ) Forward Relocation Response消息携带 EPS bearer status信元, 该 EPS bearer status信元中对应的比特位中的不同取值 (例如 1或 0 )分别指明了目标 网络侧能创建或保留的承载以及目标网络侧不能创建或保留的承载， 源网络侧 MME根据所述 EPS承载状态信元获知目标网络侧不能创建或保留的承载的信 息； 或者， ( 3 ) Forward Relocation Response消息携带 LPCNSI标识， 以指示目标网 络侧不能创建或保留的 LIPA PDN连接；
此外， Forward Relocation Response消息还携带了 SGWCI标识， 用以指示 该 Handover流程已选择了新的 SGW;
S 1006： 目标网络侧 MME向目标网络侧 SGW发送创建会话请求（ Create Session Request ) 消息；
所述 Create Session Request消息携带目标网络侧能够创建或保留的承载的 缺省承载标识， 与方法实施例五和方法实施例六不同的是， 该步骤 S1006将不 触发目标网络侧 SGW向 PGW发送 Modify Bearer Request消息，在该流程的后 消息， 以触发目标网络侧 SGW向 PGW发送 Modify Bearer Request消息；
其中， 该步骤为 PDN粒度的， 若多个 PDN连接（承载）可在目标网络侧 创建或保留，则相应地触发多条 Create Session Request消息，每条 Create Session Request消息对应相关的 PDN连接， 对于目标网络侧不能创建或保留的 PDN 连接不会触发该步骤；
S1007: 目标网络侧 MME接收目标网络侧 SGW 发送的创建会话响应 ( Create Session Response ) 消息；
S1008: 源网络侧 MME根据前述步骤 S1005中接收到的目标网络侧 MME 发送的转发重定向响应消息， 获知目标网络侧不能创建或保留的承载的信息； 在此需要说明的是， 本步骤 S1008可以发生在步骤 S1006之前、 之后、 或 者与其同时发生,并不存在先后顺序，在接收到目标网络侧 MME发送的转发重 定向响应消息后， 源网络侧 MME即可执行本步骤；
S1009: 源网络侧 MME向源网络侧 SGW发送第一删除会话请求 ( Delete Session Request ) 消息；
对目标网络侧不能创建或保留的承载， 可触发源网络侧 MME向源网络侧 SGW发送携带操作标识 01的第一删除会话请求消息， 其中的具体的一种实施 方式中， 该 01标识设置为 1 , 所述 01标识用以指示源网络侧 SGW向 PGW发 送第二删除会话请求消息；
其中， 该步骤为 PDN粒度的， 若有多条 PDN连接在目标网络侧不能创建 或者保留， 则相应地触发多条第一删除会话请求消息， 每条第一删除会话请求 消息对应相关的 PDN连接， 每条第一删除会话请求消息均携带了缺省承载标 识；
S1010:源网络侧 SGW根据接收到的携带操作标识的第一删除会话请求消 息向 PGW发送第二删除会话请求（ Delete Session Request ) 消息；
其中， 所述第二删除会话请求消息携带目标网络侧不能创建或保留的承载 的信息；
S1011: PGW接收到源网络侧 SGW发送的第二删除会话请求消息后， 根 据所述第二删除会话请求消息中携带的目标网络侧不能创建或保留的承载的 信息， 删除所述目标网络侧不能创建或保留的承载的信息， 之后， 向源网络侧 SGW发送第二删除会话响应 （ Delete Session Response ) 消息；
S1012: 源网络侧 MME接收源网络侧 SGW 发送的第一删除会话响应 ( Delete Session Response ) 消息；
S1013: 源网络侧 MME向源网络侧 SGW发送第三删除会话请求 ( Delete Session Request ) 消息；
删除完所述目标网络侧不能创建或者保留的承载的信息后， 源网络侧 MME将发起对源网络侧 SGW中 UE的剩余承载上下文的删除流程；
其中， 该步骤为 UE粒度的， 此时所述第三删除会话请求消息中携带 SI 标识， 且该 SI标识设置为 1 , 指示源网络侧 SGW释放 UE的所有 PDN连接上 下文， 且此时 01标识设置为 0, 使得源网络侧 SGW不用向 PGW发送删除会 话请求消息； S1014: 源网络侧 MME接收源网络侧 SGW 发送的第三删除会话响应 ( Delete Session Response ) 消息。
在本实施例中， 除通过通知消息获知目标网络侧不能创建或保留的承载的 信息外， 源网络侧 MME还可以通过接收目标网络侧 MME发送的目标网络侧 创建或保留承载的依据信息， 确定目标网络侧不能创建或保留的承载的信息。 的信息可通过转发重定向响应消息转发给源网络侧 MME, 源网络侧 MME接 收到携带目标网络侧创建或保留承载的依据信息的转发重定向响应消息后， 确 定目标网络侧不能创建或保留的承载的信息。
本发明实施例提供的方法实施例八， 在发生切换流程时， 通过源网络侧 MME指示源网络侧服务网关向 PGW发送第二删除会话请求消息，可触发 PGW 删除目标网络侧不能创建或保留的承载的信息， 使得 PGW中不再保留冗余的 承载信息， 节省了网络侧承载上下文资源， 另外， 源网络侧 MME可通过通知 消息或者目标网络侧创建或保留承载的依据信息， 获知目标网络侧不能创建或 保留的承载的信息， 使得源网络侧 MME获知目标网络侧不能创建或保留的承 载的信息的方式更加灵活， 其次， 对删除会话请求操作进行了分类， 源网络侧 以及分组数据网关先删除目标网络侧不能创建或保留的承载信息， 之后才在源 网络侧删除用户设备剩余的目标网络侧能够创建或保留的承载信息， 增强了源 网络侧删除其所创建的 UE的承载上下文信息的可操作性以及灵活性。 如图 11 所示， 为本发明实施例提供的方法实施例九的实现流程图， 该实 施例针对发生 Handover流程时 MME未发生变化， SGW发生变化的应用场景， 该实施例包括：
S 1101： 源网络侧 HeNB触发 Handover流程；
S1102: 源网络侧 HeNB向 MME发送 Handover Required消息；
S 1103： MME确定目标网络侧不能创建或保留的承载的信息； 其中， 所述 MME根据目标网络侧创建或保留承载的依据信息确定目标网 络侧不能创建或保留的承载的信息， 目标网络侧不能创建或保留承载的情形包 括：
当在源网络侧创建 LIPA PDN连接的 UE发生移动时， MME判断所述创建 的 LIPA PDN连接在目标网络侧不能保留； 例如， MME自身保存的 UE的承载 上下文信息中包含了缺省承载 5和缺省承载 6的上下文， 其中， 缺省承载 6为 LIPA PDN连接， 缺省承载 5为常规 PDN连接， 源网络侧 HeNB和目标网络侧 HeNB 不在同一个本地家庭基站网络中， 此时， MME经判断后， 即可确定目 标网络侧不能创建或保留缺省承载 6;
在本实施例中， MME还可以根据本地策略确定目标网络侧不能创建或保 留的承载的信息， 其中所述本地策略可以包含接入 PDN连接数量和 /或承载上 下文数量控制策略；
S1104: MME向目标网络侧 SGW发送发送 Create Session Request消息； 所述 Create Session Request消息携带目标网络侧能够创建或保留的承载的 缺省承载标识， 并且该步骤 S1104 将不触发目标网络侧 SGW 向 PGW发送 Modify Bearer Request消息， 在该流程的后续操作中， MME会向目标网络侧 SGW发送 Modify Bearer Request消息， 以触发目标网络侧 SGW向 PGW发送 Modify Bearer Request消息；
其中， 若多个 PDN连接（承载）可在目标网络侧创建或保留， 则相应地 触发多条 Create Session Request消息 , 每条 Create Session Request消息对应相 关的 PDN连接，对于目标网络侧不能创建或保留的 PDN连接不会触发该步骤；
S 1106： MME向源网络侧 SGW发送第一删除会话请求消息；
对目标网络侧不能创建或保留的承载， 可触发 MME向源网络侧 SGW发 送携带操作标识 01的第一删除会话请求消息， 其中的具体的一种实施方式中， 该 01标识设置为 1 ;
其中， 该步骤为 PDN粒度的， 若有多条 PDN连接在目标网络侧不能创建 或者保留， 则相应地触发多条第一删除会话请求消息， 每条第一删除会话请求 消息对应相关的 PDN连接， 每条第一删除会话请求消息均携带了缺省承载标 识；
S1107:源网络侧 SGW根据接收到的携带操作标识的第一删除会话请求消 息向 PGW发送第二删除会话请求消息；
其中， 所述第二删除会话请求消息携带所述目标网络侧不能创建或保留的 承载的信息；
S1108: PGW接收到源网络侧 SGW发送的第二删除会话请求消息后， 根 据所述第二删除会话请求消息中携带的目标网络侧不能创建或保留的承载的 信息， 删除所述目标网络侧不能创建或保留的承载的信息， 之后， 向源网络侧 SGW发送第二删除会话响应消息；
S1109: MME接收源网络侧 SGW发送的第一删除会话响应消息；
S 1110： MME向源网络侧 SGW发送第三删除会话请求消息；
删除完所述目标网络侧不能创建或者保留的承载的信息后， MME将发起 对源网络侧 SGW中 UE的剩余承载上下文的删除流程；
其中， 该步骤为 UE粒度的， 此时所述第三删除会话请求消息中携带 SI 标识， 且该 SI标识设置为 1 , 指示源网络侧 SGW释放 UE的所有 PDN连接上 下文， 且此时 01标识设置为 0, 使得源网络侧 SGW不用向 PGW发送删除会 话请求消息；
Sllll: MME接收源网络侧 SGW发送的第三删除会话响应消息。
本发明实施例提供的方法实施例九， 在发生切换流程时， 通过指示源网络 侧服务网关向 PGW发送第二删除会话请求消息， 可触发触发 PGW删除目标 网络侧不能创建或保留的承载的信息，使得 PGW中不再保留冗余的承载信息， 节省了网络侧 载上下文资源， 另夕卜， 源网络侧 MME和目标网络侧 MME为 同一 MME, 减少了网元之间的通讯开销， 其次， 对删除会话请求操作进行了 分类， 源网络侧以及分组数据网关先删除目标网络侧不能创建或保留的承载信 息， 之后才在源网络侧删除用户设备剩余的目标网络侧能够创建或保留的承载 信息， 增强了源网络侧删除其所创建的 UE的承载上下文信息的可操作性以及 灵活性。 如图 12所示， 为本发明实施例提供的方法实施例十的实现流程图， 该实 施例针对发生 Handover流程时 MME发生变化， SGW未发生变化的应用场景， 该实施例包括：
S1201 : 源网络侧 HeNB触发 Handover流程；
S1202: 源网络侧 HeNB向源网络侧 MME发送 Handover Required消息； S1203: 源网络侧 MME接收到源网络侧 HeNB发送的 Handover Required 消息后，向目标网络侧 MME发送 Forward Relocation Request消息，所述 Forward Relocation Request 消息携带用以描述 UE 的承载上下文信息的 EPS PDN Connections信元；
S 1204： 目标网络侧 MME确定目标网络侧不能创建或保留的承载的信息； 其中， 所述目标网络侧 MME根据目标网络侧创建或保留承载的依据信息 确定目标网络侧不能创建或保留的承载的信息， 目标网络侧不能创建或保留承 载的情形可分为以下几种方式：
( 1 )所述目标网络侧 MME根据本地策略确定目标网络侧不能创建或保留 的承载的信息， 其中所述本地策略可以包含接入 PDN连接数量和 /或承载上下 文数量控制策略， 此时目标网络侧 MME可能由于上述控制策略， 不能成功创 建 UE的所有承载， 导致部分承载不能在目标网络侧创建或保留； 例如， 源网 络侧 MME传递的承载上下文包含了缺省承载 5和缺省承载 6的上下文， 但目 标网络侧 MME由于其上已经创建的承载上下文数目已达许可创建承载上下文 数目的上限， 只能创建缺省承载 5 , 此时， 目标网络侧 MME经判断后， 即可 确定目标网络侧不能创建或保留缺省承载 6;
( 2 ) 当在源网络侧创建 LIPA PDN连接的 UE发生移动时， 目标网络侧 MME判断所述创建的 LIPA PDN连接在目标网络侧不能保留； 例如， 源网络 侧 MME传递的承载上下文信息中包含了缺省承载 5和缺省承载 6的上下文， 其中， 缺省承载 6为 LIPA PDN连接， 缺省承载 5为常规 PDN连接， 源网络侧 HeNB和目标网络侧 HeNB不在同一个本地家庭基站网络中， 此时， 目标网络 侧 MME经判断后， 即可确定目标网络侧不能创建或保留缺省承载 6;
S 1205： 目标网络侧 MME向源网络侧 MME发送通知消息， 本实施例中， 所述通知消息可以采用 Forward Relocation Response消息；
其中， 所述 Forward Relocation Response消息可以显式（直接 )指示目标 网络侧不能创建或保留的承载的信息， 也可以隐式（间接）指示目标网络侧不 能创建或保留的承载的信息， 其具体实现方式可以通过以下方式之一或其组合 实现：
( 1 ) Forward Relocation Response消息携带缺省承载标识或接入点名信息， 其中， 该缺省承载标识或接入点名可以直接对应于目标网络侧不能创建或保留 的承载的标识， 例如所述缺省承载标识或接入点名可以包含在待删除上下文 "Context to be removed"信元中， 直接指示目标网络侧不能创建或保留的承载 的标识； 或者， 该缺省承载标识或接入点名对应于目标网络侧可以创建或保留 的承载的标识， 隐式指示目标网络侧不能创建或保留的承载的信息， 源网络侧 MME通过本地存储的用户设备的承载上下文信息和所述获知的目标网络侧可 以创建或保留的承载的信息， 获知剩余的目标网络侧不能创建或保留的承载的 信息； 或者，
( 2 ) Forward Relocation Response消息携带 EPS bearer status信元, 该 EPS bearer status信元中对应的比特位中的不同取值 (例如 1或 0 )分别指明了目标 网络侧能创建或保留的承载和目标网络侧不能创建或保留的承载， 源网络侧
MME根据所述 EPS bearer status信元获知目标网络侧不能创建或保留的承载的 信息； 或者，
( 3 ) Forward Relocation Response消息携带 LPCNSI标识， 以指示目标网 络侧不能创建或保留的 LIPA PDN连接；
在该流程的后续操作中， 目标网络侧 MME会向 SGW发送 Modify Bearer Request消息， 以指示 SGW向 PGW发送 Modify Bearer Request消息；
此外， Forward Relocation Response消息将不携带 SGWCI标识， 以指示该 Handover流程中的 SGW未发生改变；
S1206: 源网络侧 MME根据接收到的目标网络侧 MME发送的 Forward Relocation Response消息， 获知目标网络侧不能创建或保留的承载的信息；
S 1207： 源网络侧 MME向 SGW发送第一删除会话请求消息；
对目标网络侧不能创建或保留的承载， 可触发源网络侧 MME向 SGW发 送携带操作标识 01的第一删除会话请求消息， 其中的具体的一种实施方式中， 该 01标识设设置为 1 ,所述 01标识用以指示 SGW向 PGW发送第二删除会话 请求消息；
其中， 该步骤为 PDN粒度的， 若有多条 PDN连接在目标网络侧不能创建 或者保留， 则相应地触发多条第一删除会话请求消息， 每条第一删除会话请求 消息对应相关的 PDN连接， 每条第一删除会话请求消息均携带了缺省承载标 识；
S1208: SGW根据接收到的携带操作标识的第一删除会话请求消息向 PGW 发送第二删除会话请求消息；
其中， 所述第二删除会话请求消息携带所述目标网络侧不能创建或保留的 承载的信息；
S1209: PGW接收到 SGW发送的第二删除会话请求消息后， 根据所述第 二删除会话请求消息中携带的目标网络侧不能创建或保留的承载的信息， 删除 所述目标网络侧不能创建或保留的承载的信息， 之后， 向 SGW发送第二删除 会话响应消息；
S1210: 源网络侧 MME接收 SGW发送的第一删除会话响应消息。
在本实施例中， 除通过通知消息获知目标网络侧不能创建或保留的承载的 信息外， 源网络侧 MME还可以通过接收目标网络侧 MME发送的目标网络侧 创建或保留承载的依据信息， 确定目标网络侧不能创建或保留的承载的信息。 的信息可通过转发重定向响应消息转发给源网络侧 MME, 源网络侧 MME接 收到携带目标网络侧创建或保留承载的依据信息的转发重定向响应消息后， 确 定目标网络侧不能创建或保留的承载的信息。
本发明实施例提供的方法实施例十， 在发生切换流程时， 通过源网络侧 MME指示服务网关向 PGW发送第二删除会话请求消息， 可触发 PGW删除目 标网络侧不能创建或保留的承载的信息， 使得 PGW中不再保留冗余的承载信 息， 节省了网络侧承载上下文资源， 另外， 源网络侧 MME可通过通知消息或 者目标网络侧创建或保留承载的依据信息， 获知目标网络侧不能创建或保留的 承载的信息， 使得源网络侧 MME获知目标网络侧不能创建或保留的承载的信 息的方式更加灵活， 其次， 对删除会话请求操作进行了分类， 源网络侧以及分 组数据网关先删除目标网络侧不能创建或保留的承载信息， 之后才在源网络侧 删除用户设备剩余的目标网络侧能够创建或保留的承载信息， 增强了源网络侧 删除其所创建的 UE的承载上下文信息的操作性以及灵活性。 如图 13所示， 为本发明实施例提供的一种移动管理网元， 包括： 获知单元 1301 , 用于获知目标网络侧不能创建或保留的承载的信息； 发送单元 1302, 用于在所述获知单元 1301获知目标网络侧不能创建或保 的承载的信息后， 触发源网络侧服务网关向分组域数据网络网关发送第二删 除会话请求消息， 所述第二删除会话请求消息携带所述目标网络侧不能创建或 创建或保留的承载的信息。
进一步地， 上述获知单元 1301可以采用以下两种构成方式实现： 构成方式一： 所述获知单元 1301包括：
第一接收单元， 用于接收目标网络侧移动管理网元发送的通知消息， 所述 通知消息携带目标网络侧不能创建或保留的承载的标识或接入点名；
第一确定单元， 用于在所述第一接收单元接收到携带目标网络侧不能创建 或保留的承载的标识或接入点名的通知消息后， 根据所述通知消息直接获知所 述目标网络侧不能创建或保留的承载的信息； 或者
第二接收单元， 用于接收目标网络侧移动管理网元发送的通知消息， 所述 通知消息携带目标网络侧可以创建或保留的承载的标识或接入点名；
第二确定单元， 用于在所述第二接收单元接收到携带目标网络侧可以创建 或保留的承载的标识或接入点名的通知消息后， 根据本地存储的用户设备的承 载上下文信息以及所述目标网络侧可以创建或保留的承载的标识或接入点名， 确定目标网络侧不能创建或保留的承载的信息； 或者
第三接收单元， 用于接收目标网络侧移动管理网元发送的通知消息， 所述 通知消息携带 EPS承载状态信元， 所述 EPS承载状态信元分别指明了目标网 络侧可以创建或保留的承载以及目标网络侧不能创建或保留的承载；
第三确定单元，用于在所述第三接收单元接收到携带 EPS承载状态信元的 通知消息后，根据所述 EPS承载状态信元获知目标网络侧不能创建或保留的承 载的信息； 或者
第四接收单元， 用于接收目标网络侧移动管理网元发送的通知消息， 所述 通知消息携带 LIPA PDN连接不支持标识；
第四确定单元， 用于在所述第四接收单元接收到携带 LIPA PDN连接不支 持标识的通知消息后， 根据所述 LIPA PDN连接不支持标识获知目标网络侧不 能创建或保留的 LIPA PDN连接。
构成方式二： 所述获知单元 1301 具体用于根据目标网络侧创建或保留承 载的依据信息确定目标网络侧不能创建或保留的承载的信息， 所述目标网络侧 创建或保留承载的依据信息包括以下信息之一或其任意组合： 用户设备的承载 上下文信息、 EPS承载状态信元、 目标网络侧的本地策略以及目标网络侧是否 支持创建 LIPA PDN连接的信息；
其中， 所述获知单元 1301具体包括：
第五确定单元，用于根据所述的用户设备的承载上下文信息与 EPS承载状 态信元是否一致， 确定目标网络侧不能创建或保留的承载的信息； 或者 能创建或保留的承载的信息， 其中， 所述的目标网络侧的本地策略包含接入 PDN连接数量和 /或承载上下文数量控制策略； 或者
第七确定单元， 用于根据所述的目标网络侧是否支持创建 LIPA PDN连接 的信息， 确定目标网络侧不能创建或保留的 LIPA PDN连接。
所述发送单元 1302具体用于在所述获知单元 1301获知目标网络侧不能创 建或保留的承载的信息后， 向源网络侧服务网关发送携带操作标识的第一删除 会话请求消息， 所述第一删除会话请求消息携带所述目标网络侧不能创建或保 留的承载的信息， 所述操作标识触发源网络侧服务网关向分组域数据网络网关 发送第二删除会话请求消息。
所述发送单元 1302还用于在删除目标网络侧不能创建或保留的承载的信 息后， 向所述源网络侧服务网关发送第三删除会话请求消息， 所述第三删除会 话请求消息指示所述源网络侧服务网关删除用户设备剩余的目标网络侧可以 创建或保留的承载的信息。
本发明实施例提供的移动管理网元， 获知单元可以通过通知消息或目标网 络侧创建或保留承载的依据信息获知目标网络侧不能创建或保留的承载的信 息，使得获知目标网络侧不能创建或保留的承载的信息的方式更加灵活，此外， 利用发送单元对要发送的删除会话请求操作进行分类， 源网络侧以及分组数据 网关先删除目标网络侧不能创建或保留的承载信息， 之后才在源网络侧删除用 户设备剩余的目标网络侧能够创建或保留的承载信息， 增强了源网络侧删除其 所创建的 UE的承载上下文信息的可操作性以及灵活性。 如图 14所示， 为本发明实施例提供的另一种移动管理网元， 包括： 确定单元 1401 , 用于确定目标网络侧不能创建或保留的承载的信息； 发送单元 1402, 用于确定单元 1401确定目标网络侧不能创建或保留的承 载的信息后， 向源网络侧移动管理网元发送通知消息， 指示源网络侧移动管理 网元获知目标网络侧不能创建或保留的承载的信息。
除通过通知消息使源网络侧移动管理网元获知目标网络侧不能创建或保 留的承载的信息外， 本发明实施例还提供一种移动管理网元， 使得目标网络侧
据信息确定目标网络侧不能创建或保留的承载的信息， 具体地， 该移动管理网 元包括：
确定单元 140Γ , 用于确定目标网络侧创建或保留承载的依据信息； 发送单元 1402，，用于确定单元 1401，确定目标网络侧创建或保留承载的依 据信息后， 向源网络侧移动管理网元发送所述目标网络侧创建或保留承载的依 据信息， 指示源网络侧移动管理网元确定目标网络侧不能创建或保留的承载的 信息。
其中， 所述目标网络侧创建或保留承载的依据信息包括以下信息之一或其 任意组合： UE的承载上下文信息、 EPS承载状态信元、 目标网络侧的本地策 略以及目标网络侧是否支持创建 LIPA PDN连接的信息。 以上两个实施例提供的移动管理网元， 通过发送单元向源网络侧移动管理 网元发送通知消息或者目标网络侧创建或保留承载的依据信息， 使得源网络侧 移动管理网元获知目标网络侧不能创建或保留的承载的信息。 如图 15所示， 为本发明实施例提供的一种服务网关 SGW, 包括： 接收单元 1501 , 用于接收源网络侧移动管理网元发送的触发指示， 所述触 发指示是所述源网络侧移动管理网元获知目标网络侧不能创建或保留的承载 的信息之后发送的；
发送单元 1502, 用于根据所述接收单元接收到的触发指示， 向分组域数据 网络网关发送第二删除会话请求消息， 所述第二删除会话请求消息携带所述目 标网络侧不能创建或保留的承载的信息， 以便于所述分组域数据网络网关删除 所述目标网络侧不能创建或保留的承载的信息。
其中， 所述接收单元 1501 具体用于接收源网络侧移动管理网元发送的携 带操作标识的第一删除会话请求消息； 所述发送单元 1502具体用于根据所述 第一删除会话请求消息中的操作标识， 向所述分组域数据网络网关发送第二删 除会话请求消息。
本发明实施例提供的服务网关， 根据接收单元接收到的操作标识， 触发发 送单元向 PGW发送第二删除会话请求消息， 指示 PGW删除目标网络侧不能 创建或保留的承载的信息， 使得 PGW中不再保留冗余的承载信息， 节省了网 络侧承载上下文资源。 如图 16所示， 为本发明实施例提供的一种承载的处理系统， 该系统包括： 源网络侧移动管理网元 1601 , 源网络侧服务网关 1602, 分组域数据网络网关 1603 , 其中，
所述源网络侧移动管理网元 1601 ,用于在获知目标网络侧不能创建或保留 的承载的信息后， 触发源网络侧服务网关 1602向分组域数据网络网关 1603发 送第二删除会话请求消息；
所述源网络侧服务网关 1602, 用于接收源网络侧移动管理网元 1601发送 的触发指示， 并根据所述触发指示， 向分组域数据网络网关 1603发送第二删 除会话请求消息， 所述第二删除会话请求消息携带所述目标网络侧不能创建或 保留的承载的信息；
分组域数据网络网关 1603 , 用于在接收到源网络侧服务网关 1602发送的 第二删除会话请求消息后， 根据所述第二删除会话请求消息中携带的目标网络 侧不能创建或保留的承载的信息， 删除所述目标网络侧不能创建或保留的承载 的信息。
其中， 所述源网络侧移动管理网元 1601包括：
获知单元， 用于获知目标网络侧不能创建或保留的承载的信息； 发送单元， 用于在所述获知单元获知目标网络侧不能创建或保留的承载的 信息后， 触发源网络侧服务网关向分组域数据网络网关发送第二删除会话请求 消息；
所述源网络侧服务网关 1602包括：
接收单元， 用于接收源网络侧移动管理网元发送的触发指示， 所述触发指 示是所述源网络侧移动管理网元获知目标网络侧不能创建或保留的承载的信 息之后发送的；
发送单元， 用于根据所述接收单元接收到的触发指示， 向分组域数据网络 网关发送第二删除会话请求消息。
另外， 该系统还包括目标网络侧移动管理网元， 则所述目标网络侧移动管 理网元用于向所述源网络侧移动管理网元 1601 发送通知消息， 使得所述源网 络侧移动管理网元 1601 根据所述通知消息获知目标网络侧不能创建或保留的 承载的信息； 或者，
移动管理网元 1601 发 送目标网络侧创建或保留承载的依据信息， 使得所述源网络侧移动管理网元
1601 根据所述目标网络侧创建或保留承载的依据信息确定目标网络侧不能创 建或保留的承载的信息， 其中， 所述目标网络侧创建或保留承载的依据信息包 括以下信息之一或其任意组合： 用户设备的承载上下文信息、 EPS承载状态信 息。
其中， 所述源网络侧移动管理网元 1601 和所述目标网络侧移动管理网元 可以为同一移动管理网元， 此时， 目标网络侧移动管理网元在确定目标网络侧 不能创建或保留的承载的信息后， 即可向源网络侧服务网关发送第一删除会话 请求消息。
本发明实施例提供的一种承载的处理方法和系统， 以及移动管理网元和服 务网关， 在发生移动管理流程时， 通过源网络侧移动管理网元指示源网络侧服 务网关向 PGW发送第二删除会话请求消息， 可触发 PGW删除目标网络侧不 能创建或保留的承载的信息， 使得 PGW中不再保留冗余的承载信息， 节省了 网络侧承载上下文资源， 另外， 源网络侧移动管理网元可通过目标网络侧移动 管理网元发送的通知消息获知目标网络侧不能创建或保留的承载的信息， 或者 息确定目标网络侧不能创建或保留的承载的信息， 使得源网络侧移动管理网元 获知目标网络侧不能创建或保留的承载的信息的方式更加灵活， 其次， 对删除 会话请求操作进行了分类， 源网络侧以及分组数据网关先删除目标网络侧不能 创建或保留的承载信息， 之后才在源网络侧删除用户设备剩余的目标网络侧能 够创建或保留的承载信息， 增强了源网络侧删除其所创建的 UE的承载上下文 信息的可操作性以及灵活性。
以上所述仅为本发明的较佳实施例而已， 并非用于限定本发明的保护范 围， 对于本领域普通技术人员来说， 本发明可以有各种变化和更改， 凡在本发 明精神和原则指导之下作出的任何修改、 等同替换或改进等， 均包含在本发明 的权利要求范围之内。

Claims

权 利 要 求 书
1、 一种承载的处理方法， 其特征在于， 该方法包括：
源网络侧移动管理网元获知目标网络侧不能创建或保留的承载的信息； 所述源网络侧移动管理网元触发源网络侧服务网关向分组域数据网络网 关发送第二删除会话请求消息， 所述第二删除会话请求消息携带所述目标网络 侧不能创建或保留的承载的信息， 以便于所述分组域数据网络网关删除所述目 标网络侧不能创建或保留的承载的信息。
2、 根据权利要求 1 所述的方法， 其特征在于， 所述源网络侧移动管理网 元触发源网络侧服务网关向分组域数据网络网关发送第二删除会话请求消息， 包括： 一删除会话请求消息， 所述第一删除会话请求消息携带所述目标网络侧不能创 建或保留的承载的信息；
所述源网络侧服务网关根据所述携带操作标识的第一删除会话请求消息， 向所述分组域数据网络网关发送第二删除会话请求消息。
3、 根据权利要求 2 所述的方法， 其特征在于， 所述操作标识取值为特定 值。
4、 根据权利要求 1或 2所述的方法， 其特征在于， 所述源网络侧移动管 理网元获知目标网络侧不能创建或保留的承载的信息， 包括：
所述源网络侧移动管理网元接收目标网络侧移动管理网元发送的通知消 息， 根据所述通知消息获知目标网络侧不能创建或保留的承载的信息。
5、 根据权利要求 4 所述的方法， 其特征在于， 所述源网络侧移动管理网 元接收目标网络侧移动管理网元发送的通知消息， 根据所述通知消息获知目标 网络侧不能创建或保留的承载的信息， 包括：
若所述通知消息携带目标网络侧不能创建或保留的承载的标识或接入点 名， 所述源网络侧移动管理网元直接获知所述目标网络侧不能创建或保留的承 载的信息； 或者
若所述通知消息携带目标网络侧可以创建或保留的承载的标识或接入点 名， 所述源网络侧移动管理网元根据本地存储的用户设备 UE的承载上下文信 息以及所述目标网络侧可以创建或保留的承载的标识或接入点名， 确定目标网 络侧不能创建或保留的承载的信息； 或者
若所述通知消息携带演进分组系统 EPS承载状态信元，所述 EPS承载状态 信元分别指明了目标网络侧可以创建或保留的承载以及目标网络侧不能创建 或保留的承载，所述源网络侧移动管理网元根据所述 EPS承载状态信元获知目 标网络侧不能创建或保留的承载的信息； 或者
若所述通知消息携带本地网际协议接入 LIPA分组数据网络 PDN连接不支 持标识， 所述源网络侧移动管理网元根据所述 LIPA PDN连接不支持标识获知 目标网络侧不能创建或保留的 LIPA PDN连接。
6、 根据权利要求 4或 5所述的方法， 其特征在于， 所述源网络侧移动管 理网元接收目标网络侧移动管理网元发送的通知消息包括： 接收所述目标网络 侧移动管理网元发送的上下文应答消息或者转发重定向响应消息。
7、 根据权利要求 4或 5或 6所述的方法， 其特征在于， 所述接收目标网 络侧移动管理网元发送的通知消息之前， 所述方法还包括： 息确定目标网络侧不能创建或保留的承载的信息， 所述目标网络侧创建或保留 承载的依据信息包括以下信息之一或其任意组合： 用户设备的承载上下文信
LIPA PDN连接的信息。
8、 根据权利要求 1或 2所述的方法， 其特征在于， 所述源网络侧移动管 理网元获知目标网络侧不能创建或保留的承载的信息， 包括： 所述源网络侧移动管理网元根据目标网络侧创建或保留承载的依据信息 确定目标网络侧不能创建或保留的承载的信息， 所述目标网络侧创建或保留承 载的依据信息包括以下信息之一或其任意组合： 用户设备的承载上下文信息、
PDN连接的信息。
9、 根据权利要求 8所述的方法， 其特征在于， 所述方法还包括： 若源网络侧移动管理网元和目标网络侧移动管理网元为同一移动管理网 元， 所述源网络侧移动管理网元获取自身保存的用户设备的承载上下文信息、 目标网络侧的本地策略和目标网络侧是否支持创建 LIPA PDN连接的信息， 以 及获取用户设备发送的 EPS承载状态信元； 或者，
若源网络侧移动管理网元和目标网络侧移动管理网元为不同的移动管理 息， 以及获取所述目标网络侧移动管理网元转发的 EPS承载状态信元、 目标网 络侧的本地策略和目标网络侧是否支持创建 LIPA PDN连接的信息。
10、 根据权利要求 7或 8或 9所述的方法， 其特征在于， 所述根据目标网 络侧创建或保留承载的依据信息确定目标网络侧不能创建或保留的承载的信 息， 包括：
根据所述用户设备的承载上下文信息与 EPS承载状态信元是否不一致，确 定目标网络侧不能创建或保留的承载的信息； 或者 的信息， 其中， 所述目标网络侧的本地策略包含接入 PDN连接数量和 /或承载 上下文数量控制策略； 或者
根据所述目标网络侧是否支持创建 LIPA PDN连接的信息， 确定目标网络 侧不能创建或保留的 LIPA PDN连接。
11、 根据权利要求 1或 2所述的方法， 其特征在于， 所述源网络侧服务网 关向所述分组域数据网络网关发送第二删除会话请求消息之后， 还包括： 请求消息， 所述第三删除会话请求消息指示所述源网络侧服务网关删除用户设 备剩余的目标网络侧可以创建或保留的承载的信息。
12、 一种承载的处理方法， 其特征在于， 该方法包括：
源网络侧服务网关接收源网络侧移动管理网元发送的触发指示， 所述触发 指示是所述源网络侧移动管理网元获知目标网络侧不能创建或保留的承载的 信息之后发送的；
所述源网络侧服务网关根据所述触发指示， 向分组域数据网络网关发送第 二删除会话请求消息， 所述第二删除会话请求消息携带所述目标网络侧不能创 建或保留的承载的信息， 以便于所述分组域数据网络网关删除所述目标网络侧 不能创建或保留的承载的信息。
13、 根据权利要求 12 所述的方法， 其特征在于， 所述源网络侧服务网关 接收源网络侧移动管理网元发送的触发指示包括： 接收所述源网络侧移动管理 网元发送的携带操作标识的第一删除会话请求消息， 所述第一删除会话请求消 息携带所述目标网络侧不能创建或保留的承载的信息；
则， 所述源网络侧服务网关根据所述携带操作标识的第一删除会话请求消 息， 向所述分组域数据网络网关发送第二删除会话请求消息。
14、 根据权利要求 12或 13所述的方法， 其特征在于， 所述源网络侧服务 网关向所述分组域数据网络网关发送第二删除会话请求消息之后， 还包括： 所述源网络侧服务网关接收所述源网络侧移动管理网元发送的第三删除 会话请求消息， 所述第三删除会话请求消息指示所述源网络侧服务网关删除用 户设备剩余的目标网络侧可以创建或保留的承载的信息。
15、 一种移动管理网元， 其特征在于， 包括：
获知单元， 用于获知目标网络侧不能创建或保留的承载的信息； 发送单元， 用于在所述获知单元获知目标网络侧不能创建或保留的承载的 信息后， 触发源网络侧服务网关向分组域数据网络网关发送第二删除会话请求 消息， 所述第二删除会话请求消息携带所述目标网络侧不能创建或保留的承载 的信息， 以便于所述分组域数据网络网关删除所述目标网络侧不能创建或保留 的承载的信息。
16、 根据权利要求 15 所述的移动管理网元， 其特征在于， 所述获知单元 包括：
第一接收单元， 用于接收目标网络侧移动管理网元发送的通知消息， 所述 通知消息携带目标网络侧不能创建或保留的承载的标识或接入点名；
第一确定单元， 用于在所述第一接收单元接收到携带目标网络侧不能创建 或保留的承载的标识或接入点名的通知消息后， 根据所述通知消息直接获知所 述目标网络侧不能创建或保留的承载的信息； 或者
第二接收单元， 用于接收目标网络侧移动管理网元发送的通知消息， 所述 通知消息携带目标网络侧可以创建或保留的承载的标识或接入点名；
第二确定单元， 用于在所述第二接收单元接收到携带目标网络侧可以创建 或保留的承载的标识或接入点名的通知消息后， 根据本地存储的用户设备的承 载上下文信息以及所述目标网络侧可以创建或保留的承载的标识或接入点名， 确定目标网络侧不能创建或保留的承载的信息； 或者
第三接收单元， 用于接收目标网络侧移动管理网元发送的通知消息， 所述 通知消息携带 EPS承载状态信元， 所述 EPS承载状态信元分别指明了目标网 络侧可以创建或保留的承载以及目标网络侧不能创建或保留的承载；
第三确定单元，用于在所述第三接收单元接收到携带 EPS承载状态信元的 通知消息后，根据所述 EPS承载状态信元获知目标网络侧不能创建或保留的承 载的信息； 或者
第四接收单元， 用于接收目标网络侧移动管理网元发送的通知消息， 所述 通知消息携带 LIPA PDN连接不支持标识；
第四确定单元， 用于在所述第四接收单元接收到携带 LIPA PDN连接不支 持标识的通知消息后， 根据所述 LIPA PDN连接不支持标识获知目标网络侧不 能创建或保留的 LIPA PDN连接。
17、 根据权利要求 15 所述的移动管理网元， 其特征在于， 所述获知单元 具体用于： 根据目标网络侧创建或保留承载的依据信息确定目标网络侧不能创 建或保留的承载的信息；
其中， 所述目标网络侧创建或保留承载的依据信息包括以下信息之一或其 任意组合： 用户设备的承载上下文信息、 EPS承载状态信元、 目标网络侧的本 地策略以及目标网络侧是否支持创建 LIPA PDN连接的信息。
18、 根据权利要求 17 所述的移动管理网元， 其特征在于， 所述获知单元 包括：
第五确定单元，用于根据所述的用户设备的承载上下文信息与 EPS承载状 态信元是否一致， 确定目标网络侧不能创建或保留的承载的信息； 或者 能创建或保留的承载的信息， 其中， 所述目标网络侧的本地策略包含接入 PDN 连接数量和 /或承载上下文数量控制策略； 或者
第七确定单元， 用于根据所述的目标网络侧是否支持创建 LIPA PDN连接 的信息， 确定目标网络侧不能创建或保留的 LIPA PDN连接。
19、 根据权利要求 15-18任意一项所述的移动管理网元， 其特征在于， 所 述发送单元具体用于：
在所述获知单元获知目标网络侧不能创建或保留的承载的信息后， 向源网 络侧服务网关发送携带操作标识的第一删除会话请求消息， 所述第一删除会话 请求消息携带所述目标网络侧不能创建或保留的承载的信息， 所述操作标识触 发源网络侧服务网关向分组域数据网络网关发送第二删除会话请求消息。
20、 根据权利要求 15或 19所述的移动管理网元， 其特征在于， 所述发送 单元还用于：
在删除目标网络侧不能创建或保留的承载的信息后， 向所述源网络侧服务 网关发送第三删除会话请求消息， 所述第三删除会话请求消息指示所述源网络 侧服务网关删除用户设备剩余的目标网络侧可以创建或保留的承载的信息。
21、 一种服务网关， 其特征在于， 包括：
接收单元， 用于接收源网络侧移动管理网元发送的触发指示， 所述触发指 示是所述源网络侧移动管理网元获知目标网络侧不能创建或保留的承载的信 息之后发送的；
发送单元， 用于根据所述接收单元接收到的触发指示， 向分组域数据网络 网关发送第二删除会话请求消息， 所述第二删除会话请求消息携带所述目标网 络侧不能创建或保留的承载的信息， 以便于所述分组域数据网络网关删除所述 目标网络侧不能创建或保留的承载的信息。
22、 根据权利要求 21 所述的服务网关， 其特征在于， 所述接收单元具体 用于接收源网络侧移动管理网元发送的携带操作标识的第一删除会话请求消 息； 所述发送单元具体用于根据所述第一删除会话请求消息中的操作标识， 向 所述分组域数据网络网关发送第二删除会话请求消息。
23、 一种承载的处理系统， 其特征在于， 包括： 源网络侧移动管理网元， 源网络侧服务网关， 分组域数据网络网关， 其中，
所述源网络侧移动管理网元， 用于在获知目标网络侧不能创建或保留的承 载的信息后， 触发源网络侧服务网关向分组域数据网络网关发送第二删除会话 请求消息；
所述源网络侧服务网关， 用于接收源网络侧移动管理网元发送的触发指 示，并根据所述触发指示，向分组域数据网络网关发送第二删除会话请求消息， 所述第二删除会话请求消息携带所述目标网络侧不能创建或保留的承载的信 息；
分组域数据网络网关， 用于在接收到源网络侧服务网关发送的第二删除会 话请求消息后， 根据所述第二删除会话请求消息中携带的目标网络侧不能创建 或保留的承载的信息， 删除所述目标网络侧不能创建或保留的承载的信息。
24、 根据权利要求 23 所述的系统， 其特征在于， 所述源网络侧移动管理 网元包括：
获知单元， 用于获知目标网络侧不能创建或保留的承载的信息； 发送单元， 用于在所述获知单元获知目标网络侧不能创建或保留的承载的 信息后， 触发源网络侧服务网关向分组域数据网络网关发送第二删除会话请求 消息。
25、 根据权利要求 23或 24所述的系统， 其特征在于， 所述源网络侧服务 网关包括：
接收单元， 用于接收源网络侧移动管理网元发送的触发指示， 所述触发指 示是所述源网络侧移动管理网元获知目标网络侧不能创建或保留的承载的信 息之后发送的；
发送单元， 用于根据所述接收单元接收到的触发指示， 向分组域数据网络 网关发送第二删除会话请求消息。
26、 根据权利要求 23或 24或 25所述的系统， 其特征在于， 所述系统还 包括目标网络侧移动管理网元； 通知消息， 使得所述源网络侧移动管理网元才艮据所述通知消息获知目标网络侧 不能创建或保留的承载的信息； 或者， 标网络侧创建或保留承载的依据信息， 使得所述源网络侧移动管理网元根据所 述目标网络侧创建或保留承载的依据信息确定目标网络侧不能创建或保留的 承载的信息， 其中， 所述目标网络侧创建或保留承载的依据信息包括以下信息 之一或其任意组合： 用户设备的承载上下文信息、 EPS承载状态信元、 目标网 络侧的本地策略以及目标网络侧是否支持创建 LIPA PDN连接的信息。
27、 根据权利要求 26所述的系统， 其特征在于， 所述源网络侧移动管理 网元和所述目标网络侧移动管理网元为同一移动管理网元。
PCT/CN2011/079153 2011-08-31 2011-08-31 一种承载的处理方法、系统及装置 WO2013029245A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2011/079153 WO2013029245A1 (zh) 2011-08-31 2011-08-31 一种承载的处理方法、系统及装置
CN201180001575.XA CN103155688B (zh) 2011-08-31 2011-08-31 一种承载的处理方法、系统及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/079153 WO2013029245A1 (zh) 2011-08-31 2011-08-31 一种承载的处理方法、系统及装置

Publications (1)

Publication Number Publication Date
WO2013029245A1 true WO2013029245A1 (zh) 2013-03-07

Family

ID=47755203

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/079153 WO2013029245A1 (zh) 2011-08-31 2011-08-31 一种承载的处理方法、系统及装置

Country Status (2)

Country Link
CN (1) CN103155688B (zh)
WO (1) WO2013029245A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104579935A (zh) * 2013-10-10 2015-04-29 宁夏先锋软件有限公司 一种可进行承载处理的服务网关
WO2017121206A1 (zh) * 2016-01-15 2017-07-20 中兴通讯股份有限公司 承载建立方法和系统、以及mme和sgw
WO2018171107A1 (zh) * 2017-03-20 2018-09-27 华为技术有限公司 一种通信系统间移动方法、设备和系统
CN109819483A (zh) * 2017-11-21 2019-05-28 电信科学技术研究院 专用承载创建方法、移动性管理实体及分组数据网络网关
CN109996324A (zh) * 2017-12-29 2019-07-09 展讯通信（上海）有限公司 Eps承载状态同步方法、装置及网络侧设备
RU2796658C2 (ru) * 2021-03-22 2023-05-29 Хуавей Текнолоджиз Ко., Лтд. Способ, устройство и система межсистемного перемещения

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112399512B (zh) * 2017-08-17 2022-03-29 华为技术有限公司 一种通信系统间移动方法及装置
CN109561473B (zh) * 2017-09-25 2021-01-15 华为技术有限公司 一种通信资源的释放方法及装置、非暂态计算机存储介质
CN111148274B (zh) * 2018-11-01 2024-04-12 北京三星通信技术研究有限公司 用于会话建立的方法、会话管理功能实体、基站和存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101656694A (zh) * 2008-08-21 2010-02-24 上海华为技术有限公司 承载删除方法、通信系统和相关设备
WO2011095256A1 (en) * 2010-02-02 2011-08-11 Telefonaktiebolaget L M Ericsson (Publ) Restart of peer node

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101656694A (zh) * 2008-08-21 2010-02-24 上海华为技术有限公司 承载删除方法、通信系统和相关设备
WO2011095256A1 (en) * 2010-02-02 2011-08-11 Telefonaktiebolaget L M Ericsson (Publ) Restart of peer node

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104579935A (zh) * 2013-10-10 2015-04-29 宁夏先锋软件有限公司 一种可进行承载处理的服务网关
WO2017121206A1 (zh) * 2016-01-15 2017-07-20 中兴通讯股份有限公司 承载建立方法和系统、以及mme和sgw
CN106982472A (zh) * 2016-01-15 2017-07-25 中兴通讯股份有限公司 一种承载建立方法和系统、以及mme和sgw
CN106982472B (zh) * 2016-01-15 2021-11-23 中兴通讯股份有限公司 一种承载建立方法和系统、以及mme和sgw
RU2745387C2 (ru) * 2017-03-20 2021-03-24 Хуавей Текнолоджиз Ко., Лтд. Способ, устройство и система межсистемного хэндовера
WO2018171107A1 (zh) * 2017-03-20 2018-09-27 华为技术有限公司 一种通信系统间移动方法、设备和系统
RU2729048C1 (ru) * 2017-03-20 2020-08-04 Хуавей Текнолоджиз Ко., Лтд. Способ, устройство и система межсистемного хэндовера
US11832134B2 (en) 2017-03-20 2023-11-28 Huawei Technologies Co., Ltd. Inter-communications-system moving method, device, and system
CN112867077B (zh) * 2017-03-20 2022-05-24 华为技术有限公司 一种通信系统间移动方法、用户设备和存储介质
CN112867077A (zh) * 2017-03-20 2021-05-28 华为技术有限公司 一种通信系统间移动方法、用户设备和存储介质
US11039345B2 (en) 2017-03-20 2021-06-15 Huawei Technologies Co., Ltd. Inter-communications-system moving method, device, and system
AU2020239707B2 (en) * 2017-03-20 2022-02-24 Huawei Technologies Co., Ltd. Inter-communications-system handover method, device, and system
US11076375B2 (en) 2017-11-21 2021-07-27 China Academy Of Telecommunications Technology Dedicated bearer creation method, mobility management entity, and packet data network gateway
CN109819483A (zh) * 2017-11-21 2019-05-28 电信科学技术研究院 专用承载创建方法、移动性管理实体及分组数据网络网关
CN109819483B (zh) * 2017-11-21 2020-09-11 电信科学技术研究院 专用承载创建方法、移动性管理实体及分组数据网络网关
CN109996324A (zh) * 2017-12-29 2019-07-09 展讯通信（上海）有限公司 Eps承载状态同步方法、装置及网络侧设备
CN109996324B (zh) * 2017-12-29 2022-03-01 展讯通信（上海）有限公司 Eps承载状态同步方法、装置及网络侧设备
RU2796658C2 (ru) * 2021-03-22 2023-05-29 Хуавей Текнолоджиз Ко., Лтд. Способ, устройство и система межсистемного перемещения

Also Published As

Publication number Publication date
CN103155688A (zh) 2013-06-12
CN103155688B (zh) 2016-07-13

Similar Documents

Publication Publication Date Title
US11979778B2 (en) Release of a second session of a wireless device by an access and mobility management function
US11606727B2 (en) Handover of a wireless device in a network
KR101044685B1 (ko) 리소스를 구축하고 삭제하기 위한 방법 및 네트워크 장비
WO2013029245A1 (zh) 一种承载的处理方法、系统及装置
US20200337093A1 (en) Method for supporting and providing ladn service in wireless communication system and apparatus therefor
WO2018145671A1 (zh) 跨系统的切换方法和装置、计算机存储介质
KR20200108036A (ko) 서비스 성능 모니터링 및 보고
WO2011009257A1 (zh) 一种承载绑定和事件报告功能的重选系统及方法
US11825356B2 (en) Policy control method and system, network element, and storage medium
WO2011011943A1 (zh) 一种承载绑定和事件报告功能的重选方法
WO2014101571A1 (zh) 一种承载分配方法及用户设备、基站和服务网关
WO2009149669A1 (zh) 一种数据通讯方法及通讯系统以及相关装置
WO2009097772A1 (zh) 一种资源释放控制方法及通讯系统以及相关设备
WO2012149769A1 (zh) 一种获取无线局域网络配置信息的方法、系统及装置
JPWO2018066702A1 (ja) 無線通信システム、ネットワーク装置及び無線通信方法
WO2009117879A1 (zh) 一种指示服务网关承载管理的方法
WO2012097509A1 (zh) 切换方法和移动管理网元
WO2008113235A1 (fr) Procédé pour éviter la libération erronée de ressources pendant une mise à jour de zone de suivi ou un transfert intercellulaire
WO2013040980A1 (zh) 一种流迁移的实现方法、终端和分组数据网络网关
KR101384697B1 (ko) 통신 접속을 제공하기 위한 방법 및 통신 엔티티
WO2009132582A1 (zh) 一种删除承载的方法与装置
EP2571302A1 (en) Method, apparatus and system for processing local address in shunt connection
WO2010004714A1 (ja) ハンドオーバ処理方法、その方法で用いられる移動端末及び通信管理装置
WO2012103773A1 (zh) 中继系统的过载控制方法及系统
WO2012013103A1 (zh) 一种网关标识上报的方法及系统

Legal Events

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

Ref document number: 201180001575.X

Country of ref document: CN

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

Ref document number: 11871477

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

Country of ref document: EP

Kind code of ref document: A1