[go: up one dir, main page]

WO2012041073A1 - 一种实现流迁移的方法及系统 - Google Patents

一种实现流迁移的方法及系统 Download PDF

Info

Publication number
WO2012041073A1
WO2012041073A1 PCT/CN2011/075400 CN2011075400W WO2012041073A1 WO 2012041073 A1 WO2012041073 A1 WO 2012041073A1 CN 2011075400 W CN2011075400 W CN 2011075400W WO 2012041073 A1 WO2012041073 A1 WO 2012041073A1
Authority
WO
WIPO (PCT)
Prior art keywords
access network
3gpp access
terminal
message
isgw
Prior art date
Application number
PCT/CN2011/075400
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 WO2012041073A1 publication Critical patent/WO2012041073A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H04W12/047—Key management, e.g. using generic bootstrapping architecture [GBA] without using a trusted network node as an anchor
    • H04W12/0471—Key exchange
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H04W80/045—Network layer protocols, e.g. mobile IP [Internet Protocol] involving different protocol versions, e.g. MIPv4 and MIPv6

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and system for implementing stream migration. Background technique
  • the EPC system supports the access of the Evolved Universal Terrestrial Radio Access Network (E-UTRAN); the EPC system supports access to the Non-3GPP access network, such as a wireless local area network (WLAN). )Access Network.
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • WLAN wireless local area network
  • FIG 1 is a schematic diagram of an evolved packet system (Evolved Packet System, EPS).
  • EPS evolved Packet System
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • P-GW/PGW Packet Data Network GateWay
  • HSS Home Subscriber Server
  • AAA Server 3GPP Authentication and Authorization Accounting Server
  • ePDG Evolved Packet Data Gateway
  • PCRF Policy and Charging Rules Function
  • the MME is responsible for mobility management, processing of non-access stratum (NAS, Non-Access Stratum) signaling, and user mobility.
  • Control plane related management such as management context
  • S-GW is an access gateway device connected to E-UTRAN for forwarding data between E-UTRAN and PDN GW
  • P-GW is 3GPP EPS and public land mobile network (Home Public Land Mobile Network, HPLMN) provides a border gateway for IP services, responsible for accessing IP services, and forwarding data between EPS and IP service networks.
  • HPLMN Home Public Land Mobile Network
  • the untrusted non-3GPP access network (Untmsted Non-3GPP Access), that is, there is no trust relationship between the 3GPP network and the non-3GPP access system, the non-3GPP access system must first access the ePDG of the 3GPP network, and then pass the S2b.
  • the interface is connected to the P-GW.
  • IPsec IP Security
  • the S2b interface uses the Proxy Mobile Internet Protocol version 6, ⁇ or the GPRS Tunnel Protocol (GTP) protocol.
  • FIG. 2 is a schematic diagram of a control plane protocol stack of the prior art scheme 1, where L2/L1 (Layer 1/Layer 2, Layer 1/Layer 2) is a data link layer and a physical layer, and IPv4/v6 is an IP layer, and the Internet is dense.
  • the second version of the key exchange (Internet Key Exchange Version 2, IKEv2) is used to negotiate keys and establish an IPSec tunnel between the terminal UE and the ePDG.
  • FIG. 3 is a schematic diagram of a process in which a terminal UE accesses an EPC through an ePDG in the prior art 1.
  • the process shown in FIG. 3 includes the following steps:
  • Step 301 The ePDG interacts with the terminal UE to perform IKEv2 signaling, establishes a security association, and performs authentication between the EPC network and the terminal UE.
  • Step 301 there is an interaction between the ePDG and the 3GPP AAA/HSS.
  • Step 302 The ePDG initiates a PDN connection establishment request message to the P-GW, where the message is The body content is a session request, and after receiving the message, the P-GW sends a setup session reply, which includes an address assigned to the terminal UE.
  • the interaction signaling of step 302 is a proxy binding update and a proxy binding acknowledgement ( Proxy binding update/PBU and Proxy binding Ack/PBA).
  • Step 303 The ePDG sends an IKEv2 message to notify the terminal UE of the IP address allocated by the P-GW, and completes the establishment of the IPSec tunnel.
  • IPv4/v6 is an IP layer.
  • the IKEv2 protocol is used to negotiate a key between the terminal UE and the ePDG and establish an IPSec. tunnel.
  • FIG. 5 is a flowchart of a method for a user to access a network in the prior art scheme 2, where the process shown in FIG. 5 includes the following steps:
  • Step 501 to step 503 Same as step 301 to step 303.
  • Step 504 The terminal UE initiates a SIP registration request.
  • Step 505 The ePDG replies with 200 OK to the terminal UE, and completes the SIP registration of the terminal UE.
  • Step 506 The terminal UE sends an invitation (INVITE) to the ePDG.
  • the terminal UE may carry information to the ePDG and reach the P-GW through the next step, for example, carrying authentication information, such as a username/password.
  • Step 507 The ePDG sends a bearer resource command to the P-GW, where the message includes the information sent by the terminal UE in step 506.
  • Step 508 When the P-GW receives the information sent by the terminal UE, the P-GW configures according to its own configuration. Make the corresponding operation. For example, when the terminal UE needs to complete the external PDN network authentication, the P-GW and the PDN network perform the authentication policy, and interact with the authentication network element in the external PDN network to complete the evening authentication.
  • the P-GW After the P-GW completes the operation, it sends an update bearer request message to the ePDG.
  • Step 508a Optionally, the ePDG replies to the P-GW to update the bearer response, and confirms that the bearer update is completed.
  • Step 509 The ePDG sends the information received in step 508 (such as the confirmation message for completing the external authentication) to the terminal UE through the 200 OK.
  • L2TP Layer 2 Transport Protocol
  • PPP Point to Point Protocol
  • FIG. 6 is a schematic diagram of the protocol stack of the prior art scheme 3, FIG. The flow is similar to the flow shown in Figures 3 and 5.
  • Figure 16 shows the implementation architecture of the data offloading scheme in the 3G network
  • Figure 17 shows the implementation architecture of the data offloading scheme in the LTE network.
  • Table 1 and Table 2 respectively explain the names, functions, and protocols of network elements and interfaces in the network architecture.
  • UTRAN Universal Terrestrial includes BSS (Base Station Subsystem,
  • Radio Access Base Station Subsystem and RNC (Radio Network Network, universal terrestrial controller, wireless network controller), providing 3G access for subscriber line access network terminal equipment
  • Node service GPRS branch unit, responsible for user mobility and session management
  • Gateway GPRS core network external interface gateway providing users with access to support node, gateway operator's own business network or Internet access GPRS support node
  • E-UTRAN Evolved Universal consists of eNodeBs, which are user terminal devices.
  • MME Mobility Management user subscription data is stored in the current network
  • NAS-layer Non-Access Stratum
  • SGW/S-GW Serving Gateway the gateway from the core network to the wireless system, responsible for user plane bearer from the final gateway to the core network, data buffer in the idle mode of the terminal, function of initiating service request on the network side, lawful interception and Packet data routing and forwarding PGW PDN Gateway evolved packet domain system (EPS) and gateway of the system external network, responsible for terminal IP address allocation, accounting function, packet filtering, policy application, etc.
  • EPS evolved packet domain system
  • the Integrated Services Gateway is a new network element in the data offloading scheme, which combines the functions of the GGSN or the S-GW or the P-GW and the GTP (GPRS Tunneling Protocol) proxy. And NAT (Network Address Translation) gateway function.
  • the ISGW is located on the user data transmission path and is used for data offloading of the internet or other specific networks.
  • the ISGW and other standardized network elements (such as SGSN, GGSN, etc.) in the network are connected by standard interfaces, and the newly defined ones are used between the two ISGWs. Gn, or S5, to connect.
  • the newly defined interface has GTP messages and user data forwarding functions, and the specific names are not standardized yet.
  • the identity it exhibits may be only the identity of one of the network elements or several network elements at the same time.
  • the ISGW It may be just an S-GW, or just a P-GW, or both S-GW and P-GW.
  • the ISGW performs the data offloading principle as follows: In the 3G network, the access network UTRAN is connected to the ISGW through a standard DT (Direct Tunnel). In the LTE network, the access network E-UTRAN is connected to the ISGW through the standard S1-U. Send user data to the ISGW.
  • the ISGW performs packet processing according to the local configuration or the user offloading policy delivered from the policy server, and converts the data NAT address conforming to the offload policy to the Internet or other external network of the operator, and sends the data that the operator wants to control to the core network.
  • the gateway GGSN or P-GW routes to the operator's proprietary service network.
  • the above data offloading scheme can also support users to access from non-3GPP. In this case, the ISGW needs to increase the TTG and ePDG network element functions, and increase the Gx interface interactive flow migration policy between the ISGW and the PCRF.
  • the main object of the present invention is to provide a method and system for implementing stream migration, which can implement switching between a non-3GPP access network and a 3GPP access network, thereby improving system flexibility and efficiency.
  • a method for implementing stream migration comprising:
  • the 3GPP access network requests the network side/terminal UE to perform flow migration;
  • the terminal UE and the network side correspondingly migrate the uplink and downlink IP flows from the non-3GPP access network to the 3GPP access network, or from the 3GPP access network to the non-3GPP access network.
  • the method is specifically:
  • the terminal UE sends a flow migration request signaling to the packet data gateway ePDG that is evolved by the network side through the non-3GPP access network, where the flow migration request signaling carries the flow migration information;
  • the ePDG sends a GTP message to the network side packet data network gateway P-GW, where the GTP message carries the flow migration information;
  • the terminal UE and the P-GW respectively migrate the uplink and downlink IP flows from the 3GPP access network to the non-3GPP access network or from the non-3GPP access network to the 3GPP access network.
  • the method is specifically:
  • the terminal UE sends a NAS message to the mobility management unit MME through the 3GPP access network, where the NAS message carries the stream migration information;
  • the MME sends a GTP message to the serving gateway S-GW and the S-GW to the P-GW, where the GTP message carries the flow migration information;
  • the terminal UE and the P-GW respectively migrate the uplink and downlink IP flows from the non-3GPP access network to the 3GPP access network or from the 3GPP access network to the non-3GPP access network.
  • the method is specifically:
  • the network-side P-GW sends a GTP message to the ePDG, where the GTP message carries the flow migration information.
  • the ePDG sends the flow migration request signaling to the terminal UE through the non-3GPP access network, where the flow migration request signaling carries the flow migration information.
  • the terminal UE and the P-GW respectively migrate the uplink and downlink IP flows from the 3GPP access network to the non-3GPP access network or from the non-3GPP access network to the 3GPP access network.
  • the method is specifically:
  • the network side P-GW sends a GTP message to the S-GW and the S-GW to the MME, where the GTP is cancelled. Carrying stream migration information;
  • the MME sends a NAS message to the terminal UE through the 3GPP access network, where the NAS message carries the flow migration information;
  • the terminal UE and the P-GW respectively migrate the uplink and downlink IP flows from the non-3GPP access network to the 3GPP access network or from the 3GPP access network to the non-3GPP access network.
  • the method is specifically:
  • the terminal UE sends the flow migration request signaling to the network side ePDG through the non-3GPP access network, where the flow migration request signaling carries the flow migration information;
  • the ePDG sends PBU signaling to the network side P-GW, where the PBU signaling carries the flow migration information;
  • the terminal UE and the P-GW respectively migrate the uplink and downlink IP flows from the non-3GPP access network to the 3GPP access network or from the 3GPP access network to the non-3GPP access network.
  • the stream migration request signaling is an RSVP message, a NAS message, an IKEv2 message, or a SIP message.
  • the GTP message sent by the MME to the S-GW and sent by the ePDG/S-GW to the P-GW is a bearer resource command message; the P-GW sends the GTP message to the ePDG/S-GW, and the S-GW sends the GTP message to the MME.
  • the bearer establish/modify/update request message; the RSVP message is a Resv message; the NAS message is a bearer resource allocation/modification request, and activating a proprietary EPS bearer context request message; the IKEv2 message is an IKE authentication request/creator Security association request/information request message; the SIP message is an invite message.
  • the flow migration information includes one or more of the following: an access identifier, a QoS information corresponding to the flow, a flow identifier, a flow level, a flow packet filter/service flow template, and a flow operation indication.
  • the method further includes: the terminal UE establishing multiple bindings with the 3GPP access network and the non-3GPP access network, that is, the terminal UE accesses from the 3GPP access network
  • the established connection and the connection established when accessing from the non-3GPP access network belong to the same
  • the two sub-paths of the PDN connection share the same APN, PDN address, and IP-CAN session.
  • the process for the terminal UE to establish the multiple binding includes:
  • the access indication is sent to the P-GW; the P-GW acquires the access indication and establishes the terminal UE and the 3GPP access Multiple bindings between the network and non-3GPP access networks.
  • the method is specifically:
  • the terminal UE interacts with the integrated service gateway ISGW to request flow migration;
  • the terminal UE and the ISGW respectively migrate the uplink and downlink data streams from the 3GPP access network to the non-3GPP access network according to the interaction result, or respectively respectively migrate the uplink and downlink data streams from the non-3GPP access network to the 3GPP access network. .
  • the interaction between the terminal UE and the ISGW is initiated by the ISGW in the form of a trigger; or is initiated by the terminal UE.
  • the interaction process initiated by the ISGW in the form of a trigger includes:
  • the ISGW is triggered to initiate a flow migration, and sends an invitation message of the SIP protocol to the terminal UE. After receiving the message, the terminal UE migrates the uplink data stream from the 3GPP access network to the non-3GPP access network, and the ISGW downlinks the data stream.
  • the 3GPP access network switches to a non-3GPP access network;
  • the ISGW is triggered to initiate a flow migration, and sends a create/modify/update bearer request message to the MME/SGSN, and the MME/SGSN sends a bearer setup/modification/update request of the NAS message to the terminal UE according to the trigger of the ISGW;
  • the UE migrates the uplink data stream from the 3GPP access network to the non-3GPP access network according to the trigger of the received request; the ISGW switches the downlink data stream from the non-3GPP access network to the 3GPP access network.
  • the trigger condition comes from a policy change of the PCRF, or a request from the P-GW/GGSN, or a change in network load, causing the ISGW to decide to initiate a flow migration.
  • the interaction process initiated by the terminal UE actively includes:
  • the terminal UE decides to initiate a flow migration, and sends an invitation message of the SIP protocol to the ISGW, the ISGW. And the downlink data stream is switched from the 3GPP access network to the non-3GPP access network according to the message, and the terminal UE migrates the uplink data stream from the 3GPP access network to the non-3GPP access network;
  • the terminal UE decides to initiate a flow migration, and sends a request bearer resource modification message of the NAS protocol to the SGSN/MME, and the SGSN/MME sends a GTP bearer resource command to the ISGW; the ISGW switches the data flow, and switches from the non-3GPP access network to In the 3GPP access network, the terminal UE migrates the upstream data stream from the non-3GPP access network to the 3GPP access network.
  • the triggering condition for the UE to initiate the flow migration is determined by the user's experience, or the related policy obtained by the terminal UE from the policy server, or the terminal UE is caused by the mobile and wireless coverage changes.
  • the migration timing of the IP data stream is as follows: When there is a resource allocation and bearer setup operation, it is executed after the resource allocation and bearer establishment is successful, or directly after receiving the SIP or NAS or GTP message.
  • a system for implementing a flow migration includes a terminal UE and a network side, where the terminal UE is configured to request a network side to perform flow migration through a 3GPP access network or a non-3GPP access network; and correspondingly uplink IP
  • the flow is migrated from the non-3GPP access network to the 3GPP access network, or migrated from the 3GPP access network to the non-3GPP access network;
  • the network side is configured to: according to the notification of the terminal UE, corresponding to the downlink IP flow
  • the 3GPP access network migrates to the 3GPP access network, or migrates from the 3GPP access network to the non-3GPP access network.
  • the method is configured to: send, by using the non-3GPP access network, the flow migration request signaling to the network side ePDG, where the flow migration request signaling carries the flow migration information;
  • the ePDG is configured to send a GTP message to the network side P-GW, where the GTP message carries the flow migration information.
  • the terminal UE When the terminal UE requests the network side to perform flow migration through the 3GPP access network, it is used to: Transmitting, by the 3GPP access network, a NAS message to the mobility management unit MME, where the NAS message carries the flow migration information;
  • the MME is configured to send a GTP message to the P-GW through the S-GW, where the GTP message carries the flow migration information.
  • the terminal UE requests the network side to perform flow migration through the non-3GPP access network, and correspondingly migrates the uplink IP flow from the non-3GPP access network to the 3GPP access network, or migrates from the 3GPP access network to the non-3GPP access network.
  • flow migration through the non-3GPP access network, and correspondingly migrates the uplink IP flow from the non-3GPP access network to the 3GPP access network, or migrates from the 3GPP access network to the non-3GPP access network.
  • the ePDG is configured to send PBU signaling to the network side P-GW, where the PBU signaling carries the flow migration information;
  • the terminal UE and the P-GW are respectively configured to migrate the uplink and downlink IP flows from the non-3GPP access network to the 3GPP access network or from the 3GPP access network to the non-3GPP access network.
  • the network side includes an ISGW, and the ISGW combines functions of a GGSN, an S-GW, or a P-GW, and a GPRS tunneling protocol and a NAT gateway function;
  • the terminal UE and the ISGW are respectively configured to: perform interaction and request to perform flow migration; and respectively, respectively, respectively, to respectively migrate uplink and downlink data flows from the 3GPP access network to the non-3GPP access network according to the interaction result, or respectively Correspondingly, the uplink and downlink data streams are migrated from the non-3GPP access network to the 3GPP access network.
  • the interaction between the terminal UE and the ISGW is initiated by the ISGW in the form of a trigger; or is initiated by the terminal UE.
  • the ISGW When the ISGW initiates in the form of a trigger, the ISGW interacts with the terminal UE to:
  • the ISGW is triggered to initiate a flow migration, and sends an invitation message of the SIP protocol to the terminal UE.
  • the terminal UE migrates the uplink data stream from the 3GPP access network to the non-3GPP access.
  • the network the ISGW switches the downlink data stream from the 3GPP access network to the non-3GPP access network; or the ISGW is triggered, decides to initiate the flow migration, and sends a create/modify/update bearer request message to the MME/SGSN, by the MME/SGSN.
  • the terminal UE migrates the uplink data flow from the 3GPP access network to the non-3GPP access network according to the trigger of the received request; the ISGW will downlink the data stream. Switching to the 3GPP access network by a non-3GPP access network.
  • the trigger condition comes from a policy change of the PCRF, or a request from the P-GW/GGSN, or a change in the network load, causing the ISGW to decide to initiate a flow migration.
  • the terminal UE and the ISGW are respectively used by: the terminal UE determines to initiate a flow migration, and sends an invitation message of the SIP protocol to the ISGW, and the ISGW accesses the downlink data flow by the 3GPP according to the message.
  • the network switches to the non-3GPP access network, and the terminal UE migrates the uplink data stream from the 3GPP access network to the non-3GPP access network after receiving the response; or, the terminal UE decides to initiate the flow migration, and sends the request bearer of the NAS protocol.
  • the resource modification message is sent to the SGSN/MME, and the SGSN/MME sends a GTP bearer resource command to the ISGW;
  • the ISGW switches the data stream according to the received command, and switches from the non-3GPP access network to the 3GPP access network, and the terminal UE migrates the uplink data stream from the non-3GPP access network to the 3GPP access network.
  • the triggering condition for the UE to initiate the flow migration is determined by the user's experience, or the related policy obtained by the terminal UE from the policy server, or the terminal UE is caused by the mobile and wireless coverage changes.
  • the migration timing of the IP data stream is as follows: When there is a resource allocation and bearer setup operation, it is executed after the resource allocation and bearer establishment is successful, or directly after receiving the SIP or NAS or GTP message.
  • a system for implementing a flow migration includes a terminal UE and a network side, where the network side is configured to request a terminal UE to enter through a 3GPP access network or a non-3GPP access network. Traffic migration; and correspondingly moving the downlink IP flow from the non-3GPP access network to the 3GPP access network, or from the 3GPP access network to the non-3GPP access network;
  • the terminal UE is configured to migrate the uplink IP flow from the non-3GPP access network to the 3GPP access network according to the notification of the network side, or migrate from the 3GPP access network to the non-3GPP access network.
  • the network side includes a network side P-GW, and when the network side P-GW requests the terminal UE to perform flow migration through the non-3GPP access network, it is used to:
  • the ePDG is configured to send a flow migration request signaling to the terminal UE by using a non-3GPP access network, where the flow migration request signaling carries the flow migration information.
  • the network side includes a network side P-GW, and when the network side P-GW requests the terminal UE to perform flow migration through the 3GPP access network, it is used to:
  • the STP sends a GTP message to the MME, where the GTP message carries the flow migration information.
  • the MME is configured to send a NAS message to the terminal UE by using the 3GPP access network, where the NAS message carries the flow migration information.
  • the network side includes an ISGW, and the ISGW combines functions of a GGSN, an S-GW, or a P-GW, and a GPRS tunneling protocol and a NAT gateway function;
  • the terminal UE and the ISGW are respectively configured to: perform interaction and request to perform flow migration; and respectively, respectively, respectively, to respectively migrate uplink and downlink data flows from the 3GPP access network to the non-3GPP access network according to the interaction result, or respectively Correspondingly, the uplink and downlink data streams are migrated from the non-3GPP access network to the 3GPP access network.
  • the interaction between the terminal UE and the ISGW is initiated by the ISGW in the form of a trigger; or is initiated by the terminal UE.
  • the ISGW and the terminal UE are respectively used to:
  • the ISGW is triggered to initiate the flow migration, and sends an invitation message of the SIP protocol to the terminal UE.
  • the terminal UE migrates the uplink data stream from the 3GPP access network to the non-3GPP access network, and the ISGW uses the downlink data stream by the 3GPP.
  • the access network switches to a non-3GPP access network;
  • the ISGW is triggered to initiate a flow migration, and sends a create/modify/update bearer request message to the MME/SGSN, and the MME/SGSN sends a bearer setup/modification/update request of the NAS message to the terminal UE according to the trigger of the ISGW, the terminal
  • the UE migrates the uplink data stream from the 3GPP access network to the non-3GPP access network according to the trigger of the received request; the ISGW switches the downlink data stream from the non-3GPP access network to the 3GPP access network.
  • the trigger condition comes from a policy change of the PCRF, or a request from the P-GW/GGSN, or a change in the network load, causing the ISGW to decide to initiate a flow migration.
  • the terminal UE and the ISGW are respectively used by: the terminal UE determines to initiate a flow migration, and sends an invitation message of the SIP protocol to the ISGW, and the ISGW accesses the downlink data flow by the 3GPP according to the message.
  • the network switches to the non-3GPP access network, and the terminal UE migrates the uplink data stream from the 3GPP access network to the non-3GPP access network;
  • the terminal UE decides to initiate a flow migration, and sends a request bearer resource modification message of the NAS protocol to the SGSN/MME, and the SGSN/MME sends a GTP bearer resource command to the ISGW;
  • the ISGW switches the data stream according to the received command, and switches from the non-3GPP access network to the 3GPP access network, and the terminal UE migrates the uplink data stream from the non-3GPP access network to the 3GPP access network.
  • the triggering condition for the UE to initiate the flow migration is determined by the user's experience, or the related policy obtained by the terminal UE from the policy server, or the terminal UE is caused by the mobile and wireless coverage changes.
  • the migration timing of the IP data stream is as follows: When there is a resource allocation and bearer setup operation, it is executed after the resource allocation and bearer establishment succeeds, or directly after receiving the SIP or NAS or GTP message.
  • the terminal UE/network side requests the network side/terminal UE to perform the flow migration through the 3GPP access network or the non-3GPP access network; the terminal UE and the network side correspondingly uplink and downlink IP flows Migrating from a non-3GPP access network to a 3GPP access network, or from a 3GPP access network to a non-3GPP access network.
  • the invention can realize the migration of the flow between the non-3GPP access network and the 3GPP access network, thereby improving system flexibility and efficiency.
  • FIG. 1 is a schematic structural diagram of an EPS that is not trusted by a non-3GPP access network
  • FIG. 3 is a schematic diagram of a process in which a terminal UE accesses an EPC through an ePDG in the prior art
  • FIG. 4 is a schematic diagram of a protocol stack in the prior art scheme 2;
  • FIG. 5 is a flowchart of a method for a user of the prior art scheme 2 to access a network
  • FIG. 7 is a schematic flowchart of a method for implementing flow migration by a terminal UE in a non-3GPP access network to initiate a flow migration operation, and a service flow in a 3GPP access network is migrated to the non-3GPP access network according to Embodiment 1 of the present invention (terminal UE)
  • the flow migration request signaling sent to the ePDG is an IKEv2 message);
  • FIG. 8 is a schematic flowchart of a method for implementing a flow migration operation by a terminal UE in a non-3GPP access network to initiate a flow migration operation, and a service flow in the 3GPP access network is migrated to the non-3GPP access network according to Embodiment 1 of the present invention (terminal UE)
  • the flow migration request signaling sent to the ePDG is a SIP message);
  • FIG. 9 is a schematic flowchart of a method for implementing a flow migration operation by a terminal UE in a non-3GPP access network to initiate a flow migration operation in a non-3GPP access network, and implementing a traffic migration to the non-3GPP access network according to Embodiment 1 of the present invention (terminal UE)
  • the flow migration request signaling sent to the ePDG is an RSVP message
  • FIG. 10 is a schematic flowchart of a method for a terminal UE to migrate a service flow from a non-3GPP access network to a 3GPP access network according to Embodiment 1 of the present invention
  • FIG. 11 is a flow chart of a method for implementing flow migration by a network side in a non-3GPP access network, and a service flow in a 3GPP access network to the non-3GPP access network according to Embodiment 1 of the present invention; Schematic diagram (the flow migration request signaling sent by the ePDG to the terminal UE is an IKEv2 message); FIG. 12 is a flow of the network mobility operation in the non-3GPP access network, and the service flow in the 3GPP access network is performed by the network side according to the embodiment 1 of the present invention.
  • Flowchart of the method for implementing the flow migration to the non-3GPP access network (the flow migration request signaling sent by the terminal UE to the ePDG is an RSVP message);
  • FIG. 13 is a schematic flowchart of a method for implementing flow migration by a network side in a non-3GPP access network to initiate a flow migration operation in a non-3GPP access network, and implementing a flow migration process to the non-3GPP access network.
  • the flow migration request signaling sent to the ePDG is a SIP message);
  • FIG. 14 is a schematic flowchart of a network side P-GW migrating a service flow from a non-3GPP access network to a 3GPP access network according to Embodiment 1 of the present invention
  • 15 is a third embodiment of the present invention, where a UE migrates a service flow from a non-3GPP access network to
  • 16 is a schematic diagram of an implementation architecture of a data offloading scheme in a 3G network
  • 17 is a schematic diagram of an implementation architecture of a data offloading scheme in an LTE network
  • Figure 18 is a flow chart of network initiated flow migration (3GPP relocation to non-3GPP);
  • FIG. 19 is a flow chart of network-initiated flow migration (non-3GPP relocation to 3GPP);
  • FIG. 20 is a flowchart of flow migration initiated by a terminal UE (3GPP relocation to non-3GPP or reverse migration);
  • FIG. 21 is a flowchart of a flow migration initiated by a terminal UE (non-3GPP relocating to 3GPP);
  • FIG. 22 is a schematic flowchart of implementing flow migration according to an embodiment of the present invention. detailed description
  • the basic idea of the present invention is that the terminal user equipment UE/network side requests the network side/terminal UE to perform flow migration through the third generation partnership project 3GPP access network or the non-3GPP access network; the terminal UE and the network side correspondingly
  • the uplink and downlink IP flows are migrated from the non-3GPP access network to the 3GPP access network, or migrated from the 3GPP access network to the non-3GPP access network.
  • the present invention is based on the architecture of non-3GPP access EPC, and mainly involves the following five situations: 1) The terminal UE sends a flow migration request signaling to the ePDG through the non-3GPP access network, where the flow migration request signaling carries the flow migration information; the ePDG sends a GTP message (such as a bearer resource command) to the P-GW, where the GTP message carries Flow migration information; The terminal UE and the P-GW respectively migrate the uplink and downlink IP flows from the 3GPP access network to the non-3GPP access network or from the non-3GPP access network to the 3GPP access network.
  • a GTP message such as a bearer resource command
  • the terminal UE sends a NAS message to the MME through the 3GPP access network, where the NAS message carries the flow migration information; the MME sends a GTP message (such as a bearer resource command) to the S-GW, and the S-GW sends the GTP message to the P-GW. Carrying the flow migration information; the terminal UE and the P-GW respectively migrate the uplink and downlink IP flows from the non-3GPP access network to the 3GPP access network or from the 3GPP access network to the non-3GPP access network.
  • a GTP message such as a bearer resource command
  • the terminal UE sends the flow migration request signaling to the network side ePDG through the non-3GPP access network, where the flow migration request signaling carries the flow migration information; the ePDG sends the PBU signaling to the network side P-GW, where the PBU The signaling carries the flow migration information; the terminal UE and the P-GW respectively migrate the uplink and downlink IP flows from the non-3GPP access network to the 3GPP access network or from the 3GPP access network to the non-3GPP access network.
  • the network side P-GW sends a GTP message (such as a bearer setup/modification/update request) to the ePDG, where the GTP message carries the flow migration information; the ePDG sends the flow migration request signaling to the terminal UE through the non-3GPP access network, The flow migration request signaling carries the flow migration information; the terminal UE and the P-GW respectively migrate the uplink and downlink IP flows from the 3GPP access network to the non-3GPP access network or from the non-3GPP access network to the 3GPP access network.
  • a GTP message such as a bearer setup/modification/update request
  • the network side P-GW sends a GTP message (such as a bearer setup/modification/update request) to the S-GW to the MME, where the GTP message carries the flow migration information; the MME sends the 3GPP access network to the terminal UE.
  • the NAS message carries the stream migration information.
  • the terminal UE and the P-GW respectively migrate the uplink and downlink IP flows from the non-3GPP access network to the 3GPP access network or from the 3GPP access network to the non-3GPP access network. It should be noted that after receiving the bearer setup/modification request, the P-GW interacts with the PCRF and initiates a dynamic PCC process to create/modify bearers.
  • the present invention is based on the architecture of non-3GPP access EPC, and mainly involves the following four situations:
  • the terminal UE sends the flow migration request signaling to the ISGW through the non-3GPP access network, where the flow migration request signaling carries the flow migration information; the terminal UE and the ISGW respectively respectively uplink and downlink IP flows
  • the 3GPP access network migrates to a non-3GPP access network or migrates from a non-3GPP access network to a 3GPP access network.
  • the terminal UE sends the flow migration request signaling to the ISGW through the 3GPP access network, where the flow migration request signaling carries the flow migration information; the terminal UE and the ISGW respectively migrate the uplink and downlink IP flows from the 3GPP access network to the non-3GPP access network. Networking or migration from a non-3GPP access network to a 3GPP access network;
  • the terminal UE sends a NAS message to the MME through the 3GPP access network, where the NAS message carries the flow migration information;
  • the MME sends a GTP message (such as a bearer resource command) to the ISGW, where the GTP message carries the flow migration information;
  • the terminal UE and the ISGW respectively Upgrading the uplink and downlink IP flows from the non-3GPP access network to the 3GPP access network or from the 3GPP access network to the non-3GPP access network;
  • the network side ISGW sends the flow migration request signaling to the terminal UE through the non-3GPP access network, and the flow migration request signaling carries the flow migration information; the terminal UE and the ISGW respectively migrate the uplink and downlink IP flows from the 3GPP access network to the non-3GPP access network.
  • the 3GPP access network is either migrated from the non-3GPP access network to the 3GPP access network.
  • the network side ISGW sends the flow migration request signaling to the terminal UE through the 3GPP access network, and the flow migration request signaling carries the flow migration information; the terminal UE and the ISGW respectively migrate the uplink and downlink IP flows from the 3GPP access network to the non-3GPP. Access network or migration from a non-3GPP access network to a 3GPP access network;
  • the network side ISGW sends a GTP message to the MME (for example, bearer setup/modification/update)
  • the GTP message carries the flow migration information
  • the MME sends a NAS message to the terminal UE through the 3GPP access network, where the NAS message carries the flow migration information
  • the terminal UE and the ISGW respectively migrate the uplink and downlink IP flows from the non-3GPP access network. Migrating to a 3GPP access network or from a 3GPP access network to a non-3GPP access network.
  • the P-GW/SGSN interacts with the GTP/PMIP message and interacts with the PCRF and initiates a dynamic PCC process to create/modify the bearer.
  • the flow migration information includes one or more of the following: an access identifier (AID), a QoS information corresponding to the flow, a flow identifier (FID), a flow level, and a flow. Packet Filter (PF) / Traffic Flow Template (TFT), flow operation indication, etc.
  • AID access identifier
  • FID flow identifier
  • TFT Traffic Flow Template
  • the foregoing flow migration request information may be an RSVP message, a NAS message, an IKEv2 message, or a SIP message.
  • the terminal UE needs to establish multiple bindings with the 3GPP access network and the non-3GPP access network, and the multiple binding is: the connection established by the terminal UE from the 3GPP access and the non-3GPP access
  • the connection established at the same time belongs to two "sub-paths" of a "PDN connection", sharing the same APN, PDN address, and IP-CAN session.
  • the terminal UE accesses the first network according to the existing technology (attach/PDN connection establishment), and when the terminal UE accesses the second network and initiates multiple binding of the same PDN connection, the terminal UE may carry the “access indication”.
  • the ISGW/P-GW acquires the AID to establish multiple bindings with the 3GPP access network and the non-3GPP access network;
  • the ISGW/P-GW can determine that the PDN connection is multi-bound as long as the terminal UE accesses from the second network. Just connect.
  • the terminal UE/network side After the multi-binding relationship is established, after the stream migration/update/delete/new operation, As long as the terminal UE/network side initiates an operation request in a certain network, it means that the terminal UE/network side needs to migrate the data flow to the network, or update/delete/new data flow in the network, without carrying the AID.
  • the AID is used to indicate that the ISGW/P-GW is to perform multiple bindings, that is, the AID is just a name, and other names may be used.
  • the present invention further provides a system for implementing a flow migration, the system comprising a terminal UE and a network side, wherein the terminal UE and the ISGW are respectively configured to: perform interaction, request flow migration; and, respectively, according to the interaction result,
  • the uplink and downlink data streams are migrated from the 3GPP access network to the non-3GPP access network, or the uplink and downlink data streams are respectively migrated from the non-3GPP access network to the 3GPP access network.
  • the interaction between the terminal UE and the ISGW is initiated by the ISGW in the form of a trigger; or is initiated by the terminal UE.
  • the ISGW When the ISGW initiates in the form of a trigger, the ISGW interacts with the terminal UE to:
  • the ISGW is triggered to initiate a flow migration, and sends an invitation message of the SIP protocol to the terminal UE.
  • the terminal UE migrates the uplink data stream from the 3GPP access network to the non-3GPP access network, and notifies the ISGW, according to the ISGW.
  • the notification switches the downlink data stream from the 3GPP access network to the non-3GPP access network;
  • the ISGW is triggered to initiate a flow migration, and sends a create/modify/update bearer request message to the MME/SGSN, and the MME/SGSN sends a bearer setup/modification/update request of the NAS message to the terminal UE according to the trigger of the ISGW, and Notify the ISGW;
  • the terminal UE migrates the uplink data stream from the 3GPP access network to the non-3GPP access network according to the trigger of the received request; the ISGW switches the downlink data stream from the non-3GPP access network to the 3GPP access network according to the notification.
  • the trigger condition is from a policy change of the PCRF, or a request from the P-GW/GGSN, Or when the network load changes, the ISGW decides to initiate a flow migration.
  • the terminal UE and the ISGW are respectively used by: the terminal UE determines to initiate a flow migration, and sends an invitation message of the SIP protocol to the ISGW, and the ISGW accesses the downlink data flow by the 3GPP according to the message.
  • the network switches to the non-3GPP access network, and feeds back the response to the terminal UE; after receiving the response, the terminal UE migrates the uplink data stream from the 3GPP access network to the non-3GPP access network;
  • the terminal UE decides to initiate a flow migration, and sends a request bearer resource modification message of the NAS protocol to the SGSN/MME, and the SGSN/MME sends a GTP bearer resource command to the SGSN/MME.
  • the ISGW switches the data flow according to the received command, switches from the non-3GPP access network to the 3GPP access network, and sends a GTP protocol creation/modification/update bearer request message to the SGSN/MME, and the SGSN/MME sends the NAS protocol.
  • the bearer setup/modification/update request is sent to the terminal UE, and the terminal UE migrates the uplink data stream from the non-3GPP access network to the 3GPP access network according to the received request.
  • the triggering condition for the UE to initiate the flow migration is determined by the user's experience, or the related policy obtained by the terminal UE from the policy server, or the terminal UE is caused by the mobile and wireless coverage changes.
  • the migration timing of the IP data stream is as follows: When there is a resource allocation and bearer setup operation, it is executed after the resource allocation and bearer establishment is successful, or directly after receiving the SIP or NAS or GTP message.
  • the terminal UE is configured to request a network side to perform flow migration through a 3GPP access network or a non-3GPP access network; and correspondingly migrate the uplink IP flow from the non-3GPP access network to the 3GPP access network, or access by the 3GPP The network migrates to a non-3GPP access network;
  • the network side is configured to migrate the downlink IP flow from the non-3GPP access network to the 3GPP access network according to the notification of the terminal UE, or migrate from the 3GPP access network to the non-3GPP access network.
  • the terminal UE requests the network side to perform flow migration through the non-3GPP access network:
  • the terminal UE sends the flow migration request signaling to the network side ePDG through the non-3GPP access network, where the flow migration request signaling carries the flow migration information;
  • the ePDG sends a GTP message to the network side P-GW, where the GTP message carries the flow migration information.
  • the terminal UE requests the network side to perform flow migration through the 3GPP access network as:
  • the terminal UE sends a NAS message to the mobility management unit MME through the 3GPP access network, where the NAS message carries the flow migration information;
  • the MME sends a GTP message to the S-GW and the S-GW to the P-GW, where the GTP message carries the flow migration information.
  • the terminal UE requests the network side to perform flow migration through the non-3GPP access network, and correspondingly migrates the uplink IP flow from the non-3GPP access network to the 3GPP access network, or migrates from the 3GPP access network to the non-3GPP access network. For:
  • the terminal UE sends the flow migration request signaling to the network side ePDG through the non-3GPP access network, where the flow migration request signaling carries the flow migration information;
  • the ePDG sends PBU signaling to the network side P-GW, where the PBU signaling carries the flow migration information;
  • the terminal UE and the P-GW respectively migrate the uplink and downlink IP flows from the non-3GPP access network to the 3GPP access network or from the 3GPP access network to the non-3GPP access network.
  • the present invention also provides a system for implementing stream migration, where the system includes a terminal UE and a network side;
  • the network side is configured to request the terminal UE to perform flow migration through the 3GPP partner network 3GPP access network or the non-3GPP access network; and correspondingly migrate the downlink IP flow from the non-3GPP access network to the 3GPP access network , or migrated from a 3GPP access network to a non-3GPP access network;
  • the terminal UE is configured to: according to the notification of the network side, corresponding to the uplink IP flow
  • the 3GPP access network migrates to the 3GPP access network, or migrates from the 3GPP access network to the non-3GPP access network.
  • the network side requests the terminal UE to perform the flow migration through the non-3GPP access network to: the network side P-GW sends a GTP message to the ePDG, where the GTP message carries the flow migration information;
  • the ePDG sends a flow migration request signaling to the terminal UE through the non-3GPP access network, where the flow migration request signaling carries the flow migration information.
  • the network side requests the terminal UE to perform flow migration through the 3GPP access network as:
  • the network side P-GW sends a GTP message to the S-GW and the S-GW to the MME, where the GTP message carries the flow migration information;
  • the MME sends a NAS message to the terminal UE through the 3GPP access network, where the NAS message carries the flow migration information.
  • Embodiments 1-3 are based on the architecture 1 of the non-3GPP access EPC, and the embodiment 4 is based on the architecture 2 of the non-3GPP access EPC.
  • the terminal UE first attaches to the 3GPP access network, and establishes one or more PDN connections; after that, the terminal UE initiates an attach/PDN connection establishment operation in the non-3GPP access network (see FIG. 3, 5), to achieve multiple bindings of the same PDN connection.
  • the terminal UE carries an "Access Identification (AID)" to the P-GW when the multiple bindings of the same PDN connection are established, and the P-GW acquires the AID.
  • AID Access Identification
  • the P-GW After receiving the Create Session Request message sent by the ePDG and parsing the AID, the P-GW establishes a GTP tunnel with the ePDG and maintains the GTP tunnel of the P-GW and the S-GW. The P-GW will assign the IP address already assigned to the terminal UE in the "Create Session Reply" message returned to the ePDG. Return to the terminal UE again through the ePDG.
  • the terminal UE may also access the non-3GPP access network first, and then access from the 3GPP access network to establish multiple bindings.
  • the AID is not carried; the process of accessing the 3GPP access network is referred to the existing 3GPP attach/PDN connection establishment operation, and the difference is different.
  • the AID is carried in the create session request message sent by the UE to the MME, the MME sends the S-GW, and the S-GW sends the P-GW to the P-GW.
  • the purpose of the AID and the operation after the P-GW receives the parameter are as described in the non-3GPP access part above, and the mechanism is the same.
  • the terminal UE sends the flow migration request signaling (the IKEv2 message or the SIP message or the RS VP message) and carries the flow migration information to the ePDG, and the ePDG sends the bearer resource command to the P-GW and carries the flow.
  • the P-GW receives the bearer resource command
  • the P-GW initiates a bearer creation/modification/update operation in the non-3GPP access network
  • the terminal UE switches the uplink data flow from the 3GPP access network to the non-3GPP access network
  • P- The GW switches the downlink data stream from the 3GPP access network to the non-3GPP access network.
  • the method uses the premise that the terminal UE has been attached to both the 3GPP access network and the non-3GPP access network, and one or more PDNs are established. Connected, and implemented multiple bindings.
  • the flow migration information sent by the terminal UE to the ePDG and sent by the ePDG to the P-GW is one or more of the following information: QoS information corresponding to the service flow, service flow identifier (FID), service flow level PF (Packet Filter) / TFT (Traffic Flow Template), traffic flow operation indication, and access identifier (AID) corresponding to the service flow.
  • QoS information corresponding to the service flow QoS information corresponding to the service flow
  • service flow identifier FID
  • service flow level PF Packet Filter
  • TFT Traffic Flow Template
  • AID access identifier
  • the service flow operation indication refers to operations performed on the flow, such as migration, new creation, modification, deletion, update, and the like.
  • the terminal UE when it initiates the flow migration, it may only carry the flow identifier (FID) and the operation indication (for example, the flow migration indication), and according to the corresponding flow identifier, the P-GW can determine that the terminal UE wants to If the P-GW does not recognize the service flow identifier and rejects the request of the terminal UE, the terminal UE may request to migrate the service flow by sending the PF/TFT corresponding to the service flow; if the terminal UE sends the PF/ The TFT is not recognized by the P-GW. The P-GW rejects the request of the terminal UE.
  • the terminal UE can send the QoS corresponding to the service flow and request to create a bearer for the service flow.
  • the terminal UE can also initiate operations of multiple service flows at the same time, and indicate the priorities of the several service flows for ensuring the order and priority of establishment.
  • the service flow operation indication may be: migration, new creation, deletion, modification update, and the like.
  • the foregoing is only an example.
  • the specific implementation may depend on the system.
  • the terminal UE carries one or more of the above information, the UE can describe the service flow and indicate its operation, which is a specific implementation.
  • FIG. 7 , FIG. 8 , and FIG. 9 respectively illustrate a flow migration operation performed by a terminal UE in a non-3GPP access network according to Embodiment 1 of the present invention, and the service flow in the 3GPP access network is migrated to the non-3GPP access network.
  • the method flow diagram is different. The difference is that, in the method shown in FIG. 7, the flow migration request signaling sent by the terminal UE to the ePDG is an IKEv2 message, and the flow migration request signaling sent by the terminal UE to the ePDG in the method shown in FIG.
  • the flow migration request signaling sent by the terminal UE to the ePDG is an RSVP message.
  • FIG. 7 includes:
  • Step 700 The terminal UE is attached to both the 3GPP access network and the non-3GPP access network, and establishes one or more PDN connections, and implements multiple binding of the PDN connection.
  • Step 701 The terminal UE sends an IKEv2 authentication message to the ePDG, but the operation is not correct.
  • the UE performs authentication.
  • the message carries flow migration information for indicating the IP flow to be migrated.
  • the specific IKEv2 Request message may be one of the following messages. Other messages are not excluded: IKE_AUTH Request, Creat_child_SA Request (Create SA Security Request, SA, Security Association, Security Alliance), Informational Request. Similarly, the IKEv2 response message of step 704 can also be IKE_AUTH. Response (IKE Authentication Response), Creat_child_SA Response (Create a Child Security Alliance Response, SA, Security Association, Security Alliance), Informational Response. The same below.
  • the stream migration information can be carried through the above-mentioned message (especially Informational Request message) or extended Notify Payload or Configuration Payload or other cells.
  • Step 702 The ePDG sends a bearer resource command to the P-GW, and carries the stream migration information.
  • the flow migration information can be carried in the GTP message through the existing cell, or can be carried by adding a new cell, or both methods can be used.
  • the existing GTP protocol supports carrying QoS information, etc., and can be carried by existing QoS-compliant cells. The same below.
  • Step 703 After receiving the message in step 702, the P-GW sends a "Create/Modify/Update Bearer Request" message to the ePDG.
  • This message is an existing message and can be modified and modified without special modifications.
  • Step 704 The ePDG sends an IKEv2 message to the terminal UE to notify the terminal UE that the gateway P-GW accepts the stream migration request.
  • the terminal UE migrates the uplink data stream from the 3GPP access network to the non-3GPP access network.
  • the UE can switch the data stream when sending 701 steps.
  • the terminal UE may switch the data stream after step 705; if step 705 is not performed, the terminal UE may switch the data stream to occur after step 704. The same below.
  • Step 705 If the resource reservation/bearer establishment mechanism is supported in the non-3GPP access network, the non-3GPP access network creates/modifies/updates the bearer according to the QoS information downloaded in step 703, and reserves resources for the new service; if not the 3GPP access If the network reservation does not support the resource reservation/bearer establishment mechanism, this step is not performed.
  • Step 706 The ePDG replies to the P-GW with "Create/Modify/Update Bearer Response" to notify the P-GW. Switch traffic flow.
  • Step 707 After receiving the message of step 706, the P-GW switches the downlink data stream from the 3GPP access network to the non-3GPP access network.
  • the P-GW can switch the data stream after receiving the ",, bear resource command" of the ePDG.
  • the above manner may be used, and the data stream is switched after receiving the message in step 706. The same below.
  • the P-GW After completing the flow switching operation, the P-GW initiates a bearer deletion/modification/resource release operation in the 3GPP access system, and deletes the bearer used by the original service flow in the 3GPP access network.
  • a bearer deletion/modification/resource release operation in the 3GPP access system, and deletes the bearer used by the original service flow in the 3GPP access network.
  • the specific process refer to the resource modification/deactivation process initiated by the P-GW in the prior art in the 3GPP system.
  • SIP (Fig. 8) or RSVP is used between the terminal UE and the ePDG.
  • the terminal UE When signaling, the terminal UE sends a SIP: invite (invitation) message or an RSVP: Resv (Reservation) message to the ePDG, and the message carries the flow migration information, which is used to indicate the IP flow to be migrated.
  • the P-GW After the P-GW sends a "Create/Modify/Update Bearer Request" to the ePDG, the ePDG replies to the terminal UE with a SIP: 200 OK message or a ResvCon Reservation confirm message, notifying the terminal that the UE P-GW has accepted the flow migration. request.
  • SIP invite
  • RSVP Resv (Reservation) message
  • the message carries the flow migration information, which is used to indicate the IP flow to be migrated.
  • the P-GW After the P-GW sends a "Create/Modify/Update Bearer Request" to the ePDG, the ePDG replies to the terminal UE with a SIP: 200 OK message or a ResvCon Reservation
  • the UE may also migrate the service flow from the non-3GPP access network to the 3GPP access network.
  • FIG. 10 For the specific flowchart, refer to FIG. 10. The difference from FIG. 7, 8, and 9 is that the signaling for carrying the flow migration information is different, and the network elements passing through are different; the mechanism of the service flow migration and the functions of the P-GW are similar.
  • the network side P-GW initiates a flow migration operation in the non-3GPP access network, and migrates the service flow in the 3GPP access network to the non-3GPP access network.
  • the terminal UE has been attached to both the 3GPP access network and the non-3GPP access network, and one or more PDN connections are established, and multiple bindings are implemented.
  • the network side P-GW is triggered, sends a "create/modify/update bearer request" and carries the flow migration information to the ePDG, and the ePDG sends the flow migration signaling to the terminal UE (is an IKEv2 message or The SIP message or the RSVP message carries the stream migration information.
  • the terminal UE switches the uplink data stream from the 3GPP access network to the non-3GPP access network, and the P-GW receives the "create/modify/update".
  • the downlink data stream is handed over from the 3GPP access network to the non-3GPP access network.
  • the message "Bearing Resource Command” message sent by the ePDG to the P-GW, the "Create/Modify/Update Bearer Request” message sent by the P-GW to the ePDG, and the “Create/Modify/Update Bearer Response” sent by the ePDG to the P-GW Messages are a specific message of a GTP message, and the above solution is just a specific implementation. Other messages of the GTP message family can also be used for specific implementation. The following embodiments are the same.
  • FIG. 11 , FIG. 12 , and FIG. 13 respectively illustrate a flow migration operation initiated by a network side in a non-3GPP access network according to Embodiment 1 of the present invention, and a service flow migration of a service flow in a 3GPP access network to the non-3GPP access network is implemented.
  • the method flow diagram is different. The difference is that, in the method shown in FIG. 11, the flow migration request signaling sent by the ePDG to the terminal UE is an IKEv2 message, and the flow migration request signaling sent by the terminal UE to the ePDG in the method shown in FIG.
  • the flow migration request signaling sent by the terminal UE to the ePDG is a SIP message.
  • FIG. 11 includes:
  • Step 1000 The terminal UE is attached to both the 3GPP access network and the non-3GPP access network, and one or more PDN connections are established, and multiple bindings are implemented.
  • Step 1001 The P-GW is triggered to decide to initiate a flow migration.
  • Step 1002 The P-GW sends a "Create/Modify/Update Bearer Request" message to the ePDG and carries the flow migration information, which is used to indicate the IP flow to be migrated.
  • Step 1003 The ePDG sends an IKEv2 certificate message to the terminal UE, where the message carries the flow migration information, and is used to indicate the IP flow to be migrated.
  • the terminal UE migrates the uplink data stream from the 3GPP access network to the non-3GPP access network. It should be noted that, if step 1004 is performed, the terminal UE handover data flow occurs after 1004; if 1004 is not performed, the terminal UE handover data flow occurs after step 1003.
  • Step 1004 If the resource reservation/bearer establishment mechanism is supported in the non-3GPP access network, the non-3GPP access network creates a bearer according to the QoS information downloaded in step 1003, and reserves resources with the new service; if the non-3GPP access network does not support The resource reservation/bearer establishment mechanism, this step is not performed.
  • Step 1005 The ePDG replies to the P-GW with a "Create/Modify/Update Bearer Response" to notify the P-GW to switch the service flow.
  • Step 1006 After receiving the message of step 1006, the P-GW switches the downlink data stream from the 3GPP access network to the non-3GPP access network.
  • the P-GW After completing the flow switching operation, the P-GW initiates a bearer deletion/modification/resource release operation in the 3GPP access system, and deletes the bearer used by the original service flow in the 3GPP access network.
  • a bearer deletion/modification/resource release operation in the 3GPP access system, and deletes the bearer used by the original service flow in the 3GPP access network.
  • the specific process refer to the resource modification/deactivation process initiated by the P-GW in the prior art in the 3GPP system.
  • SIP is used between the terminal UE and the ePDG (Fig. 13) or
  • the ePDG When the RSVP is used, the ePDG sends a SIP: invite message or an RSVP: Resv message to the terminal UE, and the message carries the flow migration information for indicating the IP flow to be migrated.
  • the terminal UE replies to the ePDG with the SIP: 200.
  • the OK message or the ResvConf message informs the network side that the flow migration request has been accepted.
  • the P-GW may also migrate the service flow from the non-3GPP access network to the 3GPP access network.
  • the specific flowchart is similar to that in FIG. 11, 12, and 13 except that The signaling for carrying the flow migration information is different, and the network elements passing through are different.
  • the mechanism of the service flow migration and the functions of the P-GW are similar.
  • the case where the terminal UE initiates a service request is similar to the case where the terminal UE initiates a flow migration operation, but there are also differences, specifically:
  • the service flow operation indication in the flow description is changed to create, modify, and delete.
  • the terminal UE and the P-GW do not perform the flow switching operation, and the corresponding establishment, modification, and deletion industries PF/TFT and 7-load corresponding to the data stream;
  • the P-GW no longer initiates bearer deletion/resource release in the source network.
  • the service flow operation indication in the flow description is changed to create, modify, and delete.
  • the terminal UE and the P-GW do not perform a flow switching operation, and correspondingly create, modify, and delete the PF/TFT and 7 corresponding to the service data flow;
  • the P-GW no longer initiates bearer deletion/resource release in the source network.
  • the terminal UE if the terminal UE is to migrate/deactivate/modify/update the service flow to a certain network or to a certain network, The corresponding network initiates the corresponding operation. For example, if the terminal UE wants to migrate traffic to a non-3GPP network, the terminal needs to send a stream migration request to the P-GW through the ePDG.
  • the terminal UE needs to carry different AIDs when accessing the first network to initiate an attach/PDN connection establishment or when accessing the second network to initiate multiple binding of the same PDN connection. For example, the terminal UE first accesses the 3GPP access network, and when the first PDN connection is established, it allocates AID-1, and when the terminal UE initiates multiple binding of the PDN connection in the second network, it assigns an AID- 2. During the lifetime of the PDN connection, AID-1 indicates the 3GPP access network, and AID-2 indicates the non-3GPP access network.
  • the terminal UE/network side migrates/creates/deletes the service flow in different access networks, in addition to carrying the flow migration information/flow description information, it also carries the AID, which represents the network where the task is performed.
  • the terminal UE may send a stream migration request to the P-GW through the ePDG in the non-3GPP access network, and carry the AID-1 (AID-1 allocated when the 3GPP accesses) and the flow migration information, because the AID-1 is carried.
  • AID-1 AID-1 allocated when the 3GPP accesses
  • the AID acts to identify the execution in the access network where the specific operation is located.
  • connection and PDN connection initiated by the terminal UE in the embodiment 1 is as follows:
  • the terminal UE accesses the 3GPP access network (the first access network) to establish the first PDN connection
  • the terminal UE is allocated with AID-1, and the AID-1 represents the 3GPP access path of the PDN connection; 301-302, in steps 501-502, the terminal UE carries AID-2 to the P-GW, and the P-GW acquires the AID-2, and establishes multiple bindings with the 3GPP access network and the non-3GPP access network, and the AID -2 characterizes the non-3GPP access path for the PDN connection.
  • the difference between the flow migration operation initiated by the UE and the UE in the first embodiment is different from that of the UE.
  • the flow migration request (IKEv2 or SIP or RSVP and bearer resource command message) sent by the terminal UE to the ePDG and ePDG to the P-GW includes flow migration information in addition to the AID.
  • the AID characterizes the network that the operation needs to perform. For example, if AID-1 is carried, it indicates that the flow is to be migrated to the 3GPP access network. If AID-2 is carried, it indicates that the flow is to be migrated to the non-3GPP access network.
  • the flow migration operation initiated by the network side is: a flow migration request message sent by the network side P-GW to the ePDG and ePDG to the terminal UE.
  • AID (Host resource command message and IKEv2 or SIP or RSVP), including flow migration information in addition to AID.
  • the AID characterizes the network that the operation needs to perform. For example, if AID-1 is carried, it indicates that the flow is to be migrated to the 3GPP access network. If AID-2 is carried, it indicates that the flow is to be migrated to the non-3GPP access network.
  • the specific description refers to the corresponding part of the method 1.
  • the difference is the same as the above 1-3, that is, the AID must be carried, which is used to identify The network to be executed by the requested operation.
  • the data channel/tunnel is established between the ePDG and the P-GW through the GTP protocol.
  • the ePDG and the P-GW may still be based on the PMIPv6 protocol.
  • Establish a data channel/tunnel is equally applicable when the PMIPv6 protocol is used between the ePDG and the P-GW.
  • the basic mechanism is the same as the GTP scenario, and the differences are further illustrated by the description in Figure 15.
  • Step 1500 to step 1501 Same as step 700 to step 701.
  • Step 1502 The ePDG sends PBU signaling to the P-GW, and carries the flow migration information.
  • the flow migration information can be carried in the PMIPv6 message by adding a new cell.
  • the existing PBU message does not support carrying the QoS information. Therefore, the flow migration information needs to be carried by the extended cell.
  • Step 1503 After receiving the message in step 1502, the P-GW switches the downlink data stream from the 3GPP access network to the non-3GPP access network.
  • Step 1504 The P-GW sends a PBA message to the ePDG.
  • Step 1505 The ePDG sends an IKEv2 message to the terminal UE to notify the terminal UE that the gateway P-GW accepts the flow migration request.
  • the terminal UE switches the upstream data stream from the 3GPP access network to the non-3GPP access network.
  • the P-GW After completing the flow switching operation, the P-GW initiates a bearer deletion/modification/resource release operation in the 3GPP access system, and deletes the bearer used by the original service flow in the 3GPP access network.
  • a bearer deletion/modification/resource release operation in the 3GPP access system, and deletes the bearer used by the original service flow in the 3GPP access network.
  • the specific process refer to the resource modification/deactivation process initiated by the P-GW in the prior art in the 3GPP system.
  • the terminal UE when SIP (FIG. 8) or RSVP (FIG. 9) signaling is used between the terminal UE and the ePDG, the terminal UE sends a SIP: invite message or RSVP: Resv to the ePDG. A message carrying the flow migration information for indicating the IP flow to be migrated.
  • the ePDG replies to the terminal UE with a SIP: 200 OK message or a ResvConf message, notifying the terminal UE that the gateway P-GW has accepted the flow migration request.
  • the UE may also migrate the service flow from the non-3GPP access network to the 3GPP access network.
  • the specific flowchart refer to FIG. 10.
  • the network side P-GW initiates a flow migration operation in the non-3GPP access network, and migrates the service flow in the 3GPP access network to the non-3GPP access network.
  • the terminal UE has been attached to both the 3GPP access network and the non-3GPP access network, and one or more PDN connections are established, and multiple bindings are implemented.
  • the network side P-GW is triggered to send the PBU and carry the flow migration information to the ePDG.
  • the ePDG sends the flow migration signaling (which is an IKEv2 message or a SIP message or an RSVP message) to the terminal UE and carries the flow migration information, and the terminal UE receives the flow.
  • the uplink data stream is switched from the 3GPP access network to the non-3GPP access network.
  • the P-GW switches the downlink data stream from the 3GPP access network to the non-3GPP access network.
  • the related description of the flow migration initiated by the terminal UE and the flow migration initiated by the network side is the related mechanism of the first embodiment.
  • the mechanism introduced in the second embodiment can also be used.
  • the GTP message sent by the MME to the S-GW and sent by the ePDG/S-GW to the P-GW may be a bearer resource command message; the P-GW sends For the ePDG/S-GW, the GTP message sent by the S-GW to the MME may be a bearer setup/modify/update request message; the RSVP message may be a Resv message, and the NAS message may be a bearer resource allocation/modification request, activated.
  • the privileged EPS bearer context request message; the IKEv2 message may be an IKE authentication request/create a sub-security association request/information request message; the SIP message may be an invite message.
  • the main idea of implementing flow migration based on non-3GPP access EPC architecture 2 is: Because 3GPP Both the access and the non-3GPP access are anchored to the ISGW, so the terminal-initiated flow migration operation request is sent to the ISGW, and the ISGW performs the flow migration operation without reporting the P-GW/GGSN or merely notifying the P-GW/GGSN. It is not necessary to perform a switching flow by the P-GW/GGSN.
  • the network-initiated flow migration may be that the ISGW is triggered by the trigger (or the trigger from the P-GW/GGSN or the trigger from the PCRF) to initiate an operation request, and the terminal is notified to perform the flow migration operation.
  • the difference from the architecture 1 of the non-3GPP access EPC is that the ISGW does not need to interact with the P-GW/GGSN or only the event report, and the P-GW/GGSN does not need to participate in the stream migration operation.
  • the flow migration (from 3GPP to non-3GPP or reverse migration) initiated by the terminal/network side is described below.
  • Step 1801 The terminal UE has been attached to both the 3GPP access network and the non-3GPP access network, and one or more PDN connections are established, and multiple bindings are implemented.
  • Step 1802 The ISGW is triggered to decide to initiate a flow migration.
  • the trigger condition may be from a policy change of the PCRF, or a request from the P-GW/GGSN, or a change in network load, causing the ISGW to decide to initiate a flow migration.
  • Step 1803 The ISGW sends an invite message of the SIP protocol to the terminal UE, where the message carries the flow migration information, and is used to indicate the IP flow to be migrated.
  • Step 1804 The terminal UE sends a 200 OK message of the SIP protocol to the ISGW.
  • the terminal UE migrates the uplink data stream from the 3GPP access network to the non-3GPP access network.
  • step 1805 the terminal UE switches the data flow to occur in the step.
  • step 1805 After 1805; if step 1805 is not performed, the terminal UE switching data flow occurs after step 1803.
  • Step 1805 If the resource reservation/bearer establishment mechanism is supported in the non-3GPP access network, the non-3GPP access network creates a bearer according to the QoS information downloaded in step 1803, and reserves resources for the new service. If the non-3GPP access network does not support the resource. The reservation/bearer establishment mechanism, this step is not performed.
  • Step 1806 After receiving the message of step 1804, the ISGW switches the downlink data stream from the 3GPP access network to the non-3GPP access network.
  • the ISGW After completing the flow switching operation, the ISGW initiates a corresponding bearer deletion/modification/resource release operation in the 3GPP access system, and deletes the bearer used by the original service flow in the 3GPP access network.
  • the specific process refer to the resource modification/deactivation process initiated by the P-GW/GGSN in the prior art in the 3GPP system.
  • Step 1901 The terminal UE has been attached to both the 3GPP access network and the non-3GPP access network, and one or more PDN connections are established, and multiple bindings are implemented.
  • Step 1902 The ISGW is triggered to decide to initiate a flow migration (non-3GPP relocates to 3GPP).
  • the trigger condition may be from a policy change of the PCRF, or a request from the P-GW/GGSN, or a change in network load, causing the ISGW to decide to initiate a flow migration.
  • Step 1903 The ISGW sends a create/modify/update bearer request message to the MME/SGSN, where the message carries the flow migration information, and is used to indicate the IP flow to be migrated.
  • Step 1904 The MME/SGSN sends a bearer establishment/modification/update request of the NAS message to the terminal UE, and the message carries the flow migration information, which is used to indicate the IP flow to be migrated.
  • Step 1905 3GPP radio resource reservation and bearer establishment.
  • the terminal UE migrates the uplink data stream from the 3GPP access network to the non-3GPP access network.
  • step 1905 the terminal UE handover data flow occurs after step 1905; if step 1905 is not performed, the terminal UE handover data flow occurs after step 1904.
  • Step 1906 After the radio bearer is established, the MME/SGSN sends a create/modify/update 7-load response message to the ISGW.
  • Step 1907 After receiving the message of step 1906, the ISGW switches the downlink data stream from the non-3GPP access network to the 3GPP access network.
  • the ISGW After completing the flow switching operation, the ISGW initiates a corresponding bearer deletion/modification/resource release operation in the non-3GPP access system, and deletes the bearer used by the original service flow in the 3GPP access network (if the operation exists in the prior art) .
  • Step 2001 The terminal UE has been attached to both the 3GPP access network and the non-3GPP access network, and one or more PDN connections are established. And implemented multiple bindings.
  • Step 2002 The terminal UE decides to initiate a flow migration (3GPP moves to non-3GPP).
  • the terminal UE sends an invite message of the SIP protocol to the ISGW, where the message carries the flow migration information, which is used to indicate the IP flow to be migrated.
  • the triggering condition that the UE decides to initiate the flow migration may be determined by the user's experience, or may be the terminal UE from the policy server (for example, ANDSF, Access Network Discovery and
  • the selection function, the network discovery and selection function, and the like acquire related policies, or the terminal UE moves due to changes in mobility and wireless coverage.
  • Step 2003 The ISGW sends a 200 OK message of the SIP protocol to the terminal UE.
  • the terminal UE migrates the uplink data stream from the 3GPP access network to the non-3GPP access network.
  • step 2004 the terminal UE handover data flow occurs after step 2004; if step 2004 is not performed, the terminal UE handover data flow occurs after step 2003.
  • Step 2005 After receiving the message of step 2002, the ISGW switches the downlink data stream from the 3GPP access network to the non-3GPP access network. Alternatively, if step 2004 is performed, the ISGW waits for the data flow to be migrated after the step 2004 is completed.
  • Step 2100 The terminal UE has been attached to both the 3GPP access network and the non-3GPP access network, and one or more PDN connections are established, and multiple bindings are implemented.
  • Step 2101 The terminal UE decides to initiate a flow migration (3GPP moves to non-3GPP).
  • the terminal UE sends a request bearer resource modification message of the NAS protocol to the SGSN/MME, where the message carries the flow migration information, which is used to indicate the IP flow to be migrated.
  • the triggering condition for the UE to initiate the flow migration may be determined by the user's experience, or the terminal UE may obtain the related policy from the policy server (for example, ANDSF, Access Network Discovery and Selection Function, network discovery and selection function, etc.). Or, the terminal UE causes flow migration due to changes in mobility and wireless coverage.
  • the policy server for example, ANDSF, Access Network Discovery and Selection Function, network discovery and selection function, etc.
  • Step 2102 The SGSN/MME sends a GTP bearer resource command to the ISGW, and the message carries the flow migration information, and is used to indicate the IP flow to be migrated.
  • the ISGW switches the data stream and migrates from non-3GPP to 3GPP.
  • Step 2103 The ISGW sends a GTP protocol creation/modification/update bearer request message to the SGSN/MME.
  • Step 2104 The SGSN/MME sends a bearer setup/modification/update request of the NAS protocol to the terminal UE, and the message carries the flow migration information, which is used to indicate the IP flow to be migrated.
  • Step 2105 The 3GPP access network performs resource reservation and bearer setup operations.
  • Step 2106 After the radio bearer is established, the MME/SGSN sends a create/modify/update 7-response message to the ISGW.
  • Step 2107 After receiving the message of step 2106, the ISGW switches the downlink data stream from the non-3GPP access network to the 3GPP access network.
  • Embodiment 4 is only a preferred embodiment of another implementation manner.
  • the UE and the ISGW can directly exchange SIP messages without By borrowing the underlying NAS and GTP messages, the flow migration information can be directly carried in the SIP message, and the MME/SGSN can be transparently transmitted, which can reduce the impact on the 3GPP network.
  • the migration timing of the IP data stream may be as described in the flowchart.
  • the resource allocation and bearer establishment are performed successfully, and after receiving the SIP or NAS or GTP message, Direct execution.
  • ePDG and other modules in the ISGW are possible to be separated.
  • the eTPG and the ISGW use the GTP or PMIP protocol to establish a data channel.
  • the flow migration mechanism can be similar to that shown in Figure 8, 9, 11, 12, 13, and 15, except that the P-GW can be changed to the ISGW; or the ISGW can directly communicate with the terminal UE.
  • Signaling see Figures 18 and 20, SIP message transparent transmission ePDG, ePDG is not shown in the figure), used to negotiate flow migration information.
  • Step 2210 The terminal UE/network side requests the network side/terminal UE to perform flow migration through the 3GPP access network or the non-3GPP access network.
  • Step 2220 The terminal UE and the network side respectively migrate the uplink and downlink IP flows from the non-3GPP access network to the 3GPP access network, or from the 3GPP access network to the non-3GPP access network.
  • the method for implementing the flow migration of the present invention can implement switching between the non-3GPP access network and the 3GPP access network, thereby improving system flexibility and efficiency.

