WO2013040980A1 - Flow migration method, terminal and packet data network gateway - Google Patents

Abstract

A flow migration method comprises: after establishing multiple accesses connected to the same packet data network (PDN), a terminal negotiates flow migration information with a packet data network gateway (P-GW) via a 3rd generation partnership project (3GPP) network signaling; and the P-GW migrates the data flow.

Description

 Method for implementing stream migration, terminal and packet data network gateway

Technical field

(EPS) EPS (Evolved Packet System), specifically relates to a method for implementing stream migration, a terminal, and a packet data network gateway.

Background technique

As shown in FIG. 1, the EPS is composed of an access network and an evolved packet core network (EPC), and the access network may be an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) or UTRAN. (Universal Terrestrial Radio Access Network, etc.), EPC includes: MME (Mobility Management Entity), SGSN (Serving GPRS (General Packet Radio Service) Support Node, Serving GPRS Support Node), S-GW (Serving Gateway), P-GW (Packet Data Network Gateway), HSS (Home Subscriber Server), 3GPP AAA Server (3GPP Authentication and Authorization) Server), PCRF (Policy and Charging Rules Function) and other supporting nodes. The E-UTRAN has an eNB (evolved NodeB), and the UTRAN has an internal NB (NodeB, base station). The MME is responsible for the mobility management of the terminal UE from the EUTRAN, and the NAS (non-access stratum). Control plane related work such as processing of signaling and management of user context; SGSN is responsible for mobility management of terminal UEs from E-UTRAN access, processing of NAS signaling, and management of user context; S-GW is with E The UTRAN-connected access gateway device forwards data between the E-UTRAN and the P-GW and is responsible for buffering the paging wait data. The P-GW is a border gateway between the 3GPP Evolved Packet System and the PDN (Packet Data Network), and is responsible for accessing the user terminal to the PDN, and forwarding data between the EPS and the PDN. The S-GW and the P-GW are connected through the S5/S8 interface, and the GTP (General Packet Radio Service Tunneling Protocol) protocol or ΡΜΙΡνό (Proxy Mobile IP version 6) is used. protocol. PCRF is the policy The billing rule function entity is connected to the operator's IP service network through the Rx interface to obtain service information, and is connected to the gateway device in the network through the Gx/Gxa/Gxb/Gxc interface, and is responsible for initiating IP (Internet Protocol, Internet). Protocol) The establishment of bearers, guarantees the QoS (Quality of Service) of service data, and performs charging control.

 The EPS also supports UE access through non-3GPP systems other than E-UTRAN, where access by non-3GPP systems is implemented through the S2a/S2b/S2c interface (S2c access is not relevant to the present invention, not shown in the figure) The P-GW serves as a data anchor for access by the 3GPP system and access by the non-3GPP system. In the system architecture of EPS, non-3GPP systems are classified into Trusted non-3 GPP IP access and Untrusted non-3GPP IP access. The trusted non-3GPP IP access network can be directly connected to the P-GW through the S2a interface; the untrusted non-3GPP IP access network needs to be connected to the P-GW via an ePDG (Evolved Packet Data Gateway), ePDG The interface with the P-GW is S2b. Both the S2a/S2b interface can use the GTP or PMIPv6 protocol.

 At present, the research topics on EPS focus on Multiple Access and IP flow mobility, where multiple access means: EPC supports UEs to be connected simultaneously through the same P-GW through multiple access networks. Into a PDN, for example, the terminal can simultaneously access the same P-GW through the 3GPP access network (EUTRAN access network or UTRAN access network) and the trusted non-3GPP access network (such as WLAN access network). - GW establishes a tunnel with S-GW tunnel and non-3GPP access gateway at the same time, or the terminal can simultaneously pass through 3GPP access network (EUTRAN access network or UTRAN access network) and untrusted non-3GPP access network (such as The WLAN access network is simultaneously connected to the same P-GW, and the P-GW simultaneously establishes a tunnel with the S-GW tunnel and the ePDG. In this scenario, the UE is attached to the EPC through multiple access networks. The P-GW allocates an IP address to the UE, and an IP connection exists between the UE and the PDN (as shown by the dotted line in FIG. 1). Since different services are applicable to different network transmissions, the multiple access technologies can select the applicable access network transmission services according to the characteristics of the services, and multiple access networks can share the network load and avoid network congestion.

The current problem is how the IP data stream dynamically migrates between the two access networks. Currently, when an IP data stream is to be migrated from the source access network to the target access network, the terminal UE will Initiating a resource request in the target access network, and when the P-GW receives the resource request, it decides to migrate the IP flow. To the second access network, or the terminal directly sends an application layer message (for example, a SIP message) to the P-GW to notify the P-GW of the data stream that needs to be migrated. However, the above solution has a great impact on the target access network. Especially when the target access network is a non-3GPP access network, the existing IETF protocol is greatly changed and is not easy to implement. Summary of the invention

 The technical problem to be solved by the present invention is to provide a method for implementing stream migration, a terminal, and a packet data network gateway, which avoid modification of the non-3GPP access network and the IETF protocol, and simplify the operation flow.

 To solve the above technical problem, the present invention provides a method for implementing flow migration, including: after a terminal establishes multiple access of the same packet data network (PDN) connection, through the third generation partnership project (3GPP) network signaling Stream migration information is negotiated with a packet data network gateway (P-GW), which migrates the data stream.

To solve the above technical problem, the present invention further provides a packet data network gateway (P-GW) for implementing stream migration, comprising a receiving module, a stream migration module, wherein:

 The receiving module is configured to: receive flow migration information sent by the terminal;

 The flow migration module is configured to: migrate the data flow according to the flow migration information received by the receiving module.

To solve the above technical problem, the present invention further provides a terminal for implementing stream migration, which includes establishing a connection module and a negotiation module, where:

 The establishing a connection module is configured to: establish multiple accesses of a same packet data network (PDN) connection;

The negotiation module is configured to: after the establishing connection module establishes multiple access of the same PDN connection, negotiate flow migration through a third generation partnership project (3GPP) network signaling and a packet data network gateway (P-GW). Information, the flow migration information is used by the P-GW to migrate the data flow. The method in the embodiment of the present invention is applied to the 3rd Generation Partnership Project (3GPP) evolved packet system (EPS), implements stream migration, and avoids modification and impact on the non-3GPP network. BRIEF abstract

 1 is a schematic diagram of a multiple access system architecture in the related art;

 Figure 2 is a flow chart of Embodiment 1 of the present invention;

 3 is a flow chart of Embodiment 2 of the present invention;

 4 is a flowchart of Embodiment 3 of the present invention;

 Figure 5 is a flow chart of Embodiment 4 of the present invention;

 Figure 6 is a flow chart of Embodiment 5 of the present invention;

 Figure 7 is a flow chart of Embodiment 6 of the present invention;

 Figure 8 is a flow chart of Embodiment 7 of the present invention;

 Figure 9 is a flow chart of Embodiment 8 of the present invention;

 Figure 10 is a flow chart of the ninth and tenth embodiments of the present invention;

 Figure 11 is a flowchart of the first mode of the eleventh embodiment of the present invention;

 FIG. 12 is a flowchart of Embodiment 2 of Embodiment 11 of the present invention; FIG.

 Figure 13 is a flowchart of the third mode of the eleventh embodiment of the present invention;

 Figure 14 is a flowchart of Embodiment 4 of Embodiment 11 of the present invention;

 Figure 15 is a flow chart of Embodiment 12 of the present invention;

 Figure 16 is a schematic structural view of Embodiment 15 of the present invention;

 Figure 17 is a schematic view showing the structure of a sixteenth embodiment of the present invention. Preferred embodiment of the invention

The scenario to be implemented by the embodiment of the present invention is: a scenario in which a PDN connection of a UE establishes multiple access, that is, a UE accesses the same PDN through a 3GPP access network and a non-3GPP access network, and acquires the same (or A pair of IP addresses, the P-GW establishes the same 3GPP access network and non-3GPP access The tunnel binding of the network.

 The design of the embodiment of the present invention is implemented by the following scheme:

 After the terminal establishes multiple accesses of the same PDN connection, the 3GPP network signaling and the P-GW collaborate to migrate the information, and the P-GW migrates the data stream, that is, the data stream is migrated from one access network to another.

 The migration of the data stream from one access network to another may be: migrating the IP data stream from the 3GPP access network to the non-3GPP access network, or migrating from the non-3GPP access network to the 3GPP access network, or The IP data stream is migrated from one non-3GPP access network to another non-3GPP access network.

 Specifically, when the P-GW performs any one of the following flow migration operations, reconfiguring the 3GPP network side bearer resources and the non-3GPP network side bearer resources, or reconfiguring only the 3GPP network side bearer resources: The IP data stream is sent from the 3GPP access network. Migrate to a non-3GPP access network or migrate IP data streams from a non-3GPP access network to a 3GPP access network. Alternatively, when the P-GW performs the following stream migration operation, reconfiguring the non-3GPP network side bearer resources, or not reconfiguring the resources: migrating the IP data streams from one non-3GPP access network to another non-3GPP access network.

 The P-GW may perform a flow migration operation after receiving the flow migration information, and then reconfigure the 3GPP network side bearer resource and/or the non-3GPP network side bearer resource; or the P-GW may also receive the flow. After the information is migrated, the 3GPP network side bearer resources and/or the non-3GPP network side bearer resources are reconfigured, and then the stream migration operation is performed.

 Regardless of which direction the terminal migrates the data stream, all negotiation messages are negotiated through the 3GPP side. Specifically, the terminal may send the flow migration information to the P-GW through 3GPP network signaling transmitted between the local terminal, the EUTRAN, the MME, and the S-GW; or, by using the terminal, the EUTRAN, the MME, the S-GW, and The 3GPP network signaling transmitted between the PCRF entities is sent to the P-GW; or, by the 3GPP network signaling transmitted between the local terminal, the UTRAN, the SGSN, and the S-GW, to the P-GW; or, by using the terminal The 3GPP network signaling transmitted between the UTRAN, the SGSN, the S-GW and the PCRF entity is sent to the P-GW. You can use enhanced existing messages when you negotiate, or you can use new messages.

Preferably, after the flow migration information is negotiated with the terminal, the P-GW may multiplex the process of reconfiguring the bearer resources of the 3GPP network side as a response to receive the flow migration information; or, the P-GW initiates a reconfiguration. The process of placing the 3GPP network side bearer resources is dedicated to receiving the flow migration information as a response.

 Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

 The following implementation schemes are an E-UTRAN network and a WLAN/fixed broadband network (fixed network) applicable to a 3GPP network as multiple access scenarios of two access networks, and also applicable to a UTRAN network and WLAN/fixed broadband of a 3GPP network. The network (fixed network) serves as a multiple access scenario for the two access networks.

 Embodiment 1:

 Referring to the flow shown in Figure 2, this embodiment negotiates flow migration information by enhancing existing signaling on the 3GPP side (EUTRAN). The network architecture based on it is the S5/8 interface using the GTP protocol. Proceed as follows:

 Step 201: The terminal UE has established multiple access from the 3GPP access network (EUTRAN) and the non-3GPP access network;

 Step 202: The UE decides to initiate a flow migration, and the UE initiates a “UE-initiated bearer resource modification” operation from the 3GPP network, and the UE sends a “Request Bearer Resource Modification” message of the NAS message family to the MME, where the message carries the flow migration information.

 For details of the flow migration information, refer to the description in Embodiment 13.

 Step 203: The MME sends a bearer resource command message of the GTP message family to the S-GW, where the message carries the flow migration information.

 Step 203a: The S-GW sends a "bearer resource command" message of the GTP message family to the P-GW, where the message carries the flow migration information.

 Preferably, after receiving the flow migration information, the P-GW may migrate the corresponding IP flow from the 3GPP network to the non-3GPP network or from the non-3GPP network to the 3GPP network according to the flow migration information. Alternatively, the P-GW may not perform the flow migration in this step, but migrate the IP data stream after the step 210.

 Step 204: Optional, P-GW and PCRF perform IP-CAN (IP-Connection Access)

Network, IP connection access network) session modification operation;

Step 204a: The P-GW decides to create a bearer or update a bearer or delete a bearer according to the received bearer resource command, and the P-GW sends a GTP message family to create a bearer request or update a bearer request or Delete bearer request" message to S-GW;

 To ensure reliability, the message may carry the flow migration information that the P-GW allows to migrate, and send it to the UE for confirmation. Or the message may not carry the flow migration information, which saves signaling overhead.

 In this embodiment, the P-GW initiates reconfiguration of the 3GPP network side bearer resources by sending any one of the following messages to the S-GW: creating a bearer request, updating a bearer request, and deleting a bearer request.

 Step 205: The S-GW sends the received message to the MME.

 Step 206: The MME sends a message corresponding to the received message to the eNB, where the message is, for example, a bearer setup message or a modify request message or a session management request message or a downlink NAS transport message or a deactivate bearer request message, where the message carries the P-GW. Allows migration of stream migration information or does not carry stream migration information;

 Step 207: The eNB sends an RRC connection reconfiguration message or a direct transmission message to the UE, where the message may carry the flow migration information that the P-GW allows to migrate or does not carry the flow migration information.

 Step 208: The dedicated bearer activates or bears the subsequent operation of modifying or carrying the deactivation.

 For the matching between the messages described in the above steps 204a-208, see 3GPP protocols TS23.401 and TS29.274.

 The above steps 204a-208 have two functions: first, as a response message of the request message (request message for stream migration) in steps 202-203a, that is, as a response to receive the stream migration information; second, as a 3GPP network The bearer resource on the side activates or updates or deactivates or modifies the operation, and the function is used to reconfigure the 3GPP network side bearer resources. In view of the second heavy function, the P-GW needs to send the message to the S-GW and the subsequent message, and carries the QoS information. Therefore, the step 204a needs to occur after the step 204, that is, the QoS information delivered by the P-GW is passed. Authorized by the PCRF.

 Step 209: The network side (P-GW or PCRF) initiates a resource activation or modification or deactivation operation on the non-3GPP access network side. Specifically, this step includes not only resource operations but also P-GW and non-3GPP access. The flow migration information negotiation operation between the gateway/eDPG is described in detail in the description in Example 11;

Step 210: Optionally, if the P-GW does not switch the IP data stream in different access networks after the step 203a, the P-GW may decide to use the flow migration information and the interaction with the PCRF in this step. The IP data stream is migrated from the 3GPP access network to the non-3GPP access network, or is connected by the non-3GPP. The network is migrated to the 3GPP access network.

 The interaction between the PGW and the PCRF and the interaction result means: the P-GW sends the flow migration information to the PCRF, and the PCRF determines the bandwidth and priority QoS guarantee required for the IP data flow, or determines whether the IP flow is suitable for a certain Transmission in the access network, or determining whether there is sufficient resources in the access network to be migrated, and the PCRF sends the determined result (such as authorized QoS information or whether the access network is allowed to transmit the IP flow) P-GW.

 The advantage of stream migration in step 210 is that stream migration is more QoS guaranteed.

 The above steps 204a-208 are reconfiguration of the bearer resources of the 3GPP network side, and step 209 is the reconfiguration of the bearer resources of the non-3GPP network side. When the data stream to be migrated migrates between the 3GPP and the non-3GPP, the above two processes are involved. When the migrated data stream is only migrated between non-3GPPs, the reconfiguration of the bearer resources of the 3GPP network side will not be involved. The reconfiguration of the 3GPP network side bearer resources and the reconfiguration of the non-3GPP network side bearer resources are not strictly sequential, and can be performed simultaneously.

Embodiment 2:

 Referring to the flow shown in Figure 3, this embodiment negotiates the flow migration information by enhancing the existing signaling of the 3GPP side (EUTRAN). The network architecture based on it is the S5/8 interface using the GTP protocol. The steps are similar to the first embodiment, but there are differences: In the first embodiment, the 204a-208 as the response signaling of the step 202-203a have the function of creating or updating or deleting resources on the 3GPP network side; but in this embodiment The function of the corresponding steps 304a-308 is only the response to the steps 302-303a, and in the steps 308a-308e, the role is the 3GPP network side bearer creation or update or deletion, which is the network initiated in the related art. Host resource creation or update or modification operations. Therefore, step 304a does not need to wait for step 304, that is, step 304 and step 304a do not have a strict sequence relationship.

 For the rest of the description, refer to the corresponding step of the first embodiment.

Embodiment 3:

Referring to the flow shown in FIG. 4, this embodiment negotiates flow migration information by enhancing existing signaling of the 3GPP side (EUTRAN). The network architecture based on the S5/8 interface uses the PMIPv6 protocol. Step The steps are as follows:

 Steps 401 - 403: the same steps 201 - 203;

 Step 403a: The S-GW sends a PBU (Roxy binding update) message to the P-GW, and the message carries the flow migration information.

 Step 404: Optionally, the P-GW and the PCRF perform an IP-CAN session modification operation. Step 404a: The P-GW sends a PB A (proxy binding Ack) message to the S-GW, where the message may carry the P - GW allows the migrated stream migration information or does not carry the stream migration information;

 In this embodiment, the P-GW sends a PBA message to the S-GW; the S-GW reconfigures the 3GPP network side bearer resource by initiating any one of the following messages: creating a bearer request, updating a bearer request, and deleting a bearer request operating. In addition to the PBA message, the P-GW may also trigger the S-GW to initiate reconfiguration of the 3GPP network side bearer resources by using a Binding Revocation Indicator (BRI) message or a new message.

 Steps 405-410: Same as steps 205-210.

 Optionally, after step 403a, the P-GW receives the flow migration information, that is, the corresponding IP flow is migrated from the 3GPP network to the non-3GPP network or from the non-3GPP network to the 3GPP network according to the flow migration information. Or in this step, the P-GW does not perform stream migration, but waits for 410 steps to migrate the IP data stream.

 The above steps 404a-408 have two functions: first, as a response message of the request message (request message for stream migration) in steps 402-403a; second, activation or update or deactivation as a bearer resource on the 3GPP network side Or modify the operation of a reconfigure resource function. In view of the second heavy function, the P-GW needs to send the PBA message and the subsequent message to the S-GW, and carries the QoS information. Therefore, the step 404a needs to occur after the step 404, that is, the QoS information delivered by the P-GW is Authorized by PCRF.

Embodiment 4:

Referring to the flow shown in FIG. 5, this embodiment negotiates flow migration information by enhancing existing signaling of the 3GPP side (EUTRAN). The network architecture based on the S5/8 interface uses the PMIPv6 protocol. The steps are similar to the third embodiment, but there are differences: In the third embodiment, as a response to steps 402-403a The signaling 404a-408 has the function of creating or updating or deleting resources on the 3GPP network side at the same time; but in this embodiment, the functions corresponding to steps 504a-508 are only responses to steps 502-503a, and in step 508a- 508g, the role of which is to create or update or delete a bearer on the 3GPP network side. This step is a network-initiated bearer resource creation or update or modification operation in the related art.

 For the rest of the description, refer to the corresponding steps of the third embodiment.

Embodiment 5:

 Referring to the flow shown in Fig. 6, this embodiment negotiates flow migration information by enhancing the existing signaling of the 3GPP side (EUTRAN) and PCC (Policy Charging and Control) signaling. The network architecture based on it is the PM56 protocol used by the S5/8 interface. Proceed as follows:

 Steps 601-603: the same steps 201-203;

 Step 603a: The S-GW initiates a gateway control and a QoS request operation to the PCRF, and carries the flow migration information to the PCRF;

 Step 604: The PCRF initiates an IP connection access network (IP-CAN) session modification operation to the P-GW, and sends the flow migration information to the P-GW.

 Step 604a: The PCRF sends a gateway control and QoS rule providing message to the S-GW;

 Optionally, in step 604, if the P-GW feeds back the migrated traffic migration information to the PCRF, the PCRF may send the migrated flow migration information to the S-GW.

 This step is an optional step, that is, the P-GW may directly perform the process after receiving the flow migration information, and does not need to feed back to the PCRF. Therefore, the PCRF does not need to perform this step to return the flow migration information to the S-GW.

 Preferably, in steps 604, 604a, the PCRF may send the authorized QoS information to the P-GW and the S-GW.

 The above steps 603a-604a are referred to as PCC (olicy control and charging) operations.

In this embodiment, the P-GW advertises the PCRF through the IP-CAN session modification operation, and the PCRF provides an operation notification S-GW through the gateway control and the QoS rule, and finally the S-GW initiates any one of the following messages. Reconfigure 3GPP network side bearer resources: Create bearer requests, updates Bear the request, delete the bearer request operation.

 Steps 605-610: Same as steps 205-210.

 Optionally, after step 604, the P-GW receives the flow migration information, that is, the corresponding IP flow is migrated from the 3GPP network to the non-3GPP network or from the non-3GPP network to the 3GPP network according to the flow migration information. Or in this step, the P-GW does not perform stream migration, but waits for 610 steps to migrate the IP data stream.

 The above steps 605-608 have two functions: first, as a response message of the request message (request message for stream migration) in steps 602-603; second, activation or update or deactivation as a bearer resource on the 3GPP network side Or modify the operation, this function is a reconfiguration resource function. In view of the second heavy function, the S-GW needs to send PBA messages and subsequent messages to the MME, carrying QoS information.

Example 6:

 Referring to the flow shown in Figure 7, this embodiment negotiates the flow migration information by enhancing the existing signaling of the 3GPP side (EUTRAN). The network architecture based on it is the PM56 protocol used by the S5/8 interface. The steps are similar to the fifth embodiment, but there are differences: In the fifth embodiment, the 605-608 as the response signaling of the steps 602-603 has the function of creating or updating or deleting resources on the 3GPP network side; but in this embodiment The function corresponding to steps 705-708 is only a response to steps 702-503, and in steps 708a-708g, the role is to create or update or delete the bearer on the 3GPP network side, which is initiated by the network in the related art. Host resource creation or update or modification operations.

 Steps 708a, 708f, 708g are optional steps, if in 703a, 704, 704a, PCRF

The S-GW and the P-GW send the authorized QoS information, and then steps 708a, 708f, 708g may skip execution, otherwise, 708a, 708f, 708g need to be executed for transmitting the QoS information.

 For the rest of the description, refer to the corresponding steps in the fifth embodiment.

Example 7:

 Referring to the flow shown in Fig. 8, this embodiment negotiates flow migration information through existing signaling on the 3GPP side (UTRAN system). Proceed as follows:

Step 801: The terminal UE has been constructed from a 3GPP access network (UTRAN) and a non-3GPP access network. Established multiple access;

 Step 802: The UE determines to initiate a flow migration, and the UE sends an “Activate PDP Context Request” message of the NAS message family to the SGSN, and carries the flow migration information.

 Step 803: the same step 203;

 Step 804: The operations that can be performed include: steps 203a-204a of the first embodiment, or steps 403a-404a of the third embodiment, or steps 603a-604a of the fifth embodiment;

 Step 805: the same step 205;

 Step 806: The SGSN, the RAN, and the UE function to negotiate the establishment of the radio access bearer. If the flow migration information that the P-GW allows to migrate is brought back in step 505, the flow migration information is brought to the UE in step 806.

 Step 807: Subsequent operation of PDP context activation;

 Steps 808-809: Same as steps 209-210.

 Optionally, in step 804, the P-GW receives the flow migration information, that is, the IP flow corresponding to the flow migration information is migrated from the 3GPP network to the non-3GPP network or from the non-3GPP network to the 3GPP network. Or in this step, the P-GW does not perform stream migration, but waits for step 809 to migrate the IP data stream.

 The above steps 805-806 have two functions: first, as a response message of the request message (request message for stream migration) in steps 402-803; second, activation or update or deactivation as a bearer resource on the 3GPP network side Or modify the operation, this function is a reconfiguration resource function. In view of the second heavy function, the P-GW needs to send a message to the S-GW, and the message sent by the S-GW to the MME and the subsequent message carry the QoS information.

Example 8:

Referring to the flow shown in FIG. 9, this embodiment negotiates flow migration information through existing signaling of the 3GPP side (UTRAN). The steps are similar to the seventh embodiment, but there are differences: In the seventh embodiment, the 805-807 as the response signaling of the steps 802-803 has the function of creating or updating or deleting resources on the 3GPP network side; In the example, the function corresponding to steps 905-907 is only the step The response of steps 902-903, and at step 907, its role is the PDP context activation operation initiated by the 3GPP network side. In addition, the operations that can be performed in step 904 include: steps 303a-304a of the second embodiment, or steps 503a-504a of the fifth embodiment, or steps 703a-704a of the seventh embodiment.

 For the rest of the description, refer to the corresponding step of the seventh embodiment.

Example 9:

 The difference between this embodiment and the embodiment one two three three is that the negotiation of the flow migration information does not enhance the existing flow or signaling, but realizes the negotiation of the flow migration information through a newly defined set of signaling.

 This embodiment first discusses the scenario in which the S5/8 interface uses the GTP protocol, and then adds a description to the differences in the PMIP scenario.

 Step 1001: The terminal UE has established multiple access from the 3GPP access network (EUTRAN or UTRAN) and the non-3GPP access network;

 Step 1002: The UE decides to initiate a flow migration, and the UE sends a “request message A” to the MME or the SGSN to carry the flow migration information.

 Step 1003: The MME or the SGSN sends a request message B to the S-GW, where the message carries the flow migration information.

 If the UE accesses from the EUTRAN, the request message is sent by the MME, and if the UE accesses from the UTRAN, the request message is sent by the SGSN.

 Step 1003a: The S-GW sends a request message C to the P-GW, where the message carries the flow migration information. Step 1004: Optionally, the P-GW and the PCRF perform an IP-CAN session modification operation. Step 1004a: The P-GW sends a response. The message C is sent to the S-GW, and the message may carry the flow migration information that the P-GW is allowed to migrate or does not carry the flow migration information.

 The above steps 1004 and 1004a do not have a strict sequence relationship.

 Step 1005: The S-GW sends a response message B to the MME/SGSN. The message may carry the flow migration information that the P-GW allows to migrate or does not carry the flow migration information.

Step 1006: The MME/SGSN sends a response message A to the UE, where the message may carry the P-GW. Allows migration of stream migration information or does not carry stream migration information;

 Step 1007-1008: Since the P-GW receives the flow migration information, the P-GW initiates a corresponding bearer operation on the 3GPP access network and the non-3GPP access network respectively.

 Step 1009: Same as step 210.

 In this embodiment, both the request message A and the response message A may be messages of the NAS message family, and the request message B, the response message ^ request message, and the response message C may all be messages of the GTP message family.

Example 10:

 The scenario based on the ninth embodiment is a scenario in which the S5/8 interface uses the GTP protocol. When the S5/8 interface uses the PMIPv6 protocol, the steps 1003a-1004a in the ninth embodiment can be as follows:

 Step 1003a: The S-GW sends a request message C1 to the P-GW, where the message carries the flow migration information. The C1 message is an enhancement of the PBU message or a new message of the PMIPv6 protocol family;

 Step 1004: Optionally, the P-GW and the PCRF perform an IP-CAN session modification operation. Step 1004a: The P-GW sends a response message C2 to the S-GW. The message may carry the flow migration information that the P-GW allows to migrate or does not carry the flow migration information. The C2 message is an enhancement of the PBA message or a new message of the PMIPv6 protocol family.

 Except for the above steps 1003a to 1004a, the remaining steps are the same as those in the embodiment 9.

Method 2:

 Steps 1003a-1004a in this embodiment are not referred to FIG. 10, but refer to steps 603a-604a of FIG. 6. The related description also refers to the corresponding description of FIG. 6, and the remaining steps refer to the correlation of Embodiment 9 (FIG. 10). description.

Example 11:

This embodiment describes the non-3GPP access network side involved in the above embodiments 1 to 10. Detailed steps for loading or modifying or deactivating a resource. Reconfiguring the non-3GPP network side bearer resources includes: the P-GW negotiates a tunnel entry between the two through the message with the ePDG, or the P-GW negotiates the tunnel entry between the two through the message with the non-3GPP access gateway.

 In view of the S2b interface between the P-GW and the ePDG and the S2a interface between the P-GW and the non-3GPP access gateway, or the GTP protocol or the PMIPv6 protocol, the P-GW and the ePDG/non-3GPP access gateway The description between them is also divided into several scenarios, corresponding to different ways.

 Manner 1: See Figure 11. The GTP protocol is used between the P-GW and the ePDG/non-3GPP access gateway.

 Step 1101: The P-GW sends a "create bearer request or update bearer request or delete bearer request" of the GTP message family to the ePDG/non-3GPP access gateway;

 Step 1102: Optionally, the bearer resource is configured in the non-3GPP access network.

 If the ePDG/non-3GPP access gateway does not support radio resource configuration, then step 1102 need not be performed.

 Step 1103: The ePDG/non-3GPP access gateway sends a "Create Bearer Response or Update Bearer Response or Delete 7-Load Response" to the P-GW.

 Steps 1101 and 1103 have the following two functions:

 1. Send QoS information to the ePDG/non-3GPP access gateway;

 2. Establish, update, or delete a GTP tunnel between the P-GW and the ePDG/non-3GPP access gateway to implement flow migration. That is, when the operation of the bearer is established or updated by step 1101 and step 1103, the GTP tunnel is established or updated after the step between the ePDG/non-3GPP access gateway and the P-GW, that is, the GTP tunnel entry is established. Or updating the GTP tunnel entry, after the P-GW migrates the IP stream to the non-3GPP, and transmits the GTP tunnel; when the GTP tunnel is deleted through steps 1101 and 1103, the ePDG/non-3GPP access gateway and the P-GW are in the After the step, the original GTP tunnel is removed, and the P-GW migrates the IP stream to 3GPP and no longer transmits through the GTP tunnel.

Manner 2: Referring to Figure 12, the PMIPv6 protocol is used between the P-GW and the ePDG/non-3GPP access gateway.

Step 1201: The P-GW sends an enhanced BRI of the PMIPv6 message family (Binding revocation Indication, binding revocation indication) message to the ePDG/non-3GPP access gateway;

 The P-GW carries the "streaming information" it allows to migrate to the ePDG/non-3GPP access gateway. Step 1202: Optionally, the bearer resource is configured in the non-3GPP access network.

 Step 1203: The ePDG/non-3GPP access gateway sends an "enhanced BRA (binding revocation Ack)" to the P-GW.

 Step 1201 and step 1203 have the following functions:

 The PMIP tunnel between the P-GW and the ePDG/non-3GPP access gateway is updated to implement flow migration. That is to say, after the step 1101 and the step 1103, the BCE (Buinet cache entry) is updated on the P-GW, and the binding update list entry (BULE) is updated on the ePDG/non-3GPP access gateway. Update the list entry), so that the P-GW migrates the IP flow to the non-3GPP according to the updated BCE. Through the updated PMIP tunnel transmission, the ePDG/non-3GPP access gateway can also transmit the migration with the P-GW due to the update of the BULE. The data stream of the packet.

