WO2011157106A2 - Procédé, système et dispositif connexe pour implémenter un délestage de flux de données de service - Google Patents

Procédé, système et dispositif connexe pour implémenter un délestage de flux de données de service Download PDF

Info

Publication number
WO2011157106A2
WO2011157106A2 PCT/CN2011/074860 CN2011074860W WO2011157106A2 WO 2011157106 A2 WO2011157106 A2 WO 2011157106A2 CN 2011074860 W CN2011074860 W CN 2011074860W WO 2011157106 A2 WO2011157106 A2 WO 2011157106A2
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
offloading
access
service data
base station
Prior art date
Application number
PCT/CN2011/074860
Other languages
English (en)
Chinese (zh)
Other versions
WO2011157106A3 (fr
Inventor
李岩
王爽
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201180000666.1A priority Critical patent/CN102918885B/zh
Priority to PCT/CN2011/074860 priority patent/WO2011157106A2/fr
Publication of WO2011157106A2 publication Critical patent/WO2011157106A2/fr
Publication of WO2011157106A3 publication Critical patent/WO2011157106A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/09—Management thereof
    • H04W28/0925—Management thereof using policies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections

Definitions

  • the present invention relates to the field of mobile communication technologies, and in particular, to a method, system and related apparatus for implementing traffic data flow offloading.
  • IPPA Local IP Access
  • SIPTO Selected IP Traffic Offload
  • IP data offload can be applied not only to the HeNB network, but also to the macro network, that is, the specific IP service data stream is offloaded from the radio side to save transmission resources. Therefore, an IP data shunting technology based on macro network is also proposed, in order to select a better path for IP traffic.
  • IP traffic data offloading in the prior art can alleviate the load and transmission cost of the core network, when the service data stream is directly accessed from the HeNB or the eNB to the packet data network, the security and stability of the access process are poor.
  • stream-based IP data offloading is required.
  • the so-called flow level-based IP data offloading is to split a part of the service data stream, so that the part of the service data stream is directly accessed from the HeNB or the eNB to the packet data network, and another part of the service data stream still needs to be accessed through the core network.
  • a packet data network In a packet data network.
  • Embodiments of the present invention provide a method, system, and related apparatus for implementing traffic data flow offloading to provide a flow level based IP data offload solution.
  • a method for implementing traffic data flow offloading including:
  • the mobile network gateway learns each The access type of the service data stream, the access type includes a split access and a non-offload access; when the mobile network gateway determines the service data stream transmitted on any one of the IP-CAN bearers according to the access type of each service data stream
  • the access type is the offload access
  • the bearer message including the offloading flag is sent, and the network entity that receives the bearer message and performs the data offloading operation transmits the service on the bearer according to the indication of the offloading flag.
  • the data stream is offloaded, and the offloading flag indicates that the access type of the service data stream transmitted on the bearer is a split access.
  • a system for implementing service data flow offloading comprising: a mobile network gateway and a network entity performing data offloading operations, where
  • the mobile network gateway is configured to learn an access type of each service data flow when establishing or modifying an IP-CAN bearer, and determine a service transmitted on any one of the IP-CAN bearers according to an access type of each service data flow.
  • the access type of the data stream is the offload access
  • the bearer message including the offloading flag is sent, and the offloading flag in the bearer message indicates that the access type of the service data stream transmitted on the bearer is a split access.
  • the access type includes a split access and a non-offload access;
  • the network entity performing the data offloading operation is configured to receive the bearer message, and perform traffic offloading on the bearer on the bearer according to the indication of the offloading flag.
  • a mobile network management entity including:
  • a first receiving unit configured to receive a bearer message that is sent by the mobile network gateway and that includes a offloading flag when the IP connection is accessed or modified, where the bearer message including the offloading flag is learned by the mobile network gateway.
  • the access type of each service data flow and determining, according to the access type of each service data flow, that the access type of the service data stream transmitted on any one of the IP-CAN bearers is sent after the split access, the access type And including the offloaded access and the non-striped access, where the offloading flag indicates that the access type of the service data stream transmitted on the bearer is a split access;
  • the first sending unit is configured to send, to the base station, a bearer message that includes the offloading flag, so that the base station performs traffic offloading on the bearer according to the indication of the offloading flag.
  • a mobile network gateway comprising:
  • the learning unit is configured to learn, when establishing or modifying an IP connection access network IP-CAN bearer, an access type of each service data flow, where the access type includes a split access and a non-split access;
  • a second sending unit configured to determine, when the access type of the service data stream transmitted on any one of the IP-CAN bearers is a split access according to an access type of each service data flow, to the mobile network management
  • the entity sends a bearer message including a offloading flag, and the offloading flag in the bearer message indicates that the access type of the service data stream transmitted on the bearer is a split access, so that the mobile network management entity sends the shunting flag to the base station.
  • the bearer message is configured to enable the base station to offload the service data stream transmitted on the bearer according to the indication of the offloading flag.
  • the traffic distribution policy indicates the access type of the service data flow, and the access type includes the traffic distribution and the non-striped access.
  • the PGW or the GGSN learns the connection of each service data flow according to the traffic distribution policy.
  • the inbound type notifies the base station of the access type of the service data stream transmitted on a certain bearer. If the access type is the offload access, the base station performs the offload processing on the current service data stream according to the indication of the access type.
  • FIG. 1 is a flowchart of an embodiment of a method for implementing service data flow offloading according to the present invention
  • FIG. 2 is a flowchart of another embodiment of a method for implementing service data flow splitting according to the present invention
  • FIG. 5 is another signaling flowchart of an embodiment of a method for implementing service data flow offloading according to the present invention
  • FIG. 6 is a flowchart of another embodiment of a method for implementing service data flow offloading according to the present invention
  • FIG. 7 is a signaling flowchart of another embodiment of a method for implementing service data flow offloading according to the present invention
  • FIG. 8 is another flow chart of another embodiment of a method for implementing service data flow offloading according to the present invention.
  • FIG. 9 is a structural diagram of an embodiment of a system for implementing service data flow offloading according to the present invention.
  • 10 is a structural diagram of an embodiment of a mobile network management entity according to the present invention.
  • FIG. 11 is a structural diagram of another embodiment of a mobile network management entity according to the present invention.
  • FIG. 12 is a mobile network management entity according to the present invention;
  • FIG. 13 is a structural diagram of an embodiment of a mobile network gateway according to the present invention.
  • a stream level IP data offload solution is implemented in a 3G network.
  • FIG. 1 is a flow diagram of an embodiment of a method for implementing traffic data flow offloading according to the present invention, including the following steps:
  • Step 101 When establishing or modifying an IP connection to access a network IP-CAN bearer, the mobile network gateway learns an access type of each service data flow, where the access type includes a split access and a non-offload access;
  • IP-Connectivity Access Network Bearer is a set of network entities and interfaces that implement communication between the UE and an IMS (IP Multimedia System) entity through IP.
  • IMS IP Multimedia System
  • An example is GPRS (General Packet Radio Service). This term is commonly used in the context of a cell to represent a 3GPP access network, such as GPRS or EDGE (Enhanced Data Rate for GSM Evolution), but can also be used to describe WLAN (Wireless Local Area Networks, wireless). Local area network) or DSL (Digital Subscriber Line) network. It is introduced as a generic term in 3GPP IMS, representing any IP-based access network and focusing on the separation of access and service networks.
  • IP-CAN bearers define IP transmission channels for attributes such as speed, delay, and bit error rate (BER).
  • the IP-CAN bearer is an EPS bearer
  • the IP-CAN bearer is a PDP (Packet Data Protocol) context.
  • the mobile network gateway obtains a traffic off policy from a PCRF (Policy and Charging Rules Function) or the mobile network gateway itself stores a traffic splitting policy, where the traffic splitting policy indicates the connection of various service data flows.
  • the access type includes offload access and non-split access.
  • Step 102 When the mobile network gateway determines, according to the access type of each service data flow, that the access type of the service data stream transmitted on any one of the IP-CAN bearers is a split access, the bearer message including the offloading flag is sent, so that And the network entity that receives the bearer message and performs the data offloading operation, according to the indication of the offloading flag, offloading the service data stream transmitted on the bearer, where the offloading flag indicates the service data stream transmitted on the bearer
  • the access type is split access.
  • the mobile network gateway obtains a traffic off policy from the policy and charging rule function PCRF or the mobile network gateway itself stores a traffic off policy.
  • the method further comprises: before the mobile network gateway acquires the offload policy from the PCRF, if the mobile network gateway indicates the receiving station in the session message received when establishing or modifying the IP-CAN session Whether the network entity carrying the message and performing the data offloading operation has a traffic offloading capability, and the mobile network gateway notifies the PCRF whether the network entity has a traffic off capability, so that the PCRF determines whether the network entity has a traffic offloading capability according to whether the network entity has a traffic offloading capability.
  • the mobile network gateway sends a bearer message that includes a offloading flag, so that the network entity that receives the bearer message and performs the data offloading operation transmits the bearer on the bearer according to the indication of the offloading flag.
  • the traffic of the service data flow can be specifically as follows:
  • the mobile network gateway sends a bearer message including the offloading flag to the base station by the mobile network management entity, so that the base station performs traffic offloading on the bearer according to the indication of the offloading flag.
  • the method further includes: 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 a traffic off capability, and the mobile network gateway moves by The network management entity sends the bearer message including the offloading flag to the base station: when the base station has the offloading capability, the mobile network management entity sends the bearer message to the base station.
  • the method further includes: if the mobile network management entity receives a message fed back by the terminal indicating that the terminal does not allow the offloading, the mobile network management entity cancels the base station A shunting process for a traffic data stream transmitted on the bearer.
  • the method further includes: before the mobile network gateway acquires the offloading policy from the PCRF, if the mobile network gateway is establishing or The session message received during the modification of 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 the offload policy according to whether the base station has the offload capability.
  • 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 the 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.
  • the mobile network gateway is a packet data network gateway PGW
  • the mobile network management entity is a mobility management entity MME.
  • the bearer message received by the MME is a create bearer request message or a modify bearer response message
  • the bearer message sent by the MME is a create/modify bearer request message.
  • the mobile network gateway is a GPRS gateway support node GGSN
  • the mobile network management entity is a GRRS service support node.
  • the bearer message received by the SGSN is a context creation response
  • the bearer message sent by the SGSN is a radio bearer allocation request.
  • the traffic distribution policy indicates the access type of each type of service data flow, and the access type includes the split access and the non-split access, and the mobile network gateway learns the connection of each service data flow according to the offload policy. If the access type of the service data stream transmitted on a certain bearer is a split access, the mobile network gateway sends a bearer message including the offloading flag, so that the network entity that receives the bearer message and performs the offloading operation learns the access type. The traffic is split and the traffic data transmitted on the bearer is offloaded according to the indication.
  • Embodiment 2 Embodiment 2
  • the PGW (PDN GateWay, Packet Data Network Gateway) obtains a traffic offloading policy from the PCRF, and the traffic splitting policy indicates the access type of various service data flows.
  • the access type includes the split access and the non-split access.
  • the PGW indicates the services transmitted on the bearer in the process of establishing the bearer.
  • the access type of the data stream Referring to FIG. 2, it is a flowchart of another embodiment of a method for implementing traffic data flow offloading according to the present invention, including the following steps:
  • Step 201 The PGW learns the access type of each service data flow according to the traffic splitting policy, and determines, when the access type of the service data flow transmitted on any one of the IP-CAN bearers is the split access according to the access type of each service data flow. And sending, by the serving gateway SGW, the mobile switching center MME to create a bearer request or modify a bearer response, where the traffic splitting policy indicates the access type of each type of service data flow, where the access type includes the split access and Non-split access, the offloading flag indicates that the access type of the service data stream transmitted on the bearer is a split access;
  • the so-called “diverted access” means that the base station directly accesses the user's service data stream to the routing device of the packet data network.
  • the router in the Internet does not pass through the core network of the operator
  • non-split access refers to The base station passes the user's service data through the operator's core network, for example, the SGW and the PGW in the core, and then accesses the packet data network.
  • the PGW may obtain the offloading 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, and receive a create session or modify the bearer at the PGW. At the request, an IP CAN session creation or modification request is sent to the PCRF, and the PCRF carries the offload policy in the returned IP CAN session creation or modification response. In addition, the PGW can also store its own traffic split strategy.
  • the traffic splitting policy in the PCRF can record various service data flows and their corresponding access types in a list. Of course, it can also be recorded in other manners.
  • the embodiment of the present invention does not limit the recording form of the traffic distribution policy.
  • the type of the access type of the service data stream can be determined by the user subscription information, the network status, or the operation policy of the operator. Not limited.
  • the service data flows with the same demand are transmitted on the same bearer.
  • the service data flows with the same Qos requirements are transmitted on the same bearer. Therefore, after the PGW learns the access type of each service data flow according to the traffic distribution policy, the service data flow with the same access type can be transmitted on the same bearer.
  • the Qos of the service data flow is also considered, Put business data streams with the same access type and the same QoS requirements in the same Loaded on the transmission.
  • the PGW learns that the access type of the service data flows a, b, and c is the split access according to the traffic splitting policy, and the access type of the service data flows d and e is the non-split access.
  • Type the PGW allocates the service data streams a, b, and c to the bearer 1, and transmits it by the bearer 1, and distributes the service data streams e and d to the bearer 2, and transmits it by the bearer 2.
  • the PGW allocates the service data flow whose access type is the split access to the bearer that meets the high QoS requirement, or allocates the service data flow whose access type is the non-split access to the satisfaction. High Qos demand on the bearer.
  • Step 202 The MME sends a create/modify bearer request that includes the offloading flag to the base station.
  • the offloading flag indicates that the access type of the service data stream transmitted on a certain bearer is a split access, and the base station can perform the offload processing on the service data stream transmitted on the bearer according to the existing offload processing manner, and the bearer is processed in the bearer.
  • the method of the offloading process adopted by the base station is not specifically limited in the embodiment of the present invention.
  • the PGW sends the non-offload to the mobile switching center MME through the serving gateway SGW.
  • the MME sends a create bearer request including the non-split flag to the base station, in step 204, the base station performs non-split processing on the service data stream transmitted on the bearer according to the existing non-split processing manner, and accesses the service data stream transmitted on the bearer through the core network.
  • the method for non-split processing adopted by the base station in the embodiment of the present invention is also not specifically limited.
  • the above embodiment is implemented in the case where all base stations in the system have the offload capability. If the system is upgraded, there will be such a scenario: some base stations have the offload capability, while others have no offload capability.
  • some base stations have the offload capability, while others have no offload capability.
  • the base station performs offload processing on the data.
  • the access type of the service data stream transmitted on any one of the IP-CAN bearers is a split access, and the MME determines whether the base station has the offload capability, and sends the create/modify bearer request to the base station when the base station has the offload capability.
  • the MME may be configured with information about whether each base station has a traffic off capability, and the MME directly learns from the locally configured information whether each base station has a traffic off capability.
  • information about whether each base station has a traffic off capability may be configured in an external database, and the MME invokes information in the external database to know whether each base station has a traffic off capability.
  • the terminal may further consider whether the terminal allows the offloading. If the terminal allows, the MME may cancel the offloading process of the service data stream transmitted by the base station on the bearer according to the intention of the terminal.
  • the method further includes: when the terminal establishes a session management or establishes a bearer process, the base station feeds back to the MME whether the traffic is allowed to be offloaded by the base station, and the MME cancels the base station pair on the bearer when the terminal does not allow the offloading.
  • the shunting of the transmitted service data stream when the terminal establishes a session management or establishes a bearer process, the base station feeds back to the MME whether the traffic is allowed to be offloaded by the base station, and the MME cancels the base station pair on the bearer when the terminal does not allow the offloading. The shunting of the transmitted service data stream.
  • the setup bearer request sent by the MME to the base station includes a offloading flag.
  • the radio resource control connection reconfiguration request sent by the base station to the terminal includes a shunting flag. , so that the terminal is informed that it needs to be offloaded.
  • the radio resource control connection reconfiguration response fed back to the base station by the terminal includes an permission flag or a non-permission flag, the permission flag indicates that the terminal allows the offload, and the non-permission flag indicates that the terminal does not allow the offload.
  • the base station sends a setup bearer response to the MME, the permission flag or the non-permission flag is included in the setup bearer response.
  • a session management request is encapsulated in the setup bearer request sent by the MME to the base station, where the session management request includes a offloading flag.
  • the base station obtains a session management request including a offloading flag by decapsulating, and sends the session management request to the terminal, so that the terminal knows that the offloading process is to be performed.
  • the radio resource control connection reconfiguration is performed between the base station and the terminal, the radio resource control connection reconfiguration response fed back to the base station by the terminal includes an allowable flag or a non-permitted flag.
  • the MME cancels the offloading process of the current service data stream by the eNB according to the intention of the terminal, where there are two cases: the MME cancels the offloading process performed by the base station on the current service data stream, or the MME is in the base station pair.
  • the current service data stream is canceled before the offloading process is performed. If the offloading policy is set by the PCRF, the PGW obtains the offloading policy from the PCRF.
  • the PW Before the PGW obtains the offloading policy from the PCRF, the PW is first notified of whether the base station has the offloading capability, so that the PCRF formulates the offloading policy according to the content of the notification.
  • the splitting strategy formulated by the PCRF can be considered to take into account the offloading capability of each base station, thereby enabling the data offload to be successfully completed.
  • the MME since the shunting strategy formulated by the PCRF has considered the offloading capability of each base station, the MME does not need to determine whether the base station has the offloading capability even if there are some base stations having the offloading capability and the other base stations do not have the offloading capability.
  • the method further includes: before the PGW obtains the offload policy from the PCRF, if the base station indicates whether the base station has the offload capability in the request for creating the session or modifying the bearer received by the PGW, the PGW whether the base station has the offload capability The PCRF is notified so that the PCRF formulates a traffic off policy according to whether the base station has a traffic off capability.
  • the traffic splitting policy indicates the access type of each type of service data flow, and the access type includes the split access and the non-split access.
  • the PGW learns the access type of each service data flow according to the split policy. And determining, according to the access type of each service data flow, an access type of the service data stream transmitted on a certain bearer, and if the access type of the service data stream transmitted on the bearer is a split access, the PGW notifies the base station
  • the access type is the offload access, and the base station performs the offload processing on the service data stream transmitted on the bearer according to the indication.
  • the MME determines whether the base station has the offload capability, and when the base station has the offload capability, notifies the base station that the access type is offloaded. Accessing, so that the base station performs offload processing on the service data stream transmitted on the bearer according to the indication.
  • the terminal feeds back to the MME whether the traffic is allowed to be offloaded by the base station in the process of establishing the session management or the establishment of the bearer, so that the MME can cancel the offloading process of the service data stream transmitted by the base station on the bearer when the terminal does not allow the offloading.
  • Embodiment 3
  • FIG. 3 is a signaling flowchart of an embodiment of a method for implementing service data flow offloading, 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 The MME sends a create session request message to the SGW.
  • the MME can learn whether the current base station has the offload capability according to the local configuration or whether the base station has the information of the offload capability stored in the external database, and indicates whether the current base station has the offload capability in the create session request.
  • Step 304 The SGW sends a create session request message to the PGW.
  • the creation session request sent by the MME to the SGW indicates whether the current base station has the offload capability
  • the creation session request sent by the SGW to the PGW also indicates whether the current base station has the offload capability.
  • Step 305 After receiving the create session request message, the PGW sends an IP CAN session establishment request message to the PCRF.
  • the IP CAN session establishment request message sent by the PGW to the PCRF also indicates whether the current base station has the offload capability.
  • the PCRF can further formulate a traffic off policy according to whether the current base station has a traffic off capability. Since the shunting strategy established by the PCRF has considered the shunting capability of each base station, the data shunting is successfully completed.
  • Step 306 The PCRF sends an IP CAN session establishment response message including a traffic off policy to the PGW.
  • the traffic distribution policy indicates the access type of each type of service data flow, and the access type includes the split access and the non-offload access.
  • Step 307 The PGW learns the access type of each service data flow according to the offloading policy, and sends a create bearer request message including the offloading flag to the SGW, where the offloading flag indicates that the access type of the service data stream transmitted on a certain bearer is offloaded.
  • Step 308 The SGW sends a create bearer request message that includes the offloading flag to the MME.
  • Step 310 If the current base station has the offloading capability, the MME sends a create bearer request message including the offloading flag to the current base station, and sends a session management request message to the current base station, where the session management request message is encapsulated in the create bearer request message;
  • Step 311 The current base station parses the session management request message, and sends the session management request message to the terminal.
  • Step 312 The radio resource control connection reconfiguration process is completed 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.
  • steps 313 and 314 have no strict sequence in execution, and may also send a session management response message and then send a create bearer response message.
  • Step 315 After the bearer is established, the current base station performs a traffic shunting process on the current service data flow according to the offloading flag.
  • the base station performs a NAT (Network Address Translation) operation on the uplink packet of the radio bearer, and forwards the received downlink packet on the radio bearer.
  • NAT Network Address Translation
  • the base station Before sending the uplink packet to the packet network router, the base station modifies the source address of the packet sent by the terminal to the address of the base station.
  • the port number of the packet is further modified to be another port, and the base station records the mapping relationship, that is, the mapping relationship between the source address, the source port, the modified address, and the port of the uplink.
  • the base station sends the uplink message to the packet network router.
  • the destination address of the packet is the address of the base station, so the packet is routed to the base station, and the base station knows which terminal the message is sent to according to the recorded mapping relationship. After the address and port number of the message, the message is sent to the terminal.
  • the purpose of the NAT operation is: If the source address of the packet sent by the terminal is not modified, the terminal address is allocated to the terminal by the PGW, so the packet is routed to the PGW, which causes the terminal to send the packet to be offloaded.
  • the received message is non-split, so the above NAT operation needs to be performed.
  • Step 316 The MME sends a create bearer response message to the SGW.
  • Step 317 The SGW sends a create bearer response message to the PGW.
  • a splitting policy is defined at the PCRF, and the splitting policy indicates the access type of each type of service data flow, and the access type includes a split access and a non-split access, and the PGW obtains from the PCRF.
  • the traffic splitting policy is used to learn the access type of each service data flow according to the traffic splitting policy, and notify the MME of the access type of the service data flow transmitted on a certain bearer, if the access type of the service data flow transmitted on the bearer is
  • the MME is further configured to determine whether the current base station has a traffic offloading capability.
  • the MME When the current base station has a traffic offloading capability, the MME notifies the base station that the service data flow on the bearer is to be subjected to offload processing, and the base station performs the service transmitted on the bearer according to the indication.
  • the data stream is offloaded.
  • FIG. 4 another signaling flowchart of an embodiment of a method for implementing service data flow offloading according to the present invention 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 The MME sends a create session request message to the SGW.
  • Step 404 The SGW sends a create session request message to the PGW.
  • Step 405 After receiving the create session request message, the PGW sends an IP CAN session establishment request message to the PCRF.
  • Step 406 The PCRF sends an IP CAN session establishment response message including a traffic off policy to the PGW.
  • Step 407 The PGW learns the access type of each service data flow according to the offloading policy, and sends a create bearer request message including the offloading flag to the SGW, where the offloading flag indicates that the access type of the service data stream transmitted on a certain bearer is offloaded.
  • Step 408 The SGW sends a create bearer request message that includes the offloading flag to the MME.
  • Step 410 If the current base station has the offloading capability, the MME sends a create bearer request message including the offloading flag to the current base station, and sends a session management request message including the offloading flag to the current base station, where the session management request message is encapsulated and created. Bearer request message;
  • the terminal can know that the bearer needs to be offloaded.
  • Step 411 The current base station parses the session management request message, and sends a session management request message including the offloading flag to the terminal.
  • Step 412 The radio bearer control reconfiguration process is completed between the current base station and the terminal, where the terminal sends a radio resource control connection reconfiguration response message indicating whether it is allowed to be offloaded to the current base station;
  • the radio resource control connection reconfiguration request message sent by the current base station to the terminal includes a shunting flag, so that the terminal can be notified.
  • Step 413 The current base station sends a create bearer response message to the MME.
  • Step 414 When the terminal does not allow the offloading, the current base station sends a session management response message including the non-permitted flag to the MME.
  • steps 413 and 414 have no strict sequence in execution, and may also send a session management response message and then send a create bearer response message.
  • Step 415 After the bearer is established, the current base station performs traffic offloading on the service data stream transmitted on the bearer according to the offloading flag.
  • the current base station performs a NAT operation on the uplink packet of the radio bearer, and forwards the received downlink packet on the radio bearer.
  • Step 416 The MME sends a create bearer response message to the SGW.
  • Step 417 The SGW sends a create bearer response message to the PGW.
  • Step 418 When the MME learns that the terminal does not allow the offload according to the non-permitted flag, the MME sends the current base station The modify bearer request message is sent to cancel the offloading process currently being performed by the base station.
  • a splitting policy is defined at the PCRF, and the splitting policy indicates the access type of each type of service data flow, and the access type includes a split access and a non-split access, and the PGW obtains from the PCRF.
  • the traffic splitting policy is used to learn the access type of each service data flow according to the traffic splitting policy, and notify the MME of the access type of the service data flow transmitted on a certain bearer, if the access type of the service data flow transmitted on the bearer For the offloading, the MME further determines whether the current base station has the offloading capability. When the current base station has the offloading capability, the MME notifies the base station that the service data stream transmitted on the bearer is to be offloaded, and the base station follows the indication on the bearer. The transmitted traffic data stream is offloaded.
  • the terminal learns that the offloading process is to be performed, the terminal also feeds back to the MME whether it is allowed to perform the offloading.
  • the MME learns that the terminal does not allow the offloading, the offloading process on the current base station is cancelled.
  • FIG. 5 it is another signaling flowchart of an embodiment of a method for implementing service data flow splitting, 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 The MME sends a modify bearer request message to the SGW.
  • the MME can know whether the target base station has the offload capability according to the local configuration or whether the base station stored in the external database has the information of the offload capability, and indicates whether the target base station has the offload capability in the modify bearer request.
  • Step 504 The SGW sends a modify bearer request message to the PGW.
  • the SGW sends the setup bearer request to the PGW to indicate whether the target base station has the offload capability.
  • Step 505 After receiving the modify bearer request message, the PGW sends an IP CAN session modification request message to the PCRF.
  • 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 a traffic off policy according to whether the target base station has the offload capability. Since the shunting policy specified by the PCRF has considered the shunting capability of each base station, the data shunting is successfully completed.
  • Step 506 The PCRF sends an IP CAN session modification response message including a traffic off policy to the PGW.
  • the traffic distribution policy indicates the access type of each type of service data flow, and the access type includes the split access and the non-offload access.
  • Step 507 The PGW learns the access type of each service data flow according to the offloading policy, and sends a modified bearer response message including the offloading flag to the SGW, where the offloading flag indicates that the access type of the service data stream transmitted on a certain bearer is tapped.
  • Step 508 The SGW sends a modify bearer response message that includes the offloading flag to the MME.
  • this step can also be omitted.
  • Step 510 If the target base station has the offload capability, the MME sends a create bearer request message including the offloading flag to the target base station, and 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 parses 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 514 The target base station sends a session management response message to the MME.
  • steps 513 and 514 have no strict sequence in execution, and may also send a session management response message and then send a create bearer response message.
  • Step 515 After the bearer is established, the target base station performs a traffic shunting process on the current service data flow according to the offloading flag.
  • Step 516 The MME sends a create bearer response message to the SGW.
  • Step 517 The SGW sends a create bearer response message to the PGW.
  • the MME may further consider whether the terminal itself has the offload capability, and cancel the offloading process of the target terminal if the target base station has the offload capability and the terminal does not have the offload capability.
  • 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 know that the target base station has the offload capability.
  • the radio resource control sent by the terminal to the base station indicates from the configuration response message whether it has allowed the offloading process.
  • the radio resource control connection may also be sent to the terminal at the target base station.
  • the reconfiguration request message indicates that the current base station has a traffic offload capability.
  • a splitting policy is defined at the PCRF, and the splitting policy indicates the access type of each type of service data flow, and the access type includes a split access and a non-split access, and the PGW obtains from the PCRF.
  • the traffic splitting policy is used to learn the access type of each service data flow according to the traffic splitting policy, and notify the MME of the access type of the service data flow transmitted on a certain bearer, if the access type of the service data flow transmitted on the bearer is
  • the MME is further configured to determine whether the current base station has a traffic offloading capability.
  • the MME When the current base station has a traffic offloading capability, the MME notifies the base station that the service data flow on the bearer is to be subjected to offload processing, and the base station performs the service transmitted on the bearer according to the indication.
  • the data stream is offloaded.
  • the GGSN obtains a traffic distribution policy from the PCRF, and the traffic distribution policy indicates the access type of each service data flow, and the access type includes the traffic distribution. Access and non-split access, and indicate the access type of the current service data flow to the base station in the process of allocating the radio bearer.
  • FIG. 6 is a flowchart of another embodiment of a method for implementing traffic data flow offloading according to the present invention, including the following steps:
  • Step 601 The GGSN determines, according to the access type of each service data flow, the access class of the service data stream transmitted on any one of the IP-CAN bearers according to the access type of each service data flow.
  • the type is a split access
  • a context creation response including a offloading flag is sent to the SGSN (Serving GPRS Support Node)
  • the access type includes a split access and a non-split access
  • the offload flag indicates The access type of the service data stream transmitted on a certain bearer is a split access;
  • the GGSN obtains the offloading policy from the PCRF. For example, when the terminal camps on a new cell, the GGSN needs to create a context. When the GGSN receives the request to create a context, it sends a CCR to the PCRF, and the PCRF carries the offloading policy in the returned CCA. In addition, the GGSN may itself store a traffic splitting policy, and the traffic splitting policy indicates the access type of each type of service data flow, and the access type includes a split access and a non-offload access.
  • the recording form of the traffic distribution policy is not limited in the embodiment of the present invention.
  • the type of the access type of the service data stream may be determined by the user subscription information, the network status, or the operation policy of the operator. Not limited.
  • Step 602 The SGSN sends a radio bearer allocation request including the offloading flag to the base station.
  • the offloading flag indicates that the access type of the service data stream transmitted on a certain bearer is a split access, and the base station can perform the offload processing on the service data stream transmitted on the bearer according to the existing offload processing manner, and the bearer is processed in the bearer.
  • the method of the offloading process adopted by the base station is not specifically limited in the embodiment of the present invention.
  • the GGSN when the access type of each service data stream transmitted on a certain bearer is non-split access in step 601, the GGSN sends a context creation response including the non-split flag to the SGSN.
  • the non-split flag indicates that the access type of the current service data flow is non-split access.
  • the SGSN sends a radio bearer allocation request including the non-split flag to the base station.
  • the base station performs non-split processing on the service data stream transmitted on the bearer according to the non-split processing manner, and the service data stream transmitted on the bearer is connected to the core network according to the existing non-split processing manner.
  • the method for non-split processing adopted by the base station is not specifically limited in the embodiment of the present invention.
  • the foregoing embodiment is implemented in the case where all base stations in the system have the offload capability. If there is a scenario in the upgrade phase of the system, there are some scenarios: some base stations have a traffic off capability, while others have a traffic off capability, The sequence of the data offloading is guaranteed to be completed.
  • the access type of the service data stream transmitted on the bearer is a split access, it is necessary to determine in advance whether the base station has the offload capability, and only if the base station has the offload capability, the base station is instructed. The data is offloaded.
  • the SGSN determines whether the base station has a shunting capability, When the base station has the offload capability, the radio bearer allocation request is sent to the base station.
  • the SGSN may be configured with information about whether each base station has a traffic off capability.
  • the SGSN directly learns from the locally configured information whether each base station has a traffic offload capability.
  • information about whether each base station has a traffic off capability may be configured in an external database, and the SGSN invokes information in the external database to know whether each base station has a traffic off capability.
  • the terminal may further consider whether the terminal allows the offloading. If the terminal does not allow the SGSN, the SGSN may cancel the offloading process of the service data stream transmitted by the base station on the bearer according to the intention of the terminal.
  • the method further includes: the terminal, in the radio bearer allocation process, feeding back, by the base station, the SGSN whether the traffic is allowed to be offloaded, and the SGSN cancels the service transmitted by the base station to the bearer when the terminal does not allow the offloading.
  • the terminal in the radio bearer allocation process, feeding back, by the base station, the SGSN whether the traffic is allowed to be offloaded, and the SGSN cancels the service transmitted by the base station to the bearer when the terminal does not allow the offloading. Streaming of data streams.
  • the radio bearer allocation request sent by the SGSN to the base station includes a offloading flag.
  • the radio bearer setup request sent by the base station to the terminal includes a shunting flag, so that the terminal knows that the radio bearer is to be performed. Split processing.
  • the radio bearer response fed back to the base station by the terminal includes an allowable flag or a non-permitted flag, the allowable flag indicates that the terminal allows the offloading, and the non-permitted flag indicates that the terminal does not allow the offloading.
  • the radio bearer allocation response includes an allow flag or a non-permission flag.
  • the SGSN cancels the offloading process of the current service data stream by the base station according to the intention of the terminal, where there are two cases: the SGSN cancels the offloading process performed by the base station on the current service data stream, or The SGSN cancels the offloading operation before the base station performs the offload processing on the current service data stream.
  • a traffic off policy is established at the PCRF or a traffic split policy is stored at the GGSN, where the traffic splitting policy indicates the access type of each type of service data flow, and the access type includes the split access and the non-offload.
  • the GGSN obtains the traffic splitting policy from the PCRF or obtains the traffic splitting policy on its own, and learns the access type of each service data flow according to the traffic splitting policy. If the access type of the service data flow transmitted on a certain bearer is the split access, the GGSN The base station is notified that the access type is a split access, and the base station performs the offload processing on the service data stream transmitted on the bearer according to the indication.
  • Another signaling flowchart of another embodiment of a method for implementing service data flow offloading according to the present invention includes the following steps:
  • Step 701 The terminal sends a create context request message to the SGSN by using the current base station.
  • Step 702 The SGSN sends a create context request message to the GGSN.
  • Step 703 After receiving the create context request message, the GGSN sends a CCR message to the PCRF.
  • Step 704 The PCRF sends a CCA message including a traffic off 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 including the offload flag to the SGSN.
  • Step 706 The SGSN determines whether the current base station has a traffic off 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 The 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 offloading flag.
  • a traffic off policy is established at the PCRF or a traffic split policy is stored at the GGSN, where the traffic splitting policy indicates the access type of each type of service data flow, and the access type includes the split access and the non-offload.
  • the GGSN obtains the offloading policy from the PCRF or obtains the offloading policy on its own, and learns the access type of each service data flow according to the offloading policy, and notifies the SGSN of the access type of the service data stream transmitted on a certain bearer, if The access type of the service data stream transmitted on the bearer is a split access, and the SGSN further determines whether the current base station has the offload capability.
  • the SGSN When the current base station has the offload capability, the SGSN notifies the base station of the service data stream transmitted on the bearer. The offloading process is performed, and the base station performs a traffic off process on the service data stream transmitted on the bearer according to the indication.
  • another signaling flowchart of another embodiment of a method for implementing service data flow offloading according to the present invention includes the following steps:
  • Step 801 The terminal sends a create context request message to the SGSN by using the current base station.
  • Step 802 The SGSN sends a create context request message to the 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 including a traffic off policy to the GGSN.
  • Step 805 The GGSN learns the access type of each service data flow according to the offloading policy, and sends a create context response message including the offloading flag to the SGSN, where the offloading flag indicates that the access type of the service data stream transmitted on a certain bearer is offloaded.
  • Step 806 The SGSN determines whether the current base station has a traffic off 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, where the current base station sends the radio bearer to the terminal. Sending a radio bearer request message including a offloading flag, when the terminal does not allow the offloading, the terminal sends a setup radio bearer response message including the non-permitted flag to the current base station;
  • Step 809 The current base station sends a radio bearer allocation response message including a non-permitted flag to the SGSN.
  • Step 810 The 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 offloading flag.
  • Step 812 The SGSN sends a radio bearer modification request message to the current base station according to the non-permitted flag, and cancels the offloading process that the current base station is performing.
  • a traffic off policy is established at the PCRF or a traffic split policy is stored at the GGSN, where the traffic splitting policy indicates the access type of each type of service data flow, and the access type includes the split access and the non-offload.
  • the PGW obtains a traffic off policy from the PCRF, and learns the access type of the current service data flow according to the traffic splitting policy, and notifies the SGSN of the access type of the service data flow transmitted on a certain bearer, if transmitted on the bearer.
  • the access type of the service data stream is a split access, and the SGSN further determines whether the current base station has a traffic offloading capability.
  • the SGSN When the current base station has a traffic offloading capability, the SGSN notifies the base station that the service data stream transmitted on the bearer is to be split-accessed. The base station performs a traffic off process on the service data stream transmitted on the bearer according to the indication.
  • the terminal learns that the offload processing is to be performed, the terminal feeds back to the SGSN whether it is allowed.
  • the SGSN learns that the terminal does not allow the offloading, the offloading process on the current base station is cancelled.
  • FIG. 9 is a structural diagram of an embodiment of a system for implementing service data flow offloading, including: a mobile network gateway 901 and a network entity 902 that performs a data offloading operation, where
  • the mobile network gateway 901 is configured to learn the access type of each service data flow when establishing or modifying the IP-CAN bearer, and determine the service data transmitted on any one of the IP-CAN bearers according to the access type of each service data flow.
  • the access type of the flow is the offload access
  • the bearer message including the offloading flag is sent, and the traffic data transmitted on the bearer is indicated by the offloading flag in the bearer message.
  • the access type is a split access, and the access type includes a split access and a non-offload access.
  • the network entity 902 that performs the data offloading operation is configured to receive the bearer message, according to the indication of the offloading flag, The traffic data stream transmitted on the bearer is offloaded.
  • the system further includes: a mobile network management entity, configured to determine, before sending the bearer message to the network entity, whether the network entity has a traffic off capability, and when the network entity has a traffic off capability, The network entity sends the bearer message.
  • a mobile network management entity configured to determine, before sending the bearer message to the network entity, whether the network entity has a traffic off capability, and when the network entity has a traffic off capability, The network entity sends the bearer message.
  • the mobile network management entity 902 is further configured to: when receiving the message that the terminal itself does not allow the offloading, the network entity cancels the offloading process of the service data stream transmitted on the bearer.
  • the mobile network gateway 901 includes: an obtaining unit, configured to obtain a traffic offloading policy from the PCRF; or a storage unit, configured to store a traffic offloading policy, where the traffic splitting policy indicates an access type of each type of service data flow, where The access types include split access and non-offload access.
  • the mobile network gateway 901 further includes: a notifying unit, configured to: before the acquiring unit acquires the offloading policy from the PCRF, if the mobile network gateway indicates the base station in the session message received when establishing or modifying the IP-CAN session Whether there is a traffic off capability, the base station is notified of whether the base station has a traffic off capability, so that the PCRF formulates a traffic off policy according to whether the base station has a traffic off capability.
  • the mobile network gateway is a packet data network gateway PGW
  • the mobile network management entity is a mobility management entity MME
  • the mobile network gateway is a GPRS gateway support node GGSN
  • the mobile network management entity is a GRRS Service support node.
  • the bearer message received by the MME is a create bearer request or a modify bearer response
  • the bearer message sent by the MME is a create/modify bearer request
  • the bearer message received by the SGSN is a context creation response
  • the bearer message sent by the SGSN is a radio bearer allocation request.
  • the traffic distribution policy indicates the access type of each type of service data flow, and the access type includes the split access and the non-split access, and the mobile network gateway learns the connection of each service data flow according to the offload policy.
  • Incoming type if the access type of the service data stream transmitted on a certain bearer is a split access, the access type is the offload access notification to the mobile network management entity, and the mobile network management entity notifies the base station to transmit on the bearer.
  • the service data stream is subjected to offload processing, and the base station processes the service data stream transmitted on the bearer according to the indication.
  • the mobile network management entity further determines whether the current base station has a traffic offloading capability. When the current base station has a traffic offloading capability, it notifies the base station that the service data stream transmitted on the bearer is to be offloaded.
  • the terminal After the terminal learns that the offloading process is to be performed, the terminal also feeds back to the mobile network management entity whether it allows the offloading. When the mobile network management entity learns that the terminal does not allow the offloading, the offloading process on the current base station is cancelled. Example ten
  • the invention also provides a mobile network management entity.
  • FIG. 10 it is a structural diagram of an embodiment of a mobile network management entity according to the present invention, including: a first receiving unit 1001 and a first sending unit 1002, where
  • the first receiving unit 1001 is configured to receive, by the mobile network gateway, a bearer message that is sent by the mobile network gateway, where the offloading flag is included, when the IP connection is received or modified, where the bearer message including the offloading flag is a mobile network gateway.
  • the first sending unit 1002 is configured to send, to the base station, the bearer message that includes the offloading flag, so that the base station, according to the indication of the offloading flag, offloads the service data stream transmitted on the bearer.
  • FIG. 11 is a structural diagram of another embodiment of a mobile network management entity according to the present invention.
  • the mobile network management entity further includes: a determining unit 1003, configured to: at the first sending unit Before the base station sends the bearer message, it is determined whether the base station has a offload capability, and the bearer message is sent to the base station when the base station has a offload capability.
  • the mobile network management entity further includes: a canceling unit, configured to cancel, if the mobile network management entity receives a message that the terminal does not allow the offloading by the terminal, cancel the service transmitted by the base station to the bearer Streaming of data streams.
  • a canceling unit configured to cancel, if the mobile network management entity receives a message that the terminal does not allow the offloading by the terminal, cancel the service transmitted by the base station to the bearer Streaming of data streams.
  • the traffic distribution policy indicates the access type of each type of service data flow, and the access type includes the split access and the non-split access, and the mobile network gateway learns each according to the split strategy.
  • the access type of the service data stream if the access type of the service data stream transmitted on a certain bearer is a split access, the access type is the offload access notification to the mobile network management entity, and the mobile network management entity notifies the base station
  • the service data stream transmitted on the bearer is subjected to offload processing, and the base station processes the service data stream transmitted on the bearer according to the indication.
  • the mobile network management entity further determines whether the current base station has a traffic offloading capability. When the current base station has a traffic offloading capability, it notifies the base station that the service data stream transmitted on the bearer is to be subjected to the offloading process.
  • the terminal After the terminal learns that the offloading process is to be performed, the terminal also feeds back to the mobile network management entity whether it allows the offloading. When the mobile network management entity learns that the terminal does not allow the offloading, the offloading process on the current base station is cancelled.
  • the invention also provides a mobile network gateway.
  • FIG. 12 it is a structural diagram of an embodiment of a mobile network gateway according to the present invention, including: a learning unit 1201 and a second sending unit 1202, where
  • the learning unit 1201 is configured to learn, when establishing or modifying an IP connection access network IP-CAN bearer, an access type of each service data flow, where the access type includes a split access and a non-split access; and the second sending unit 1202 And, when determining, according to the access type of each service data flow of the learning unit 1201, that the access type of the service data stream transmitted on any one of the IP-CAN bearers is a split access, sending the split network identifier to the mobile network management entity.
  • the learning unit 1201 includes: an obtaining unit, configured to obtain a traffic offloading policy from the PCRF; or a storage unit, configured to store a trafficking policy, where the trafficking policy indicates an access type of each type of service data flow, where the Incoming types include offload access and non-split access.
  • the mobile network gateway further comprises: a notifying unit, configured to: before the acquiring unit obtains the offloading policy from the PCRF, if the mobile network gateway is establishing or The base station indicated in the session message received when modifying the IP-CAN session indicates the base station Whether there is a traffic off capability, the base station is notified of whether the base station has a traffic off capability, so that the PCRF formulates a traffic off policy according to whether the base station has a traffic off capability.
  • a notifying unit configured to: before the acquiring unit obtains the offloading policy from the PCRF, if the mobile network gateway is establishing or The base station indicated in the session message received when modifying the IP-CAN session indicates the base station Whether there is a traffic off capability, the base station is notified of whether the base station has a traffic off capability, so that the PCRF formulates a traffic off policy according to whether the base station has a traffic off capability.
  • the traffic distribution policy indicates the access type of each type of service data flow, and the access type includes the split access and the non-split access, and the mobile network gateway learns the connection of each service data flow according to the offload policy.
  • Incoming type if the access type of the service data stream transmitted on a certain bearer is a split access, the access type is the offload access notification to the mobile network management entity, and the mobile network management entity notifies the base station to transmit on the bearer.
  • the service data stream is subjected to offload processing, and the base station processes the service data stream transmitted on the bearer according to the indication.
  • the mobile network management entity further determines whether the current base station has a traffic offloading capability. When the current base station has a traffic offloading capability, it notifies the base station that the service data stream transmitted on the bearer is to be subjected to the offloading process.
  • the terminal After the terminal learns that the offloading process is to be performed, the terminal also feeds back to the mobile network management entity whether it allows the offloading. When the mobile network management entity learns that the terminal does not allow the offloading, the offloading process on the current base station is cancelled.
  • the program when executed, may include the flow of an embodiment of the methods as described above.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé, un système et un dispositif connexe pour implémenter un délestage de flux de données de service. Le procédé de délestage comprend les étapes suivantes : lorsque des porteuses de réseau d'accès de connectivité IP (« IP-Connectivity Access Network » ou IP-CAN) sont établies ou modifiées, une entité de gestion de réseau mobile reçoit un message porteur comprenant un drapeau de délestage à partir d'une passerelle de réseau mobile, qui obtient le type d'accès de chaque flux de données de service, les types d'accès comprenant un accès de délestage et un accès de non-délestage ; lorsqu'il est déterminé que le type d'accès du flux de données de service transmis sur une quelconque porteuse IP-CAN est l'accès de délestage en fonction du type d'accès de chaque flux de données de service, le drapeau de délestage est utilisé pour indiquer que le type d'accès du flux de données de service transmis sur la porteuse est l'accès de délestage ; l'entité de gestion de réseau mobile transmet un message porteur qui comprend le drapeau de délestage à une station de base pour que la station de base puisse implémenter un délestage pour des flux de données de service transmis sur la porteuse en fonction de l'indication du drapeau de délestage. Des modes de réalisation de la présente invention concernent une solution de délestage de flux de données IP en fonction d'un niveau de flux peut être proposée.