Landscapes

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

Abstract

本发明公开了一种实现流迁移的方法，包括：终端用户设备UE/网络侧通过第三代合作伙伴计划3GPP接入网或非3GPP接入网请求网络侧/终端UE进行流迁移；所述终端UE和网络侧相应地将上下行IP流由非3GPP接入网迁移到3GPP接入网，或由3GPP接入网迁移到非3GPP接入网。本发明还相应地公开了一种实现流迁移的系统。本发明能够实现非3GPP接入网与3GPP接入网之间的流的迁移，从而能够提高系统灵活度及效率。

Description

一种实现流迁移的方法及系统 技术领域
本发明涉及通信领域， 尤其涉及一种实现流迁移的方法及系统。 背景技术
为了保持第三代移动通信系统在移动通信领域强有力的竟争力， 必须 提高其网络性能以及降低网络建设和运营成本， 因此， 第三代合作伙伴计 划 ( 3rd Generation Partnership Project, 3GPP ) 的标准化工作组目前正致力 研究核心网系统下一代演进——演进的分组核心网 （ Evolved Packet Core, EPC ), 目的是能为用户提供更高的传输速率、 更短的传输时延。 EPC系统 支持演进的通用陆地无线接入网 （ Evolved Universal Terrestrial Radio Access Network, E-UTRAN )的接入； EPC系统支持 Non-3GPP接入网的接入， 如 无线局域网 （ Wireless Local Area Network, WLAN )接入网。
一、 非 3GPP接入 EPC的架构一
图 1为演进的分组系统（ Evolved Packet System, EPS )的架构示意图， 如图 1所示， 终端用户设备（User Equipment, UE )处于非漫游情况下， 终 端 UE可以通过不信任的 Non-3GPP接入网接入 EPC, 或者通过 E-UTRAN 接入 EPC。 EPS中一般包括以下网元： 移动管理单元（Mobility Management Entity, MME )、 服务网关 （ Serving Gateway, S-GW )、 分组数据网络网关 ( Packet Data Network GateWay, P-GW/PGW )、 归属用户服务器 （Home Subscriber Server, HSS )、 3GPP认证授权计费服务器（ AAA服务器）、 演 进的分组数据网关 （ Evolved Packet Data Gateway, ePDG )、 策略与计费规 则功能（ Policy and Charging Rules Function, PCRF )。 其中， MME负责移 动性管理、 非接入层 (NAS , Non-Access Stratum)信令的处理、 用户的移动 管理上下文的管理等控制面相关工作； S-GW是与 E-UTRAN相连的接入网 关设备， 用于在 E-UTRAN和 PDN GW之间转发数据； P-GW是 3GPP EPS 与公共陆地移动网络（Home Public Land Mobile Network, HPLMN )提供 的 IP业务的边界网关， 负责 IP业务的接入、 以及在 EPS与 IP业务网间转 发数据。
不信任的非 3GPP接入网（ Untmsted Non-3GPP Access ), 即 3GPP网络 和该非 3GPP接入系统之间不存在信任关系，非 3GPP接入系统必须首先接 入 3GPP网络的 ePDG,再通过 S2b接口接入 P-GW。这时，终端 UE与 ePDG 之间建立 IPsec ( IP Security, IP安全）隧道， 保证终端 UE与 3GPP网络之 间信令和数据的安全。 其中， S2b接口使用代理移动 IP协议第六版（Proxy Mobile Internet Protocol version 6, ΡΜΙΡνό )或者 GPRS隧道协议 ( GPRS Tunnel Protocol, GTP )协议。
终端 UE通过非 3GPP接入系统接入到 ePDG时， 可以通过以下现有方 案实现：
方案 1 : IPsec方案
图 2 为现有技术方案 1 的控制面协议栈示意图， 其中 L2/L1 ( Layer 1/Layer 2, 层 1/层 2 )为数据链路层和物理层， IPv4/v6为 IP层， 因特网密 钥交换第二版（ Internet Key Exchange Version 2 , IKEv2 )用来在终端 UE和 ePDG之间协商密钥以及建立 IPSec隧道。
图 3为现有技术方案 1的终端 UE通过 ePDG接入 EPC的流程示意图， 图 3所示流程包括以下步骤：
步骤 301 : ePDG与终端 UE之间交互 IKEv2信令，建立安全联盟， EPC 网络和终端 UE之间进行认证。
需要说明的是， 在步骤 301中， ePDG和 3GPP AAA/HSS之间有交互。 步骤 302: ePDG向 P-GW发起 PDN连接建立请求消息， 该消息的具 体内容为创建会话请求， P-GW收到该消息后发送建立会话回复，其中包含 为该终端 UE分配的地址。
上述内容针对 ePDG和 P-GW之间釆用 GTP协议的场景， 如果 ePDG 和 P-GW之间釆用的是 PMIPv6协议，则步骤 302的交互信令是代理绑定更 新和代理绑定确认 ( Proxy binding update/PBU和 Proxy binding Ack/PBA )。
步骤 303: ePDG发送 IKEv2消息通知终端 UE上述 P-GW分配的 IP 地址， 完成 IPSec隧道的建立。
方案 2: NAS/SIP方案
图 4为现有技术方案 2的协议栈示意图， 其中 L2/L1为数据链路层和 物理层， IPv4/v6为 IP层， IKEv2协议用来在终端 UE和 ePDG之间协商密 钥以及建立 IPSec隧道。 IPsec隧道之上存在其他的协议栈， 图中是 NAS或 者 SIP协议栈。
当终端 UE完成 IKEv2协议交互， 建立 IPsec隧道后， 再启动 SIP协议 栈交互。 图 5为现有技术方案 2的用户接入网络的方法流程图， 图 5所示 流程包括以下步骤：
步骤 501~步骤 503: 同步骤 301~步骤 303。
步骤 504: 终端 UE发起 SIP注册请求。
步骤 505: ePDG回复 200 OK给终端 UE, 完成终端 UE的 SIP注册。 步骤 506: 终端 UE向 ePDG发送邀请 ( INVITE )。
该步骤中，当终端 UE需要完成外部 PDN网络认证时或者其他用途时， 终端 UE可以携带信息给 ePDG并通过下一步到达 P-GW, 例如携带认证信 息， 如用户名 /密码等。
步骤 507: ePDG发送承载资源命令给 P-GW,上述消息中包含步骤 506 中终端 UE发来的信息。
步骤 508: 当 P-GW收到了终端 UE发来的信息， P-GW根据自身配置 做出对应操作。 例如， 当终端 UE需要完成外部 PDN网络认证时， P-GW 与 PDN网络执行认证的策略， 与外部 PDN网络中的认证网元交互， 完成 夕卜部认证。
P-GW完成操作后， 向 ePDG发送更新承载请求消息。
步骤 508a: 可选的， ePDG回复 P-GW更新承载应答， 确认承载更新 完成。
步骤 509: ePDG将步骤 508中收到的信息（如完成外部认证的确认信 息 )通过 200 OK发给终端 UE。
方案 3: 层 2传输协议（ Layer 2 Transport Protocol, L2TP ) +点对点协 议 ( Point to Point Protocol, PPP )方案
该方案中，终端 UE通过承载在 L2TP上的 PPP协议建立了到 ePDG的 连接， 并通过承载在 L2TP上的 RSVP协议来管理资源， 图 6为现有技术方 案 3的协议栈示意图， 图 6所示流程与图 3和图 5所示流程类似。
二、 非 3GPP接入 EPC的架构二
移动运营商期望在不改变现有网络的基础上进行 internet数据本地分流 或者疏导， 避免大量数据路由至核心网所带来的网络拥塞和设备升级问题。 因此， 结合现有 3G/LTE网络架构和运营商需求，提出了如图 16和图 17所 示的数据分流架构。 其中， 图 16为 3G网络中数据分流方案的实现架构， 图 17为 LTE网络中数据分流方案的实现架构。表 1和表 2分别对网络架构 中的网元、 接口的名称、 功能、 釆用协议做了阐述说明。
英文缩写 英文全称及中文解释 网元功能解释
MS Mobile Subscriber, 移 3G网络中的用户终端设备
动用户
UTRAN Universal Terrestrial 包括 BSS( Base Station Subsystem,
Radio Access 基站子系统） 和 RNC(Radio Network Network, 通用陆地无 controller, 无线网络控制器）， 为用户 线接入网络 终端设备提供 3G接入
SGSN Serving GPRS Support GPRS 核心网网络的移动性管理
Node, 服务 GPRS支 单元， 负责用户的移动性和会话管理 持节点
GGSN Gateway GPRS 核心网对外的接口网关，为用户提供到 support Node , 网关 运营商自营业务网络或 Internet的访问 GPRS支持节点
UE User Equipment, 用户 LTE网络的用户终端设备
设备
E-UTRAN Evolved Universal 由 eNodeB组成， 为用户终端设备
Terrestrial Radio 提供 LTE网络的接入
Access Network, 演进
的通用陆地无线接入
网络
MME Mobility Management 用户签约数据在当前网络的存放
Entity, 移动性管理实 地点， 负责终端到网络的 NAS 层 体 (Non-Access Stratum,非接入层)信令管 理、用户空闲模式下的跟踪和寻呼管理 功能和承载管理
SGW/S-GW Serving Gateway,月良务 核心网到无线系统的网关，负责终 网关 端到核心网的用户面承载、终端空闲模 式下的数据緩存、网络侧发起业务请求 的功能、合法监听和分组数据路由和转 发功能 PGW PDN Gateway 演进的分组域系统 ( EPS )和该系 统外部网络的网关， 负责终端的 IP地 址分配、 计费功能、 分组包过滤、 策略 应用等功能 表 1
Figure imgf000008_0001
表 2
上述网络架构中， 综合服务网关（ ISGW )为数据分流方案中的新网元， 它融合了 GGSN或者 S-GW或者 P-GW的功能以及 GTP ( GPRS Tunneling Protocol, GPRS隧道协议）代理（ proxy)和 NAT( Network Address Translation, 网络地址转换） 网关功能。 ISGW位于用户数据传输路径上， 用于 internet 或者其它特定网络的数据分流。 ISGW 和网络中其它的标准化网元 （如 SGSN、 GGSN等）釆用标准接口进行连接， 两个 ISGW之间釆用新定义的 Gn，或者 S5，进行连接。 新定义的接口具有 GTP消息和用户数据转发功能， 具体名称暂未标准化。 因为 ISGW可以融合多个网元的功能， 在某些特定 的场景下， 它表现出来的身份可能仅仅是其中一个网元或者同时几个网元 的共同身份， 比如说， 在一个流程中， ISGW可能仅仅就是一个 S-GW, 或 者仅仅是一个 P-GW, 或者同时是 S-GW和 P-GW的身份。
ISGW执行数据分流原理如下： 在 3G网络中接入网络 UTRAN通过标 准 DT ( Direct Tunnel, 直接隧道）方式与 ISGW相连， 在 LTE网络中接入 网络 E-UTRAN通过标准 S1-U 与 ISGW相连， 用于将用户数据发送至 ISGW。 ISGW根据本地配置或者从策略服务器下发的用户分流策略进行数 据包处理， 将符合分流策略的数据 NAT地址转换后发送到 Internet或者其 它运营商外部网络， 将运营商希望控制的数据发送给核心网网关 GGSN或 者 P-GW路由至运营商自营业务网络。 上述数据分流方案也可以支持用户 从 non-3GPP接入， 此时需要 ISGW增加 TTG、 ePDG网元功能， 并且增加 ISGW和 PCRF之间的 Gx接口交互流迁移策略。
上述两种架构给出了 non-3GPP接入到 EPC的网络架构方案， 运营商 为了提供根据吸引力的业务功能和服务， 需要支持业务数据流在 3GPP和 non-3GPP接入之间的迁移。但目前并没有如何将上下行 IP流由非 3GPP接 入网 /3GPP接入网迁移到 3GPP接入网 /非 3GPP接入网的相关解决方案。 发明内容
有鉴于此， 本发明的主要目的在于提供一种实现流迁移的方法及系统， 能够实现非 3GPP接入网与 3GPP接入网之间的切换，提高系统灵活度及效 率。
为达到上述目的， 本发明的技术方案是这样实现的：
一种实现流迁移的方法， 该方法包括：
终端用户设备 UE/网络侧通过第三代合作伙伴计划 3GPP接入网或非 3GPP接入网请求网络侧 /终端 UE进行流迁移；
所述终端 UE和网络侧相应地将上下行 IP流由非 3GPP接入网迁移到 3GPP接入网， 或由 3GPP接入网迁移到非 3GPP接入网。
该方法具体为：
终端 UE通过非 3GPP接入网向网络侧演进的分组数据网关 ePDG发送 流迁移请求信令， 所述流迁移请求信令携带流迁移信息；
所述 ePDG向网络侧分组数据网络网关 P-GW发送 GTP消息，所述 GTP 消息携带流迁移信息；
所述终端 UE和所述 P-GW分别将上下行 IP流由 3GPP接入网迁移到 非 3GPP接入网或者由非 3GPP接入网迁移到 3GPP接入网。
该方法具体为：
终端 UE通过 3GPP接入网向移动管理单元 MME发送 NAS消息 , 所 述 NAS消息携带流迁移信息；
所述 MME向服务网关 S-GW、 所述 S-GW向 P-GW发送 GTP消息， 所述 GTP消息携带流迁移信息；
所述终端 UE和 P-GW分别将上下行 IP流由非 3GPP接入网迁移到 3GPP接入网或者由 3GPP接入网迁移到非 3GPP接入网。
该方法具体为：
网络侧 P-GW向 ePDG发送 GTP消息，所述 GTP消息携带流迁移信息； 所述 ePDG通过非 3GPP接入网向终端 UE发送流迁移请求信令，所述 流迁移请求信令携带流迁移信息；
所述终端 UE和 P-GW分别将上下行 IP流由 3GPP接入网迁移到非 3GPP接入网或者由非 3GPP接入网迁移到 3GPP接入网。
该方法具体为：
网络侧 P-GW向 S-GW、 S-GW向 MME发送 GTP消息， 所述 GTP消 息携带流迁移信息；
所述 MME通过 3GPP接入网向终端 UE发送 NAS消息， 所述 NAS 消息携带流迁移信息；
所述终端 UE和 P-GW分别将上下行 IP流由非 3GPP接入网迁移到 3GPP接入网或者由 3GPP接入网迁移到非 3GPP接入网。
该方法具体为：
终端 UE通过非 3GPP接入网向网络侧 ePDG发送流迁移请求信令，所 述流迁移请求信令携带流迁移信息；
所述 ePDG向网络侧 P-GW发送 PBU信令，所述 PBU信令携带流迁移 信息；
所述终端 UE和 P-GW分别将上下行 IP流由非 3GPP接入网迁移到 3GPP接入网或者由 3GPP接入网迁移到非 3GPP接入网。
所述流迁移请求信令为 RSVP消息、 NAS消息、 IKEv2消息或 SIP消 息。
所述 MME发送给 S-GW、 ePDG/S-GW发送给 P-GW的 GTP消息为承 载资源命令消息； 所述 P-GW发送给 ePDG/S-GW , S-GW发送给 MME的 GTP消息为承载建立 /修改 /更新请求消息； 所述 RSVP消息为 Resv消息； 所述 NAS消息为承载资源分配 /修改请求、 激活专有 EPS承载上下文请求 消息；所述 IKEv2消息为 IKE认证请求 /创建子安全联盟请求 /信息请求消息； 所述 SIP消息为邀请消息。
所述流迁移信息包括以下一种或几种： 接入标识、 流对应的 QoS信息、 流标识、 流级别、 流分组过滤器 /业务流模板、 流操作指示。
在实现所述流迁移之前，该方法还包括：所述终端 UE建立与所述 3GPP 接入网和所述非 3GPP接入网的多重绑定， 即终端 UE从所述 3GPP接入网 接入时建立的连接和从所述非 3GPP接入网接入时建立的连接同属一个 PDN连接的两条子路径， 共用相同 APN、 PDN地址、 IP-CAN会话。
所述终端 UE建立所述多重绑定的过程包括：
终端 UE接入所述 3GPP接入网和 /或非 3GPP接入网时，携带接入指示 给 P-GW; P-GW获取所述接入指示并建立所述终端 UE与所述 3GPP接入 网和非 3GPP接入网的多重绑定。
该方法具体为：
终端 UE与综合服务网关 ISGW交互， 请求进行流迁移；
终端 UE与 ISGW根据交互结果， 分别相应地将上下行数据流从 3GPP 接入网迁移到非 3GPP接入网，或分别相应地将上下行数据流从非 3GPP接 入网迁移到 3GPP接入网。
所述终端 UE与 ISGW交互是由 ISGW以触发的形式发起的； 或者， 是由终端 UE主动发起的。
由 ISGW以触发的形式发起的所述交互过程包括：
ISGW受触发， 决定发起流迁移， 并发送 SIP协议的邀请消息给终端 UE;终端 UE收到消息后将上行数据流从 3GPP接入网迁移到非 3GPP接入 网， 由 ISGW将下行数据流由 3GPP接入网切换到非 3GPP接入网；
或者， ISGW受触发， 决定发起流迁移， 并发送创建 /修改 /更新承载请 求消息给 MME/SGSN,由 MME/SGSN根据 ISGW的触发发送 NAS消息的 承载建立 /修改 /更新请求给终端 UE; 终端 UE根据收到的请求的触发将上 行数据流从 3GPP接入网迁移到非 3GPP接入网； ISGW将下行数据流由非 3GPP接入网切换到 3GPP接入网。
所述触发条件来自 PCRF的策略改变， 或者来自 P-GW/GGSN的请求， 或者网络负荷的改变， 导致 ISGW决定发起流迁移。
由终端 UE主动发起的所述交互过程包括：
终端 UE决定发起流迁移，并发送 SIP协议的邀请消息给 ISGW, ISGW 根据所述消息将下行数据流由 3GPP接入网切换到非 3GPP接入网， 终端 UE将上行数据流从 3GPP接入网迁移到非 3GPP接入网；
或者， 终端 UE决定发起流迁移， 并发送 NAS协议的请求承载资源修 改消息给 SGSN/MME , SGSN/MME 发送 GTP 协议的承载资源命令给 ISGW; ISGW切换数据流， 从非 3GPP接入网切换到 3GPP接入网， 终端 UE将上行数据流从非 3GPP接入网迁移到 3GPP接入网。
UE决定发起流迁移的触发条件来自用户的体验决定， 或是终端 UE从 策略服务器获取的相关策略，或者是终端 UE由于移动、无线覆盖发生变化 引起流迁移。
IP数据流的迁移时机为： 当有资源分配与承载建立操作时， 发生在资 源分配和承载建立成功后执行，或者在收到 SIP或者 NAS或者 GTP消息后 直接执行。
一种实现流迁移的系统， 该系统包括终端 UE和网络侧； 其中， 所述终端 UE, 用于通过 3GPP接入网或非 3GPP接入网请求网络侧进 行流迁移； 以及相应地将上行 IP流由非 3GPP接入网迁移到 3GPP接入网， 或由 3GPP接入网迁移到非 3GPP接入网；
所述网络侧， 用于根据所述终端 UE 的通知相应地将下行 IP 流由非
3GPP接入网迁移到 3GPP接入网， 或由 3GPP接入网迁移到非 3GPP接入 网。
所述终端 UE通过非 3GPP接入网请求网络侧进行流迁移时， 用于： 通过非 3GPP接入网向网络侧 ePDG发送流迁移请求信令，所述流迁移 请求信令携带流迁移信息；
所述 ePDG用于向网络侧 P-GW发送 GTP消息，所述 GTP消息携带流 迁移信息。
所述终端 UE通过 3GPP接入网请求网络侧进行流迁移时， 用于： 通过 3GPP接入网向移动管理单元 MME发送 NAS消息 ,所述 NAS消 息携带流迁移信息；
所述 MME用于通过 S-GW向 P-GW发送 GTP消息，所述 GTP消息携 带流迁移信息。
所述终端 UE通过非 3GPP接入网请求网络侧进行流迁移 ,以及相应地 将上行 IP流由非 3GPP接入网迁移到 3GPP接入网，或由 3GPP接入网迁移 到非 3GPP接入网时， 用于：
通过非 3GPP接入网向网络侧 ePDG发送流迁移请求信令，所述流迁移 请求信令携带流迁移信息；
所述 ePDG用于向网络侧 P-GW发送 PBU信令， 所述 PBU信令携带流 迁移信息；
所述终端 UE和 P-GW分别用于将上下行 IP流由非 3GPP接入网迁移 到 3GPP接入网或者由 3GPP接入网迁移到非 3GPP接入网。
所述网络侧包括 ISGW, 所述 ISGW融合了 GGSN、 S-GW或者 P-GW 的功能以及 GPRS隧道协议和 NAT网关功能；
所述终端 UE与 ISGW分别用于： 进行交互， 请求进行流迁移； 以及， 分别用于根据交互结果，分别相应地将上下行数据流从 3GPP接入网迁移到 非 3GPP接入网， 或分别相应地将上下行数据流从非 3GPP接入网迁移到 3GPP接入网。
所述终端 UE与 ISGW交互是由 ISGW以触发的形式发起的； 或者， 是由终端 UE主动发起的。
由 ISGW以触发的形式发起时， 所述 ISGW与终端 UE在交互时分别 用于：
ISGW受触发， 决定发起流迁移， 并发送 SIP协议的邀请消息给终端 UE;终端 UE收到消息后将上行数据流从 3GPP接入网迁移到非 3GPP接入 网， ISGW将下行数据流由 3GPP接入网切换到非 3GPP接入网； 或者， ISGW受触发， 决定发起流迁移， 并发送创建 /修改 /更新承载请 求消息给 MME/SGSN,由 MME/SGSN根据 ISGW的触发发送 NAS消息的 承载建立 /修改 /更新请求给终端 UE, 终端 UE根据收到的请求的触发将上 行数据流从 3GPP接入网迁移到非 3GPP接入网； ISGW将下行数据流由非 3GPP接入网切换到 3GPP接入网。
所述触发条件来自 PCRF的策略改变， 或者来自 P-GW/GGSN的请求， 或者网络负荷的改变时， 导致 ISGW决定发起流迁移。
由终端 UE主动发起所述交互时， 所述终端 UE与 ISGW分别用于： 终端 UE决定发起流迁移，并发送 SIP协议的邀请消息给 ISGW, ISGW 根据所述消息将下行数据流由 3GPP接入网切换到非 3GPP接入网， 终端 UE收到所述响应后将上行数据流从 3GPP接入网迁移到非 3GPP接入网； 或者， 终端 UE决定发起流迁移， 并发送 NAS协议的请求承载资源修 改消息给 SGSN/MME , SGSN/MME 发送 GTP 协议的承载资源命令给 ISGW;
ISGW根据收到的所述命令切换数据流，从非 3GPP接入网切换到 3GPP 接入网 , 终端 UE将上行数据流从非 3GPP接入网迁移到 3GPP接入网。
UE决定发起流迁移的触发条件来自用户的体验决定， 或是终端 UE从 策略服务器获取的相关策略，或者是终端 UE由于移动、无线覆盖发生变化 引起流迁移。
IP数据流的迁移时机为： 当有资源分配与承载建立操作时， 发生在资 源分配和承载建立成功后执行，或者在收到 SIP或者 NAS或者 GTP消息后 直接执行。
一种实现流迁移的系统， 该系统包括终端 UE和网络侧； 其中， 所述网络侧， 用于通过 3GPP接入网或非 3GPP接入网请求终端 UE进 行流迁移； 以及相应地将下行 IP流由非 3GPP接入网迁移到 3GPP接入网， 或由 3GPP接入网迁移到非 3GPP接入网；
所述终端 UE, 用于根据所述网络侧的通知相应地将上行 IP 流由非 3GPP接入网迁移到 3GPP接入网， 或由 3GPP接入网迁移到非 3GPP接入 网。
所述网络侧包括网络侧 P-GW , 所述网络侧 P-GW在通过非 3GPP接入 网请求终端 UE进行流迁移时， 用于：
向 ePDG发送 GTP消息， 所述 GTP消息携带流迁移信息；
所述 ePDG用于通过非 3GPP接入网向终端 UE发送流迁移请求信令， 所述流迁移请求信令携带流迁移信息。
所述网络侧包括网络侧 P-GW， 所述网络侧 P-GW在通过 3GPP接入网 请求终端 UE进行流迁移时， 用于：
通过 S-GW向 MME发送 GTP消息， 所述 GTP消息携带流迁移信息； 所述 MME用于通过 3GPP接入网向终端 UE发送 NAS消息 ,所述 NAS 消息携带流迁移信息。
所述网络侧包括 ISGW, 所述 ISGW融合了 GGSN、 S-GW或者 P-GW 的功能以及 GPRS隧道协议和 NAT网关功能；
所述终端 UE与 ISGW分别用于： 进行交互， 请求进行流迁移； 以及， 分别用于根据交互结果，分别相应地将上下行数据流从 3GPP接入网迁移到 非 3GPP接入网， 或分别相应地将上下行数据流从非 3GPP接入网迁移到 3GPP接入网。
所述终端 UE与 ISGW交互是由 ISGW以触发的形式发起的； 或者， 是由终端 UE主动发起的。
由 ISGW以触发的形式发起时， 所述 ISGW与终端 UE在交互时分别 用于： ISGW受触发， 决定发起流迁移， 并发送 SIP协议的邀请消息给终端 UE;终端 UE收到消息后将上行数据流从 3GPP接入网迁移到非 3GPP接入 网， ISGW将下行数据流由 3GPP接入网切换到非 3GPP接入网；
或者， ISGW受触发， 决定发起流迁移， 并发送创建 /修改 /更新承载请 求消息给 MME/SGSN ,由 MME/SGSN根据 ISGW的触发发送 NAS消息的 承载建立 /修改 /更新请求给终端 UE, 终端 UE根据收到的请求的触发将上 行数据流从 3GPP接入网迁移到非 3GPP接入网； ISGW将下行数据流由非 3GPP接入网切换到 3GPP接入网。
所述触发条件来自 PCRF的策略改变， 或者来自 P-GW/GGSN的请求， 或者网络负荷的改变时， 导致 ISGW决定发起流迁移。
由终端 UE主动发起所述交互时， 所述终端 UE与 ISGW分别用于： 终端 UE决定发起流迁移，并发送 SIP协议的邀请消息给 ISGW, ISGW 根据所述消息将下行数据流由 3GPP接入网切换到非 3GPP接入网， 终端 UE将上行数据流从 3GPP接入网迁移到非 3GPP接入网；
或者， 终端 UE决定发起流迁移， 并发送 NAS协议的请求承载资源修 改消息给 SGSN/MME , SGSN/MME 发送 GTP 协议的承载资源命令给 ISGW;
ISGW根据收到的所述命令切换数据流，从非 3GPP接入网切换到 3GPP 接入网 , 终端 UE将上行数据流从非 3GPP接入网迁移到 3GPP接入网。
UE决定发起流迁移的触发条件来自用户的体验决定， 或是终端 UE从 策略服务器获取的相关策略，或者是终端 UE由于移动、无线覆盖发生变化 引起流迁移。
IP数据流的迁移时机为： 当有资源分配与承载建立操作时， 发生在资 源分配和承载建立成功后执行，或者在收到 SIP或者 NAS或者 GTP消息后 直接执行。 本发明实现流迁移的方法及系统，终端 UE/网络侧通过 3GPP接入网或 非 3GPP接入网请求网络侧 /终端 UE进行流迁移；所述终端 UE和网络侧相 应地将上下行 IP流由非 3GPP接入网迁移到 3GPP接入网，或由 3GPP接入 网迁移到非 3GPP接入网。 本发明能够实现非 3GPP接入网与 3GPP接入网 之间的流的迁移， 从而能够提高系统灵活度及效率。 附图说明
图 1为不可信任非 3GPP接入网接入的 EPS的架构示意图；
图 2为现有技术方案 1的协议栈示意图；
图 3为现有技术方案 1的终端 UE通过 ePDG接入 EPC的流程示意图； 图 4为现有技术方案 2的协议栈示意图；
图 5为现有技术方案 2的用户接入网络的方法流程图；
图 6为现有技术方案 3的协议栈示意图；
图 7为本发明实施例 1终端 UE在非 3GPP接入网中发起流迁移操作， 将 3GPP接入网中的业务流迁移到该非 3GPP接入网的实现流迁移的方法流 程示意图 （终端 UE向 ePDG发送的流迁移请求信令为 IKEv2消息）；
图 8为本发明实施例 1终端 UE在非 3GPP接入网中发起流迁移操作， 将 3GPP接入网中的业务流迁移到该非 3GPP接入网的实现流迁移的方法流 程示意图 （终端 UE向 ePDG发送的流迁移请求信令为 SIP消息）；
图 9为本发明实施例 1终端 UE在非 3GPP接入网中发起流迁移操作， 将 3GPP接入网中的业务流迁移到该非 3GPP接入网的实现流迁移的方法流 程示意图 （终端 UE向 ePDG发送的流迁移请求信令为 RSVP消息）；
图 10为本发明实施例 1终端 UE将业务流从非 3GPP接入网迁移到 3GPP接入网的流程示意图；
图 11为本发明实施例 1网络侧在非 3GPP接入网中发起流迁移操作， 将 3GPP接入网中的业务流迁移到该非 3GPP接入网的实现流迁移的方法流 程示意图 （ ePDG向终端 UE发送的流迁移请求信令为 IKEv2消息）； 图 12为本发明实施例 1网络侧在非 3GPP接入网中发起流迁移操作， 将 3GPP接入网中的业务流迁移到该非 3GPP接入网的实现流迁移的方法流 程示意图 （终端 UE向 ePDG发送的流迁移请求信令为 RSVP消息）；
图 13为本发明实施例 1网络侧在非 3GPP接入网中发起流迁移操作， 将 3GPP接入网中的业务流迁移到该非 3GPP接入网的实现流迁移的方法流 程示意图 （终端 UE向 ePDG发送的流迁移请求信令为 SIP消息）；
图 14为本发明实施例 1网络侧 P-GW将业务流从非 3GPP接入网迁移 到 3GPP接入网的流程示意图；
图 15为本发明实施例 3终端 UE将业务流从非 3GPP接入网迁移到
3GPP接入网的流程示意图；
图 16为 3G网络中数据分流方案的实现架构示意图；
图 17为 LTE网络中数据分流方案的实现架构示意图；
图 18为网络发起的流迁移 （ 3GPP迁往非 3GPP ) 的流程图；
图 19为网络发起的流迁移 （非 3GPP迁往 3GPP ) 的流程图； 图 20为终端 UE发起的流迁移（ 3GPP迁往非 3GPP或者反向迁移 )的 流程图；
图 21为终端 UE发起的流迁移 （非 3GPP迁往 3GPP ) 的流程图； 图 22为本发明实施例的实现流迁移的流程简图。 具体实施方式
本发明的基本思想是：终端用户设备 UE/网络侧通过第三代合作伙伴计 划 3GPP接入网或非 3GPP接入网请求网络侧 /终端 UE进行流迁移；所述终 端 UE和网络侧相应地将上下行 IP流由非 3GPP接入网迁移到 3GPP接入网， 或由 3GPP接入网迁移到非 3GPP接入网。
本发明基于非 3GPP接入 EPC的架构一时， 主要涉及以下五种情况： 1 )终端 UE通过非 3GPP接入网向 ePDG发送流迁移请求信令， 所述 流迁移请求信令携带流迁移信息； ePDG向 P-GW发送 GTP消息 （如承载 资源命令 ), 该 GTP消息携带流迁移信息； 终端 UE和 P-GW分别将上下行 IP流由 3GPP接入网迁移到非 3GPP接入网或者由非 3GPP接入网迁移到 3GPP接入网。
2 )终端 UE通过 3GPP接入网向 MME发送 NAS消息 , 所述 NAS消 息携带流迁移信息； MME向 S-GW, S-GW向 P-GW发送 GTP消息（如承 载资源命令）， 该 GTP消息携带流迁移信息； 终端 UE和 P-GW分别将上下 行 IP流由非 3GPP接入网迁移到 3GPP接入网或者由 3GPP接入网迁移到非 3GPP接人网。
3 )终端 UE通过非 3GPP接入网向网络侧 ePDG发送流迁移请求信令， 所述流迁移请求信令携带流迁移信息；所述 ePDG向网络侧 P-GW发送 PBU 信令， 所述 PBU信令携带流迁移信息； 所述终端 UE和 P-GW分别将上下 行 IP流由非 3GPP接入网迁移到 3GPP接入网或者由 3GPP接入网迁移到非 3GPP接入网。
4 )网络侧 P-GW向 ePDG发送 GTP消息（如承载建立 /修改 /更新请求；)， 所述 GTP消息携带流迁移信息； ePDG通过非 3GPP接入网向终端 UE发送 流迁移请求信令，该流迁移请求信令携带流迁移信息； 终端 UE和 P-GW分 别将上下行 IP流由 3GPP接入网迁移到非 3GPP接入网或者由非 3GPP接入 网迁移到 3GPP接入网。
5 ) 网络侧 P-GW向 S-GW, S-GW向 MME发送 GTP消息（如承载建 立 /修改 /更新请求）， 所述 GTP消息携带流迁移信息； MME通过 3GPP接 入网向终端 UE发送 NAS消息 , 该 NAS消息携带流迁移信息； 终端 UE和 P-GW分别将上下行 IP流由非 3GPP接入网迁移到 3GPP接入网或者由 3GPP接入网迁移到非 3GPP接入网。 需要说明的是， P-GW收到承载建立 /修改请求后， 会与 PCRF交互并 发起动态 PCC过程， 新建 /修改承载。
本发明基于非 3GPP接入 EPC的架构二时， 主要涉及以下四种情况：
1 )终端 UE通过非 3GPP接入网向 ISGW发送流迁移请求信令， 所述 流迁移请求信令携带流迁移信息； 终端 UE和 ISGW分别将上下行 IP流由
3GPP接入网迁移到非 3GPP接入网或者由非 3GPP接入网迁移到 3GPP接 入网。
2 )终端 UE通过 3GPP接入网向 ISGW发送流迁移请求信令， 所述流 迁移请求信令携带流迁移信息； 终端 UE和 ISGW分别将上下行 IP流由 3GPP接入网迁移到非 3GPP接入网或者由非 3GPP接入网迁移到 3GPP接 入网；
或者 , 终端 UE通过 3GPP接入网向 MME发送 NAS消息 , 所述 NAS 消息携带流迁移信息； MME向 ISGW发送 GTP消息 （如承载资源命令）， 该 GTP消息携带流迁移信息； 终端 UE和 ISGW分别将上下行 IP流由非 3GPP接入网迁移到 3GPP接入网或者由 3GPP接入网迁移到非 3GPP接入 网；
3 )网络侧 ISGW通过非 3GPP接入网向终端 UE发送流迁移请求信令， 该流迁移请求信令携带流迁移信息； 终端 UE和 ISGW分别将上下行 IP流 由 3GPP接入网迁移到非 3GPP接入网或者由非 3GPP接入网迁移到 3GPP 接入网。
4 ) 网络侧 ISGW通过 3GPP接入网向终端 UE发送流迁移请求信令， 该流迁移请求信令携带流迁移信息； 终端 UE和 ISGW分别将上下行 IP流 由 3GPP接入网迁移到非 3GPP接入网或者由非 3GPP接入网迁移到 3GPP 接入网；
或者， 网络侧 ISGW向 MME发送 GTP消息（如承载建立 /修改 /更新请 求 ), 所述 GTP消息携带流迁移信息； MME通过 3GPP接入网向终端 UE 发送 NAS消息，该 NAS消息携带流迁移信息； 终端 UE和 ISGW分别将上 下行 IP流由非 3GPP接入网迁移到 3GPP接入网或者由 3GPP接入网迁移到 非 3GPP接入网。
需要说明的是， ISGW 收到承载建立 /修改请求后， 可能会与
P-GW/SGSN交互 GTP/PMIP消息， 以及与 PCRF交互并发起动态 PCC过 程， 以新建 /修改承载。
针对以上两种架构的不同场景而言， 所述流迁移信息包括以下一种或 几种： 接入标识（ AID ), 流对应的 QoS信息、 流标识（ Flow Identity, FID )、 流级别、 流分组过滤器 （Packet Filter , PF ) /业务流模板 ( Traffic Flow Template, TFT ), 流操作指示等。
上述流迁移请求信息可以是 RSVP消息、 NAS消息、 IKEv2消息或 SIP 消息等。
为了实现本发明方法， 终端 UE需要建立与 3GPP接入网和非 3GPP接 入网的多重绑定， 所述的多重绑定为： 终端 UE从 3GPP接入时建立的连接 和从非 3GPP接入时建立的连接同属一个 "PDN连接" 的两条 "子路径"， 共用相同 APN, PDN地址， IP-CAN会话。 具体的， 终端 UE按照现有的 技术接入第一个网络（附着 /PDN连接建立 ),终端 UE在接入第二网络并发 起同一个 PDN连接的多重绑定时， 可以携带 "接入指示 （ Access Identify, AID )" 给 ISGW/P-GW, ISGW/P-GW获取该 AID, 才能建立与 3GPP接入 网和非 3GPP接入网的多重绑定； 也可以在终端 UE接入第一个网络时， 携 带 AID, 或者从两个网络接入时都携带同一个或者不同的 AID, 只要终端 UE从第二个网络接入时， ISGW/P-GW能够断定该 PDN连接是多绑定连接 即可。
在建立了多重绑定关系之后， 之后的流迁移 /更新 /删除 /新建等操作中， 只要终端 UE/网络侧在某一个网络中发起操作请求，就代表终端 UE/网络侧 需要向该网络迁移数据流， 或者在该网络中更新 /删除 /新建数据流， 无需携 带 AID。
需要说明的是， AID起到指示 ISGW/P-GW要进行多重绑定的作用， 即 AID只是个名称而已， 也可以釆用其他的名称。
本发明还提出一种实现流迁移的系统， 该系统包括终端 UE和网络侧； 其中，所述终端 UE与 ISGW分别用于： 进行交互，请求进行流迁移； 以及， 分别用于根据交互结果，分别相应地将上下行数据流从 3GPP接入网迁移到 非 3GPP接入网， 或分别相应地将上下行数据流从非 3GPP接入网迁移到 3GPP接入网。
所述终端 UE与 ISGW交互是由 ISGW以触发的形式发起的； 或者， 是由终端 UE主动发起的。
由 ISGW以触发的形式发起时， 所述 ISGW与终端 UE在交互时分别 用于：
ISGW受触发， 决定发起流迁移， 并发送 SIP协议的邀请消息给终端 UE;终端 UE收到消息后将上行数据流从 3GPP接入网迁移到非 3GPP接入 网， 并通知 ISGW, 由 ISGW根据所述通知将下行数据流由 3GPP接入网切 换到非 3GPP接入网；
或者， ISGW受触发， 决定发起流迁移， 并发送创建 /修改 /更新承载请 求消息给 MME/SGSN,由 MME/SGSN根据 ISGW的触发发送 NAS消息的 承载建立 /修改 /更新请求给终端 UE, 并通知 ISGW;
终端 UE根据收到的请求的触发将上行数据流从 3GPP接入网迁移到非 3GPP接入网； ISGW根据所述通知将下行数据流由非 3GPP接入网切换到 3GPP接入网。
所述触发条件来自 PCRF的策略改变， 或者来自 P-GW/GGSN的请求， 或者网络负荷的改变时， 导致 ISGW决定发起流迁移。
由终端 UE主动发起所述交互时， 所述终端 UE与 ISGW分别用于： 终端 UE决定发起流迁移，并发送 SIP协议的邀请消息给 ISGW, ISGW 根据所述消息将下行数据流由 3GPP接入网切换到非 3GPP接入网，并向终 端 UE反馈响应； 终端 UE收到所述响应后将上行数据流从 3GPP接入网迁 移到非 3GPP接入网；
或者， 终端 UE决定发起流迁移， 并发送 NAS协议的请求承载资源修 改消息给 SGSN/MME , SGSN/MME 发送 GTP 协议的承载资源命令给
ISGW;
ISGW根据收到的所述命令切换数据流，从非 3GPP接入网切换到 3GPP 接入网， 并发送 GTP协议的创建 /修改 /更新承载请求消息给 SGSN/MME, SGSN/MME发送 NAS协议的承载建立 /修改 /更新请求给终端 UE,终端 UE 根据收到的所述请求将上行数据流从非 3GPP接入网迁移到 3GPP接入网。
UE决定发起流迁移的触发条件来自用户的体验决定， 或是终端 UE从 策略服务器获取的相关策略，或者是终端 UE由于移动、无线覆盖发生变化 引起流迁移。
IP数据流的迁移时机为： 当有资源分配与承载建立操作时， 发生在资 源分配和承载建立成功后执行，或者在收到 SIP或者 NAS或者 GTP消息后 直接执行。
所述终端 UE, 用于通过 3GPP接入网或非 3GPP接入网请求网络侧进 行流迁移； 以及相应地将上行 IP流由非 3GPP接入网迁移到 3GPP接入网， 或由 3GPP接入网迁移到非 3GPP接入网；
所述网络侧， 用于根据所述终端 UE 的通知相应地将下行 IP 流由非 3GPP接入网迁移到 3GPP接入网， 或由 3GPP接入网迁移到非 3GPP接入 网。 所述终端 UE通过非 3GPP接入网请求网络侧进行流迁移为：
所述终端 UE通过非 3GPP接入网向网络侧 ePDG发送流迁移请求信令， 所述流迁移请求信令携带流迁移信息；
所述 ePDG向网络侧 P-GW发送 GTP消息，所述 GTP消息携带流迁移 信息。
所述终端 UE通过 3GPP接入网请求网络侧进行流迁移为：
所述终端 UE通过 3GPP接入网向移动管理单元 MME发送 NAS消息 , 所述 NAS消息携带流迁移信息；
所述 MME向 S-GW、 所述 S-GW向 P-GW发送 GTP消息 , 所述 GTP 消息携带流迁移信息。
所述终端 UE通过非 3GPP接入网请求网络侧进行流迁移，以及相应地 将上行 IP流由非 3GPP接入网迁移到 3GPP接入网，或由 3GPP接入网迁移 到非 3GPP接入网为：
所述终端 UE通过非 3GPP接入网向网络侧 ePDG发送流迁移请求信令， 所述流迁移请求信令携带流迁移信息；
所述 ePDG向网络侧 P-GW发送 PBU信令，所述 PBU信令携带流迁移 信息；
所述终端 UE和 P-GW分别将上下行 IP流由非 3GPP接入网迁移到 3GPP接入网或者由 3GPP接入网迁移到非 3GPP接入网。
本发明还提出一种实现流迁移的系统， 该系统包括终端 UE和网络侧； 其中，
所述网络侧，用于通过第三代合作伙伴计划 3GPP接入网或非 3GPP接 入网请求终端 UE进行流迁移； 以及相应地将下行 IP流由非 3GPP接入网 迁移到 3GPP接入网， 或由 3GPP接入网迁移到非 3GPP接入网；
所述终端 UE, 用于根据所述网络侧的通知相应地将上行 IP 流由非 3GPP接入网迁移到 3GPP接入网， 或由 3GPP接入网迁移到非 3GPP接入 网。
所述网络侧通过非 3GPP接入网请求终端 UE进行流迁移为： 所述网络侧 P-GW向 ePDG发送 GTP消息，所述 GTP消息携带流迁移 信息；
所述 ePDG通过非 3GPP接入网向终端 UE发送流迁移请求信令，所述 流迁移请求信令携带流迁移信息。
所述网络侧通过 3GPP接入网请求终端 UE进行流迁移为：
所述网络侧 P-GW向 S-GW、 S-GW向 MME发送 GTP消息，所述 GTP 消息携带流迁移信息；
所述 MME通过 3GPP接入网向终端 UE发送 NAS消息 , 所述 NAS消 息携带流迁移信息。
下面结合具体实施例对技术方案的实施作进一步的详细描述。
其中， 实施例 1-3均基于非 3GPP接入 EPC的架构一， 实施例 4基于 非 3GPP接入 EPC的架构二。
实施例 1
本实施例中， 终端 UE首先在 3GPP接入网中附着， 建立了一个或者多 个 PDN连接； 之后， 终端 UE又在非 3GPP接入网中发起了附着 /PDN连接 建立操作 （如图 3、 5所示）， 实现同一个 PDN连接的多重绑定。
在步骤 301-302、 步骤 501-502中， 终端 UE在建立同一个 PDN连接的 多重绑定时， 携带了 "接入指示 ( Access Identify, AID )"给 P-GW, P-GW 获取该 AID , 建立与 3GPP接入网和非 3GPP接入网的多重绑定。
P-GW在收到 ePDG发送来的创建会话请求消息， 并解析出 AID后， 与 ePDG建立 GTP隧道， 并保持 P-GW与 S-GW的 GTP隧道。 P-GW在向 ePDG返回的 "创建会话应答" 消息中， 将已经为终端 UE分配的 IP地址 通过 ePDG再次返回给终端 UE。
需要说明的是， 终端 UE也可以先在非 3GPP接入网接入， 再从 3GPP 接入网接入，建立多重绑定。从非 3GPP接入网接入的流程参见图 5及其描 述， 该操作中， 没有携带 AID; 之后向 3GPP接入网接入的流程参见现有的 3GPP附着 /PDN连接建立操作， 不同之处在于， UE发给 MME的 NAS消 息、 MME发给 S-GW、 S-GW发给 P-GW的创建会话请求消息中携带了 AID。 具体的， AID的用途和 P-GW接收到该参数后的操作， 参见上面的非 3GPP 接入部分描述， 机制相同。
终端 UE发起流迁移操作的情况下， 终端 UE发送流迁移请求信令 ( IKEv2消息或者是 SIP消息或者 RS VP消息）并携带流迁移信息给 ePDG , ePDG向 P-GW发送承载资源命令并携带流迁移信息， P-GW收到承载资源 命令后， 在非 3GPP接入网中发起承载创建 /修改 /更新操作， 终端 UE将上 行数据流由 3GPP接入网切换到非 3GPP接入网， P-GW将下行数据流由 3GPP接入网切换到非 3GPP接入网，该方法使用的前提是，终端 UE在 3GPP 接入网和非 3GPP接入网都已经附着， 并建立了一个或者多个 PDN连接， 并且实现了多重绑定。
所述的终端 UE发送给 ePDG、 ePDG发送给 P-GW的流迁移信息为以 下信息中的一种或者几种： 业务流对应的 QoS 信息、 业务流标识 （Flow Identity, FID ), 业务流级别、 业务流对应的 PF ( Packet Filter, 分组过滤器） /TFT ( Traffic Flow Template, 业务流模板）、 业务流操作指示、 接入标识 ( AID )。
所述的业务流操作指示指的是对该流执行的操作， 例如迁移、 新建、 修改、 删除、 更新等。
举例来说， 终端 UE发起流迁移时， 可以只携带流标识（ FID )和操作 指示 （例如流迁移指示）， 4艮据对应的流标识， P-GW就能判断终端 UE要 迁移的业务流；如果 P-GW不能辨识该业务流标识，拒绝了终端 UE的请求， 终端 UE可以再通过发送业务流对应的 PF/TFT来请求迁移该业务流； 如果 终端 UE发送的 PF/TFT, 在 P-GW也无法辨识， P-GW拒绝了终端 UE的 请求， 终端 UE可以发送业务流对应的 QoS, 请求新建该业务流的承载。 终 端 UE还可以同时发起多个业务流的操作， 并指明这几个业务流的优先级， 用于保证建立的次序和优先次序。 其中业务流操作指示可以是： 迁移、 新 建、 删除、 修改更新等。
上述只是举例说明，具体的实现可以取决了系统，只要终端 UE携带上 述信息中的一种或者几种， 能够描述该业务流并指示其操作， 就是一种具 体实现。
图 7、 图 8、 图 9分别为本发明实施例 1终端 UE在非 3GPP接入网中 发起流迁移操作，将 3GPP接入网中的业务流迁移到该非 3GPP接入网的实 现流迁移的方法流程示意图， 不同之处在于， 图 7 所示方法中， 终端 UE 向 ePDG发送的流迁移请求信令为 IKEv2消息、 图 8所示方法中， 终端 UE 向 ePDG发送的流迁移请求信令为 SIP消息， 图 9所示方法中， 终端 UE向 ePDG发送的流迁移请求信令为 RSVP消息， 下面以图 7为例进行说明， 图 7所示的方法包括：
步骤 700: 终端 UE在 3GPP接入网和非 3GPP接入网都已经附着， 并 建立了一个或者多个 PDN连接， 并且实现 PDN连接的多绑定。
步骤 701： 终端 UE向 ePDG发送 IKEv2认证消息 , 但该操作不对终端
UE进行认证。 该消息中携带流迁移信息， 用于指示要迁移的 IP流。
具体的 IKEv2 Request消息可以是以下消息中的一种。并且不排除其他 消息： IKE_AUTH Request ( IKE认证请求）、 Creat_child_SA Request (创建 子安全联盟请求， SA, Security Association,安全联盟 ), Informational Request (信息请求）。 同样， 步骤 704的 IKEv2 response消息也可以是 IKE_AUTH Response ( IKE认证响应）、 Creat_child_SA Response (创建子安全联盟响应， SA, Security Association, 安全联盟), Informational Response (信息响应)。 下同。
流迁移信息可以通过上述消息（特别是 Informational Request消息） 中 增力口或者扩展 Notify Payload (通知有效载荷 )或者 Configuration Payload (配置有效载荷）或者其他信元携带。
步骤 702: ePDG向 P-GW发送承载资源命令，并携带所述流迁移信息。 流迁移信息在 GTP消息中可以通过现有信元携带， 也可以通过增设新 的信元携带， 或者两种方法都釆用。 比如说， 现有的 GTP协议就支持携带 QoS信息等， 可以通过现有的 QoS对应的信元携带。 下同。
步骤 703: P-GW收到步骤 702中的消息后发送 "创建 /修改 /更新承载 请求" 消息给 ePDG。 该消息为现有消息， 可以不做特殊增强和修改。
步骤 704: ePDG发送 IKEv2消息给终端 UE,通知终端 UE网关 P-GW 接受流迁移请求。
终端 UE收到请求后将上行数据流从 3GPP接入网迁移到非 3GPP接入 网。
需要说明的是， UE可以在发送 701步的时候就切换数据流。 另外作为 优化方式， 如果步骤 705执行， 终端 UE可以切换数据流发生在步骤 705 之后；如果步骤 705不执行，终端 UE可以切换数据流发生在步骤 704之后。 下同。
步骤 705:如果非 3GPP接入网中支持资源预留 /承载建立机制，非 3GPP 接入网根据步骤 703步下载的 QoS信息创建 /修改 /更新承载，为新业务预留 资源； 如果非 3GPP接入网不支持资源预留 /承载建立机制， 则该步骤不执 行。
步骤 706: ePDG向 P-GW回复 "创建 /修改 /更新承载响应 "，通知 P-GW 切换业务流。
步骤 707: P-GW收到步骤 706的消息后， 将下行数据流由 3GPP接入 网切换到非 3GPP接入网。
需要说明的是 P-GW在收到 ePDG的 "，， 承载资源命令 "后就可以切 换数据流。 作为优化的方式， 可以釆用上述方式， 等收到步骤 706 中的消 息后在切换数据流。 下同。
P-GW在完成流切换操作后， 将在 3GPP接入系统中发起承载删除 /修 改 /资源释放操作， 删除原来业务流在 3GPP接入网所用的承载。 具体流程 参见现有技术的 P-GW在 3GPP系统中发起的资源修改 /去激活流程。
需要说明的是，在终端 UE和 ePDG之间釆用的是 SIP(图 8 )或者 RSVP
(图 9 )信令时， 终端 UE会向 ePDG发送 SIP: invite (邀请） 消息或者 RSVP: Resv(Reservation, 预留）消息， 该消息中携带流迁移信息， 用于指 示要迁移的 IP流。 当 P-GW向 ePDG发送 "创建 /修改 /更新承载请求" 后， ePDG向终端 UE回复 SIP: 200 OK消息或者 ResvCon Reservation confirm, 预留确认） 消息， 通知终端 UE网关 P-GW已经接受流迁移请求。 下同。
需要说明的是， UE也可以将业务流从非 3GPP接入网迁移到 3GPP接 入网中， 具体的流程图参见图 10。 与图 7、 8、 9的不同之处在于承载流迁 移信息的信令不同， 中间经过的网元不同； 业务流迁移的机制、 P-GW的功 能都是类似的。
网络侧发起的流迁移操作的情况下，网络侧 P-GW在非 3GPP接入网中 发起流迁移操作， 将 3GPP接入网中的业务流迁移到该非 3GPP接入网， 该 方法中， 终端 UE在 3GPP接入网和非 3GPP接入网都已经附着 , 并建立了 一个或者多个 PDN连接， 并且实现了多重绑定。
网络侧 P-GW受到触发， 发送 "创建 /修改 /更新承载请求" 并携带流迁 移信息给 ePDG, ePDG向终端 UE发送流迁移信令 (是 IKEv2消息或者是 SIP消息或者 RSVP消息）并携带流迁移信息，终端 UE收到流迁移信息后， 将上行数据流由 3GPP接入网切换到非 3GPP接入网， P-GW在收到 "创建 /修改 /更新承载响应" 后， 将下行数据流由 3GPP接入网切换到非 3GPP接 入网。
上述 ePDG发送给 P-GW的消息 "承载资源命令" 消息， P-GW发送给 ePDG的 "创建 /修改 /更新承载请求" 消息， ePDG发送给 P-GW的 "创建 / 修改 /更新承载响应" 消息都是 GTP消息的一条特定消息， 上述方案只是一 种特定实现。 具体实现时也可以釆用 GTP消息族的其他消息。 下述实施例 同。
图 11、 图 12、 图 13分别为本发明实施例 1网络侧在非 3GPP接入网中 发起流迁移操作，将 3GPP接入网中的业务流迁移到该非 3GPP接入网的实 现流迁移的方法流程示意图， 不同之处在于， 图 11所示方法中， ePDG向 终端 UE发送的流迁移请求信令为 IKEv2消息、 图 12所示方法中， 终端 UE向 ePDG发送的流迁移请求信令为 RSVP消息， 图 13所示方法中， 终 端 UE向 ePDG发送的流迁移请求信令为 SIP消息， 下面以图 11为例进行 说明， 图 11所示的方法包括：
步骤 1000: 终端 UE在 3GPP接入网和非 3GPP接入网都已经附着， 并 建立了一个或者多个 PDN连接， 并实现了多绑定。
步骤 1001 : P-GW受触发， 决定发起流迁移。
步骤 1002: P-GW发送 "创建 /修改 /更新承载请求" 消息给 ePDG并携 带流迁移信息， 用于指示要迁移的 IP流。
步骤 1003: ePDG发送 IKEv2证消息给终端 UE, 该消息中携带流迁移 信息， 用于指示要迁移的 IP流。
终端 UE收到消息后将上行数据流从 3GPP接入网迁移到非 3GPP接入 网。 需要说明的是,如果步骤 1004步执行，终端 UE切换数据流发生在 1004 之后； 如果 1004不执行， 终端 UE切换数据流发生在步骤 1003之后。
步骤 1004: 如果非 3GPP接入网中支持资源预留 /承载建立机制， 非 3GPP接入网根据步骤 1003步下载的 QoS信息创建承载， 与新业务预留资 源； 如果非 3GPP接入网不支持资源预留 /承载建立机制， 则该步骤不执行。
步骤 1005: ePDG向 P-GW回复"创建 /修改 /更新承载响应"，通知 P-GW 切换业务流。
步骤 1006: P-GW收到步骤 1006的消息后， 将下行数据流由 3GPP接 入网切换到非 3GPP接入网。
P-GW在完成流切换操作后， 将在 3GPP接入系统中发起承载删除 /修 改 /资源释放操作， 删除原来业务流在 3GPP接入网所用的承载。 具体流程 参见现有技术的 P-GW在 3GPP系统中发起的资源修改 /去激活流程。
需要说明的是， 在终端 UE和 ePDG之间釆用的是 SIP (图 13 )或者
RSVP(图 12 M言令时， ePDG会向终端 UE发送 SIP: invite消息或者 RSVP: Resv消息， 该消息中携带流迁移信息， 用于指示要迁移的 IP流。 终端 UE 向 ePDG回复 SIP: 200 OK消息或者 ResvConf消息 , 通知网络侧已经接受 流迁移请求。
需要说明的是， P-GW也可以将业务流从非 3GPP接入网迁移到 3GPP 接入网中， 如图 14所示， 具体的流程图与图 11、 12、 13类似， 不同之处 在于承载流迁移信息的信令不同， 中间经过的网元不同； 业务流迁移的机 制、 P-GW的功能都是类似的。
终端 UE发起业务请求（建立、 修改、 删除）的情况， 与终端 UE发起 流迁移操作的情况类似， 但也有不同之处， 具体在于：
流描述中的业务流操作指示对应的改为建立、 修改、 删除；
终端 UE和 P-GW不执行流切换操作， 而且对应的建立、修改、删除业 务数据流对应的 PF/TFT和 7 载；
P-GW不再发起源网络中的承载删除 /资源释放。
网络侧发起业务请求 （建立、 修改、 删除） 的情况， 与网路侧发起流 迁移操作的情况类似， 但也有不同之处， 具体在于：
流描述中的业务流操作指示对应的改为建立、 修改、 删除；
终端 UE和 P-GW不执行流切换操作， 而且对应的建立、修改、删除业 务数据流对应的 PF/TFT和 7 载；
P-GW不再发起源网络中的承载删除 /资源释放。
上述为实施例 1 的具体实现， 需要特别说明的是在该是实例中， 终端 UE如果在要向某个网络迁移业务流或者在某个网络中建立 /删除 /修改 /更新 业务流， 就到相应网络发起对应的操作。 举例来说， 如果终端 UE要向非 3GPP网络迁移业务流， 终端就需要通过 ePDG向 P-GW发送流迁移请求。
实施例 2
本实施例中， 终端 UE无论在接入第一个网络发起附着 /PDN连接建立 时， 还是在接入第二网络发起同一个 PDN连接的多重绑定时， 都需要携带 不同的 AID。 例如， 终端 UE首先接入 3GPP接入网， 建立的第一个 PDN 连接时， 为其分配 AID-1 , 终端 UE在第二网络中发起该 PDN连接的多重 绑定时， 为其分配 AID-2, 在该 PDN连接生命期中， AID-1就指示了 3GPP 接入网， AID-2就指示了该非 3GPP接入网。
另外， 终端 UE建立的多个 PDN连接也分配有不同的 AID。
当终端 UE/网络侧将业务流在不同的接入网中迁移 /新建 /删除时， 除了 携带流迁移信息 /流描述信息外， 还要携带 AID, 该 AID表征了执行该任务 所在的网络。 例如， 终端 UE可以在非 3GPP接入网中通过 ePDG发送流迁 移请求给 P-GW, 携带 AID-1 ( 3GPP接入时分配的 AID-1 )和流迁移信息， 因为携带了 AID-1 , 这表征了终端 UE要向 3GPP中迁移数据流， 而与发起 该请求所在的网络没有关系。 AID起到标识具体操作所在的那个接入网中 执行的作用。
下面具体说明本实施例与实施例 1的具体不同：
1. 终端 UE发起的附着 /PDN连接建立时， 本实施例与实施例 1终端 UE发起的附着 /PDN连接建立的不同之处在于：
在终端 UE接入 3GPP接入网（第一接入网 )建立第一个 PDN连接时， 为终端 UE分配了 AID-1 ,该 AID-1表征了该 PDN连接的 3GPP接入路径； 在步骤 301-302、 步骤 501-502中， 终端 UE携带了 AID-2给 P-GW, P-GW 获取该 AID-2,建立与 3GPP接入网和非 3GPP接入网的多重绑定，该 AID-2 表征了该 PDN连接的该非 3GPP接入路径。
2. 终端 UE发起的流迁移操作时， 本实施例与实施例 1终端 UE发起 的流迁移操作的不同之处在于：
终端 UE发送给 ePDG、 ePDG发送给 P-GW的流迁移请求 （ IKEv2或 者 SIP或者 RSVP和承载资源命令消息 ),除了 AID外还包括了流迁移信息。 AID表征了该操作需要执行的网络。 比如说如果携带了 AID-1 , 说明要向 3GPP接入网中迁移流， 如果携带了 AID-2, 说明要向非 3GPP接入网中迁 移流。
3. 网络侧发起的流迁移操作时，本实施例与实施例 1的不同之处在于： 网络侧 P-GW发送给 ePDG、 ePDG发送给终端 UE的流迁移请求消息
(承载资源命令消息和 IKEv2或者 SIP或者 RSVP ) , 除了 AID外还包括了 流迁移信息。 AID表征了该操作需要执行的网络。比如说如果携带了 AID-1 , 说明要向 3GPP接入网中迁移流， 如果携带了 AID-2, 说明要向非 3GPP接 入网中迁移流。
4. 终端 UE发起业务请求（建立、 修改、 删除） 时， 具体描述参照方 法一的对应部分， 不同之处同上述 1-3所述， 就是必须携带 AID, 用来标识 请求的操作所要执行的网络。
5. 网络侧发起的业务请求（建立、 修改、 删除） 时， 具体描述参照方 法一的对应部分， 不同之处同上述 1-3所述， 就是必须携带 AID, 用来标识 请求的操作所要执行的网络。
实施例 3
以上实施例 1和实施例 2基于的系统中， ePDG和 P-GW之间是通过 GTP协议建立数据通道 /隧道的， 在背景技术中提到， ePDG和 P-GW之间 还是可以基于 PMIPv6协议建立数据通道 /隧道的。 当 ePDG和 P-GW之间 釆用 PMIPv6协议时， 本发明同样适用。 基本机制与 GTP场景是相同的， 不同之处通过图 15的描述进一步说明。
步骤 1500至步骤 1501 : 同步骤 700至步骤 701。
步骤 1502: ePDG向 P-GW发送 PBU信令， 并携带所述流迁移信息。 流迁移信息在 PMIPv6消息中可以通过增设新的信元携带，现有的 PBU 消息不支持携带 QoS信息等， 因此需要通过扩展信元携带流迁移信息。
步骤 1503: P-GW收到步骤 1502中的消息后， 将下行数据流由 3GPP 接入网切换到非 3GPP接入网。
步骤 1504: P-GW发送 PBA消息给 ePDG。
步骤 1505: ePDG发送 IKEv2消息给终端 UE,通知终端 UE网关 P-GW 接受流迁移请求。 终端 UE将上行数据流由 3GPP接入网切换到非 3GPP接 入网。
P-GW在完成流切换操作后， 将在 3GPP接入系统中发起承载删除 /修 改 /资源释放操作， 删除原来业务流在 3GPP接入网所用的承载。 具体流程 参见现有技术的 P-GW在 3GPP系统中发起的资源修改 /去激活流程。
需要说明的是，在终端 UE和 ePDG之间釆用的是 SIP(图 8 )或者 RSVP (图 9 )信令时，终端 UE会向 ePDG发送 SIP: invite消息或者 RSVP: Resv 消息，该消息中携带流迁移信息，用于指示要迁移的 IP流。当 P-GW向 ePDG 发送 PBA后， ePDG向终端 UE回复 SIP: 200 OK消息或者 ResvConf消息， 通知终端 UE网关 P-GW已经接受流迁移请求。
需要说明的是， UE也可以将业务流从非 3GPP接入网迁移到 3GPP接 入网中， 具体的流程图参见图 10。
网络侧发起的流迁移操作的情况下，网络侧 P-GW在非 3GPP接入网中 发起流迁移操作， 将 3GPP接入网中的业务流迁移到该非 3GPP接入网， 该 方法中， 终端 UE在 3GPP接入网和非 3GPP接入网都已经附着 , 并建立了 一个或者多个 PDN连接， 并且实现了多重绑定。
网络侧 P-GW受到触发， 发送 PBU并携带流迁移信息给 ePDG, ePDG 向终端 UE发送流迁移信令 (是 IKEv2消息或者是 SIP消息或者 RSVP消 息）并携带流迁移信息，终端 UE收到流迁移信息后，将上行数据流由 3GPP 接入网切换到非 3GPP接入网， P-GW在收到 PBA后，将下行数据流由 3GPP 接入网切换到非 3GPP接入网。
上述终端 UE发起的流迁移和网络侧发起的流迁移的相关描述釆用的 是实施例 1的相关机制， 在此， 同样可以釆用实施例 2介绍的机制。
需要说明的是， 以上实施例 （1-3 ) 中， 所述 MME发送给 S-GW、 ePDG/S-GW发送给 P-GW 的 GTP 消息可以为承载资源命令消息； 所述 P-GW发送给 ePDG/S-GW, S-GW发送给 MME的 GTP消息可以为承载建 立 /修改 /更新请求消息； 所述 RSVP消息可以为 Resv消息， 所述 NAS消息 可以为承载资源分配 /修改请求， 激活专有 EPS承载上下文请求消息； 所述 IKEv2消息可以为 IKE认证请求 /创建子安全联盟请求 /信息请求消息； 所述 SIP消息可以为邀请消息。
实施例 4
基于非 3GPP接入 EPC的架构二实现流迁移的主要思想是： 因为 3GPP 接入和非 3GPP接入都锚定到了 ISGW,故终端发起的流迁移操作请求发送 到 ISGW, 由 ISGW执行流迁移的操作， 而不必报告 P-GW/GGSN或者只 是通知 P-GW/GGSN而无需由 P-GW/GGSN执行切换流。 网络发起的流迁 移，可以是 ISGW受到触发（或者来自 P-GW/GGSN的触发或者来自 PCRF 的触发）发起操作请求， 通知终端执行流迁移操作。 相比于非 3GPP接入 EPC的架构一的不同之处在于： ISGW无需和 P-GW/GGSN交互或者仅仅 是事件报告， P-GW/GGSN 无需参与流迁移操作。 下面对终端 /网络侧发起 的流迁移 （由 3GPP迁往非 3GPP或者反向迁移 ) 流程做描述。
流程图 18: 网络发起的流迁移 （ 3GPP迁往非 3GPP )
步骤 1801 : 终端 UE在 3GPP接入网和非 3GPP接入网都已经附着， 并 建立了一个或者多个 PDN连接， 并实现了多绑定。
步骤 1802: ISGW受触发， 决定发起流迁移。
其中，所述触发条件可以来自 PCRF的策略改变，或者来自 P-GW/GGSN 的请求， 或者网络负荷的改变， 导致 ISGW决定发起流迁移。
步骤 1803: ISGW发送 SIP协议的邀请（ invite )消息给终端 UE, 该消 息中携带流迁移信息， 用于指示要迁移的 IP流。
步骤 1804: 终端 UE发送 SIP协议的 200 OK消息给 ISGW。
终端 UE收到消息后将上行数据流从 3GPP接入网迁移到非 3GPP接入 网。
需要说明的是， 如果执行步骤 1805 , 终端 UE切换数据流发生在步骤
1805之后； 如果不执行步骤 1805 , 终端 UE切换数据流发生在步骤 1803 之后。
步骤 1805: 如果非 3GPP接入网中支持资源预留 /承载建立机制， 非 3GPP接入网根据步骤 1803下载的 QoS信息创建承载，为新业务预留资源； 如果非 3GPP接入网不支持资源预留 /承载建立机制， 则该步骤不执行。 步骤 1806: ISGW收到步骤 1804的消息后， 将下行数据流由 3GPP接 入网切换到非 3GPP接入网。
ISGW在完成流切换操作后，将在 3GPP接入系统中发起对应的承载删 除 /修改 /资源释放操作， 删除原来业务流在 3GPP接入网所用的承载。 具体 流程参见现有技术的 P-GW/GGSN在 3GPP系统中发起的资源修改 /去激活 流程。
流程图 19: 网络发起的流迁移 （非 3GPP迁往 3GPP )
步骤 1901 : 终端 UE在 3GPP接入网和非 3GPP接入网都已经附着， 并 建立了一个或者多个 PDN连接， 并实现了多绑定。
步骤 1902: ISGW受触发， 决定发起流迁移 （非 3GPP迁往 3GPP )。 其中，所述触发条件可以来自 PCRF的策略改变，或者来自 P-GW/GGSN 的请求， 或者网络负荷的改变， 导致 ISGW决定发起流迁移。
步骤 1903: ISGW发送创建 /修改 /更新承载请求消息给 MME/SGSN, 该消息中携带流迁移信息， 用于指示要迁移的 IP流。
步骤 1904： 受到 ISGW的触发， MME/SGSN发送 NAS消息的承载建 立 /修改 /更新请求给终端 UE, 消息中携带流迁移信息， 用于指示要迁移的 IP流。
步骤 1905: 3GPP无线资源预留和承载建立。
终端 UE收到消息后将上行数据流从 3GPP接入网迁移到非 3GPP接入 网。
需要说明的是， 如果执行步骤 1905 , 终端 UE切换数据流发生在步骤 1905之后； 如果不执行步骤 1905 , 终端 UE切换数据流发生在步骤 1904 之后。
步骤 1906: MME/SGSN在无线承载建立完成后， 发送创建 /修改 /更新 7 载响应消息给 ISGW。 步骤 1907: ISGW收到步骤 1906的消息后， 将下行数据流由非 3GPP 接入网切换到 3GPP接入网。
ISGW在完成流切换操作后，将在非 3GPP接入系统中发起相应的承载 删除 /修改 /资源释放操作， 删除原来业务流在 3GPP接入网所用的承载 （如 果现有技术中存在该操作）。
流程图 20:终端 UE发起的流迁移（ 3GPP迁往非 3GPP或者反向迁移 ) 步骤 2001 : 终端 UE在 3GPP接入网和非 3GPP接入网都已经附着， 并 建立了一个或者多个 PDN连接， 并实现了多绑定。
步骤 2002: 终端 UE决定发起流迁移 （ 3GPP迁往非 3GPP )。 终端 UE 发送 SIP协议的邀请（ invite ) 消息给 ISGW, 该消息中携带流迁移信息， 用于指示要迁移的 IP流。
其中， UE决定发起流迁移的触发条件可以来自用户的体验决定， 也可 能是终端 UE从策略服务器（例如， ANDSF, Access Network Discovery and
Selection Function, 网络发现和选择功能等）等获取了相关的策略， 或者是 终端 UE由于移动、 无线覆盖发生变化引起流迁移。
步骤 2003: ISGW发送 SIP协议的 200 OK消息给终端 UE。
终端 UE收到消息后将上行数据流从 3GPP接入网迁移到非 3GPP接入 网。
需要说明的是， 如果执行步骤 2004, 终端 UE切换数据流发生在步骤 2004之后； 如果不执行步骤 2004, 终端 UE切换数据流发生在步骤 2003 之后。
步骤 2005: ISGW收到步骤 2002的消息后， 将下行数据流由 3GPP接 入网切换到非 3GPP接入网； 或者， 如果执行步骤 2004, ISGW等待步骤 2004执行完成后迁移数据流。
流程图 21 : 终端 UE发起的流迁移 （非 3GPP迁往 3GPP ) 步骤 2100: 终端 UE在 3GPP接入网和非 3GPP接入网都已经附着， 并 建立了一个或者多个 PDN连接， 并实现了多绑定。
步骤 2101 : 终端 UE决定发起流迁移 （ 3GPP迁往非 3GPP )。 终端 UE 发送 NAS协议的请求承载资源修改消息给 SGSN/MME, 该消息中携带流 迁移信息， 用于指示要迁移的 IP流。
其中， UE决定发起流迁移的触发条件可以来自用户的体验决定， 也可 能是终端 UE从策略服务器（例如， ANDSF, Access Network Discovery and Selection Function, 网络发现和选择功能等）等获取了相关的策略， 或者是 终端 UE由于移动、 无线覆盖发生变化引起流迁移。
步骤 2102: SGSN/MME发送 GTP协议的承载资源命令给 ISGW, 消 息中携带流迁移信息， 用于指示要迁移的 IP流。
ISGW切换数据流， 从非 3GPP迁移到 3GPP。
步骤 2103: ISGW发送 GTP协议的创建 /修改 /更新承载请求消息给 SGSN/MME。
步骤 2104: SGSN/MME发送 NAS协议的承载建立 /修改 /更新请求给终 端 UE, 并且消息中携带流迁移信息， 用于指示要迁移的 IP流。
步骤 2105: 3GPP接入网执行资源预留和承载建立操作。
终端 UE收到消息后将上行数据流从非 3GPP接入网迁移到 3GPP接入网。 步骤 2106: MME/SGSN在无线承载建立完成后， 发送创建 /修改 /更新 7 载响应消息给 ISGW。
步骤 2107: ISGW收到步骤 2106的消息后， 将下行数据流由非 3GPP 接入网切换到 3GPP接入网。
ISGW在完成流切换操作后，将在非 3GPP接入系统中发起相应的承载 删除 /修改 /资源释放操作， 删除原来业务流在 3GPP接入网所用的承载 （如 果现有技术中存在该操作；)。 需要说明的是： 实施例 4只是作为另外一种实现方式的优选实施例而 已， 当 IP数据流由非 3GPP接入网迁移到 3GPP接入网时， UE和 ISGW可 以直接互通 SIP消息， 而无需借用底层的 NAS和 GTP消息， 这样直接在 SIP消息中携带流迁移信息， 透传 MME/SGSN即可， 可以减少对 3GPP网 络的影响。
另外， IP数据流的迁移时机可以如流程图中所述， 当有资源分配与承 载建立操作的时候， 发生在资源分配和承载建立成功后执行， 也可以在收 到 SIP或者 NAS或者 GTP消息后直接执行。
再次，具体网络部署时， ePDG与 ISGW中的其他模块是有可能分设的， ePDG和 ISGW之间釆用 GTP或者 PMIP协议建立数据通道。 在这种场景 下， 流迁移的机制可以釆用类同于图 8、 9、 11、 12、 13、 15 , 只是将 P-GW 改为 ISGW即可； 或者 ISGW直接与终端 UE之间互通 SIP信令（参见图 18、 20, SIP消息透传 ePDG, ePDG在图中未体现）， 用于协商流迁移信息。
结合以上各实施例可知， 本发明实现流迁移的操作思路可以表示如图 22所示的流程， 该流程包括以下步骤：
步骤 2210:终端 UE/网络侧通过 3GPP接入网或非 3GPP接入网请求网 络侧 /终端 UE进行流迁移。
步骤 2220: 所述终端 UE和网络侧相应地将上下行 IP流由非 3GPP接 入网迁移到 3GPP接入网， 或由 3GPP接入网迁移到非 3GPP接入网。
综上所述可见， 无论是方法还是系统， 本发明实现流迁移的技术， 均 可实现非 3GPP接入网与 3GPP接入网之间的切换，从而能够提高系统灵活 度及效率。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围， 凡在本发明的精神和原则之内所作的任何修改、 等同替换和改进 等， 均应包含在本发明的保护范围之内。

