WO2016106702A1

WO2016106702A1 - Service traffic distribution method and apparatus

Info

Publication number: WO2016106702A1
Application number: PCT/CN2014/095949
Authority: WO
Inventors: 诸华林; 于游洋; 李欢
Original assignee: 华为技术有限公司
Priority date: 2014-12-31
Filing date: 2014-12-31
Publication date: 2016-07-07
Also published as: CN107005909A

Abstract

Provided are a service traffic distribution method and apparatus. The method comprises: firstly, a gateway receiving a second routing message sent by a second device, the second routing message being a first routing message or a message obtained by updating the first routing message by the second device, and the first routing message being generated by a first device according to a congestion message or quintuple in service traffic or a non-3GPP service set identifier (SSID) of a wireless local area network; and secondly, the gateway distributing service traffic at a Third Generation Partnership Project (3GPP) network side to a non-3GPP side according to the second routing message, or distributing service traffic at the non-3GPP side to the 3GPP network side, thereby improving the reliability of a communication system.

Description

Service flow distribution method and device

Technical field

The embodiments of the present invention relate to communication technologies, and in particular, to a service flow offloading method and apparatus.

Background technique

With the continuous development of communication technologies, data traffic on User Equipment (UE) is growing at a high speed.

Generally, the UE implements data transmission through the 3rd Generation Partnership Project (3GPP) network and the non-3GPP network, where the non-3GPP network includes: Wireless Local Area Networks (WLAN), code division multiple access ( Code Division Multiple Access (CDMA) network, Worldwide Interoperability for Microwave Access (WiMax) network, etc. And the traffic of the service flow in the two networks is independent of each other. Due to the increase of service traffic, there is often a problem that the signaling of the 3GPP side is congested. The method for solving the congestion problem in the prior art is: 1. If congestion occurs. Mobility Management Entity (MME) will limit the progress of some low-priority session management processes and mobility management processes, and limit the number of downlink control plane signaling; 2. Packet Data Network Gateway For example, PGW will also be processed accordingly, such as rejecting certain low-priority user equipments from accessing a packet data network (Packet Data Network (PDN) connection); 3. The MME sends a back_off timer to the UE to notify the UE that Do not attempt to initiate a session management request or a mobility management request for a period of time.

However, in the prior art, regardless of the above method, it solves the 3GPP congestion problem by rejecting the low-priority user access, that is, the congestion problem is solved by cutting off the service flow, thereby reducing the communication network. Reliability.

Summary of the invention

The embodiment of the invention provides a service flow offloading method and device, thereby improving the reliability of the communication network.

In a first aspect, an embodiment of the present invention provides a service flow offloading method, including: a gateway receiving a second routing message sent by a second device, where the second routing message is a first routing message or is a second device pair. The first routing message is updated by the first device according to a congestion message or a quintuple in the service flow, or a non-3GPP service set identifier SSID of the WLAN; the gateway And offloading the third generation partner planned 3GPP network side service flow to the non-3GPP side according to the second routing message, or offloading the non-3GPP side service flow to the 3GPP network side; wherein the congestion message is used to indicate that the same public service flow is based The third-generation partner of the network PDN connection plans congestion of the 3GPP network side and the non-3GPP network side traffic flow, the quintuple includes: source Internet Protocol IP address, source port, destination IP address, destination port, and transport layer protocol No. The first routing message carries a routing message name, an access type, a service flow number, and a filtering condition.

In conjunction with the first aspect, in a first possible implementation manner of the first aspect, the second routing message further includes a default routing message name, a default access type, a default service flow number, and a default filtering condition.

With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the gateway, according to the second routing message, performs service flow offloading, specifically: the gateway according to the foregoing The filtering condition in the two routing messages matches the service flow; if the matching is successful, the service flow is offloaded to the network of the access type corresponding to the filtering condition; if the matching fails, the service flow is offloaded to the In the network corresponding to the default access type, the access type and the default access type include: a wireless local area network non-3GPP and a third generation partner plan 3GPP network.

With reference to the first aspect, or the first possible implementation manner or the second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, the first device is a user equipment UE, the second The device is a policy charging rule function PCRF server; or the first device is a policy charging rule function PCRF server, and the second device is a user equipment UE.

With reference to the third possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, the method further includes: if the first device is a policy charging rule function PCRF server, the second device is a user The device UE sends the congestion message to the first device.

In a second aspect, an embodiment of the present invention provides a service flow offloading method, including: a first device Obtaining a congestion message, where the congestion message is used to indicate congestion of a third generation partner plan 3GPP network side and a non-3GPP network side service flow based on the same public service flow network PDN connection; the first device generates a first routing message; The first device sends the first routing message to the second device; the first device receives the second routing message sent by the second device by using the gateway; wherein the first routing message carries the routing message name, An access type, a service flow number, and a filter condition, where the second routing message is the first routing message or a message that is updated by the second device to the first routing message, where the second routing message is used Diverted from the business flow.

With reference to the second aspect, in a first possible implementation manner of the second aspect, the first device is a user equipment UE, and the second device is a policy charging rule function PCRF server; or the first device is The policy charging rule function is a PCRF server, and the second device is a user equipment UE.

With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, if the first device is a user equipment UE, and the second device is a policy charging rule function PCRF server, The first device obtains the congestion message, and the method includes: the first device acquiring the congestion message sent by the gateway or the second device; or the first device determining whether the network side is congested, and acquiring the location according to the determination result Congestion messages.

With reference to the second possible implementation manner of the second aspect, in a third possible implementation manner of the second aspect, the method further includes: the first device performing traffic splitting according to the second routing message.

With reference to the first possible implementation manner of the second aspect, in a fourth possible implementation manner of the second aspect, if the first device is a policy charging rule function PCRF server, and the second device is a user equipment UE, And the first device acquiring the congestion message, where the method includes: acquiring, by the first device, a congestion message sent by the gateway.

With reference to the second aspect or the first possible implementation or the second possible implementation manner, or the third possible implementation manner or the fourth possible implementation manner of the second aspect, in a fifth possible implementation manner of the second aspect, The first device generates the first routing message, specifically: the first device generates the first according to the congestion message, or a quintuple in the service flow, or a service set identifier SSID of the WLAN non-3GPP The routing message, wherein the five-tuple includes: a source Internet Protocol IP address, a source port, a destination IP address, a destination port, and a transport layer protocol number.

In a third aspect, an embodiment of the present invention provides a service flow offloading method, including: a second device Receiving, by the first device, the first routing message, where the first routing message is generated by the first device according to a congestion message or a quintuple in the service flow, or a non-3GPP service set identifier SSID of the WLAN; The second device sends a second routing message to the gateway, so that the gateway performs traffic distribution according to the second routing message, where the second routing message is the first routing message or is the second device pair. The updated message of the first routing message; wherein the congestion message is used to indicate congestion caused by a third generation partner plan 3GPP network side and a non-3GPP network side service flow based on the same public service flow network PDN connection, the five The tuple includes: a source Internet Protocol IP address, a source port, a destination IP address, a destination port, and a transport layer protocol number, and the first routing message carries a routing message name, an access type, a service flow number, and a filtering condition.

With reference to the third aspect, in a first possible implementation manner of the third aspect, the first routing message further includes: a protocol barring item; the second device determining, according to the protocol barring item, whether to update the first Routing messages.

In a fourth aspect, the embodiment of the present invention provides a service flow offloading device, including: a receiving module, configured to receive a second routing message sent by a second device, where the second routing message is a first routing message or The second device sends the updated message to the first routing message, where the first routing message is generated by the first device according to a congestion message or a quintuple in the service flow, or a non-3GPP service set identifier SSID of the WLAN. And a processing device, configured to offload the third generation partner plan 3GPP network side service flow to the non-3GPP side according to the second routing message, or offload the non-3GPP side service flow to the 3GPP network side; wherein the congestion message is used to indicate that the The third generation partner of the same public service flow network PDN is connected to the 3GPP network side and the non-3GPP network side service flow, and the quintuple includes: source Internet protocol IP address, source port, destination IP address, destination port, And a transport layer protocol number, where the first routing message carries a routing message name, an access type, a service flow number, and a filtering condition.

In conjunction with the fourth aspect, in a first possible implementation manner of the fourth aspect, the second routing message further includes a default routing message name, a default access type, a default service flow number, and a default filtering condition.

With reference to the first possible implementation manner of the fourth aspect, in a second possible implementation manner of the fourth aspect, the processing module is configured to match the service flow according to the filtering condition in the second routing message; Discharging the service flow to the network of the access type corresponding to the filter condition; if the match fails, the service flow is offloaded to the network corresponding to the default access type, The access type and the default access type include: a wireless local area network non-3GPP and a third generation partnership plan 3GPP network.

With reference to the fourth aspect, or the first possible implementation manner or the second possible implementation manner of the fourth aspect, in a third possible implementation manner of the fourth aspect, the first device is a user equipment UE, the second The device is a policy charging rule function PCRF server; or the first device is a policy charging rule function PCRF server, and the second device is a user equipment UE.

With reference to the third possible implementation manner of the fourth aspect, in a fourth possible implementation manner of the fourth aspect, if the first device is a policy charging rule function PCRF server, the second device is a user equipment UE, The gateway further includes: a sending module, configured to send the congestion message to the first device.

In a fifth aspect, the embodiment of the present invention provides a service flow offloading device, including: an obtaining module, configured to acquire a congestion message, where the congestion message is used to indicate a third generation partner plan 3GPP network based on a PDN connection of the same public service flow network The congestion occurs on the side and the non-3GPP network side service flow; the generating module is configured to generate the first routing message; the sending module is configured to send the first routing message to the second device; and the receiving module is configured to receive the first a second routing message sent by the second device by the gateway; where the first routing message carries a routing message name, an access type, a service flow number, and a filtering condition, where the second routing message is the first routing message or The second device updates the message of the first routing message, and the second routing message is used for traffic splitting.

With reference to the fifth aspect, in a first possible implementation manner of the fifth aspect, the service flow offloading device is a user equipment UE, and the second device is a policy charging rule function PCRF server; or the service flow is offloaded. The device is a policy charging rule function PCRF server, and the second device is a user equipment UE.

With reference to the first possible implementation manner of the fifth aspect, in a second possible implementation manner of the fifth aspect, if the service flow offloading device is a user equipment UE, and the second device is a policy charging rule function PCRF server, The acquiring module is specifically configured to: obtain a congestion message sent by the gateway or the second device; or determine whether there is congestion on the network side, and obtain the congestion message according to the determination result.

With reference to the second possible implementation manner of the fifth aspect, in a third possible implementation manner of the fifth aspect, the method further includes: a processing module, configured to perform service flow splitting according to the second routing message.

With reference to the first possible implementation manner of the fifth aspect, in a fourth possible implementation manner of the fifth aspect, if the service flow offloading device is a policy charging rule function PCRF server, the second device is a user equipment UE The acquiring module is specifically configured to: obtain a congestion message sent by the gateway.

With reference to the fifth aspect or the first possible implementation or the second possible implementation manner, or the third possible implementation manner or the fourth possible implementation manner of the fifth aspect, in a fifth possible implementation manner of the fifth aspect, The generating module is specifically configured to: generate the first routing message according to the congestion message, or a quintuple in a service flow, or a service set identifier SSID of a non-3GPP of a wireless local area network, where the quintuple includes : source Internet Protocol IP address, source port, destination IP address, destination port, and transport layer protocol number.

In a sixth aspect, the embodiment of the present invention provides a service flow offloading device, including: a receiving module, configured to receive a first routing message sent by a first device, where the first routing message is that the first device is according to a congestion message or a quintuple in the service flow, or a wireless local area network generated by the service set identifier SSID of the 3GPP; the sending module is configured to send a second routing message to the gateway, so that the gateway performs the service flow according to the second routing message. The second routing message is the first routing message or the message that the second device updates the first routing message; wherein the congestion message is used to indicate that the PDN connection is based on the same public service flow network. The third generation partner plans to congest the 3GPP network side and the non-3GPP network side traffic flow, the quintuple includes: source Internet Protocol IP address, source port, destination IP address, destination port, and transport layer protocol number, The first routing message carries a routing message name, an access type, a service flow number, and a filtering condition.

With reference to the sixth aspect, in a first possible implementation manner of the sixth aspect, the first routing message further includes: a protocol forbidden item; the service flow offloading device further includes: a determining module; the determining module, And configured to determine, according to the protocol prohibition item, whether to update the first routing message.

An embodiment of the present invention provides a service flow offloading method and apparatus, where the method includes: a first device generates a first routing message, and then sends the first routing message to a second device, where the second device determines to obtain a second according to the first routing message. The routing message is such that the UE and the gateway finally perform traffic splitting according to the second routing message. Since the first routing message and the second routing message take into account the congestion message or the useful information in the service flow, the service flow distribution is more effective and reasonable, and further The reliability of the communication system is guaranteed.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any inventive labor.

1 is a schematic diagram of an LTE network architecture provided by the present invention;

2 is a flowchart of a service flow offloading method according to Embodiment 1 of the present invention;

3 is a flowchart of a service flow offloading method according to Embodiment 2 of the present invention;

4 is a flowchart of a service flow offloading method according to Embodiment 3 of the present invention;

FIG. 5 is a flowchart of creating a new dedicated bearer according to Embodiment 4 of the present invention; FIG.

FIG. 6 is a flowchart of a UE initiated service request according to Embodiment 4 of the present invention;

FIG. 7 is a flowchart 1 of a service flow switching initiated by a PCRF according to Embodiment 4 of the present invention;

FIG. 8 is a flowchart 2 of a service flow switching initiated by a PCRF according to Embodiment 4 of the present invention;

FIG. 9 is a schematic structural diagram of a service flow offloading apparatus according to Embodiment 5 of the present invention;

10 is a schematic structural diagram of a service flow distribution device according to Embodiment 6 of the present invention;

FIG. 11 is a schematic structural diagram of a service flow offloading apparatus according to Embodiment 7 of the present invention;

FIG. 12 is a schematic structural diagram of a service flow offloading apparatus according to Embodiment 8 of the present invention;

FIG. 13 is a schematic structural diagram of a service flow offloading apparatus according to Embodiment 9 of the present invention;

FIG. 14 is a schematic structural diagram of a service flow offloading apparatus according to Embodiment 10 of the present invention.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The technical solution of the present invention can be applied to various communication systems of a wireless cellular network, for example: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access Wireless (WCDMA) system, general packet The present invention is not limited to the general packet radio service (GPRS) system, the Long Term Evolution (LTE) system, the Universal Mobile Telecommunications System (UMTS), and the like.

The embodiment of the present invention can be applied to the following scenario: the UE accesses the same PGW of 3GPP and non-3GPP through a PDN connection, and uses a General Packet Radio Service (GPRS) tunneling protocol (GPRS Tunneling Protocol). GTP). FIG. 1 is a schematic diagram of an LTE network architecture provided by the present invention. The core network side of the LTE system mainly includes: an MME, a Serving GPRS Support Node (SGSN), and a Packet Data Network Gateway (PGW). The Home Subscriber Server (HSS) and the Policy Control Rule Function (PCRF), where the MME is responsible for the Non-Access Stratum (NAS) signaling and NAS signaling. The encryption is performed to allocate a temporary identity to the user equipment, and the core network elements such as the S-GW and the P-GW are selected to provide functions such as roaming, tracking, and security, which correspond to the control plane part of the SGSN in the current UMTS system. The S-GW is a mobility anchor that switches between evolved Node Bases (eNBs) and provides lawful interception related functions. The P-GW is responsible for user address allocation, policy control, and enforcement of charging rules. And lawful interception related functions. The HSS is used to store subscription information of users, and the PCRF provides policy and charging control rules.

