WO2017084042A1 - 一种业务流的传输方法及装置 - Google Patents

一种业务流的传输方法及装置 Download PDF

Info

Publication number
WO2017084042A1
WO2017084042A1 PCT/CN2015/094907 CN2015094907W WO2017084042A1 WO 2017084042 A1 WO2017084042 A1 WO 2017084042A1 CN 2015094907 W CN2015094907 W CN 2015094907W WO 2017084042 A1 WO2017084042 A1 WO 2017084042A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
gateway
bearer
service
information
Prior art date
Application number
PCT/CN2015/094907
Other languages
English (en)
French (fr)
Inventor
陈中平
周汉
夏渊
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2015/094907 priority Critical patent/WO2017084042A1/zh
Priority to EP15908539.8A priority patent/EP3361816A1/en
Priority to CN201580082384.9A priority patent/CN107926066B/zh
Publication of WO2017084042A1 publication Critical patent/WO2017084042A1/zh
Priority to US15/972,370 priority patent/US20180255481A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H04W28/12—Flow control between communication endpoints using signalling between network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/17—Selecting a data network PoA [Point of Attachment]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels

Definitions

  • the embodiments of the present invention relate to the field of wireless communications technologies, and in particular, to a method and an apparatus for transmitting a service flow.
  • FIG. 1 is a schematic diagram of a network architecture of an EPS disclosed in the prior art. In the EPS network architecture shown in FIG.
  • the evolved packet core network mainly includes a Mobility Management Entity (MME), a Serving Gateway (S-GW), and a Packet Data Gateway.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • the user equipment when the user equipment (UE, User Equipment) accesses the EPC, it first needs to be based on the Access Point Name (APN) information (default configuration or provided by the UE).
  • APN Access Point Name
  • create a PDN connection also known as a "session connection" that the APN points to.
  • the UE is provided with a corresponding IP address.
  • the first bearer created in the session connection is called the default bearer (which remains active during the entire session connection period), and the bearer created later is proprietary. Hosted.
  • FIG. 2 is a schematic diagram of network deployment of an EPS disclosed in the prior art. In the network deployment shown in Figure 2, one service flow is bound to one bearer, one bearer is bound to one PDN connection, one PDN connection is anchored to a specific gateway, and the service flow with the same APN information is finally connected to the same PDN.
  • the service flows with different APN information are finally connected to different PDN networks. It can be seen that the current EPS network deployment can only flexibly access the PDN network and the flexible deployment of service flows in the PDN network. It can be seen that the deployment of service flows in the current EPS has a problem of low flexibility.
  • the embodiment of the invention discloses a method and a device for transmitting a service flow, which can improve the flexibility of service flow deployment.
  • a first aspect of the embodiments of the present invention discloses a method for transmitting a service flow, where the method includes:
  • the first gateway device determines a target service currently performed by the user equipment UE, where the target service may be a service for accessing a website, a call service, or an instant messaging service;
  • the first gateway device performs a bearer processing operation to obtain a target bearer corresponding to the target service, and binds the service flow of the target service to the target bearer, where the bearer processing operation may include a bearer creation process. Or bear the modification process;
  • the first gateway device anchors the target bearer with the target gateway, and completes service flow transmission between the UE and the network corresponding to the target service by using the target gateway, where the target bearer and the target are Gateway anchoring is to send the context information of the target bearer to the target gateway.
  • the flexible deployment of the service flow is realized by binding the service flow to the target bearer obtained by performing the bearer processing operation and anchoring the target bearer and the target gateway.
  • the method further includes:
  • the first gateway device selects the target gateway for the target service according to the corresponding relationship between the service and the gateway deployment.
  • the method of selecting the target gateway according to the correspondence between the service and the gateway deployment can Selecting different target gateways for service flows with the same APN information, and then enabling service flows with the same APN information to access different PDN networks, and implementing flexible deployment of service flows in the PDN network.
  • the first gateway device is configured according to the corresponding relationship between the service and the gateway deployment. Selecting the target gateway by the target service, including:
  • the first gateway device determines, according to a correspondence between the service and the gateway deployment, a list of target gateways that can provide services for the UE, and the target gateway list includes a plurality of gateways capable of providing services for the UE. In this way, the first gateway device can select a suitable gateway (such as a gateway with better location, etc.) from the plurality of gateways included in the target gateway list as the target gateway according to actual needs of the target service;
  • the first gateway device determines one gateway from the plurality of gateways included in the target gateway list as the target gateway.
  • the first gateway device includes the Determining a gateway as the target gateway among the gateways includes:
  • the first gateway device determines the current gateway as The target gateway. In this way, the method of determining the current gateway as the target gateway can reduce the handover of the network, thereby reducing the processing delay for the target service.
  • the first gateway device includes the Determining a gateway as the target gateway among the gateways includes:
  • the first gateway device obtains from the target gateway list Determining, by the plurality of gateways, a gateway other than the current gateway as the target gateway; or
  • the first gateway device determines one gateway from the plurality of gateways included in the target gateway list as the Target gateway.
  • the target gateway selected by the first gateway device may be a gateway with a better location, which can reduce the processing delay of the target service.
  • the first gateway device performs a bearer processing operation to obtain the foregoing
  • the target bearer corresponding to the target service including:
  • the first gateway device When the target gateway is not the current gateway serving the UE, the first gateway device performs a bearer creation process to obtain the target bearer.
  • the first gateway device performs Carrying a processing operation to obtain a target bearer corresponding to the target service, including:
  • the first gateway device performs a bearer creation process to obtain the target bearer
  • the first gateway device performs a bearer modification process to obtain the target bearer.
  • the first gateway device performs a bearer creation process, to obtain the foregoing Target bearers, including:
  • the first gateway device performs a bearer creation process to obtain the target bearer;
  • the first gateway device performs bearer creation. Flow to obtain the target bearer;
  • the first gateway device performs a bearer creation process to obtain the target bearer.
  • the first gateway device directly performs the bearer creation process, and does not need to perform QCI information judgment, and the processing is simple, and the target bearer can be quickly obtained.
  • the first gateway device performs a bearer modification process to obtain the foregoing Target bearers, including:
  • the first gateway performs a bearer modification process to obtain the target bearer. This eliminates the need to create new bearers and saves on hosting resources.
  • the first gateway device The target bearer is anchored with the target gateway, including:
  • the information corresponding to the target bearer includes a full tunnel end point of the S1_U interface service gateway. Identifying SGW FTEID information, where the S1_U interface SGW FTEID information is used to indicate that the target gateway receives an uplink service flow that is sent by the UE and that matches the S1_U interface SGW FTEID information; or
  • the information corresponding to the target bearer includes the service flow template TFT information, where the TFT information is used to indicate that the target gateway receives a downlink service flow that needs to be sent to the UE that matches the TFT information; or
  • the information corresponding to the target bearer includes the S1-U interface evolved base station eNB FTEID information, where the S1-U interface eNB FTEID information is used to indicate that the target gateway will receive the received information according to the S1-U interface eNB FTEID information.
  • the downlink traffic sent to the UE is sent to the eNB.
  • the first gateway device determines, by the first gateway device, the target service currently performed by the user equipment UE, including:
  • the first gateway device determines the target service according to the packet feature information.
  • the first gateway device may be a gateway control plane (GW_C, Gateway Controller), and the target gateway is a gateway forwarding plane (GW_U, Gateway User) (ie, New_GW_U); or the first gateway
  • the device may also be a remote gateway (R_GW, Remote Gateway), and the target gateway may be a local gateway (L_GW, Local Gateway).
  • the first gateway device determines, by the first gateway device, the target service currently performed by the user equipment UE, including:
  • the first gateway device receives a session modification request message sent by a policy and charging rule function PCRF entity, where the session modification request message includes message feature information;
  • the first gateway device determines the target service according to the packet feature information.
  • the first gateway device may be GW_C, and the target gateway is GW_U; or the first gateway device may also be an R_GW, and the target gateway may be an L_GW.
  • the first gateway device determines, by the first gateway device, the target service currently performed by the user equipment UE, including:
  • the first gateway device receives an event reported by the second gateway device, where the event is reported by the second gateway device when it detects that the service packet received by the second gateway device meets the preset condition;
  • the first gateway device determines the target service according to the event.
  • the event reported by the second gateway device may be reported by the second gateway device, or may be reported by the second gateway device under the subscription of the first gateway device, and the first The gateway device may be GW_C and the second gateway device may be a default bearer-anchored GW_U (ie, Old_GW_U), and the target gateway is GW_U (ie, New_GW_U).
  • a second aspect of the embodiments of the present invention discloses a service flow transmission apparatus, where the apparatus includes a determination module, a bearer processing module, a binding module, an anchor module, and a transmission module, where:
  • the determining module is configured to determine a target service currently performed by the user equipment UE, where the target
  • the standard service can be a service to access a website, a call service or an instant messaging service;
  • the bearer processing module is configured to perform a bearer processing operation to obtain a target bearer corresponding to the target service, where the bearer processing operation may include a bearer creation process or a bearer modification process;
  • the binding module is configured to bind the service flow of the target service to the target bearer
  • the anchoring module is configured to anchor the target bearer to the target gateway, wherein the anchoring module anchors the target bearer and the target gateway to send the context information of the target bearer to the target gateway.
  • the transmission module is configured to complete, by using the target gateway, service flow transmission between the UE and a network corresponding to the target service.
  • the implementation method realizes flexible deployment of the service flow by binding the service flow to the target bearer obtained by performing the bearer processing operation and anchoring the target bearer and the target gateway.
  • the device further includes a selection module, where:
  • the selecting module is configured to select the target gateway for the target service according to a correspondence between the service and the gateway deployment.
  • the method of selecting the target gateway according to the corresponding relationship between the service and the gateway deployment can select different target gateways for the service flows with the same APN information, and then the service flows with the same APN information are accessed to different PDN networks, and the PDN network is implemented. Flexible deployment of business flows.
  • the selecting module includes a first determining submodule and a second determining Module, where:
  • the first determining submodule is configured to determine, according to the correspondence between the service and the gateway deployment, a target gateway list that can provide services for the UE, where the target gateway list includes multiple gateways capable of providing services for the UE .
  • a suitable gateway such as a gateway with better location
  • the second determining submodule is configured to determine, as the target gateway, one gateway from multiple gateways included in the target gateway list.
  • the second determining submodule is included in the target gateway list.
  • the specific way of determining one gateway as the target gateway among multiple gateways is:
  • the plurality of gateways included in the target gateway list include a current gateway serving the UE and the current gateway meets a service requirement of the target service, determining the current gateway as the target gateway. In this way, the method of determining the current gateway as the target gateway can reduce the handover of the network, thereby reducing the processing delay for the target service.
  • the second determining submodule is included in the target gateway list.
  • the specific way of determining one gateway as the target gateway among multiple gateways is:
  • the plurality of gateways included in the target gateway list include a current gateway serving the UE and the current gateway does not satisfy the service requirement of the target service, from among multiple gateways included in the target gateway list Determining a gateway other than the current gateway as the target gateway; or
  • the target gateway list do not include the current gateway serving the UE, determining one gateway from the plurality of gateways included in the target gateway list as the target gateway.
  • the target gateway determined by the second determining sub-module may be a gateway with better location, which can reduce the processing delay of the target service.
  • the bearer processing module performs a bearer processing operation to obtain the target.
  • the specific way of carrying the target corresponding to the service is:
  • the bearer creation process is performed to obtain the target bearer.
  • the bearer processing module performs a bearer creation process,
  • the specific way to obtain the target bearer is as follows:
  • the gateway anchored by the first bearer cannot provide a service for the target service, perform a bearer creation process to obtain the Target bearing;
  • the bearer creation process is performed to obtain the target bearer.
  • the bearer processing module can directly perform the bearer creation process, eliminating the need to judge the QCI information, and the processing is simple, and the target bearer can be quickly obtained.
  • the bearer processing module performs a bearer modification process to obtain the target.
  • the specific way of carrying is:
  • the gateway anchored by the second bearer can provide a service for the target service, perform a bearer modification process, To get the target bearer. This eliminates the need to create new bearers and saves on hosting resources.
  • the anchoring module The specific way of anchoring the target bearer and target gateway is:
  • the information corresponding to the target bearer is sent to the target gateway, and the information corresponding to the target bearer is used to complete service flow transmission between the UE and the network corresponding to the target service.
  • the information corresponding to the target bearer includes the S1_U interface service gateway full amount.
  • the tunnel endpoint identifies the SGW FTEID information, where the S1_U interface SGW FTEID information is used to indicate that the target gateway receives the uplink service flow that is sent by the UE and matches the S1_U interface SGW FTEID information; or
  • the information corresponding to the target bearer includes the service flow template TFT information, where the TFT information is used to indicate that the target gateway receives a downlink service flow that needs to be sent to the UE that matches the TFT information; or
  • the information corresponding to the target bearer includes the S1-U interface evolved base station eNB FTEID information, where the S1-U interface eNB FTEID information is used to indicate that the target gateway will receive the received information according to the S1-U interface eNB FTEID information.
  • the downlink traffic sent to the UE is sent to the eNB.
  • the determining, by the determining module, the specific manner of the target service currently performed by the user equipment UE is:
  • the determining, by the determining module, the specific manner of the target service currently performed by the user equipment UE is:
  • the determining, by the determining module, the specific manner of the target service currently performed by the user equipment UE is:
  • a third aspect of the embodiments of the present invention discloses a service flow transmission apparatus, including a processor, a memory, and a communication interface, where the memory stores a set of program codes, and the processor is used to call the office.
  • the program code stored in the memory is used to perform the following operations:
  • the gateway is anchored, wherein the target service may be a service for accessing a website, a call service, or an instant messaging service, and the bearer processing operation may include a bearer creation process or a bearer modification process, and the target bearer is anchored with the target gateway.
  • the target service may be a service for accessing a website, a call service, or an instant messaging service
  • the bearer processing operation may include a bearer creation process or a bearer modification process
  • the target bearer is anchored with the target gateway.
  • the communication interface is configured to complete, by using the target gateway, service flow transmission between the UE and a network corresponding to the target service.
  • the processor is configured to invoke program code stored in the memory, and is further configured to:
  • Selecting the target gateway for the target service according to the correspondence between the service and the gateway deployment.
  • the method of selecting the target gateway according to the corresponding relationship between the service and the gateway deployment can select different target gateways for the service flows with the same APN information, and then the service flows with the same APN information are accessed to different PDN networks, and the PDN network is implemented. Flexible deployment of business flows.
  • the processor is configured according to the corresponding relationship between the service and the gateway deployment.
  • the specific way for the target service to select the target gateway is:
  • a list of target gateways capable of serving the UE is determined according to a correspondence between the service and the gateway deployment, the target gateway list including a plurality of gateways capable of providing services for the UE.
  • the first gateway device can select a suitable gateway (such as a gateway with better location, etc.) from the plurality of gateways included in the target gateway list as the target gateway according to actual needs of the target service;
  • the processor includes multiple gateways that are included in the target gateway list.
  • the specific way to determine a gateway as the target gateway is:
  • the method of determining the current gateway as the target gateway can reduce the handover of the network, thereby reducing the processing delay for the target service.
  • the processor includes multiple gateways from the target gateway list.
  • the specific way to determine a gateway as the target gateway is:
  • the plurality of gateways included in the target gateway list include a current gateway serving the UE and the current gateway does not satisfy the service requirement of the target service, from among multiple gateways included in the target gateway list Determining a gateway other than the current gateway as the target gateway; or
  • the target gateway list do not include the current gateway serving the UE, determining one gateway from the plurality of gateways included in the target gateway list as the target gateway.
  • the target gateway determined by the processor may be a gateway with better location, which can reduce the processing delay of the target service.
  • the processor performs a bearer processing operation to obtain the target service corresponding
  • the specific way of carrying the target is:
  • the bearer creation process is performed to obtain the target bearer.
  • the processor performs bearer processing.
  • the specific manner of obtaining the target bearer corresponding to the target service is:
  • the processor performs a bearer creation process to obtain the target bearer.
  • the specific way is:
  • the bearer creation process is performed to obtain the target bearer;
  • the gateway anchored by the first bearer cannot provide a service for the target service, perform a bearer creation process to obtain the Target bearing;
  • the bearer creation process is performed to obtain the target bearer.
  • the processor directly performs the bearer creation process, and does not need to judge the QCI information. The processing is simple and the target bearer can be quickly obtained.
  • the processor performs a bearer modification process to obtain the target bearer.
  • the specific way is:
  • the gateway anchored by the second bearer can provide a service for the target service, perform a bearer modification process, To get the target bearer. This eliminates the need to create new bearers and saves on hosting resources.
  • the specific way of anchoring the target bearer and target gateway is:
  • the information corresponding to the target bearer includes the S1_U interface service gateway
  • the tunnel endpoint identifies the SGW FTEID information, where the S1_U interface SGW FTEID information is used to indicate that the target gateway receives the uplink service flow that is sent by the UE and matches the S1_U interface SGW FTEID information; or
  • the information corresponding to the target bearer includes service flow template TFT information, and the TFT information is used to indicate that the target gateway receives a downlink service flow that needs to be sent to the UE that matches the TFT information. or
  • the information corresponding to the target bearer includes the S1-U interface evolved base station eNB FTEID information, where the S1-U interface eNB FTEID information is used to indicate that the target gateway will receive the received information according to the S1-U interface eNB FTEID information.
  • the downlink traffic sent to the UE is sent to the eNB.
  • the first possible implementation manner of the third aspect of the embodiment of the present invention to any one of the possible implementation manners of the tenth possible implementation manner of the third aspect of the embodiment of the present invention, in an eleventh possible implementation manner of the third aspect of the embodiment, is:
  • the first possible implementation manner of the third aspect of the embodiment of the present invention to any one of the possible implementation manners of the tenth possible implementation manner of the third aspect of the embodiment of the present invention, in a twelfth possible implementation manner of the third aspect of the embodiment, is:
  • the first possible implementation manner of the third aspect of the embodiment of the present invention to any one of the possible implementation manners of the tenth possible implementation manner of the third aspect of the embodiment of the present invention, in a thirteenth possible implementation manner of the third aspect of the embodiment, is:
  • the first gateway device determines the target service currently performed by the UE, and performs a bearer processing operation, to obtain a target bearer corresponding to the target service, and binds the service flow of the target service to the target bearer, where The gateway device anchors the target bearer with the target gateway, and completes service flow transmission between the UE and the network corresponding to the target service by using the target gateway.
  • the service flow can be bound to a new bearer and the new bearer can be anchored to a suitable gateway, so that different bearers of the same PDN connection can be anchored to different gateways, thereby realizing flexible deployment of service flows. Improve the flexibility of business flow deployment.
  • FIG. 1 is a schematic diagram of a network architecture of an EPS disclosed in the prior art
  • FIG. 2 is a schematic diagram of network deployment of an EPS disclosed in the prior art
  • FIG. 3 is a schematic flowchart of a method for transmitting a service flow according to an embodiment of the present invention
  • FIG. 4 is a schematic flowchart of another method for transmitting a service flow according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of still another method for transmitting a service flow according to an embodiment of the present invention.
  • FIG. 6 is a schematic flowchart of still another method for transmitting a service flow according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of an effect disclosed by an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a service flow transmission apparatus according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of another service flow transmission apparatus according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of still another service flow transmission apparatus according to an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of still another service flow transmission apparatus according to an embodiment of the present invention.
  • the embodiment of the invention discloses a method and a device for transmitting a service flow, which can improve the flexibility of service flow deployment by anchoring different bearers connected to the same PDN to different gateways. The details are described below separately.
  • FIG. 3 is a schematic flowchart of a method for transmitting a service flow according to an embodiment of the present invention.
  • the method shown in FIG. 3 can be applied to the EPS network architecture shown in FIG. 1.
  • the method may include the following steps:
  • the first gateway device determines a target service currently performed by the UE.
  • the first gateway device performs a bearer processing operation to obtain a target bearer corresponding to the target service.
  • the first gateway device obtains different bearers for different services, and different bearers are used to anchor different gateways.
  • the first gateway device binds the service flow of the target service to the target bearer.
  • the first gateway device anchors the target bearer and the target gateway, and completes service flow transmission between the UE and the network corresponding to the target service by using the target gateway.
  • the embodiment of the present invention can bind the service flow to a bearer obtained after performing the bearer operation and anchor the bearer to a suitable gateway (ie, the target gateway), thereby implementing flexible deployment of the service flow and improving the service flow deployment. flexibility.
  • the method for transmitting the service flow may further include the following steps:
  • the first gateway device selects the target gateway for the target service according to the corresponding relationship between the service and the gateway deployment.
  • the optional embodiment can select a target gateway according to the corresponding relationship between the service and the gateway deployment, and can select different target gateways for the service flow with the same APN information, so that the service flow with the same APN information can access different PDN networks.
  • the flexible deployment of service flows in the PDN network is realized.
  • the first gateway device may select the target gateway according to the corresponding relationship between the service and the gateway deployment, and may occur after step S301 and before step S302.
  • the target service performs a bearer creation process or a bearer modification process to obtain a target bearer corresponding to the target service.
  • the first gateway device may select the target gateway according to the corresponding relationship between the service and the gateway deployment, or may occur after step S302 and before step S303.
  • the embodiment of the present invention is not limited.
  • the first gateway device performs the bearer processing operation to perform the bearer creation process to obtain the target bearer corresponding to the target service. And determining, by the first gateway device, the target bearer and the destination corresponding to the target service. After the target gateway, the target bearer and the target gateway are anchored, that is, the first gateway device anchors the target bearer to the target gateway.
  • the selecting, by the first gateway device, the target gateway for the target service according to the corresponding relationship between the service and the gateway deployment may include:
  • the first gateway device Determining, by the first gateway device, a list of target gateways capable of serving the UE according to the correspondence between the service and the gateway deployment, where the target gateway list includes multiple (ie, at least one) gateway capable of providing services for the UE;
  • the first gateway device determines one gateway from the plurality of gateways included in the determined target gateway list as the target gateway selected by the first gateway device for the target service.
  • the first gateway device determines, according to the determined plurality of gateways included in the target gateway list, a specific manner of the gateway as the target gateway selected by the first gateway device for the target service. Can be:
  • the first gateway device determines the current gateway as the first gateway device as the target service.
  • the selected target gateway such that the current gateway is determined as the target gateway, can reduce the handover of the network, thereby reducing the processing delay for the target service.
  • the specific manner in which the first gateway device determines one gateway from the plurality of gateways included in the determined target gateway list as the target gateway selected by the first gateway device for the target service is further Can be:
  • the first gateway device determines, according to the multiple gateways included in the target gateway list. a gateway other than the current gateway as a target gateway selected by the first gateway device for the target service; or
  • the first gateway device determines one gateway from the plurality of gateways included in the target gateway list as the first gateway device as the target service. The selected target gateway.
  • the target gateway selected by the first gateway device for the target service may be a gateway with a better location, so that the processing delay of the target service may be reduced.
  • the method further includes: performing, by the first gateway device, the bearer processing operation, to obtain the target bearer corresponding to the target service, where the target bearer may include:
  • the first gateway device When the target gateway is not the current gateway serving the UE, the first gateway device performs a bearer creation process to obtain the target bearer.
  • the anchoring the target bearer to the target gateway by the first gateway device may include:
  • the first gateway device sends the information corresponding to the target bearer to the target gateway to anchor the target bearer to the target gateway, where the information corresponding to the target bearer is used to complete the network between the UE and the target service.
  • Business flow transmission
  • the information corresponding to the target bearer may include information of a S1_U interface service gateway full MPLS tunnel identifier (SGW FTEID), where the S1_U interface SGW FTEID information is used to indicate that the target gateway receives the UE.
  • SGW FTEID S1_U interface service gateway full MPLS tunnel identifier
  • the information corresponding to the target bearer also includes the traffic flow template (TFT) information, where the TFT information is used to indicate that the target gateway receives the The downlink information service that is matched by the TFT information and needs to be sent to the UE; or the information corresponding to the target bearer may also include the S1-U interface eNB FTEID information, where the S1-U interface eNB FTEID information is used to indicate that the target gateway is configured according to the The S1-U interface eNB FTEID information sends the received downlink service flow that needs to be sent to the UE to the eNB.
  • TFT traffic flow template
  • the first gateway device performing the bearer processing operation to obtain the target bearer corresponding to the target service may include:
  • the first gateway device performs a bearer creation process to obtain the foregoing target bearer
  • the first gateway device performs a bearer modification process to obtain the target bearer.
  • the first gateway device performs the bearer creation process, and the target bearer corresponding to the target service may include:
  • the first gateway device performs a bearer creation process to obtain the target bearer.
  • QCI QoS Class Identifier
  • the QCI information of the target service is consistent with the QCI information of the first bearer of the UE, and the first The bearer anchored by the bearer cannot provide the service for the target service, and the first gateway device performs the bearer creation process to obtain the target bearer, where the first bearer is one of all the bearers of the UE;
  • the first gateway device when the network where the target service is located is an independent network (that is, the network where the target service is located is isolated from the network where other services are located), for example, when the network where the target service is located is a virtual private network (VPN) (Virtual Private Network), the first gateway device performs the bearer creation process to obtain the target bearer, that is, when the network where the target service is located is an independent network, the first gateway device directly performs the bearer creation process, and does not need to perform QCI information again. Judging, the processing is simple, and the target bearer can be obtained quickly.
  • VPN Virtual Private Network
  • the first gateway device performs the bearer modification process, so that the target bearer corresponding to the target service may include:
  • the first gateway device performs a bearer modification process to obtain the target bearer. This eliminates the need to create new bearers and saves on hosting resources.
  • the determining, by the first gateway device, the target service currently performed by the UE may include:
  • the first gateway device receives the service request message sent by the UE, where the service request message may include packet feature information, such as a traffic flow template (TFT), packet filtering information, or 5-tuple information.
  • packet feature information such as a traffic flow template (TFT), packet filtering information, or 5-tuple information.
  • the first gateway device determines, according to the packet feature information in the service request message, the target service currently performed by the UE.
  • the first gateway device may be a gateway control plane (GW_C, Gateway Controller), and the target gateway in step S304 is a gateway forwarding plane (GW_U, Gateway User) (ie, New_GW_U), that is,
  • GW_U gateway forwarding plane
  • GW_U Gateway User
  • New_GW_U gateway forwarding plane
  • the application architecture of the optional embodiment is an application architecture of “GW_C+GW_U”; or the first gateway device may also be a remote gateway (R_GW, Remote Gateway), and the target gateway in step S304 may be a local gateway (L_GW).
  • L_GW Local Gateway
  • the application architecture of the optional embodiment is an application architecture of “R_GW+L_GW”.
  • the first gateway device determines that the target service currently performed by the UE is also Can include:
  • the first gateway device receives the session modification request message sent by the entity of the Policy and Charging Rules Function (PCRF), where the session modification request message may include packet feature information, such as TFT information and packet filtering information. Or 5-tuple information, etc.;
  • PCRF Policy and Charging Rules Function
  • the first gateway device determines, according to the packet feature information in the session modification request message, the target service currently performed by the UE.
  • the first gateway device may be the gateway control plane GW_C, and the target gateway in step S304 is GW_U (ie, New_GW_U), that is, the application architecture of the optional embodiment is “GW_C+”.
  • the application architecture of the GW_U"; or the first gateway device may also be the remote gateway R_GW, and the target gateway in the step S304 may be the local gateway L_GW, that is, the application architecture of the optional embodiment is "R_GW+L_GW" Architecture.
  • the determining, by the first gateway device, the target service currently performed by the UE may also include:
  • the first gateway device receives the event reported by the second gateway device, where the event is reported to the first gateway device by the second gateway device when it detects that the service packet received by the second gateway device meets the preset condition;
  • the first gateway device determines, according to the event reported by the second gateway device, the target service currently performed by the UE.
  • the event reported by the second gateway device may be actively reported by the second gateway device, that is, after the second gateway device receives the service packet sent by the UE, the second gateway device actively performs the second gateway device.
  • the second gateway device actively reports the event, and the first gateway device determines the target service currently performed by the UE according to the event.
  • the service message sent by the UE received by the second gateway device is a Domain Name System (DNS) message containing the destination information (such as the target domain name to be accessed by the UE) to be accessed by the UE.
  • DNS Domain Name System
  • the event reported by the second gateway device may be passively reported by the second gateway device, that is, the first gateway device subscribes to the second gateway device in advance to trigger the second gateway setting.
  • the service packet After receiving the service packet sent by the UE, the service packet is identified, and the event is reported to the first gateway device when the service packet meets the event requirement, where the subscribed event may be L3/L4 information based on the service packet.
  • the L7 layer protocol information or the L7 layer content information and the like are not limited in the embodiment of the present invention.
  • the first gateway device may be GW_C and the second gateway device may be the default bearer-anchored GW_U (ie, Old_GW_U), and the target gateway in step 304 is GW_U (ie, New_GW_U). That is, the application architecture of the optional embodiment is an application architecture of “GW_C+Old_GW_U+New_GW_U”.
  • the target gateway should be as close as possible to the service server, that is, the gateway with the better service path can be regarded as a suitable target gateway.
  • FIG. 4 is a schematic flowchart diagram of another method for transmitting a service flow according to an embodiment of the present invention.
  • 4 is a schematic flowchart of a method for transmitting a service flow when the first gateway device determines a target service currently performed by the UE according to the packet feature information in the service request message sent by the UE, and the first gateway device is GW_C, where The UE performs uplink and downlink service flow transmission by the eNB and the current GW_U (ie, Old_GW_U).
  • the method for transmitting the service flow may include the following steps:
  • the UE sends a resource request message to the MME.
  • the resource request message carries the packet feature information, such as the TFT information, the packet filtering information, or the 5-tuple information of the packet.
  • the resource request message may also carry the service quality corresponding to the packet.
  • the QoS (Quality of Service) information such as the QCI information and/or the required Guaranteed Bit Rate (GBR) information, is not limited in the embodiment of the present invention.
  • the MME sends a bearer resource command (BRC, Bearer Resource Command) message to the GW_C.
  • BRC Bearer Resource Command
  • the BRC message carries the resource request message.
  • the GW_C receives the foregoing BRC message, and selects a target GW_U for the target service currently performed by the UE.
  • the target GW_U selected by the GW_C for the target service currently performed by the UE is the GW_U that is as close as possible to the service server and the service path is optimized, and the GW_C is the target GW_U selected by the target service currently performed by the UE. Identifying the current execution of the UE after the above BRC message The target service, and according to the correspondence between the service and the gateway deployment, select an appropriate target GW_U for the target service currently executed by the UE. Among them, a more specific implementation is:
  • the GW_C After receiving the foregoing BRC message, the GW_C identifies the target service currently performed by the UE according to the message feature information in the resource request message included in the foregoing BRC message, and identifies, according to the destination address information, that the UE currently needs to access a specific website;
  • the service rule is matched and the service policy is confirmed.
  • the service policy is used to provide the basis for selecting the target GW_U. For example, the gateway close to the service server is selected as much as possible, that is, the local service is required to be enabled or the local grooming is enabled. (LBO, Local Breakout) feature;
  • the GW_C confirms the GW_U list that can serve the target service according to the correspondence between the service and the gateway deployment, and selects the GW_U with the better location as the target GW_U from the multiple GW_Us included in the GW_U list, where the GW_U list may include multiple
  • the GW_U that provides the service for the foregoing target service, and the corresponding relationship between the service and the gateway deployment may be statically configured, or may be sent to the GW_C by the OM (Operation Management) system, which is not limited in the embodiment of the present invention.
  • the GW_C may directly confirm the GW_U list that can serve the target service according to the correspondence between the service and the gateway deployment, and select one of the multiple GW_Us included in the GW_U list.
  • GW_U (such as GW_U with better location) is used as the target GW_U. It is not necessary to perform the above-mentioned service rule matching to confirm the operation of the service policy. That is, GW_C adopts the “correspondence between service and gateway deployment to confirm that the above target can be served for all services.
  • a GW_U list of services and a processing policy of selecting a GW_U with a better location as the target GW_U from among a plurality of GW_Us included in the GW_U list, wherein the correspondence between the service and the gateway deployment is supported by the gateway device in a specific location Description of the service, for example, the gateway A in the location a supports the services 1, 2, 3, and the gateway B in the location b supports the services 4, 5, 6, etc., and the corresponding relationship can be configured locally in the GW_C, or can be placed In other places (for example, DNS service network) for GW_C query.
  • the GW_C determines the current GW_U as the target GW_U selected by the target service;
  • the above GW_U list contains services for the UE.
  • the GW_C determines, from all GW_Us included in the GW_U list, a GW_U (such as a better-position GW_U, etc.) other than the current GW_U as GW_C.
  • the target service selection target GW_U when the GW_U list does not include the current GW_U serving the UE, the GW_C determines one GW_U (such as a better-position GW_U, etc.) from all the GW_Us included in the GW_U list as the GW_C.
  • the target service selects the target GW_U.
  • the GW_C after the GW_C selects the target GW_U for the target service, the GW_C performs a bearer processing operation to obtain a target bearer corresponding to the target service, where different bearers are used to anchor different gateways and the target service corresponds to The target carries the target GW_U for anchoring to the target service selection.
  • the GW_C When the GW_U list includes the current GW_U serving the UE and the current GW_U meets the service requirement of the target service, the GW_C performs a corresponding bearer processing operation according to the target GW_U, and the target bearer corresponding to the target service may include :
  • the GW_C performs a bearer creation process to obtain the target bearer.
  • the GW_C performs a bearer creation process to obtain the target bearer
  • the GW_C performs a bearer modification procedure to obtain the target bearer.
  • the GW_C When the network where the target service is located is an independent network, the GW_C performs a bearer creation process to obtain the target bearer.
  • the GW_C is based on the target GW_U.
  • Performing corresponding bearer processing operations may include:
  • GW_C performs the bearer creation process and obtains the above target bearer.
  • the GW_C performs the bearer modification process as the prior art, and is not specifically described in the embodiment of the present invention; the GW_C execution bearer creation process may be as described in steps S404-S409, namely:
  • the GW_C sends a bearer creation request to the MME.
  • the bearer creation request may carry the Full Qualified Tunnel Endpoint Identifier (F-TEID) of the S1_U interface of the target GW_U.
  • F-TEID Full Qualified Tunnel Endpoint Identifier
  • the MME sends a notification message to the eNB to notify the eNB to establish an evolved radio access bearer (E-RAB, Envolved-Radio Access Bearer).
  • E-RAB evolved radio access bearer
  • the notification message carries the F-TEID of the S1_U interface of the target GW_U.
  • the MME sends, to the UE, a Non-Access Stratum (NAS) message for informing the UE to create a bearer.
  • NAS Non-Access Stratum
  • the NAS message may include a bearer ID of the bearer that the UE needs to create, corresponding TFT information, QoS information, and the like.
  • the eNB establishes a bearer with the target GW-U according to the F-TEID in the foregoing notification message, and sends a first bearer creation response to the MME.
  • the first bearer creation response is used to indicate that the bearer between the eNB and the target GW_U is established.
  • the UE establishes a bearer with the eNB according to the foregoing NAS message, and sends a second bearer creation response to the MME.
  • the second bearer creation response is used to indicate that the bearer setup between the UE and the eNB is completed.
  • the MME sends a third bearer creation response to the GW_C according to the first bearer creation response and the second bearer creation response.
  • the third bearer creation response is used to indicate that the new bearer has been created, and the QoS information provided by the newly created bearer satisfies the QoS information requested by the UE.
  • GW_C sends information corresponding to the target bearer to the target GW_U.
  • the GW_C sends the information corresponding to the target bearer to the target gateway, so that the target bearer is anchored with the target gateway, where the information corresponding to the target bearer is used to complete the UE corresponding to the target service. Traffic between networks.
  • the information corresponding to the target bearer may include a full tunnel endpoint of the S1_U interface service gateway.
  • the information of the SGW (the GW) is used to indicate that the target gateway receives the uplink service flow that is sent by the UE and matches the SGW FTEID information of the S1_U interface; or
  • the information corresponding to the target bearer also includes the traffic flow template (TFT) information, where the TFT information is used to indicate that the target gateway receives the downlink service flow that matches the TFT information and needs to be sent to the UE; or the foregoing target
  • the bearer corresponding information may also include an S1-U interface eNB FTEID information, where the S1-U interface eNB FTEID information is used to indicate that the target gateway sends the received downlink service flow that needs to be sent to the UE according to the S1-U interface eNB FTEID information. Send to the eNB.
  • the UE performs the transmission of the service flow of the target service between the eNB and the target GW_U.
  • the process of the uplink transmission of the service flow of the target service is: the UE matches the newly created bearer according to the TFT information in the NAS message, and sends an uplink service packet to the network side by using the newly created bearer;
  • the uplink service packet is matched with the context of the E-RAB, and the uplink service packet is sent to the target GW_U based on the F-TEID information of the S1_U interface (that is, the GW_C is the GW_U selected by the target service), and the target GW_U is sent by the eNB.
  • the uplink service packet of the target service the uplink service packet is sent to the network corresponding to the target service, that is, the GW_C completes the service flow transmission between the UE and the target service through the target GW_U.
  • the service flow currently performed by the UE can be bound to the bearer obtained by the bearer processing operation and the bearer is anchored to a GW_U selected according to the corresponding relationship between the service and the gateway deployment, and the GW_U is not selected according to the APN information. That is, different GW_Us can be selected for the service flows with the same APN information, and the service flows with the same APN information can be accessed to different PDN networks, thereby realizing flexible deployment of service flows in the PDN network.
  • FIG. 5 is a schematic flowchart of still another method for transmitting a service flow according to an embodiment of the present invention.
  • 5 is a schematic flowchart of a method for transmitting a service flow when the first gateway device determines a target service currently performed by the UE according to the packet feature information in the session modification request message sent by the PCRF, and the first gateway device is GW_C.
  • the UE performs uplink and downlink service flow transmission by the eNB and the current GW_U (ie, Old_GW_U).
  • the method for transmitting the service flow may include the following steps. Step:
  • the PCRF entity sends a session modification request message to the GW_C.
  • the session modification request message carries the packet feature information, such as the TFT information, the packet filtering information, or the 5-tuple information of the packet.
  • the resource request message may further carry the QoS information corresponding to the packet.
  • the QCI information and/or the required guaranteed bit rate (GBR) information, etc. are not limited in the embodiment of the present invention.
  • the GW_C receives the session modification request message, and selects a target GW_U for the target service currently performed by the UE.
  • the target GW_U selected by the GW_C for the target service currently performed by the UE is the GW_U that is as close as possible to the service server and the service path is optimized, and the GW_C is the target GW_U selected by the target service currently performed by the UE.
  • the target service currently performed by the UE is identified, and the appropriate target GW_U is selected for the target service currently performed by the UE according to the corresponding relationship between the service and the gateway deployment.
  • a more specific implementation is:
  • the GW_C After receiving the session modification request message, the GW_C identifies the target service currently performed by the UE according to the message feature information included in the session modification request message, and identifies that the UE currently needs to access a specific website according to the destination address information;
  • the service rule is matched and the service policy is confirmed.
  • the service policy is used to provide the basis for selecting the target GW_U. For example, the gateway close to the service server is selected, that is, the local service is required to be enabled or localized. LBO (Local Breakout) characteristics;
  • the GW_C confirms the GW_U list that can serve the target service according to the correspondence between the service and the gateway deployment, and selects the GW_U with the better location as the target GW_U from the multiple GW_Us included in the GW_U list, where the GW_U list may include multiple
  • the GW_U that provides the service for the foregoing target service, and the corresponding relationship between the service and the gateway deployment may be statically configured, or may be sent to the GW_C by the OM system, which is not limited in the embodiment of the present invention.
  • the GW_C may directly confirm the GW_U list that can serve the target service according to the correspondence between the service and the gateway deployment, and select one of the multiple GW_Us included in the GW_U list.
  • GW_U (such as GW_U with better location) is used as the target GW_U. It is not necessary to perform the above-mentioned business rule matching to confirm the operation of the business policy.
  • GW_C adopts a "GW_U list that can serve the above-mentioned target service according to the correspondence between the service and the gateway, and selects a GW_U with a better location as the target GW_U from among the multiple GW_Us included in the GW_U list" for all services.
  • the correspondence between the service and the gateway deployment is a description of the services supported by the gateway device in a specific location, for example, the gateway A in the location a supports the services 1, 2, and 3, and the gateway B in the location b supports the service 4. , 5, 6, and so on, and this correspondence can be configured locally in GW_C, or can be placed elsewhere (for example, DNS service network) for GW_C to query.
  • the GW_C determines the current GW_U as the target GW_U selected by the target service;
  • the GW_C determines, from all GW_Us included in the GW_U list, a GW_U other than the current GW_U (if the location is compared) GW_U, etc.
  • the GW_C is the target service selection target GW_U; when the GW_U list does not include the current GW_U serving the UE, the GW_C determines one GW_U from all the GW_Us included in the GW_U list (if the location is superior) GW_U, etc.) as GW_C selects the target GW_U for the above-mentioned target service.
  • the GW_C after the GW_C selects the target GW_U for the target service, the GW_C performs a bearer processing operation to obtain a target bearer corresponding to the target service, where different bearers are used to anchor different gateways and the target service corresponds to The target carries the target GW_U for anchoring to the target service selection.
  • the GW_C When the GW_U list includes the current GW_U serving the UE and the current GW_U meets the service requirement of the target service, the GW_C performs a corresponding bearer processing operation according to the target GW_U, and the target bearer corresponding to the target service may include :
  • the GW_C performs a bearer creation process to obtain the target bearer.
  • the GW_C performs a bearer creation process to obtain the target bearer.
  • the GW_C performs a bearer modification procedure to obtain the target bearer.
  • the GW_C is based on the target GW_U.
  • Performing corresponding bearer processing operations may include:
  • GW_C performs the bearer creation process and obtains the above target bearer.
  • the GW_C performs the bearer modification process as the prior art, and is not specifically described in the embodiment of the present invention; the GW_C execution bearer creation process may be as described in steps S503-S508, namely:
  • the GW_C sends a bearer creation request to the MME.
  • the bearer creation request may carry the Full Qualified Tunnel Endpoint Identifier (F-TEID) of the S1_U interface of the target GW_U.
  • F-TEID Full Qualified Tunnel Endpoint Identifier
  • the MME sends a notification message to the eNB to notify the eNB to establish an evolved radio access bearer E-RAB.
  • the notification message carries the F-TEID of the S1_U interface of the target GW_U.
  • the MME sends a non-access stratum NAS message for informing the UE to create a bearer to the UE.
  • the NAS message may include a bearer ID of the bearer that the UE needs to create, corresponding TFT information, QoS information, and the like.
  • the eNB establishes a bearer with the target GW-U according to the F-TEID in the foregoing notification message, and sends a first bearer creation response to the MME.
  • the first bearer creation response is used to indicate that the bearer between the eNB and the target GW_U is established.
  • the UE establishes a bearer with the eNB according to the foregoing NAS message, and sends a second bearer creation response to the MME.
  • the second bearer creation response is used to indicate that the bearer setup between the UE and the eNB is completed.
  • the MME sends a third bearer creation response to the GW_C according to the first bearer creation response and the second bearer creation response.
  • the third bearer creation response is used to indicate that the new bearer has been created, and the QoS information provided by the newly created bearer satisfies the QoS information requested by the UE.
  • GW_C sends information corresponding to the target bearer to the target GW_U.
  • the GW_C sends the information corresponding to the target bearer to the target gateway, so that the target bearer is anchored with the target gateway, where the information corresponding to the target bearer is used to complete the UE corresponding to the target service. Traffic between networks.
  • the S1_U interface SGW FTEID information is used to indicate that the target gateway receives the UE, and the SGW_UI interface SGW FTEID information is used by the target gateway.
  • An uplink service flow that matches the SGW FTEID information of the S1_U interface; or the information corresponding to the target bearer also includes information of a Traffic Flow Template (TFT), where the TFT information is used to indicate that the target gateway receives the TFT information.
  • TFT Traffic Flow Template
  • the information of the downlink traffic that needs to be sent to the UE; or the information corresponding to the target bearer may also include the S1-U interface eNB FTEID information, where the S1-U interface eNB FTEID information is used to indicate that the target gateway follows the S1-
  • the U interface eNB FTEID information sends the received downlink service flow that needs to be sent to the UE to the eNB.
  • the UE performs the transmission of the service flow of the target service between the eNB and the target GW_U.
  • the process of the uplink transmission of the service flow of the target service is: the UE matches the newly created bearer according to the TFT information in the NAS message, and sends an uplink service packet to the network side by using the newly created bearer;
  • the uplink service packet is matched with the context of the E-RAB, and the uplink service packet is sent to the target GW_U based on the F-TEID information of the S1_U interface (that is, the GW_C is the GW_U selected by the target service), and the target GW_U is sent by the eNB.
  • the uplink service packet is sent to the network corresponding to the target service.
  • the service flow currently performed by the UE can be bound to the bearer obtained by the bearer processing operation and the bearer is anchored to a GW_U selected according to the corresponding relationship between the service and the gateway deployment, and the GW_U is not selected according to the APN information. That is, different GW_Us can be selected for the service flows with the same APN information, and the service flows with the same APN information can be accessed to different PDN networks, thereby realizing flexible deployment of service flows in the PDN network.
  • FIG. 6 is a schematic flowchart diagram of still another method for transmitting a service flow according to an embodiment of the present invention.
  • 6 is a schematic flowchart of a method for transmitting a service flow when a first gateway device determines a target service currently being executed by the UE according to an event reported by the current GW_U serving the UE, and the first gateway device is GW_C.
  • the method for transmitting the service flow may include the following steps:
  • GW_C subscribes to the event of the first GW_U.
  • the first GW_U is a GW_U based on the default bearer, and the GW_C subscription event to the first GW_U is used to trigger the first GW_U to identify the service packet when receiving the service packet sent by the UE.
  • the event is reported to GW_C.
  • the GW_C is based on the default bearer-anchored GW_U subscription event, and the subscribed event may be based on L3/L4 information, L7 protocol information, or L7 content information (such as a uniform resource locator URL, etc.) of the service message, the present invention.
  • the embodiment is not limited.
  • the first GW_U sends a subscription determination message to the GW_C for the subscribed event.
  • the first GW_U receives the service packet sent by the UE, and parses whether the service packet meets the requirement of the subscribed event.
  • the event may carry the packet characteristic information, such as the TFT information, the packet filtering information, or the 5-tuple information of the packet.
  • the resource request message may further carry the QoS information corresponding to the packet, such as the QCI information.
  • the embodiment of the present invention is not limited to the GBR information and the like.
  • the GW_C receives the foregoing event, and selects a target GW_U for the target service currently performed by the UE.
  • the target GW_U selected by the GW_C for the target service currently performed by the UE is the GW_U that is as close as possible to the service server and the service path is optimized, and the GW_C is the target GW_U selected by the target service currently performed by the UE.
  • the target service currently performed by the UE is identified, and the appropriate target GW_U is selected for the target service currently performed by the UE according to the corresponding relationship between the service and the gateway deployment.
  • a more specific implementation is:
  • the GW_C After receiving the foregoing event sent by the first GW_U, the GW_C identifies the target service currently performed by the UE according to the packet feature information carried by the event, for example, identifying the current needs of the UE according to the destination address information. Visit a specific website, etc.
  • the service rule is matched and the service policy is confirmed.
  • the service policy is used to provide the basis for selecting the target GW_U. For example, the gateway close to the service server is selected, that is, the local service is required to be enabled or localized. LBO (Local Breakout) characteristics;
  • the GW_C confirms the GW_U list that can serve the target service according to the correspondence between the service and the gateway deployment, and selects the GW_U with the better location as the target GW_U from the multiple GW_Us included in the GW_U list, where the GW_U list may include multiple
  • the GW_U that provides the service for the foregoing target service, and the corresponding relationship between the service and the gateway deployment may be statically configured, or may be sent to the GW_C by the OM system, which is not limited in the embodiment of the present invention.
  • the GW_C may directly confirm the GW_U list that can serve the target service according to the correspondence between the service and the gateway deployment, and select one of the multiple GW_Us included in the GW_U list.
  • GW_U (such as GW_U with better location) is used as the target GW_U. It is not necessary to perform the above-mentioned service rule matching to confirm the operation of the service policy. That is, GW_C adopts the “correspondence between service and gateway deployment to confirm that the above target can be served for all services.
  • the GW_C determines the current GW_U as the target GW_U selected for the target service;
  • the GW_C determines a GW_U other than the current GW_U from all the GW_Us included in the GW_U list (if the location is superior) GW_U, etc.) as the target GW_U for the target service;
  • the GW_C determines one GW_U from all the GW_Us included in the GW_U list (for example, the GW_U with better location) Etc.) as the target GW_U for the above target business.
  • the GW_C after the GW_C selects the target GW_U for the target service, the GW_C performs a corresponding bearer processing operation to obtain a target bearer corresponding to the target service, where different bearers are used to anchor different gateways and the foregoing target
  • the target bearer for the service is used to anchor to the target industry.
  • the target GW_U is selected.
  • the GW_C When the GW_U list includes the current GW_U serving the UE and the current GW_U meets the service requirement of the target service, the GW_C performs a corresponding bearer processing operation according to the target GW_U, and the target bearer corresponding to the target service may include :
  • the GW_C performs a bearer creation process to obtain the target bearer.
  • the GW_C performs a bearer creation process to obtain the target bearer.
  • the GW_C performs a bearer modification procedure to obtain the target bearer.
  • the GW_C is based on the target GW_U.
  • Performing corresponding bearer processing operations may include:
  • GW_C performs the bearer creation process and obtains the above target bearer.
  • the GW_C performs the bearer modification process as the prior art, and is not specifically described in the embodiment of the present invention; the GW_C execution bearer creation process may be as described in steps S606-S611, namely:
  • the GW_C sends a bearer creation request to the MME.
  • the bearer creation request may carry the full tunnel endpoint identifier F-TEID of the S1_U interface of the target GW_U.
  • the MME sends a notification message to the eNB to notify the eNB to establish an evolved radio access bearer E-RAB.
  • the notification message carries the F-TEID of the S1_U interface of the target GW_U.
  • the MME sends a non-access stratum NAS message for informing the UE to create a bearer to the UE.
  • the NAS message may include a bearer ID of the bearer that the UE needs to create, corresponding TFT information, QoS information, and the like.
  • the eNB establishes a bearer with the target GW-U according to the F-TEID in the foregoing notification message, and sends a first bearer creation response to the MME.
  • the first bearer creation response is used to indicate that the bearer between the eNB and the target GW_U is established.
  • the UE establishes a bearer with the eNB according to the foregoing NAS message, and sends a second bearer creation response to the MME.
  • the second bearer creation response is used to indicate that the bearer setup between the UE and the eNB is completed.
  • the MME sends a third bearer creation response to the GW_C according to the first bearer creation response and the second bearer creation response.
  • the third bearer creation response is used to indicate that the new bearer has been created, and the QoS information provided by the newly created bearer satisfies the QoS information requested by the UE.
  • S612 and GW_C send information corresponding to the target bearer to the target GW_U.
  • the GW_C sends the information corresponding to the target bearer to the target gateway, so that the target bearer is anchored with the target gateway, where the information corresponding to the target bearer is used to complete the UE corresponding to the target service. Traffic between networks.
  • the S1_U interface SGW FTEID information is used to indicate that the target gateway receives the UE, and the SGW_UI interface SGW FTEID information is used by the target gateway.
  • An uplink service flow that matches the SGW FTEID information of the S1_U interface; or the information corresponding to the target bearer also includes information of a Traffic Flow Template (TFT), where the TFT information is used to indicate that the target gateway receives the TFT information.
  • TFT Traffic Flow Template
  • the information of the downlink traffic that needs to be sent to the UE; or the information corresponding to the target bearer may also include the S1-U interface eNB FTEID information, where the S1-U interface eNB FTEID information is used to indicate that the target gateway follows the S1-
  • the U interface eNB FTEID information sends the received downlink service flow that needs to be sent to the UE to the eNB.
  • the UE performs the transmission of the service flow of the target service between the eNB and the target GW_U.
  • the process of the uplink transmission of the service flow of the target service is: the UE matches the newly created bearer according to the TFT information in the NAS message, and sends the industry to the network side through the newly created bearer.
  • the eNB receives the uplink service packet sent by the UE, matches the context of the E-RAB, and sends the uplink service packet to the target GW_U based on the F-TEID information of the S1_U interface (that is, the GW_C is the GW_U selected by the target service).
  • the target GW_U After receiving the uplink service packet of the target service sent by the eNB, the target GW_U sends the uplink service packet to the network corresponding to the target service.
  • the step S601 and the step S602 are optional, that is, the GW_U can directly perform the detection of the service packet, and the event is reported to the GW_C according to the preset service matching rule, and the GW_C reports the message through the GW_U.
  • the event directly senses the target service that is currently performed by the UE, and can also obtain the corresponding service rule and the QoS information through the event reported by the GW_U, which is not limited in the embodiment of the present invention.
  • the service flow currently performed by the UE can be bound to a new bearer and the bearer is anchored to a GW_U selected according to the corresponding relationship between the service and the gateway deployment, and the GW_U is not required to be selected according to the APN information, that is, The service flows with the same APN information are selected by different GW_Us, and the service flows with the same APN information are accessed to different PDN networks, thereby implementing flexible deployment of service flows in the PDN network.
  • the GW_C selects the target GW_U for the target service, and then performs the bearer processing operation to obtain the target bearer. Perform the bearer creation process or perform the bearer modification process. In an actual application, the GW_C may perform the bearer processing process by performing the corresponding bearer processing operation to obtain the target bearer, and then selecting the target GW_U for the target service.
  • the GW_C performs a bearer creation process
  • the GW_C device performs a bearer creation process
  • the GW_C performs a bearer modification process
  • the network where the target service is located is an independent network (that is, the network where the target service is located is isolated from the network where other services are located, and may also be referred to as a slicing_slice network), for example, when the target service is located.
  • the network is a VPN network (which can be regarded as a slice network)
  • GW_C performs a bearer creation process to obtain the above target bearer.
  • FIG. 7 is a schematic diagram of an effect disclosed by the embodiment of the present invention. As shown in FIG. 7 , the technical effects achieved by the foregoing method embodiments are as follows:
  • GW_C binds the service flow related to the application (APP, Application) to a specific bearer (which can be implemented by TFT) and is anchored to a specific GW_U (ie, the target GW_U mentioned in the foregoing method embodiment).
  • the link information of the user plane of GPRS Tunneling Protocol (GTP-U) is configured for the bearer on demand. Based on this, the eNB can distribute the service packets to different GW_Us.
  • An independent communication tunnel can be established between GW_U and APP to ensure isolation between applications.
  • the same IP can access different applications, and no need to configure APN information for each application.
  • FIG. 8 is a schematic structural diagram of a service flow transmission apparatus according to an embodiment of the present invention.
  • the apparatus may include a determining module 801, a bearer processing module 802, a binding module 803, an anchoring module 804, and a transmission module 805, where:
  • the determining module 801 is configured to determine a target service currently performed by the UE.
  • the bearer processing module 802 is configured to perform a bearer processing operation to obtain a target bearer corresponding to the target service.
  • the binding module 803 is configured to bind the service flow of the target service to the target bearer.
  • the anchor module 804 is configured to anchor the target bearer to the target gateway.
  • the transmission module 805 is configured to complete service flow transmission between the UE and the network corresponding to the target service by using the foregoing target gateway.
  • the embodiment of the present invention can bind the service flow to a bearer obtained after performing the bearer operation, and
  • the bearer is anchored to a suitable gateway (ie, the target gateway), which realizes flexible deployment of service flows and improves the flexibility of service flow deployment.
  • the device may further include a selection module 806.
  • the device may be as shown in FIG. 9, and FIG. 9 is disclosed in the embodiment of the present invention.
  • FIG. 9 Another schematic diagram of the structure of a transmission device for a service flow. among them:
  • the selecting module 806 is configured to select the target gateway for the target service according to the correspondence between the service and the gateway deployment.
  • the optional embodiment can select a target gateway according to the corresponding relationship between the service and the gateway deployment, and can select different target gateways for the service flow with the same APN information, so that the service flow with the same APN information can access different PDN networks.
  • the flexible deployment of service flows in the PDN network is realized.
  • the selecting the module 806 to select the target gateway for the target service according to the corresponding relationship between the service and the gateway deployment may occur after the determining module 801 determines the target service currently performed by the UE and performs a bearer processing operation on the bearer processing module 802 to obtain the foregoing target.
  • the bearer processing module 802 is specifically configured to perform the bearer creation process or the bearer modification process according to the target service; the selecting module 806 selects the target gateway for the target service according to the corresponding relationship between the service and the gateway deployment.
  • the binding processing module 802 may perform the bearer processing operation to obtain the target bearer corresponding to the target service, and before the binding module 803 binds the service flow of the target service to the target bearer, or the binding module 803 may perform the foregoing. After the service flow of the target service is bound to the target bearer and before the anchor module 804 anchors the target bearer and the target gateway, the bearer processing module 802 is specifically configured to perform the bearer creation process.
  • the specific manner of the determining module 801 determining the target service currently performed by the user equipment UE may be:
  • the target service is determined according to the message characteristic information.
  • the specific manner in which the determining module 801 determines the target service currently performed by the user equipment UE may also be:
  • the target service is determined according to the message characteristic information.
  • the specific manner of the determining module 801 determining the target service currently performed by the user equipment UE may also be:
  • the above target business is determined based on the event.
  • the selection module 806 can include a first determining submodule 8061 and a second determining submodule 8062.
  • the structure of the device can be as shown in FIG. 10, and FIG. 10 is an embodiment of the present invention.
  • the first determining sub-module 8061 is configured to determine, according to a correspondence between the service and the gateway deployment, a target gateway list that can provide services for the UE, where the target gateway list includes multiple (ie, at least one) gateways capable of serving the UE.
  • the second determining submodule 8062 is configured to determine one gateway from the plurality of gateways included in the target gateway list as the target gateway.
  • the specific manner that the second determining sub-module 8062 determines one gateway from the plurality of gateways included in the target gateway list as the target gateway may be:
  • the plurality of gateways included in the target gateway list include a current gateway serving the UE and the current gateway meets the service requirement of the target service, determining the current gateway as the target gateway, so that the current gateway is determined as the target gateway. The way to reduce network switching, thereby reducing the processing delay for the target service.
  • the specific manner that the second determining sub-module 8062 determines one gateway from the plurality of gateways included in the target gateway list as the target gateway may also be:
  • the plurality of gateways included in the target gateway list include a current gateway serving the UE and the current gateway does not meet the service requirement of the target service, determining, by the plurality of gateways included in the target gateway list, the current gateway a gateway outside as the above target gateway; or
  • the target gateway list do not include the current gateway serving the UE, determining one gateway from the plurality of gateways included in the target gateway list as the target gateway.
  • the target gateway determined by the second determining submodule 8062 for the target service may be a gateway with a better location, so that the processing delay of the target service may be reduced.
  • the specific manner of the bearer processing operation performed by the bearer processing module 802 to obtain the target bearer corresponding to the target service may be:
  • the bearer creation process is performed to obtain the target bearer.
  • the specific manner in which the bearer processing module 802 performs the bearer processing operation to obtain the target bearer corresponding to the target service may be:
  • the specific manner in which the bearer processing module 802 performs the bearer creation process to obtain the target bearer may be:
  • the bearer creation process is performed to obtain the target bearer
  • the gateway anchored by the first bearer cannot provide the service for the target service, perform a bearer creation process to obtain the target bearer;
  • the bearer creation process is performed to obtain the target bearer, that is, when the network where the target service is located is an independent network, the bearer processing module 802 can directly perform the bearer.
  • the creation process eliminates the need to judge the QCI information, and the processing is simple, and the target bearer can be quickly obtained.
  • the bearer processing module 802 performs the bearer modification process to obtain the target bearer.
  • the specific manner may be:
  • the gateway anchored by the second bearer can provide the service for the target service, perform a bearer modification process to obtain the target bearer, so that the target bearer does not need to be created.
  • the new bearer saves the bearer resources.
  • the specific manner in which the anchor module 804 anchors the target bearer to the target gateway may be:
  • the S1_U interface SGW FTEID information is used to indicate that the target gateway receives the UE, and the SGW_UI interface SGW FTEID information is used by the target gateway.
  • An uplink service flow that matches the SGW FTEID information of the S1_U interface; or the information corresponding to the target bearer also includes information of a Traffic Flow Template (TFT), where the TFT information is used to indicate that the target gateway receives the TFT information.
  • TFT Traffic Flow Template
  • the information of the downlink traffic that needs to be sent to the UE; or the information corresponding to the target bearer may also include the S1-U interface eNB FTEID information, where the S1-U interface eNB FTEID information is used to indicate that the target gateway follows the S1-
  • the U interface eNB FTEID information sends the received downlink service flow that needs to be sent to the UE to the eNB.
  • FIG. 11 is a schematic structural diagram of another apparatus for transmitting a service flow according to an embodiment of the present invention.
  • the apparatus may include: a memory 1101, a communication interface 1102, at least one processor 1103 (such as a CPU), and at least one communication bus 1104.
  • the memory 1101 may be a high-speed RAM memory or a non-volatile memory ( Non-volatile memory, such as at least one disk storage. Alternatively, the memory 1101 may be at least one storage device located away from the processor 1103. among them:
  • Communication bus 1104 is used to implement connection communication between these components.
  • a set of program codes is stored in the memory 1101, and the processor 1103 is configured to call the program code stored in the memory 1101 for performing the following operations:
  • the communication interface 1102 is configured to complete service flow transmission between the UE and the network corresponding to the target service by using the foregoing target gateway.
  • the processor 1103 is configured to call a program generation stored in the memory 1101.
  • the code can also be used to do the following:
  • the foregoing target gateway is selected according to the corresponding relationship between the service and the gateway deployment for the foregoing target service.
  • the specific manner in which the processor 1103 selects the target gateway for the target service according to the corresponding relationship between the service and the gateway deployment may be:
  • a gateway is determined from the plurality of gateways included in the target gateway list as the target gateway.
  • the specific manner in which the processor 1103 determines one gateway from the plurality of gateways included in the target gateway list as the target gateway may be:
  • the current gateway is determined as the target gateway.
  • the specific manner in which the processor 1103 determines one gateway from the plurality of gateways included in the target gateway list as the target gateway may also be:
  • the plurality of gateways included in the target gateway list include a current gateway serving the UE and the current gateway does not meet the service requirement of the target service, determining, by the plurality of gateways included in the target gateway list, the current gateway a gateway outside as the above target gateway; or
  • the target gateway list do not include the current gateway serving the UE, determining one gateway from the plurality of gateways included in the target gateway list as the target gateway.
  • the method further includes: performing the bearer processing operation to obtain the target bearer corresponding to the target service, where the specific manner may be:
  • the bearer creation process is performed to obtain the target bearer.
  • the specific manner in which the processor 1103 determines the target service currently performed by the UE may be:
  • the target service is determined according to the message characteristic information.
  • the processor 1103 determines a specific manner of the target service currently being executed by the UE. Can also be:
  • the target service is determined according to the message characteristic information.
  • the specific manner in which the processor 1103 determines the target service currently performed by the UE may also be:
  • the above target business is determined based on the event.
  • the specific manner in which the processor 1103 performs the corresponding bearer processing operation to obtain the target bearer corresponding to the target service may be:
  • the specific manner in which the processor 1103 performs the bearer creation process to obtain the foregoing target bearer may be:
  • the bearer creation process is performed to obtain the target bearer
  • the bearer creation process is performed to obtain the target bearer
  • the bearer creation process is performed to obtain the target bearer.
  • the specific manner in which the processor 1103 performs the bearer modification process to obtain the target bearer may be:
  • the gateway anchored by the second bearer can provide the service for the target service, perform a bearer modification process to obtain the target bearer.
  • the processor 1103 carries the target bearer and the target gateway anchor.
  • the specific way can be:
  • the information corresponding to the target bearer is sent to the target gateway, where the information corresponding to the target bearer is used to complete service flow transmission between the UE and the network corresponding to the target service.
  • the information corresponding to the target bearer may include information of a S1_U interface service gateway full MPLS tunnel identifier (SGW FTEID), where the S1_U interface SGW FTEID information is used to indicate that the target gateway receives the UE.
  • SGW FTEID S1_U interface service gateway full MPLS tunnel identifier
  • the information corresponding to the target bearer also includes the traffic flow template (TFT) information, where the TFT information is used to indicate that the target gateway receives the The downlink information service that is matched by the TFT information and needs to be sent to the UE; or the information corresponding to the target bearer may also include the S1-U interface eNB FTEID information, where the S1-U interface eNB FTEID information is used to indicate that the target gateway is configured according to the The S1-U interface eNB FTEID information sends the received downlink service flow that needs to be sent to the UE to the eNB.
  • TFT traffic flow template
  • the embodiment of the present invention can bind the service flow to the bearer obtained by performing the bearer processing operation, and can select a suitable gateway for the service flow according to the corresponding relationship between the service and the gateway deployment, and anchor the obtained bearer to the appropriate gateway.
  • the different bearers connected to the same PDN are anchored to different gateways, thereby implementing flexible deployment of service flows and improving flexibility of service flow deployment.
  • the modules and sub-modules in the first gateway device of the embodiment of the present invention may be combined, divided, and deleted according to actual needs.
  • modules and sub-modules in the embodiments of the present invention may be implemented by a general-purpose integrated circuit, such as a CPU (Central Processing Unit) or an ASIC (Application Specific Integrated Circuit).
  • a general-purpose integrated circuit such as a CPU (Central Processing Unit) or an ASIC (Application Specific Integrated Circuit).
  • the readable storage medium when executed, may include the flow of an embodiment of the methods as described above.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Abstract

本发明实施例公开了一种业务流的传输方法及装置，该方法包括第一网关设备确定UE当前执行的目标业务并执行承载处理操作，以得到该目标业务对应的目标承载，并将该目标业务的业务流绑定到该目标承载，第一网关设备将该目标承载与目标网关锚定，并通过该目标网关完成UE与该目标业务对应的网络之间的业务流传输。可见，本发明实施例能够将业务流绑定到一个执行承载操作后得到的承载且将该承载锚定到一个合适的网关，实现了业务流的灵活部署，提高了业务流部署的灵活性。

Description

一种业务流的传输方法及装置 技术领域
本发明实施例涉及无线通信技术领域，具体涉及一种业务流的传输方法及装置。
背景技术
为了应对无线宽带技术的挑战，保持第三代合作伙伴计划(3GPP，the 3rd Generation Partnership Project)网络的领先优势，3GPP在2004年底制定了移动通信网络的长期演进(LTE，Long Term Evolution)计划。在LTE计划的指导下定义了新的移动通信网络架构，该新的移动通信网络架构比现在的2G、3G网络更加扁平，且只保留了分组域(PS，Packet Switching Domain)，因此可以称之为演进的分组系统(EPS，Evolved Packet System)。且该EPS的网络架构可以如图1所示，图1是现有技术公开的一种EPS的网络架构示意图。在图1所示的EPS网络架构中，演进的分组核心网(EPC，Envolved Packet Core)主要包含移动管理实体(MME，Mobility Management Entity)、服务网关(S-GW，Serving Gateway)、分组数据网关(P-GW，Packet Data Network Gateway)三个逻辑功能体，其中，MME主要负责非接入层(NAS，Non-Access)信令及NAS信令加密、漫游及跟踪、分配用户临时身份标识以及安全功能等，它对应于GERAN/UTRAN网络中服务GPRS支持节点(SGSN，Serving GPRS Support Node)的控制平面部分；S-GW主要负责本地的移动性锚点、3GPP系统内部的移动性锚点以及合法监听相关信息等功能；P-GW主要负责策略执行和计费以及合法监听等相关功能。
在图1所示的EPS网络架构中，当用户设备(UE，User Equipment)接入EPC时，首先需要基于接入点名称(APN，Access Point Name)信息(缺省配置或者UE提供)为UE创建APN所指向的PDN连接(又称“会话连接”)。此外，会话连接创建过程中会为UE提供相应的IP地址，会话连接里创建的第一个承载称为缺省承载(在整个会话连接周期内保持激活状态)，之后创建的承载则是专有 承载。当UE进行业务时，具有相同UE IP地址且流向同一个PDN网络(即具有相同APN属性)的流汇聚到一个会话连接里，进一步的，具有相同服务质量(QoS，Quality of Service)属性的流又被汇聚到一个承载里。且针对图1所示的EPS网络架构的网络部署可以如图2所示，图2是现有技术公开的一种EPS的网络部署示意图。在图2所示的网络部署中，一个业务流绑定一个承载，一个承载绑定一个PDN连接，一个PDN连接锚定在一个特定网关，具有相同APN信息的业务流最终接入到同一个PDN网络，具有不同APN信息的业务流最终接入不同的PDN网络，可见，当前EPS的网络部署只能做到业务流灵活接入PDN网络，无法做到PDN网络内业务流的灵活部署。可见，当前的EPS中业务流的部署存在灵活性低的问题。
发明内容
本发明实施例公开了一种业务流的传输方法及装置，能够提高业务流部署的灵活性。
本发明实施例第一方面公开了一种业务流的传输方法，所述方法包括：
第一网关设备确定用户设备UE当前执行的目标业务，其中，该目标业务可以是访问某网站的业务、呼叫业务或即时通讯业务等；
所述第一网关设备执行承载处理操作，以得到所述目标业务对应的目标承载，并将所述目标业务的业务流绑定到所述目标承载，其中，该承载处理操作可以包括承载创建流程或承载修改流程；
所述第一网关设备将所述目标承载与目标网关锚定，并通过所述目标网关完成所述UE与所述目标业务对应的网络之间的业务流传输，其中，将该目标承载与目标网关锚定即为将目标承载的上下文信息发送至目标网关。这样通过将业务流与执行承载处理操作得到的目标承载绑定并将目标承载与目标网关锚定的方式实现了业务流的灵活部署。
在本发明实施例第一方面的第一种可能的实现方式中，所述方法还包括：
所述第一网关设备根据业务与网关部署的对应关系为所述目标业务选择所述目标网关。这样根据业务与网关部署的对应关系选择目标网关的方式能够 为具有相同APN信息的业务流选择不同的目标网关，进而使具有相同APN信息的业务流接入不同的PDN网络，实现了PDN网络内业务流的灵活部署。
结合本发明实施例第一方面的第一种可能的实现方式，在本发明实施例第一方面的第二种可能的实现方式中，所述第一网关设备根据业务与网关部署的对应关系为所述目标业务选择所述目标网关，包括：
所述第一网关设备根据业务与网关部署的对应关系确定能够为所述UE提供服务的目标网关清单，所述目标网关清单包括多个能够为所述UE提供服务的网关。这样能够使第一网关设备根据目标业务的实际需求从目标网关清单包括的多个网关中选择一个合适的网关(如位置较优的网关等)作为目标网关；
所述第一网关设备从所述目标网关清单包括的多个网关中确定一个网关作为所述目标网关。
结合本发明实施例第一方面的第二种可能的实现方式，在本发明实施例第一方面的第三种可能的实现方式中，所述第一网关设备从所述目标网关清单包括的多个网关中确定一个网关作为所述目标网关，包括：
若所述目标网关清单包括的多个网关中包含为所述UE提供服务的当前网关且所述当前网关满足所述目标业务的业务需求，则所述第一网关设备将所述当前网关确定为所述目标网关。这样将当前网关确定为目标网关的方式能够减少网络的切换，进而减少针对目标业务的处理时延。
结合本发明实施例第一方面的第二种可能的实现方式，在本发明实施例第一方面的第四种可能的实现方式中，所述第一网关设备从所述目标网关清单包括的多个网关中确定一个网关作为所述目标网关，包括：
若所述目标网关清单包括的多个网关中包含为所述UE提供服务的当前网关且所述当前网关不满足所述目标业务的业务需求，则所述第一网关设备从所述目标网关清单包括的多个网关中确定除所述当前网关之外的一个网关作为所述目标网关；或着
若所述目标网关清单包括的多个网关中不包含为所述UE提供服务的当前网关，则所述第一网关设备从所述目标网关清单中包括的多个网关中确定一个网关作为所述目标网关。
其中，第一网关设备选择的目标网关可以为位置较优的网关，这样能够减少目标业务的处理时延。
结合本发明实施例第一方面的第四种可能的实现方式，在本发明实施例第一方面的第五种可能的实现方式中，所述第一网关设备执行承载处理操作，以得到所述目标业务对应的目标承载，包括：
当所述目标网关不是为所述UE提供服务的当前网关时，所述第一网关设备执行承载创建流程，以得到所述目标承载。
结合本发明实施例第一方面或本发明实施例第一方面的第一种可能的实现方式，在本发明实施例第一方面的第六种可能的实现方式中，所述第一网关设备执行承载处理操作，以得到所述目标业务对应的目标承载，包括：
所述第一网关设备执行承载创建流程，以得到所述目标承载；或者
所述第一网关设备执行承载修改流程，以得到所述目标承载。
结合本发明实施例第一方面的第六种可能的实现方式，在本发明实施例第一方面的第七种可能的实现方式中，所述第一网关设备执行承载创建流程，以得到所述目标承载，包括：
若所述目标业务的服务质量等级标识QCI信息与所述UE的所有承载中每一个承载的QCI信息都不一致，则所述第一网关设备执行承载创建流程，以得到所述目标承载；或者
若所述目标业务的QCI信息与所述UE的第一承载的QCI信息一致且所述第一承载所锚定的网关不能为所述目标业务提供服务，则所述第一网关设备执行承载创建流程，以得到所述目标承载；或者
若所述目标业务所在的网络为一个独立网络，则第一网关设备执行承载创建流程，以得到所述目标承载。当目标业务所在的网络为独立网络时，第一网关设备直接执行承载创建流程，无需再进行QCI信息的判断，处理简单，能够快速的得到目标承载。
结合本发明实施例第一方面的第六种可能的实现方式，在本发明实施例第一方面的第八种可能的实现方式中，所述第一网关设备执行承载修改流程，以得到所述目标承载，包括：
若所述目标业务的服务质量等级标识QCI信息与所述UE的第二承载的QCI信息一致且所述第二承载所锚定的网关能够为所述目标业务提供服务，则所述第一网关设备执行承载修改流程，以得到所述目标承载。这样无需创建新的承载，节省了承载资源。
结合本发明实施例第一方面或本发明实施例第一方面的第一种可能的实现方式，在本发明实施例第一方面的第九种可能的实现方式中，所述第一网关设备将所述目标承载与目标网关锚定，包括：
所述第一网关设备将所述目标承载对应的信息发送给所述目标网关，以完成目标承载与目标网关的锚定，所述目标承载对应的信息用于完成所述UE与所述目标业务对应的网络之间的业务流传输。
结合本发明实施例第一方面的第九种可能的实现方式，在本发明实施例第一方面的第十种可能的实现方式中，所述目标承载对应的信息包括S1_U接口服务网关全量隧道端点标识SGW FTEID信息，所述S1_U接口SGW FTEID信息用于指示所述目标网关接收所述UE发送的与所述S1_U接口SGW FTEID信息相匹配的上行业务流；或者
所述目标承载对应的信息包括业务流模板TFT信息，所述TFT信息用于指示所述目标网关接收与所述TFT信息相匹配的需要发送给所述UE的下行业务流；或者
所述目标承载对应的信息包括S1-U接口演进型基站eNB FTEID信息，所述S1-U接口eNB FTEID信息用于指示所述目标网关按照所述S1-U接口eNB FTEID信息将接收到的需要发送给所述UE的下行业务流发送给eNB。
结合本发明实施例第一方面、本发明实施例第一方面的第一种可能的实现方式至本发明实施例第一方面的第十种可能的实现方式中的任意一种可能的实现方式，在本发明实施例第一方面的第十一种可能的实现方式中，所述第一网关设备确定用户设备UE当前执行的目标业务，包括：
所述第一网关设备接收所述UE发送的业务请求消息，所述业务请求消息包括报文特征信息；
所述第一网关设备根据所述报文特征信息确定所述目标业务。
其中，在该可选的实施方式中，第一网关设备可以为网关控制面(GW_C，Gateway Controller)，且上述目标网关为网关转发面(GW_U，Gateway User)(即New_GW_U)；或者第一网关设备也可以是远端网关(R_GW，Remote Gateway)，且上述目标网关可以为本地网关(L_GW，Local Gateway)。
结合本发明实施例第一方面、本发明实施例第一方面的第一种可能的实现方式至本发明实施例第一方面的第十种可能的实现方式中的任意一种可能的实现方式，在本发明实施例第一方面的第十二种可能的实现方式中，所述第一网关设备确定用户设备UE当前执行的目标业务，包括：
所述第一网关设备接收策略与计费规则功能PCRF实体发送的会话修改请求消息，所述会话修改请求消息包括报文特征信息；
所述第一网关设备根据所述报文特征信息确定所述目标业务。
其中，在该可选的实施方式中，第一网关设备可以为GW_C，且上述目标网关为GW_U；或者第一网关设备也可以是R_GW，且上述目标网关可以为L_GW。
结合本发明实施例第一方面、本发明实施例第一方面的第一种可能的实现方式至本发明实施例第一方面的第十种可能的实现方式中的任意一种可能的实现方式，在本发明实施例第一方面的第十三种可能的实现方式中，所述第一网关设备确定用户设备UE当前执行的目标业务，包括：
所述第一网关设备接收第二网关设备上报的事件，所述事件是由所述第二网关设备在检测出其接收到的业务报文满足预设条件时上报的；
所述第一网关设备根据所述事件确定所述目标业务。
其中，在该可选的实施方式中，第二网关设备上报的事件可以是由第二网关设备主动上报的，也可以是第二网关设备在第一网关设备的订阅下上报的，且第一网关设备可以为GW_C且第二网关设备可以是缺省承载锚定的GW_U(即Old_GW_U)，上述目标网关为GW_U(即New_GW_U)。
本发明实施例第二方面公开了一种业务流的传输装置，所述装置包括确定模块、承载处理模块、绑定模块、锚定模块以及传输模块，其中：
所述确定模块，用于确定用户设备UE当前执行的目标业务，其中，该目 标业务可以是访问某网站的业务、呼叫业务或即时通讯业务等；
所述承载处理模块，用于执行承载处理操作，以得到所述目标业务对应的目标承载，其中，该承载处理操作可以包括承载创建流程或承载修改流程；
所述绑定模块，用于将所述目标业务的业务流绑定到所述目标承载；
所述锚定模块，用于将所述目标承载与目标网关锚定，其中，锚定模块将目标承载与目标网关锚定即为将目标承载的上下文信息发送至目标网关。；
所述传输模块，用于通过所述目标网关完成所述UE与所述目标业务对应的网络之间的业务流传输。
该实施方式通过将业务流与执行承载处理操作得到的目标承载绑定并将目标承载与目标网关锚定的方式实现了业务流的灵活部署
在本发明实施例第二方面的第一种可能的实现方式中，所述装置还包括选择模块，其中：
所述选择模块，用于根据业务与网关部署的对应关系为所述目标业务选择所述目标网关。这样根据业务与网关部署的对应关系选择目标网关的方式能够为具有相同APN信息的业务流选择不同的目标网关，进而使具有相同APN信息的业务流接入不同的PDN网络，实现了PDN网络内业务流的灵活部署。
结合本发明实施例第二方面的第一种可能的实现方式，在本发明实施例第二方面的第二种可能的实现方式中，所述选择模块包括第一确定子模块以及第二确定子模块，其中：
所述第一确定子模块，用于根据所述业务与网关部署的对应关系确定能够为所述UE提供服务的目标网关清单，所述目标网关清单包括多个能够为所述UE提供服务的网关。这样能够根据目标业务的实际需求从目标网关清单包括的多个网关中选择一个合适的网关(如位置较优的网关等)作为目标网关；
所述第二确定子模块，用于从所述目标网关清单包括的多个网关中确定一个网关作为所述目标网关。
结合本发明实施例第二方面的第二种可能的实现方式，在本发明实施例第二方面的第三种可能的实现方式中，所述第二确定子模块从所述目标网关清单包括的多个网关中确定一个网关作为所述目标网关的具体方式为：
若所述目标网关清单包括的多个网关中包含为所述UE提供服务的当前网关且所述当前网关满足所述目标业务的业务需求，则将所述当前网关确定为所述目标网关。这样将当前网关确定为目标网关的方式能够减少网络的切换，进而减少针对目标业务的处理时延。
结合本发明实施例第二方面的第二种可能的实现方式，在本发明实施例第二方面的第四种可能的实现方式中，所述第二确定子模块从所述目标网关清单包括的多个网关中确定一个网关作为所述目标网关的具体方式为：
若所述目标网关清单包括的多个网关中包含为所述UE提供服务的当前网关且所述当前网关不满足所述目标业务的业务需求，则从所述目标网关清单包括的多个网关中确定除所述当前网关之外的一个网关作为所述目标网关；或着
若所述目标网关清单包括的多个网关中不包含为所述UE提供服务的当前网关，则从所述目标网关清单中包括的多个网关中确定一个网关作为所述目标网关。
其中，第二确定子模块确定的目标网关可以为位置较优的网关，这样能够减少目标业务的处理时延。
结合本发明实施例第二方面的第四种可能的实现方式，在本发明实施例第二方面的第五种可能的实现方式中，所述承载处理模块执行承载处理操作，以得到所述目标业务对应的目标承载的具体方式为：
当所述目标网关不是为所述UE提供服务的当前网关时，执行承载创建流程，以得到所述目标承载。
结合本发明实施例第二方面或本发明实施例第二方面的第一种可能的实现方式，在本发明实施例第二方面的第六种可能的实现方式中，其特征在于，所述承载处理模块执行承载处理操作，以得到所述目标业务对应的目标承载的具体方式为：
执行承载创建流程，以得到所述目标承载；或者
执行承载修改流程，以得到所述目标承载。
结合本发明实施例第二方面的第六种可能的实现方式，在本发明实施例第二方面的第七种可能的实现方式中，所述承载处理模块执行承载创建流程，以 得到所述目标承载的具体方式为：
若所述目标业务的服务质量等级标识QCI信息与所述UE的所有承载中每一个承载的QCI信息都不一致，则执行承载创建流程，以得到所述目标承载；或者
若所述目标业务的QCI信息与所述UE的第一承载的QCI信息一致且所述第一承载所锚定的网关不能为所述目标业务提供服务，则执行承载创建流程，以得到所述目标承载；或者
若所述目标业务所在的网络为一个独立网络，则执行承载创建流程，以得到所述目标承载。当目标业务所在的网络为独立网络时，承载处理模块可以直接执行承载创建流程，无需再进行QCI信息的判断，处理简单，能够快速的得到目标承载。
结合本发明实施例第二方面的第六种可能的实现方式，在本发明实施例第二方面的第八种可能的实现方式中，所述承载处理模块执行承载修改流程，以得到所述目标承载的具体方式为：
若所述目标业务的服务质量等级标识QCI信息与所述UE的第二承载的QCI信息一致且所述第二承载所锚定的网关能够为所述目标业务提供服务，则执行承载修改流程，以得到所述目标承载。这样无需创建新的承载，节省了承载资源。
结合本发明实施例第二方面或本发明实施例第二方面的第一种可能的实现方式，在本发明实施例第二方面的第九种可能的实现方式中，所述锚定模块将所述目标承载与目标网关锚定的具体方式为：
将所述目标承载对应的信息发送给所述目标网关，所述目标承载对应的信息用于完成所述UE与所述目标业务对应的网络之间的业务流传输。
结合本发明实施例第二方面的第九种可能的实现方式，在本发明实施例第二方面的第十种可能的实现方式中，所述所述目标承载对应的信息包括S1_U接口服务网关全量隧道端点标识SGW FTEID信息，所述S1_U接口SGW FTEID信息用于指示所述目标网关接收所述UE发送的与所述S1_U接口SGW FTEID信息相匹配的上行业务流；或者
所述目标承载对应的信息包括业务流模板TFT信息，所述TFT信息用于指示所述目标网关接收与所述TFT信息相匹配的需要发送给所述UE的下行业务流；或者
所述目标承载对应的信息包括S1-U接口演进型基站eNB FTEID信息，所述S1-U接口eNB FTEID信息用于指示所述目标网关按照所述S1-U接口eNB FTEID信息将接收到的需要发送给所述UE的下行业务流发送给eNB。
结合本发明实施例第二方面、本发明实施例第二方面的第一种可能的实现方式至本发明实施例第二方面的第十种可能的实现方式中的任意一种可能的实现方式，在本发明实施例第二方面的第十一种可能的实现方式中，所述确定模块确定用户设备UE当前执行的目标业务的具体方式为：
接收所述UE发送的业务请求消息，所述业务请求消息包括报文特征信息；
根据所述报文特征信息确定所述目标业务。
结合本发明实施例第二方面、本发明实施例第二方面的第一种可能的实现方式至本发明实施例第二方面的第十种可能的实现方式中的任意一种可能的实现方式，在本发明实施例第二方面的第十二种可能的实现方式中，所述确定模块确定用户设备UE当前执行的目标业务的具体方式为：
接收服务质量等级标识PCRF实体发送的会话修改请求消息，所述会话修改请求消息包括报文特征信息；
根据所述报文特征信息确定所述目标业务。
结合本发明实施例第二方面、本发明实施例第二方面的第一种可能的实现方式至本发明实施例第二方面的第十种可能的实现方式中的任意一种可能的实现方式，在本发明实施例第二方面的第十三种可能的实现方式中，所述确定模块确定用户设备UE当前执行的目标业务的具体方式为：
接收第二网关设备上报的事件，所述事件是由所述第二网关设备在检测出其接收到的业务报文满足预设条件时上报的；
根据所述事件确定所述目标业务。
本发明实施例第三方面公开了一种业务流的传输装置，包括处理器、存储器以及通信接口，所述存储器中存储一组程序代码，且所述处理器用于调用所 述存储器中存储的程序代码，用于执行以下操作：
确定用户设备UE当前执行的目标业务，执行承载处理操作，以得到所述目标业务对应的目标承载，将所述目标业务的业务流绑定到所述目标承载，并将所述目标承载与目标网关锚定，其中，该目标业务可以是访问某网站的业务、呼叫业务或即时通讯业务等，该承载处理操作可以包括承载创建流程或承载修改流程，且将该目标承载与目标网关锚定即为将目标承载的上下文信息发送至目标网关。这样通过将业务流与执行承载处理操作得到的目标承载绑定并将目标承载与目标网关锚定的方式实现了业务流的灵活部署；
所述通信接口，用于通过所述目标网关完成所述UE与所述目标业务对应的网络之间的业务流传输。
在本发明实施例第三方面的第一种可能的实现方式中，所述处理器用于调用所述存储器中存储的程序代码，还用于执行以下操作：
根据业务与网关部署的对应关系为所述目标业务选择所述目标网关。这样根据业务与网关部署的对应关系选择目标网关的方式能够为具有相同APN信息的业务流选择不同的目标网关，进而使具有相同APN信息的业务流接入不同的PDN网络，实现了PDN网络内业务流的灵活部署。
结合本发明实施例第三方面的第一种可能的实现方式，在本发明实施例第三方面的第二种可能的实现方式中，所述处理器根据业务与网关部署的对应关系为所述目标业务选择所述目标网关的具体方式为：
根据业务与网关部署的对应关系确定能够为所述UE提供服务的目标网关清单，所述目标网关清单包括多个能够为所述UE提供服务的网关。这样能够使第一网关设备根据目标业务的实际需求从目标网关清单包括的多个网关中选择一个合适的网关(如位置较优的网关等)作为目标网关；
从所述目标网关清单包括的多个网关中确定一个网关作为所述目标网关。
结合本发明实施例第三方面的第二种可能的实现方式，在本发明实施例第三方面的第三种可能的实现方式中，所述处理器从所述目标网关清单包括的多个网关中确定一个网关作为所述目标网关的具体方式为：
若所述目标网关清单包括的多个网关中包含为所述UE提供服务的当前网 关且所述当前网关满足所述目标业务的业务需求，则将所述当前网关确定为所述目标网关。这样将当前网关确定为目标网关的方式能够减少网络的切换，进而减少针对目标业务的处理时延。
结合本发明实施例第三方面的第二种可能的实现方式，在本发明实施例第三方面的第四种可能的实现方式中，所述处理器从所述目标网关清单包括的多个网关中确定一个网关作为所述目标网关的具体方式为：
若所述目标网关清单包括的多个网关中包含为所述UE提供服务的当前网关且所述当前网关不满足所述目标业务的业务需求，则从所述目标网关清单包括的多个网关中确定除所述当前网关之外的一个网关作为所述目标网关；或着
若所述目标网关清单包括的多个网关中不包含为所述UE提供服务的当前网关，则从所述目标网关清单中包括的多个网关中确定一个网关作为所述目标网关。
其中，处理器确定的目标网关可以为位置较优的网关，这样能够减少目标业务的处理时延。
结合本发明实施例第三方面的第四种可能的实现方式，在本发明实施例第三方面的第五可能的实现方式中，所述处理器执行承载处理操作，以得到所述目标业务对应的目标承载的具体方式为：
当所述目标网关不是为所述UE提供服务的当前网关时，执行承载创建流程，以得到所述目标承载。
结合本发明实施例第三方面或本发明实施例第三方面的第一种可能的实现方式，在本发明实施例第三方面的第六种可能的实现方式中，所述处理器执行承载处理操作，以得到所述目标业务对应的目标承载的具体方式为：
执行承载创建流程，以得到所述目标承载；或者
执行承载修改流程，以得到所述目标承载。
结合本发明实施例第三方面的第六种可能的实现方式，在本发明实施例第三方面的第七种可能的实现方式中，所述处理器执行承载创建流程，以得到所述目标承载的具体方式为：
若所述目标业务的服务质量等级标识QCI信息与所述UE的所有承载中每一 个承载的QCI信息都不一致，则执行承载创建流程，以得到所述目标承载；或者
若所述目标业务的QCI信息与所述UE的第一承载的QCI信息一致且所述第一承载所锚定的网关不能为所述目标业务提供服务，则执行承载创建流程，以得到所述目标承载；或者
若所述目标业务所在的网络为一个独立网络，则执行承载创建流程，以得到所述目标承载。当目标业务所在的网络为独立网络时，处理器直接执行承载创建流程，无需再进行QCI信息的判断，处理简单，能够快速的得到目标承载。
结合本发明实施例第三方面的第六种可能的实现方式，在本发明实施例第三方面的第八种可能的实现方式中，所述处理器执行承载修改流程，以得到所述目标承载的具体方式为：
若所述目标业务的服务质量等级标识QCI信息与所述UE的第二承载的QCI信息一致且所述第二承载所锚定的网关能够为所述目标业务提供服务，则执行承载修改流程，以得到所述目标承载。这样无需创建新的承载，节省了承载资源。
结合本发明实施例第三方面或本发明实施例第三方面的第一种可能的实现方式中，在本发明实施例第三方面的第九种可能的实现方式中，所述处理器将所述目标承载与目标网关锚定的具体方式为：
将所述目标承载对应的信息发送给所述目标网关，以完成目标承载与目标网关的锚定，所述目标承载对应的信息用于完成所述UE与所述目标业务对应的网络之间的业务流传输。
结合本发明实施例第三方面的第九种可能的实现方式，在本发明实施例第三方面的第十种可能的实现方式中，所述所述目标承载对应的信息包括S1_U接口服务网关全量隧道端点标识SGW FTEID信息，所述S1_U接口SGW FTEID信息用于指示所述目标网关接收所述UE发送的与所述S1_U接口SGW FTEID信息相匹配的上行业务流；或者
所述目标承载对应的信息包括业务流模板TFT信息，所述TFT信息用于指示所述目标网关接收与所述TFT信息相匹配的需要发送给所述UE的下行业务流； 或者
所述目标承载对应的信息包括S1-U接口演进型基站eNB FTEID信息，所述S1-U接口eNB FTEID信息用于指示所述目标网关按照所述S1-U接口eNB FTEID信息将接收到的需要发送给所述UE的下行业务流发送给eNB。
结合本发明实施例第三方面、本发明实施例第三方面的第一种可能的实现方式至本发明实施例第三方面的第十种可能的实现方式中的任意一种可能的实现方式，在本发明实施例第三方面的第十一种可能的实现方式中，所述处理器确定UE当前执行的目标业务的具体方式为：
接收所述UE发送的业务请求消息，所述业务请求消息包括报文特征信息；
根据所述报文特征信息确定所述目标业务。
结合本发明实施例第三方面、本发明实施例第三方面的第一种可能的实现方式至本发明实施例第三方面的第十种可能的实现方式中的任意一种可能的实现方式，在本发明实施例第三方面的第十二种可能的实现方式中，所述处理器确定UE当前执行的目标业务的具体方式为：
接收策略与计费规则功能PCRF实体发送的会话修改请求消息，所述会话修改请求消息包括报文特征信息；
根据所述报文特征信息确定所述目标业务。
结合本发明实施例第三方面、本发明实施例第三方面的第一种可能的实现方式至本发明实施例第三方面的第十种可能的实现方式中的任意一种可能的实现方式，在本发明实施例第三方面的第十三种可能的实现方式中，所述处理器确定UE当前执行的目标业务的具体方式为：
接收第二网关设备上报的事件，所述事件是由所述第二网关设备在检测出其接收到的业务报文满足预设条件时上报的；
根据所述事件确定所述目标业务。
本发明实施例中，第一网关设备确定UE当前执行的目标业务并执行承载处理操作，以得到该目标业务对应的目标承载，并将该目标业务的业务流绑定到该目标承载，第一网关设备将该目标承载与目标网关锚定，并通过该目标网关完成UE与该目标业务对应的网络之间的业务流传输。可见，本发明实施例 能够将业务流绑定到一个新的承载且将该新的承载锚定到一个合适的网关，实现了将同一个PDN连接的不同承载锚定到不同的网关，进而实现了业务流的灵活部署，提高了业务流部署的灵活性。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是现有技术公开的一种EPS的网络架构示意图；
图2是现有技术公开的一种EPS的网络部署示意图；
图3是本发明实施例公开的一种业务流的传输方法的流程示意图；
图4是本发明实施例公开的另一种业务流的传输方法的流程示意图；
图5是本发明实施例公开的又一种业务流的传输方法的流程示意图；
图6是本发明实施例公开的又一种业务流的传输方法的流程示意图；
图7是本发明实施例公开的一种效果示意图；
图8是本发明实施例公开的一种业务流的传输装置的结构示意图；
图9是本发明实施例公开的另一种业务流的传输装置的结构示意图；
图10是本发明实施例公开的又一种业务流的传输装置的结构示意图；
图11是本发明实施例公开的又一种业务流的传输装置的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本发明实施例公开了一种业务流的传输方法及装置，能够通过将同一个PDN连接的不同承载锚定到不同的网关的方式，提高业务流部署的灵活性。以下分别进行详细说明。
请参阅图3，图3是本发明实施例公开的一种业务流的传输方法的流程示意图。其中，图3所示的方法可以应用于图1所示的EPS网络架构中。如图3所示，该方法可以包括以下步骤：
S301、第一网关设备确定UE当前执行的目标业务。
S302、第一网关设备执行承载处理操作，以得到上述目标业务对应的目标承载。
本发明实施例中，第一网关设备针对不同的业务得到不同的承载，且不同的承载用于锚定不同的网关。
S303、第一网关设备将上述目标业务的业务流绑定到上述目标承载。
S304、第一网关设备将上述目标承载与目标网关锚定，并通过该目标网关完成UE与上述目标业务对应的网络之间的业务流传输。
本发明实施例能够将业务流绑定到一个执行承载操作后得到的承载且将该承载锚定到一个合适的网关(即目标网关)，实现了业务流的灵活部署，提高了业务流部署的灵活性。
在一个可选的实施例中，该业务流的传输方法还可以包括以下步骤：
第一网关设备根据业务与网关部署的对应关系为上述目标业务选择上述目标网关。
该可选的实施例能够根据业务与网关部署的对应关系选择目标网关的方式能够为具有相同APN信息的业务流选择不同的目标网关，进而使具有相同APN信息的业务流接入不同的PDN网络，实现了PDN网络内业务流的灵活部署。
在该可选的实施例中，第一网关设备根据业务与网关部署的对应关系选择上述目标网关可以发生在步骤S301之后以及步骤S302之前，此时，第一网关设备执行承载处理操作可以为根据目标业务执行承载创建流程或承载修改流程，以得到上述目标业务对应的目标承载；第一网关设备根据业务与网关部署的对应关系选择上述目标网关也可以发生在步骤S302之后以及步骤S303之前或者发生在步骤S303之后以及步骤S304之前，本发明实施例不作限定，此时，第一网关设备执行承载处理操作可以为执行承载创建流程，以得到上述目标业务对应的目标承载。且在第一网关设备确定出上述目标业务对应的目标承载以及目 标网关后，将该目标承载以及目标网关进行锚定，即第一网关设备将该目标承载锚定到该目标网关。
作为该可选的实施例的一种可选的实施方式，第一网关设备根据业务与网关部署的对应关系为上述目标业务选择目标网关可以包括：
第一网关设备根据业务与网关部署的对应关系确定能够为UE提供服务的目标网关清单，其中，该目标网关清单包括多个(即至少一个)能够为UE提供服务的网关；
第一网关设备从确定出的目标网关清单包括的多个网关中确定一个网关作为第一网关设备为上述目标业务选择的目标网关。
在该可选的实施方式中，进一步可选的，第一网关设备从确定出的目标网关清单包括的多个网关中确定一个网关作为第一网关设备为上述目标业务选择的目标网关的具体方式可以为：
若上述目标网关清单包括的多个网关中包含为UE提供服务的当前网关且该当前网关满足上述目标业务的业务需求，则第一网关设备将该当前网关确定为第一网关设备为上述目标业务选择的目标网关，这样将当前网关确定为目标网关的方式能够减少网络的切换，进而减少针对目标业务的处理时延。
在该可选的方式中，进一步可选的，第一网关设备从确定出的目标网关清单包括的多个网关中确定一个网关作为第一网关设备为上述目标业务选择的目标网关的具体方式还可以为：
若上述目标网关清单包括的多个网关中包含为UE提供服务的当前网关且该当前网关不满足上述目标业务的业务需求，则第一网关设备从上述目标网关清单包括的多个网关中确定除该当前网关之外的一个网关作为第一网关设备为上述目标业务选择的目标网关；或着
若上述目标网关清单包括的多个网关中不包含为UE提供服务的当前网关，则第一网关设备从上述目标网关清单中包括的多个网关中确定一个网关作为第一网关设备为上述目标业务选择的目标网关。
其中，在该可选的实施例中，第一网关设备为上述目标业务选择的目标网关可以为位置较优的网关，这样可以减少目标业务的处理时延。
在该可选的方式中，又进一步可选的，第一网关设备执行承载处理操作，以得到上述目标业务对应的目标承载可以包括：
当上述目标网关不是为UE提供服务的当前网关时，第一网关设备执行承载创建流程，以得到上述目标承载。
在另一个可选的实施例中，第一网关设备将目标承载与目标网关锚定可以包括：
第一网关设备将上述目标承载对应的信息发送给上述目标网关，以将上述目标承载锚定到上述目标网关，其中，该目标承载对应的信息用于完成UE与上述目标业务对应的网络之间的业务流传输。
可选的，上述目标承载对应的信息可以包括S1_U接口服务网关全量隧道端点标识(SGW FTEID，Service Gateway Full Qualified Tunnel Endpoint Identifier)信息，其中，该S1_U接口SGW FTEID信息用于指示上述目标网关接收UE发送的与该S1_U接口SGW FTEID信息相匹配的上行业务流；或者，上述目标承载对应的信息也包括业务流模板(TFT，Traffic Flow Template)信息，该TFT信息用于指示上述目标网关接收与该TFT信息相匹配的且需要发送给UE的下行业务流；或者，上述目标承载对应的信息也可以包括S1-U接口eNB FTEID信息，该S1-U接口eNB FTEID信息用于指示上述目标网关按照该S1-U接口eNB FTEID信息将接收到的需要发送给UE的下行业务流发送给eNB。
在另一个可选的实施例中，第一网关设备执行承载处理操作，以得到上述目标业务对应的目标承载可以包括：
第一网关设备执行承载创建流程，以得到上述目标承载；或者
第一网关设备执行承载修改流程，以得到上述目标承载。
可选的，第一网关设备执行承载创建流程，以得到上述目标业务对应的目标承载可以包括：
若上述目标业务的服务质量等级标识(QCI，QoS Class Identifier)信息与UE的所有承载中每一个承载的QCI信息都不一致，则第一网关设备执行承载创建流程，以得到上述目标承载；
或者，若上述目标业务的QCI信息与UE的第一承载的QCI信息一致且该第一 承载所锚定的网关不能为上述目标业务提供服务，则第一网关设备执行承载创建流程，以得到上述目标承载，其中，第一承载为UE的所有承载中的其中一个承载；
或者，根据特定的配置，当上述目标业务所在的网络为一个独立网络(即上述目标业务所在的网络与其它业务所在的网络隔离)时，例如当上述目标业务所在的网络为虚拟专用网络(VPN，Virtual Private Network)时，第一网关设备执行承载创建流程，以得到上述目标承载，即当目标业务所在的网络为独立网络时，第一网关设备直接执行承载创建流程，无需再进行QCI信息的判断，处理简单，能够快速的得到目标承载。
可选的，第一网关设备执行承载修改流程，以得到上述目标业务对应的目标承载可以包括：
若上述目标业务的QCI信息与UE的第二承载的QCI信息一致且该第二承载所锚定的网关能够为上述目标业务提供服务，则第一网关设备执行承载修改流程，以得到上述目标承载，这样无需创建新的承载，节省了承载资源。
在一个可选的实施例中，第一网关设备确定UE当前执行的目标业务可以包括：
第一网关设备接收UE发送的业务请求消息，其中，该业务请求消息中可以包括报文特征信息，如业务流模板(TFT，Traffic Flow Template)信息、包过滤信息或5元组信息等；
第一网关设备根据业务请求消息中的报文特征信息确定UE当前执行的目标业务。
其中，在该可选的实施例中，第一网关设备可以为网关控制面(GW_C，Gateway Controller)，且步骤S304中的目标网关为网关转发面(GW_U，Gateway User)(即New_GW_U)，即该可选的实施例的应用架构为“GW_C+GW_U”的应用架构；或者第一网关设备也可以是远端网关(R_GW，Remote Gateway)，且步骤S304中的目标网关可以为本地网关(L_GW，Local Gateway)，即该可选的实施例的应用架构为“R_GW+L_GW”的应用架构。
在另一个可选的实施例中，第一网关设备确定UE当前执行的目标业务也 可以包括：
第一网关设备接收策略与计费规则功能(PCRF，Policy and Charging Rules Function)实体发送的会话修改请求消息，其中，该会话修改请求消息中可以包括报文特征信息，如TFT信息、包过滤信息或5元组信息等；
第一网关设备根据会话修改请求消息中的报文特征信息确定UE当前执行的目标业务。
其中，在该可选的实施例中，第一网关设备可以为网关控制面GW_C，且步骤S304中的目标网关为GW_U(即New_GW_U)，即该可选的实施例的应用架构为“GW_C+GW_U”的应用架构；或者第一网关设备也可以是远端网关R_GW，且步骤S304中的目标网关可以为本地网关L_GW，即该可选的实施例的应用架构为“R_GW+L_GW”的应用架构。
在又一个可选的实施例中，第一网关设备确定UE当前执行的目标业务也可以包括：
第一网关设备接收第二网关设备上报的事件，其中，该事件是由第二网关设备在检测出其接收到的业务报文满足预设条件时上报给第一网关设备的；
第一网关设备根据第二网关设备上报的事件确定UE当前执行的目标业务。
在该可选的实施例中，第二网关设备上报的事件可以是由第二网关设备主动上报的，即在第二网关设备接收到UE发送的业务报文后，由第二网关设备主动执行业务报文检测且在业务报文符合预设业务规则时，由第二网关设备主动上报事件，第一网关设备根据该事件确定UE当前执行的目标业务。举例来说，假设第二网关设备接收到的UE发送的业务报文为包含UE要访问的目的信息(如UE要访问的目标域名)的域名系统(DNS，Domain Name System)报文，由第二网关设备主动向第一网关设备上报事件，其中，该事件包括该DNS报文的报文特征信息，第一网关设备可以根据DNS报文的报文特征信息确定UE当前执行的目标业务。
在该可选的实施例中，第二网关设备上报的事件可以是由第二网关设备被动上报的，即第一网关设备提前向第二网关设备订阅事件，以触发第二网关设 备在接收到UE发送的业务报文后对业务报文进行识别并在业务报文满足事件需求时向第一网关设备上报事件，其中，订阅的事件可以是基于业务报文的L3/L4信息、L7层协议信息或者L7层内容信息等，本发明实施例不做限定。
其中，在该可选的实施例中，第一网关设备可以为GW_C且第二网关设备可以是缺省承载锚定的GW_U(即Old_GW_U)，步骤304中的目标网关为GW_U(即New_GW_U)，即该可选的实施例的应用架构为“GW_C+Old_GW_U+New_GW_U”的应用架构。
需要说明的是，在本发明实施例中，上述目标网关应尽可能靠近业务服务器，即业务路径较优的网关即可视为合适的目标网关。
请参阅图4，图4是本发明实施例公开的另一种业务流的传输方法的流程示意图。其中，图4为当第一网关设备根据UE发送的业务请求消息中的报文特征信息确定UE当前执行的目标业务时业务流的传输方法的流程示意图，且该第一网关设备为GW_C，其中，UE通过eNB与当前GW_U(即Old_GW_U)进行上下行业务流的传输。如图4所示，该业务流的传输方法可以包括以下步骤：
S401、UE向MME发送资源请求消息。
其中，该资源请求消息中携带有报文特征信息，如TFT信息、包过滤信息或者报文的5元组信息等，可选的，该资源请求消息中还可以携带有报文对应的服务质量(QoS，Quality of Service)信息，如QCI信息和/或其要求的保证比特率(GBR，Guaranteed Bit Rate)信息等，本发明实施例不做限定。
S402、MME向GW_C发送承载资源命令(BRC，Bearer Resource Command)消息。
其中，该BRC消息中携带上述资源请求消息。
S403、GW_C接收上述BRC消息，并为UE当前执行的目标业务选择目标GW_U。
本发明实施例中，GW_C为UE当前执行的目标业务选择的目标GW_U为尽量靠近业务服务器且业务路径较优化的GW_U，且GW_C为UE当前执行的目标业务选择的目标GW_U的实现方式为在接收到上述BRC消息后识别UE当前执行 的目标业务，并根据业务与网关部署的对应关系为UE当前执行的目标业务选择合适的目标GW_U。其中，更为具体的实现方式为：
GW_C在接收到上述BRC消息后，根据上述BRC消息包括的上述资源请求消息中的报文特征信息识别UE当前执行的目标业务，如根据目的地址信息识别UE当前需要访问某具体网站等；
GW_C在确定出目标业务后进行业务规则匹配，确认业务策略，其中，业务策略用于提供选择目标GW_U的依据，如尽量选择靠近业务服务器的网关，即要求使能本地业务疏导或使能本地疏导(LBO，Local Breakout)特性；
GW_C根据业务与网关部署的对应关系确认能够服务上述目标业务的GW_U清单，并从GW_U清单中包括的多个GW_U中选择位置较优的GW_U作为目标GW_U，其中，该GW_U清单可以包括多个能够为上述目标业务提供服务的GW_U，且业务与网关部署的对应关系可以是静态配置的，也可以是操作管理(OM，Operation Management)系统下发给GW_C的，本发明实施例不做限定。
需要说明的是，在识别出UE当前执行的目标业务后，GW_C可以直接根据业务与网关部署的对应关系确认能够服务上述目标业务的GW_U清单，并从GW_U清单中包括的多个GW_U中选择一个GW_U(如位置较优的GW_U等)作为目标GW_U，无需执行上述进行业务规则匹配，确认业务策略的操作，即GW_C针对所有的业务均采取“根据业务与网关部署的对应关系确认能够服务上述目标业务的GW_U清单，并从GW_U清单中包括的多个GW_U中选择位置较优的GW_U作为目标GW_U”的处理策略，其中，业务与网关部署的对应关系为对处于特定位置的网关设备所支持的业务的描述，例如，处于位置a的网关A支持业务1、2、3，处于位置b的网关B支持业务4、5、6等等，且这种对应关系可以配置在GW_C本地，也可以放置在其它地方(例如，DNS服务网)以供GW_C进行查询。
本发明实施例中，当上述GW_U清单中包含为UE提供服务的当前GW_U且该当前GW_U满足上述目标业务的业务需求时，GW_C将该当前GW_U确定为GW_C为上述目标业务选择的目标GW_U；当上述GW_U清单中包含为UE提供服 务的当前GW_U且该当前GW_U不满足上述目标业务的业务需求时，GW_C从上述GW_U清单包括的所有GW_U中确定除该当前GW_U之外的一个GW_U(如位置较优的GW_U等)作为GW_C为上述目标业务选择目标GW_U；当上述GW_U清单中不包含为UE提供服务的当前GW_U时，GW_C从上述GW_U清单中包括的所有GW_U中确定一个GW_U(如位置较优的GW_U等)作为GW_C为上述目标业务选择目标GW_U。
本发明实施例中，在GW_C为上述目标业务选择好目标GW_U之后，GW_C执行承载处理操作，得到上述目标业务对应的目标承载，其中，不同的承载用于锚定不同的网关且上述目标业务对应的目标承载用于锚定为目标业务选择的目标GW_U。
其中，当上述GW_U清单中包含为UE提供服务的当前GW_U且该当前GW_U满足上述目标业务的业务需求时，GW_C根据上述目标GW_U执行对应的承载处理操作，得到上述目标业务对应的目标承载可以包括：
当UE请求的QCI信息与上述当前GW_U的所有承载的QCI信息不一致时，GW_C执行承载创建流程，得到上述目标承载；
当UE请求的QCI信息与上述当前GW_U的所有承载中其中一个承载的QCI信息一致且该其中一个承载未与上述当前GW_U绑定时，GW_C执行承载创建流程，得到上述目标承载；或者
当UE请求的QCI信息与上述当前GW_U的所有承载中其中一个承载的QCI信息一致且该其中一个承载与上述当前GW_U绑定时，GW_C执行承载修改流程，得到上述目标承载。或者
当上述目标业务所在的网络为一个独立的网络时，GW_C执行承载创建流程，得到上述目标承载。
其中，当上述GW_U清单中包含为UE提供服务的当前GW_U且当前GW_U不满足上述目标业务的业务需求时，或者当上述GW_U清单中不包含为UE提供服务的当前GW_U时，GW_C根据上述目标GW_U执行对应的承载处理操作可以包括：
GW_C执行承载创建流程，得到上述目标承载。
其中，GW_C执行承载修改流程为现有技术，本发明实施例不再具体赘述；GW_C执行承载创建流程可以如步骤S404-S409所述，即：
S404、GW_C向MME发送承载创建请求。
其中，该承载创建请求可以携带有上述目标GW_U的S1_U接口的全量隧道端点标识(F-TEID，Full Qualified Tunnel Endpoint Identifier)。
S405、MME向eNB发送用于通知eNB建立演进的无线接入承载(E-RAB，Envolved-Radio Access Bearer)的通知消息。
其中，该通知消息中携带有上述目标GW_U的S1_U接口的F-TEID。
S406、MME向UE发送用于通知UE创建承载的非接入层(NAS，Non-Access Sratum)消息。
其中，该NAS消息可以包括UE需要创建的承载的承载ID、相应的TFT信息以及QoS信息等。
S407、eNB根据上述通知消息中的F-TEID建立与上述目标GW-U之间的承载，并向MME发送第一承载创建响应。
其中，该第一承载创建响应用于指示eNB与上述目标GW_U间的承载建立完毕。
S408、UE根据上述NAS消息建立与eNB之间的承载，并向MME发送第二承载创建响应。
其中，该第二承载创建响应用于指示UE与eNB间的承载建立完毕。
S409、MME根据上述第一承载创建响应以及上述第二承载创建响应向GW_C发送第三承载创建响应。
其中，该第三承载创建响应用于指示新的承载已创建完毕，且新创建的承载所提供的QoS信息满足UE所请求的QoS信息。
S410、GW_C将上述目标承载对应的信息发送至上述目标GW_U。
本发明实施例中，GW_C将上述目标承载对应的信息发送至上述目标网关，以将上述目标承载与上述目标网关锚定，其中，该目标承载对应的信息用于完成UE与上述目标业务对应的网络之间的业务流传输。
其中，上述目标承载对应的信息可以包括S1_U接口服务网关全量隧道端点 标识(SGW FTEID，Service Gateway Full Qualified Tunnel Endpoint Identifier)信息，其中，该S1_U接口SGW FTEID信息用于指示上述目标网关接收UE发送的与该S1_U接口SGW FTEID信息相匹配的上行业务流；或者，上述目标承载对应的信息也包括业务流模板(TFT，Traffic Flow Template)信息，该TFT信息用于指示上述目标网关接收与该TFT信息相匹配的且需要发送给UE的下行业务流；或者，上述目标承载对应的信息也可以包括S1-U接口eNB FTEID信息，该S1-U接口eNB FTEID信息用于指示上述目标网关按照该S1-U接口eNB FTEID信息将接收到的需要发送给UE的下行业务流发送给eNB。
S411、UE通过eNB与上述目标GW_U之间进行上述目标业务的业务流的传输。
其中，上述目标业务的业务流的上行传输的流程为：UE根据上述NAS消息中的TFT信息匹配到新创建的承载，通过该新创建的承载向网络侧发送上行业务报文；eNB接收UE发送的上行业务报文，匹配E-RAB的上下文并基于上述S1_U接口的F-TEID信息将上行业务报文发送给上述目标GW_U(即GW_C为上述目标业务选择的GW_U)，目标GW_U接收到eNB发送的上述目标业务的上行业务报文后将该上行业务报文发送至上述目标业务对应的网络，即GW_C通过目标GW_U完成UE与上述目标业务之间的业务流传输。
可见，通过上述操作可以将UE当前执行的业务流绑定到经过承载处理操作得到的承载且将该承载锚定到一个根据业务与网关部署的对应关系选择的GW_U，无需根据APN信息选择GW_U，即能够为具有相同APN信息的业务流选择不同的GW_U，进而使具有相同APN信息的业务流接入不同的PDN网络，实现了PDN网络内业务流的灵活部署。
请参阅图5，图5是本发明实施例公开的又一种业务流的传输方法的流程示意图。其中，图5为当第一网关设备根据PCRF发送的会话修改请求消息中的报文特征信息确定UE当前执行的目标业务时业务流的传输方法的流程示意图，且该第一网关设备为GW_C，其中，UE通过eNB与当前GW_U(即Old_GW_U)进行上下行业务流的传输。如图5所示，该业务流的传输方法可以包括以下步 骤：
S501、PCRF实体向GW_C发送会话修改请求消息。
其中，该会话修改请求消息中携带有报文特征信息，如TFT信息、包过滤信息或者报文的5元组信息等，可选的，该资源请求消息中还可以携带报文对应的QoS信息，如QCI信息和/或其要求的保证比特率(GBR，Guaranteed Bit Rate)信息等，本发明实施例不做限定。
S502、GW_C接收上述会话修改请求消息，并为UE当前执行的目标业务选择目标GW_U。
本发明实施例中，GW_C为UE当前执行的目标业务选择的目标GW_U为尽量靠近业务服务器且业务路径较优化的GW_U，且GW_C为UE当前执行的目标业务选择的目标GW_U的实现方式为在接收到上述会话修改请求消息后识别UE当前执行的目标业务，并根据业务与网关部署的对应关系为UE当前执行的目标业务选择合适的目标GW_U。其中，更为具体的实现方式为：
GW_C在接收到上述会话修改请求消息后，根据上述会话修改请求消息包括的报文特征信息识别UE当前执行的目标业务，如根据目的地址信息识别UE当前需要访问某具体网站等；
GW_C在确定出目标业务后进行业务规则匹配，确认业务策略，其中，业务策略用于提供选择目标GW_U的依据，如尽量选择靠近业务服务器的网关等，即要求使能本地业务疏导或使能本地疏导(LBO，Local Breakout)特性；
GW_C根据业务与网关部署的对应关系确认能够服务上述目标业务的GW_U清单，并从GW_U清单中包括的多个GW_U中选择位置较优的GW_U作为目标GW_U，其中，该GW_U清单可以包括多个能够为上述目标业务提供服务的GW_U，且业务与网关部署的对应关系可以是静态配置的，也可以是OM系统下发给GW_C的，本发明实施例不做限定。
需要说明的是，在识别出UE当前执行的目标业务后，GW_C可以直接根据业务与网关部署的对应关系确认能够服务上述目标业务的GW_U清单，并从GW_U清单中包括的多个GW_U中选择一个GW_U(如位置较优的GW_U等)作为目标GW_U，无需执行上述进行业务规则匹配，确认业务策略的操作，即 GW_C针对所有的业务均采取“根据业务与网关部署的对应关系确认能够服务上述目标业务的GW_U清单，并从GW_U清单中包括的多个GW_U中选择位置较优的GW_U作为目标GW_U”的处理策略，其中，业务与网关部署的对应关系为对处于特定位置的网关设备所支持的业务的描述，例如，处于位置a的网关A支持业务1、2、3，处于位置b的网关B支持业务4、5、6等等，且这种对应关系可以配置在GW_C本地，也可以放置在其它地方(例如，DNS服务网)以供GW_C进行查询。
本发明实施例中，当上述GW_U清单中包含为UE提供服务的当前GW_U且该当前GW_U满足上述目标业务的业务需求时，GW_C将该当前GW_U确定为GW_C为上述目标业务选择的目标GW_U；当上述GW_U清单中包含为UE提供服务的当前GW_U且该当前GW_U不满足上述目标业务的业务需求时，GW_C从上述GW_U清单包括的所有GW_U中确定除该当前GW_U之外的一个GW_U(如位置较优的GW_U等)作为GW_C为上述目标业务选择目标GW_U；当上述GW_U清单中不包含为UE提供服务的当前GW_U时，GW_C从上述GW_U清单中包括的所有GW_U中确定一个GW_U(如位置较优的GW_U等)作为GW_C为上述目标业务选择目标GW_U。
本发明实施例中，在GW_C为上述目标业务选择好目标GW_U之后，GW_C执行承载处理操作，得到上述目标业务对应的目标承载，其中，不同的承载用于锚定不同的网关且上述目标业务对应的目标承载用于锚定为目标业务选择的目标GW_U。
其中，当上述GW_U清单中包含为UE提供服务的当前GW_U且该当前GW_U满足上述目标业务的业务需求时，GW_C根据上述目标GW_U执行对应的承载处理操作，得到上述目标业务对应的目标承载可以包括：
当UE请求的QCI信息与上述当前GW_U的所有承载的QCI信息不一致时，GW_C执行承载创建流程，得到上述目标承载；
当UE请求的QCI信息与上述当前GW_U的所有承载中其中一个承载的QCI信息一致且该其中一个承载未与上述当前GW_U绑定时，GW_C执行承载创建流程，得到上述目标承载；
当UE请求的QCI信息与上述当前GW_U的所有承载中其中一个承载的QCI信息一致且该其中一个承载与上述当前GW_U绑定时，则GW_C执行承载修改流程，得到上述目标承载。
其中，当上述GW_U清单中包含为UE提供服务的当前GW_U且当前GW_U不满足上述目标业务的业务需求时，或者当上述GW_U清单中不包含为UE提供服务的当前GW_U时，GW_C根据上述目标GW_U执行对应的承载处理操作可以包括：
GW_C执行承载创建流程，得到上述目标承载。
其中，GW_C执行承载修改流程为现有技术，本发明实施例不再具体赘述；GW_C执行承载创建流程可以如步骤S503-S508所述，即：
S503、GW_C向MME发送承载创建请求。
其中，该承载创建请求可以携带有上述目标GW_U的S1_U接口的全量隧道端点标识(F-TEID，Full Qualified Tunnel Endpoint Identifier)。
S504、MME向eNB发送用于通知eNB建立演进的无线接入承载E-RAB的通知消息。
其中，该通知消息中携带有上述目标GW_U的S1_U接口的F-TEID。
S505、MME向UE发送用于通知UE创建承载的非接入层NAS消息。
其中，该NAS消息可以包括UE需要创建的承载的承载ID、相应的TFT信息以及QoS信息等。
S506、eNB根据上述通知消息中的F-TEID建立与上述目标GW-U之间的承载，并向MME发送第一承载创建响应。
其中，该第一承载创建响应用于指示eNB与上述目标GW_U间的承载建立完毕。
S507、UE根据上述NAS消息建立与eNB之间的承载，并向MME发送第二承载创建响应。
其中，该第二承载创建响应用于指示UE与eNB间的承载建立完毕。
S508、MME根据上述第一承载创建响应以及上述第二承载创建响应向GW_C发送第三承载创建响应。
其中，该第三承载创建响应用于指示新的承载已创建完毕，且新创建的承载所提供的QoS信息满足UE所请求的QoS信息。
S509、GW_C将上述目标承载对应的信息发送至上述目标GW_U。
本发明实施例中，GW_C将上述目标承载对应的信息发送至上述目标网关，以将上述目标承载与上述目标网关锚定，其中，该目标承载对应的信息用于完成UE与上述目标业务对应的网络之间的业务流传输。
其中，上述目标承载对应的信息可以包括S1_U接口服务网关全量隧道端点标识(SGW FTEID，Service Gateway Full Qualified Tunnel Endpoint Identifier)信息，其中，该S1_U接口SGW FTEID信息用于指示上述目标网关接收UE发送的与该S1_U接口SGW FTEID信息相匹配的上行业务流；或者，上述目标承载对应的信息也包括业务流模板(TFT，Traffic Flow Template)信息，该TFT信息用于指示上述目标网关接收与该TFT信息相匹配的且需要发送给UE的下行业务流；或者，上述目标承载对应的信息也可以包括S1-U接口eNB FTEID信息，该S1-U接口eNB FTEID信息用于指示上述目标网关按照该S1-U接口eNB FTEID信息将接收到的需要发送给UE的下行业务流发送给eNB。
S510、UE通过eNB与上述目标GW_U之间进行上述目标业务的业务流的传输。
其中，上述目标业务的业务流的上行传输的流程为：UE根据上述NAS消息中的TFT信息匹配到新创建的承载，通过该新创建的承载向网络侧发送上行业务报文；eNB接收UE发送的上行业务报文，匹配E-RAB的上下文并基于上述S1_U接口的F-TEID信息将上行业务报文发送给上述目标GW_U(即GW_C为上述目标业务选择的GW_U)，目标GW_U接收到eNB发送的上述目标业务的上行业务报文后将该上行业务报文发送至上述目标业务对应的网络。
可见，通过上述操作可以将UE当前执行的业务流绑定到经过承载处理操作得到的承载且将该承载锚定到一个根据业务与网关部署的对应关系选择的GW_U，无需根据APN信息选择GW_U，即能够为具有相同APN信息的业务流选择不同的GW_U，进而使具有相同APN信息的业务流接入不同的PDN网络，实现了PDN网络内业务流的灵活部署。
请参阅图6，图6是本发明实施例公开的又一种业务流的传输方法的流程示意图。其中，图6为当第一网关设备根据为UE提供服务的当前GW_U上报的事件确定UE当前执行的目标业务时业务流的传输方法的流程示意图，且该第一网关设备为GW_C。如图6所示，该业务流的传输方法可以包括以下步骤：
S601、GW_C向第一GW_U订阅事件。
其中，该第一GW_U是为基于缺省承载锚定的GW_U，且GW_C向第一GW_U订阅事件用于触发该第一GW_U在接收到UE发送的业务报文时对业务报文进行识别，当业务报文满足订阅的事件的要求时，向GW_C上报事件。一般来说，GW_C基于缺省承载锚定的GW_U订阅事件，且订阅的事件可以基于业务报文的L3/L4信息、L7协议信息或L7内容信息(如统一资源定位符URL等)，本发明实施例不做限定。
S602、第一GW_U向GW_C发送针对上述订阅的事件的订阅确定消息。
S603、第一GW_U接收UE发送的业务报文，并解析该业务报文是否满足订阅的事件的要求。
S604、当UE发送的业务报文满足订阅的事件的要求时，第一GW_U向GW_C上报事件。
其中，该事件可以携带有报文特征信息，如TFT信息、包过滤信息或者报文的5元组信息，可选的，该资源请求消息中还可以携带报文对应的QoS信息，如QCI信息和/或其要求的GBR信息等，本发明实施例不做限定。
S605、GW_C接收上述事件，并为UE当前执行的目标业务选择目标GW_U。
本发明实施例中，GW_C为UE当前执行的目标业务选择的目标GW_U为尽量靠近业务服务器且业务路径较优化的GW_U，且GW_C为UE当前执行的目标业务选择的目标GW_U的实现方式为在接收到上述事件后识别UE当前执行的目标业务，并根据业务与网关部署的对应关系为UE当前执行的目标业务选择合适的目标GW_U。其中，更为具体的实现方式为：
GW_C在接收到第一GW_U发送的上述事件后，根据上述事件携带的报文特征信息识别UE当前执行的目标业务，如根据目的地址信息识别UE当前需要 访问某具体网站等；
GW_C在确定出目标业务后进行业务规则匹配，确认业务策略，其中，业务策略用于提供选择目标GW_U的依据，如尽量选择靠近业务服务器的网关等，即要求使能本地业务疏导或使能本地疏导(LBO，Local Breakout)特性；
GW_C根据业务与网关部署的对应关系确认能够服务上述目标业务的GW_U清单，并从GW_U清单中包括的多个GW_U中选择位置较优的GW_U作为目标GW_U，其中，该GW_U清单可以包括多个能够为上述目标业务提供服务的GW_U，且业务与网关部署的对应关系可以是静态配置的，也可以是OM系统下发给GW_C的，本发明实施例不做限定。
需要说明的是，在识别出UE当前执行的目标业务后，GW_C可以直接根据业务与网关部署的对应关系确认能够服务上述目标业务的GW_U清单，并从GW_U清单中包括的多个GW_U中选择一个GW_U(如位置较优的GW_U等)作为目标GW_U，无需执行上述进行业务规则匹配，确认业务策略的操作，即GW_C针对所有的业务均采取“根据业务与网关部署的对应关系确认能够服务上述目标业务的GW_U清单，并从GW_U清单中包括的多个GW_U中选择位置较优的GW_U作为目标GW_U”的处理策略。
本发明实施例中，当上述GW_U清单中包含为UE提供服务的当前GW_U且该当前GW_U满足上述目标业务的业务需求时，GW_C将该当前GW_U确定为为上述目标业务选择的目标GW_U；当上述GW_U清单中包含为UE提供服务的当前GW_U且该当前GW_U不满足上述目标业务的业务需求时，GW_C从上述GW_U清单包括的所有GW_U中确定除该当前GW_U之外的一个GW_U(如位置较优的GW_U等)作为为上述目标业务选择目标GW_U；当上述GW_U清单中不包含为UE提供服务的当前GW_U时，GW_C从上述GW_U清单中包括的所有GW_U中确定一个GW_U(如位置较优的GW_U等)作为为上述目标业务选择目标GW_U。
本发明实施例中，在GW_C为上述目标业务选择好目标GW_U之后，GW_C执行对应的承载处理操作，得到上述目标业务对应的目标承载，其中，不同的承载用于锚定不同的网关且上述目标业务对应的目标承载用于锚定为目标业 务选择的目标GW_U。
其中，当上述GW_U清单中包含为UE提供服务的当前GW_U且该当前GW_U满足上述目标业务的业务需求时，GW_C根据上述目标GW_U执行对应的承载处理操作，得到上述目标业务对应的目标承载可以包括：
当UE请求的QCI信息与上述当前GW_U的所有承载的QCI信息不一致时，GW_C执行承载创建流程，得到上述目标承载；
当UE请求的QCI信息与上述当前GW_U的所有承载中其中一个承载的QCI信息一致且该其中一个承载未与上述当前GW_U绑定时，GW_C执行承载创建流程，得到上述目标承载；
当UE请求的QCI信息与上述当前GW_U的所有承载中其中一个承载的QCI信息一致且该其中一个承载与上述当前GW_U绑定时，GW_C执行承载修改流程，得到上述目标承载。
其中，当上述GW_U清单中包含为UE提供服务的当前GW_U且当前GW_U不满足上述目标业务的业务需求时，或者当上述GW_U清单中不包含为UE提供服务的当前GW_U时，GW_C根据上述目标GW_U执行对应的承载处理操作可以包括：
GW_C执行承载创建流程，得到上述目标承载。
其中，GW_C执行承载修改流程为现有技术，本发明实施例不再具体赘述；GW_C执行承载创建流程可以如步骤S606-S611所述，即：
S606、GW_C向MME发送承载创建请求。
其中，该承载创建请求可以携带有上述目标GW_U的S1_U接口的全量隧道端点标识F-TEID。
S607、MME向eNB发送用于通知eNB建立演进的无线接入承载E-RAB的通知消息。
其中，该通知消息中携带有上述目标GW_U的S1_U接口的F-TEID。
S608、MME向UE发送用于通知UE创建承载的非接入层NAS消息。
其中，该NAS消息可以包括UE需要创建的承载的承载ID、相应的TFT信息以及QoS信息等。
S609、eNB根据上述通知消息中的F-TEID建立与上述目标GW-U之间的承载，并向MME发送第一承载创建响应。
其中，该第一承载创建响应用于指示eNB与上述目标GW_U间的承载建立完毕。
S610、UE根据上述NAS消息建立与eNB之间的承载，并向MME发送第二承载创建响应。
其中，该第二承载创建响应用于指示UE与eNB间的承载建立完毕。
S611、MME根据上述第一承载创建响应以及上述第二承载创建响应向GW_C发送第三承载创建响应。
其中，该第三承载创建响应用于指示新的承载已创建完毕，且新创建的承载所提供的QoS信息满足UE所请求的QoS信息。
S612、GW_C将上述目标承载对应的信息发送至上述目标GW_U。
本发明实施例中，GW_C将上述目标承载对应的信息发送至上述目标网关，以将上述目标承载与上述目标网关锚定，其中，该目标承载对应的信息用于完成UE与上述目标业务对应的网络之间的业务流传输。
其中，上述目标承载对应的信息可以包括S1_U接口服务网关全量隧道端点标识(SGW FTEID，Service Gateway Full Qualified Tunnel Endpoint Identifier)信息，其中，该S1_U接口SGW FTEID信息用于指示上述目标网关接收UE发送的与该S1_U接口SGW FTEID信息相匹配的上行业务流；或者，上述目标承载对应的信息也包括业务流模板(TFT，Traffic Flow Template)信息，该TFT信息用于指示上述目标网关接收与该TFT信息相匹配的且需要发送给UE的下行业务流；或者，上述目标承载对应的信息也可以包括S1-U接口eNB FTEID信息，该S1-U接口eNB FTEID信息用于指示上述目标网关按照该S1-U接口eNB FTEID信息将接收到的需要发送给UE的下行业务流发送给eNB。
S613、UE通过eNB与上述目标GW_U之间进行上述目标业务的业务流的传输。
其中，上述目标业务的业务流的上行传输的流程为：UE根据上述NAS消息中的TFT信息匹配到新创建的承载，通过该新创建的承载向网络侧发送上行业 务报文；eNB接收UE发送的上行业务报文，匹配E-RAB的上下文并基于上述S1_U接口的F-TEID信息将上行业务报文发送给上述目标GW_U(即GW_C为上述目标业务选择的GW_U)，目标GW_U接收到eNB发送的上述目标业务的上行业务报文后将该上行业务报文发送至上述目标业务对应的网络。
本发明实施例中，需要说明的是，步骤S601以及步骤S602是可选的，即GW_U可以直接执行业务报文的检测，根据预先设置的业务匹配规则，主动向GW_C上报事件，GW_C通过GW_U上报的事件直接感知UE当前执行的目标业务，且还可以通过GW_U上报的事件获得相应的业务规则以及QoS信息等，本发明实施例不做限定。
可见，通过上述操作可以将UE当前执行的业务流绑定到一个新的承载且将该承载锚定到一个根据业务与网关部署的对应关系选择的GW_U，无需根据APN信息选择GW_U，即能够为具有相同APN信息的业务流选择不同的GW_U，进而使具有相同APN信息的业务流接入不同的PDN网络，实现了PDN网络内业务流的灵活部署。
需要说明的是，在图4-图6所示的方法实施例中，GW_C都是先为上述目标业务选择目标GW_U，然后再执行承载处理操作得到目标承载，此时，执行承载处理操作可以包括执行承载创建流程或执行承载修改流程。在实际应用中，GW_C也可以先执行对应的承载处理操作得到目标承载，然后再为上述目标业务选择目标GW_U，此时，执行对应的承载处理操作可以包括：执行承载创建流程。具体的：
若上述目标业务的QCI信息与UE的所有承载中每一个承载的QCI信息都不一致，则GW_C执行承载创建流程；或者
若上述目标业务的QCI信息与UE的第一承载的QCI信息一致且该第一承载所锚定的网关不能为上述目标业务提供服务，则GW_C设备执行承载创建流程；或者
若上述目标业务的QCI信息与用户设备UE的第二承载的QCI信息一致且该第二承载所锚定的网关可以为上述目标业务提供服务，则GW_C执行承载修改流程；或者
根据特定的配置，当上述目标业务所在的网络为一个独立网络(即上述目标业务所在的网络与其它业务所在的网络隔离，也可称为一个slicing_切片网络)时，例如当上述目标业务所在的网络为VPN网络(可视为切片网络)时，则GW_C执行承载创建流程，以得到上述目标承载。
需要说明的是，上述方法实施例能够达到的效果示意图可以如图7所示，图7是本发明实施例公开的一种效果示意图。其中，如图7所示，上述方法实施例达到的技术效果为：
1、GW_C将不同应用(APP，Application)相关的业务流绑定在特定的承载(可以通过TFT实现)，并锚定在特定的GW_U(即上述方法实施例中提到的目标GW_U)。
2、按需为承载配置独立的GPRS隧道协议用户面(GTP-U，User plane of GPRS Tunneling Protocol)链路信息，基于此，eNB可以将业务报文分发给不同的GW_U。
3、GW_U与APP之间可以建立独立的通信隧道，以确保应用之间的隔离。
4、对于UE而言，相同的IP可以访问不同的应用，不需要为每个应用配置APN信息。
请参阅如8，图8是本发明实施例公开的一种业务流的传输装置的结构示意图。如图8所示，该装置可以包括确定模块801、承载处理模块802、绑定模块803、锚定模块804以及传输模块805，其中：
确定模块801用于确定UE当前执行的目标业务。
承载处理模块802用于执行承载处理操作，以得到上述目标业务对应的目标承载。
绑定模块803用于将上述目标业务的业务流绑定到上述目标承载。
锚定模块804用于将上述目标承载与目标网关锚定。
传输模块805用于通过上述目标网关完成UE与上述目标业务对应的网络之间的业务流传输。
本发明实施例能够将业务流绑定到一个执行承载操作后得到的承载且将 该承载锚定到一个合适的网关(即目标网关)，实现了业务流的灵活部署，提高了业务流部署的灵活性。
在一个可选的实施例中，在图8所示的装置结构基础上，该装置还可以包括选择模块806，此时，该装置可以如图9所示，图9是本发明实施例公开的另一种业务流的传输装置的结构示意图。其中：
选择模块806用于根据业务与网关部署的对应关系为上述目标业务选择上述目标网关。
该可选的实施例能够根据业务与网关部署的对应关系选择目标网关的方式能够为具有相同APN信息的业务流选择不同的目标网关，进而使具有相同APN信息的业务流接入不同的PDN网络，实现了PDN网络内业务流的灵活部署。
其中，选择模块806根据业务与网关部署的对应关系为上述目标业务选择上述目标网关可以发生在确定模块801确定UE当前执行的目标业务之后且在承载处理模块802执行承载处理操作，以得到上述目标业务对应的目标承载之前，此时，承载处理模块802具体用于根据上述目标业务执行承载创建流程或承载修改流程；选择模块806根据业务与网关部署的对应关系为上述目标业务选择上述目标网关也可以发生在承载处理模块802执行承载处理操作，以得到上述目标业务对应的目标承载之后且在绑定模块803将上述目标业务的业务流绑定到上述目标承载之前，或者绑定模块803将上述目标业务的业务流绑定到上述目标承载之后且在锚定模块804将上述目标承载与目标网关锚定之前，此时，承载处理模块802具体用于执行承载创建流程。
作为一种可选的实施方式，确定模块801确定用户设备UE当前执行的目标业务的具体方式可以为：
接收UE发送的业务请求消息，该业务请求消息包括报文特征信息；
根据报文特征信息确定上述目标业务。
作为另一种可选的实施方式，确定模块801确定用户设备UE当前执行的目标业务的具体方式也可以为：
接收PCRF实体发送的会话修改请求消息，该会话修改请求消息包括报文特征信息；
根据报文特征信息确定上述目标业务。
作为又一种可选的实施方式，确定模块801确定用户设备UE当前执行的目标业务的具体方式还可以为：
接收第二网关设备上报的事件，该事件是由第二网关设备在检测出其接收到的业务报文满足预设条件时上报的；
根据事件确定上述目标业务。
在另一个可选的实施例中，选择模块806可以包括第一确定子模块8061以及第二确定子模块8062，此时，该装置的结构可以如图10所示，图10是本发明实施例公开的又一种业务流的传输装置的结构示意图。其中：
第一确定子模块8061用于根据业务与网关部署的对应关系确定能够为UE提供服务的目标网关清单，其中，该目标网关清单包括多个(即至少一个)能够为UE提供服务的网关。
第二确定子模块8062用于从上述目标网关清单包括的多个网关中确定一个网关作为上述目标网关。
可选的，第二确定子模块8062从上述目标网关清单包括的多个网关中确定一个网关作为上述目标网关的具体方式可以为：
若上述目标网关清单包括的多个网关中包含为UE提供服务的当前网关且该当前网关满足上述目标业务的业务需求，则将该当前网关确定为上述目标网关，这样将当前网关确定为目标网关的方式能够减少网络的切换，进而减少针对目标业务的处理时延。
可选的，第二确定子模块8062从上述目标网关清单包括的多个网关中确定一个网关作为上述目标网关的具体方式也可以为：
若上述目标网关清单包括的多个网关中包含为UE提供服务的当前网关且该当前网关不满足上述目标业务的业务需求，则从上述目标网关清单包括的多个网关中确定除该当前网关之外的一个网关作为上述目标网关；或着
若上述目标网关清单包括的多个网关中不包含为UE提供服务的当前网关，则从上述目标网关清单中包括的多个网关中确定一个网关作为上述目标网关。
其中，在该可选的实施例中，第二确定子模块8062为上述目标业务确定出的目标网关可以为位置较优的网关，这样可以减少目标业务的处理时延。
在该可选的实施例中，进一步可选的，承载处理模块802执行承载处理操作，以得到上述目标业务对应的目标承载的具体方式可以为：
当上述目标网关不是为UE提供服务的当前网关时，执行承载创建流程，以得到上述目标承载。
在另一个可选的实施例中，承载处理模块802执行承载处理操作，以得到上述目标业务对应的目标承载的具体方式可以为：
执行承载创建流程，以得到上述目标承载；或者
执行承载修改流程，以得到上述目标承载。
可选的，承载处理模块802执行承载创建流程，以得到上述目标承载的具体方式可以为：
若上述目标业务的QCI信息与UE的所有承载中每一个承载的QCI信息都不一致，则执行承载创建流程，以得到上述目标承载；或者
若上述目标业务的QCI信息与UE的第一承载的QCI信息一致且该第一承载所锚定的网关不能为上述目标业务提供服务，则执行承载创建流程，以得到上述目标承载；或者
若上述目标业务所在的网络为一个独立网络(如VPN网络时)，则执行承载创建流程，以得到上述目标承载，即当目标业务所在的网络为独立网络时，承载处理模块802可以直接执行承载创建流程，无需再进行QCI信息的判断，处理简单，能够快速的得到目标承载。
又一步可选的，承载处理模块802执行承载修改流程，以得到上述目标承载的具体方式可以为：
若上述目标业务的QCI信息与UE的第二承载的QCI信息一致且该第二承载所锚定的网关能够为上述目标业务提供服务，则执行承载修改流程，以得到上述目标承载，这样无需创建新的承载，节省了承载资源。
在又一个实施例中，锚定模块804将上述目标承载与上述目标网关锚定的具体方式可以为：
将上述目标承载对应的信息发送给上述目标网关，以将上述目标承载与上述目标网关进行锚定，其中，该目标承载对应的信息用于完成UE与上述目标业务对应的网络之间的业务流传输。
其中，上述目标承载对应的信息可以包括S1_U接口服务网关全量隧道端点标识(SGW FTEID，Service Gateway Full Qualified Tunnel Endpoint Identifier)信息，其中，该S1_U接口SGW FTEID信息用于指示上述目标网关接收UE发送的与该S1_U接口SGW FTEID信息相匹配的上行业务流；或者，上述目标承载对应的信息也包括业务流模板(TFT，Traffic Flow Template)信息，该TFT信息用于指示上述目标网关接收与该TFT信息相匹配的且需要发送给UE的下行业务流；或者，上述目标承载对应的信息也可以包括S1-U接口eNB FTEID信息，该S1-U接口eNB FTEID信息用于指示上述目标网关按照该S1-U接口eNB FTEID信息将接收到的需要发送给UE的下行业务流发送给eNB。
请参阅图11，图11是本发明实施例公开的又一种业务流的传输装置的结构示意图。如图11所示，该装置可以包括：存储器1101、通信接口1102、至少一个处理器1103(如CPU)以及至少一个通信总线1104，存储器1101可以是高速RAM存储器，也可以是非易失性存储器(non-volatile memory)，如至少一个磁盘存储器，可选的，存储器1101还可以是至少一个位于远离前述处理器1103的存储装置。其中：
通信总线1104用于实现这些组件之间的连接通信。
存储器1101中存储一组程序代码，且处理器1103用于调用存储器1101中存储的程序代码，用于执行以下操作：
确定UE当前执行的目标业务，执行承载处理操作，以得到该目标业务对应的目标承载，将该目标业务的业务流绑定到该目标承载，并将该目标承载与目标网关锚定；
通信接口1102用于通过上述目标网关完成UE与上述目标业务对应的网络之间的业务流传输。
在一个可选的实施例中，处理器1103用于调用存储器1101中存储的程序代 码，还可以用于执行以下操作：
根据业务与网关部署的对应关系为上述目标业务选择上述目标网关。
可选的，处理器1103根据业务与网关部署的对应关系为上述目标业务选择上述目标网关的具体方式可以为：
根据业务与网关部署的对应关系确定能够为UE提供服务的目标网关清单，其中，该目标网关清单包括多个能够为UE提供服务的网关；
从目标网关清单包括的多个网关中确定一个网关作为上述目标网关。
进一步可选的，处理器1103从目标网关清单包括的多个网关中确定一个网关作为上述目标网关的具体方式可以为：
若目标网关清单包括的多个网关中包含为UE提供服务的当前网关且该当前网关满足目标业务的业务需求，则将该当前网关确定为上述目标网关。
进一步可选的，处理器1103从目标网关清单包括的多个网关中确定一个网关作为上述目标网关的具体方式也可以为：
若上述目标网关清单包括的多个网关中包含为UE提供服务的当前网关且该当前网关不满足上述目标业务的业务需求，则从上述目标网关清单包括的多个网关中确定除该当前网关之外的一个网关作为上述目标网关；或着
若上述目标网关清单包括的多个网关中不包含为UE提供服务的当前网关，则从上述目标网关清单中包括的多个网关中确定一个网关作为上述目标网关。
在该可选的实施例中，又进一步可选的，处理器1103执行承载处理操作，以得到上述目标业务对应的目标承载的具体方式可以为：
当上述目标网关不是为UE提供服务的当前网关时，执行承载创建流程，以得到上述目标承载。
在另一个实施例中，处理器1103确定UE当前执行的目标业务的具体方式可以为：
接收UE发送的业务请求消息，其中，该业务请求消息包括报文特征信息；
根据报文特征信息确定上述目标业务。
在又一个实施例中，处理器1103确定UE当前执行的目标业务的具体方式 也可以为：
接收PCRF实体发送的会话修改请求消息，该会话修改请求消息包括报文特征信息；
根据报文特征信息确定上述目标业务。
在又一个可选的实施例中，处理器1103确定UE当前执行的目标业务的具体方式还可以为：
接收第二网关设备上报的事件，该事件是由第二网关设备在检测出其接收到的业务报文满足预设条件时上报的；
根据事件确定上述目标业务。
在又一个可选的实施例中，处理器1103执行对应的承载处理操作，以得到上述目标业务对应的目标承载的具体方式可以为：
执行承载创建流程，以得到上述目标承载；或者
执行承载修改流程，以得到上述目标承载。
可选的，处理器1103执行承载创建流程，以得到上述目标承载的具体方式可以为：
若上述目标业务的服务质量等级标识QCI信息与UE的所有承载中每一个承载的QCI信息都不一致，则执行承载创建流程，以得到上述目标承载；或者
若上述目标业务的QCI信息与UE的第一承载的QCI信息一致且该第一承载所锚定的网关不能为上述目标业务提供服务，则执行承载创建流程，以得到上述目标承载；
或者若上述目标业务所在的网络为一个独立网络(如VPN网络时)，则执行承载创建流程，以得到上述目标承载。
可选的，处理器1103执行承载修改流程，以得到上述目标承载的具体方式可以为：
若上述目标业务的QCI信息与UE的第二承载的QCI信息一致且该第二承载所锚定的网关能够为上述目标业务提供服务，则执行承载修改流程，以得到上述目标承载。
在又一个可选的实施例中，处理器1103将上述目标承载与上述目标网关锚 定的具体方式可以为：
将上述目标承载对应的信息发送给上述目标网关，其中，该目标承载对应的信息用于完成UE与上述目标业务对应的网络之间的业务流传输。
可选的，上述目标承载对应的信息可以包括S1_U接口服务网关全量隧道端点标识(SGW FTEID，Service Gateway Full Qualified Tunnel Endpoint Identifier)信息，其中，该S1_U接口SGW FTEID信息用于指示上述目标网关接收UE发送的与该S1_U接口SGW FTEID信息相匹配的上行业务流；或者，上述目标承载对应的信息也包括业务流模板(TFT，Traffic Flow Template)信息，该TFT信息用于指示上述目标网关接收与该TFT信息相匹配的且需要发送给UE的下行业务流；或者，上述目标承载对应的信息也可以包括S1-U接口eNB FTEID信息，该S1-U接口eNB FTEID信息用于指示上述目标网关按照该S1-U接口eNB FTEID信息将接收到的需要发送给UE的下行业务流发送给eNB。
可见，本发明实施例能够将业务流绑定到执行承载处理操作得到的承载，且能够根据业务与网关部署的对应关系为业务流选择合适的网关并将得到得承载锚定到该合适的网关，实现了将同一个PDN连接的不同承载锚定到不同的网关，进而实现了业务流的灵活部署，提高业务流部署的灵活性。
需要说明的是，在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详细描述的部分，可以参见其他实施例的相关描述。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作、模块以及子模块并不一定是本发明所必须的。
本发明实施例方法中的步骤可以根据实际需要进行顺序调整、合并和删减。
本发明实施例第一网关设备中的模块以及子模块可以根据实际需要进行合并、划分和删减。
本发明实施例中所述模块以及子模块，可以通过通用集成电路，例如CPU(Central Processing Unit，中央处理器)，或通过ASIC(Application Specific Integrated Circuit，专用集成电路)来实现。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的程序可存储于计算机 可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory，ROM)或随机存储记忆体(Random Access Memory，RAM)等。
总之，以上所述仅为本发明的较佳实施例而已，并非用于限定本发明的保护范围。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (28)

  1. 一种业务流的传输方法，其特征在于，所述方法包括：
    第一网关设备确定用户设备UE当前执行的目标业务；
    所述第一网关设备执行承载处理操作，以得到所述目标业务对应的目标承载，并将所述目标业务的业务流绑定到所述目标承载；
    所述第一网关设备将所述目标承载与目标网关锚定，并通过所述目标网关完成所述UE与所述目标业务对应的网络之间的业务流传输。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一网关设备根据业务与网关部署的对应关系为所述目标业务选择所述目标网关。
  3. 根据权利要求2所述的方法，其特征在于，所述第一网关设备根据业务与网关部署的对应关系为所述目标业务选择所述目标网关，包括：
    所述第一网关设备根据业务与网关部署的对应关系确定能够为所述UE提供服务的目标网关清单，所述目标网关清单包括多个能够为所述UE提供服务的网关；
    所述第一网关设备从所述目标网关清单包括的多个网关中确定一个网关作为所述目标网关。
  4. 根据权利要求3所述的方法，其特征在于，所述第一网关设备从所述目标网关清单包括的多个网关中确定一个网关作为所述目标网关，包括：
    若所述目标网关清单包括的多个网关中包含为所述UE提供服务的当前网关且所述当前网关满足所述目标业务的业务需求，则所述第一网关设备将所述当前网关确定为所述目标网关。
  5. 根据权利要求3所述的方法，其特征在于，所述第一网关设备从所述目标网关清单包括的多个网关中确定一个网关作为所述目标网关，包括：
    若所述目标网关清单包括的多个网关中包含为所述UE提供服务的当前网关且所述当前网关不满足所述目标业务的业务需求，则所述第一网关设备从所述目标网关清单包括的多个网关中确定除所述当前网关之外的一个网关作为所述目标网关；或着
    若所述目标网关清单包括的多个网关中不包含为所述UE提供服务的当前网关，则所述第一网关设备从所述目标网关清单中包括的多个网关中确定一个网关作为所述目标网关。
  6. 根据权利要求5所述的方法，其特征在于，所述第一网关设备执行承载处理操作，以得到所述目标业务对应的目标承载，包括：
    当所述目标网关不是为所述UE提供服务的当前网关时，所述第一网关设备执行承载创建流程，以得到所述目标承载。
  7. 根据权利要求1或2所述的方法，其特征在于，所述第一网关设备执行承载处理操作，以得到所述目标业务对应的目标承载，包括：
    所述第一网关设备执行承载创建流程，以得到所述目标承载；或者
    所述第一网关设备执行承载修改流程，以得到所述目标承载。
  8. 根据权利要求7所述的方法，其特征在于，所述第一网关设备执行承载创建流程，以得到所述目标承载，包括：
    若所述目标业务的服务质量等级标识QCI信息与所述UE的所有承载中每一个承载的QCI信息都不一致，则所述第一网关设备执行承载创建流程，以得到所述目标承载；或者
    若所述目标业务的QCI信息与所述UE的第一承载的QCI信息一致且所述第一承载所锚定的网关不能为所述目标业务提供服务，则所述第一网关设备执行承载创建流程，以得到所述目标承载；或者
    若所述目标业务所在的网络为一个独立网络，则第一网关设备执行承载创建流程，以得到所述目标承载。
  9. 根据权利要求7所述的方法，其特征在于，所述第一网关设备执行承载修改流程，以得到所述目标承载，包括：
    若所述目标业务的服务质量等级标识QCI信息与所述UE的第二承载的QCI信息一致且所述第二承载所锚定的网关能够为所述目标业务提供服务，则所述第一网关设备执行承载修改流程，以得到所述目标承载。
  10. 根据权利要求1或2所述的方法，其特征在于，所述第一网关设备将所述目标承载与目标网关锚定，包括：
    所述第一网关设备将所述目标承载对应的信息发送给所述目标网关，所述目标承载对应的信息用于完成所述UE与所述目标业务对应的网络之间的业务流传输。
  11. 根据权利要求10所述的方法，其特征在于，所述目标承载对应的信息包括S1_U接口服务网关全量隧道端点标识SGW FTEID信息，所述S1_U接口SGWFTEID信息用于指示所述目标网关接收所述UE发送的与所述S1_U接口SGWFTEID信息相匹配的上行业务流；或者
    所述目标承载对应的信息包括业务流模板TFT信息，所述TFT信息用于指示所述目标网关接收与所述TFT信息相匹配的需要发送给所述UE的下行业务流；或者
    所述目标承载对应的信息包括S1-U接口演进型基站eNB FTEID信息，所述S1-U接口eNB FTEID信息用于指示所述目标网关按照所述S1-U接口eNB FTEID信息将接收到的需要发送给所述UE的下行业务流发送给eNB。
  12. 根据权利要求1-11任一项所述的方法，其特征在于，所述第一网关设备确定用户设备UE当前执行的目标业务，包括：
    所述第一网关设备接收所述UE发送的业务请求消息，所述业务请求消息包括报文特征信息；
    所述第一网关设备根据所述报文特征信息确定所述目标业务。
  13. 根据权利要求1-11任一项所述的方法，其特征在于，所述第一网关设备确定用户设备UE当前执行的目标业务，包括：
    所述第一网关设备接收策略与计费规则功能PCRF实体发送的会话修改请求消息，所述会话修改请求消息包括报文特征信息；
    所述第一网关设备根据所述报文特征信息确定所述目标业务。
  14. 根据权利要求1-11任一项所述的方法，其特征在于，所述第一网关设备确定用户设备UE当前执行的目标业务，包括：
    所述第一网关设备接收第二网关设备上报的事件，所述事件是由所述第二网关设备在检测出其接收到的业务报文满足预设条件时上报的；
    所述第一网关设备根据所述事件确定所述目标业务。
  15. 一种业务流的传输装置，其特征在于，所述装置包括确定模块、承载处理模块、绑定模块、锚定模块以及传输模块，其中：
    所述确定模块，用于确定用户设备UE当前执行的目标业务；
    所述承载处理模块，用于执行承载处理操作，以得到所述目标业务对应的目标承载；
    所述绑定模块，用于将所述目标业务的业务流绑定到所述目标承载；
    所述锚定模块，用于将所述目标承载与目标网关锚定；
    所述传输模块，用于通过所述目标网关完成所述UE与所述目标业务对应的网络之间的业务流传输。
  16. 根据权利要求15所述的装置，其特征在于，所述装置还包括选择模块，其中：
    所述选择模块，用于根据业务与网关部署的对应关系为所述目标业务选择所述目标网关。
  17. 根据权利要求16所述的装置，其特征在于，所述选择模块包括第一确定子模块以及第二确定子模块，其中：
    所述第一确定子模块，用于根据所述业务与网关部署的对应关系确定能够为所述UE提供服务的目标网关清单，所述目标网关清单包括多个能够为所述UE提供服务的网关；
    所述第二确定子模块，用于从所述目标网关清单包括的多个网关中确定一个网关作为所述目标网关。
  18. 根据权利要求17所述的装置，其特征在于，所述第二确定子模块从所述目标网关清单包括的多个网关中确定一个网关作为所述目标网关的具体方式为：
    若所述目标网关清单包括的多个网关中包含为所述UE提供服务的当前网关且所述当前网关满足所述目标业务的业务需求，则将所述当前网关确定为所述目标网关。
  19. 根据权利要求17所述的装置，其特征在于，所述第二确定子模块从所述目标网关清单包括的多个网关中确定一个网关作为所述目标网关的具体方式为：
    若所述目标网关清单包括的多个网关中包含为所述UE提供服务的当前网关且所述当前网关不满足所述目标业务的业务需求，则从所述目标网关清单包括的多个网关中确定除所述当前网关之外的一个网关作为所述目标网关；或着
    若所述目标网关清单包括的多个网关中不包含为所述UE提供服务的当前网关，则从所述目标网关清单中包括的多个网关中确定一个网关作为所述目标网关。
  20. 根据权利要求19所述的装置，其特征在于，所述承载处理模块执行承载处理操作，以得到所述目标业务对应的目标承载的具体方式为：
    当所述目标网关不是为所述UE提供服务的当前网关时，执行承载创建流程，以得到所述目标承载。
  21. 根据权利要求15或16所述的装置，其特征在于，所述承载处理模块执行承载处理操作，以得到所述目标业务对应的目标承载的具体方式为：
    执行承载创建流程，以得到所述目标承载；或者
    执行承载修改流程，以得到所述目标承载。
  22. 根据权利要求21所述的装置，其特征在于，所述承载处理模块执行承载创建流程，以得到所述目标承载的具体方式为：
    若所述目标业务的服务质量等级标识QCI信息与所述UE的所有承载中每一个承载的QCI信息都不一致，则执行承载创建流程，以得到所述目标承载；或者
    若所述目标业务的QCI信息与所述UE的第一承载的QCI信息一致且所述第一承载所锚定的网关不能为所述目标业务提供服务，则执行承载创建流程，以得到所述目标承载；或者
    若所述目标业务所在的网络为一个独立网络，则执行承载创建流程，以得到所述目标承载。
  23. 根据权利要求21所述的装置，其特征在于，所述承载处理模块执行承载修改流程，以得到所述目标承载的具体方式为：
    若所述目标业务的服务质量等级标识QCI信息与所述UE的第二承载的QCI信息一致且所述第二承载所锚定的网关能够为所述目标业务提供服务，则执行承载修改流程，以得到所述目标承载。
  24. 根据权利要求15或16所述的装置，其特征在于，所述锚定模块将所述目标承载与目标网关锚定的具体方式为：
    将所述目标承载对应的信息发送给所述目标网关，所述目标承载对应的信 息用于完成所述UE与所述目标业务对应的网络之间的业务流传输。
  25. 根据权利要求24所述的装置，其特征在于，所述所述目标承载对应的信息包括S1_U接口服务网关全量隧道端点标识SGW FTEID信息，所述S1_U接口SGW FTEID信息用于指示所述目标网关接收所述UE发送的与所述S1_U接口SGW FTEID信息相匹配的上行业务流；或者
    所述目标承载对应的信息包括业务流模板TFT信息，所述TFT信息用于指示所述目标网关接收与所述TFT信息相匹配的需要发送给所述UE的下行业务流；或者
    所述目标承载对应的信息包括S1-U接口演进型基站eNB FTEID信息，所述S1-U接口eNB FTEID信息用于指示所述目标网关按照所述S1-U接口eNB FTEID信息将接收到的需要发送给所述UE的下行业务流发送给eNB。
  26. 根据权利要求15-24任一项所述的装置，其特征在于，所述确定模块确定用户设备UE当前执行的目标业务的具体方式为：
    接收所述UE发送的业务请求消息，所述业务请求消息包括报文特征信息；
    根据所述报文特征信息确定所述目标业务。
  27. 根据权利要求15-24任一项所述的装置，其特征在于，所述确定模块确定用户设备UE当前执行的目标业务的具体方式为：
    接收策略与计费规则功能PCRF实体发送的会话修改请求消息，所述会话修改请求消息包括报文特征信息，并根据所述报文特征信息确定所述目标业务。
  28. 根据权利要求15-24任一项所述的装置，其特征在于，所述确定模块确定用户设备UE当前执行的目标业务的具体方式为：
    接收第二网关设备上报的事件，所述事件是由所述第二网关设备在检测出其接收到的业务报文满足预设条件时上报的，并根据所述事件确定所述目标业务。