Claims

权利要求书
1、 一种实现流迁移的方法， 其特征在于， 该方法包括：
终端用户设备 UE/网络侧通过第三代合作伙伴计划 3GPP接入网或非 3GPP接入网请求网络侧 /终端 UE进行流迁移；
所述终端 UE和网络侧相应地将上下行 IP流由非 3GPP接入网迁移到 3GPP接入网， 或由 3GPP接入网迁移到非 3GPP接入网。
2、 根据权利要求 1所述的方法， 其特征在于， 该方法具体为： 终端 UE通过非 3GPP接入网向网络侧演进的分组数据网关 ePDG发送 流迁移请求信令， 所述流迁移请求信令携带流迁移信息；
所述 ePDG向网络侧分组数据网络网关 P-GW发送 GTP消息，所述 GTP 消息携带流迁移信息；
所述终端 UE和所述 P-GW分别将上下行 IP流由 3GPP接入网迁移到 非 3GPP接入网或者由非 3GPP接入网迁移到 3GPP接入网。
3、 根据权利要求 1所述的方法， 其特征在于， 该方法具体为： 终端 UE通过 3GPP接入网向移动管理单元 MME发送 NAS消息 , 所 述 NAS消息携带流迁移信息；
所述 MME向服务网关 S-GW、 所述 S-GW向 P-GW发送 GTP消息， 所述 GTP消息携带流迁移信息；
所述终端 UE和 P-GW分别将上下行 IP流由非 3GPP接入网迁移到 3GPP接入网或者由 3GPP接入网迁移到非 3GPP接入网。
4、 根据权利要求 1所述的方法， 其特征在于， 该方法具体为： 网络侧 P-GW向 ePDG发送 GTP消息，所述 GTP消息携带流迁移信息； 所述 ePDG通过非 3GPP接入网向终端 UE发送流迁移请求信令，所述 流迁移请求信令携带流迁移信息；
所述终端 UE和 P-GW分别将上下行 IP流由 3GPP接入网迁移到非 3GPP接入网或者由非 3GPP接入网迁移到 3GPP接入网。
5、 根据权利要求 1所述的方法， 其特征在于， 该方法具体为： 网络侧 P-GW向 S-GW、 S-GW向 MME发送 GTP消息 , 所述 GTP消 息携带流迁移信息；
所述 MME通过 3GPP接入网向终端 UE发送 NAS消息， 所述 NAS 消息携带流迁移信息；
所述终端 UE和 P-GW分别将上下行 IP流由非 3GPP接入网迁移到 3GPP接入网或者由 3GPP接入网迁移到非 3GPP接入网。
6、 根据权利要求 1所述的方法， 其特征在于， 该方法具体为： 终端 UE通过非 3GPP接入网向网络侧 ePDG发送流迁移请求信令，所 述流迁移请求信令携带流迁移信息；
所述 ePDG向网络侧 P-GW发送 PBU信令，所述 PBU信令携带流迁移 信息；
所述终端 UE和 P-GW分别将上下行 IP流由非 3GPP接入网迁移到 3GPP接入网或者由 3GPP接入网迁移到非 3GPP接入网。
7、 根据权利要求 2、 4或 6所述的方法， 其特征在于， 所述流迁移请 求信令为 RS VP消息、 NAS消息、 IKEv2消息或 SIP消息。
8、 根据权利要求 2至 5任一项所述的方法， 其特征在于，
所述 MME发送给 S-GW、 ePDG/S-GW发送给 P-GW的 GTP消息为承 载资源命令消息； 所述 P-GW发送给 ePDG/S-GW , S-GW发送给 MME的 GTP消息为承载建立 /修改 /更新请求消息； 所述 RSVP消息为 Resv消息； 所述 NAS消息为承载资源分配 /修改请求、 激活专有 EPS承载上下文请求 消息；所述 IKEv2消息为 IKE认证请求 /创建子安全联盟请求 /信息请求消息； 所述 SIP消息为邀请消息。
9、 根据权利要求 1至 6任一项所述的方法， 其特征在于， 所述流迁移 信息包括以下一种或几种： 接入标识、 流对应的 QoS信息、 流标识、 流级 另 'J、 流分组过滤器 /业务流模板、 流操作指示。
10、 根据权利要求 2至 6任一项所述的方法， 其特征在于， 在实现所 述流迁移之前， 该方法还包括： 所述终端 UE建立与所述 3GPP接入网和所 述非 3GPP接入网的多重绑定， 即终端 UE从所述 3GPP接入网接入时建立 的连接和从所述非 3GPP接入网接入时建立的连接同属一个 PDN连接的两 条子路径， 共用相同 APN、 PDN地址、 IP-CAN会话。
11、 根据权利要求 10所述的方法， 其特征在于， 所述终端 UE建立所 述多重绑定的过程包括：
终端 UE接入所述 3GPP接入网和 /或非 3GPP接入网时，携带接入指示 给 P-GW; P-GW获取所述接入指示并建立所述终端 UE与所述 3GPP接入 网和非 3GPP接入网的多重绑定。
12、 根据权利要求 1所述的方法， 其特征在于， 该方法具体为： 终端 UE与综合服务网关 ISGW交互， 请求进行流迁移；
终端 UE与 ISGW根据交互结果， 分别相应地将上下行数据流从 3GPP 接入网迁移到非 3GPP接入网，或分别相应地将上下行数据流从非 3GPP接 入网迁移到 3GPP接入网。
13、根据权利要求 12所述的方法，其特征在于，所述终端 UE与 ISGW 交互是由 ISGW以触发的形式发起的； 或者， 是由终端 UE主动发起的。
14、 根据权利要求 13所述的方法， 其特征在于， 由 ISGW以触发的形 式发起的所述交互过程包括：
ISGW受触发， 决定发起流迁移， 并发送 SIP协议的邀请消息给终端 UE;终端 UE收到消息后将上行数据流从 3GPP接入网迁移到非 3GPP接入 网， 由 ISGW将下行数据流由 3GPP接入网切换到非 3GPP接入网；
或者， ISGW受触发， 决定发起流迁移， 并发送创建 /修改 /更新承载请 求消息给 MME/SGSN,由 MME/SGSN根据 ISGW的触发发送 NAS消息的 承载建立 /修改 /更新请求给终端 UE; 终端 UE根据收到的请求的触发将上 行数据流从 3GPP接入网迁移到非 3GPP接入网； ISGW将下行数据流由非 3GPP接入网切换到 3GPP接入网。
15、根据权利要求 14所述的方法，其特征在于，所述触发条件来自 PCRF 的策略改变， 或者来自 P-GW/GGSN的请求， 或者网络负荷的改变， 导致 ISGW决定发起流迁移。
16、 根据权利要求 13所述的方法， 其特征在于， 由终端 UE主动发起 的所述交互过程包括：
终端 UE决定发起流迁移，并发送 SIP协议的邀请消息给 ISGW, ISGW 根据所述消息将下行数据流由 3GPP接入网切换到非 3GPP接入网， 终端 UE将上行数据流从 3GPP接入网迁移到非 3GPP接入网；
或者， 终端 UE决定发起流迁移， 并发送 NAS协议的请求承载资源修 改消息给 SGSN/MME , SGSN/MME 发送 GTP 协议的承载资源命令给 ISGW; ISGW切换数据流， 从非 3GPP接入网切换到 3GPP接入网， 终端 UE将上行数据流从非 3GPP接入网迁移到 3GPP接入网。
17、 根据权利要求 16所述的方法， 其特征在于， UE决定发起流迁移 的触发条件来自用户的体验决定，或是终端 UE从策略服务器获取的相关策 略， 或者是终端 UE由于移动、 无线覆盖发生变化引起流迁移。
18、 根据权利要求 12至 17任一项所述的方法， 其特征在于， IP数据 流的迁移时机为： 当有资源分配与承载建立操作时， 发生在资源分配和承 载建立成功后执行， 或者在收到 SIP或者 NAS或者 GTP消息后直接执行。
19、 一种实现流迁移的系统， 其特征在于， 该系统包括终端 UE和网络 侧； 其中，
所述终端 UE, 用于通过 3GPP接入网或非 3GPP接入网请求网络侧进 行流迁移； 以及相应地将上行 IP流由非 3GPP接入网迁移到 3GPP接入网， 或由 3GPP接入网迁移到非 3GPP接入网；
所述网络侧， 用于根据所述终端 UE 的通知相应地将下行 IP 流由非 3GPP接入网迁移到 3GPP接入网， 或由 3GPP接入网迁移到非 3GPP接入 网。
20、 根据权利要求 19所述的系统， 其特征在于，
所述终端 UE通过非 3GPP接入网请求网络侧进行流迁移时， 用于： 通过非 3GPP接入网向网络侧 ePDG发送流迁移请求信令，所述流迁移 请求信令携带流迁移信息；
所述 ePDG用于向网络侧 P-GW发送 GTP消息，所述 GTP消息携带流 迁移信息。
21、根据权利要求 19所述的系统，其特征在于，所述终端 UE通过 3GPP 接入网请求网络侧进行流迁移时， 用于：
通过 3GPP接入网向移动管理单元 MME发送 NAS消息 ,所述 NAS消 息携带流迁移信息；
所述 MME用于通过 S-GW向 P-GW发送 GTP消息，所述 GTP消息携 带流迁移信息。
22、 根据权利要求 19所述的系统， 其特征在于， 所述终端 UE通过非 3GPP接入网请求网络侧进行流迁移， 以及相应地将上行 IP流由非 3GPP 接入网迁移到 3GPP接入网， 或由 3GPP接入网迁移到非 3GPP接入网时， 用于：
通过非 3GPP接入网向网络侧 ePDG发送流迁移请求信令，所述流迁移 请求信令携带流迁移信息；
所述 ePDG用于向网络侧 P-GW发送 PBU信令， 所述 PBU信令携带流 迁移信息； 所述终端 UE和 P-GW分别用于将上下行 IP流由非 3GPP接入网迁移 到 3GPP接入网或者由 3GPP接入网迁移到非 3GPP接入网。
23、根据权利要求 19所述的系统，其特征在于，所述网络侧包括 ISGW, 所述 ISGW融合了 GGSN、S-GW或者 P-GW的功能以及 GPRS隧道协议和 NAT网关功能；
所述终端 UE与 ISGW分别用于： 进行交互， 请求进行流迁移； 以及， 分别用于根据交互结果，分别相应地将上下行数据流从 3GPP接入网迁移到 非 3GPP接入网， 或分别相应地将上下行数据流从非 3GPP接入网迁移到 3GPP接入网。
24、根据权利要求 23所述的系统，其特征在于，所述终端 UE与 ISGW 交互是由 ISGW以触发的形式发起的； 或者， 是由终端 UE主动发起的。
25、 根据权利要求 24所述的系统， 其特征在于， 由 ISGW以触发的形 式发起时， 所述 ISGW与终端 UE在交互时分别用于：
ISGW受触发， 决定发起流迁移， 并发送 SIP协议的邀请消息给终端 UE;终端 UE收到消息后将上行数据流从 3GPP接入网迁移到非 3GPP接入 网， ISGW将下行数据流由 3GPP接入网切换到非 3GPP接入网；
或者， ISGW受触发， 决定发起流迁移， 并发送创建 /修改 /更新承载请 求消息给 MME/SGSN,由 MME/SGSN根据 ISGW的触发发送 NAS消息的 承载建立 /修改 /更新请求给终端 UE, 终端 UE根据收到的请求的触发将上 行数据流从 3GPP接入网迁移到非 3GPP接入网； ISGW将下行数据流由非 3GPP接入网切换到 3GPP接入网。
26、根据权利要求 25所述的系统，其特征在于，所述触发条件来自 PCRF 的策略改变， 或者来自 P-GW/GGSN的请求， 或者网络负荷的改变时， 导 致 ISGW决定发起流迁移。
27、 根据权利要求 24所述的系统， 其特征在于， 由终端 UE主动发起 所述交互时， 所述终端 UE与 ISGW分别用于：
终端 UE决定发起流迁移，并发送 SIP协议的邀请消息给 ISGW, ISGW 根据所述消息将下行数据流由 3GPP接入网切换到非 3GPP接入网， 终端 UE收到所述响应后将上行数据流从 3GPP接入网迁移到非 3GPP接入网； 或者， 终端 UE决定发起流迁移， 并发送 NAS协议的请求承载资源修 改消息给 SGSN/MME , SGSN/MME 发送 GTP 协议的承载资源命令给 ISGW;
ISGW根据收到的所述命令切换数据流，从非 3GPP接入网切换到 3GPP 接入网 , 终端 UE将上行数据流从非 3GPP接入网迁移到 3GPP接入网。
28、 根据权利要求 27所述的系统， 其特征在于， UE决定发起流迁移 的触发条件来自用户的体验决定，或是终端 UE从策略服务器获取的相关策 略， 或者是终端 UE由于移动、 无线覆盖发生变化引起流迁移。
29、 根据权利要求 23至 28任一项所述的系统， 其特征在于， IP数据 流的迁移时机为： 当有资源分配与承载建立操作时， 发生在资源分配和承 载建立成功后执行， 或者在收到 SIP或者 NAS或者 GTP消息后直接执行。
30、 一种实现流迁移的系统， 其特征在于， 该系统包括终端 UE和网络 侧； 其中，
所述网络侧， 用于通过 3GPP接入网或非 3GPP接入网请求终端 UE进 行流迁移； 以及相应地将下行 IP流由非 3GPP接入网迁移到 3GPP接入网， 或由 3GPP接入网迁移到非 3GPP接入网；
所述终端 UE, 用于根据所述网络侧的通知相应地将上行 IP 流由非 3GPP接入网迁移到 3GPP接入网， 或由 3GPP接入网迁移到非 3GPP接入 网。
31、 根据权利要求 30所述的系统， 其特征在于， 所述网络侧包括网络 侧 P-GW, 所述网络侧 P-GW在通过非 3GPP接入网请求终端 UE进行流迁 移时， 用于：
向 ePDG发送 GTP消息， 所述 GTP消息携带流迁移信息；
所述 ePDG用于通过非 3GPP接入网向终端 UE发送流迁移请求信令， 所述流迁移请求信令携带流迁移信息。
32、 根据权利要求 30所述的系统， 其特征在于， 所述网络侧包括网络 侧 P-GW, 所述网络侧 P-GW在通过 3GPP接入网请求终端 UE进行流迁移 时， 用于：
通过 S-GW向 MME发送 GTP消息， 所述 GTP消息携带流迁移信息； 所述 MME用于通过 3GPP接入网向终端 UE发送 NAS消息 ,所述 NAS 消息携带流迁移信息。
33、根据权利要求 30所述的系统，其特征在于，所述网络侧包括 ISGW, 所述 ISGW融合了 GGSN、S-GW或者 P-GW的功能以及 GPRS隧道协议和 NAT网关功能；
所述终端 UE与 ISGW分别用于： 进行交互， 请求进行流迁移； 以及， 分别用于根据交互结果，分别相应地将上下行数据流从 3GPP接入网迁移到 非 3GPP接入网， 或分别相应地将上下行数据流从非 3GPP接入网迁移到 3GPP接入网。
34、根据权利要求 33所述的系统，其特征在于，所述终端 UE与 ISGW 交互是由 ISGW以触发的形式发起的； 或者， 是由终端 UE主动发起的。
35、 根据权利要求 34所述的系统， 其特征在于， 由 ISGW以触发的形 式发起时， 所述 ISGW与终端 UE在交互时分别用于：
ISGW受触发， 决定发起流迁移， 并发送 SIP协议的邀请消息给终端 UE;终端 UE收到消息后将上行数据流从 3GPP接入网迁移到非 3GPP接入 网， ISGW将下行数据流由 3GPP接入网切换到非 3GPP接入网；
或者， ISGW受触发， 决定发起流迁移， 并发送创建 /修改 /更新承载请 求消息给 MME/SGSN,由 MME/SGSN根据 ISGW的触发发送 NAS消息的 承载建立 /修改 /更新请求给终端 UE, 终端 UE根据收到的请求的触发将上 行数据流从 3GPP接入网迁移到非 3GPP接入网； ISGW将下行数据流由非 3GPP接入网切换到 3GPP接入网。
36、根据权利要求 35所述的系统，其特征在于，所述触发条件来自 PCRF 的策略改变， 或者来自 P-GW/GGSN的请求， 或者网络负荷的改变时， 导 致 ISGW决定发起流迁移。
37、 根据权利要求 34所述的系统， 其特征在于， 由终端 UE主动发起 所述交互时， 所述终端 UE与 ISGW分别用于：
终端 UE决定发起流迁移，并发送 SIP协议的邀请消息给 ISGW, ISGW 根据所述消息将下行数据流由 3GPP接入网切换到非 3GPP接入网， 终端 UE将上行数据流从 3GPP接入网迁移到非 3GPP接入网；
或者， 终端 UE决定发起流迁移， 并发送 NAS协议的请求承载资源修 改消息给 SGSN/MME , SGSN/MME 发送 GTP 协议的承载资源命令给 ISGW;
ISGW根据收到的所述命令切换数据流，从非 3GPP接入网切换到 3GPP 接入网 , 终端 UE将上行数据流从非 3GPP接入网迁移到 3GPP接入网。
38、 根据权利要求 37所述的系统， 其特征在于， UE决定发起流迁移 的触发条件来自用户的体验决定，或是终端 UE从策略服务器获取的相关策 略， 或者是终端 UE由于移动、 无线覆盖发生变化引起流迁移。
39、 根据权利要求 33至 38任一项所述的系统， 其特征在于， IP数据 流的迁移时机为： 当有资源分配与承载建立操作时， 发生在资源分配和承 载建立成功后执行， 或者在收到 SIP或者 NAS或者 GTP消息后直接执行。
PCT/CN2011/075400 2010-09-27 2011-06-07 一种实现流迁移的方法及系统 WO2012041073A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201010295638.4 2010-09-27
CN201010295638 2010-09-27
CN201110005120.7A CN102421155B (zh) 2010-09-27 2011-01-12 一种实现流迁移的方法及系统
CN201110005120.7 2011-01-12