Generally, the non-3GPP network can be divided into a trusted non-3GPP network and an untrusted 3GPP network, wherein the trusted non-3GPP network accesses through the S2a interface with the P-GW; the non-trusted non-3GPP network passes the evolved packet data. The S2b interface between the gateway (evolved PDN, ePDN for short) and the P-GW is accessed. The ePDN is responsible for forwarding or allocating the mobile local Internet Protocol (IP) address of the user equipment, registering the local IP address of the user equipment, and binding the mobile IP address of the user equipment with the local IP address. When accessing from a non-3GPP network, there is also an important network element that is an authentication, authorization, and accounting (Authentication, Authorization, Accounting, AAA) server, which is implemented by interacting with the HSS. The authentication authorization operation is performed; the P-GW identification information used by each PDN connection established by the user equipment is registered in the HSS.

Certainly, when the current non-3GPP network accesses the 3GPP system core network, the trusted non-3GPP system or the non-trusted non-3GPP system can also be accessed through the S2c interface between the user equipment and the P-GW. At the same time, when the 3GPP system accesses, the user equipment can also establish a binding with the P-GW through the S2c interface.

The current 3GPP standard is developing a technology that enables a UE to simultaneously access a 3GPP network and a non-3GPP network through a network-based mobility protocol and using one PDN connection, but the data stream is independent of each other in the 3GPP network and the non-3GPP network transmission, when one of the networks When congestion occurs, the reliability of the communication system is reduced. In order to solve the technical problem, the embodiment of the present invention provides a service flow offloading method, where a user equipment can perform traffic splitting on a WLAN and a 3GPP side for a service flow of a certain PDN, and support the service flow in the two access types. Seamless switching between.