Mode 3: Referring to Figure 13, the PMIPv6 protocol or GTP protocol is used between the P-GW and the ePDG/non-3GPP access gateway.

 Step 1301: The P-GW sends a newly defined request message D of the PMIPv6 message family, or a newly defined request message D of the GTP protocol family, to the ePDG/non-3GPP access gateway;

 Optionally, the P-GW carries the "stream migration information" that it allows to migrate to the ePDG/non-3GPP access gateway.

 Step 1302: Optionally, configuring a bearer resource in the non-3GPP access network;

 Step 1303: The ePDG/non-3GPP access gateway sends a newly defined response message D of the PMIPv6 message family, or a newly defined response message D of the GTP protocol family, to the P-GW.

 The functions of step 1301 and step 1303:

 1. If 1301 and 1303 are GTP family messages, the functions are the same as 1101 and 1103;

 2. If 1301 and 1303 are messages of the PMIP family, the functions are the same as 1201 and 1203.

Method 4: Referring to Figure 14, PMIPv6 is used between P-GW and ePDG/non-3GPP access gateways. In this mode, the bearer operation is initiated by the PCC operation, and there is no interaction signaling between the ePDG/non-3GPP access network gateway and the P-GW.

 Step 1401: The PCRF initiates a gateway control and a QoS rule providing operation;

 Optionally, the PCRF carries the "stream migration information" that it allows to migrate to the ePDG/non-3GPP access gateway.

 Step 1402: Configure bearer resources in the non-3GPP access network.