Publications (1)

Publication Number Publication Date
WO2012041073A1 true WO2012041073A1 (zh) 2012-04-05

Family

ID=45891884

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/075400 WO2012041073A1 (zh) 2010-09-27 2011-06-07 一种实现流迁移的方法及系统

Country Status (2)

Country Link
CN (1) CN102421155B (zh)
WO (1) WO2012041073A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103379569A (zh) * 2012-04-17 2013-10-30 中兴通讯股份有限公司 流迁移的触发方法及装置
CN103686883A (zh) * 2012-09-20 2014-03-26 上海贝尔股份有限公司 用于在多无线接入网络中进行数据流迁移的方法与装置

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103857011B (zh) * 2012-11-30 2018-01-05 中兴通讯股份有限公司 一种ue接入网络的选择方法、装置、系统及一种ue
CN104080073B (zh) * 2013-03-29 2018-03-23 电信科学技术研究院 一种实现ip流移动性的方法、装置及系统
CN104641679B (zh) * 2013-04-03 2019-03-19 华为技术有限公司 一种无线网络的分流方法及设备、系统
CN104113918B (zh) * 2013-04-22 2018-03-16 电信科学技术研究院 一种切换过程中承载信息的交互方法及装置
CN104521292B (zh) * 2013-06-27 2018-09-21 华为技术有限公司 一种业务分流方法和基站
CN105282798A (zh) * 2014-07-24 2016-01-27 中兴通讯股份有限公司 一种关于流迁移触发的相关实现方法及设备
CN105392177A (zh) * 2014-09-09 2016-03-09 中兴通讯股份有限公司 一种实现流迁移的方法和装置
CN105897375A (zh) * 2015-01-26 2016-08-24 中兴通讯股份有限公司 业务迁移方法及装置
CN106162801A (zh) * 2015-03-27 2016-11-23 中兴通讯股份有限公司 实现缺省路由决策的方法、核心网网元、用户设备及系统
US9730120B2 (en) * 2015-06-01 2017-08-08 Intel Corporation Handover using group evolved packet system (EPS) bearers

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101730072A (zh) * 2009-04-30 2010-06-09 中兴通讯股份有限公司 在多接入场景下分组数据网络网关标识的保存方法及系统
CN101730150A (zh) * 2009-01-19 2010-06-09 中兴通讯股份有限公司 业务流迁移时对网络资源进行控制的方法
CN101835201A (zh) * 2009-03-11 2010-09-15 中兴通讯股份有限公司 一种多网络连接环境中保证数据不中断的方法及系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101237677B (zh) * 2007-02-02 2010-09-08 华为技术有限公司 系统间切换时传递聚合最大位速率的方法、网络系统及目的侧网络

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101730150A (zh) * 2009-01-19 2010-06-09 中兴通讯股份有限公司 业务流迁移时对网络资源进行控制的方法
CN101835201A (zh) * 2009-03-11 2010-09-15 中兴通讯股份有限公司 一种多网络连接环境中保证数据不中断的方法及系统
CN101730072A (zh) * 2009-04-30 2010-06-09 中兴通讯股份有限公司 在多接入场景下分组数据网络网关标识的保存方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Multi access PDN connectivity and IP flow mobility (Release 9)", 3GPP TR 23.861 V1.3.0 (2009-09), September 2009 (2009-09-01), pages 11 - 12, 21 - 22, 30 - 31 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103379569A (zh) * 2012-04-17 2013-10-30 中兴通讯股份有限公司 流迁移的触发方法及装置
CN103686883A (zh) * 2012-09-20 2014-03-26 上海贝尔股份有限公司 用于在多无线接入网络中进行数据流迁移的方法与装置
CN103686883B (zh) * 2012-09-20 2017-08-25 上海贝尔股份有限公司 用于在多无线接入网络中进行数据流迁移的方法与装置