FIG. 2 is a flowchart of a service flow offloading method according to Embodiment 1 of the present invention. The method is implemented by: a PGW, where the method includes the following process:

S201: The gateway receives the second routing message sent by the second device, where the second routing message is the first routing message or the message that the second device updates the first routing message, where the first routing message is the first device according to the congestion message. Or a quintuple in the service flow, or a wireless local area network generated by the non-3GPP service set identifier SSID;

S202: The gateway offloads the third generation partner planned 3GPP network side service flow to the non-3GPP side according to the second routing message, or offloads the non-3GPP side service flow to the 3GPP network side.

The congestion message is used to indicate congestion of the 3GPP network side and the non-3GPP network side service flow based on the PDN connection of the same public service flow network PDN. The quintuple includes: source Internet protocol IP address, source port, destination IP address, destination port, and transport layer protocol number. The first routing message carries the routing message name, access type, service flow number, and filtering criteria.

Optionally, the first device is a user equipment UE, and the second device is a policy charging rule function PCRF server; or the first device is a policy charging rule function PCRF server, and the second device is User equipment UE.

Specifically, the first device is the user equipment UE, and the second device is the policy charging rule function PCRF server. The gateway is between the UE and the PCRF server, and the UE is based on the current congestion. The first routing message is generated by the situation or the quintuple of the data stream or other information in the data stream, where the first routing message carries the routing message name, the access type, the service flow number, and the filtering condition; The routing message may also carry the access type priority, the service flow priority, and the protocol forbidden item. The following is the format of the first routing message:

The access type may be 3GPP and non-3GPP, and the non-3GPP is usually a WLAN. The priority of the access type is X and Y respectively. Generally, the data traffic on the 3GPP network is large. Therefore, the priority of the X can be set. Below Y, when traffic congestion occurs on the 3GPP network, traffic can be offloaded to non-3GPP with high priority. In addition, the first routing message includes a filtering condition, where the filtering condition may be filtered according to the service flow quintuple: source IP, destination IP, source port number, destination port number, and transport layer protocol number, and the same service flow may be A plurality of filtering conditions are met. Therefore, when a service flow meets the filtering conditions corresponding to the message 2 and the filtering condition corresponding to the message 3, the access type corresponding to the message 2 and the access type corresponding to the message 3 may be used. The priority determines the access mode of the service flow. If the Y priority is higher than X, it can be determined that the access type of the service flow should be non-3GPP. Of course, there may be the following cases. The service flow that meets the same filter condition may be multiple. For example, service flow 1 and service flow 2 satisfy condition 1 at the same time. According to the number of service flow 1 and service flow 2, they may be determined to correspond. The service flow priority can be connected to the corresponding access type network according to the order of the traffic flow priorities from high to low. In addition, the protocol forbidden item in the first routing message may be 0 and 1. When the item is 0, the second device cannot update the first routing message. When the item is 1, the second device may The first routing message is updated. When the update is possible, the formed new message is the second routing message. Therefore, the format of the second routing message is similar to that of the first routing message, except that some parameters are updated. That is to say, the second routing message is a result of consistency negotiation between the first device and the second device.

Generally, since the 3GPP network side is prone to congestion, the first routing message and the first The role of the two routing messages should be to switch the traffic flow from the 3GPP network side to the non-3GPP network side as much as possible, and the first routing message and the second routing message should switch as many service flows as possible to one in one bearer at a time. On the 3GPP network side, the more traffic that is switched at one time, the less signaling is generated in 3GPP, and the more effective it is to alleviate 3GPP congestion.

Further, the foregoing second routing message further includes a default routing message name, a default access type, a default service flow number, and a default filtering condition.

Optionally, the gateway performs service flow splitting according to the second routing message, specifically: the gateway matches the service flow according to the filtering condition in the second routing message; if the matching succeeds, the service flow is offloaded to the access type corresponding to the filtering condition. If the matching fails, the service flow is offloaded to the network corresponding to the default access type, where the access type and the default access type include: the wireless local area network non-3GPP and the third generation partner plan 3GPP network.

Assuming that none of the second routing messages match traffic flow 1, then traffic flow 1 will use the default route message name, default access type, default traffic flow number, and default filter criteria. For example, if the default access type is non-3GPP, the service flow will be accessed by default on the non-3GPP network. This default access technology is consistent for all service flows, not just for a specific service flow. Can be used for business flows that do not match any of the filter criteria.

Optionally, if the first device is a policy charging rule function PCRF server and the second device is a user equipment UE, the gateway further sends a congestion message to the first device, so that the first device is configured according to the congestion message or the service flow. The first routing message is generated by the tuple, or the WLAN of the non-3GPP service set identifier (SSID). Therefore, the first routing message is not a static message, but the first device is based on the congestion message and the quintuple information. A dynamic message is generated, and it is assumed that the first device is a PCRF server. In the prior art, when the 3GPP core network is congested, each network element transmits an overload control message to each other in a process with GTP-C signaling. (Overload Control Information), but the message is not sent to the PCRF, so the PCRF cannot generate the first routing message according to the congestion message. The first routing message is equivalent to an initial basis of the traffic flow offload, that is, naturally not The subsequent dynamic flow of the service flow is performed according to the congestion message or the information of the quintuple.