Mode 5: Integrating Figure 12 and Figure 14, or combining Figures 13 and 14, the PMIPv6 protocol is used between the P-GW and the ePDG/non-3GPP access gateway. This mode initiates bearer operations through PCC operations, through enhanced BRI/BRA. The message, or the newly added request message D/send response message D, negotiates the flow migration information between the P-GW and the ePDG/non-3GPP access network gateway.

Example 12:

 The operation of the non-3GPP access network gateway/ePDG and the P-GW to negotiate the flow migration information is discussed in the embodiment 11. The embodiment discusses the operation of negotiating the flow migration information between the S-GW and the P-GW on the 3GPP side. Steps: When the PMIPv6 protocol is used in S5/8, except that the S-GW and the P-GW discussed in the foregoing embodiments pass:

 1) Enhanced PBU/PBA (Figures 4 and 5)

 2) PCC operation (Figure 6 and Figure 7)

 3) Request message C/Response message C (Figure 10)

 In addition to the operation of negotiating the flow migration information, before the P-GW performs the flow migration operation, the P-GW and the S-GW can also perform the following operations (see FIG. 15): The P-GW will actively pass the enhanced BRI/BRA message ( That is, the BRI/BRA message carrying the "Streaming Information", or the newly added PMIP message (Request Message E/Response Message E) to negotiate with the S-GW to update the PMIP tunnel entry. The role of the update tunnel is:

Note: The "stream migration information" carried here may not be exactly the same as the stream migration information content and form sent by the terminal to the P-GW, because there may be flow migration information allowed after the P-GW processing. The PMIP tunnel between the P-GW and the S-GW is updated to implement flow migration. That is to say, after step 1501 and step 1502, the P-GW updates the BCE (binding cache entry), and the S-Gw updates the BULE (binding update list entry). In this way, the P-GW migrates the IP stream to the 3GPP according to the updated BCE. Through the updated PMIP tunnel transmission, the S-GW can also transmit the data packet of the migrated data stream with the P-GW because the BULE is updated.

Example 13:

 This embodiment is to demonstrate the "stream migration information" in the above embodiment. The stream migration information includes at least: identifier information of the IP stream, identifier information of the access network, and association relationship between the IP stream and the access network.

 The information of the identifier flow may be a flow ID, or a packet filter (PF), or a TFT, or a temporary sequence number that identifies the access network.

 The access network identification information may be: an access network type (such as an EUTRAN access network, a UTRAN access network, a WLAN access network), or an identifier of the network element in the access network (S-GW/MME address or FQDN) , or ePDG address or FQDN, or non-3GPP access gateway address/FQDN), or one other identifier in the access network that uniquely identifies the access network (such as the default bearer identifier LBI in the 3GPP network (linked bearer) ID ) ) , or a data label generated by the P-GW according to the access sequence (such as access 1 , access network 2 ).

 The association between the IP flow and the access network refers to: an IP flow is transmitted in an access network, and the binding relationship between the flow information (flow ID or packet filter or TFT) and the access network identifier is identified.

 For example, the flow migration information sent by the UE to the core network may be in the following form:

 Flow ID-x<——>WLAN (access network type)

 Or: [PF-y+Flow ID-y] <—— >ePDG IP address (network address)

 Or: TFT-z (or part of TFT-z) <->LBI-xx (3GPP default bearer identifier) or: TFT-u (or part of TFT-u) <-> access network 1 (this connection The network access number can be recognized by both the P-GW and the UE).