PCT/CN2015/094907 2015-11-18 2015-11-18 一种业务流的传输方法及装置 WO2017084042A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2015/094907 WO2017084042A1 (zh) 2015-11-18 2015-11-18 一种业务流的传输方法及装置
EP15908539.8A EP3361816A1 (en) 2015-11-18 2015-11-18 Service flow transmission method and apparatus
CN201580082384.9A CN107926066B (zh) 2015-11-18 2015-11-18 一种业务流的传输方法及装置
US15/972,370 US20180255481A1 (en) 2015-11-18 2018-05-07 Service flow transmission method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/094907 WO2017084042A1 (zh) 2015-11-18 2015-11-18 一种业务流的传输方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/972,370 Continuation US20180255481A1 (en) 2015-11-18 2018-05-07 Service flow transmission method and apparatus

Publications (1)

Publication Number Publication Date
WO2017084042A1 true WO2017084042A1 (zh) 2017-05-26

Family

ID=58717130

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/094907 WO2017084042A1 (zh) 2015-11-18 2015-11-18 一种业务流的传输方法及装置

Country Status (4)

Country Link
US (1) US20180255481A1 (zh)
EP (1) EP3361816A1 (zh)
CN (1) CN107926066B (zh)
WO (1) WO2017084042A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018057077A1 (en) * 2016-09-21 2018-03-29 Mavenir Systems, Inc. Method and system for session resilience in packet gateways
JP6887436B2 (ja) * 2016-09-30 2021-06-16 株式会社Ｎｔｔドコモ ゲートウェイ選択方法および通信システム
US20200022074A1 (en) * 2016-09-30 2020-01-16 Ntt Docomo, Inc. Gateway selection method and communication system
EP3624499B1 (en) * 2017-05-08 2023-04-19 NTT DoCoMo, Inc. Communication control method and communication system

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101557646A (zh) * 2008-04-10 2009-10-14 华为技术有限公司 创建承载方法、服务网关和移动性管理实体
US20090285179A1 (en) * 2008-05-16 2009-11-19 Bridgewater Systems Corp. Long-Term Evolution (LTE) Packet Data Network Gateway (PDN-GW) Selection
CN101631354A (zh) * 2008-07-18 2010-01-20 华为技术有限公司 一种分组数据网络选择的方法、装置与系统

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8064403B2 (en) * 2007-08-17 2011-11-22 Research In Motion Limited Mobility mechanism for service continuity
EP2884812B1 (en) * 2011-04-01 2016-12-28 Interdigital Patent Holdings, Inc. Apparatus and method for sharing a common PDP context
US20140153391A1 (en) * 2011-06-22 2014-06-05 Telefonaktiebolaget L M Ericsson (Publ) Method for Policy Control and Method for Bearer Control as Well as Corresponding Servers, Systems and Computer Programs
CN103248451B (zh) * 2012-02-09 2016-12-07 华为技术有限公司 业务速率控制方法和系统以及设备
CN103716850B (zh) * 2012-09-29 2018-10-26 中兴通讯股份有限公司 通信路径的切换方法、系统及装置
CN104661205B (zh) * 2013-11-22 2019-12-03 中兴通讯股份有限公司 一种网关更新信息通知方法及控制器
JP2015231139A (ja) * 2014-06-05 2015-12-21 日本電気株式会社 ゲートウェイ装置、フェムトセル用基地局、通信システム、通信方法およびプログラム
US9591516B2 (en) * 2014-12-23 2017-03-07 Motorola Solutions, Inc. Method and apparatus for managing bearers in a wireless communication system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101557646A (zh) * 2008-04-10 2009-10-14 华为技术有限公司 创建承载方法、服务网关和移动性管理实体
US20090285179A1 (en) * 2008-05-16 2009-11-19 Bridgewater Systems Corp. Long-Term Evolution (LTE) Packet Data Network Gateway (PDN-GW) Selection
CN101631354A (zh) * 2008-07-18 2010-01-20 华为技术有限公司 一种分组数据网络选择的方法、装置与系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3361816A4 *