PCT/CN2011/074860 2011-05-30 2011-05-30 Procédé, système et dispositif connexe pour implémenter un délestage de flux de données de service WO2011157106A2 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201180000666.1A CN102918885B (zh) 2011-05-30 2011-05-30 一种实现业务数据流分流的方法、系统及相关装置
PCT/CN2011/074860 WO2011157106A2 (fr) 2011-05-30 2011-05-30 Procédé, système et dispositif connexe pour implémenter un délestage de flux de données de service

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/074860 WO2011157106A2 (fr) 2011-05-30 2011-05-30 Procédé, système et dispositif connexe pour implémenter un délestage de flux de données de service

Publications (2)

Publication Number Publication Date
WO2011157106A2 true WO2011157106A2 (fr) 2011-12-22
WO2011157106A3 WO2011157106A3 (fr) 2012-04-26

Family

ID=45348602

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/074860 WO2011157106A2 (fr) 2011-05-30 2011-05-30 Procédé, système et dispositif connexe pour implémenter un délestage de flux de données de service

Country Status (2)

Country Link
CN (1) CN102918885B (fr)
WO (1) WO2011157106A2 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9819469B2 (en) * 2013-07-01 2017-11-14 Qualcomm Incorporated Techniques for enabling quality of service (QoS) on WLAN for traffic related to a bearer on cellular networks
BR112019006507A2 (pt) * 2016-09-30 2019-06-25 Ericsson Telefon Ab L M método em um nó de rede, método em um dispositivo sem fio, nó de rede e dispositivo sem fio
CN110213798B (zh) * 2019-07-17 2022-10-25 京信网络系统股份有限公司 一种基于Femto网关的分流方法及装置

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101990247A (zh) * 2009-08-07 2011-03-23 华为技术有限公司 数据传输方法、装置和通信系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102056129A (zh) * 2009-11-05 2011-05-11 中兴通讯股份有限公司 本地ip访问连接的建立方法和装置
CN102056142B (zh) * 2009-11-09 2014-07-02 中兴通讯股份有限公司 一种建立本地ip访问下行数据通道的方法及系统
CN102149071B (zh) * 2010-02-08 2014-12-10 中兴通讯股份有限公司 一种对本地ip连接的建立进行控制的方法

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101990247A (zh) * 2009-08-07 2011-03-23 华为技术有限公司 数据传输方法、装置和通信系统

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
'3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Local IP Access and Selected IP Traffic Offload(LIPA-SIPTO) (Release 10)' 3GPP TR 23.829 V10.0.0 29 March 2011, *
'Discussion on policy for SIPTO' 3GPP TSG-SA WG1 MEETING #53 07 February 2011, *
XU MUHONG: 'Local IP Access and IP traffic offload technologies' TELECOMMUNICATIONS NETWORK TECHNOLOGY August 2010, pages 16 - 19 *

