WO2017080266A1 - 一种网关信息更新的方法及装置 - Google Patents

一种网关信息更新的方法及装置 Download PDF

Info

Publication number
WO2017080266A1
WO2017080266A1 PCT/CN2016/094213 CN2016094213W WO2017080266A1 WO 2017080266 A1 WO2017080266 A1 WO 2017080266A1 CN 2016094213 W CN2016094213 W CN 2016094213W WO 2017080266 A1 WO2017080266 A1 WO 2017080266A1
Authority
WO
WIPO (PCT)
Prior art keywords
gwu
mme
enodeb
address
teid
Prior art date
Application number
PCT/CN2016/094213
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 中兴通讯股份有限公司
Publication of WO2017080266A1 publication Critical patent/WO2017080266A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0064—Transmission or use of information for re-establishing the radio link of control information between different access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node

Definitions

  • This document relates to, but is not limited to, the field of communications, and in particular, to a method and apparatus for updating gateway information.
  • FIG. 1 is a schematic structural diagram of an EPS (Evolved Packet System) of 3GPP (3rd Generation Partnership Project).
  • the EPS includes E-UTRAN (Evolved Universal Terrestrial Radio). Access Network, evolved universal mobile communication system terrestrial radio access network), MME (Mobility Management Entity), S-GW (Serving Gateway), PDN GW or P-GW (Packet Data Network Gateway, The packet data network gateway, the HSS (Home Subscriber Server), the PCRF (Policy and Charging Rules Function), and other supporting nodes.
  • E-UTRAN Evolved Universal Terrestrial Radio
  • Access Network evolved universal mobile communication system terrestrial radio access network
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • PDN GW or P-GW Packet Data Network Gateway
  • the packet data network gateway the HSS (Home Subscriber Server), the PCRF (Policy and Charging Rules Function), and other supporting nodes.
  • HSS Home Subscriber Server
  • PCRF Policy and Charging Rules Function
  • the MME and the E-UTRAN are connected through an S1-MME interface, and are used for control plane related operations such as mobility management, non-access stratum signaling processing, and user mobility management context management;
  • the S-GW is passed with the E-UTRAN.
  • the access gateway device connected to the S1-U interface forwards data between the E-UTRAN and the P-GW, and is used to buffer the paging waiting data;
  • the P-GW is the EPS and PDN (Packet Data Network Gateway, packet) A border gateway for data networks, for PDN access and forwarding of data between EPS and PDN.
  • the PCRF is responsible for the formulation of policy decisions and charging rules, and the operator's IP services (interacting with the operator's IP service entity), providing service data flow-based gating, quality of service control, and charging rules to the GW (Gateway, Gateway).
  • the bearer plane performs the policy and charging rules established by the PCRF.
  • the GW performs QoS (Quality of Service) authorization and gating control according to the rules sent by the PCRF.
  • QoS Quality of Service
  • the charging rule sent by the PCRF the corresponding service data flow charging operation is performed, and the charging may be online charging or offline charging. If it is online charging, you need to work with OCS (Online Charging System) for credit management.
  • OCS Online Charging System
  • the related charging information is exchanged between the OFCS (Offline Charging System) and the offline charging system.
  • the interface between the GW and the PCRF is a Gx interface
  • the interface between the OC and the OCS is a Gy interface
  • the interface between the OFCS and the OFCS is a Gz interface.
  • the User Equipment can find the corresponding PDN through the APN (Access Point Name), and establish an IP-CAN (IP Connectivity Access Network) for accessing the PDN network.
  • the PDN connection for the session is not limited to 3GPP.
  • EPS gateways gradually create some constraints.
  • the user data stream processing is concentrated on the PDN egress gateway, which causes the gateway device to have complicated functions and poor scalability.
  • the control plane of the gateway is highly coupled with the forwarding plane, which is not conducive to the smooth evolution of the core network.
  • the frequency of the forwarding surface expansion is higher than that of the control plane.
  • the tight coupling causes the control plane to forward and expand synchronously.
  • the short equipment update period leads to an increase in the composite cost.
  • Network layer data forwarding is difficult to identify users and service features. It can only be forwarded according to the QoS delivered by the upper layer, resulting in inefficient use of network resources. It is difficult to finely control the data flow based on user and service characteristics.
  • a large number of strategies require manual configuration, resulting in increased management complexity and high operating costs. Therefore, the control functions and forwarding functions in the packet domain gateway need to be further separated to meet the needs of network development and market applications.
  • the architecture splits the S-GW/P-GW in the original EPS architecture into two functional network elements: GwC (Gateway Controller, Gateway Control Entity) and GwU (Gateway User).
  • GwC is responsible for the control plane functions of the S/P-GW, including load sharing, GwU selection, IP address and tunnel identification assignment, policy and charging control.
  • GwU includes SGwU (Serving Gateway User) and PGwU (Packet Data Network Gateway User), which correspond to the user planes of S-GW and P-GW, and are responsible for S/P-
  • the user plane related functions of the GW include data stream identification and deep packet parsing, QoS processing and bearer binding, and buffering of downlink paging data.
  • the user plane and control plane interface of the docking correspond to GwC and SGwU/PGwU respectively, and the other corresponding interface functions are compared with the original EPS architecture.
  • the MME performs selection of the S-GW based on the user location, the subscription information, and the like.
  • the MME determines whether the S-GW needs to be reselected, and performs S-GW selection and information update of the uplink and downlink data transmission paths. If it is determined that the S-GW needs to be reselected, the reselection is based on the updated location information and the subscription information.
  • the appropriate S-GW sends the newly selected S-GW uplink user plane address and the tunnel identifier to the eNodeB (Evolved Node B, Evolved Node B), and updates the uplink data transmission path information to ensure the correct transmission of the uplink data. .
  • the new eNodeB information for example, the eNodeB downlink user plane address and the tunnel identifier are sent to the S-GW, and the downlink data transmission path information is updated to ensure the correct transmission of the downlink data. If the reselection of the S-GW is not required, the information such as the current user plane address and the tunnel identifier of the current S-GW is sent to the new eNodeB, and the new eNodeB downlink user plane address and the tunnel identifier are transmitted to the current S-GW. Perform reconstruction of the uplink and downlink data channels. In the handover process, whether the MME is changed may be referred to the mechanism in the related art, and the expansion description is not described here.
  • the GW selection by the MME is actually the selection of the GwC, and the GwC is responsible for selecting and managing the GwU in its corresponding GwU group.
  • the data cannot be correctly forwarded in a scenario where the GwC does not need to be switched but the GwU is reselected. For example, the switching process based on the S1 interface.
  • the MME After the MME receives the handover request message of the original eNodeB, the MME determines that the GwC does not need to be changed, and the current GwU address and the tunnel identifier are sent to the new eNodeB, and the new eNodeB does not necessarily obtain the final GwU address and Tunnel ID. If GwU is reselected, the upstream and downstream data channels are set up incorrectly. If the uplink data arrives at the eNodeB, it will be transmitted to the old GwU. This may result in the failure to connect to the GwU or the GwU to be discarded after it is received. Business continuity and data integrity cannot be guaranteed.
  • the handover mechanism in the related art cannot support the correct and reliable transmission of the data stream in some scenarios, and cannot guarantee the continuity and integrity of the service.
  • the embodiment of the invention provides a method and a device for updating gateway information, which can support the correct and reliable transmission of data streams in an architecture separated from the GW control plane and the user plane.
  • a method for updating gateway information includes:
  • the mobility management unit MME acquires a gateway GW type
  • the MME When the MME learns that the evolved Node B eNodeB of the user equipment UE is changed, if the acquired GW type is a GW separated from the user plane and the control plane, the MME sends a create session request message or a modify bearer request message to the gateway control plane entity GwC. Carrying the location information of the UE in the create session request message or the modify bearer request message;
  • the MME obtains a gateway user plane entity GwU address and a tunnel endpoint identifier TEID from the Create Session Response message or the Modify Bearer Response message returned by the GwC.
  • the location information includes a tracking area identifier TAI and user location information ECGI.
  • the method further includes:
  • the location change indication of the UE is carried in the create session request message or the modify bearer request message.
  • the manner in which the MME learns that the eNodeB of the UE is changed includes: receiving one or more of the following messages: an attach request, a tracking area update request, a service request, a handover request, and a forward relocation request.
  • the acquiring, by the MME, the gateway GW type includes:
  • the MME acquires the GW type according to the GW type or the control plane user plane separation identifier carried in the Create Session Response message or the Modify Bearer Response message returned by the serving gateway S-GW or the GwC.
  • the MME acquiring the gateway GW type further includes: when the GW type and the control plane user plane separation identifier are not carried in the create session response message or the modify bearer response message, the MME determines that the acquired GW type is The GW of the user plane and the control plane are unified.
  • the method further includes:
  • the MME sends a Create Session Request message or a Modify Bearer Request message to the S-GW or the GwC, and carries the GW type request.
  • the MME further includes:
  • the MME If the MME does not send the GwU address and the TEID to the changed eNodeB, the MME transmits the acquired GwU address and the TEID to the changed eNodeB.
  • the MME further includes:
  • the MME has sent the GwU address and the TEID to the changed eNodeB, it is determined whether the acquired GwU address and the TEID are the same as those sent to the changed eNodeB, and if not, the acquired GwU address and TEID are sent. Give the changed eNodeB.
  • the method further includes:
  • the MME in the handover request or the initial context request of the changed eNodeB, carries a pending transaction indication, where the pending transaction indication is used to notify the changed eNodeB before receiving the GwU address and the TEID again, or confirming Before GwU changes, the data that is uplinked to GwU and the data that is forwarded are buffered.
  • a gateway information updating device configured in the mobility management unit MME, includes:
  • a type obtaining module configured to obtain a gateway GW type
  • the requesting module is configured to send a create session request message or modify a bearer request message to the gateway control plane if the acquired GW type is a GW separated from the user plane and the control plane when the evolved Node B eNodeB of the user equipment UE is changed.
  • the entity GwC carries the location information of the UE in the create session request message or the modify bearer request message;
  • the gateway information obtaining module is configured to obtain a gateway user plane entity GwU address and a tunnel endpoint identifier TEID from the create session response message or the modify bearer response message returned by the GwC.
  • the location information includes a tracking area identifier TAI and user location information ECGI.
  • the requesting module is further configured to carry a location change indication of the UE in the create session request message or the modify bearer request message.
  • the manner in which the requesting module learns that the eNodeB of the UE is changed includes: receiving one or more of the following messages: an attach request, a tracking area update request, a service request, a handover request, and a forward relocation request.
  • the acquiring the GW type by the type obtaining module includes:
  • the type obtaining module creates a session response message according to the service gateway S-GW or GwC. Or modify the GW type carried in the bearer response message or the control plane user plane separation identifier to obtain the GW type.
  • the obtaining, by the type obtaining module, the gateway GW type further includes: when the GW type and the control plane user plane separation identifier are not carried in the create session response message or the modify bearer response message, determining that the acquired GW type is a user The GW of the face and control surfaces.
  • the type obtaining module is further configured to send a create session request message or a modify bearer request message to the S-GW or the GwC in the process flow that the UE is attached to the network before acquiring the gateway GW type, Carry a GW type request.
  • the device according to any one of the preceding claims further comprising:
  • the sending module is configured to send the GwU address and the TEID acquired by the gateway information acquiring module to the changed eNodeB when the GwU address and the TEID are not sent to the changed eNodeB.
  • the device further includes:
  • the sending module is configured to determine, when the GwU address and the TEID have been sent to the changed eNodeB, whether the GwU address and the TEID acquired by the gateway information acquiring module are the same as those sent to the changed eNodeB, if different And sending the GwU address and the TEID acquired by the gateway information acquiring module to the changed eNodeB.
  • the sending module is further configured to: in the handover request or the initial context request of the changed eNodeB, carry a pending transaction indication, where the pending transaction indication is used to notify the changed eNodeB to receive the GwU again.
  • the data that is uplinked to the GwU and the data that is forwarded are buffered.
  • a computer readable storage medium storing computer executable instructions for performing the above method.
  • the MME when the GW control plane and the user plane are separated, the MME can learn the correct GwU address and the tunnel endpoint identifier, and further inform the eNodeB, so as to ensure that the data flow can be correctly and reliably transmitted when the GwU is changed. .
  • 1 is a schematic structural diagram of an evolved packet system of 3GPP
  • FIG. 2 is a schematic structural diagram of separating a GW control plane from a user plane in a non-roaming scenario
  • FIG. 3 is a schematic flowchart of a gateway information update method according to Embodiment 1;
  • FIG. 4 is a schematic diagram of the GwC informing the GW type or the GW controlling the user plane separation indication in the attach procedure;
  • FIG. 5 is a schematic diagram of establishing a correct uplink data channel in a handover process based on an S1 interface
  • Figure 6 is a schematic diagram of establishing a correct uplink data channel in a service request process
  • FIG. 7 is a schematic diagram of a gateway information updating apparatus of Embodiment 2.
  • Embodiment 1 A method for updating gateway information, as shown in FIG. 3, includes steps S110-S130:
  • the MME acquires a gateway GW type.
  • the MME sends a create session request message or a modify bearer request message to the GwC if the acquired GW type is a GW with a user plane and a control plane separated, and the MME creates a session request message.
  • the MME obtains a GwU address and a TEID (Tunnel Endpoint Identifier) from the Create Session Response message or the Modify Bearer Response message returned by the GwC.
  • the TEID may be one or more.
  • the GwC address and the TEID carried in the GwC in the Create Session Response message or the Modify Bearer Response message are the current correct GwU address and TEID; GwC may determine whether to perform GwU reselection according to the location information, if Return to the original GwU address without reselecting And TEID, if you want to reselect, select GwU and return the changed GwU address and TEID.
  • the reason for the eNodeB change of the UE may be, but is not limited to, including: the location of the UE is changed.
  • the criterion for the change of the location of the UE may be: the eNodeB where the UE is currently located changes, that is, the IDs (identifications) of the eNodeBs before and after the UE are different.
  • the method may further include:
  • the location change indication of the UE is carried in the create session request message or the modify bearer request message.
  • the manner in which the MME learns that the eNodeB of the UE is changed may include, but is not limited to, receiving one or more of the following messages: an attach request, a tracking area update request, a service request, a handover request, and a forward relocation request.
  • step S110 includes:
  • the MME learns the GW type of the peer end according to the GW type or the control plane user plane separation identifier carried in the S-GW or the GwC to create the session response message or the modification bearer response message; the GW type includes the separation of the user plane and the control plane. GW, or GW where the user plane and the control plane are unified; when carrying the control plane user plane separation identifier, the GW type is a GW in which the user plane and the control plane are separated.
  • the peer end connected by the MME is a GW control plane function entity.
  • the method may further include:
  • the MME sends a Create Session Request message or a Modify Bearer Request message to the S-GW or the GwC, and carries the GW type request.
  • the GW type is a GW in which the user plane and the control plane are unified;
  • the step S110 may further include: when the GW type and the control plane user plane separation identifier are not carried in the create session response message or the modify bearer response message, the GW type acquired by the MME is a combination of a user plane and a control plane. GW.
  • step S130 may further include:
  • the MME If the MME does not send the GwU address and the TEID to the changed eNodeB, the MME sends The obtained GwU address and TEID are sent to the changed eNodeB.
  • the GwU address and the TEID sent in the alternative are the changed GwU address and the TEID.
  • step S130 may further include:
  • the MME has sent the GwU address and the TEID to the changed eNodeB, it is determined whether the acquired GwU address and the TEID are the same as those sent to the changed eNodeB, and if not, the acquired GwU address and TEID are sent. Give the changed eNodeB.
  • the GW sends the GwU address and the TEID to the changed eNodeB according to the process in the related art; and then sends the location information to the GwC; if the MME finds the GwU address and the TEID returned by the GwC.
  • the MME sends the GwU address and the TEID to the changed eNodeB again; if they are the same, they can no longer send; in other alternatives, they can also be set to send the station whether they are the same or not.
  • the obtained GwU address and TEID are given to the changed eNodeB.
  • the method may further include:
  • the MME carries a Pending Transaction (Pending Transaction) in the handover request or the initial context request of the changed eNodeB, where the Pending Transaction is used to notify the changed eNodeB before receiving the GwU address and the TEID again.
  • Pending Transaction Pending Transaction
  • the data that is uplinked to GwU and the data that is forwarded are buffered.
  • the Pending Transaction is equivalent to notifying the changed eNodeB to wait for the GwU to reselect. If the GwU address and the TEID sent by the MME are received again, the GwU reselection is confirmed, and the MME resends. The GwU address and the TEID are used to replace the GwU address and the TEID sent by the MME for the first time. If the eNodeB does not receive the GwU address and TEID sent by the MME again within the predetermined time period, the GwU is not changed, and the MME is used for the first time. The transmitted GwU address and TEID are used for uplink data transmission.
  • the eNodeB adds a cache function. Before the eNodeB receives the GwU address and the TEID again, or confirms that the GwU does not change, the eNodeB buffers the data that is uplinked to the GwU and the data that is forwarded.
  • the GW After the MME learns the eNodeB handover, the GW sends the GwU address and the TEID to the changed eNodeB according to the process in the related art; and then sends the location information to the GwC; the GwU address and the TEID acquired from the GwC are sent to the changed Whether the eNodeB is the same, and the obtained GwU address and the TEID are sent to the changed eNodeB again;
  • the Pending Transaction is configured to notify the changed eNodeB to cache the data that is uplinked to the GwU and the downlink forwarding data before receiving the GwU address and the TEID again;
  • the changed eNodeB buffers the data that is uplinked to the GwU and the data that is forwarded, until the GwU address and the TEID are received from the MME for the second time, and the GwU address and the TEID received for the second time are used for uplink data transmission.
  • the following is the process of attaching the UE to the network.
  • the SGW/GwC sends a Create Session Response message to the MME
  • the message carries the GW type identifier or the control plane user plane separation identifier, so that the MME perceives the peer connection.
  • GW type is a GW in which the user plane and the control plane are unified.
  • the GW type includes: a GW in which the user plane and the control plane are separated (ie, GW partitioning), or a GW in which the user plane and the control plane are unified (ie, GW set).
  • the peer end of the MME connection is a GW control plane function entity.
  • the GW type request is carried in the create session request message sent by the MME to the SGW/GwC.
  • the processing flow (1) includes the following steps 301-317:
  • Step 301 The UE initiates an attach operation to the EPS network, and the network completes the authentication and authorization for the UE.
  • the process is as described in the following steps 301-1 ⁇ 301-6:
  • the UE sends an attach request message to the eNodeB, where the message includes: the user identifier, the last visited tracking area, the core network capability of the UE, the attachment type, the NAS (Non-access stratum) serial number, and the PDN. Type and other information.
  • the eNodeB participates according to RRC (Radio Resource Control).
  • RRC Radio Resource Control
  • MME selection function select MME.
  • the eNodeB then forwards the attach message to the new MME along with the TAI and ECGI identity of the cell in which the UE is located.
  • the current new MME obtains the old MME address, and sends an identity request message to the old MME to request the IMSI (International Mobile Subscriber Identification Number). Code) and mobility context.
  • IMSI International Mobile Subscriber Identification Number
  • the new MME sends an identity request message to the UE to request the IMSI.
  • the UE notifies the network using an identity response message containing the IMSI.
  • the authentication process and the NAS security up and down establishment process must be performed. If the UE context exists in the network and the attachment request message is integrity protected or encrypted, the integrity check is successful. This step is optional. If the NAS security algorithm changes, this step only performs the NAS security context establishment process. The authentication and NAS security context establishment process is performed as defined in the Security Features section. After this step, all NAS messages will be protected by the NAS security function indicated by the MME.
  • IMEI mobile device identifier
  • the MME sends a mobile device identity detection request to the EIR (Equipment Identity Register), and the EIR responds with the detected result by the mobile device identity detection response message.
  • EIR Equipment Identity Register
  • this step may obtain an encryption option from the UE.
  • Step 302 The MME performs gateway selection according to the mechanism of selecting the GW in the EPC network in the related art, and acquires an IP address of the SGW and the PGW control plane. Whether the gateway type is the SGW or the GW separated from the control plane and the user plane has no effect on the GW selection of the MME. In this example, the GW type is a GW where the control plane and the user plane are separated, where the SGW control plane IP address is the IP address of the GwC.
  • Steps 303-306 are optional steps. If there is old context information in the network (for example, an active bearer context exists in the MME), the MME deletes the old bearer context information in the GW by deleting the session request procedure.
  • old context information in the network for example, an active bearer context exists in the MME
  • Step 303 The MME sends a Delete Session Request message to the GwC.
  • Step 304 The GwC initiates an IP-CAN session termination operation to the PCRF.
  • Step 305 The GwC sends a delete flow table request to the SGwU and the PGwU.
  • Step 306 The GwC replies to the MME with a Delete Session Response message.
  • Step 307 The MME sends a Create Session Request message of the S1-MME interface to the GwC, and carries the user identifier, the APN identifier, the MME control plane TEID, the GwC address, the PGW address, the PDN address, the bearer identifier, the handover indication, and the like. .
  • the handover indication indicates whether the current attachment is an initial attachment or a handover attachment.
  • the GwC has different operations in the subsequent steps according to the indication. For details, refer to the subsequent steps.
  • the PGW address is the address of the GwC (when the GW is set) or the address of the selected P-GW (when the GW is set).
  • the MME sends a GW type request to the Create Session Request message sent by the MME to the S-GW or the GwC.
  • Step 308 The GwC selects the correct GwU according to the gateway selection function, that is, selects the GwU that performs the forwarding function as the SGwU and the PGwU.
  • the TEID is assigned to the GwU, including the default bearer TEID of the PGwU, and the UL (Uplink, uplink) and DL (Downlink) TEID of the SGwU.
  • the GwC assigns an IP address to the PDN connection of the UE or acquires an IP address from the external PDN.
  • Step 309 When the PCRF is deployed and the session request message is created, the handover indication does not exist, and the GwC performs an IP-CAN session establishment process to obtain a default PCC (Policy and Charging Control) criterion of the UE. If there is a handover indication, the GwC performs an IP-CAN session modification procedure. The IP-CAN session establishment or modification operation on the Gx interface is initiated to the PCRF to trigger the establishment of the relevant bearer. If no dynamic PCC is deployed, GwC adopts a local QoS policy.
  • PCC Policy and Charging Control
  • Step 310 The GwC sends a flow table to the SGwU, including: an IP address of the PGwU, a TEID, and the like.
  • Step 311 The GwC sends a flow table to the PGwU, including: an SGwU IP address, a TEID, a meter, and other statistics.
  • Step 312 The GwC responds to the Create Session Response message to the MME, including the IP address of the SGwU, the TEID of the user plane, the TEID of the control plane, and the IP address and TEID of the PGwU. And the message carries the GW type identifier or the control plane user plane separation identifier, so that the MME perceives that the GW type is a GW in which the user plane and the control plane are separated (the MME and the GwC interact), or the GW in which the user plane and the control plane are unified ( Then the MME interacts with the S-GW).
  • the GW type is a GW in which the user plane and the control plane are separated.
  • the GwU address and the TEID carried in the create session response message are the changed GwU address and the TEID.
  • the Create Session Response message also carries related parameters defined by other EPS network S1-MME interfaces.
  • the MME senses and saves the GW type, and uses the GW type to decide whether to send the location change information to the GwC according to the GW type for the GGW to decide whether to perform the GwU reselection.
  • Step 313 The access network signaling interaction and the air interface bearer establishment.
  • the eNodeB sends an RRC Connection Reconfiguration message to the UE, which includes an EPS RB (Resource Block) ID and an Attach Accept message.
  • the UE sends an RRC Connection Reconfiguration Complete message to the eNodeB.
  • the eNodeB sends an Initial Context Response message to the new MME.
  • the message contains the TEID of the eNode B and the address of the eNodeB for the downlink data transmission of the S1-U interface.
  • the UE sends a Direct Transfer message to the eNodeB, which contains an Attach Complete message.
  • the eNodeB forwards the Attach Complete message to the new MME using the uplink NAS transport message.
  • Step 314 The MME sends the user plane address and the TEID of the eNodeB to the GW through the Modify Bearer Request message (in this example, to the GwC).
  • Step 315 The GwC updates the flow table to the SGwU, and sends the user plane address and the TEID of the eNodeB to the SGwU. After the downlink data channel is completed, data can be sent to the UE.
  • Step 316 If the connection scenario is switched, the GwC updates the flow table to the PGwU, and notifies the GwUPGwU to send data from the network side.
  • Step 317 The GwC replies to the MME with a Modify Bearer Response message.
  • the following is a process of initiating a handover between eNodeBs based on the S1 interface when the source eNodeB and the target eNodeB are not connected to the X2 interface.
  • the MME After receiving the handover request message, the MME detects that the location of the UE has changed, that is, the eNodeB has switched.
  • the current GW type is the user plane control plane separation GW, that is, the peer end of the MME connection is GwC.
  • a create session request message or a modify bearer request message is sent to the GwC, where the location information is carried.
  • the GwC determines whether the GwU needs to be reselected and executed.
  • the correct GwU address and tunnel identity TEID information is returned to the MME, and is transmitted by the MME to the target eNodeB to establish a correct uplink data transmission channel.
  • the process flow (2) includes the following steps 401 to 423:
  • Step 401 The source eNodeB sends a Handover Required message to the source MME (if the MME changes).
  • the handover request message carries a source-to-target transparent container, a target eNodeB Identity, a target TAI, and directly forwards the tag.
  • a list of bearers performing data forwarding is indicated in the transparent container.
  • the purpose of the TAI is to facilitate the selection of a suitable target MME.
  • Step 402 If the MME changes, the source MME selects the target MME, and sends a Forward Relocation Request message to the target MME, where the message includes the MME user context, the source to the target transparent container, and the target eNodeB identifier. Target tracking area identification and other information.
  • the target TAI is used by the MME to determine whether SGW/GwC reselection is to be performed.
  • the MME user context includes: a GW type identifier or a control plane user plane separation identifier, indicating that the GW type is a GW (the MME and the GwC interaction) separated by the user plane control plane or the GW of the user plane control plane is unified (the MME and the S- GW interaction).
  • Step 403 The MME determines whether S-GW/GwC reselection is to be performed (whether the source S-GW can continue to serve the UE), and if necessary, selects a new S-GW/GwC. If the MME does not relocate, the source MME determines whether to perform S-GW/GwC reselection and selects when to reselect. If the MME has relocated, the destination MME determines whether to perform S-GW/GwC weighting. Choose and choose when you want to re-elect.
  • the MME determines the GW type of the peer end according to the GW type identifier or the control plane user plane separation identifier.
  • the GW is the GW separated by the user plane control plane, that is, the peer end is GwC. If the eNodeB changes (according to the eNodeB ID), The target MME sends a create session request message or The GWC is modified to include the PGW address and the TEID, the TAI, the ECGI (including the identifier of the eNodeB), and the Serving Network (service network) for the GwC to perform the GwU reselection judgment and execution.
  • Step 403a if the GwU reselection is performed, and the GwU user plane address and the TEID are allocated by the GwU, the GwC sends a routing information update request to acquire a new GwU user plane address and TEID.
  • Step 404 The GwC determines whether to perform the reselection of the GwU according to the location information in the create session request message or the modify bearer request message, and the GwU selection function, and if necessary, perform the GwU selection.
  • the GwU user plane address and TEID for the uplink data transmission of the S1-U interface are allocated for the GwU.
  • the GwC sends a create session response message or a modify bearer response message to the target MME, and carries the allocated GwU address and the user faceted TEID. If the GwU is reselected, the GwU address is the new GwU address after the reselection.
  • Step 405 The target MME sends a Handover Request message to the target eNodeB, and creates a UE context on the target eNodeB, including bearer information and a security context.
  • the message carries the GwU address and the uplink TEID and EPS bearer QoS for the user plane allocated for each EPS bearer.
  • Step 406 The target eNodeB sends a Handover Request Acknowledge message to the target MME, where the message includes the address and TEID allocated by the target eNodeB for the uplink and downlink packets of the S1-U interface, and the address and TEID allocated for receiving the forwarding data.
  • Step 407 If the MME changes, the target MME sends a forward relocation response message to the source MME, where the message carries the address and TEID allocated by the eNodeB for receiving and forwarding data, and the message is forwardly forwarded, and the message includes the GwU forwarding address forwarded indirectly. And TEID.
  • Step 408 Indirect forwarding, the target MME sends a Create Indirect Data Forwarding Tunnel Request message to the GwC, where the message carries the target eNodeB user plane address and TEID for data forwarding.
  • Step 409 The GwC sends a routing information update message to the SGwU, and carries the IP address and TEID information of the target eNodeB used for data forwarding.
  • Step 409a GwC sends a routing information update message to the PGwU, which is carried for data forwarding.
  • Step 410 The GwC sends a Create Indirect Data Forwarding Tunnel Response message to the target MME, where the message carries the address and TEID used by the GwU to forward the uplink data of the S1-U interface. If the GwC is not relocated, the MME is the source MME.
  • Steps 411-415 perform an air interface switching operation and an indirect forwarding process of the data packet:
  • Step 411 The source MME sends a Handover Command message to the source eNodeB, where the message carries the address and TEID used by the GwU for data forwarding.
  • the source eNodeB constructs a Handover Command message to the UE using a Target to Source transparent container.
  • Step 412 The source eNodeB starts to forward downlink data from the source eNodeB through the GwU to the target eNodeB.
  • Step 413 After successfully synchronizing to the target cell, the UE sends a Handover Confirm message to the target eNodeB.
  • the downlink forwarding data from the source eNodeB is transmitted to the UE, and the uplink data is transmitted by the target eNodeB to the GwU.
  • Step 414 The target eNodeB sends a Handover Notify message to the target MME, where the message carries the TAI and the ECGI.
  • Step 415 If the target MME is relocated, the target MME sends a Forward Relocation Complete message to the source MME.
  • the source MME may send a Forward Relocation Complete Acknowledge message to the target MME.
  • Step 416 The target MME sends a Modify Bearer Request message to the GwC, and carries the user plane address and TEID of the target eNodeB.
  • the user location information may also be carried.
  • Step 417 If the user location information is reported in step 416, and the PCRF signs the event information, the GwC initiates an IP-CAN session modification operation with the PCRF, and reports the event information.
  • Step 418 The GwC sends a routing information update message to the SGwU, and carries the IP address and TEID information of the target eNodeB.
  • Step 418a The GwC sends a routing information update message to the PGwU, carrying the target eNodeB. IP address and TEID information.
  • Step 419 The GwC sends a Modify Bearer Response message to the target MME.
  • the GwC sends one or more "end marker" packets on the old path immediately after the path conversion to assist the target eNodeB in performing the reordering function.
  • Step 420 The downlink data runs through, and the source network side radio resource is released.
  • Step 421 The source MME sends a Delete Indirect Data Forwarding Tunnel Request message to the GwC to release the temporary resource allocated for indirect forwarding.
  • Step 422 The GwC sends a flow table update request to the SGwU, and deletes the flow table information used for data forwarding.
  • Step 423 The GwC returns a delete forward data channel request response message to the source MME.
  • the following is a service request procedure, that is, a process in which the UE establishes a signaling connection for the transmission of the upper layer signaling or the reserved resource of the active bearer in the IDLE state.
  • the MME detects that the location of the UE has changed, that is, the eNodeB has switched.
  • the GW type is the GW of the user plane control plane separation, that is, the peer end of the MME connection is GwC.
  • the MME sends a create session request message or a modify bearer request message to the GwC, where the location information is carried. Based on the location information provided by the MME, the GwC determines whether the GwU needs to be reselected and executed.
  • the correct GwU address and tunnel identity TEID information is returned to the MME, and is transmitted by the MME to the eNodeB to establish a correct uplink data transmission channel.
  • the process flow (3) includes the following steps 501-511:
  • Step 501 The UE sends a Service Request message to the MME by using the NAS message encapsulated in the RRC message.
  • the message is forwarded to the MME by the eNodeB, and the message is encapsulated in an Initial UE Message of the S1-AP type.
  • the initial UE message carries the user identifier and user location related information, including the TAI and the ECGI.
  • Step 502 The NAS authentication and security activation process may be performed according to the needs of the network.
  • Step 503 The MME determines the GW type of the peer end according to the GW type identifier or the control plane user plane separation identifier.
  • the GW type is the GW separated by the user plane control plane, that is, the peer end is GwC, if the eNodeB changes (according to the eNodeB ID) Judge), the MME sends a create session
  • the request message or the modify bearer request message is sent to the GwC, and the message includes location information such as a PGW address and a TEID, a TAI, an ECGI (including an eNodeB ID), and a Serving Network.
  • GwC performs judgment and execution of GwU reselection.
  • Step 503a if the GwU reselection is performed, and the GwU user plane address and the TEID are allocated by the GwU, the GwC sends a routing information update request to acquire a new GwU user plane address and TEID.
  • Step 504 The GwC determines whether to perform GwU reselection according to the GwU selection function according to the location information in the create session request message or the modification bearer request message, and performs the GwU selection if necessary.
  • the GwU is allocated a GwU address and a TEID for the uplink data transmission of the S1-U interface.
  • the GwC sends a Create Session Response message or a Modify Bearer Response message to the MME, and carries the allocated GwU address and the user-side TEID to the MME. If the GwU is reselected, the GwU address is the new GwU address after the reselection.
  • Step 505 The MME sends an S1-AP type message Initial Context Setup Request to the eNodeB, where the message carries the GwU address and the TEID on the user plane, and carries information such as QoS, security context, and MME signaling connection identifier.
  • Step 506 The eNodeB performs a radio bearer setup process according to the received GwU address, the TEID on the user plane, and the bearer QoS. And establish a user plane security context. After the user plane radio bearer setup and service request are completed and the EPS bearer status is synchronized between the UE and the MME, the UE will delete the EPS bearer without the radio bearer. If a radio bearer of a default EPS bearer is not established, the UE locally deactivates all EPS bearers associated with this default bearer.
  • Step 507 The uplink data of the UE is forwarded to the GwU through the eNodeB.
  • the eNodeB sends the uplink data to the GwU address and TEID provided in step 505.
  • SGwU forwards the upstream data to PGwU.
  • Step 508 The eNodeB sends an S1-AP type message Initial Context Setup Complete to the MME, where the message carries an eNodeB user plane address and TEID for downlink data transmission, and other bearer related information.
  • Step 509 The MME sends a Modify Bearer Request message to the GwC, where the message carries the eNodeB user plane address and TEID for downlink data transmission, and other bearer related information.
  • Step 510 The GwC sends a flow table to the SGwU to update the routing information, where the user plane IP address and TEID information of the eNodeB are included.
  • Step 510a The GwC sends a flow table to the PGwU, and updates the routing information, where the user plane IP address and TEID information of the eNodeB are included. At this point, the downlink data channel is established, and the GwU can send downlink data to the UE through the channel.
  • Step 511 The GwC responds to the MME with a modify bearer response message.
  • the MME When the MME detects that the location of the UE has changed, that is, the eNodeB has switched, and the current GW type is the GW of the user plane control plane separation type, that is, the peer end of the MME connection is GwC, the MME does not immediately perform, for example, a processing flow ( Steps 403-404 in the second step, that is, the process of obtaining the correct GwU address and TEID by creating a session request message or modifying the bearer request message to carry the location information to the GwC.
  • Steps 403-404 in the second step that is, the process of obtaining the correct GwU address and TEID by creating a session request message or modifying the bearer request message to carry the location information to the GwC.
  • the MME first performs the service request process processing in the related art, and sends the currently stored GwU address and TEID to the changed eNodeB, and sends a Pending Transaction to the changed eNodeB; until step 416, the MME again
  • the modify bearer request message carries the eNodeB address and the TEID.
  • the GwC carries the final GwU address and TEID to the MME in the modify bearer response message in step 419.
  • the MME compares the GwU information according to the GW type. If the GwU is changed, the MME changes the bearer modification process to the eNodeB, and delivers the final GwU address and the TEID to the eNodeB.
  • the eNodeB first caches the data, and after receiving the updated GwU address and TEID, completes the bearer modification process and updates the GwU information. And the transmission of the cached data is completed; or the updated GwU address and the TEID are not received within the predetermined time period, and it is confirmed that the GwU is not changed, and the original bearer is used to transmit the cached data.
  • the eNodeB needs to add a cache function.
  • the data that is uplinked to GwU and the data that is forwarded are buffered before the updated GwU address and TEID are received, or before the GwU is confirmed to be unchanged.
  • the MME carries a Pending Transaction in the handover request of step 405.
  • the transaction indication is sent to the eNodeB to inform that there may be a reselection of the GwU and an information update (ie, the GwU address and the TEID are retransmitted), so that the eNodeB can buffer the uplink data to the GwU and the downlink forwarding data when the data transmission fails.
  • the cache time period and mode depend on the actual product implementation, which is not limited here.
  • the corresponding implementation manner may also be:
  • the MME When the MME detects that the location of the UE has changed, that is, the eNodeB has been handed over, and the GW is determined to be the GW of the user plane control plane separation, that is, the peer end of the MME connection is GwC, the MME does not immediately perform, for example, a processing flow (three) Steps 503-504 in the process of obtaining the correct GwU address and TEID by creating a session request message or modifying the bearer request message to carry the location information to the GwC.
  • a processing flow three
  • the MME first performs the handover process in the related art, and sends the currently stored GwU address and TEID to the changed eNodeB, and sends a Pending Transaction to the changed eNodeB; until step 509, the MME further modifies The bearer request message carries the eNodeB address and the TEID.
  • the GwC carries the final GwU address and the TEID to the MME in the modify bearer response message in step 511.
  • the MME compares the GwU information according to the GW type. If the GwU is changed, the MME changes the bearer modification process to the eNodeB, and delivers the final GwU address and the TEID to the eNodeB.
  • the eNodeB first caches the data, and after receiving the updated GwU address and TEID, completes the bearer modification process and updates the GwU information. And the transmission of the cached data is completed; or the updated GwU address and the TEID are not received within the predetermined time period, and it is confirmed that the GwU is not changed, and the original bearer is used to transmit the cached data.
  • the eNodeB needs to add a new cache function.
  • the data that is uplinked to GwU and the data that is forwarded are buffered before the updated GwU address and TEID are received, or before the GwU is confirmed to be unchanged.
  • the MME carries the Pending in the initial context request of the eNodeB in step 505.
  • the Transaction is sent to the eNodeB to inform that there may be a reselection of the GwU and an information update (ie, the GwU address and the TEID are sent again), so that the eNodeB can buffer the data of the uplink to the GwU and the downlink forwarding data when the data transmission fails.
  • the cache time period and mode depend on the actual product implementation, which is not limited here.
  • the processing flows (1) and (2), the processing flows (1) and (3), the processing flows (1) and (4), and the processing flows (1) and (5) constitute the two scenarios respectively.
  • the four processing flows of the two embodiments A method for supporting the correct and reliable transmission of data streams in a scenario where the user location changes in the GW control plane and the user plane separation architecture is described. The method is also applicable to scene processing of other UE location changes. And the processing of data transmission in a communication architecture where control and user plane functions are separated.
  • Embodiment 2 A device for updating gateway information, which is set in the MME, as shown in FIG. 7, includes:
  • the type obtaining module 71 is configured to acquire a gateway GW type.
  • the requesting module 72 is configured to send a create session request message or modify a bearer request message to the gateway control if the acquired GW type is a GW separated from the user plane and the control plane when the evolved Node B eNodeB of the user equipment UE is changed.
  • the plane entity GwC carries the location information of the UE in the create session request message or the modify bearer request message;
  • the gateway information obtaining module 73 is configured to obtain a gateway user plane entity GwU address and a tunnel endpoint identifier TEID from the create session response message or the modify bearer response message returned by the GwC.
  • the location information includes a tracking area identifier TAI and user location information ECGI.
  • the requesting module is further configured to carry a location change indication of the UE in the create session request message or the modify bearer request message.
  • the manner in which the requesting module learns that the eNodeB of the UE is changed includes: receiving one or more of the following messages: an attach request, a tracking area update request, a service request, a handover request, and a forward relocation request.
  • the acquiring the GW type by the type obtaining module includes:
  • the type obtaining module acquires the GW type according to the GW type or the control plane user plane separation identifier carried in the Create Session Response message or the Modify Bearer Response message returned by the serving gateway S-GW or the GwC.
  • the type obtaining module acquiring the gateway GW type further includes: determining, by the type obtaining module, that the GW type and the control plane user plane separation identifier are not carried in the create session response message or the modify bearer response message,
  • the acquired GW type may be a GW in which the user plane and the control plane are unified.
  • the type obtaining module may be further configured to send a session creation request message or modify the bearer to the S-GW or the GwC in the process flow that the UE is attached to the network before acquiring the gateway GW type.
  • Request message carrying a GW type request.
  • the device further includes:
  • the sending module is configured to send the GwU address and the TEID acquired by the gateway information acquiring module to the changed eNodeB when the GwU address and the TEID are not sent to the changed eNodeB.
  • the device further includes:
  • the sending module is configured to determine, when the GwU address and the TEID have been sent to the changed eNodeB, whether the GwU address and the TEID acquired by the gateway information acquiring module are the same as those sent to the changed eNodeB, if different And sending the GwU address and the TEID acquired by the gateway information acquiring module to the changed eNodeB.
  • the sending module may be further configured to: in the handover request or the initial context request of the changed eNodeB, carry a pending transaction indication, where the pending transaction indication is used to notify the changed eNodeB to Before the GwU address and the TEID are received, or before the GwU is confirmed to be changed, the data that is uplinked to the GwU and the data that is forwarded are buffered.
  • a computer readable storage medium storing computer executable instructions for performing the method of the first embodiment.
  • the MME when the GW control plane and the user plane are separated, the MME can learn the correct GwU address and the tunnel endpoint identifier, and further inform the eNodeB, so as to ensure that the data flow can be correctly and reliably transmitted when the GwU is changed. .

Landscapes

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

Abstract

一种网关信息更新方法及装置；所述方法包括：移动管理单元MME获取网关GW类型；所述MME当获知用户设备UE的演进的节点B eNodeB改变时，如果所获取的GW类型为用户面和控制面分离的GW，则发送创建会话请求消息或修改承载请求消息给网关控制面实体GwC，在所述创建会话请求消息或修改承载请求消息中携带所述UE的位置信息；所述MME从所述GwC返回的创建会话响应消息或修改承载响应消息中获取网关用户面实体GwU地址和隧道端点标识TEID。

Description

一种网关信息更新的方法及装置 技术领域
本文涉及但不限于通信领域，尤其涉及一种网关信息更新的方法及装置。
背景技术
图1为3GPP(the 3rd Generation Partnership Project，第三代合作伙伴项目)的EPS(Evolved Packet System，演进的分组系统)的结构示意图，如图1所示，EPS包括E-UTRAN(Evolved Universal Terrestrial Radio Access Network，演进的通用移动通信系统陆地无线接入网)、MME(Mobility Management Entity，移动管理单元)、S-GW(Serving Gateway，服务网关)、PDN GW或P-GW(Packet Data Network Gateway，分组数据网络网关)、HSS(Home Subscriber Server，归属用户服务器)、PCRF(Policy and Charging Rules Function，策略和计费规则功能实体)及其它支撑节点组成。
其中，MME与E-UTRAN通过S1-MME接口相连，用于移动性管理、非接入层信令的处理和用户移动管理上下文的管理等控制面相关工作；S-GW是与E-UTRAN通过S1-U接口相连的接入网关设备，在E-UTRAN与P-GW之间转发数据，并且用于对寻呼等待数据进行缓存；P-GW则是EPS与PDN(Packet Data Network Gateway，分组数据网)的边界网关，用于PDN的接入及在EPS与PDN间转发数据等功能。PCRF负责策略决策和计费规则的制定，与operator’s IP services(运营商的IP服务实体交互)，提供基于业务数据流的门控、服务质量控制及计费规则给GW(Gateway，网关)，在承载面执行PCRF所制定的策略和计费规则。在承载建立时，GW按照PCRF发送的规则进行QoS(Quality of Service，服务质量)授权和门控控制。根据PCRF发送的计费规则，执行相应的业务数据流计费操作，计费既可以是在线计费，也可以是离线计费。如果是在线计费，则需要和OCS(Online Charging System，在线计费系统)一起进行信用管理。OFCS(Offline Charging System，离线计费则和离线计费系统)之间交换相关的计费信息。GW与PCRF之间的接口是Gx接口，与OCS之间的接口是Gy接口，与OFCS之间的接口是Gz接口。
3GPP中，UE(User Equipment，用户设备)通过APN(Access Point Name，接入点名称)可以找到对应PDN，为访问PDN网络会建立一个IP-CAN(IP Connectivity Access Network，IP连接接入网)会话的PDN连接。
随着需求增长，EPS网关逐步产生了一些约束。用户数据流处理集中在PDN出口网关，造成网关设备功能繁杂，可扩展性差。网关的控制面与转发面高度耦合，不利于核心网平滑演进。转发面扩容需求频度高于控制面，紧耦合导致控制面转发面同步扩容，设备更新周期短导致复合成本增加。网络层数据转发难以识别用户、业务特征，仅能根据上层传递的QoS转发，导致网络资源利用低效，难以依据用户和业务特性对数据流进行精细控制。此外，大量策略需要手工配置，导致管理复杂度增加，运营成本居高不下。因此，需要将分组域网关中的控制功能与转发功能进一步分离，以适应网络发展和市场应用的需求。
图2是本文所基于的非漫游场景下GW控制面和用户面分离的架构。该架构将原先的EPS架构中的S-GW/P-GW拆分成了GwC(Gateway Controller，网关控制面实体)和GwU(Gateway User，网关用户面实体)两类功能网元。GwC负责S/P-GW的控制面功能，包括负荷分担、GwU的选择、IP地址和隧道标识的分配、策略和计费控制等功能。GwU包括SGwU(Serving Gateway User，服务网关用户面实体)和PGwU(Packet Data Network Gateway User，分组数据网络网关用户面实体)，分别对应S-GW和P-GW的用户面，负责S/P-GW的用户面相关功能，包括数据流识别和深度包解析、QoS处理和承载绑定，下行寻呼数据的缓存等功能。对接的用户面和控制面接口分别对应到GwC和SGwU/PGwU上，其余相应接口功能对照原EPS架构。
GW控制面和用户面分离之后，解决了EPS网关存在的诸多上述问题，但同时也引入了新的技术问题。例如，导致相关技术中的切换机制在部分场景下不能支持数据流的正确可靠的传输。
相关技术中，MME根据用户位置和签约信息等进行S-GW的选择。当用户位置发生移动引发切换和跟踪区更新流程时，MME判断是否需要进行S-GW的重选，并进行S-GW选择和上下行数据传送路径的信息更新。若判断需要进行S-GW的重选，则根据更新后的位置信息和签约信息重新选择合 适的S-GW，并将新选择的S-GW上行用户面地址和隧道标识等信息发送给eNodeB(Evolved Node B，演进型节点B)，更新上行数据传送路径信息，确保上行数据的正确传送。并将新的eNodeB信息，例如将eNodeB下行用户面地址和隧道标识发送给S-GW，更新下行数据传送路径信息，保证下行数据的正确传送。若不需要进行S-GW的重选，则将当前的S-GW的上行用户面地址和隧道标识等信息发送给新的eNodeB，并将新的eNodeB下行用户面地址和隧道标识传送给当前的S-GW。进行上下行数据通道的重建。切换流程中，MME是否变更可参照相关技术中的机制处理，此处不做展开描述。
当S-GW控制和用户面功能分离后，MME根据相关技术中的机制进行的GW选择实际是GwC的选择，由GwC负责在其对应的GwU组中进行GwU的选择和管理。则根据如上所述机制，在GwC不需要切换但GwU会重选的场景下则无法实现数据的正确转发。例如，基于S1接口的切换流程。MME收到原eNodeB的切换请求消息后，MME判断GwC不需要变更，将会将当前的GwU地址和隧道标识下发给新的eNodeB，则新的eNodeB获取到的不一定是最终的GwU地址和隧道标识，若GwU进行了重选，则上下行数据通道建立错误。则上行数据到达eNodeB后会往老的GwU传送，可能导致无法和GwU连接或是GwU收到后丢弃，导致无法正确上传。无法保证业务的连续性和数据的完整性。
因此，GW控制面和用户面分离之后，相关技术中的切换机制在部分场景下不能支持数据流的正确可靠的传输，无法保证业务的连续性和完整性。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提供一种网关信息更新的方法及装置，在GW控制面和用户面分离的架构中能支持数据流正确可靠传输。
本发明实施例采用如下技术方案。
一种网关信息更新方法，包括：
移动管理单元MME获取网关GW类型；
所述MME当获知用户设备UE的演进的节点B eNodeB改变时，如果所获取的GW类型为用户面和控制面分离的GW，则发送创建会话请求消息或修改承载请求消息给网关控制面实体GwC，在所述创建会话请求消息或修改承载请求消息中携带所述UE的位置信息；
所述MME从所述GwC返回的创建会话响应消息或修改承载响应消息中获取网关用户面实体GwU地址和隧道端点标识TEID。
可选地，所述位置信息包括跟踪区标识TAI和用户位置信息ECGI。
可选地，所述方法还包括：
在所述创建会话请求消息或修改承载请求消息中携带所述UE的位置变更指示。
可选地，所述MME获知UE的eNodeB改变的方式包括：接收到以下一种或多种消息：附着请求，跟踪区更新请求，业务请求，切换请求，前转重定位请求。
可选地，所述MME获取网关GW类型包括：
所述MME根据服务网关S-GW或GwC返回的创建会话响应消息或修改承载响应消息中携带的GW类型或控制面用户面分离标识，获取GW类型。
可选地，所述MME获取网关GW类型还包括：当所述创建会话响应消息或修改承载响应消息中未携带GW类型及控制面用户面分离标识时，所述MME确定所获取的GW类型为用户面和控制面合一的GW。
可选地，所述MME获取网关GW类型前还包括：
在所述UE附着到网络的处理流程中，所述MME给S-GW或所述GwC发送创建会话请求消息或修改承载请求消息，携带GW类型请求。
可选地，所述MME从所述GwC返回的创建会话响应消息或修改承载响应消息中获取GwU地址和TEID后还包括：
所述MME如果未向变更后的eNodeB发送过GwU地址和TEID，则发送所获取的GwU地址和TEID给变更后的eNodeB。
可选地，所述MME从所述GwC返回的创建会话响应消息或修改承载响应消息中获取GwU地址和TEID后还包括：
所述MME如果已向变更后的eNodeB发送过GwU地址和TEID，则判断所获取的GwU地址和TEID与发送给所述变更后的eNodeB的是否相同，如果不同则发送所获取的GwU地址和TEID给所述变更后的eNodeB。
可选地，所述的方法还包括：
所述MME在给变更后的eNodeB的切换请求或初始上下文请求中，携带待定事务指示，所述待定事务指示用于通知所述变更后的eNodeB在再次收到GwU地址和TEID前、或者，确认GwU不变更前，缓存上行到GwU的数据和下行转发的数据。
一种网关信息更新装置，设置于移动管理单元MME，包括：
类型获取模块，设置成获取网关GW类型；
请求模块，设置成当获知用户设备UE的演进的节点B eNodeB改变时，如果所获取的GW类型为用户面和控制面分离的GW，则发送创建会话请求消息或修改承载请求消息给网关控制面实体GwC，在所述创建会话请求消息或修改承载请求消息中携带所述UE的位置信息；
网关信息获取模块，设置成从所述GwC返回的创建会话响应消息或修改承载响应消息中获取网关用户面实体GwU地址和隧道端点标识TEID。
可选地，所述位置信息包括跟踪区标识TAI和用户位置信息ECGI。
可选地，所述请求模块还设置成在所述创建会话请求消息或修改承载请求消息中携带所述UE的位置变更指示。
可选地，所述请求模块获知UE的eNodeB改变的方式包括：接收到以下一种或多种消息：附着请求，跟踪区更新请求，业务请求，切换请求，前转重定位请求。
可选地，所述类型获取模块获取网关GW类型包括：
所述类型获取模块根据服务网关S-GW或GwC返回的创建会话响应消息 或修改承载响应消息中携带的GW类型或控制面用户面分离标识，获取GW类型。
可选地，所述类型获取模块获取网关GW类型还包括：当所述创建会话响应消息或修改承载响应消息中未携带GW类型及控制面用户面分离标识时，确定所获取的GW类型为用户面和控制面合一的GW。
可选地，所述类型获取模块还设置成在获取网关GW类型前，在所述UE附着到网络的处理流程中，给S-GW或所述GwC发送创建会话请求消息或修改承载请求消息，携带GW类型请求。
可选地，任一项所述的装置还包括：
发送模块，设置成在未向变更后的eNodeB发送过GwU地址和TEID时，发送所述网关信息获取模块所获取的GwU地址和TEID给变更后的eNodeB。
可选地，所述的装置还包括：
发送模块，设置成在已向变更后的eNodeB发送过GwU地址和TEID时，判断所述网关信息获取模块所获取的GwU地址和TEID与发送给所述变更后的eNodeB的是否相同，如果不同则发送所述网关信息获取模块所获取的GwU地址和TEID给所述变更后的eNodeB。
可选地，所述发送模块还设置成在给变更后的eNodeB的切换请求或初始上下文请求中，携带待定事务指示，所述待定事务指示用于通知所述变更后的eNodeB在再次收到GwU地址和TEID前、或者，确认GwU不变更前，缓存上行到GwU的数据和下行转发的数据。
一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述方法。
本发明实施例能够在GW控制面和用户面分离的情况下，使MME获知正确的GwU地址及隧道端点标识，并进而告知eNodeB，从而保证在GwU有更改的情况下数据流还是能够正确可靠传输。
在阅读并理解了附图和详细描述后，可以明白其它方面。
附图概述
图1为3GPP的演进分组系统的结构示意图；
图2为非漫游场景下GW控制面和用户面分离的架构示意图；
图3为实施例一的网关信息更新方法的流程示意图；
图4为附着流程中GwC告知GW类型或GW控制用户面分离指示的示意图；
图5为基于S1接口的切换流程中，建立正确的上行数据通道示意图；
图6为业务请求流程中，建立正确的上行数据通道示意图；
图7为实施例二的网关信息更新装置的示意图。
本发明的实施方式
需要说明的是，如果不冲突，本发明实施例以及实施例中的特征可以相互结合。另外，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
实施例一、一种网关信息更新方法，如图3所示，包括步骤S110～S130：
S110、MME获取网关GW类型；
S120、所述MME当获知UE的eNodeB改变时，如果所获取的GW类型为用户面和控制面分离的GW，则发送创建会话请求消息或修改承载请求消息给GwC，在所述创建会话请求消息或修改承载请求消息中携带所述UE的位置信息；所述位置信息可以但不限于至少包括TAI(Tracking Area Identity，跟踪区标识)和ECGI(User Location Information，用户位置信息)。
S130、所述MME从所述GwC返回的创建会话响应消息或修改承载响应消息中获取GwU地址和TEID(Tunnel Endpoint Identifier，隧道端点标识)；其中，所述TEID可以为一个或多个。
本实施例中，所述GwC在创建会话响应消息或修改承载响应消息中携带的GwU地址和TEID是当前正确的GwU地址和TEID；GwC可以根据所述位置信息判断是否要进行GwU重选，如果不用重选则返回原有的GwU地址 和TEID，如果要重选则选择GwU后返回变更后的GwU地址和TEID。
本实施例中，所述UE的eNodeB改变的原因可以但不限于包括：所述UE的位置发生改变。
所述UE的位置发生改变的判断标准可以是：所述UE当前所在的eNodeB发生改变，即所述UE前后eNodeB的ID(标识)不同。
可选地，所述方法还可以包括：
在所述创建会话请求消息或修改承载请求消息中携带所述UE的位置变更指示。可选地，所述MME获知UE的eNodeB改变的方式可以但不限于包括：接收到以下一种或多种消息：附着请求，跟踪区更新请求，业务请求，切换请求，前转重定位请求。
可选地，步骤S110包括：
所述MME根据S-GW或GwC返回的创建会话响应消息或修改承载响应消息中携带的GW类型或控制面用户面分离标识，获知对端的GW类型；所述GW类型包括用户面和控制面分离的GW，或，用户面和控制面合一的GW；当携带控制面用户面分离标识时，所述GW类型为用户面和控制面分离的GW。
本可选方式中，GW类型为用户面和控制面分离的GW时，则MME连接的对端为GW控制面功能实体。
本可选方式中，所述S110前还可以包括：
在所述UE附着到网络的处理流程中，所述MME给S-GW或所述GwC发送创建会话请求消息或修改承载请求消息，携带GW类型请求。
本可选方式中，当所述创建会话响应消息或修改承载响应消息中缺省GW类型标识或控制面用户面分离标识时，可以默认为GW类型是用户面和控制面合一的GW；即所述步骤S110还可以包括：当所述创建会话响应消息或修改承载响应消息中未携带GW类型及控制面用户面分离标识时，所述MME所获取的GW类型为用户面和控制面合一的GW。
可选地，所述步骤S130后还可以包括：
所述MME如果未向变更后的eNodeB发送过GwU地址和TEID，则发 送所获取的GwU地址和TEID给变更后的eNodeB。
可见，若GwU发生了变更，则本可选方案中发送的GwU地址和TEID为变更后的GwU地址和TEID。
可选地，所述步骤S130后还可以包括：
所述MME如果已向变更后的eNodeB发送过GwU地址和TEID，则判断所获取的GwU地址和TEID与发送给所述变更后的eNodeB的是否相同，如果不同则发送所获取的GwU地址和TEID给所述变更后的eNodeB。
本可选方案中，所述MME获知eNodeB改变后，先根据相关技术中的流程发送GwU地址和TEID给变更后的eNodeB；之后再发送位置信息给GwC；如果MME发现GwC返回的GwU地址和TEID与之前发送给变更后的eNodeB的不同，则MME再次发送GwU地址和TEID给变更后的eNodeB；如果相同则可以不再发送；在其它可选方案中也可以设置成无论是否相同，都发送所获取的GwU地址和TEID给变更后的eNodeB。
本可选方案中，所述方法还可以包括：
所述MME在给变更后的eNodeB的切换请求或初始上下文请求中，携带Pending Transaction(待定事务指示)，所述Pending Transaction用于通知所述变更后的eNodeB在再次收到GwU地址和TEID前、或者，确认GwU不变更前，缓存上行到GwU的数据和下行转发的数据。
本可选方案中，所述Pending Transaction的作用相当于通知所述变更后的eNodeB等待确认GwU是否重选，如果再次收到MME发送的GwU地址和TEID则确认GwU重选，用MME再次发送的GwU地址和TEID替代MME第一次发送的GwU地址和TEID，进行上行数据的传输；如果eNodeB在预定时长内未收到MME再次发送的GwU地址和TEID则确认GwU不变更，使用MME第一次发送的GwU地址和TEID进行上行数据的传输。
本可选方案中，eNodeB新增缓存功能。eNodeB在再次收到GwU地址和TEID前、或者，确认GwU不变更之前，缓存上行到GwU的数据和下行转发的数据。
在其它可选方案中，也可以采取如下方案：
MME获知eNodeB切换后，先根据相关技术中的流程发送GwU地址和TEID给变更后的eNodeB；之后再发送位置信息给GwC；无论从GwC所获取的GwU地址和TEID与发送给所述变更后的eNodeB的是否相同，都再次发送所获取的GwU地址和TEID给所述变更后的eNodeB；
所述Pending Transaction用于通知所述变更后的eNodeB在再次收到GwU地址和TEID前，对上行到GwU的数据和下行转发数据的进行缓存；
所述变更后的eNodeB缓存上行到GwU的数据和下行转发的数据，直到第二次从MME收到GwU地址和TEID，采用第二次收到的GwU地址和TEID进行上行数据发送。
实施示例一
处理流程(一)
以下为在UE附着到网络的处理流程中，SGW/GwC给MME发送Create Session Response(创建会话响应)消息时，消息中携带GW类型标识或控制面用户面分离标识，让MME感知对端连接的GW类型。可选地，所述创建会话响应消息中缺省GW类型标识或控制面用户面分离标识时，默认GW类型为用户面和控制面合一的GW。所述GW类型包括：用户面和控制面分离的GW(即：GW分设)，或用户面和控制面合一的GW(即：GW合设)。其中，当GW类型为用户面和控制面分离的GW时，则MME连接的对端为GW控制面功能实体。可选地，MME给SGW/GwC发送的创建会话请求消息中携带GW类型请求。
如图4所示，处理流程(一)包括如下步骤301～317：
步骤301、UE向EPS网络发起附着操作，网络完成对UE的认证授权。过程如以下步骤301-1～301-6的描述：
301-1、UE发送附着请求消息给eNodeB，消息包含：用户标识，上次访问的跟踪区，UE的核心网络能力，附着类型，NAS(Non-access stratum，非接入层)序列号，PDN类型等信息。
301-2、eNodeB根据RRC(Radio Resource Control，无线资源控制)参 数和选择的网络，或MME选择功能，选择MME。然后eNodeB将附着消息和UE所在小区的TAI和ECGI标识一起转发给新的MME。
301-3、如果UE自从上次去附着后MME发生了变化，当前的新的MME获取旧的MME地址，并发送身份标识请求消息到旧MME请求IMSI(International Mobile Subscriber Identification Number，国际移动用户识别码)和移动性上下文。
301-4、如果UE在新和旧MME中都不能被识别，则新MME发送标识请求消息给UE请求IMSI。UE使用包含IMSI的标识响应消息通知网络。
301-5a、如果网络中没有UE上下文存在，或者如果附着请求消息没有完整性保护或加密，或者如果完整性检查失败，则认证过程和NAS安全上下建立过程必须进行。如果网络中存在UE上下文、且附着请求消息有完整性保护或加密，完整性检查成功，则本步骤可选。如果NAS安全算法改变，则该步骤只执行NAS安全上下文建立过程。认证和NAS安全上下文建立过程按照安全功能章节的定义进行。在该步骤之后，所有NAS消息将受到MME指示的NAS安全功能保护。
301-5b、从UE获取移动设备标识IMEI。IMEI标识必须采用加密方式传输，除非是在紧急附着情况下且不能被认证时。为了最小化信令的迟延，移动设备标识获取可以合并在步骤301-5a的NAS安全上下文建立过程中。MME发送移动设备标识检测请求给EIR(Equipment Identity Register，设备标识寄存器)，EIR将检测的结果通过移动设备标识检测应答消息响应。MME根据结果确定是否继续附着过程或拒绝UE。
301-6、如果UE在附着请求消息中设置了加密选项传输标记，则本步骤可以从UE获取加密选项。
步骤302、MME根据相关技术中的EPC网络选择GW的机制，进行网关选择，获取SGW和PGW控制面的IP地址。网关类型是否为SGW还是控制面和用户面分离的GW，对MME的GW选择无影响。本示例中，GW类型为控制面和用户面分离的GW，这里SGW控制面IP地址为GwC的IP地址。
步骤303-306为可选步骤，如果网络中有老的上下文信息(例如，MME中存在激活承载上下文)，则MME通过删除会话请求过程删除GW中老的承载上下文信息。
步骤303、MME向GwC发送Delete Session Request(删除会话请求)消息。
步骤304、GwC向PCRF发起IP-CAN会话终止操作。
步骤305、GwC向SGwU和PGwU发送删除流表请求；
步骤306、GwC向MME回复Delete Session Response(删除会话响应)消息。
步骤307、MME向GwC发送S1-MME接口的Create Session Request(创建会话请求)消息，携带用户标识，APN标识，MME控制面TEID，GwC地址，PGW地址，PDN地址，承载标识，切换指示等信息。其中，切换指示指示了当前是初始附着还是切换附着，GwC根据该指示在后续步骤中有不同的操作，详见后续步骤。其中，PGW地址即为GwC的地址(GW分设时)或者选择的P-GW的地址(GW合设时)。可选地，MME发送给S-GW或GwC的创建会话请求消息中，携带GW类型请求。
步骤308、GwC根据网关选择功能选择正确的GwU，即选择执行转发功能的GwU作为SGwU和PGwU。为GwU分配TEID，包括PGwU的默认承载TEID，SGwU默认承载的UL(Uplink，上行链路)和DL(Downlink，下行链路)的TEID。GwC为该UE的PDN连接分配IP地址或者从外部PDN获取IP地址。
步骤309、当部署了PCRF且创建会话请求消息中切换指示不存在，GwC执行IP-CAN会话建立过程，获取UE的默认PCC(Policy and Charging Control，策略计费控制)准则。若存在切换指示，则GwC执行IP-CAN会话修改流程。向PCRF发起Gx接口上的IP-CAN会话建立或修改相关操作，触发相关承载的建立。如果没有部署动态PCC，则GwC采用本地QoS策略。
步骤310、GwC向SGwU下发流表，包括：PGwU的IP地址，TEID等信息。
步骤311、GwC向PGwU下发流表，包括：SGwU的IP地址，TEID，meter(计量)统计等信息。
步骤312、GwC回应Create Session Response(创建会话响应)消息给MME，包含SGwU的IP地址，用户面TEID，控制面TEID，PGwU的IP地址和TEID。以及，消息中携带GW类型标识或控制面用户面分离标识，让MME感知GW类型为用户面和控制面分离的GW(则MME和GwC交互)，或为用户面和控制面合一的GW(则MME和S-GW交互)。本示例中GW类型为用户面和控制面分离的GW。这里，若GwU发生了变更，则所述创建会话响应消息中携带的GwU地址和TEID为变更后的GwU地址和TEID。所述创建会话响应消息中还携带其他EPS网络S1-MME接口定义的相关参数。MME感知并保存GW类型，用于后续UE位置变更eNodB切换后，根据GW类型决策是否要发送位置变更信息给GwC，供GwC决策是否进行GwU重选。
步骤313、接入网信令交互和空口承载建立。eNodeB发送RRC连接重配置消息给UE，其包含EPS RB(Resource Block，资源块)ID和Attach Accept(附加接受)消息。UE发送RRC连接重配置完成消息给eNodeB。eNodeB发送Initial Context Response(初始上下文响应)消息给新的MME，消息包含eNode B的TEID以及eNodeB的地址，用于S1-U接口的下行数据的传送。UE发送Direct Transfer(直接转移)消息给eNodeB，该消息包含Attach Complete(附加完成)消息。eNodeB使用上行NAS传输消息转发Attach Complete消息给新的MME。
步骤314、MME将eNodeB的用户面地址和TEID通过Modify Bearer Request(修改承载请求)消息发送给GW(本示例中即发送给GwC)。
步骤315：GwC向SGwU更新流表，将eNodeB的用户面地址和TEID发送给SGwU。下行数据通道完成，数据可下发到UE。
步骤316：若是切换附着场景，GwC向PGwU更新流表，通知GwUPGwU可以从网络侧发送数据。
步骤317：GwC向MME回复Modify Bearer Response(修改承载响应)消息。
处理流程(二)
以下为源eNodeB与目标eNodeB没有X2接口连接时，发起一个基于S1接口的eNodeB间的切换的流程。MME接收到切换请求消息后，感知到UE的位置发生了变化，即eNodeB发生了切换。本示例中，当前GW类型为用户面控制面分离GW，即MME连接的对端为GwC。则发送创建会话请求消息或修改承载请求消息给GwC，其中携带位置信息。GwC根据MME提供的位置信息，判断GwU是否需要重选并执行。将正确的GwU地址和隧道标识TEID信息返回给MME，并由MME传送给目标eNodeB，建立正确的上行数据传送通道。如图5所示，处理流程(二)包括如下步骤401～423：
步骤401、源eNodeB发送一条Handover Required(切换请求)消息给源MME(若MME发生了改变)。该切换请求消息携带源到目标透明容器、target eNodeB Identity(目标eNodeB标识)、target(目标)TAI，直接转发标记。在透明容器中指示了执行数据转发的承载列表。TAI的目的是便于选择合适的目标MME。
步骤402、若MME发生了改变，则源MME选择目标MME，并发送Forward Relocation Request(前转重定位请求)消息给目标MME，消息中包括MME用户上下文，源到目标透明容器、目标eNodeB标识，目标跟踪区标识等信息。目标TAI用于MME判断是否要进行SGW/GwC重选。MME用户上下文中包括：GW类型标识或控制面用户面分离标识，指示GW类型为用户面控制面分离的GW(则MME和GwC交互)或用户面控制面合一的GW(则MME和S-GW交互)。
步骤403、MME判断是否要进行S-GW/GwC重选(源S-GW是否可以继续为UE服务)，若需要则选择新的S-GW/GwC。如果MME没有重定位则由源MME判断是否要进行S-GW/GwC的重选以及在要重选时进行选择，如果MME已重定位则由目的MME判断是否要进行S-GW/GwC的重选以及在要重选时进行选择。
MME根据GW类型标识或控制面用户面分离标识判断对端的GW类型，本示例中GW为用户面控制面分离的GW，即对端为GwC，如果eNodeB发生了改变(根据eNodeB ID判断)，则目标MME发送创建会话请求消息或 修改承载请求给GwC，消息中包括PGW地址和TEID，TAI，ECGI(其中包括eNodeB的标识)，Serving Network(服务网络)等位置信息，供GwC进行GwU重选的判断和执行。
步骤403a、可选地，若执行了GwU的重选，且GwU用户面地址和TEID由GwU分配，则GwC发送路由信息更新请求获取新的GwU用户面地址和TEID。
步骤404、GwC根据创建会话请求消息或修改承载请求消息中的位置信息，结合GwU选择功能，判断是否要进行GwU的重选，若需要则执行GwU的选择。为GwU分配用于S1-U接口上行数据传送的GwU用户面地址和TEID。GwC发送创建会话响应消息或修改承载响应消息给目标MME，携带所分配的GwU地址和用户面上行TEID。若GwU进行了重选，则该GwU地址为重选后的新GwU地址。
步骤405、目标MME发送Handover Request(切换请求)消息给目标eNodeB，在目标eNodeB创建UE上下文，包含承载信息，安全上下文。消息携带为每个EPS承载分配的用于用户面的GwU地址和上行TEID及EPS承载QoS。
步骤406、目标eNodeB发送一条Handover Request Acknowledge(切换请求应答)消息给目标MME，消息中包含目标eNodeB为S1-U接口上下行分组分配的地址和TEID，以及为接收转发数据分配的地址和TEID。
步骤407、若MME发生了变更，则目标MME发送前转重定位响应消息给源MME，消息中携带eNodeB为接收转发数据分配的地址和TEID，间接转发，消息包含间接转发的的GwU前转地址和TEID。
步骤408、间接转发，目标MME通过发送Create Indirect Data Forwarding Tunnel Request(创建间接数据转发隧道请求)消息给GwC，消息携带用于数据转发的target eNodeB用户面地址和TEID。
步骤409、GwC向SGwU发送路由信息更新消息，携带用于数据转发的目标eNodeB的IP地址和TEID信息。
步骤409a、GwC向PGwU发送路由信息更新消息，携带用于数据转发 的目标eNodeB的IP地址和TEID信息。
步骤410、GwC发送Create Indirect Data Forwarding Tunnel Response(创建间接数据转发隧道响应)消息给目标MME，消息携带GwU用于S1-U接口上行数据前转的地址和TEID。如果GwC不重定位，该MME为源MME。
步骤411-415执行空口切换操作和数据包的间接转发处理：
步骤411、源MME发送一个Handover Command(切换命令)消息到源eNodeB，消息中携带GwU用于数据前转的地址和TEID。源eNodeB使用Target to Source transparent container(目标到源的透明容器)构造Handover Command消息发送给UE。
步骤412、源eNodeB开始从源eNodeB经过GwU到目标eNodeB，间接转发下行链路数据。
步骤413、UE成功地同步到目标小区后，发送Handover Confirm(切换确认)消息到目标eNodeB。来自源eNodeB的下行转发数据被传到UE，而上行数据由目标eNodeB发送到GwU。
步骤414、目标eNodeB发送一条Handover Notify(切换通知)消息给目标MME，消息中携带TAI和ECGI。
步骤415、如果目标MME重定位，则目标MME发送Forward Relocation Complete(转发重定位完成)消息到源MME。
步骤415a、作为响应，源MME可以发送一条Forward Relocation Complete Acknowledge(转发重定位完成应答)消息给目标MME。
步骤416、目标MME发送Modify Bearer Request(修改承载请求)消息给GwC，携带目标eNodeB的用户面地址和TEID，可选地，还可以携带用户位置信息。
步骤417、如果步骤416中上报了用户位置信息，且PCRF签订了该事件信息，则GwC将与PCRF发起IP-CAN会话修改操作，上报事件信息。
步骤418、GwC向SGwU发送路由信息更新消息，携带目标eNodeB的IP地址和TEID信息。
步骤418a、GwC向PGwU发送路由信息更新消息，携带目标eNodeB的 IP地址和TEID信息。
步骤419、GwC发送Modify Bearer Response(修改承载响应)消息给目标MME。GwC在路径转换之后立即在旧路径上发送一个或多个“end marker”分组包以辅助目标eNodeB执行重排序功能。
步骤420、下行数据跑通，源网络侧无线资源释放。
步骤421、源MME发送Delete Indirect Data Forwarding Tunnel Request(删除前转数据通道请求)消息给GwC，释放为间接转发所分配的临时资源。
步骤422、GwC向SGwU发送流表更新请求，删除用于数据转发的流表信息。
步骤423、GwC向源MME返回删除前转数据通道请求响应消息。
处理流程(三)
以下为业务请求流程，即UE在IDLE(空闲)状态下，为上层信令的发送或者活动的承载预留资源而建立一条信令连接的过程。MME接收到业务请求消息后，感知到UE的位置发生了变化，即eNodeB发生了切换。本示例中，GW类型为用户面控制面分离的GW，即MME连接的对端为GwC。MME发送创建会话请求消息或修改承载请求消息给GwC，其中携带位置信息。GwC根据MME提供的位置信息，判断GwU是否需要重选并执行。将正确的GwU地址和隧道标识TEID信息返回给MME，并由MME传送给eNodeB，建立正确的上行数据传送通道。如图6所示，处理流程(三)包括如下步骤501～511：
步骤501、UE通过封装在RRC消息上的NAS消息发送Service Request(业务请求)消息给MME。该消息通过eNodeB前转给MME，该消息被封装在一个S1-AP类型的Initial UE Message(初始UE消息)中发送，初始UE消息携带用户标识和用户位置相关信息，包括TAI和ECGI等。
步骤502、根据网络的需要，可能会执行NAS鉴权和安全激活过程。
步骤503、MME根据GW类型标识或控制面用户面分离标识判断对端的GW类型，本示例中GW类型为用户面控制面分离的GW，即对端是GwC，如果eNodeB发生了改变(根据eNodeB ID判断)，则MME发送创建会话 请求消息或修改承载请求消息给GwC，消息中包括PGW地址和TEID，TAI，ECGI(其中包括eNodeB ID)，Serving Network等位置信息。供GwC进行GwU重选的判断和执行。
步骤503a、可选地，若执行了GwU的重选，且GwU用户面地址和TEID由GwU分配，则GwC发送路由信息更新请求获取新的GwU用户面地址和TEID。
步骤504、GwC根据创建会话请求消息或修改承载请求消息中的位置信息，结合GwU选择功能，判断是否要进行GwU的重选，若需要则执行GwU的选择。可选地，为GwU分配用于S1-U接口上行数据传送的GwU地址和TEID。GwC发送创建会话响应消息或修改承载响应消息给MME，将分配的GwU地址和用户面上行TEID携带给MME。若GwU进行了重选，则该GwU地址为重选后的新GwU地址。
步骤505、MME给eNodeB发送S1-AP类型消息Initial Context Setup Request(初始上下文建立请求)，消息中携带GwU地址和用户面上行TEID，以及承载QoS，安全上下文，MME信令连接标识等信息。
步骤506、eNodeB根据收到的GwU地址和用户面上行TEID以及承载QoS等信息执行无线承载建立过程。并且建立用户面安全上下文。当用户面无线承载建立和服务请求完成并且EPS承载状态在UE与MME之间同步之后，UE将删除没有无线承载的EPS承载。如果一个缺省EPS承载的无线承载没有建立，UE本地去激活与这个缺省承载相关联的所有EPS承载。
步骤507、UE的上行数据通过eNodeB前转到GwU。eNodeB向步骤505中提供的GwU地址和TEID发送上行数据。SGwU将上行数据前转到PGwU。
步骤508、eNodeB发送S1-AP类型消息Initial Context Setup Complete(初始上下文建立完成消息)给MME，消息中携带用于下行数据传送的eNodeB用户面地址和TEID，以及其它承载相关信息。
步骤509、MME发送Modify Bearer Request(修改承载请求)消息给GwC，消息中携带用于下行数据传送的eNodeB用户面地址和TEID，以及其它承载相关信息。
步骤510、GwC向SGwU下发流表，更新路由信息，其中包含eNodeB的用户面IP地址和TEID信息。
步骤510a、GwC向PGwU下发流表，更新路由信息，其中包含eNodeB的用户面IP地址和TEID信息。至此下行数据通道建立，GwU可以通过该通道发送下行数据给UE。
步骤511、GwC向MME回应修改承载响应消息。
处理流程(四)
在处理流程(二)的场景下，相应的实施方式还可以为：
当MME感知到UE的位置发生了变化，即eNodeB发生了切换，且判断当前GW类型为用户面控制面分离类型的GW，即MME连接的对端为GwC时，MME不是立刻执行例如处理流程(二)中的步骤403-404，即：通过创建会话请求消息或修改承载请求消息携带位置信息给GwC，获取到正确的GwU地址和TEID的处理流程。本处理流程中，MME先执行相关技术中的业务请求流程处理，发送当前存储的GwU地址和TEID给变更后的eNodeB，并发送Pending Transaction给所述变更后的eNodeB；直到步骤416，MME再在修改承载请求消息中携带eNodeB地址和TEID。
GwC在步骤419的修改承载响应消息中，携带最终的GwU地址和TEID给MME。MME根据GW类型进行GwU信息的对比，若GwU发生了变更，则触发到eNodeB的承载修改流程，下发最终的GwU地址和TEID给eNodeB。
eNodeB先缓存数据，在收到更新后的GwU地址和TEID后完成承载修改处理，更新GwU信息。并完成缓存数据的发送；或者在预定时长内收不到更新后的GwU地址和TEID，则确认GwU不变更，采用原先的承载发送缓存数据。
可选地，处理流程(四)中，eNodeB需要新增缓存功能。在收到更新的GwU地址和TEID、或者确认GwU不变更之前，缓存上行到GwU的数据和下行转发的数据。
可选地，MME在步骤405的切换请求中，携带Pending Transaction(待 定事务指示)给eNodeB，告知后续可能存在GwU的重选和信息更新(即：再次发送GwU地址和TEID)，便于eNodeB在数据传送失败时对上行到GwU的数据和下行转发数据的缓存。缓存时间周期和方式，取决于实际产品实现，这里不做限定。
处理流程(四)其余的详细流程的处理同(二)中的相应步骤，不做重复描述。
处理流程(五)
在处理流程(三)的场景下，相应的实施方式还可以为：
当MME感知到UE的位置发生了变化，即eNodeB发生了切换，且判断当前GW类型为用户面控制面分离的GW，即MME连接的对端为GwC时，MME不是立刻执行例如处理流程(三)中的步骤503-504，即：通过创建会话请求消息或修改承载请求消息携带位置信息给GwC，获取到正确的GwU地址和TEID的处理流程。本处理流程中，MME先执行相关技术中的切换流程处理，发送当前存储的GwU地址和TEID给变更后的eNodeB，并发送Pending Transaction给所述变更后的eNodeB；直到步骤509，MME再在修改承载请求消息中携带eNodeB地址和TEID。
GwC在步骤511的修改承载响应消息中，携带最终的GwU地址和TEID给MME。MME根据GW类型进行GwU信息的对比，若GwU发生了变更，则触发到eNodeB的承载修改流程，下发最终的GwU地址和TEID给eNodeB。
eNodeB先缓存数据，在收到更新后的GwU地址和TEID后完成承载修改处理，更新GwU信息。并完成缓存数据的发送；或者在预定时长内收不到更新后的GwU地址和TEID，则确认GwU不变更，采用原先的承载发送缓存数据。
可选地，处理流程(五)中，eNodeB需要新增缓存功能。在收到更新的GwU地址和TEID、或者确认GwU不变更之前，缓存上行到GwU的数据和下行转发的数据。
可选地，MME在步骤505给eNodeB的初始上下文请求中，携带Pending  Transaction给eNodeB，告知后续可能存在GwU的重选和信息更新(即：再次发送GwU地址和TEID)，便于eNodeB在数据传送失败时对上行到GwU的数据和下行转发数据的缓存。缓存时间周期和方式，取决于实际产品实现，这里不做限定。
处理流程(五)其余的详细流程的处理同(三)中的相应步骤，不做重复描述。
如上描述，处理流程(一)和(二)，处理流程(一)和(三)，处理流程(一)和(四)，处理流程(一)和(五)，分别构成了两个场景下的两个实施方式的四种处理流程。描述了一种GW控制面和用户面分离架构中用户位置发生改变场景下，能够支持数据流正确可靠传输的方法。该方法还适用于其它UE位置变更的场景处理。以及其它控制和用户面功能分离的通信架构中的数据传输的处理。
实施例二、一种网关信息更新装置，设置于MME，如图7所示，包括：
类型获取模块71，设置成获取网关GW类型；
请求模块72，设置成当获知用户设备UE的演进的节点B eNodeB改变时，如果所获取的GW类型为用户面和控制面分离的GW，则发送创建会话请求消息或修改承载请求消息给网关控制面实体GwC，在所述创建会话请求消息或修改承载请求消息中携带所述UE的位置信息；
网关信息获取模块73，设置成从所述GwC返回的创建会话响应消息或修改承载响应消息中获取网关用户面实体GwU地址和隧道端点标识TEID。
可选地，所述位置信息包括跟踪区标识TAI和用户位置信息ECGI。
可选地，所述请求模块还设置成在所述创建会话请求消息或修改承载请求消息中携带所述UE的位置变更指示。
可选地，所述请求模块获知UE的eNodeB改变的方式包括：接收到以下一种或多种消息：附着请求，跟踪区更新请求，业务请求，切换请求，前转重定位请求。
可选地，所述类型获取模块获取网关GW类型包括：
所述类型获取模块根据服务网关S-GW或GwC返回的创建会话响应消息或修改承载响应消息中携带的GW类型或控制面用户面分离标识，获取GW类型。
本可选方案中，所述类型获取模块获取网关GW类型还包括：所述类型获取模块当所述创建会话响应消息或修改承载响应消息中未携带GW类型及控制面用户面分离标识时，确定所获取的GW类型可以为用户面和控制面合一的GW。
本可选方案中，所述类型获取模块还可以设置成在获取网关GW类型前，在所述UE附着到网络的处理流程中，给S-GW或所述GwC发送创建会话请求消息或修改承载请求消息，携带GW类型请求。
可选地，所述的装置还包括：
发送模块，设置成在未向变更后的eNodeB发送过GwU地址和TEID时，发送所述网关信息获取模块所获取的GwU地址和TEID给变更后的eNodeB。
可选地，所述的装置还包括：
发送模块，设置成在已向变更后的eNodeB发送过GwU地址和TEID时，判断所述网关信息获取模块所获取的GwU地址和TEID与发送给所述变更后的eNodeB的是否相同，如果不同则发送所述网关信息获取模块所获取的GwU地址和TEID给所述变更后的eNodeB。
本可选方案中，所述发送模块还可以设置成在给变更后的eNodeB的切换请求或初始上下文请求中，携带待定事务指示，所述待定事务指示用于通知所述变更后的eNodeB在再次收到GwU地址和TEID前、或者，确认GwU不变更前，缓存上行到GwU的数据和下行转发的数据。
一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行实施例一所述的方法。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序 来指令相关硬件完成，所述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地，上述实施例中的模块/单元可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。本发明实施例不限制于任何特定形式的硬件和软件的结合。
工业实用性
本发明实施例能够在GW控制面和用户面分离的情况下，使MME获知正确的GwU地址及隧道端点标识，并进而告知eNodeB，从而保证在GwU有更改的情况下数据流还是能够正确可靠传输。

Claims (20)

  1. 一种网关信息更新方法，包括：
    移动管理单元MME获取网关GW类型；
    所述MME当获知用户设备UE的演进的节点B eNodeB改变时，如果所获取的GW类型为用户面和控制面分离的GW，则发送创建会话请求消息或修改承载请求消息给网关控制面实体GwC，在所述创建会话请求消息或修改承载请求消息中携带所述UE的位置信息；
    所述MME从所述GwC返回的创建会话响应消息或修改承载响应消息中获取网关用户面实体GwU地址和隧道端点标识TEID。
  2. 如权利要求1所述的方法，其中：
    所述位置信息包括跟踪区标识TAI和用户位置信息ECGI。
  3. 如权利要求1所述的方法，还包括：
    在所述创建会话请求消息或修改承载请求消息中携带所述UE的位置变更指示。
  4. 如权利要求1所述的方法，其中，所述MME获知UE的eNodeB改变的方式包括：接收到以下一种或多种消息：附着请求，跟踪区更新请求，业务请求，切换请求，前转重定位请求。
  5. 如权利要求1所述的方法，其中，所述MME获取网关GW类型包括：
    所述MME根据服务网关S-GW或GwC返回的创建会话响应消息或修改承载响应消息中携带的GW类型或控制面用户面分离标识，获取GW类型。
  6. 如权利要求5所述的方法，其中，所述MME获取网关GW类型还包括：
    当所述创建会话响应消息或修改承载响应消息中未携带GW类型及控制面用户面分离标识时，所述MME确定所获取的GW类型为用户面和控制面合一的GW。
  7. 如权利要求5所述的方法，其中，所述MME获取网关GW类型前还包括：
    在所述UE附着到网络的处理流程中，所述MME给S-GW或所述GwC发送创建会话请求消息或修改承载请求消息，携带GW类型请求。
  8. 如权利要求1～7任一项所述的方法，其中，所述MME从所述GwC返回的创建会话响应消息或修改承载响应消息中获取GwU地址和TEID后还包括：
    所述MME如果未向变更后的eNodeB发送过GwU地址和TEID，则发送所获取的GwU地址和TEID给变更后的eNodeB。
  9. 如权利要求1～7任一项所述的方法，其中，所述MME从所述GwC返回的创建会话响应消息或修改承载响应消息中获取GwU地址和TEID后还包括：
    所述MME如果已向变更后的eNodeB发送过GwU地址和TEID，则判断所获取的GwU地址和TEID与发送给所述变更后的eNodeB的是否相同，如果不同则发送所获取的GwU地址和TEID给所述变更后的eNodeB。
  10. 如权利要求9所述的方法，还包括：
    所述MME在给变更后的eNodeB的切换请求或初始上下文请求中，携带待定事务指示，所述待定事务指示用于通知所述变更后的eNodeB在再次收到GwU地址和TEID前、或者，确认GwU不变更前，缓存上行到GwU的数据和下行转发的数据。
  11. 一种网关信息更新装置，设置于移动管理单元MME，包括：
    类型获取模块，设置成获取网关GW类型；
    请求模块，设置成当获知用户设备UE的演进的节点B eNodeB改变时，如果所获取的GW类型为用户面和控制面分离的GW，则发送创建会话请求消息或修改承载请求消息给网关控制面实体GwC，在所述创建会话请求消息或修改承载请求消息中携带所述UE的位置信息；
    网关信息获取模块，设置成从所述GwC返回的创建会话响应消息或修改承载响应消息中获取网关用户面实体GwU地址和隧道端点标识TEID。
  12. 如权利要求11所述的装置，其中：
    所述位置信息包括跟踪区标识TAI和用户位置信息ECGI。
  13. 如权利要求11所述的装置，其中：
    所述请求模块还设置成在所述创建会话请求消息或修改承载请求消息中携带所述UE的位置变更指示。
  14. 如权利要求11所述的装置，其中，所述请求模块获知UE的eNodeB改变的方式包括：接收到以下一种或多种消息：附着请求，跟踪区更新请求，业务请求，切换请求，前转重定位请求。
  15. 如权利要求11所述的装置，其中，所述类型获取模块获取网关GW类型包括：
    所述类型获取模块根据服务网关S-GW或GwC返回的创建会话响应消息或修改承载响应消息中携带的GW类型或控制面用户面分离标识，获取GW类型。
  16. 如权利要求15所述的装置，其中，所述类型获取模块获取网关GW类型还包括：
    所述类型获取模块当所述创建会话响应消息或修改承载响应消息中未携带GW类型及控制面用户面分离标识时，确定所获取的GW类型为用户面和控制面合一的GW。
  17. 如权利要求15所述的装置，其中：
    所述类型获取模块还设置成在获取网关GW类型前，在所述UE附着到网络的处理流程中，给S-GW或所述GwC发送创建会话请求消息或修改承载请求消息，携带GW类型请求。
  18. 如权利要求11～17任一项所述的装置，还包括：
    发送模块，设置成在未向变更后的eNodeB发送过GwU地址和TEID时，发送所述网关信息获取模块所获取的GwU地址和TEID给变更后的eNodeB。
  19. 如权利要求11～17任一项所述的装置，还包括：
    发送模块，设置成在已向变更后的eNodeB发送过GwU地址和TEID时，判断所述网关信息获取模块所获取的GwU地址和TEID与发送给所述变更后的eNodeB的是否相同，如果不同则发送所述网关信息获取模块所获取的GwU地址和TEID给所述变更后的eNodeB。
  20. 如权利要求19所述的装置，其中：
    所述发送模块还设置成在给变更后的eNodeB的切换请求或初始上下文请求中，携带待定事务指示，所述待定事务指示用于通知所述变更后的eNodeB在再次收到GwU地址和TEID前、或者，确认GwU不变更前，缓存上行到GwU的数据和下行转发的数据。
PCT/CN2016/094213 2015-11-09 2016-08-09 一种网关信息更新的方法及装置 WO2017080266A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510756108.8A CN106686666A (zh) 2015-11-09 2015-11-09 一种网关信息更新的方法及装置
CN201510756108.8 2015-11-09

Publications (1)

Publication Number Publication Date
WO2017080266A1 true WO2017080266A1 (zh) 2017-05-18

Family

ID=58694712

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/094213 WO2017080266A1 (zh) 2015-11-09 2016-08-09 一种网关信息更新的方法及装置

Country Status (2)

Country Link
CN (1) CN106686666A (zh)
WO (1) WO2017080266A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111064784A (zh) * 2019-12-12 2020-04-24 天翼物联科技有限公司 物联网会话实现方法、终端、平台、系统和存储介质
CN111182591A (zh) * 2018-11-12 2020-05-19 华为技术有限公司 网络切换的方法和装置

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109428852B (zh) * 2017-07-18 2023-09-15 中兴通讯股份有限公司 通信隧道端点地址分离方法、终端、ePDG及存储介质
CN109548038B (zh) 2017-08-10 2020-12-29 中兴通讯股份有限公司 一种连接方法、配置更新方法、控制面设备和用户面设备
CN114697989A (zh) * 2020-12-31 2022-07-01 大唐移动通信设备有限公司 一种通信传输的方法、设备及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101047982A (zh) * 2006-04-02 2007-10-03 华为技术有限公司 一种网关迁移的方法
US20140092869A1 (en) * 2012-10-02 2014-04-03 Htc Corporation Local Gateway Reselection
CN104661205A (zh) * 2013-11-22 2015-05-27 中兴通讯股份有限公司 一种网关更新信息通知方法及控制器
CN104969653A (zh) * 2013-04-07 2015-10-07 华为技术有限公司 无线回程链路的建立方法和设备

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2291951B1 (en) * 2008-04-29 2018-03-28 Nokia Solutions and Networks Oy Decentralizing core network functionalities
KR101388315B1 (ko) * 2009-11-02 2014-04-29 엘지전자 주식회사 로컬 ｉｐ 접속을 위한 상관 ｉｄ
US9060374B2 (en) * 2010-04-27 2015-06-16 Nec Corporation Communication method, mobile network system and device
US9473971B2 (en) * 2012-03-21 2016-10-18 Lg Electronics Inc. Method and apparatus for managing QoS group in wireless communication system
US9516577B2 (en) * 2012-07-20 2016-12-06 Nec Corporation Dynamic activation of ANDSF policies
CN103945559B (zh) * 2013-01-18 2019-02-15 中兴通讯股份有限公司 网络接入系统及方法
US9882733B2 (en) * 2013-06-14 2018-01-30 Telefonaktiebolaget Lm Ericsson (Publ) Migrating eMBMS into a cloud computing system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101047982A (zh) * 2006-04-02 2007-10-03 华为技术有限公司 一种网关迁移的方法
US20140092869A1 (en) * 2012-10-02 2014-04-03 Htc Corporation Local Gateway Reselection
CN104969653A (zh) * 2013-04-07 2015-10-07 华为技术有限公司 无线回程链路的建立方法和设备
CN104661205A (zh) * 2013-11-22 2015-05-27 中兴通讯股份有限公司 一种网关更新信息通知方法及控制器

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111182591A (zh) * 2018-11-12 2020-05-19 华为技术有限公司 网络切换的方法和装置
CN111182591B (zh) * 2018-11-12 2021-07-16 华为技术有限公司 网络切换的方法和装置
US11751105B2 (en) 2018-11-12 2023-09-05 Huawei Technologies Co., Ltd. Network handover method and apparatus
CN111064784A (zh) * 2019-12-12 2020-04-24 天翼物联科技有限公司 物联网会话实现方法、终端、平台、系统和存储介质

Also Published As

Publication number Publication date
CN106686666A (zh) 2017-05-17

Similar Documents

Publication Publication Date Title
JP6985455B2 (ja) 無線通信システムにおけるネットワーク間の相互連動方法及びそのための装置
US10674420B2 (en) Method, apparatus, and system for routing user plane data in mobile network
EP3516922B1 (en) Method and apparatus for establishing dual-connectivity to transmit data in new radio communication architecture
US10104541B2 (en) Method and apparatus for establishing user plane bearer
CN104812008B (zh) 一种小小区系统中支持ue移动的方法及装置
US11477633B2 (en) Method and apparatus for managing packet data network connection on basis of local area in wireless communication system
EP3100516B1 (en) Efficient session management method and apparatus guaranteeing terminal mobility
US10660006B2 (en) Bearer handover control device and control method
WO2017080266A1 (zh) 一种网关信息更新的方法及装置
CN114390618B (zh) 一种支持切换的方法
US11044006B2 (en) Method enabling an RN to support multiple wireless access systems
WO2017162121A1 (zh) 用户面服务网关选择方法及系统
KR20160042027A (ko) 작은 셀 아키텍처에서 로컬 브레이크아웃을 지원하기 위한 방법, 시스템 및 장치
WO2017054611A1 (zh) 用户设备初始附着方法及系统
WO2011006404A1 (zh) 本地ip访问连接建立的实现方法及系统
KR102446520B1 (ko) 라우팅 선택 방법, 장치, 디바이스 및 시스템 및 저장 매체
WO2017080261A1 (zh) 一种网关信息更新方法及装置
WO2012126319A1 (zh) 一种本地访问业务的切换方法及系统
WO2010121421A1 (zh) 一种实现本地ip接入的方法、系统及网络设备
WO2015054850A1 (zh) 通信方法、通信装置及通信系统
WO2013000344A1 (zh) 切换过程中本地访问连接的处理方法及装置
WO2018001247A1 (zh) 控制用户设备的方法、装置及系统和网关
WO2015054847A1 (zh) 通信方法、本地网关、基站、mme和系统
WO2012129997A1 (zh) 本地访问连接的处理方法及装置

Legal Events

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

Ref document number: 16863444

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

Country of ref document: EP

Kind code of ref document: A1