An embodiment of the present invention provides a service flow offloading method, including: first, a gateway receives a second routing message sent by a second device, where the second routing message is a first routing message or is updated by the second device to the first routing message. Message, the first routing message is for the first device according to the congestion The first routing message carries the routing message name, the access type, the service flow number, and the filtering condition. The second routing message is generated by the quintuple in the service or the traffic stream or the non-3GPP service set identifier SSID. The routing message offloads the third generation partner planned 3GPP network side traffic to the non-3GPP side, or offloads the non-3GPP side traffic to the 3GPP network side. In summary, the gateway effectively offloads the service flow according to the second routing message negotiated by the first device and the second device, thereby improving the reliability of the communication network.

FIG. 3 is a flowchart of a service flow offloading method according to Embodiment 2 of the present invention. The method is performed by a first device, where the first device may be a user equipment UE or a policy charging rule function PCRF. Server, the method includes the following process:

S301: The first device acquires a congestion message, where the congestion message is used to indicate that congestion occurs on the 3GPP network side and the non-3GPP network side service flow of the third generation partner plan based on the same public service flow network PDN connection;

S302: The first device generates a first routing message.

S303: The first device sends the first routing message to the second device.

S304: The first device receives the second routing message sent by the second device by using the gateway, where the first routing message carries the routing message name, the access type, the service flow number, and the filtering condition, where the second routing message is the first routing message. Or the message that the second device updates the first routing message, and the second routing message is used for traffic splitting.

Optionally, when the first device is the user equipment UE, the second device is the policy charging rule function PCRF server; when the first device is the policy charging rule function PCRF server, the second device is the user equipment UE.

In one case, if the first device is the user equipment UE and the second device is the policy charging rule function PCRF server, the first device acquires the congestion message, which specifically includes: the first device acquiring the gateway or The congestion message sent by the second device; or the first device determines whether there is congestion on the network side, and obtains the congestion message according to the determination result. That is, the UE may obtain the congestion message in a display or implicit manner, and the congestion message may be: a Period of Validity and an Overload Reduction Metric, and the implicit congestion message may be sent by the UE according to the MME. The back_off timer or the UE determines that the 3GPP network is congested according to the network side's transmission access type control trend of the service flow. For example, a large number of service flows are transmitted through the non-3GPP network.

Generally, since the 3GPP network side is prone to congestion, the role of the first routing message and the second routing message should be to switch the traffic flow from the 3GPP network side to the non-3GPP network side as much as possible, and the first routing message and the first The two routing messages should switch as many service flows as possible to the non-3GPP network side at one time, because the more traffic flows that are switched at one time, the less signaling generated in 3GPP, and the more the 3GPP congestion is alleviated. effective.

After the UE obtains the congestion message, the UE generates a first routing message according to the congestion message, or the quintuple in the service flow, or the non-3GPP service set identifier SSID of the WLAN, where the quintuple includes: the source Internet Protocol IP address, the source Port, destination IP address, destination port, and transport layer protocol number. Certainly, the UE may also generate a first routing message according to other messages in the system. The method for generating the first routing message in this embodiment is not limited thereto.

Further, the UE can generate the first routing message immediately after learning the 3GPP network congestion message, and then initiate the switching of the currently existing service flow, or initiate the switching of the current existing service flow in the subsequent process.

After the UE generates the first routing message, the first routing message is sent to the PCRF through the session management process. The UE may send the first routing message by using the following message in the bearer modification process, for example, a WLAN Control Protocol (WLCP) network-based flow mobility (NB-IFOM) request (WLCP NB-IFOM Request), Bearer resource Command, IP-Connectivity Access Network (IP-CAN) Session-Adjustment Procedure (IP-CAN Session Modification Procedure) message will be the first routing message Sent to the PCRF. Of course, it can also be other session management processes, such as hosting a new bearer process.

Further, the UE receives the second routing message sent by the PCRF, and the second routing message is a result of the consistency negotiation between the UE and the PCRF, and the UE and the gateway may perform traffic offloading according to the second routing message.

Further, the UE may determine that the network congestion is released. For example, when the congestion message received by the UE is from the PCRF, the UE determines that the 3GPP network congestion is released once the Period of Validity timer overflows. When the UE implicitly determines the 3GPP network congestion according to the back_off timer sent by the MME, the UE should determine the 3GPP network congestion cancellation by using the back_off timer overflow. If the UE is based on the transmission access class of the service flow on the network side The type control trend (a large number of traffic flows through non-3GPP transmission) judges that the 3GPP network is congested, and the UE should also judge the 3GPP network congestion release according to the trend of the transmission access type of the service flow (that is, the 3GPP service traffic returns to normal). It should be noted that the UE determines that the 3GPP network congestion cancellation should not affect the original effect of the back_off timer.

In another case, if the first device is a policy charging rule function PCRF server and the second device is a user equipment UE, the first device acquires a congestion message, which includes: the first device acquiring a congestion message sent by the gateway . The congestion message may be: a Period of Validity and an Overload Reduction Metric, which are part of the Overload Control Information sent by the gateway to the first device, Period of Validity indicates the estimated duration of congestion. The Overload Reduction Metric can implicitly indicate the current level of network congestion. Therefore these two parameters can be passed to the PCRF as congestion reference information. It should be noted that if the network element where signaling congestion occurs is a P-GW, the method of the present invention is invalid, because even if the service flow is switched to the WLAN, the control plane data is still transmitted through the P-GW, and the congestion cannot be alleviated. Effect. It should be noted that, in this embodiment, the method for transmitting the foregoing congestion message to the PCRF by the present invention is not limited thereto.

After the PCRF obtains the congestion message, the PCRF generates a first routing message according to the congestion message, or the quintuple in the service flow, or the non-3GPP service set identifier SSID of the WLAN, where the quintuple includes: the source Internet Protocol IP address, the source Port, destination IP address, destination port, and transport layer protocol number. Certainly, the PCRF may also generate a first routing message according to other messages in the system. The method for generating the first routing message in the embodiment of the present invention is not limited thereto.

Further, the PCRF can generate the first routing message immediately after the 3GPP network congestion message is learned, and then initiate the switching of the currently existing service flow, or initiate the switching of the current existing service flow in the subsequent process.

After the PCRF generates the first routing message, the first routing message is sent to the UE through the session management process. The PCRF transmits the first routing message through an IP-CAN Session Modification Begin or Create/Update Bearer Request or WLCP NB-IFOM Request message. Give the UE. The UE may be simultaneously notified in the process of transmitting the first routing message, and the 3GPP is congested. The method for transmitting the first routing message in the embodiment of the present invention is not limited thereto. The first routing message can also be sent through other session distances.

Further, the PCRF receives the second routing message sent by the UE, and the second routing message is a result of the consistency negotiation between the UE and the PCRF, and the UE and the gateway may perform traffic distribution according to the second routing message.

Further, the PCRF can determine that the network congestion is released, and the PCRF saves the congestion message until the 3GPP network congestion is released (ie, the Period of Validity timer overflows), and maintains the policy trend of the subsequent second routing message, that is, because the 3GPP network side is easy to appear. Congestion, therefore, the role of the second routing message should be to switch the traffic flow from the 3GPP network side to the non-3GPP network side as much as possible, and the second routing message should switch as many service flows as possible to one in one bearer at a time. On the 3GPP network side, the more traffic that is switched at one time, the less signaling is generated in 3GPP, and the more effective it is to alleviate 3GPP congestion. If the network congestion is removed (ie, the Period of Validity timer overflows), the PCRF will resume normal operation, that is, the congestion message stored by the PCRF is cleared, and the first routing message generated by the PCRF no longer tends to transmit the service flow through the non-3GPP side.

An embodiment of the present invention provides a service flow offloading method, including: first, a first device acquires a congestion message, where the congestion message is used to indicate a third generation partner plan 3GPP network side and a non-3GPP network based on a PDN connection of the same public service flow network Congestion of the side traffic flow; secondly, the first device generates a first routing message, and sends the first routing message to the second device; then, the first device receives the second routing message sent by the second device by using the gateway; A routing message carries a routing message name, an access type, a service flow number, and a filtering condition. The second routing message is a first routing message or a message that is updated by the second device to the first routing message, and the second routing message is used for the service. Streaming. In summary, the first device generates a first routing message, and finally obtains a second routing message by negotiating with the second device, so that the gateway can effectively offload the service flow according to the second routing message, thereby improving the reliability of the communication network.

FIG. 4 is a flowchart of a service flow offloading method according to Embodiment 3 of the present invention, where the executor of the method is a second device, where the second device may be a user equipment UE or a policy charging rule function. PCRF server, the method includes the following process:

S401: The second device receives the first routing message sent by the first device, where the first routing message is generated by the first device according to the congestion message or the quintuple in the service flow, or the non-3GPP service set identifier SSID of the WLAN;

S402: The second device sends a second routing message to the gateway, so that the gateway cancels according to the second route. The service flow is offloaded, and the second routing message is the first routing message or the message that the second device updates the first routing message.

The congestion message is used to indicate congestion caused by a third generation partner plan 3GPP network side and a non-3GPP network side service flow based on the same public service flow network PDN connection, where the quintuple includes: source Internet Protocol IP address, source The port, the destination IP address, the destination port, and the transport layer protocol number, the first routing message carrying the routing message name, the access type, the service flow number, and the filtering condition.

The above S401 and S402 are substantially the process of consistency negotiation performed by the first device and the second device.

Optionally, the first routing message further includes: a protocol barring item;

The second device determines, according to the protocol barring item, whether to update the first routing message.

Specifically, the second device may be a user equipment UE, or may be a policy charging rule function PCRF server, and the method may be divided into two cases:

In one case, if the second device is the policy charging rule function PCRF server, and the first device is the user equipment UE, the PCRF determines whether to update the first routing message according to the protocol barring item in the received first routing message, where The protocol forbidden item in a routing message may be 0 and 1. When the item is 0, it indicates that the second device cannot update the first routing message. When the item is 1, it indicates that the second device can use the first route. The message is updated. When it can be updated, the new message formed is the second routing message. Therefore, the format of the second routing message is similar to that of the first routing message, except that some parameters are updated. That is to say, the second routing message is a result of consistency negotiation between the first device and the second device. The PCRF may transmit the second routing message to the UE by using the following message, such as: Update Bearer Request, Update Bearer Response, and WLCP NB-IFOM Response (WLCP NB-IFOM Response) message will be second. The routing message is fed back to the UE.

In another case, if the second device is the user equipment UE and the first device is the policy charging rule function PCRF server, the UE determines whether to update the first routing message according to the protocol barring item in the received first routing message, where The protocol forbidden item in the first routing message may be 0 and 1. When the item is 0, the second device cannot update the first routing message. When the item is 1, the second device may be the first. The routing message is updated. When it can be updated, the new message formed is the second routing message. Where the UE will respond via WLCP NB-IFOM (WLCP NB-IFOM Response), the Create/Update Bearer Response and the IP-CAN Session Modification End message feed back the second routing message to the gateway and the first device. This completes the consistency negotiation with the first device. Therefore, the same routing rule can be adopted on the terminal side and the network side, that is, the service flow is offloaded according to the information in the second routing message.

The present invention provides a service flow offloading method, where the method includes: the second device receives the first routing message sent by the first device, where the first routing message is a quintuple in the congestion message or the service flow of the first device, or The WLAN is generated by the non-3GPP service set identifier SSID; the second device sends a second routing message to the gateway, so that the gateway performs traffic splitting according to the second routing message, and the second routing message is the first routing message or the second The message that the device updates the first routing message. In summary, the second device obtains the second routing message according to the first routing message, so that the gateway can effectively offload the service flow according to the second routing message, thereby improving the reliability of the communication network.

The following describes the transmission process of the congestion message, the first routing message, and the second routing message in different session flows:

FIG. 5 is a flowchart of a new private bearer according to Embodiment 4 of the present invention, where the bearer process has the following steps:

S501: The PCRF sends an IP-CAN Session Modification (IP-CAN Session Modification) message to the PGW.

S502: The PGW sends a Create Bearer Request message to the SGW.

S503: The SGW sends a Create Bearer Request message to the MME.

S504: The MME sends a Bearer Setup Response message or a Session Management Request message to the eNodeB.

S505: The eNodeB sends an RRC Connection Reconfiguration message to the UE.

S506: The UE sends an RRC Connection Reconfiguration Complete message to the eNodeB.

S507: The eNodeB sends a Bearer Setup Response message to the MME.

S508: The UE sends a Direct Transfer message to the eNodeB.

S509: The eNodeB sends a session management response (Session Management Response) message to the MME.

S510: The MME sends a Create Bearer Response message to the SGW.

S511: The SGW sends a Create Bearer Response message to the PGW.

S512: The PGW sends an IP-CAN Session Modification (IP-CAN Session Modification) message to the PCRF.

In the above-mentioned proprietary bearer new process, the PCRF is the first device described in the embodiment of the present invention, wherein the PGW can send a congestion message to the PCRF through the IP-CAN Session Modification (IP-CAN Session Modification) message in the S512, where The congestion message can be: Period of Validity and Overload Reduction Metric, that is, the IP-CAN Session Modification message in S512 carries these two parameters, which will cause congestion. The message can be passed to the PCRF as a congestion reference.

FIG. 6 is a flowchart of a UE initiated service request according to Embodiment 4 of the present invention, which has the following steps:

S601: The UE sends a Service Request message to the eNodeB.

S602: The eNodeB sends a service request (Service Request) message to the MME.

S603: Establish an Security Authentication message between the UE and the MME, and between the MME and the HSS.

S604: The MME sends an initial context setup request (Initial Context Setup Request) message to the eNodeB.

S605: The UE sends a Radio Bearer Establishment message to the eNodeB.

S606: The UE sends an uplink data (Uplink Data) message to the PGW via the eNodeB and the SGW.

S607: The eNodeB sends an initial context setup complete (Initial Context Setup Complete) message to the MME.

S608: The MME sends a Modify Bearer Eequest message to the SGW.

S609: The SGW sends a Modify Bearer Eequest message to the PGW.

S610: The PCRF sends an IP connection access network session adjustment (IP-CAN Session Modification) message to the PGW.

S611: The PGW sends a Modify Bearer Response message to the SGW.

S612: The SGW sends a Modify Bearer Response message to the MME.

In the above-mentioned UE-initiated service request process, the PCRF is the first device described in the embodiment of the present invention, wherein the PGW can send a congestion message to the PCRF through the IP-CAN Session Modification (IP-CAN Session Modification) message in the S610, where The congestion message can be: Period of Validity and Overload Reduction Metric, that is, the IP-CAN Session Modification message in S610 carries these two parameters, which will cause congestion. The message can be passed to the PCRF as a congestion reference.

The flow shown in FIG. 5 and FIG. 6 only gives two examples of the PGW sending a congestion message to the PCRF. Of course, the congestion message may be sent to the PCRF through other session flows, which is not limited in this embodiment of the present invention.

FIG. 7 is a flowchart 1 of a service flow switching initiated by a PCRF according to Embodiment 4 of the present invention, which specifically includes the following processes:

S701: establishing, by the UE, a connection with a third generation partner plan 3GPP network and a non-3GPP network connected based on the same public service flow network PDN;

S702: The hPCRF sends an IP-CAN Session Modification Begin message to the PGW.

S703: The PGW sends a Create/Update Bearer Request message to the Trusted Wireless Local Area Networks Access Network (TWAN).

S704: The TWAN sends a WLCP NB-IFOM request to the UE (WLCP NB-IFOM) Request) message;

S705: The UE sends a WLCP NB-IFOM Response (WLCP NB-IFOM Response) message to the TWAN.

S706: The TWAN sends a Create/Update Bearer Response message to the PGW.

S707: The PGW sends an IP-CAN Session Modification End (IP-CAN Session Modification End) message to the hPCRF.

S708: A 3GPP access bearer modification or cancellation is established between the UE and the hPCRF.

In the above process, the hPCRF is equivalent to the first device in the present invention, and the UE is the second device. After the hPCRF generates the first routing message, the first routing message is accessed through the IP connection to access the network session (IP-CAN Session). The Modification Begin) or Create/Update Bearer Request or WLCP NB-IFOM Request message conveys the first routing message to the UE. The UE will use the WLCP NB-IFOM Response, the Create/Update Bearer Response and the IP-CAN Session Modification End message to send the second routing message. Feedback to the first device.

FIG. 8 is a flowchart 2 of a service flow switching initiated by a PCRF according to Embodiment 4 of the present invention, which specifically includes the following processes:

S801: Establish a connection between the UE and a third-generation partner plan 3GPP network and a non-3GPP network connected according to the same public service flow network PDN;

S802: The UE sends a WLCP NB-IFOM Request (WLCP NB-IFOM Request) message to the TWAN.

S803: The TWAN sends a bearer resource command to the PGW.

S804: establishing an IP-Connectivity Access Network (IP-CAN Session Modification Procedure) between the PGW and the hPCRF;

S805: The PGW sends an Update Bearer Request to the TWAN.

S806: The TWAN sends an update bearer response to the PGW.

S807: TWAN sends WLCP NB-IFOM response to the UE (WLCP NB-IFOM Response) message;

S808: Establish a non-3GPP specific resource modification (Non-3GPP Specific Resource Modification) message between the UE and the TWAN.

S809: A 3GPP evolved Evolved Packet System (EPS) resource release or modification is established between the UE and the HSS/AAA.

In the above process, where the UE is equivalent to the first device in the present invention, and the hPCRF is the second device, the first routing message generated by the UE passes the (WLCP NB-IFOM Request) message, the bearer resource command (Bearer resource Command), and The IP-CAN Session Modification Procedure is sent to the hPCRF, and then the hPCRF feeds back the second routing message to the UE by using an Update Bearer Request and a WLCP NB-IFOM Response message.

In summary, the service flow offloading method provided by the embodiment of the present invention includes: the first device generates a first routing message, and then sends the first routing message to the second device, where the second device determines to obtain the second routing message according to the first routing message, The UE and the gateway finally perform traffic splitting according to the second routing message. The first routing message and the second routing message consider the congestion message or the useful information in the service flow, so that the service flow distribution is more effective and reasonable, thereby ensuring the reliability of the communication system.

FIG. 9 is a schematic structural diagram of a service flow offloading apparatus according to Embodiment 5 of the present invention, wherein the service flow splitting apparatus is a gateway, and the receiving module 901 is configured to receive a second routing message sent by the second device, where The second routing message is a first routing message or a message that is updated by the second device to the first routing message, where the first routing message is a quintuple of the first device according to the congestion message or the service flow. Or the wireless local area network is generated by the service set identifier SSID of the non-3GPP; the processing device 902 is configured to offload the third generation partner plan 3GPP network side service flow to the non-3GPP side according to the second routing message, or send the non-3GPP side service flow Offloading to the 3GPP network side; wherein the congestion message is used to indicate congestion caused by the third generation partner plan 3GPP network side and the non-3GPP network side service flow based on the same public service flow network PDN connection, the quintuple including: source The Internet Protocol IP address, the source port, the destination IP address, the destination port, and the transport layer protocol number, where the first routing message carries the routing message name and the access type. , service flow number and filter conditions.

Optionally, the second routing message further includes a default routing message name, a default access type, The default business stream number and default filter criteria.

The processing module 902 is specifically configured to: match the service flow according to the filtering condition in the second routing message; if the matching is successful, the service flow is offloaded to the network of the access type corresponding to the filtering condition; If the matching fails, the service flow is offloaded to the network corresponding to the default access type, where the access type and the default access type include: a wireless local area network non-3GPP and a third generation partnership plan 3GPP network.

If the first device is a policy charging rule function PCRF server, and the second device is a user equipment UE, the gateway further includes: a sending module 903, configured to send the congestion message to the first device.

The service flow offloading device of this embodiment may be used to implement the technical solution of the method embodiment shown in FIG. 2, and the implementation principle and the technical effect are similar, and details are not described herein again.

10 is a schematic structural diagram of a service flow offloading apparatus according to Embodiment 6 of the present invention. The apparatus is equivalent to the first device in the present invention, and includes: an obtaining module 1001, configured to acquire a congestion message, where the congestion message is used. The generating module 1002 is configured to generate a first routing message, and the sending module 1003 is configured to use the third-generation partner plan based on the same public service flow network PDN connection to generate congestion on the 3GPP network side and the non-3GPP network side service flow. The first routing message is sent to the second device, and the receiving module 1004 is configured to receive the second routing message sent by the second device by using the gateway, where the first routing message carries the routing message name, access type, and service flow. The number and the filtering condition, the second routing message is the first routing message or the message that the second device updates the first routing message, and the second routing message is used for service flow offloading.

Optionally, the service flow offloading device is a user equipment UE, and the second device is a policy charging rule function PCRF server; or the service flow offloading device is a policy charging rule function PCRF server, the second The device is a user equipment UE.

Further, if the service flow offloading device is a user equipment UE and the second device is a policy charging rule function PCRF server, the acquiring module 1001 is specifically configured to: acquire the sent by the gateway or the second device Congestion message; or, to determine whether there is congestion on the network side, Obtaining the congestion message according to the judgment result.

The device further includes: a processing module 1005, configured to perform traffic splitting according to the second routing message.

If the service flow offloading device is a policy charging rule function PCRF server, and the second device is a user equipment UE, the acquiring module 1001 is specifically configured to: obtain a congestion message sent by the gateway.

Optionally, the generating module 1002 is specifically configured to: generate the first routing message according to the congestion message, or a quintuple in a service flow, or a service set identifier SSID of a non-3GPP of a wireless local area network, where The quintuple includes: source Internet Protocol IP address, source port, destination IP address, destination port, and transport layer protocol number.

The service flow offloading device of this embodiment may be used to implement the technical solution of the method embodiment shown in FIG. 3, and the implementation principle and the technical effect are similar, and details are not described herein again.

FIG. 11 is a schematic structural diagram of a service flow offloading apparatus according to Embodiment 7 of the present invention. The apparatus is equivalent to the second device in the present invention, and includes: a receiving module 1101, configured to receive a first route sent by the first device. The first routing message is generated by the first device according to a congestion message or a quintuple in the service flow, or a service set identifier SSID of the non-3GPP of the WLAN; the sending module 1102 is configured to send the first to the gateway. And routing the message, so that the gateway performs traffic distribution according to the second routing message, where the second routing message is the first routing message or after the second device updates the first routing message. The message is used to indicate congestion caused by a third generation partner plan 3GPP network side and a non-3GPP network side service flow based on the same public service flow network PDN connection, the quintuple comprising: source internet protocol IP An address, a source port, a destination IP address, a destination port, and a transport layer protocol number, where the first routing message carries a routing message name, an access type, and a service flow number. Filter criteria.

Optionally, the first routing message further includes: a protocol forbidden item; the service flow offloading device further includes: a determining module 1103; configured to determine, according to the protocol barring item, whether to update the first routing message.

The service flow offloading device of this embodiment may be used to implement the technical solution of the method embodiment shown in FIG. 4, and the implementation principle and the technical effect are similar, and details are not described herein again.

FIG. 12 is a schematic structural diagram of a service flow offloading apparatus according to Embodiment 8 of the present invention, The device is a gateway, and includes: a receiver 1201, configured to receive a second routing message sent by the second device, where the second routing message is a first routing message or the first routing message is sent by the second device The updated message, the first routing message is generated by the first device according to a congestion message or a quintuple in the service flow, or a non-3GPP service set identifier SSID of the wireless local area network; the processor 1202 is configured to The routing message offloads the third generation partner plan 3GPP network side service flow to the non-3GPP side, or offloads the non-3GPP side service flow to the 3GPP network side; wherein the congestion message is used to indicate the PDN connection based on the same public service flow network Three generations of partners plan congestion of 3GPP network side and non-3GPP network side traffic flows, the quintuple includes: source Internet Protocol IP address, source port, destination IP address, destination port, and transport layer protocol number, said A routing message carries the routing message name, access type, service flow number, and filtering conditions.

Optionally, the second routing message further includes a default routing message name, a default access type, a default service flow number, and a default filtering condition.

Optionally, the processor 1202 is configured to: according to the filtering condition in the second routing message, match the service flow; if the matching succeeds, the service flow is offloaded to the access type corresponding to the filtering condition. If the matching fails, the service flow is offloaded to the network corresponding to the default access type, where the access type and the default access type include: a wireless local area network non-3GPP and a Three generation partners plan the 3GPP network.

The first device is a user equipment UE, and the second device is a policy charging rule function PCRF server; or the first device is a policy charging rule function PCRF server, and the second device is a user equipment. UE.

Further, if the first device is a policy charging rule function PCRF server, and the second device is a user equipment UE, the gateway further includes: a sender 1203, configured to send the Congestion message.

FIG. 13 is a schematic structural diagram of a service flow offloading apparatus according to Embodiment 9 of the present invention, including: a processor 1301, configured to acquire a congestion message, where the congestion message is used to indicate a third connection based on a PDN connection of the same public service flow network On behalf of the partner, the 3GPP network side and the non-3GPP network side traffic flow are congested; the processor 1301 is further configured to generate a first routing message; the transmitter The first routing message is sent to the second device, and the receiver 1303 is configured to receive the second routing message sent by the second device by using the gateway, where the first routing message carries the routing message name, An access type, a service flow number, and a filter condition, where the second routing message is the first routing message or a message that is updated by the second device to the first routing message, where the second routing message is used Diverted from the business flow.

Further, if the service flow offloading device is a user equipment UE and the second device is a policy charging rule function PCRF server, the processor 1301 is specifically configured to: acquire the sent by the gateway or the second device Congestion message; or, determining whether there is congestion on the network side, and acquiring the congestion message according to the judgment result. The processor 1301 is configured to perform traffic splitting according to the second routing message.

If the service flow offloading device is a policy charging rule function PCRF server, and the second device is a user equipment UE, the processor 1301 is specifically configured to: obtain a congestion message sent by the gateway.

Optionally, the processor 1301 is configured to: generate the first routing message according to the congestion message, or a quintuple in a service flow, or a non-3GPP service set identifier SSID of a wireless local area network, where The quintuple includes: source Internet Protocol IP address, source port, destination IP address, destination port, and transport layer protocol number.

FIG. 14 is a schematic structural diagram of a service flow offloading apparatus according to Embodiment 10 of the present invention, including: a receiver 1401, configured to receive a first routing message sent by a first device, where the first routing message is the first The device generates the second routing message according to the congestion message or the quintuple in the service flow or the non-3GPP service set identifier SSID of the WLAN; the sender 1402 is configured to send the second routing message to the gateway, so that the gateway is configured according to the And the second routing message is the first routing message or the message that is updated by the second device to the first routing message, where the congestion message is used to indicate that the same is based on the same The third generation partner program of the public service flow network PDN connection appears on the 3GPP network side and the non-3GPP network side service flow Congestion, the quintuple includes: a source Internet Protocol IP address, a source port, a destination IP address, a destination port, and a transport layer protocol number, the first routing message carrying a routing message name, an access type, and a service flow number. And filter conditions.

Optionally, the first routing message further includes: a protocol barring item; the service flow offloading device further includes: a processor 1403; configured to determine, according to the protocol barring item, whether to update the first routing message.

The service flow offloading device of this embodiment may be used to implement the technical solution of the method embodiment shown in FIG. 5, and the implementation principle and the technical effect are similar, and details are not described herein again.

One of ordinary skill in the art will appreciate that all or part of the steps to implement the various method embodiments described above may be accomplished by hardware associated with the program instructions. The aforementioned program can be stored in a computer readable storage medium. The program, when executed, performs the steps including the foregoing method embodiments; and the foregoing storage medium includes various media that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Finally, it should be noted that the above embodiments are merely illustrative of the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that The technical solutions described in the foregoing embodiments may be modified, or some or all of the technical features may be equivalently replaced; and the modifications or substitutions do not deviate from the technical solutions of the embodiments of the present invention. range.

Claims

A service flow offloading method, comprising:

The gateway receives the second routing message sent by the second device, where the second routing message is a first routing message or a message that is updated by the second device to the first routing message, where the first routing message is The first device is generated according to a congestion message or a quintuple in the service flow, or a non-3GPP service set identifier SSID of the WLAN;

The gateway, according to the second routing message, offloads the third generation partner planned 3GPP network side service flow to the non-3GPP side, or offloads the non-3GPP side service flow to the 3GPP network side;

The congestion message is used to indicate congestion caused by a third generation partner plan 3GPP network side and a non-3GPP network side service flow based on the same public service flow network PDN connection, where the quintuple includes: source Internet Protocol IP address, source The port, the destination IP address, the destination port, and the transport layer protocol number, the first routing message carrying the routing message name, the access type, the service flow number, and the filtering condition.
The method according to claim 1, wherein the second routing message further comprises a default routing message name, a default access type, a default traffic stream number, and a default filtering condition.
The method according to claim 2, wherein the gateway performs traffic distribution according to the second routing message, specifically:

The gateway matches the service flow according to the filtering condition in the second routing message;

If the matching is successful, the service flow is offloaded to the network of the access type corresponding to the filtering condition;

If the matching fails, the service flow is offloaded to the network corresponding to the default access type, where the access type and the default access type include: a wireless local area network non-3GPP and a third generation partnership plan 3GPP network.
The method according to any one of claims 1-3, wherein the first device is a user equipment UE, and the second device is a policy charging rule function PCRF server; or

The first device is a policy charging rule function PCRF server, and the second device is a user equipment UE.
The method of claim 4, further comprising:

If the first device is a policy charging rule function PCRF server and the second device is a user equipment UE, the gateway further sends the congestion message to the first device.
A service flow offloading method, comprising:

The first device acquires a congestion message, where the congestion message is used to indicate congestion caused by the third generation partner plan 3GPP network side and the non-3GPP network side service flow based on the same public service flow network PDN connection;

The first device generates a first routing message;

Sending, by the first device, the first routing message to a second device;

Receiving, by the first device, a second routing message sent by the second device by using a gateway;

The first routing message carries a routing message name, an access type, a service flow number, and a filtering condition, where the second routing message is the first routing message or the second routing device is the first routing message. The updated message, the second routing message is used for traffic splitting.
The method according to claim 6, wherein the first device is a user equipment UE, and the second device is a policy charging rule function PCRF server; or

The first device is a policy charging rule function PCRF server, and the second device is a user equipment UE.
The method according to claim 7, wherein if the first device is a user equipment UE and the second device is a policy charging rule function PCRF server, the first device acquires a congestion message, which specifically includes:

Obtaining, by the first device, a congestion message sent by the gateway or the second device; or

The first device determines whether there is congestion on the network side, and obtains the congestion message according to the determination result.
The method according to claim 8, further comprising: the first device performing traffic splitting according to the second routing message.
The method according to claim 7, wherein if the first device is a policy charging rule function PCRF server and the second device is a user equipment UE, the first device acquires a congestion message, specifically including :

The first device acquires a congestion message sent by the gateway.
The method according to any one of claims 6 to 10, wherein the generating, by the first device, the first routing message comprises:

The first device according to the congestion message, or a quintuple in a service flow, or wireless The local area network non-3GPP service set identifier SSID generates the first routing message, where the quintuple includes: a source Internet Protocol IP address, a source port, a destination IP address, a destination port, and a transport layer protocol number.
A service flow offloading method, comprising:

The second device receives the first routing message sent by the first device, where the first routing message is generated by the first device according to a congestion message or a quintuple in the service flow, or a non-3GPP service set identifier SSID of the WLAN of;

The second device sends a second routing message to the gateway, so that the gateway performs traffic distribution according to the second routing message, where the second routing message is the first routing message or is the second device. The updated message of the first routing message;

The congestion message is used to indicate congestion caused by a third generation partner plan 3GPP network side and a non-3GPP network side service flow based on the same public service flow network PDN connection, where the quintuple includes: source Internet Protocol IP address, source The port, the destination IP address, the destination port, and the transport layer protocol number, the first routing message carrying the routing message name, the access type, the service flow number, and the filtering condition.
The method according to claim 12, wherein the first routing message further includes: a protocol barring item;

The second device determines, according to the protocol barring item, whether to update the first routing message.
A service flow distribution device, comprising:

a receiving module, configured to receive a second routing message sent by the second device, where the second routing message is a first routing message or a message that is updated by the second device to the first routing message, where A routing message is generated by the first device according to a congestion message or a quintuple in the service flow, or a non-3GPP service set identifier SSID of the WLAN;

The processing device is configured to offload the third generation partner plan 3GPP network side service flow to the non-3GPP side according to the second routing message, or offload the non-3GPP side service flow to the 3GPP network side;

The congestion message is used to indicate congestion caused by a third generation partner plan 3GPP network side and a non-3GPP network side service flow based on the same public service flow network PDN connection, where the quintuple includes: source Internet Protocol IP address, source The port, the destination IP address, the destination port, and the transport layer protocol number, the first routing message carrying the routing message name, the access type, the service flow number, and the filtering condition.
The apparatus according to claim 14, wherein the second routing message further comprises a default routing message name, a default access type, a default traffic stream number, and a default filtering condition.
The device according to claim 15, wherein the processing module is specifically configured to:

Matching the service flow according to the filtering condition in the second routing message;

If the matching is successful, the service flow is offloaded to the network of the access type corresponding to the filtering condition;

If the matching fails, the service flow is offloaded to the network corresponding to the default access type, where the access type and the default access type include: a wireless local area network non-3GPP and a third generation partnership plan 3GPP network.
The device according to any one of claims 14-16, wherein the first device is a user equipment UE, and the second device is a policy charging rule function PCRF server; or

The first device is a policy charging rule function PCRF server, and the second device is a user equipment UE.
The device of claim 17 wherein:

If the first device is a policy charging rule function PCRF server, and the second device is a user equipment UE, the gateway further includes:

And a sending module, configured to send the congestion message to the first device.
A service flow distribution device, comprising:

An obtaining module, configured to acquire a congestion message, where the congestion message is used to indicate congestion caused by a third generation partner plan 3GPP network side and a non-3GPP network side service flow based on the same public service flow network PDN connection;

Generating a module, configured to generate a first routing message;

a sending module, configured to send the first routing message to the second device;

a receiving module, configured to receive a second routing message sent by the second device by using a gateway;

The first routing message carries a routing message name, an access type, a service flow number, and a filtering condition, where the second routing message is the first routing message or the second routing device is the first routing message. The updated message, the second routing message is used for traffic splitting.
The device according to claim 19, wherein the service flow offloading device is a user equipment UE, and the second device is a policy charging rule function PCRF server; or

The service flow offloading device is a policy charging rule function PCRF server, and the second device is a user equipment UE.
The device according to claim 20, wherein if the service flow offloading device is a user equipment UE and the second device is a policy charging rule function PCRF server, the obtaining module is specifically configured to:

Obtaining a congestion message sent by the gateway or the second device; or

The network side is determined to be congested, and the congestion message is obtained according to the judgment result.
The device according to claim 21, further comprising: a processing module, configured to perform traffic splitting according to the second routing message.
The device according to claim 20, wherein, if the service flow offloading device is a policy charging rule function PCRF server, and the second device is a user equipment UE, the acquiring module is specifically configured to: obtain Congestion message sent by the gateway.
The device according to any one of claims 19 to 23, wherein the generating module is specifically configured to:

Generating the first routing message according to the congestion message, or a quintuple in a service flow, or a service set identifier SSID of a wireless local area network non-3GPP, where the quintuple includes: a source Internet Protocol IP address, a source port , destination IP address, destination port, and transport layer protocol number.
A service flow distribution device, comprising:

a receiving module, configured to receive a first routing message sent by the first device, where the first routing message is a quintuple of the first device according to a congestion message or a service flow, or a service set identifier of a non-3GPP wireless local area network Generated by SSID;

a sending module, configured to send a second routing message to the gateway, so that the gateway performs traffic distribution according to the second routing message, where the second routing message is the first routing message or is the second device The updated message of the first routing message;

The congestion message is used to indicate congestion caused by a third generation partner plan 3GPP network side and a non-3GPP network side service flow based on the same public service flow network PDN connection, the five yuan The group includes: a source Internet Protocol IP address, a source port, a destination IP address, a destination port, and a transport layer protocol number, and the first routing message carries a routing message name, an access type, a service flow number, and a filtering condition.
The device according to claim 25, wherein the first routing message further comprises: a protocol barring item;

The service flow offloading device further includes: a determining module;

The determining module is configured to determine, according to the protocol barring item, whether to update the first routing message.