Also Published As

Publication number Publication date
CN102918885A (zh) 2013-02-06
CN102918885B (zh) 2015-07-08
WO2011157106A3 (fr) 2012-04-26

Similar Documents

Publication Publication Date Title
JP7416368B2 (ja) 時間依存ネットワーキングのための制御プレーンに基づく設定
RU2735699C1 (ru) Отображение типа сеанса pdn и pdu и обнаружение способности
JP7140871B2 (ja) 選択インターネットプロトコルトラフィックオフロードのパケットデータネットワーク調整変更
US9717019B2 (en) Data flow control method, and related device and communications system
US9277522B2 (en) Exchanging rich communication suite capability information in a communications system
EP2428001B1 (fr) Procédé d'assistance à la sélection de passerelle pdn
US10827394B2 (en) Triggering selective fallback based on user subscription information
US20180103389A1 (en) Service rate adjustment method and apparatus
JP5798693B2 (ja) リバース単一無線音声通話継続性における音声ベアラ選択装置及び方法
KR20100060800A (ko) ＨｅＮＢ에서 단말에게 선택적으로 자원을 할당하기 위한 시스템 및 장치
US9455910B2 (en) Exchanging internet protocol version capability information between client devices over a communications network
EP3416413B1 (fr) Procédé de contrôle de service de données, et dispositif associé
US9642109B2 (en) Single network registration where multiple applications access the network using separate processors
WO2009089790A1 (fr) Procédé pour l'acquisition du type d'un service support et pour la commutation entre réseaux supports pour des terminaux
KR20210024160A (ko) 통신 방법 및 장치
US20140068064A1 (en) Method for qos management in home and roaming scenarios based on location/app server assistance
US8483182B1 (en) Single radio voice call continuity handover of calls with video media from a circuit switched access network
WO2015174700A1 (fr) Procédé de configuration d'apn-ambr dans un système de communications sans fil prenant en charge csipto et dispositif apparenté
US9860792B2 (en) Network device for supporting gateway change in mobile communication system, and method for operating same
WO2017084042A1 (fr) Procédé et appareil de transmission de flux de service
WO2014059647A1 (fr) Procédé, appareil et système de traitement de service du domaine des données
WO2011109999A1 (fr) Procédé d'indication de données et élément de réseau de gestion de mobilité
WO2011134408A1 (fr) Procédé, système et équipement pour notifier et envoyer une activation de délestage de trafic ip sélectionné
WO2011157106A2 (fr) Procédé, système et dispositif connexe pour implémenter un délestage de flux de données de service
WO2013037271A1 (fr) Procédé et système d'accès multiple

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180000666.1

Country of ref document: CN

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

Ref document number: 11795072

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11795072

Country of ref document: EP

Kind code of ref document: A2