WO2012041073A1 - Procédé et système adaptés pour exécuter un transfert de flux - Google Patents

Procédé et système adaptés pour exécuter un transfert de flux 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)
Chinese (zh)
Inventor
毕以峰
朱春晖
周娜
王静
赵佑春
吴瑟
刘建业
王卫斌
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012041073A1 publication Critical patent/WO2012041073A1/fr

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

La présente invention se rapporte à un procédé adapté pour exécuter un transfert de flux. Le procédé selon l'invention comprend les étapes suivantes : un équipement d'utilisateur (UE, User Equipment) formant terminal/un côté réseau demande, via un réseau d'accès 3GPP(3rd Generation Partnership Project) ou un réseau d'accès autre qu'un réseau 3GPP, à un côté réseau/un UE formant terminal d'exécuter un transfert de flux; en réponse, l'UE formant terminal et le côté réseau transfèrent les flux IP sur la liaison montante et sur la liaison descendante, du réseau d'accès autre qu'un réseau 3GPP au réseau d'accès 3GPP, ou du réseau d'accès 3GPP au réseau d'accès autre qu'un réseau 3GPP. La présente invention se rapporte d'autre part à un système adapté pour exécuter un transfert de flux. La présente invention est apte à exécuter un transfert de flux entre un réseau d'accès autre qu'un réseau 3GPP et un réseau d'accès 3GPP, et permet ainsi d'améliorer la flexibilité et l'efficacité d'un système.
PCT/CN2011/075400 2010-09-27 2011-06-07 Procédé et système adaptés pour exécuter un transfert de flux WO2012041073A1 (fr)

Applications Claiming Priority (4)

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

Publications (1)

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

Family

ID=45891884

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/075400 WO2012041073A1 (fr) 2010-09-27 2011-06-07 Procédé et système adaptés pour exécuter un transfert de flux

Country Status (2)

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

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 电信科学技术研究院 一种切换过程中承载信息的交互方法及装置
WO2014205713A1 (fr) * 2013-06-27 2014-12-31 华为技术有限公司 Procédé de délestage de service et station de base
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
CN101730150A (zh) * 2009-01-19 2010-06-09 中兴通讯股份有限公司 业务流迁移时对网络资源进行控制的方法
CN101730072A (zh) * 2009-04-30 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 (fr) Procédé, appareil et système pour router des données de plan d'utilisateur dans un réseau mobile
US8855045B2 (en) Method and system for controlling establishment of local IP access
EP2475142B1 (fr) Procédé et système d'acquisition de stratégies d itinéraire
WO2011020386A1 (fr) Procédé d'indication, système pour un type de porteur et élément de réseau de dérivation de transmission
CN103716850B (zh) 通信路径的切换方法、系统及装置
CN101370261B (zh) 从cs域向ps域切换的资源准备方法及通信设备
KR20100060800A (ko) ＨｅＮＢ에서 단말에게 선택적으로 자원을 할당하기 위한 시스템 및 장치
WO2008138259A1 (fr) Procédé et système et dispositif pour un procédé d'enregistrement
WO2013010415A1 (fr) Procédé, système et sgw pour réaliser une notification d'attributs d'adresse ip
WO2012094957A1 (fr) Procédé et système pour effecteur une gestion de mobilité sur un terminal mtc
KR102017167B1 (ko) 무선 통신 시스템에서 데이터 트래픽 분산을 위한 방법 및 장치
WO2011140888A1 (fr) Système et procédé de communication pour continuité d'appel vocal radio unique améliorée
WO2011006404A1 (fr) Procédé et système d'établissement d'une connexion d'accès ip local
WO2013040980A1 (fr) Procédé de migration de flux, terminal et passerelle de réseau de données par paquets
WO2010111944A1 (fr) Procédé, appareil, fonction de commande de politique et système destinés à libérer des connexions d'accès
CN103428888B (zh) 一种直通隧道建立方法及系统
WO2011017979A1 (fr) Procede et dispositif de gestion de ressources dans un systeme de communication soutenant le shuntage ip
WO2012126319A1 (fr) Procédé et système pour le transfert intercellulaire d'un service d'accès local
WO2012041131A1 (fr) Procédé et système permettant à un abonné de participer à l'établissement d'une communication en accès local
WO2011134324A1 (fr) Procédé et système de commande dynamique de distribution de données
WO2011063692A1 (fr) Procédé et système de distinction de type de liaison de réseau par unité de tampon de données
WO2011160509A1 (fr) Procédé et dispositif d'allocation d'adresse dans un réseau de délestage de trafic
WO2012129997A1 (fr) Procédé et dispositif pour traiter une connexion d'accès à un réseau local

Legal Events

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

Ref document number: 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