Also Published As

Publication number Publication date
US20180255481A1 (en) 2018-09-06
CN107926066B (zh) 2020-05-15
CN107926066A (zh) 2018-04-17
EP3361816A4 (en) 2018-08-15
EP3361816A1 (en) 2018-08-15

Similar Documents

Publication Publication Date Title
US11051212B2 (en) Interworking with bearer-based system
EP3454601B1 (en) Method and apparatus for controlling quality of service
US20190141169A1 (en) User-plane protocol stack determining method, control-plane network element, and system
JP6561204B2 (ja) Ｉｐ層におけるデュアルコネクティビティおよびキャリアアグリゲーション
EP3001735B1 (en) Service offloading method and base station
US11825356B2 (en) Policy control method and system, network element, and storage medium
JP2019521588A (ja) 通信制御方法および関連するネットワーク要素
WO2019242731A1 (zh) 数据处理方法和设备
US10536457B2 (en) User data processing apparatus and method, and system
US9860869B2 (en) Method and apparatus for offloading data traffic in a wireless communication system
WO2016191963A1 (zh) 一种建立承载的方法、用户设备及基站
US9961045B2 (en) Service path changing method and apparatus
US20180255481A1 (en) Service flow transmission method and apparatus
WO2016107404A1 (zh) 业务流传输路径优化方法、装置及mme
JP2016536814A (ja) 専用ベアラを用いるローカルａｎｄｓｆサーバへのアクセス
WO2013053133A1 (zh) 业务数据传输处理方法、设备以及通信系统
US20150271709A1 (en) Bearer Management in the RAN Based on Quality of Service
EP2844022B1 (en) Method and system for routing cdn traffic with a shadow packet data network gateway
WO2011134408A1 (zh) 选择性ip数据分流激活的通知及输出方法、系统和设备
WO2018045515A1 (zh) 一种数据分流方法及相关装置
WO2016131240A1 (zh) 分组数据业务的处理系统、方法及装置
US20220116798A1 (en) Data transmission method, apparatus, and device
KR102109605B1 (ko) 패킷 데이터 네트워크 연결 설정 방법 및 이를 위한 장치
EP2903330B1 (en) Data transmission method, base station, access network device and user equipment

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2015908539

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE