CN102918885B - Method, system and related device for implementing service data stream offload - Google Patents

Abstract

The embodiment of the invention discloses a method, a system and a related device for realizing business data stream distribution. One of the offloading methods includes: when establishing or modifying the IP connection access network IP-CAN bearer, the mobile network management entity receives the bearer message containing the offload flag sent by the mobile network gateway, and the mobile network gateway learns the access of each service data flow type, when it is determined according to the access type of each service data flow that the access type of the service data flow transmitted on any IP-CAN bearer is offload access, the offload flag in the bearer message indicates that the offload access on the bearer The access type of the service data flow transmitted on the uplink is offloading access, and the access type includes offloading access and non-offloading access; the mobile network management entity sends a bearer message containing an offloading flag to the base station, so that the base station follows the The indication of the offloading flag is to offload the service data flow transmitted on the bearer. According to the embodiment of the present invention, a flow level based IP data offloading solution can be provided.

Description

A method, system, and related device for realizing business data stream offloading

technical field

The present invention relates to the technical field of mobile communication, in particular to a method, system and related device for realizing business data stream distribution.

Background technique

Local IP Access (LIPA) technology and IP data offload (Selected IP Traffic Offload, SIPTO) technology were originally proposed based on the Home Base Station (Home enhanced NodeB, HeNB) network, which means that the user's business data flow directly from The HeNB is connected to the packet data network without going through the operator's core network. Compared with the operator's core network, since this part of the service data flow is directly diverted from the HeNB, the load and transmission of the core network are reduced. cost.

With the development of wireless access technology, data transmission is transmitted at a higher rate, and the increase in the number of users and the increase in user data transmission rate have put forward higher requirements on the performance of network elements of the core network. The industry believes that this kind of IP data offloading can not only be applied to the HeNB network, but also can be implemented on the macro network, that is, specific IP service data streams are offloaded from the wireless side to save transmission resources. Therefore, an IP data distribution technology based on a macro network is also proposed, with the purpose of selecting a better path for IP traffic.

Although the offloading of IP service data in the prior art can reduce the load and transmission cost of the core network, when the service data flow is directly connected to the packet data network from the HeNB or eNB, the security and stability of the access process are poor. Sometimes, in order to meet the special requirements of some applications, IP data distribution based on the flow level is required. The so-called stream-level IP data offloading is to offload a part of the service data stream, so that this part of the service data stream is directly connected to the packet data network from the HeNB or eNB, and the other part of the service data stream still needs to be connected to the packet data network through the core network. in packet data networks. At present, there is no flow-level IP data distribution solution.

Contents of the invention

Embodiments of the present invention provide a method, system and related device for realizing service data stream offloading, so as to provide a flow level-based IP data offloading solution.

The invention discloses the following technical solutions:

A method for realizing business data flow offloading, comprising:

When establishing or modifying the IP connection access network IP-CAN bearer, the mobile network gateway learns the access type of each service data flow, and the access type includes split access and non-distributed access;

When the mobile network gateway determines that the access type of the service data stream transmitted on any IP-CAN bearer is split access according to the access type of each service data stream, it sends a bearer message that includes a split flag, so that the receiving The network entity that bears the message and performs the data offloading operation offloads the service data stream transmitted on the bearer according to the indication of the offloading flag, and the offloading flag indicates the access of the service data stream transmitted on the bearer The type is split access.

A system for realizing business data flow offloading, including: a mobile network gateway and a network entity performing data offloading operations, wherein,

The mobile network gateway is used to know the access type of each service data flow when establishing or modifying the IP-CAN bearer, and determine the service transmitted on any IP-CAN bearer according to the access type of each service data flow When the access type of the data stream is offload access, sending a bearer message including an offload flag, indicating that the access type of the service data stream transmitted on the bearer is offload access through the offload flag in the bearer message, The access type includes split access and non-split access;

The network entity performing the data offloading operation is configured to receive the bearer message, and offload the service data flow transmitted on the bearer according to the indication of the offload flag.

A mobile network management entity comprising:

The first receiving unit is configured to receive the bearer message containing the offload flag sent by the mobile network gateway when establishing or modifying the IP connection to access the network IP-CAN bearer, wherein the bearer message containing the offload flag is known by the mobile network gateway The access type of each service data flow, and according to the access type of each service data flow, it is determined that the access type of the service data flow transmitted on any IP-CAN bearer is sent after split access, and the access type Including offload access and non-offload access, the offload flag indicates that the access type of the service data flow transmitted on the bearer is offload access;

The first sending unit is configured to send a bearer message including an offload flag to the base station, so that the base station offloads the service data flow transmitted on the bearer according to the instruction of the offload flag.

A mobile network gateway comprising:

The learning unit is used to learn the access type of each service data flow when establishing or modifying the IP connection access network IP-CAN bearer, and the access type includes split access and non-distributed access;

The second sending unit is used to send the mobile network management entity to the mobile network management entity when the access type of the service data flow transmitted on any IP-CAN bearer is determined to be offload access according to the access type of each service data flow. The bearer message, using the offload flag in the bearer message to indicate that the access type of the service data flow transmitted on the bearer is offload access, so that the mobile network management entity sends the bearer message including the offload flag to the base station, so that The base station offloads the service data flow transmitted on the bearer according to the indication of the offload flag.

It can be seen from the above embodiments that the offload policy indicates the access types of various service data flows, and the access types include offload access and non-offload access, and the PGW or GGSN knows the access of each service data flow according to the offload policy. The base station notifies the base station of the access type of the service data flow transmitted on a certain bearer. If the access type is offload access, the base station performs offload processing on the current service data flow according to the instruction of the access type.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without creative work.

Fig. 1 is a flow chart of an embodiment of a method for realizing business data stream distribution in the present invention;

Fig. 2 is a flow chart of another embodiment of a method for realizing business data stream distribution in the present invention;

FIG. 3 is a signaling flow chart of an embodiment of a method for realizing service data stream distribution in the present invention;

FIG. 4 is another signaling flow chart of an embodiment of a method for realizing service data stream offloading according to the present invention;

FIG. 5 is another signaling flow chart of an embodiment of a method for realizing service data stream offloading according to the present invention;

FIG. 6 is a flow chart of another embodiment of a method for realizing business data stream distribution in the present invention;

FIG. 7 is a signaling flow chart of another embodiment of a method for realizing service data stream offloading according to the present invention;

FIG. 8 is another signaling flow chart of another embodiment of a method for realizing service data stream offloading according to the present invention;

FIG. 9 is a structural diagram of an embodiment of a system for realizing business data stream distribution in the present invention;

FIG. 10 is a structural diagram of an embodiment of a mobile network management entity in the present invention;

Fig. 11 is a structural diagram of another embodiment of a mobile network management entity in the present invention;

Fig. 12 is a structural diagram of an embodiment of a mobile network gateway of the present invention.

Detailed ways

Embodiment one

In the embodiment, a solution for implementing flow-level IP data offloading in a 3G network is provided. Please refer to Fig. 1, which is a flow chart of an embodiment of a method for realizing business data stream distribution in the present invention, including the following steps:

Step 101: When establishing or modifying the IP connection to access the network IP-CAN bearer, the mobile network gateway obtains the access type of each service data flow, wherein the access type includes split access and non-distributed access;

Among them, IP-CAN (IP-Connectivity Access Network Bearer, IP connection access network) is a collection of network entities and interfaces that realize the connectivity between UE and IMS (IP Multimedia Subsystem, IP Multimedia System) entities through IP. Typical An example is GPRS (General Packet Radio Service, General Packet Radio Service). The term is usually used in the cellular context to indicate 3GPP access networks, such as GPRS or EDGE (Enhanced Data Rate for GSM Evolution, enhanced data rate GSM evolution technology), but can also be used to describe WLAN (Wireless LocalArea Networks, wireless local area network network) or DSL (Digital Subscriber Line, Digital Subscriber Line) network. It was introduced in 3GPP IMS as a generic term to denote any IP-based access network and focuses on the separation of access and service networks. IP-CAN carries an IP transmission channel that defines attributes such as speed, delay, and bit error rate (BER).

It should be noted that in the EPS (Evolved Packet System, evolved packet system) network, the IP-CAN bearer is the EPS bearer, while in the GPRS network, the IP-CAN bearer is the PDP (PacketData Protocol, packet data protocol) context.

In addition, the mobile network gateway obtains a distribution strategy from PCRF (Policy and Charging Rules Function, policy and charging rule function) or the mobile network gateway itself stores a distribution strategy, and the distribution strategy indicates the connection of various service data flows. The access type includes split access and non-distribution access.

Step 102: When the mobile network gateway determines that the access type of the service data stream transmitted on any IP-CAN bearer is split access according to the access type of each service data stream, send a bearer message that includes a split flag, so that The network entity receiving the bearer message and performing a data offloading operation offloads the service data flow transmitted on the bearer according to the indication of the offload flag, and the offload flag indicates the service data flow transmitted on the bearer The access type is split access.

Preferably, the mobile network gateway acquires the offload policy from the policy and charging rule function PCRF or the mobile network gateway itself stores the offload policy.

Further preferably, the method further includes: before the mobile network gateway obtains the offload policy from the PCRF, if the session message received by the mobile network gateway when establishing or modifying the IP-CAN session indicates receiving the Whether the network entity carrying the message and performing the data offloading operation has the offloading capability, the mobile network gateway notifies the PCRF whether the network entity has the offloading capability, so that the PCRF formulates the offloading according to whether the network entity has the offloading capability Strategy.

In this embodiment of the present invention, the mobile network gateway sends a bearer message including an offload flag, so that the network entity that receives the bearer message and performs data offload operations performs a data offload operation on the bearer according to the indication of the offload flag. The diversion of business data flow can be specifically as follows:

The mobile network gateway sends the bearer message including the offload flag to the base station through the mobile network management entity, so that the base station offloads the service data flow transmitted on the bearer according to the instruction of the offload flag.

Preferably, the method further includes: before the mobile network management entity sends the bearer message to the base station, the mobile network management entity judges whether the base station has offload capability, and then the mobile network gateway The network management entity sending the bearer message including the offload flag to the base station is: when the base station has an offload capability, the mobile network management entity sends the bearer message to the base station.

Further, preferably, the method further includes: if the mobile network management entity receives a message fed back by the terminal indicating that the terminal itself does not allow offloading, the mobile network management entity cancels the base station's support for the service transmitted on the bearer Split processing of data flow.

Further, when the mobile network gateway acquires the offload policy from the PCRF, preferably, the method further includes: before the mobile network gateway acquires the offload policy from the PCRF, if the mobile network gateway is establishing or The session message received when modifying the IP-CAN session indicates whether the base station has the offload capability, and the mobile network gateway notifies the PCRF whether the base station has the offload capability, so that the PCRF formulates an offload strategy according to whether the base station has the offload capability.

It should be noted that the IP-CAN session refers to the association between the user terminal and the IP network. The association is identified by the IP address of the terminal and available terminal ID information. An IP-CAN session contains one or more IP-CAN bearers. Support for multiple IP-CAN bearers depends on the type of IP-CAN. As long as the terminal IP address remains connected to the IP network, the IP-CAN session will always exist.

In the EPS network, the mobile network gateway is a packet data network gateway PGW, and the mobile network management entity is a mobility management entity MME.

Further, the bearer message received by the MME is a bearer creation request message or a bearer modification response message, and the bearer message sent by the MME is a bearer creation/modification request message.

In the GPRS network, the mobile network gateway is a GPRS gateway support node GGSN, and the mobile network management entity is a GRRS service support node.

Further, the bearer message received by the SGSN is a context creation response, and the bearer message sent by the SGSN is a radio bearer allocation request.

It can be seen from the above embodiments that the distribution strategy indicates the access types of various service data flows, and the access types include distribution access and non-distribution access, and the mobile network gateway learns the access types of each service data flow according to the distribution strategy. If the access type of the service data flow transmitted on a certain bearer is offload access, the mobile network gateway sends a bearer message containing the offload flag, so that the network entity that receives the bearer message and performs the offload operation knows the access type To offload access, and perform offload processing on the service data stream transmitted on the bearer according to the instructions.

Embodiment two

In the EPS network architecture of this embodiment, the offload strategy is obtained from PCRF by PGW (PDN GateWay, packet data network gateway), and the offload strategy indicates the access types of various service data flows, and the access type includes offload access And non-distribution access, after the PGW obtains the access types of various service data flows according to the distribution policy, and then in the process of establishing the bearer, it indicates to the base station the access type of the service data flow transmitted on a certain bearer. Please refer to FIG. 2, which is a flow chart of another embodiment of a method for realizing business data stream distribution in the present invention, including the following steps:

Step 201: The PGW learns the access type of each service data flow according to the offload strategy, and when it is determined that the access type of the service data flow transmitted on any IP-CAN bearer is offload access according to the access type of each service data flow , sending a create bearer request or modify bearer response including an offload flag to the mobile switching center MME through the serving gateway SGW, the offload strategy indicates the access types of various service data flows, and the access types include offload access and Non-distribution access, the distribution flag indicates that the access type of the service data flow transmitted on the bearer is distribution access;

The so-called "distributed access" means that the base station directly connects the user's service data flow to the routing device of the packet data network. For example, the router in the Internet does not pass through the core network of the operator. The base station connects the user's service data to the packet data network through the operator's core network, for example, the SGW and PGW in the core.

The PGW can obtain the offload policy from the PCRF. For example, when the terminal camps on a new cell, or switches from the source cell to the new cell, it needs to create a session or modify an existing bearer. When a request is made, send an IP CAN session creation or modification request to the PCRF, and the PCRF carries the distribution policy in the returned IP CAN session creation or modification response. In addition, the PGW can also store its own distribution strategy.

The offload policy in the PCRF can record various service data flows and their corresponding access types in a list form. Of course, it can also be recorded in other ways, and the embodiment of the present invention does not limit the recording form of the distribution policy. In addition, the access type corresponding to various service data streams may be determined by user subscription information, network conditions, or operator's operation strategy. The embodiment of the present invention does not specify which access type corresponds to various service data streams. Not limited.

Usually, when the PGW creates a bearer, it also transmits service data flows with the same requirements on the same bearer, for example, transmits service data flows with the same Qos requirements on the same bearer. Therefore, after the PGW knows the access type of each service data flow according to the distribution policy, it can transmit the service data flow with the same access type on the same bearer. Of course, if the QoS of the service data flow is also considered, it can also be The service data flows with the same access type and the same QoS requirements are transmitted on the same bearer.

For example, the PGW learns that the access types of service data flows a, b, and c are offloading access according to the offloading policy, and the access types of service data flows d and e are non-offloading access. When creating a bearer, if only access Type, the PGW allocates service data flows a, b, and c to bearer 1, and bearer 1 transmits them, and allocates service data flows e and d to bearer 2, and bearer 2 transmits them.

If the access type and QoS are considered at the same time, the PGW allocates the service data flow whose access type is offloaded access to bearers that meet high QoS requirements, or allocates the service data flow whose access type is non-distributed access to bearers that meet On bearers with high QoS requirements.

Step 202: MME sends a create/modify bearer request including an offload flag to the base station;

Step 203: The base station offloads the service data flow transmitted on the bearer according to the indication of the offload flag.

The offload flag indicates that the access type of the service data flow transmitted on a certain bearer is offload access. The base station can perform offload processing on the service data flow transmitted on the bearer according to the existing offload processing method. The service data stream transmitted on the uplink is directly connected to the packet data network, and the embodiment of the present invention does not specifically limit the offload processing method adopted by the base station.

In another case, when in step 202, the access type of each service data flow transmitted on a certain bearer is non-distribution access, the PGW will send the non-distribution access to the mobile switching center MME through the serving gateway SGW Create a bearer request or modify a bearer response with a flag, the non-distributed flag indicates that the access type of the current service data flow is non-distributed access, in step 203, the MME sends the create bearer request including the non-distributed flag to the base station, in step In 204, according to the indication of the non-distribution flag, the base station can perform non-distribution processing on the service data flow transmitted on the bearer according to the existing non-distribution processing method, and access the service data flow transmitted on the bearer through the core network In the packet data network, the embodiment of the present invention does not specifically limit the non-distribution processing method adopted by the base station.

The foregoing embodiments are completed when all base stations in the system have offload capabilities. If the system is being upgraded, there will be such a scenario: some base stations have offload capabilities, while others do not. In order to ensure the smooth completion of data offloading, when the access type of the service data flow transmitted on a certain bearer is offloading access, it is necessary to pre-judge whether the base station has the offloading capability, and only when the base station has the offloading capability, then instruct The base station performs offloading processing on the data.

Therefore, preferably, before the MME sends the create/modify bearer request to the base station, if the access type of the service data flow transmitted on any IP-CAN bearer is offload access, the MME judges whether the base station has offload capability, Sending the create/modify bearer request to the base station when the base station has an offload capability.

For example, information on whether each base station has the offload capability may be locally configured in the MME, and the MME directly learns whether each base station has the offload capability from the locally configured information. Alternatively, information about whether each base station has the offload capability may also be configured in an external database, and the MME invokes the information in the external database to learn whether each base station has the offload capability.

In addition, before offloading IP service data, it is also possible to further consider whether the terminal allows offloading. If the terminal allows offloading, the MME can cancel the offloading processing of the service data stream transmitted by the base station on the bearer according to the terminal's wishes.

Therefore, preferably, the method further includes: the terminal feeds back to the MME through the base station whether offloading is allowed during the process of session management or bearer establishment, and the MME cancels the pairing of the base station on the bearer when the terminal does not allow offloading. Offload processing of the transmitted business data flow.

For example, the bearer establishment request sent by the MME to the base station contains an offload flag, and when the radio resource control connection reconfiguration is performed between the base station and the terminal, the offload flag is included in the radio resource control connection reconfiguration request sent by the base station to the terminal , so that the terminal is notified to perform offload processing. In addition, the RRC connection reconfiguration response fed back by the terminal to the base station contains a permission flag or a non-permission flag, the permission flag indicates that the terminal allows offloading, and the non-permission flag indicates that the terminal does not allow offloading. When the base station sends a bearer establishment response to the MME, the bearer establishment response includes a permission flag or a non-permission flag. Alternatively, a session management request is encapsulated in the bearer establishment request sent by the MME to the base station, and the session management request includes an offload flag. The base station obtains the session management request including the offload flag through decapsulation, and sends the session management request to the terminal, so that the terminal knows that offload processing is to be performed. When performing radio resource control connection reconfiguration between the base station and the terminal, the radio resource control connection reconfiguration response fed back by the terminal to the base station contains a permission flag or a non-permission flag. When the base station sends a session management response to the MME, the session The admin response contains either an allow flag or a non-allow flag.

Through the above method, when the MME obtains the non-permission flag, the MME cancels the offload processing of the current service data flow by the base station according to the terminal's will. There are two situations: the MME cancels the offload processing of the current service data flow by the base station, or , the MME cancels the offloading operation before the base station offloads the current service data flow.

If the offload strategy is formulated by the PCRF, the PGW obtains the offload strategy from the PCRF. Before the PGW obtains the offload strategy from the PCRF, it first notifies the PCRF whether the base station has the offload capability, so that the PCRF can formulate the offload strategy according to the notified content. In this way, it can be ensured that the offloading strategy formulated by the PCRF takes into account the offloading capability of each base station, so that data offloading can be successfully completed. At the same time, since the offloading strategy formulated by the PCRF has considered the offloading capability of each base station, even if some base stations have the offloading capability and some base stations do not have the offloading capability, the MME does not need to judge whether the base station has the offloading capability.

Based on this, preferably, the method further includes: before the PGW obtains the offload policy from the PCRF, if the request for creating a session or modifying a bearer received by the PGW indicates whether the base station has the offload capability, the PGW determines whether the base station has the offload capability The PCRF is notified, so that the PCRF formulates an offload policy according to whether the base station has offload capability.

It can be seen from the above embodiments that the offloading strategy indicates the access types of various service data flows, and the access types include offloading access and non-offloading access, and the PGW learns the access types of each service data flow according to the offloading strategy , and further determine the access type of the service data flow transmitted on a certain bearer according to the access type of each service data flow, if the access type of the service data flow transmitted on the bearer is split access, the PGW notifies the base station The access type is split access, and the base station performs split processing on the service data flow transmitted on the bearer according to the instruction.

Further, before the MME sends a create/modify bearer request to the base station to notify the base station that the access type is offload access, the MME determines whether the base station has the offload capability, and only notifies the base station that the access type is offload when the base station has the offload capability Access, so that the base station performs offloading processing on the service data flow transmitted on the bearer according to the instruction.

Further, the terminal feeds back to the MME through the base station whether offloading is allowed during session management or bearer establishment, so that the MME can cancel the offloading processing of the service data stream transmitted by the base station on the bearer when the terminal does not allow offloading .

Embodiment three

Taking the terminal stationed in a new cell as an example, and each base station in the system has different offloading capabilities (some base stations can realize data offloading, and some base stations cannot realize data offloading) as an example, the whole The process of data shunting. Wherein, the PGW obtains the distribution policy from the PCRF. Please refer to FIG. 3 , which is a signaling flow chart of an embodiment of a method for realizing business data flow offloading according to the present invention, which specifically includes the following steps:

Step 301: the terminal sends an attach request message to the current base station;

Step 302: the current base station sends an attach request message to the MME;

Step 303: MME sends a session creation request message to SGW;

Preferably, the MME can know whether the current base station has the offload capability according to the local configuration or the information on whether each base station has the offload capability stored in the external database, and indicate whether the current base station has the offload capability in the session creation request.

Step 304: SGW sends a session creation request message to PGW;

Similarly, when the session creation request sent by the MME to the SGW indicates whether the current base station has the offload capability, the session creation request sent by the SGW to the PGW also indicates whether the current base station has the offload capability.

Step 305: PGW sends IP CAN session establishment request message to PCRF after receiving establishment session request message;

Similarly, when indicating whether the current base station has offload capability in the session creation request message in step 303 and step 304, whether the current base station has offload capability is also indicated in the IP CAN session establishment request message sent by the PGW to PCRF, like this, The PCRF can further formulate an offload strategy according to whether the current base station has offload capability. Since the offloading strategy formulated by the PCRF has considered the offloading capability of each base station, the data offloading can be successfully completed.

Step 306: PCRF sends to PGW the IP CAN session establishment response message that comprises distribution policy;

Wherein, the distribution policy indicates access types of various service data flows, and the access types include distribution access and non-distribution access.

Step 307: The PGW learns the access type of each service data flow according to the offload policy, and sends to the SGW a create bearer request message containing an offload flag, which indicates that the access type of the service data flow transmitted on a certain bearer is offload access;

Step 308: The SGW sends the create bearer request message containing the offload flag to the MME;

Step 309: MME judges whether the current base station has offload capability;

Currently, if the PCRF has considered whether the current base station has the offload capability when specifying the offload policy, this step can also be omitted.

Step 310: If the current base station has the offload capability, the MME sends to the current base station a create bearer request message including an offload flag, and at the same time, sends a session management request message to the current base station, and the session management request message is encapsulated in the create bearer request message;

Step 311: The current base station analyzes and obtains the session management request message, and sends the session management request message to the terminal;

Step 312: Complete the RRC connection reconfiguration process between the current base station and the terminal;

Step 313: The current base station sends a create bearer response message to the MME;

Step 314: The current terminal sends a session management response message to the MME through the base station;

The above steps 313 and 314 are executed in no strict sequence, and the session management response message may be sent first, and then the bearer creation response message may be sent.

Step 315: After the bearer is established, the current base station performs offload processing on the current service data flow according to the offload flag;

During the offload processing, the base station performs a NAT (Network Address Translation, Network Address Translation) operation on the uplink message of the radio bearer, and forwards the received downlink message on the radio bearer.

The specific process of the NAT operation is: the base station modifies the source address of the message sent by the terminal to the address of the base station before sending the uplink message to the packet network router. Optionally, the port number of the message is further modified to another port, and the base station records the mapping relationship, that is, the mapping relationship between the source address of the uplink message, the source port, the modified address, and the port. Finally, the base station sends the uplink message to the packet network router. When the opposite end of the terminal sends a message to the terminal, the destination address of the message is the address of the base station, so the message will be routed to the base station, and the base station knows which terminal the message is sent to according to the recorded mapping relationship. After receiving the address and port number of the message, the message is sent to the terminal.

The purpose of using NAT operation is: if the source address of the message sent by the terminal is not modified, the destination address used by the peer end of the terminal when sending a message to the terminal is the source address of the original terminal, and this address is assigned by the PGW The terminal, so the message will be routed to the PGW, which will cause the terminal to send the message to be distributed, and the received message will not be distributed. Therefore, the above NAT operation needs to be performed.

Step 316: MME sends a create bearer response message to SGW;

Step 317: The SGW sends a create bearer response message to the PGW.

It can be seen from the above embodiments that the offload strategy is formulated at the PCRF, and the offload strategy indicates the access types of various service data flows. The access types include offload access and non-offload access, and the PGW obtains from the PCRF According to the distribution strategy, the access type of each service data flow is obtained according to the distribution strategy, and the access type of the service data flow transmitted on a certain bearer is notified to the MME. If the access type of the service data flow transmitted on the bearer is Offload access. The MME further judges whether the current base station has the offload capability. When the current base station has the offload capability, the MME notifies the base station that the service data flow on the bearer needs to be offloaded. The data flow is split and processed.

Embodiment four

The difference between this embodiment and Embodiment 2 is that the MME further considers whether the terminal itself allows offloading, and cancels the offloading processing of the current base station when the current base station has the offloading capability but the terminal does not allow offloading. Please refer to FIG. 4 , which is another signaling flow chart of an embodiment of a method for realizing business data flow offloading according to the present invention, which specifically includes the following steps:

Step 401: the terminal sends an attach request message to the current base station;

Step 402: the current base station sends an attach request message to the MME;

Step 403: MME sends a session creation request message to SGW;

Step 404: SGW sends a session creation request message to PGW;

Step 405: PGW sends IP CAN session establishment request message to PCRF after receiving establishment session request message;

Step 406: PCRF sends to PGW the IP CAN session establishment response message that comprises distribution policy;

Step 407: The PGW learns the access type of each service data flow according to the offload policy, and sends a bearer creation request message containing an offload flag to the SGW, and the offload flag indicates that the access type of the service data flow transmitted on a certain bearer is offload access;

Step 408: The SGW sends the create bearer request message containing the offload flag to the MME;

Step 409: MME judges whether the current base station has offload capability;

The above steps 401-409 are the same as the steps 301-309 in the second embodiment, and the detailed process can refer to the part of the second embodiment.

Step 410: If the current base station is capable of offloading, the MME sends to the current base station a create bearer request message containing the offloading flag, and at the same time, sends a session management request message including the offloading flag to the current base station, and the session management request message is encapsulated in the creation in a bearer request message;

Since the offload flag is included in the session management request message, the terminal can learn that the bearer needs offload.

Step 411: The current base station analyzes and obtains the session management request message, and sends the session management request message including the offload flag to the terminal;

Step 412: The radio bearer control reconfiguration process is completed between the current base station and the terminal, wherein the terminal sends a radio resource control connection reconfiguration response message indicating whether offloading is allowed to the current base station;

In addition, in addition to including the offload flag in the session management request message in step 410, so as to notify the terminal, in this step, the current base station can also be included in the radio resource control connection reconfiguration request message sent to the terminal. The offload flag is included, and furthermore, in the radio bearer control reconfiguration process in step 412, the offload flag is included in the RRC connection reconfiguration request message sent by the current base station to the terminal, so that the terminal can be notified.

Step 413: the current base station sends a create bearer response message to the MME;

When the offload flag is notified to the terminal in the manner in step 411, the bearer creation response message in this step indicates whether the terminal allows offload.

Step 414: When the terminal does not allow offloading, the current base station sends a session management response message including a non-allowed flag to the MME;

Similarly, there is no strict sequence in the execution of the above steps 413 and 414, and the session management response message may be sent first, and then the bearer creation response message may be sent.

Step 415: After the bearer is established, the current base station performs offload processing on the service data flow transmitted on the bearer according to the offload flag;

During the offloading process, the current base station performs a NAT operation on the uplink message of the radio bearer, and forwards the received downlink message on the radio bearer.

Step 416: MME sends a create bearer response message to SGW;

Step 417: SGW sends a create bearer response message to PGW;

Step 418: When the MME knows that the offload is not allowed by the terminal according to the non-permission flag, it sends a modify bearer request message to the current base station, and cancels the offload processing being performed by the current base station.

It can be seen from the above embodiments that the offload strategy is formulated at the PCRF, and the offload strategy indicates the access types of various service data flows. The access types include offload access and non-offload access, and the PGW obtains from the PCRF According to the distribution strategy, the access type of each service data flow is obtained according to the distribution strategy, and the access type of the service data flow transmitted on a certain bearer is notified to the MME. If the access type of the service data flow transmitted on the bearer For offload access, the MME further judges whether the current base station has the offload capability. When the current base station has the offload capability, the MME notifies the base station that the service data stream transmitted on the bearer needs to be offloaded, and the base station performs offload processing on the bearer according to the instruction. The transmitted business data flow is divided and processed.

In addition, after the terminal knows that the offloading process is to be performed, the terminal also feeds back to the MME whether it allows offloading, and when the MME knows that the terminal does not allow offloading, it cancels the offloading process on the current base station.

Embodiment five

The difference between the embodiment of the present application and the second embodiment is that this embodiment describes the whole data offloading process of the handover of the terminal from the source cell to the target cell. Please refer to FIG. 5 , which is another signaling flow chart of an embodiment of a method for realizing service data flow offloading according to the present invention, which specifically includes the following steps:

Step 501: the terminal sends a tracking area update request message to the target base station;

Step 502: The target base station sends a tracking area update request message to the MME;

Step 503: MME sends a modify bearer request message to SGW;

Preferably, the MME can know whether the target base station has the offload capability according to the local configuration or the information on whether each base station has the offload capability stored in the external database, and indicates whether the target base station has the offload capability in the bearer modification request.

Step 504: SGW sends a modify bearer request message to PGW;

Similarly, when the bearer modification request sent by the MME to the SGW indicates whether the target base station has the offload capability, the bearer establishment request sent by the SGW to the PGW also indicates whether the target base station has the offload capability.

Step 505: After receiving the modification bearer request message, the PGW sends the IP CAN session modification request message to the PCRF;

Similarly, when the modification bearer request message in step 503 and step 504 indicates whether the target base station has the offload capability, the IP CAN session modification request message sent by the PGW to the PCRF also indicates whether the target base station has the offload capability. The PCRF can further formulate an offload strategy according to whether the target base station has offload capability. Since the offloading strategy specified by the PCRF has considered the offloading capability of each base station, the data offloading can be successfully completed.

Step 506: PCRF sends to PGW the IP CAN session modification response message that includes distribution policy;

Wherein, the distribution policy indicates access types of various service data flows, and the access types include distribution access and non-distribution access.

Step 507: The PGW learns the access type of each service data flow according to the offload policy, and sends to the SGW a modified bearer response message containing an offload flag, and the offload flag indicates that the access type of the service data flow transmitted on a certain bearer is offload access. enter;

Step 508: The SGW sends the modify bearer response message containing the offload flag to the MME;

Step 509: MME judges whether the target base station has offload capability;

Currently, if the PCRF has considered whether the target base station has the offload capability when formulating the offload strategy, this step can also be omitted.

Step 510: If the target base station has offload capability, the MME sends to the target base station a create bearer request message including an offload flag, and at the same time, sends a session management request message to the target base station, where the session management request message is encapsulated in the create bearer request message;

Step 511: The target base station analyzes and obtains the session management request message, and sends the session management request message to the terminal;

Step 512: The radio resource control connection reconfiguration process is completed between the target base station and the terminal;

Step 513: The target base station sends a create bearer response message to the MME;

Step 514: the target base station sends a session management response message to the MME;

The above steps 513 and 514 are executed in no strict order, and the session management response message may be sent first, and then the bearer creation response message may be sent.

Step 515: After the bearer is established, the target base station performs offload processing on the current service data flow according to the offload flag;

During the offloading process, the base station performs a NAT operation on the uplink message of the radio bearer, and forwards the received downlink message on the radio bearer.

Step 516: MME sends a create bearer response message to SGW;

Step 517: The SGW sends a create bearer response message to the PGW.

In the above process, the MME may further consider whether the terminal itself has the offload capability, and cancel the offload processing of the target terminal when the target base station has the offload capability but the terminal does not have the offload capability. Specifically, in step 510, the session management request message sent by the MME to the base station further indicates that the target base station has the offload capability, so that the terminal can learn that the target base station has the offload capability. In step 512, when the radio bearer control reconfiguration is completed between the target base station and the terminal, the radio resource control secondary configuration response message sent by the terminal to the base station indicates whether offload processing is allowed by itself. In addition, in addition to notifying the terminal by indicating that the target base station has the offload capability in the session management request message in steps 510 and 511, in step 512, the radio resource control connection sent by the target base station to the terminal The reconfiguration request message indicates that the current base station has offload capability.

It can be seen from the above embodiments that the offload strategy is formulated at the PCRF, and the offload strategy indicates the access types of various service data flows. The access types include offload access and non-offload access, and the PGW obtains from the PCRF According to the distribution strategy, the access type of each service data flow is obtained according to the distribution strategy, and the access type of the service data flow transmitted on a certain bearer is notified to the MME. If the access type of the service data flow transmitted on the bearer is Offload access. The MME further judges whether the current base station has the offload capability. When the current base station has the offload capability, the MME notifies the base station that the service data flow on the bearer needs to be offloaded. The data flow is split and processed.

Embodiment six

In the GPRS network framework of the present embodiment, by GGSN (Gateway GPRS Support Node, GPRS gateway support node) obtains offload policy from PCRF, offload policy has indicated the access type of various business data flows, and described access type includes offload Access and non-distributed access, and indicate the access type of the current service data flow to the base station during the process of allocating radio bearers. Please refer to FIG. 6 , which is a flow chart of another embodiment of a method for realizing business data stream distribution in the present invention, including the following steps:

Step 601: GGSN obtains the access type of each service data flow, and when determining that the access type of the service data flow transmitted on any IP-CAN bearer is split access according to the access type of each service data flow, send SGSN (Serving GPRS Support Node, GPRS service support node) sends a context creation response containing an offload flag, the access type includes offload access and non-offload access, and the offload flag indicates the service transmitted on a certain bearer The access type of the data flow is split access;

The GGSN obtains the offload policy from the PCRF. For example, when the terminal camps on a new cell, it needs to create a context. When the GGSN receives the context creation request, it sends a CCR to the PCRF, and the PCRF carries the offload policy in the returned CCA. In addition, the GGSN itself may also store a distribution strategy, which indicates the access types of various service data flows, and the access types include distribution access and non-distribution access.

The embodiment of the present invention does not limit the recording form of the distribution policy. In addition, the access type corresponding to various service data streams may be determined by user subscription information, network conditions, or operator's operation strategy. The embodiment of the present invention does not specify which access type corresponds to various service data streams. Not limited.

Usually, when the PGW creates a bearer, it also transmits service data flows with the same requirements on the same bearer, for example, transmits service data flows with the same Qos requirements on the same bearer. Therefore, after the PGW knows the access type of each service data flow according to the distribution policy, it can transmit the service data flow with the same access type on the same bearer. Of course, if the QoS of the service data flow is also considered, it can also be The service data flows with the same access type and Qos requirements are transmitted on the same bearer. Step 602: SGSN sends a radio bearer allocation request including an offload flag to the base station;

Step 603: The base station offloads the service data flow transmitted on the bearer according to the instruction of the offload flag.

The offload flag indicates that the access type of the service data flow transmitted on a certain bearer is offload access. The base station can perform offload processing on the service data flow transmitted on the bearer according to the existing offload processing method. The service data stream transmitted on the uplink is directly connected to the packet data network, and the embodiment of the present invention does not specifically limit the offload processing method adopted by the base station.

Another situation is that when in step 601, the access type of each service data flow transmitted on a certain bearer is non-distribution access, the GGSN will send a context creation response containing a non-distribution flag to the SGSN, the The non-distribution flag indicates that the access type of the current service data flow is non-distribution access. In step 602, the SGSN sends a radio bearer allocation request containing the non-distribution flag to the base station. In step 603, the base station , the service data flow transmitted on the bearer can be non-distributed according to the existing non-distribution processing method, and the service data flow transmitted on the bearer can be connected to the packet data network through the core network, the embodiment of the present invention There is also no specific limitation on the non-distribution processing method adopted by the base station.

The above embodiments are completed under the condition that all base stations in the system have offload capabilities. If in the upgrade stage of the system, there will be such a scenario: some base stations have offload capabilities, while other base stations do not have offload capabilities. In order to Ensure that the sequence of data offloading is completed. When the access type of the service data flow transmitted on the bearer is offloading access, it is necessary to pre-judge whether the base station has the offloading capability. Only when the base station has the offloading capability, instruct the base station Streamline the data.

Therefore, preferably, before the SGSN sends a radio bearer allocation request to the base station, if the access of the service data flow transmitted on the bearer is offload access, the SGSN judges whether the base station has offload capability, and in the When the base station has an offload capability, send the radio bearer allocation request to the base station.

For example, information about whether each base station has the offload capability can be locally configured in the SGSN, and the SGSN directly learns whether each base station has the offload capability from the locally configured information. Alternatively, information about whether each base station has the offload capability may also be configured in an external database, and the SGSN calls the information in the external database to learn whether each base station has the offload capability.

In addition, before offloading IP service data, you can further consider whether the terminal allows offloading. If the terminal does not allow it, the SGSN can cancel the offloading processing of the service data stream transmitted by the base station on the bearer according to the terminal's wishes.

Therefore, preferably, the method further includes: during the wireless bearer allocation process, the terminal feeds back to the SGSN through the base station whether it allows offloading, and the SGSN cancels the base station's support for the service transmitted on the bearer when the terminal does not allow offloading. Split processing of data flow.

For example, the radio bearer allocation request sent by the SGSN to the base station contains an offload flag. When the radio bearer is established between the base station and the terminal, the radio bearer establishment request sent by the base station to the terminal contains the offload flag, so that the terminal knows that it needs to perform Triage processing. Moreover, the radio bearer response fed back by the terminal to the base station includes an allow flag or a non-allow flag, the allow flag indicates that the terminal allows offloading, and the non-allow flag indicates that the terminal does not allow offloading. When the base station sends a radio bearer allocation response to the SGSN, the radio bearer allocation response includes a permission flag or a non-permission flag.

Through the above method, when the SGSN obtains the non-permission flag, the SGSN cancels the offload processing of the current service data flow by the base station according to the terminal's will. There are two situations: the SGSN cancels the offload processing of the current service data flow by the base station, or , the SGSN cancels the offloading operation before the base station offloads the current service data flow.

As can be seen from the above embodiments, the offload strategy is formulated at the PCRF or saved at the GGSN. The offload strategy indicates the access types of various service data flows, and the access types include offload access and non-offload access. access, the GGSN obtains the offload policy from the PCRF or obtains the offload policy itself, and learns the access type of each service data flow according to the offload policy. If the access type of the service data flow transmitted on a certain bearer is offload access, the GGSN The base station is notified that the access type is offload access, and the base station performs offload processing on the service data flow transmitted on the bearer according to the instruction.

Embodiment seven

In the following, when the terminal is stationed in a new cell, and each base station in the system has different offloading capabilities (some base stations can realize data offloading, and some base stations cannot realize data offloading) as an example, the data will be described in detail. The whole process of diversion. Wherein, the GGSN obtains the distribution strategy from the PCRF. Please refer to FIG. 7 , which is another signaling flow chart of another embodiment of a method for realizing business data stream offloading according to the present invention, which specifically includes the following steps:

Step 701: The terminal sends a context creation request message to the SGSN through the current base station;

Step 702: SGSN sends a create context request message to GGSN;

Step 703: After receiving the context creation request message, the GGSN sends a CCR message to the PCRF;

Step 704: The PCRF sends a CCA message containing the offload policy to the GGSN;

Step 705: The GGSN learns the access type of each service data flow according to the offload policy, and sends a create context response message containing the offload flag to the SGSN;

Step 706: SGSN judges whether the current base station has offload capability;

Step 707: If the current base station has the offload capability, the SGSN sends a radio bearer allocation request message including the offload flag to the current base station;

Step 708: Establish a radio bearer between the current base station and the terminal;

Step 709: The current base station sends a radio bearer allocation response message to the SGSN;

Step 710: SGSN sends a create context response message to the terminal;

Step 711: After the context is established, the current base station processes the current service data flow according to the indication of the offload flag.

As can be seen from the above embodiments, the offload strategy is formulated at the PCRF or saved at the GGSN. The offload strategy indicates the access types of various service data flows, and the access types include offload access and non-offload access. access, the GGSN obtains the offloading strategy from the PCRF or obtains the offloading strategy itself, and obtains the access type of each service data flow according to the offloading strategy, and notifies the SGSN of the access type of the service data flow transmitted on a certain bearer. The access type of the service data flow transmitted on the bearer is offload access. The SGSN further determines whether the current base station has the offload capability. When the current base station has the offload capability, the SGSN notifies the base station that the service data flow transmitted on the bearer needs Perform offload processing, and the base station performs offload processing on the service data stream transmitted on the bearer according to the instruction.

Embodiment eight

The difference between this embodiment and implementation six is that the SGSN further considers whether the terminal itself allows offloading, and cancels the offloading processing of the current base station when the current base station has the offloading capability but the terminal does not allow offloading. Please refer to FIG. 8 , which is another signaling flow chart of another embodiment of a method for realizing service data flow offloading according to the present invention, which specifically includes the following steps:

Step 801: The terminal sends a context creation request message to the SGSN through the current base station;

Step 802: SGSN sends a create context request message to GGSN;

Step 803: After receiving the Create Context Request message, the GGSN sends a CCR message to the PCRF;

Step 804: The PCRF sends a CCA message containing the offload policy to the GGSN;

Step 805: The GGSN learns the access type of each service data flow according to the offload policy, and sends to the SGSN a context creation response message containing an offload flag, which indicates that the access type of the service data flow transmitted on a certain bearer is offload access;

Step 806: SGSN judges whether the current base station has offload capability;

Step 807: If the current base station has the offload capability, the SGSN sends a radio bearer allocation request message including the offload flag to the current base station;

Step 808: Establish a radio bearer between the current base station and the terminal, wherein the current base station sends a radio bearer establishment request message containing an offload flag to the terminal, and when the terminal does not allow offload, the terminal sends a radio bearer establishment request message containing a non-permission flag to the current base station. bearer response message;

Step 809: the current base station sends a radio bearer allocation response message containing a non-allowed flag to the SGSN;

Step 810: SGSN sends a create context response message to the terminal;

Step 811: After the context is established, the base station processes the current service data flow according to the indication of the offload flag;

Step 812: When the SGSN knows that offloading is not allowed by the terminal according to the non-permission flag, it sends a radio bearer modification request message to the current base station, and cancels the offloading process being performed by the current base station.

As can be seen from the above embodiments, the offload strategy is formulated at the PCRF or saved at the GGSN. The offload strategy indicates the access types of various service data flows, and the access types include offload access and non-offload access. access, the PGW obtains the offload policy from the PCRF, and learns the access type of the current service data flow according to the offload policy, and notifies the SGSN of the access type of the service data flow transmitted on a certain bearer. The access type of the service data stream is offloading access. The SGSN further judges whether the current base station has the offloading capability. When the current base station has the offloading capability, the SGSN notifies the base station that the service data stream transmitted on the bearer needs to be offloaded. The base station performs offloading processing on the service data flow transmitted on the bearer according to the instruction.

In addition, when the terminal knows that the offloading process is to be performed, the terminal feeds back to the SGSN whether it allows it, and when the SGSN knows that the offloading process is not allowed by the terminal, it cancels the offloading process on the current base station.

Embodiment nine

Corresponding to the method for realizing the offloading of service data streams in the first embodiment, the present invention also provides a system for realizing offloading of service data streams. Please refer to FIG. 9 , which is a structural diagram of an embodiment of a system for implementing service data flow distribution according to the present invention, including: a mobile network gateway 901 and a network entity 902 performing data distribution operations, wherein,

The mobile network gateway 901 is used to know the access type of each service data flow when establishing or modifying the IP-CAN bearer, and determine the service data transmitted on any IP-CAN bearer according to the access type of each service data flow When the access type of the flow is offload access, send a bearer message including an offload flag, and use the offload flag in the bearer message to indicate that the access type of the service data stream transmitted on the bearer is offload access, so The above access types include split access and non-split access;

The network entity 902 performing the data offloading operation is configured to receive the bearer message, and offload the service data flow transmitted on the bearer according to the indication of the offload flag.

Preferably, the system further includes: a mobile network management entity, configured to determine whether the network entity has offload capability before sending the bearer message to the network entity, and send the The network entity sends the bearer message.

Further preferably, the mobile network management entity 902 is further configured to cancel the offload processing of the service data flow transmitted on the bearer by the network entity when receiving a message fed back by the terminal that the terminal itself does not allow offload.

Further preferably, the mobile network gateway 901 includes: an acquisition unit, configured to obtain the offloading strategy from the PCRF; or, a storage unit, used to store the offloading strategy, and the offloading strategy indicates the access type of various service data flows, so The above access types include split access and non-split access.

Further preferably, the mobile network gateway 901 further includes: a notification unit, configured to indicate that the base station is indicated in the session message received by the mobile network gateway when establishing or modifying the IP-CAN session before the acquiring unit acquires the offload policy from the PCRF. Whether the base station has the offload capability, and notifies the PCRF whether the base station has the offload capability, so that the PCRF formulates an offload policy according to whether the base station has the offload capability. Preferably, the mobile network gateway is a packet data network gateway PGW, and the mobile network management entity is a mobility management entity MME, or, the mobile network gateway is a GPRS gateway support node GGSN, and the mobile network management entity is a GRRS Service support nodes.

Further preferably, the bearer message received by the MME is a bearer creation request or a bearer modification response, the bearer message sent by the MME is a create/modify bearer request, or the bearer message received by the SGSN is a context creation response, the The bearer message sent by the SGSN is a radio bearer allocation request.

It can be seen from the above embodiments that the distribution strategy indicates the access types of various service data flows, and the access types include distribution access and non-distribution access, and the mobile network gateway learns the access types of each service data flow according to the distribution strategy. If the access type of the service data flow transmitted on a certain bearer is offload access, the mobile network management entity is notified that the access type is offload access, and the mobile network management entity notifies the base station of the service data flow transmitted on the bearer The service data flow needs to be offloaded, and the base station processes the service data flow transmitted on the bearer according to the instruction.

In addition, at the mobile network management entity, it is further judged whether the current base station has the offloading capability, and when the current base station has the offloading capability, the base station is notified that the service data flow transmitted on the bearer needs to be offloaded.

After the terminal knows that the offloading process is to be performed, the terminal also feeds back to the mobile network management entity whether it allows offloading, and when the mobile network management entity learns that the terminal does not allow offloading, it cancels the offloading process on the current base station.

Embodiment ten

The invention also provides a mobile network management entity. Please refer to FIG. 10, which is a structural diagram of an embodiment of a mobile network management entity in the present invention, including: a first receiving unit 1001 and a first sending unit 1002, wherein,

The first receiving unit 1001 is configured to receive a bearer message containing an offload flag sent by a mobile network gateway when establishing or modifying an IP connection to access a network IP-CAN bearer, wherein the bearer message containing an offload flag is a mobile network gateway The access type of each service data flow is known, and according to the access type of each service data flow, it is determined that the access type of the service data flow transmitted on any IP-CAN bearer is sent after split access, and the access The types include offload access and non-offload access, and the offload flag indicates that the access type of the service data flow transmitted on the bearer is offload access;

The first sending unit 1002 is configured to send the bearer message including the offload flag to the base station, so that the base station offloads the service data flow transmitted on the bearer according to the instruction of the offload flag.

Preferably, please refer to FIG. 11 , which is a structural diagram of another embodiment of a mobile network management entity in the present invention. The mobile network management entity further includes: a judging unit 1003, configured to send the first sending unit to the Before the base station sends the bearer message, determine whether the base station has offload capability, and send the bearer message to the base station when the base station has offload capability.

Preferably, the mobile network management entity further includes: a canceling unit, configured to cancel the service transmitted by the base station on the bearer if the mobile network management entity receives a message fed back by the terminal that the terminal itself does not allow offloading. Split processing of data flow.

It can be seen from the above embodiments that the distribution strategy indicates the access types of various service data flows, and the access types include distribution access and non-distribution access, and the mobile network gateway learns the access types of each service data flow according to the distribution strategy. If the access type of the service data flow transmitted on a certain bearer is offload access, the mobile network management entity is notified that the access type is offload access, and the mobile network management entity notifies the base station of the service data flow transmitted on the bearer The service data flow needs to be offloaded, and the base station processes the service data flow transmitted on the bearer according to the instruction.

In addition, at the mobile network management entity, it is further judged whether the current base station has the offloading capability, and when the current base station has the offloading capability, the base station is notified that the service data flow transmitted on the bearer needs to be offloaded.

After the terminal knows that the offloading process is to be performed, the terminal also feeds back to the mobile network management entity whether it allows offloading, and when the mobile network management entity learns that the terminal does not allow offloading, it cancels the offloading process on the current base station.

Embodiment Eleven

The invention also provides a mobile network gateway. Please refer to FIG. 12 , which is a structural diagram of an embodiment of a mobile network gateway in the present invention, including: an acquiring unit 1201 and a second sending unit 1202, wherein,

The obtaining unit 1201 is configured to obtain the access type of each service data flow when establishing or modifying the IP connection access network IP-CAN bearer, and the access type includes distribution access and non-distribution access;

The second sending unit 1202 is configured to send the mobile network management entity the Sending a bearer message containing an offload flag, indicating that the access type of the service data stream transmitted on the bearer is offload access through the offload flag in the bearer message, so that the mobile network management entity sends a message containing the offload flag to the base station The bearer message enables the base station to offload the service data flow transmitted on the bearer according to the indication of the offload flag.

Preferably, the obtaining unit 1201 includes: an acquiring unit, configured to obtain an offloading strategy from the PCRF; or a storage unit, configured to store the offloading strategy, the offloading strategy indicating the access type of various service data flows, the accessing The input types include split access and non-distribution access.

When the obtaining unit obtains the offloading strategy from the PCRF, further preferably, the mobile network gateway further includes: a notification unit, configured to, before the obtaining unit obtains the offloading strategy from the PCRF, if the mobile network gateway is establishing or The session message received when modifying the IP-CAN session indicates whether the base station has the offload capability, and notifies the PCRF whether the base station has the offload capability, so that the PCRF formulates an offload strategy according to whether the base station has the offload capability.

It can be seen from the above embodiments that the distribution strategy indicates the access types of various service data flows, and the access types include distribution access and non-distribution access, and the mobile network gateway learns the access types of each service data flow according to the distribution strategy. If the access type of the service data flow transmitted on a certain bearer is offload access, the mobile network management entity is notified that the access type is offload access, and the mobile network management entity notifies the base station of the service data flow transmitted on the bearer The service data flow needs to be offloaded, and the base station processes the service data flow transmitted on the bearer according to the instruction.

In addition, at the mobile network management entity, it is further judged whether the current base station has the offloading capability, and when the current base station has the offloading capability, the base station is notified that the service data flow transmitted on the bearer needs to be offloaded.

After the terminal knows that the offloading process is to be performed, the terminal also feeds back to the mobile network management entity whether it allows offloading, and when the mobile network management entity learns that the terminal does not allow offloading, it cancels the offloading process on the current base station.

It should be noted that those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing related hardware through computer programs, and the programs can be stored in a computer-readable memory In the medium, when the program is executed, it may include the processes of the embodiments of the above-mentioned methods. Wherein, the storage medium may be a magnetic disk, an optical disk, a read-only memory (Read-Only Memory, ROM) or a random access memory (Random AccessMemory, RAM), etc.

A method, system and related devices for realizing business data flow distribution provided by the present invention have been introduced in detail above. In this paper, specific embodiments are used to illustrate the principle and implementation of the present invention. The description of the above embodiments is only used To help understand the method of the present invention and its core idea; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation and scope of application. In summary, this specification The content should not be construed as a limitation of the invention.

Claims (16)

1. A method for realizing business data flow shunting, characterized in that, comprising: When establishing or modifying the IP connection access network IP-CAN bearer, the mobile network gateway learns the access type of each service data flow, and the access type includes split access and non-distributed access; When the mobile network gateway determines that the access type of the service data stream transmitted on any IP-CAN bearer is split access according to the access type of each service data stream, the mobile network gateway sends a message to the base station through the mobile network management entity A bearer message including an offload flag, so that the base station receiving the bearer message and performing a data offload operation offloads the service data flow transmitted on the bearer according to the indication of the offload flag, and the offload flag indicates The access type of the service data flow transmitted on the bearer is offload access; wherein, before the mobile network management entity sends the bearer message to the base station, the mobile network management entity determines whether the base station has offload capability, sending the bearer message to the base station when the base station has offload capability. 2. The method according to claim 1, wherein the mobile network gateway obtains a distribution strategy from the policy and charging rule function PCRF or the mobile network gateway itself stores a distribution strategy, and the distribution strategy indicates the distribution of various service data flows. An access type, where the access type includes offload access and non-offload access. 3. The method according to claim 2, further comprising: before the mobile network gateway obtains the offloading policy from the PCRF, if the mobile network gateway is establishing or modifying the IP-CAN The session message received during the session indicates whether the network entity receiving the bearer message and performing the data offloading operation has the offloading capability, and the mobile network gateway notifies the PCRF whether the network entity has the offloading capability, so that the PCRF An offload policy is formulated according to whether the network entity has an offload capability. 4. The method according to claim 1, further comprising: if the mobile network management entity receives a message from the terminal indicating that the terminal itself does not allow offloading, the mobile network management entity cancels the The base station offloads and processes the service data flow transmitted on the bearer. 5. The method according to any one of claims 1-4, wherein the mobile network gateway is a packet data network gateway PGW, and the mobile network management entity is a mobility management entity MME, or the The mobile network gateway is a GPRS gateway support node GGSN, and the mobile network management entity is a GRRS serving support node SGSN. 6. The method according to claim 5, wherein the bearer message received by the MME is a bearer creation request message or a bearer modification response message, and the bearer message sent by the MME is a bearer creation/modification request message; Alternatively, the bearer message received by the SGSN is a context creation response message, and the bearer message sent by the SGSN is a radio bearer allocation request message. 7. A system for realizing business data stream offloading, comprising: a mobile network gateway, a network entity performing data offloading operations, and a mobile network management entity, wherein, The mobile network gateway is used to know the access type of each service data flow when establishing or modifying the IP-CAN bearer, and determine the service transmitted on any IP-CAN bearer according to the access type of each service data flow When the access type of the data stream is offloading access, the mobile network management entity sends a bearer message including an offloading flag, and the offloading flag in the bearer message indicates the access type of the service data stream transmitted on the bearer For distribution access, the access type includes distribution access and non-distribution access; The network entity performing the data offloading operation is configured to receive the bearer message, and offload the service data flow transmitted on the bearer according to the indication of the offload flag; The mobile network management entity is configured to determine whether the network entity has the offload capability before sending the bearer message to the network entity, and send the bearer to the network entity when the network entity has the offload capability information. 8. The system according to claim 7, wherein the mobile network management entity is further configured to, when receiving a message fed back by the terminal that the terminal itself does not allow offloading, cancel the connection between the network entity and the bearer Offload processing of business data streams transmitted on the Internet. 9. The system according to any one of claims 7-8, wherein the mobile network gateway comprises: An acquisition unit, configured to acquire a distribution strategy from the PCRF, the distribution strategy indicates the access type of various service data flows, and the access type includes distribution access and non-distribution access; or, The storage unit is used to store the offloading policy, the offloading policy indicates the access type of various service data flows, and the access type includes offloading access and non-offloading access. 10. The system according to claim 9, wherein the mobile network gateway further comprises: a notification unit, configured to, before the acquiring unit acquires the offload policy from the PCRF, if the mobile network gateway is establishing or revising the IP - The session message received during the CAN session indicates whether the network entity that receives the bearer message and performs the data offloading operation has the offloading capability, and notifies the PCRF whether the network entity has the offloading capability, so that the PCRF according to the Whether the network entity has the ability to divert traffic to formulate a traffic diversion strategy. 11. The system according to claim 7, 8 or 10, wherein the mobile network gateway is a packet data network gateway PGW, the mobile network management entity is a mobility management entity MME, or the mobile network The gateway is a GPRS gateway support node GGSN, and the mobile network management entity is a GRRS service support node. 12. The system according to claim 11, wherein the bearer message received by the MME is a bearer creation request or a bearer modification response, the bearer message sent by the MME is a bearer creation/modification request, or the SGSN The received bearer message is a context creation response, and the bearer message sent by the SGSN is a radio bearer allocation request. 13. A mobile network management entity, comprising: The first receiving unit is configured to receive the bearer message containing the offload flag sent by the mobile network gateway when establishing or modifying the IP connection to access the network IP-CAN bearer, wherein the bearer message containing the offload flag is known by the mobile network gateway The access type of each service data flow, and according to the access type of each service data flow, it is determined that the access type of the service data flow transmitted on any IP-CAN bearer is sent after split access, and the access type Including offload access and non-offload access, the offload flag indicates that the access type of the service data flow transmitted on the bearer is offload access; The first sending unit is configured to send a bearer message including an offload flag to the base station, so that the base station offloads the service data flow transmitted on the bearer according to the indication of the offload flag; A judging unit, configured to judge whether the base station has offload capability before the first sending unit sends the bearer message to the base station, and sends the bearer message to the base station when the base station has offload capability. 14. The mobile network management entity according to claim 13, further comprising: The canceling unit is configured to cancel the offload processing of the service data flow transmitted on the bearer by the base station if the mobile network management entity receives a message fed back by the terminal that the terminal itself does not allow offload. 15. A mobile network gateway, comprising: The learning unit is used to learn the access type of each service data flow when establishing or modifying the IP connection access network IP-CAN bearer, and the access type includes split access and non-distributed access; The second sending unit is used to send the mobile network management entity to the mobile network management entity when the access type of the service data flow transmitted on any IP-CAN bearer is determined to be offload access according to the access type of each service data flow. The bearer message, using the offload flag in the bearer message to indicate that the access type of the service data flow transmitted on the bearer is offload access, so that the mobile network management entity sends the bearer message including the offload flag to the base station, so that The base station offloads the service data flow transmitted on the bearer according to the indication of the offload flag; the notification unit is used to, before the acquisition unit obtains the offload policy from the PCRF, if the mobile network gateway is establishing or modifying the IP - Whether the base station has offload capability is indicated in the session message received during the CAN session, and whether the base station has offload capability is notified to the PCRF, so that the PCRF formulates an offload strategy according to whether the base station has offload capability. 16. The mobile network gateway according to claim 15, wherein the acquiring unit comprises: An acquisition unit, configured to acquire a distribution strategy from the PCRF, the distribution strategy indicates the access type of various service data flows, and the access type includes distribution access and non-distribution access; or, The storage unit is used to store the offloading policy, the offloading policy indicates the access type of various service data flows, and the access type includes offloading access and non-offloading access.