The above "<->" indicates an association. The first example shows that the UE requests the IP data stream whose stream is identified as X to be transmitted to the WLAN access network.

 After the P-GW receives the information, if the IP stream is originally transmitted on the WLAN access network, the P-GW does not change. If the original IP stream is transmitted in the 3GPP access network, then the P-GW The IP stream whose stream is identified as X is migrated from the 3GPP access network to the WLAN access network according to the flow migration information.

 The flow migration information that the P-GW allows to migrate refers to the flow migration information of the one or more flows carried in the flow migration information, which allows the flow migration information of the migrated data flow.

Example 14: Promotion

 The above embodiment is a specific implementation in the scenario where the terminal accesses the 3GPP access network and the other non-3GPP access network at the same time. The solution can be extended to the scenario where multiple access networks exist simultaneously, and the terminal can also access the 3GPP access network. The signaling interaction on the side negotiates the flow migration information, so that the data flow is forward or reverse between the 3GPP access network and the non-3GPP access network, and between the multiple non-3GPP access networks.

Embodiment 15: P-GW implementing stream migration

 As shown in FIG. 16, the P-GW that implements the flow migration includes a receiving module and a flow migration module, where: the receiving module is configured to receive flow migration information sent by the terminal;

 The flow migration module is configured to migrate the data flow according to the flow migration information received by the receiving module. Preferably, the stream migration module is configured to migrate the data stream according to the stream migration information received by the receiving module in the following manner:

 The flow migration module performs a flow migration operation after receiving the flow migration information, and reconfigures the 3GPP network side bearer resource and/or the non-3GPP network side bearer resource; or

 After receiving the stream migration information, the stream migration module reconfigures the 3GPP network side bearer resources and/or the non-3GPP network side bearer resources, and then performs the stream migration operation.

Preferably, the P-GW further includes a response module for multiplexing the reconfiguration 3GPP network side bearing The process of carrying the resource is a response to receiving the flow migration information; or the process of initiating a reconfiguration of the 3GPP network side bearer resource is dedicated to receiving the flow migration information as a response.

 Preferably, the flow migration module is configured to perform a flow migration operation in the following manner, and reconfigure the 3GPP network side bearer resource and/or the non-3GPP network side bearer resource:

 When the flow migration module performs any of the following flow migration operations, reconfigure the 3GPP network side bearer resources and the non-3GPP network side bearer resources, or only reconfigure the 3GPP network side bearer resources: migrate the IP data stream from the 3GPP access network to The non-3GPP access network, or the IP data stream is migrated from the non-3GPP access network to the 3GPP access network; or the flow migration module performs the following flow migration operation, reconfiguring the non-3GPP network side bearer resources, or not reconfiguring Resource: Migrate IP data streams from one non-3GPP access network to another non-3GPP access network.

 The flow migration module is configured to reconfigure 3GPP network side bearer resources and/or non-3GPP network side bearer resources in the following manner, and then perform a stream migration operation:

 The flow migration module reconfigures 3GPP network side bearer resources and non-3GPP network side bearer resources, or reconfigures only 3GPP network side bearer resources when performing any of the following flow migration operations: Migrating IP data flows from the 3GPP access network to The non-3GPP access network, or the IP data stream is migrated from the non-3GPP access network to the 3GPP access network; or the flow migration module is configured to reconfigure the non-3GPP network side bearer resources, or not Configure resources: Migrate IP data flows from one non-3GPP access network to another non-3GPP access network.

 Preferably, the flow migration module is configured to reconfigure the 3GPP network side bearer resources in the following manner:

 The flow migration module initiates reconfiguration of the 3GPP network side bearer resource by sending any one of the following messages to the S-GW: creating a bearer request, updating a bearer request, and deleting a bearer request; or the flow migration module sends the S-GW to the S-GW. Any one of the following messages: a proxy binding acknowledgement (PBA) message, a binding revocation indication (BRI) message, a new message, and a reconfiguration of the 3GPP network side bearer resource by the S-GW; or

The flow migration module advertises an operation notification PCRF through an IP connection access network (IP-CAN) session, and the S-GW is advertised by the PCRF, and finally the S-GW initiates reconfiguration of the 3GPP network side bearer resource. Preferably, the stream migration module is further configured to negotiate to update the PMIP tunnel entry with the S-GW by using a BRI message carrying the flow migration information or a newly added PMIP message before performing the stream migration operation.

 Preferably, the flow migration module is configured to reconfigure the non-3GPP network side bearer resource in the following manner: the flow migration module negotiates a tunnel entry between the two with the ePDG by using any of the following messages, or the P- The GW negotiates the tunnel entry between the two with the non-3GPP access gateway by any of the following messages: Create a bearer request, update a bearer request, delete a bearer request, a BRI message, a new message.

 The foregoing flow migration information includes identifier information of the IP data stream to be migrated, access network identifier information, and an association relationship between the IP data stream and the access network.

Embodiment 15: A terminal that implements stream migration

 As shown in FIG. 17, the terminal for implementing the flow migration includes a connection establishment module and a negotiation module, where: the establishing connection module is used to establish multiple access of the same PDN connection;

 The negotiation module is configured to negotiate flow migration information with the P-GW through the 3GPP network signaling after the establishing connection module establishes multiple access of the same PDN connection, where the flow migration information is used for the P- GW migrates the data stream.

 Preferably, the negotiation module is configured to negotiate the flow migration information with the P-GW through the 3GPP network signaling in the following manner, including:

 The negotiation module sends the flow migration information to the P-GW through 3GPP network signaling transmitted between the local terminal, the EUTRAN, the MME, and the S-GW; or

 The negotiation module sends the flow migration information to the P-GW through 3GPP network signaling transmitted between the local terminal, the EUTRAN, the MME, the S-GW, and the PCRF entity; or

 The negotiation module sends the flow migration information to the P-GW through 3GPP network signaling transmitted between the terminal, the UTRAN, the SGSN, and the S-GW; or

 The negotiation module passes the flow migration information through the terminal, the UTRAN, the SGSN, the S-GW, and

The 3GPP network signaling transmitted between the PCRF entities is sent to the P-GW.

Preferably, the flow migration information includes identifier information of the IP data stream to be migrated, and an access network identifier. Information, and an association relationship between the IP data stream and the access network.

Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or they may be Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any particular combination of hardware and software.

 The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial Applicability The method described in the embodiments of the present invention is applied to a third generation partnership project (3GPP) evolved packet system (EPS), which implements stream migration and avoids modification and impact on non-3GPP networks.

Claims

Claim  1. A method for implementing flow migration, comprising:  After the terminal establishes multiple accesses of the same packet data network (PDN) connection, the flow migration information is negotiated with the packet data network gateway (P-GW) through the third generation partnership project (3GPP) network signaling, the P-GW Migrate the data stream.  2. The method of claim 1 wherein  The negotiating the flow migration information with the P-GW by using the 3GPP network signaling includes:  The terminal sends the flow migration information to the P-through through 3GPP network signaling transmitted between the terminal, the evolved universal terrestrial radio access network (EUTRAN), the mobility management unit (MME), and the serving gateway (S-GW). GW; or  Transmitting, by the terminal, flow migration information to 3GPP network signaling transmitted between the local terminal, the evolved universal terrestrial radio access network (EUTRAN), the MME, the S-GW, and the Policy and Charging Rules Function (PCRF) entity P-GW; or  The terminal sends the flow migration information to the P-GW through 3GPP network signaling transmitted between the local terminal, the universal terrestrial radio access network (UTRAN), the general packet radio service (SGSN), and the serving gateway (S-GW) ; or  The terminal sends the flow migration information to the P-through through 3GPP network signaling transmitted between the local terminal, the universal terrestrial radio access network (UTRAN), the SGSN, the S-GW, and the Policy and Charging Rules Function (PCRF) entity. GW.  3. The method according to claim 1 or 2, wherein  The P-GW migrates the data stream, including:  After receiving the flow migration information, the P-GW performs a flow migration operation, and reconfigures the 3GPP network side bearer resources and/or the non-3GPP network side bearer resources; or  After receiving the flow migration information, the P-GW reconfigures the 3GPP network side bearer resources and/or the non-3GPP network side bearer resources, and performs a stream migration operation.  4. The method of claim 3, wherein After the flow migration information is negotiated, the method further includes: The P-GW multiplexing reconfigures a 3GPP network side bearer resource as a response to receive the flow migration information; or  The process by which the P-GW initiates a reconfiguration of the 3GPP network side bearer resources is dedicated to receiving a response to the flow migration information.  5. The method of claim 3, wherein  The P-GW performs a stream migration operation, and reconfigures the 3GPP network side bearer resources and/or the non-3GPP network side bearer resources, including:  When the P-GW performs any one of the following stream migration operations, reconfigure the 3GPP network side bearer resource and the non-3GPP network side bearer resource, or only reconfigure the 3GPP network side bearer resource: migrate the IP data stream from the 3GPP access network To a non-3GPP access network, or to migrate IP data streams from a non-3GPP access network to a 3GPP access network; or  When the P-GW performs the following stream migration operation, reconfigure the non-3GPP network side bearer resources, or not reconfigure the resources: Migrate the IP data stream from one non-3GPP access network to another non-3GPP access network.  6. The method of claim 3, wherein  The P-GW reconfigures the 3GPP network side bearer resource and/or the non-3GPP network side bearer resource, and then performs a stream migration operation, including:  When the P-GW is to perform any one of the following stream migration operations, reconfigure the 3GPP network side bearer resources and the non-3GPP network side bearer resources, or only reconfigure the 3GPP network side bearer resources: The IP data stream is from the 3GPP access network. Migrating to a non-3GPP access network, or migrating IP data streams from a non-3GPP access network to a 3GPP access network; or  When the P-GW is to perform the following flow migration operation, reconfigure the non-3GPP network side bearer resources, or not reconfigure the resources: Migrate the IP data flows from one non-3GPP access network to another non-3GPP access network.  7. The method of claim 3, wherein  The reconfiguring 3GPP network side bearer resources includes: The P-GW initiates reconfiguration of the 3GPP network side bearer resource by sending any one of the following messages to the S-GW: creating a bearer request, updating a bearer request, and deleting a bearer request; or The P-GW sends any one of the following messages to the S-GW: a proxy binding acknowledgement (PBA) message, a binding revocation indication (BRI) message, a new message; the S-GW initiates any one of the following messages Reconfiguring 3GPP network side bearer resources: creating a bearer request, updating a bearer request, and deleting a bearer request operation; or  The P-GW advertises an operation notification PCRF through an IP connection access network (IP-CAN) session, The PCRF provides an operation notification S-GW through the gateway control and QoS rules, and the S-GW reconfigures the 3GPP network side bearer resources by sending any one of the following messages: creating a bearer request, updating a bearer request, and deleting a bearer request operation.  8. The method of claim 7, wherein  Before the P-GW performs a stream migration operation, the method further includes:  The P-GW negotiates and updates the PMIP tunnel entry with the S-GW through a BRI message carrying the flow migration information or a newly added PMIP message.  9. The method of claim 3, wherein  The reconfiguring non-3GPP network side bearer resources includes:  The P-GW negotiates a tunnel entry between the two with an evolved packet data gateway (ePDG), or the P-GW negotiates the two with a non-3GPP access gateway by using any of the following messages: Tunnel entries between: Create Bearer Request, Update Bearer Request, Delete Bearer Request, BRI Message, New Message.  10. The method of claim 1, wherein  The flow migration information includes identifier information of the IP data stream to be migrated, access network identifier information, and an association relationship between the IP data stream and the access network.  11. The method of claim 2, wherein  The terminal sends the flow migration information to the P-GW through the 3GPP network signaling that is transmitted between the local terminal, the EUTRAN, the MME, and the S-GW, and includes:  Transmitting, by the EUTRAN, the first message carrying the flow migration information to the MME by using the EUTRAN, After receiving the first message, the MME sends a second message carrying the flow migration information to the S-GW, and the S-GW sends a third message carrying the flow migration information to the P-GW. 12. The method of claim 11 wherein  The first message is a request bearer resource modification message, and the second message and the third message are both bearer resource commands; or  The first message is a request bearer resource modification message, the second message is a bearer resource command, and the third message is a PBU message.  13. The method of claim 2, wherein  The terminal sends the flow migration information to the P-GW through the 3GPP network signaling that is transmitted between the terminal, the UTRAN, the SGSN, and the S-GW, and includes:  The terminal sends a fourth message carrying the flow migration information to the SGSN by using the UTRAN, and after receiving the fourth message, the SGSN sends a fifth message carrying the flow migration information to the S-GW, where the S-GW goes to the P The GW sends a sixth message carrying the flow migration information.  14. The method of claim 13 wherein  The fourth message is an activated PDP context request message, where the fifth message and the sixth message are both bearer resource commands; or  The fourth message is an activated PDP context request message, the fifth message is a bearer resource command, and the sixth message is a PBU message.  15. The method of claim 2, wherein  The terminal sends the flow migration information to the P-GW through the 3GPP network signaling that is transmitted between the local terminal, the EUTRAN, the MME, the S-GW, and the PCRF entity, including:  Transmitting, by the EUTRAN, the seventh message carrying the flow migration information to the MME by using the EUTRAN, After receiving the seventh message, the MME sends an eighth message carrying the flow migration information to the S-GW, and the S-GW sends a ninth message carrying the flow migration information to the PCRF, where the PCRF sends the bearer to the P-GW. The tenth message of the stream migration information.  16. The method of claim 15, wherein The seventh message is a request bearer resource modification message, the eighth message is a bearer resource command, the ninth message is a gateway control QoS rule request message, and the tenth message is an IP connection access network (IP-CAN) ) Session modification message. 17. The method of claim 13 wherein  The terminal sends the flow migration information to the P-GW through the 3GPP network signaling transmitted between the local terminal, the UTRAN, the SGSN, the S-GW, and the PCRF entity, including:  The terminal sends an eleventh message carrying the flow migration information to the SGSN by using the UTRAN, and after receiving the eleventh message, the SGSN sends a twelfth message carrying the flow migration information to the S-GW, where the S- The GW sends a thirteenth message carrying the flow migration information to the PCRF, and the PCRF sends a fourteenth message carrying the flow migration information to the P-GW.  18. The method of claim 17, wherein  The eleventh message is an activated PDP context request message, the twelfth message is a bearer resource command, the thirteenth message is a gateway control QoS rule request message, and the fourteenth message is an IP-CAN session modification. Message.  19. The method of claim 16 or 18, wherein  When the PCRF sends an IP-CAN session modification message carrying the flow migration information to the P-GW, the PCR message carries the QoS information in the IP-CAN session modification message.  20. A packet data network gateway (P-GW) for implementing stream migration, comprising a receiving module, a stream migration module, wherein:  The receiving module is configured to: receive flow migration information sent by the terminal;  The flow migration module is configured to: migrate the data flow according to the flow migration information received by the receiving module.  21. The P-GW according to claim 20, wherein  The flow migration module is configured to: migrate the data flow according to the flow migration information received by the receiving module in the following manner:  The flow migration module performs a flow migration operation after the receiving module receives the flow migration information, and reconfigures the 3GPP network side bearer resources and/or the non-3GPP network side bearer resources; or  After the receiving module receives the stream migration information, the stream migration module reconfigures the 3GPP network side bearer resource and/or the non-3GPP network side bearer resource, and then performs a stream migration operation. 22. The P-GW according to claim 20, wherein The P-GW further includes a response module, configured to: multiplex the process of reconfiguring the 3GPP network side bearer resource as a response to receive the flow migration information; or initiate a process of reconfiguring the 3GPP network side bearer resource, which is dedicated to receiving The response of the stream migration information.  23. The P-GW according to claim 21, wherein  The flow migration module is configured to: perform a flow migration operation in the following manner, and reconfigure 3GPP network side bearer resources and/or non-3GPP network side bearer resources:  When the flow migration module performs any of the following flow migration operations, reconfigure the 3GPP network side bearer resource and the non-3GPP network side bearer resource, or only reconfigure the 3GPP network side bearer resource: Migrate the IP data stream from the 3GPP access network To a non-3GPP access network, or to migrate IP data streams from a non-3GPP access network to a 3GPP access network; or  When the flow migration module performs the following flow migration operation, reconfigure the non-3GPP network side bearer resources, or not reconfigure the resources: migrate the IP data flows from one non-3GPP access network to another non-3GPP access network.  24. The P-GW according to claim 21, wherein  The flow migration module is configured to: first reconfigure the 3GPP network side bearer resource and/or the non-3GPP network side bearer resource in the following manner, and then perform a stream migration operation:  The flow migration module reconfigures the 3GPP network side bearer resource and the non-3GPP network side bearer resource, or only reconfigures the 3GPP network side bearer resource when performing any one of the following stream migration operations: The IP data stream is removed from the 3GPP access network. Migrating to a non-3GPP access network, or migrating IP data streams from a non-3GPP access network to a 3GPP access network; or  The flow migration module reconfigures non-3GPP network side bearer resources when the flow migration operation is performed, or does not reconfigure resources: Migrate IP data flows from one non-3GPP access network to another non-3GPP access network.  The P-GW according to claim 23 or 24, wherein The flow migration module is configured to: reconfigure the 3GPP network side bearer resource in the following manner: The flow migration module initiates reconfiguration of the 3GPP network side bearer resource by sending any one of the following messages to the S-GW: Requesting, updating a bearer request, deleting a bearer request; or the flow migration module sends any of the following messages to the S-GW: Proxy Binding Confirmation (PBA) a message, a binding revocation indication (BRI) message, a new message, and a reconfiguration of the 3GPP network side bearer resource by the S-GW; or  The flow migration module advertises an operation notification PCRF through an IP connection access network (IP-CAN) session, and the S-GW is advertised by the PCRF, and finally the S-GW initiates reconfiguration of the 3GPP network side bearer resource.  26. The P-GW according to claim 25, wherein  The stream migration module is further configured to: update the PMIP tunnel entry with the S-GW by using a BRI message carrying the flow migration information or a newly added PMIP message before performing the stream migration operation.  27. The P-GW according to claim 23 or 24, wherein  The flow migration module is configured to: 重 reconfigure non-3GPP network side bearer resources in the following manner:  The flow migration module negotiates a tunnel entry between the two with an evolved packet data gateway (ePDG), or the P-GW negotiates the two with a non-3GPP access gateway by using any of the following messages: Tunnel entries between: Create Bearer Request, Update Bearer Request, Delete Bearer Request, BRI Message, New Message.  28. The P-GW according to claim 20, wherein  The flow migration information includes identifier information of the IP data stream to be migrated, access network identifier information, and an association relationship between the IP data stream and the access network.  A terminal for implementing flow migration, comprising: establishing a connection module, and a negotiation module, wherein: the establishing connection module is configured to: establish multiple access of a same packet data network (PDN) connection;  The negotiation module is configured to: after the establishing connection module establishes multiple access of the same PDN connection, negotiate flow migration through a third generation partnership project (3GPP) network signaling and a packet data network gateway (P-GW). Information, the flow migration information is used by the P-GW to migrate the data flow.  30. The terminal of claim 29, wherein The negotiation module is configured to: negotiate the flow migration information with the P-GW through the 3GPP network signaling in the following manner, including: The negotiation module passes the flow migration information through the local terminal, the evolved universal terrestrial radio access network 3GPP network signaling transmitted between (EUTRAN), mobility management unit (MME) and serving gateway (S-GW) to the P-GW; or  The negotiation module sends the flow migration information through 3GPP network signaling transmitted between the local terminal, the evolved universal terrestrial radio access network (EUTRAN), the MME, the S-GW, and the Policy and Charging Rules Function (PCRF) entity. To P-GW; or  The negotiation module sends the flow migration information to the P- through 3GPP network signaling transmitted between the local terminal, the universal terrestrial radio access network (UTRAN), the general packet radio service (SGSN), and the serving gateway (S-GW). GW; or  The negotiation module passes the flow migration information to the terminal, the universal terrestrial radio access network The 3GPP network signaling passed between the (UTRAN), SGSN, S-GW, and Policy and Charging Rules Function (PCRF) entities is sent to the P-GW.  31. The terminal of claim 29, wherein  The flow migration information includes identifier information of the IP data stream to be migrated, access network identifier information, and an association relationship between the IP data stream and the access network.