Also Published As

Publication number Publication date
CN102421155A (zh) 2012-04-18
CN102421155B (zh) 2017-03-01

Similar Documents

Publication Publication Date Title
JP6947878B2 (ja) 無線通信システムにおける登録解除方法及びこのための装置
CN102421155B (zh) 一种实现流迁移的方法及系统
EP2445261B1 (en) Method, apparatus and system for routing user plane data in mobile network
CN102883381B (zh) 在系统间切换的情况下用于为终端传送pdp上下文信息的设备和方法
US8855045B2 (en) Method and system for controlling establishment of local IP access
EP2475142B1 (en) Method and system for acquiring route strategies
WO2011020386A1 (zh) 承载类型的指示方法、系统及传输分流网元
CN103716850B (zh) 通信路径的切换方法、系统及装置
KR20100060800A (ko) ＨｅＮＢ에서 단말에게 선택적으로 자원을 할당하기 위한 시스템 및 장치
CN101370261B (zh) 从cs域向ps域切换的资源准备方法及通信设备
WO2008138259A1 (fr) Procédé et système et dispositif pour un procédé d'enregistrement
WO2013010415A1 (zh) 一种实现ip地址属性通知的方法、系统和sgw
WO2012094957A1 (zh) 一种对mtc终端进行移动性管理的方法和系统
WO2011140888A1 (zh) 一种增强单接入语音业务连续性的通信系统及方法
KR102017167B1 (ko) 무선 통신 시스템에서 데이터 트래픽 분산을 위한 방법 및 장치
WO2011006404A1 (zh) 本地ip访问连接建立的实现方法及系统
WO2013040980A1 (zh) 一种流迁移的实现方法、终端和分组数据网络网关
WO2010111944A1 (zh) 释放接入连接的方法、装置、策略控制实体及系统
CN103428888B (zh) 一种直通隧道建立方法及系统
WO2011017979A1 (zh) 支持ip分流的通信系统中资源管理方法与装置
CN103139914A (zh) 对本地卸载数据进行资源控制的方法及系统
WO2012126319A1 (zh) 一种本地访问业务的切换方法及系统
WO2012041131A1 (zh) 一种用户参与本地访问连接建立的方法及系统
WO2011134324A1 (zh) 一种数据分流的动态控制方法及系统
WO2011063692A1 (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: 11827969

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

Country of ref document: EP

Kind code of ref document: A1