[go: up one dir, main page]

WO2016033811A1 - 一种分流策略协商方法及装置 - Google Patents

一种分流策略协商方法及装置 Download PDF

Info

Publication number
WO2016033811A1
WO2016033811A1 PCT/CN2014/086073 CN2014086073W WO2016033811A1 WO 2016033811 A1 WO2016033811 A1 WO 2016033811A1 CN 2014086073 W CN2014086073 W CN 2014086073W WO 2016033811 A1 WO2016033811 A1 WO 2016033811A1
Authority
WO
WIPO (PCT)
Prior art keywords
routing rule
indication
rule
negotiation
routing
Prior art date
Application number
PCT/CN2014/086073
Other languages
English (en)
French (fr)
Inventor
于游洋
李欢
诸华林
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201910611911.0A priority Critical patent/CN110461012B/zh
Priority to ES19204616T priority patent/ES2926077T3/es
Priority to PCT/CN2014/086073 priority patent/WO2016033811A1/zh
Priority to EP19204616.7A priority patent/EP3668023B1/en
Priority to CN201480032643.2A priority patent/CN105594165B/zh
Priority to EP14901168.6A priority patent/EP3182654B1/en
Publication of WO2016033811A1 publication Critical patent/WO2016033811A1/zh
Priority to US15/449,028 priority patent/US11178057B2/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W40/00Communication routing or communication path finding
    • H04W40/02Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0893Assignment of logical groups to network elements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0894Policy-based network configuration management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/20Traffic policing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/16Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18Negotiating wireless communication parameters
    • H04W28/20Negotiating bandwidth
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W40/00Communication routing or communication path finding
    • H04W40/02Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/20Communication route or path selection, e.g. power-based or shortest path routing based on geographic position or location
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W40/00Communication routing or communication path finding
    • H04W40/34Modification of an existing route
    • H04W40/36Modification of an existing route due to handover
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/02Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10Small scale networks; Flat hierarchical networks
    • H04W84/12WLAN [Wireless Local Area Networks]

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and device for negotiating a traffic split strategy. Background technique
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • Packet Packet Data Network Gateway
  • P-GW Packet Data Network Gateway
  • the S-GW is a mobility anchor for switching between local base station eNodeBs, and provides related functions such as lawful interception;
  • the P-GW is responsible for user address allocation, policy control, and execution of charging rules, and Lawful interception and other related functions; home subscriber network server
  • HSS Home Subscriber Server
  • PCRF Policy and Charging Rules Function
  • the non-3GPP network can establish a connection with the P-GW in the 3GPP network through the S2a interface, thereby accessing the 3GPP network, or based on the UE through the S2c interface and the P in the 3GPP network.
  • - GW establishes a connection.
  • the 3GPP standard protocol supports the UE accessing both a 3GPP network and a non-3GPP network, and further, the UE can simultaneously access the 3GPP network and the non-3GPP network based on the same Packet Data Network (PDN) connection. That is, different data streams in the same PDN connection may be distributed in a 3GPP network and a non-3GPP network to achieve effective offloading and reasonable utilization of network resources.
  • PDN Packet Data Network
  • the UE may use a statically configured policy, a dynamically received policy, or The user prefers to choose a network.
  • the prior art shows the synchronization of the routing information between the UE and the network side based on the dual stack mobile IPv6 (DSMIPv6) and the data flow moving process.
  • DSMIPv6 dual stack mobile IPv6
  • the process of data flow switching initiated by the UE is:
  • the UE simultaneously accesses a 3GPP network and a non-3GPP network, and simultaneously uses one PDN connection in the two networks;
  • the UE sends a binding update message Binding Update to the network side, requesting to update the routing rule;
  • the network side provides a new routing rule, and stores the mapping relationship between the updated routing address and the access network, and finally sends a binding acknowledgement message Binding Acknowledgement to the UE, indicating which updated routing rules are accepted.
  • the UE and the network side perform data flow switching based on the accepted updated routing rules. For example, for those data streams that are switched to the non-3GPP system, the 3GPP network initiates a resource release procedure.
  • the mobility protocols used by 3GPP are: GPRS Tunneling Protocol (GTP), Proxy Mobile IPv6 ( ⁇ ), and DSMIPv6.
  • GTP GPRS Tunneling Protocol
  • Proxy Mobile IPv6
  • DSMIPv6 DSMIPv6
  • the embodiments of the present invention provide a method and a device for negotiating a traffic policy, which are used to solve the problem that the method for the data stream handover initiated by the UE in the prior art is less applicable, and the network side cannot control the UE and reduce the user experience. .
  • a method for negotiating a traffic policy includes:
  • the first device sends the offloading policy to the second device, where the offloading policy includes at least one of the following: a default access indication and at least one routing rule;
  • the offloading policy performs data stream transmission based on the confirmed offloading policy.
  • the first device is a core network device or a user equipment UE.
  • the method before the sending, by the first device, the offloading policy to the second device, the method further includes:
  • the first device generates a traffic off policy, which specifically includes:
  • the first device When the first device is a core network device, the first device generates at least one routing rule as a traffic off policy according to at least one of the received rule information, the indication information sent by the UE, the local configuration information, and the current network state; Or
  • the first device When the first device is a UE, the first device generates at least one of a routing rule and a default access indication according to at least one of its own configuration information and a current network state, as a traffic off policy.
  • the routing rule includes: a route access technology, a flow description information, a negotiation indication, and first routing rule identifier information, where The first routing rule identifier information is at least one of a rule name and a rule priority; or
  • the routing rule includes: a route access technology, a flow description information, a route access technology indication, and a second routing rule identifier information, where the second routing rule identifier information is at least one of a rule name and a rule priority. .
  • the routing rule when the routing rule includes: a route access technology, a flow description information, a negotiation indication, and a first routing rule identifier information,
  • the negotiation indication is used to identify the modification permission of the UE to the routing rule, and the value is the permission negotiation identifier or the negotiation negotiation identifier.
  • the negotiation indication value is the permission negotiation identifier, the UE selects the route access technology in the routing rule or Other access technologies; when the negotiation indication value is the forbidden negotiation identifier, it indicates that the UE selects the route access technology in the routing rule; or
  • the route access technology indication is used to identify a route rule. If the route access technology indicates that the value is a forbidden value, the route access technology in the route rule is forbidden; or, when the route is accessed, the route access technology is used as the forbidden value or the allowable value.
  • the technical indication value is an allowable value, it indicates that the route access technology in the routing rule is allowed to be used.
  • the routing rule to which the negotiation indication belongs is a routing rule for prohibiting negotiation
  • the route access technology indicates that the value is a forbidden value, it indicates that the route access technology indicates that the route rule belongs to the route rule that prohibits negotiation.
  • the routing access technology indicates that the rule priority of the routing rule corresponding to the forbidden value is higher than the route access technology indication Specifies the rule priority of the routing rule corresponding to the value.
  • the negotiation indication in the routing rule is empty
  • the route access technology indication included in the routing rule is equal to the allowed value.
  • the first device when the first device is a core network device, the first device The offloading policy is sent to the second device, including:
  • the first device carries the routing rule in the bearer update request or the bearer new request to the mobile management entity MME, so that after receiving the routing rule, the MME carries the routing rule to the non-access stratum NAS. Transmitting to the second device in the message; or
  • the first device carries the routing rule to the trusted access gateway TWAG in the bearer update request or the bearer new request, so that after the TWAG receives the routing rule, the routing rule is carried in the designated Transmitting to the second device in a WLAN control plane protocol WLCP message; or
  • the routing rule is carried in the network key agreement protocol IKEv2 message and transmitted to the second device; or the first device sends the routing rule to the packet data protocol PDP context modification request or the PDP new request to send to the Two devices.
  • the first device where the first device carries the routing rule in a bearer update request or a bearer new request, includes:
  • the first device adds the routing rule as a new parameter to the bearer update request or the bearer new request transmission; or
  • the first device adds the routing rule to the protocol configuration option PCO in the bearer update request or the bearer new request.
  • the first device that causes the MME to carry the routing rule in a non-access stratum NAS message includes:
  • the first device causes the MME to add the routing rule as a new parameter to the NAS message for transmission;
  • the first device causes the MME to add the routing rule to a PCO in the NAS message for transmission.
  • the first device when the first device is a UE, the first device The offloading policy is sent to the second device, including:
  • the first device When the offloading policy includes the routing rule, the first device carries the offloading policy in a NAS message and sends the message to the MME, so that after the MME receives the offloading policy, the offloading policy is carried. Transmitting the second device in a bearer resource command; or
  • the first device sends the default access indication to the MME in the NAS message, so that the MME receives the default access indication. And sending, by the first device, the default access indication to the second device; or the first device sends the default access indication to the WLCP packet data network PDN connection request and sent to the TWAG After the TWAG receives the default access indication, the default access indication is carried in the session new request and sent to the second device; or the first device connects the default The inbound indication is carried in the network key agreement protocol IKEv2 message and sent to the non-trusted access gateway ePDG, so that after the ePDG receives the default access indication, the default access indication is carried in the session new The request is sent to the second device.
  • IKEv2 network key agreement protocol
  • the first device when the traffic distribution policy includes the routing rule, the first device carries the traffic distribution policy to a NAS Sent in the message, including:
  • the first device adds the offloading policy as a new parameter to the NAS message to send; or
  • the first device adds the offloading policy to the PCO in the NAS message for sending.
  • the traffic distribution policy is a default access indication
  • the first device is configured to connect the default
  • the incoming indication is carried in the NAS message or the WLCP PDN connection request, and includes:
  • the offloading policy is the default access indication
  • the first device causes the MME or the TWAG to carry the default access indication in the session new request, specifically used in: The first device causes the MME or the TWAG to add the default access indication to the PCO in the session new request to send; or
  • the specific device is specifically used to:
  • the first device adds the default access indication as a new parameter to the IKEv2 message for transmission.
  • the first device when the first device is a core network device, the first device receives the acknowledged traffic off policy that is returned by the second device, and includes:
  • the first device receives the route sent by the second device Other routing rules that are not modified in the rule and updated routing rules that modify the at least one routing rule; or
  • the first device receives the unmodified routing rule.
  • the negotiation indication included in the at least one routing rule modified by the second device is to allow a negotiation identifier
  • the route access technology indication included in the at least one routing rule modified by the second device is equal to the allowed value.
  • the first device receives the confirmed offloading policy that is returned by the second device for the offloading policy , Also includes:
  • the first device when the first device is a UE, the first device receives the The confirmed offloading policy returned by the second device for the offloading policy includes:
  • the first device receives the confirmed default access indication returned by the second device, and includes:
  • the second device modifies the received default access indication according to at least one of the received rule information, the indication information sent by the UE, the local configuration information, and the current network status, Receiving, by the first device, the modified default access indication returned by the second device; or if the second device does not modify the default access indication, the first device receives the An unmodified default access indication returned by the second device;
  • the receiving, by the first device, the confirmed routing rule returned by the second device includes: if the second device is configured according to the received rule information, the indication information sent by the UE, the local configuration information, and the current network state. And modifying, by the at least one one of the received routing rules, the first device, the first device, the other routing rule that is not modified in the routing rule sent by the second device, and the at least one route The updated routing rule after the rule is modified; or
  • the first device receives the unmodified routing rule.
  • the negotiation indication included in the updated routing rule that is modified by the at least one routing rule is a forbidden negotiation identifier
  • the route access technology included in the updated routing rule modified by the at least one routing rule is indicated as a forbidden value.
  • the second aspect a method for negotiating a traffic policy, includes:
  • the second device receives the offloading policy sent by the first device, and confirms the offloading policy, where the offloading policy includes at least one of the following: a default access indication and at least one routing rule; And confirming the offloading policy, and returning the confirmed offloading policy to the first device, and performing data stream transmission based on the confirmed offloading policy.
  • the second device is a user equipment UE or a core network device.
  • the traffic off policy is at least one routing rule sent by the first device
  • the traffic distribution policy is at least sent by the first device. At least one of a routing rule and a default access indication.
  • the routing rule that is sent by the first device includes: a route access technology, a flow description information, a negotiation indication, and a a routing rule identifier information, where the first routing rule identifier information is at least one of a rule name and a rule priority; or
  • the routing rule sent by the first device includes: a route access technology, a flow description information, a route access technology indication, and a second routing rule identifier information, where the second routing rule identifier information is a rule name and At least one of the rule priorities.
  • the routing rule when the routing rule includes: a route access technology, a flow description information, a negotiation indication, and a first routing rule identifier information,
  • the negotiation indication is used to identify the modification permission of the UE to the routing rule, and the value is the permission negotiation identifier or the negotiation negotiation identifier.
  • the negotiation indication value is the permission negotiation identifier, the UE selects the route access technology in the routing rule or Other access technologies; when the negotiation indication value is the forbidden negotiation identifier, it indicates that the UE selects the route access technology in the routing rule; or
  • the route access technology indication is used to identify a route access technology in the route rule.
  • the privilege value is the forbidden value or the allowable value.
  • the route access technology indicates that the value is a forbidden value, the route access technology in the routing rule is forbidden. Indicates that the route access technology in the routing rule is allowed to be used.
  • the routing rule to which the negotiation indication belongs is a routing rule for prohibiting negotiation
  • the route access technology indicates that the value is a forbidden value, it indicates that the route access technology indicates that the route rule belongs to the route rule that prohibits negotiation.
  • the routing access technology indicates that the rule of the routing rule corresponding to the forbidden value has a higher priority than the routing
  • the incoming technical indication is the rule priority of the routing rule corresponding to the allowed value.
  • the negotiation indication in the routing rule sent by the first device is empty. ;
  • the route access technology indication in the routing rule sent by the first device is equal to an allowed value.
  • the second device confirms the routing rule, and specifically includes:
  • the second device determines that at least one of its own configuration information and the current network state does not match at least one of the routing rules, and the at least one routing rule is not a negotiated routing rule,
  • the at least one routing rule is modified, and the modified updated routing rule is generated, and the other routing rules that are not modified in the routing rule and the updated routing rule that is modified by the at least one routing rule are used as the confirmed route. Rule; or
  • the second device determines that at least one of its own configuration information and the current network state matches all routing rules in the routing rule, or at least one of its own configuration information and current network status, and the routing rule When the routing rule that is not matched is the routing rule that is forbidden, the routing rule is not modified, and the unmodified routing rule is used as the confirmed routing rule.
  • the second device when the second device is a core network device, the second device is configured to perform the offloading
  • the strategy confirms, including:
  • the second device confirms the default access indication in the offloading policy, and/or the second device confirms the routing rule in the offloading policy;
  • the second device confirms the default access indication, including:
  • the default is The access indication is modified, and the modified default access indication is used as the default access indication after confirmation;
  • the second device determines that the received rule information, the indication information sent by the UE, the local configuration information, and the current network status match the default access indication, the default access indication is not modified, and the unmodified
  • the default access indication is used as a default access indication after confirmation;
  • the second device confirms the routing rule, including:
  • the at least one routing rule is Modifying, and generating a modified updated routing rule, using the other routing rules that are not modified in the routing rule and the updated routing rule that is modified by the at least one routing rule as the confirmed routing rule; or
  • the second device determines that the received rule information, the indication information sent by the UE, the local configuration information, and the current network status match all the routing rules in the routing rule, the routing rule is not modified, and the unmodified one is The routing rule is used as the confirmed routing rule.
  • the modifying, by the second device, the at least one routing rule includes:
  • the second device modifies a route access technology included in the at least one routing rule
  • the negotiation indication included in the at least one routing rule is set as a forbidden negotiation identifier; when the at least one routing rule includes a route access technology indication, the at least the The route access technology indication contained in a routing rule is set to a forbidden value.
  • the second device when the second device is a UE, the second device returns the confirmed offloading policy to the The first device, including:
  • the second device Transmitting, by the second device, the confirmed routing rule in the non-access stratum NAS message to the mobility management entity MME, so that after the MME receives the confirmed routing rule,
  • the confirmed routing rule is carried in the bearer update response or the bearer new response to be transmitted to the first device;
  • the second device carries the confirmed routing rule in a specified WLAN control plane protocol WLCP message and transmits it to the trusted access gateway TWAG, so that after the TWAG receives the confirmed routing rule, Transmitting the confirmed routing rule to the first device by carrying the bearer update response or the bearer new response; or
  • the second device carries the confirmed routing rule in the network key agreement protocol IKEv2 message to the non-trusted access gateway ePDG, so that after the ePDG receives the confirmed routing rule,
  • the confirmed routing rule is carried in the bearer update response or the bearer new response and transmitted to the first device.
  • the second device is configured to carry the advertised routing rule in a NAS message and transmit the message to the MME, where:
  • the second device adds the confirmed routing rule as a new parameter to the NAS message and transmits to the MME; or
  • the second device adds the confirmed routing rule to the protocol configuration option PCO in the NAS message and transmits it to the MME.
  • the confirmed routing rule is carried in the bearer update response or the bearer new response, and is transmitted to the first device , including:
  • the second device returns the confirmed offloading policy to the first device, and further includes:
  • the second device when the second device is a core network device, the second device returns the confirmed offloading policy To the first device, including:
  • the second device transmits the confirmed offloading policy to the bearer update request or the bearer new request by using the confirmed offloading policy to include the confirmed routing rule.
  • the MME After the MME receives the acknowledged offloading policy, the MME is carried in the NAS message and transmitted to the first device; or the second device performs the confirmed The offloading policy is carried in the packet data protocol PDP context modification request or the PDP context new request to the first device; or
  • the second device sends the confirmed default access indication to the MME in the session new response, so that the MME is configured to send the MME to the MME.
  • the acknowledgment default access indication is carried in the NAS message and sent to the first device; or the second device after the acknowledgment
  • the default access indication is sent to the trusted access gateway TWAG in the session new response, so that after the TWAG receives the confirmed default access indication, the queried default access is obtained.
  • the indication is sent to the first device in a WLAN control plane protocol WLCP packet data network PDN connection response; or the second device sends the confirmed default access indication in the session new response to be sent to the session
  • the non-trusted access gateway ePDG so that the ePDG receives the queried default access indication, and carries the confirmed default access indication in the network key agreement protocol IKEv2 message to send to the Narrative a device.
  • the second device when the confirmed offloading policy includes the confirmed routing rule, the second device causes the MME to The confirmed offloading policy is carried in the NAS message and transmitted to the first device, the packet Includes:
  • the second device causes the MME to add the confirmed offloading policy as a new parameter to the NAS message and transmit to the first device;
  • the second device causes the MME to add the confirmed offloading policy to the PCO in the NAS message to be transmitted to the first device.
  • the second device when the confirmed offloading policy is the default access indication after the confirmation, the second device The acknowledgment default access indication is sent in the session new response, and includes:
  • the second device adds the confirmed default access indication to the PCO in the session new response to send;
  • the second device after the acknowledgment, is configured to send the queried default access indication to the NAS message, where: The second device enables the MME to add the confirmed default access indication to the PCO in the NAS message for sending;
  • the second device When the acknowledgment offloading policy is the default access indication after the acknowledgment, the second device enables the TWAG to carry the queried default access indication in the WLCP PDN connection response, In:
  • the second device causes the TWAG to add the confirmed default access indication to the PCO in the WLCP PDN connection response for sending;
  • the second device causes the ePDG to carry the acknowledgment default access indication in the IKEv2 message, where the acknowledgment of the IPSec policy is:
  • the second device causes the ePDG to add the confirmed default access indication as a new parameter to the IKEv2 message for transmission.
  • a traffic distribution negotiation device includes:
  • a sending unit configured to send the offloading policy to the second device, where the offloading policy includes at least one of the following: a default access indication and at least one routing rule;
  • a receiving unit configured to receive and store an acknowledgement returned by the second device for the offloading policy
  • the subsequent offloading strategy performs data stream transmission based on the confirmed offloading policy.
  • the offloading policy negotiation device is a core network device or a user equipment UE.
  • the offloading policy negotiation device further includes:
  • a generating unit configured to generate a trafficking policy, where the sending unit sends the traffic distribution policy to the second device, where the generating unit is specifically configured to:
  • the generating unit When the offloading policy negotiation device is a core network device, the generating unit generates at least one routing rule as a traffic distribution policy according to at least one of the received rule information, the indication information sent by the UE, the local configuration information, and the current network state; Or
  • the generating unit When the offloading policy negotiation device is a UE, the generating unit generates at least one of the at least one routing rule and the default access indication according to at least one of its own configuration information and the current network state, as the trafficking policy.
  • the routing rule includes: a route access technology, a flow description information, a negotiation indication, and a first routing rule identifier information, where The first routing rule identifier information is at least one of a rule name and a rule priority; or
  • the routing rule includes: a route access technology, a flow description information, a route access technology indication, and a second routing rule identifier information, where the second routing rule identifier information is at least one of a rule name and a rule priority. .
  • the routing rule when the routing rule includes: a route access technology, a flow description information, a negotiation indication, and a first routing rule identifier information,
  • the negotiation indication is used to identify the modification permission of the UE to the routing rule, and the value is the permission negotiation identifier or the negotiation negotiation identifier.
  • the negotiation indication value is the permission negotiation identifier, the UE selects the route access technology in the routing rule or Other access technologies; when the negotiation indication value is the forbidden negotiation identifier, it indicates that the UE selects the route access technology in the routing rule; or
  • the routing rule includes: a route access technology, a flow description information, and a route access technology indication
  • the route access technology indication is used to identify the use permission of the route access technology in the route rule, and the value is a forbidden value or an allowable value, and the value of the route access technology indication is
  • the value is forbidden, it means that the route access technology in the routing rule is forbidden; or when the route access technology indicates that the value is allowed, it indicates that the route access technology in the routing rule is allowed.
  • the routing rule to which the negotiation indication belongs is a routing rule for prohibiting negotiation
  • the route access technology indicates that the value is a forbidden value, it indicates that the route access technology indicates that the route rule belongs to the route rule that prohibits negotiation.
  • the routing access technology indicates that the rule priority of the routing rule corresponding to the forbidden value is higher than the route access technology indication Specifies the rule priority of the routing rule corresponding to the value.
  • the negotiation indication in the routing rule is empty; or the routing rule The route access technology indication contained in it is equal to the allowed value.
  • the sending unit when the offloading policy negotiation device is a core network device, the sending unit is specifically used.
  • the sending unit carries the routing rule to the mobility management entity MME in the bearer update request or the bearer new request, so that after receiving the routing rule, the MME carries the routing rule to the non-access stratum NAS message. Transfer to the second device; or
  • the sending unit carries the routing rule to the trusted access gateway TWAG in the bearer update request or the bearer new request, so that after the TWAG receives the routing rule, the routing rule is carried in the designated The WLAN control plane protocol WLCP message is transmitted to the second device; or
  • the sending unit carries the routing rule in a bearer update request or a bearer new request After being sent to the non-trusted access gateway ePDG, after the ePDG receives the routing rule, the routing rule is carried in the network key agreement protocol IKEv2 message and transmitted to the second device; or the sending The unit sends the routing rule to the second device in the packet data protocol PDP context modification request or the PDP new request.
  • the sending unit is configured to: when the routing rule is carried in a bearer update request or a bearer new request,
  • the sending unit adds the routing rule to the protocol configuration option PCO in the bearer update request or bearer new request.
  • the sending unit when the MME is configured to carry the routing rule in a non-access stratum NAS message, is specifically used to:
  • the sending unit causes the MME to add the routing rule as a new parameter to the NAS message for transmission;
  • the sending unit causes the MME to add the routing rule to the PCO in the NAS message for transmission.
  • the sending unit is specifically used In:
  • the sending unit When the offloading policy includes the routing rule, the sending unit carries the offloading policy in a NAS message and sends it to the MME, so that after the MME receives the offloading policy, the offloading policy is carried in the offloading policy. Transmitting the second device in a bearer resource command; or
  • the sending unit uses the default access indication And being sent to the MME in the NAS message, so that after the MME receives the default access indication, the default access indication is carried in the session new request and sent to the second device; or, the sending The unit sends the default access indication to the TWAG in the WLCP packet data network PDN connection request, so that after the TWAG receives the default access indication, the default access indication is carried in the session.
  • the new request is sent to the second device; or the sending unit carries the default access indication in the network key agreement protocol IKEv2 message and sends the message to the non-trusted access gateway ePDG, so that the ePDG receives the After the default access indication, the default access indication is carried in the session new request and sent to the second device.
  • the sending unit when the traffic distribution policy includes the routing rule, the sending unit is configured to carry the traffic distribution policy to a NAS message.
  • the sending unit When sent in, specifically used to:
  • the sending unit adds the offloading policy as a new parameter to the NAS message to send;
  • the sending unit adds the offloading policy to the PCO in the NAS message for sending.
  • the sending unit when carried in a NAS message or sent in the WLCP PDN connection request, it is specifically used to:
  • the sending unit is configured to: when the MME or the TWAG sends the default access indication to the session creation request, specifically: The sending unit causes the MME or the TWAG to add the default access indication to the PCO in the session new request to send; or
  • the sending unit when the offloading policy is the default access indication, is specifically used to:
  • the sending unit adds the default access indication as a new parameter to the IKEv2 message for sending.
  • the receiving unit specifically Used for:
  • the routing rule sent by the second device if the second device modifies at least one routing rule in the received routing rule according to at least one of the configuration information and the current network state.
  • the receiving unit receives the unmodified routing rule.
  • the negotiation indication included in the at least one routing rule modified by the second device is to allow the negotiation identifier
  • the route access technology indication included in the at least one routing rule modified by the second device is equal to the allowed value.
  • the receiving unit is further configured to:
  • the receiving unit is specifically configured to: :
  • the receiving unit when receiving the confirmed default access indication returned by the second device, is specifically used to:
  • the second device modifies the received default access indication according to at least one of the received rule information, the indication information sent by the UE, the local configuration information, and the current network status, Receiving, by the receiving unit, the modified default access indication returned by the second device; or if the second device does not modify the default access indication, the receiving unit receives the second The unmodified default access indication returned by the device;
  • the receiving unit when receiving the confirmed routing rule returned by the second device, is specifically used to:
  • the second device modifies at least one of the received routing rules according to at least one of the received rule information, the indication information sent by the UE, the local configuration information, and the current network state, the receiving unit Receiving another routing rule that is not modified in the routing rule sent by the second device, and an updated routing rule that is modified after the at least one routing rule is modified; or
  • the receiving unit receives the unmodified routing rule.
  • the negotiation indication included in the modified routing rule that is modified by the at least one routing rule is a forbidden negotiation identifier
  • the route access technology included in the updated routing rule modified by the at least one routing rule is indicated as a forbidden value.
  • the fourth aspect relates to a traffic distribution policy negotiation device, including:
  • an acknowledgment unit configured to receive the offloading policy sent by the first device, and confirm the offloading policy, where the offloading policy includes at least one of the following: a default access indication and at least one routing rule;
  • the processing unit is configured to store the confirmed offloading policy, and return the confirmed offloading policy to the first device, and perform data stream transmission based on the confirmed offloading policy.
  • the offloading policy negotiation device is a user equipment UE or a core network device.
  • the traffic distribution policy negotiation device when the traffic distribution policy negotiation device is a UE, the traffic distribution policy is sent by the first device a routing rule;
  • the traffic distribution policy is at least one of at least one routing rule and a default access indication sent by the first device.
  • the routing rule that is sent by the first device includes: a route access technology, a flow description information, a negotiation indication, and a a routing rule identifier information, where the first routing rule identifier information is at least one of a rule name and a rule priority; or
  • the routing rule sent by the first device includes: a route access technology, a flow description information, a route access technology indication, and a second routing rule identifier information, where the second routing rule identifier information is a rule name and At least one of the rule priorities.
  • the routing rule when the routing rule includes: a route access technology, a flow description information, a negotiation indication, and a first routing rule identifier information,
  • the negotiation indication is used to identify the modification permission of the UE to the routing rule, and the value is the permission negotiation identifier or the negotiation negotiation identifier.
  • the negotiation indication value is the permission negotiation identifier, the UE selects the route access technology in the routing rule or Other access technologies; when the negotiation indication value is the forbidden negotiation identifier, it indicates that the UE selects the route access technology in the routing rule; or
  • the route access technology indication is used to identify a route access technology in the route rule.
  • the privilege value is the forbidden value or the allowable value.
  • the route access technology indicates that the value is a forbidden value, the route access technology in the routing rule is forbidden. Indicates that the route access technology in the routing rule is allowed to be used.
  • the routing rule to which the negotiation indication belongs is a routing rule for prohibiting negotiation
  • the routing access technology indicates that the value is a forbidden value, it indicates that the routing rule to which the routing access technology indicates belongs is a routing rule that prohibits negotiation.
  • the routing access technology indicates that the rule priority of the routing rule corresponding to the forbidden value is higher than the route access technology indication is The rule priority of the routing rule corresponding to the allowed value.
  • the negotiation indication in the routing rule sent by the first device is empty. ;
  • the route access technology indication in the routing rule sent by the first device is equal to an allowed value.
  • the confirming unit is configured to: The routing rules are confirmed;
  • the confirmation unit confirms the routing rule, it is specifically used to:
  • the confirmation unit determines that at least one of the configuration information of the self and the current network state does not match the at least one routing rule in the routing rule, and the at least one routing rule is not a routing rule that prohibits negotiation, and the at least one A routing rule is modified, and a modified updated routing rule is generated, and other routing rules that are not modified in the routing rule and updated routing rules that modify the at least one routing rule are used as the confirmed routing rule. ; or
  • the confirming unit determines that at least one of the configuration information of the self and the current network state matches all the routing rules in the routing rule, or at least one of the configuration information of the self and the current network state, and the routing rule does not
  • the matching routing rule is a rule that prohibits negotiation
  • the routing rule is not modified, and the unmodified routing rule is used as the confirmed routing rule.
  • the confirming unit is configured to:
  • the confirming unit determines that the default access indication is modified when at least one of the received rule information, the indication information sent by the UE, the local configuration information, and the current network status does not match the default access indication. , using the modified default access indication as the default access indication after confirmation; or
  • the confirmation unit determines that the received rule information, the indication information sent by the UE, the local configuration information, and the current network status match the default access indication, and does not modify the default access indication, and the unmodified Defining the default access indication as the default access indication after confirmation;
  • the confirmation unit confirms the routing rule, it is specifically used to:
  • the determining unit determines that the at least one routing rule is performed when at least one of the received rule information, the indication information sent by the UE, the local configuration information, and the current network state does not match the at least one routing rule in the routing rule. Modifying, and generating a modified updated routing rule, using the other routing rules that are not modified in the routing rule and the updated routing rule that is modified by the at least one routing rule as the confirmed routing rule; or
  • the acknowledgment unit determines that the received rule information, the indication information sent by the UE, the local configuration information, and the current network status match all the routing rules in the routing rule, and does not modify the routing rule, and the unmodified route is The rule is used as the routing rule after confirmation.
  • the confirmation unit modifies the route access technology included in the at least one routing rule
  • the negotiation indication included in the at least one routing rule is set as a forbidden negotiation identifier; when the at least one routing rule includes a route access technology indication, the at least the The route access technology indication contained in a routing rule is set to a forbidden value.
  • the processing unit is specifically configured to:
  • the processing unit carries the confirmed routing rule in a non-access stratum NAS message for transmission After the MME receives the queried routing rule, the MME is carried in the bearer update response or the bearer new response to be transmitted to the first device; or
  • the processing unit carries the confirmed routing rule in a specified WLAN control plane protocol WLCP message and transmits it to the trusted access gateway TWAG, so that after the TWAG receives the confirmed routing rule,
  • the confirmed routing rule is carried in the bearer update response or the bearer new response to be transmitted to the first device; or
  • the processing unit carries the confirmed routing rule in the network key agreement protocol IKEv2 message and transmits it to the non-trusted access gateway ePDG, so that after the ePDG receives the confirmed routing rule,
  • the confirmed routing rule is carried in the bearer update response or the bearer new response and transmitted to the first device.
  • the processing unit when the advertised routing rule is carried in a NAS message and transmitted to the MME, is specifically used to :
  • the processing unit adds the confirmed routing rule as a new parameter to the NAS message and transmits it to the MME; or
  • the processing unit adds the confirmed routing rule to the protocol configuration option PCO in the NAS message and transmits it to the MME.
  • the processing unit is configured to enable the MME, the TWAG, or the ePDG to carry the confirmed routing rule When it is transmitted to the first device in a bearer update response or a bearer new response, it is specifically used to:
  • the processing unit causes the MME, the TWAG, or the ePDG to add the confirmed routing rule as a new parameter to the bearer update response or bearer new response to be transmitted to the first device; or
  • the processing unit causes the MME, the TWAG, or the ePDG to add the confirmed routing rule to the bearer context in the bearer update response or the bearer new response. To the first device; or
  • the processing unit causes the MME, the TWAG, or the ePDG to add the confirmed routing rule to the PCO in the bearer update response or bearer new response to be transmitted to the first device.
  • the processing unit is further configured to:
  • the processing unit is specifically configured to:
  • the processing unit transmits the confirmed offloading policy to the MME by carrying the confirmed offloading policy in the bearer update request or the bearer new request, so that the MME receives the queried policy.
  • the spoofed offloading policy is carried in the NAS message and transmitted to the first device; or the processing unit carries the acknowledged offloading policy in the packet data protocol PDP. Sending to the first device in a context modification request or a PDP context new request; or
  • the processing unit sends the confirmed default access indication to the MME in the session new response to enable the MME to receive, after the acknowledging offloading policy is the default access indication after the acknowledgment.
  • the acknowledgment default access indication is carried in the NAS message and sent to the first device; or, the processing unit
  • the provincial access indication is carried in the session new response and sent to the trusted access gateway TWAG, so that after the TWAG receives the confirmed default access indication, the NBAG carries the confirmed default access indication.
  • the processing unit Transmitting to the first device in a WLAN control plane protocol WLCP packet data network PDN connection response; or, the processing unit carries the confirmed default access indication in a session new response and sent to the non-trusted Accessing the ePDG, so that the ePDG receives the queried default access indication, and sends the confirmed default access indication to the network key agreement protocol IKEv2 message to send to the first device.
  • the processing unit when the confirmed offloading policy includes the confirmed routing rule, the processing unit causes the MME to confirm the After the offloading policy is carried in the NAS message and transmitted to the first device, it is specifically used to:
  • the processing unit causes the MME to add the confirmed offloading policy as a new parameter to the NAS message and transmit to the first device;
  • the processing unit causes the MME to add the confirmed offloading policy to the PCO in the NAS message to be transmitted to the first device.
  • the processing unit when the confirmed offloading policy is a default access indication after confirmation, the processing unit is configured to: add, by the processing unit, the confirmed default access indication to the PCO in the session new response to send ;
  • the processing unit When the acknowledgment offloading policy is the default access indication after the acknowledgment, the processing unit enables the MME to carry the queried default access indication in the NAS message, specifically for:
  • the processing unit causes the MME to add the confirmed default access indication to the PCO in the NAS message for sending;
  • the processing unit When the acknowledgment offloading policy is the default access indication after the acknowledgment, the processing unit enables the TWAG to carry the queried default access indication in the WLCP PDN connection response, specifically for :
  • the processing unit causes the TWAG to add the confirmed default access indication to the PCO in the WLCP PDN connection response for sending;
  • the processing unit is configured to: when the acknowledgment of the default access indication is the acknowledgment of the default access indication, the processing unit, when the ePDG sends the queried default access indication to the IKEv2 message, specifically:
  • the processing unit causes the ePDG to add the confirmed default access indication as a new parameter to Sent in the IKEv2 message.
  • the first device sends the offloading policy to the second device, where the offloading policy includes a default access indication and a routing rule; the first device receives and stores the acknowledgement returned by the second device for the offloading policy.
  • the subsequent offloading strategy performs data stream transmission based on the confirmed offloading strategy.
  • FIG. 1 is a flowchart of a method for negotiating a traffic distribution policy on a first device side according to an embodiment of the present disclosure
  • FIG. 2 is a flow chart of a method for negotiating a traffic distribution policy on a second device side according to an embodiment of the present disclosure
  • FIG. 3 is a flowchart of an example of a first offload policy negotiation according to an embodiment of the present invention
  • FIG. 4 is a flowchart of an example of a second offload policy negotiation according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of an example of a third offload policy negotiation according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of a fourth example of a traffic distribution policy negotiation according to an embodiment of the present disclosure.
  • FIG. 7 is a flowchart of a fifth example of a traffic distribution policy negotiation according to an embodiment of the present disclosure.
  • FIG. 8 is a structural diagram of a device for offloading policy negotiation on a first device side according to an embodiment of the present invention
  • FIG. 9 is a structural diagram of a device for negotiating a traffic policy on a second device side according to an embodiment of the present invention
  • FIG. 11 is a structural diagram of a traffic distribution policy negotiation device on a second device side according to an embodiment of the present invention.
  • the first device After the first device generates a new offloading policy, the first device sends the generated new offloading policy to the second device. After the second device confirms and saves, the confirmed offloading policy is returned to the first device. After the first device saves the confirmed offloading policy, the first device and the second device perform data stream transmission based on the confirmed offloading policy, so that, in the process of generating the traffic offloading policy, the network side and the UE may be used.
  • the negotiation can obtain a traffic offloading policy that is acceptable on both sides, improve the efficiency of data stream transmission, and solve the problem that the method of data flow switching initiated by the UE in the prior art is less applicable, and the network side cannot control and manage the UE. Reduce the user experience.
  • the offloading policy includes at least one of a routing rule and a default access indication, where the default access indication, that is, when the data stream is matched, is not found in all the locally stored routing rules. If the routing rule matches the data flow, the access technology specified in the default access indication is selected to transmit the data stream.
  • the default access indication may be 3GPP, WLAN, or the like.
  • the embodiment of the present invention provides an extended routing rule, where the routing rule includes: a routing access technology, a flow description information, a negotiation indication, and a first routing rule identifier information, where the first routing rule identifier information is a rule name, At least one of the rule priorities.
  • the routing rule may further include a routing access technology priority. In this embodiment, only the routing rule includes the routing access technology, the flow description information, the negotiation indication, the rule name, and the rule priority, as shown in Table 1.
  • the rule name can uniquely identify each routing rule (that is, a routing entry);
  • the route access technology in each routing rule is an access technology identifier recommended by the routing rule, and may be a value of 3GPP, WLAN, non-3GPP or WinMax; Value, the smaller the value, the higher the priority;
  • the flow description information indicates the data flow description information.
  • the data flow description information may include at least one parameter of a source destination IP address, a source destination port number, a protocol type, and the like;
  • the negotiation indication is used to implement the negotiation of the routing rule.
  • the negotiation indication is used to identify the modification permission of the UE to the routing rule.
  • the value is the permission negotiation identifier and the negotiation negotiation identifier.
  • the negotiation indication value is the permission negotiation identifier
  • the UE can select the negotiation identifier.
  • the route access technology in the routing rule can also select other access technologies.
  • the negotiation indication value is the forbidden negotiation identifier, it indicates that the UE can only select the route access technology in the routing rule.
  • the negotiation indication is used to indicate whether the current routing rule can be modified by the UE.
  • the negotiation indication may generally be two types of values: the negotiation negotiation identifier and the prohibition negotiation identifier, and may be defined by, but not limited to, using a boolean value.
  • the negotiation indication value is 1, it indicates that the routing rule is allowed to be negotiated, that is, the UE is allowed to modify it; if the negotiation indication takes a value of 0 Indicates that the routing rule is not allowed to be negotiated, that is, the UE is not allowed to modify it. Therefore, 1 is the negotiation negotiation indication, and 0 is the prohibition negotiation indication.
  • the routing rule to which the negotiation indication belongs is a routing rule for prohibiting negotiation.
  • the access technology used to transmit the data stream can be determined according to the routing rules in Table 1.
  • the feature of the received data stream is obtained, and the obtained data flow feature is matched with the flow description information of the locally stored routing rule, and the routing rule that includes the flow description information corresponding to the feature of the data flow is used as an alternative routing rule. ;
  • the routing access technology set in the default access indication stored locally is used to transmit the data stream;
  • the routing access technology included in the routing rule is directly selected to transmit the data stream
  • the routing rule with the highest priority of the rule can be selected as the target routing rule in the candidate routing rule, and the selected routing rule is included.
  • the route access technology transmits the data stream.
  • the routing rule in Table 1 is used as an example, if the UE receives the data flow characterized by the data flow description information 1, the routing rule with the rule name 1 can be retrieved in the locally stored routing rule.
  • the data stream is transmitted according to the route access technology 3GPP specified in the routing rule.
  • the embodiment of the present invention further provides another extended routing rule, where the routing rule includes: a route access technology, a flow description information, a route access technology indication, and a second routing rule identifier information, where the second routing rule identifier The information is at least one of a rule name and a rule priority.
  • the routing rule includes a route access technology, a flow description information, a rule name, a route access technology indication, and a rule priority, as shown in Table 2.
  • the rule name, the route accessing technology, the rule priority, and the flow description information have the same meanings as the first extended routing rule, and are not described here.
  • the negotiation rule is set to implement the negotiation of the routing rule, and in the second extended routing rule provided by the embodiment of the present invention, the routing is accessed through the route.
  • Technical instructions to achieve are provided in the first extended routing rule provided by the embodiment of the present invention.
  • the route access technology indicates whether the route access technology is allowed or prohibited.
  • the route access technology indicator is used to identify the use permission of the route access technology in the route rule. When the route access technology indicates that the value is prohibited. Indicates that the route access technology in the routing rule is forbidden. When the route access technology indicates that the value is allowed, the route access technology in the route rule is allowed to be used. , indicating the routing rule to which the route access technology indication belongs. It is a routing rule that prohibits negotiation.
  • the routing access technology indicates that the rule priority of the routing rule corresponding to the forbidden value is higher than the rule priority of the routing rule indicated by the routing access technology as the allowed value.
  • the data stream indicating that the upper stream description information is matched may be transmitted by using the access technology indicated in the route access technology.
  • the route access technology indicates that it is forbidden, it indicates that the data flow matching the upstream description information is prohibited from being transmitted using the access technology indicated in the route access technology.
  • the Boolean value is still used as an example.
  • the value indicates that the corresponding route access technology is allowed to transmit.
  • the route access technology is prohibited from being transmitted.
  • the UE when the value is 0, the UE must strictly comply with the policy indication, and prohibit the transmission of the matched data stream on the corresponding access technology, that is, the policy cannot be modified by the UE, and the negotiation policy is prohibited.
  • the UE may also select other access technologies to transmit the matching data stream, in order to allow the negotiation policy.
  • the route access technology indicates that the value is a forbidden value, it indicates that the route access technology indicates that the route rule belongs to the route rule that prohibits negotiation.
  • the route other than the route access technology included in the route rule for which the negotiation is prohibited is selected.
  • the access technology transmits the data stream.
  • the UE may not modify the routing rule that is forbidden to negotiate, and may modify other routing rules except the routing rule that the routing access technology indicates that the negotiation is allowed, that is, the UE must use the routing rule specified in the prohibited negotiation.
  • Other routing access technologies other than the routing access technology transmit the data stream, but may use the routing access technology specified in the routing rule that allows negotiation to transmit the data stream, and may also use the routing rule that allows negotiation.
  • Other route access technologies other than the specified route access technology transmit data streams.
  • the access technology used to transmit the data stream can be determined according to the routing rules in Table 2.
  • the feature of the received data stream is obtained, and the obtained data flow feature is matched with the flow description information of the locally stored routing rule, and the routing rule that includes the flow description information corresponding to the feature of the data flow is used as an alternative routing rule. ;
  • the default access indication stored locally is selected.
  • the set route access technology transmits the data stream;
  • the data stream is transmitted according to the routing access technology included in the alternative routing rule, if the data stream is received If the device is a UE, the UE may also use other route access technologies to transmit the data stream.
  • the routing access technology When the number of the alternative routing rules is 1, and the routing access technology indicates a specified value of 0, that is, the alternative routing rule is a routing rule that prohibits negotiation, the routing access technology included in the prohibited routing rule is selected.
  • An external route access technology transmits the data stream;
  • the routing rule with the highest rule priority is selected as the target routing rule in the alternative routing rule, and the data flow is transmitted according to the routing access technology included in the target routing rule.
  • the rule of the route rule that is forbidden to negotiate may be set to be higher than the rule priority of the route rule that is allowed to be negotiated, that is, the rule priority of the route rule corresponding to the barring access technology indication is higher than the route access technology indication. Specifies the rule priority of the routing rule corresponding to the value.
  • the embodiment of the present invention provides a method for negotiating a traffic splitting policy, which is applicable to a UE and a network side device, such as a P-GW, for processing a data flow switching service.
  • a traffic splitting policy which is applicable to a UE and a network side device, such as a P-GW, for processing a data flow switching service.
  • a specific processing procedure of a method for negotiating a traffic distribution policy includes:
  • Step 101 The first device sends the offloading policy to the second device, where the offloading policy includes at least one of the following default access indications and at least one routing rule.
  • the classification policy sent by the first device is generally a classification policy generated by the first device.
  • the offloading policy generated by the first device may include a newly established offloading policy and a new offloading policy modified in the original offloading policy.
  • the first device is a device that performs data stream transmission according to the offloading policy, and specifically, may be a core network device (such as a P-GW) or a UE. In this embodiment, only the first device is a P-GW or a UE.
  • the second device is also a device for performing data stream transmission according to the offloading policy, and the first device is the core network device, and the second device is the UE; When the first device is a UE, the second device is a core network device.
  • the first device can be a core network device or a UE, the first device generates a traffic off policy, including two modes:
  • the first mode is: when the first device is a core network device, the first device is configured according to the received rule information (for example, a PCC rule sent by the PCRF, or the UE sends the indication information, etc.), the local configuration information, and the current network state. At least one of generating or modifying at least one routing rule as a traffic off policy; or
  • the second mode is: when the first device is the UE, the first device generates or modifies at least one of the at least one routing rule and the default access indication according to at least one of the configuration information and the current network state. As a shunt strategy.
  • the P-GW may be based on rule information (such as PCC rules, etc.) sent by the PCRF, and indication information sent by the UE (such as a default connection sent by the UE).
  • Rule information such as PCC rules, etc.
  • indication information sent by the UE (such as a default connection sent by the UE).
  • At least one type of information such as an indication indication, local configuration information, and current network status, determines whether to create or modify a routing rule.
  • the foregoing information includes, for example, specifying that certain data streams must be transmitted through a 3GPP network, current network status, such as a 3GPP network, and a non-3GPP network failure. Or poor signal quality, etc.
  • the second device When the second device is a UE, its own configuration information, such as a specific application set by the user in the UE, selects which access technology.
  • the UE When the UE is running in the application, the routing rule is generated or modified according to the above configuration information and the current network state.
  • the first type the routing rule generated by the first device includes: a route access technology, a flow description information, a negotiation indication, and a first routing rule identifier information, where the first routing rule identifier information is a rule name and a rule priority. At least one item;
  • the routing rule generated by the first device includes: a route access technology, a flow description information, a route access technology indication, and a second routing rule identifier information, where the second routing rule The identification information is at least one of a rule name and a rule priority.
  • the route accessing technology, the flow description information, the negotiation indication, the rule name, and the rule priority routing rule are taken as an example;
  • the routing access technology, the flow description information, the rule name, the route access technology indication, and the rule priority routing rule are taken as an example.
  • the negotiation indication is used to identify the modification permission of the UE to the routing rule, and the value is the permission negotiation identifier or the negotiation negotiation identifier.
  • the negotiation indication value is the permission negotiation identifier
  • the UE selects the route access technology or other access technology in the routing rule.
  • the negotiation indication value is the forbidden negotiation identifier
  • the UE selects the route access in the routing rule.
  • the route access technology indication is used to identify the use permission of the route access technology in the route rule,
  • the value is a forbidden value or an allowable value.
  • the route access technology indicates that the value is a forbidden value, it indicates that the route access technology in the route rule is forbidden; or when the route access technology indicates that the value is allowed, it indicates that the value is allowed.
  • the routing rule to which the negotiation indication belongs is a routing rule for prohibiting negotiation
  • the route access technology indicates that the value is a forbidden value, it indicates that the route access technology indicates that the route rule belongs to the route rule that prohibits negotiation.
  • the routing access technology indicates that the rule of the routing rule corresponding to the forbidden value has a higher priority than the rule that the routing access technology indicates that the routing rule corresponds to the allowed value.
  • the negotiation indication in the routing rule generated by the first device is null;
  • the route access technology indication included in the routing rule generated by the first device is equal to the allowed value.
  • the traffic splitting policy generated or modified by the first device is a routing rule
  • the first device sends the traffic splitting policy to the second device, where: the first device Carrying the routing rule on the bearer update request or the bearer new request transmission to After the MME receives the routing rule, the MME carries the non-access stratum (NAS) message to the second device; or
  • NAS non-access stratum
  • the first device carries the routing rule to the Trusted WLAN Access Gateway (TWAG) in the bearer update request or the bearer new request, so that the TWAG carries the routing rule after receiving the routing rule.
  • TWAG Trusted WLAN Access Gateway
  • the specified WLAN Control Plane protocol WLCP message is transmitted to the second device; or
  • the first device carries the routing rule to the bearer update request or the bearer new request, and transmits the route to the non-trusted access gateway (ePDG), so that the ePDG carries the routing rule and carries the routing rule. Transmitted to the second device in a Network Key Exchange Protocol 2 (IKEv2) message; or
  • IKEv2 Network Key Exchange Protocol 2
  • the first device sends the routing rule to the second device in the Packet Data Protocol (PDP) context modification request or the PDP new request.
  • PDP Packet Data Protocol
  • the specified WLCP message includes: WLCP NB_IFOM Request/Response message, WLCP Create Bearer Request/Response, WLCP Update Bearer Request/Response, and the like. If the generated routing rule is sent from the non-3GPP side (such as the TWAN network) to the UE, the message between the trusted WLAN access network (TWAN) and the UE needs to be defined as the formulated message. Let the message, for example, define a WLCP NB_IFOM Request/Response message, and then send the generated routing rule to the UE in the message.
  • TWAN trusted WLAN access network
  • the bearer update request or the bearer new request may transmit the routing rule in the following forms:
  • the first device adds the routing rule as a new parameter to the bearer update request or the bearer new request for transmission.
  • the first device adds the routing rule to the bearer context in the bearer update request or the bearer new request.
  • the first device adds the routing rule to the protocol configuration option (PCO) in the bearer update request or the bearer new request.
  • PCO protocol configuration option
  • NAS messages transmit routing rules in two ways: First, the first device causes the MME to add the routing rule as a new parameter to the NAS message for transmission, that is, the routing rule can be delivered as a separate parameter in the NAS message.
  • the first device causes the MME to add a routing rule to the PCO in the N AS message for transmission.
  • the MME continues to store the routing rule in the PCO in the NAS message.
  • the offloading policy generated by the first device includes at least one of a routing rule and a default access indication, and the first device sends the generated offloading policy to the second device, including:
  • the first device sends the traffic distribution policy to the MME, and the MME sends the second device to the bearer resource command after the MME receives the traffic distribution policy.
  • the first device sends the generated default access indication carrying message to the MME, so that the MME receives the default access indication, and then uses the default access indication. And the first device sends the default access indication to the TWAG in the WLCP PDN connection request, so that the TWAG receives the default access indication, The default access indication is sent to the second device in the session new request; or the first device sends the default access indication to the Internet Key Exchange Protocol 2 (IKEv2) message to send to the non- After the ePoG receives the default access indication, the ePDG carries the default access indication and sends the default access indication to the second device.
  • IKEv2 Internet Key Exchange Protocol 2
  • the first device adds the traffic distribution policy as a new parameter to the NAS message, or the first device adds the traffic distribution policy to the PCO in the NAS message, that is, the traffic distribution policy. It can be passed as a separate parameter in the NAS message, or it can be stored in the PCO in the NAS message.
  • the sending the default access indication in the NAS message, the session new request, or the WLCP PDN connection request includes: adding the default access indication to the NAS message, the session new request Or send in the PCO in the WLCP PDN connection request;
  • the default access indication is sent in the IKEv2 message, and includes: adding the default access indication as a new parameter to the IKEv2 message for sending.
  • Step 102 The first device receives and stores the confirmed offloading policy returned by the second device for the offloading policy, and performs data stream transmission based on the confirmed offloading policy.
  • the traffic splitting policy generated by the first device is a routing rule. Therefore, after the acknowledged traffic splitting policy is the confirmed routing rule, the first device receives the confirmed return from the second device. Diversion strategy, including:
  • the first device receives the other route that is not modified in the routing rule sent by the second device. Rules and updated routing rules that modify at least one routing rule; or
  • the first device receives the unmodified routing rule.
  • the second device may return the unmodified routing rule when returning the unmodified routing rule, and may also return only the unmodified routing rule identifier.
  • the routing rule is modified, that is, the routing access technology in the routing rule is modified.
  • the negotiation indication included in the at least one routing rule modified by the second device is to allow the negotiation identifier; or
  • the routing access technology indication included in the at least one routing rule modified by the second device is equal to the allowed value, that is, when the second device UE confirms the routing rule, it can only modify the routing rule that can be modified by the UE.
  • the first device receives the acknowledged traffic off policy returned by the second device for the traffic offloading policy, and further includes:
  • the determining result includes: the UE accepts the bearer update process initiated by the network side or the bearer newly built repair The process is changed, or the UE does not accept the bearer update process initiated by the network side or the bearer new modification process, and also includes the special cause value of the UE, such as UE refuse, IP traffic remove, N3GPP preferred, and the like.
  • the classification policy generated by the first device includes at least one of a routing rule and a default access indication, and the first device receives the confirmed offloading policy returned by the second device for the offloading policy. , including:
  • the receiving, by the first device, the confirmed default access indication returned by the second device includes: if the second device receives the default connection according to at least one of the received rule information, the local configuration information, and the current network state. After the indication is modified, the first device receives the modified default access indication returned by the second device; or
  • the first device receives the unmodified default access indication returned by the second device.
  • the first device receives the confirmed routing rule returned by the second device, including:
  • the first device receives the routing rule sent by the second device.
  • Other routing rules modified and updated routing rules modified by at least one routing rule or
  • the first device receives the unmodified routing rule.
  • the negotiation indication included in the updated routing rule modified by the at least one routing rule is a forbidden negotiation identifier; or the route access technology indication included in the updated routing rule modified by the at least one routing rule To prohibit the value.
  • the network side After receiving the routing rule generated by the UE, the network side confirms the routing rule, that is, when the network side does not allow a certain routing access technology to transmit a certain data stream, the corresponding routing rule is forcibly modified and modified.
  • the updated routing rule is set to prohibit the UE from modifying again, and the UE must A routing rule that performs data stream transmission as specified by the routing rule.
  • an embodiment of the present invention further provides a method for negotiating a traffic distribution policy, where the specific processing process includes:
  • Step 201 The second device receives the offloading policy sent by the first device, and confirms the offloading policy, where the offloading policy includes at least one of the following: a default access indication and at least one routing rule.
  • the second device is a device that performs data stream transmission according to the offloading policy, and specifically, may be a core network device (such as a P-GW) or a UE. In this embodiment, only the second device is a P-GW or a UE. For example.
  • the first device is also a device that performs data stream transmission according to the offloading policy, and the first device is a UE, and the first device is a UE.
  • the second device is a UE, the first device is a core network device.
  • the traffic offloading policy received by the second device is at least one routing rule sent by the first device;
  • the traffic offloading policy received by the second device is at least one of a routing rule and a default access indication sent by the first device.
  • the routing rules sent by the first device include two forms:
  • the first type the routing rule sent by the first device includes: a route access technology, a flow description information, a negotiation indication, and a first routing rule identifier information, where the first routing rule identifier information is a rule name and a rule priority. At least one of; or
  • the routing rule sent by the first device includes: a route access technology, a flow description information, a route access technology indication, and a second routing rule identifier information, where the second routing rule identifier information is a rule name and a rule At least one of the priorities.
  • the route accessing technology, the flow description information, the negotiation indication, the rule name, and the rule priority routing rule are taken as an example;
  • the routing access technology, the flow description information, the rule name, the route access technology indication, and the rule priority routing rule are taken as an example.
  • the routing rule includes: the routing access technology, the flow description information, the negotiation indication, and the first routing rule identifier information
  • the negotiation indication is used to identify the modification permission of the UE to the routing rule, and the value is the permission negotiation identifier or the negotiation negotiation identifier.
  • the negotiation indication value is the permission negotiation identifier
  • the UE selects the route access technology or other access technology in the routing rule.
  • the negotiation indication value is the forbidden negotiation identifier, the UE selects the route access in the routing rule.
  • the route access technology indication is used to identify the use permission of the route access technology in the route rule,
  • the value is a forbidden value or an allowable value.
  • the route access technology indicates that the value is a forbidden value, it indicates that the route access technology in the route rule is forbidden; or when the route access technology indicates that the value is allowed, it indicates that the value is allowed.
  • the routing rule to which the negotiation indication belongs is a routing rule for prohibiting negotiation
  • the route access technology indicates that the value is a forbidden value, it indicates that the route access technology indicates that the route rule belongs to the route rule that prohibits negotiation.
  • the routing access technology indicates that the rule of the routing rule corresponding to the forbidden value has a higher priority than the rule that the routing access technology indicates that the routing rule corresponds to the allowed value.
  • the negotiation indication in the routing rule sent by the first device is empty when the first device is a UE;
  • the route access technology indication included in the routing rule sent by the first device is equal to the allowed value.
  • the traffic offloading policy received by the second device is a routing rule sent by the first device, and the second device confirms the trafficking policy, including:
  • the second device confirms the routing rule, and specifically includes:
  • the at least one routing rule is performed on the at least one routing rule. Modifying, and generating a modified updated routing rule, using the other routing rules that are not modified in the routing rule and the updated routing rule modified by the at least one routing rule as the confirmed routing rule; or The second device determines that at least one of its own configuration information and the current network state matches all the routing rules in the routing rule, or at least one of its own configuration information and the current network state does not match the routing rule.
  • the new routing rule is not modified.
  • the unmodified routing rule is used as the confirmed routing rule.
  • the traffic splitting policy received by the second device is at least one of a routing rule and a default access indication sent by the first device, and the second device confirms the trafficking policy.
  • the second device confirms the default access indication in the offloading policy, and/or the second device confirms the routing rule in the offloading policy.
  • the second device confirms the default access indication, including:
  • the default access indication is modified and will be modified.
  • the default access indication is used as the default access indication after confirmation; or
  • the second device determines that the received rule information, the indication information sent by the UE, the local configuration information, and the current network status match the default access indication, the default access indication is not modified, and the default connection is not modified.
  • the incoming indication is used as the default access indication after confirmation.
  • the second device confirms the routing rule, including:
  • the at least one routing rule is modified and generated.
  • the modified routing rule, the other routing rules that are not modified in the routing rule, and the updated routing rule modified by modifying at least one routing rule are used as the confirmed routing rule; or
  • the second device determines that the received rule information, the indication information sent by the UE, the local configuration information, and the current network status match all the routing rules in the routing rule, the routing rule is not modified, and the unmodified routing rule is used as the confirmation. Routing rules.
  • the modifying, by the second device, the at least one routing rule includes:
  • the second device modifies the route access technology included in the at least one routing rule, and When the at least one routing rule includes the negotiation indication, the negotiation indication included in the at least one routing rule is set as the forbidden negotiation identifier; when the at least one routing rule includes the route access technology indication, the at least one routing rule is included The included route access technology indication is set to a forbidden value.
  • Step 202 The second device stores the confirmed offloading policy, and returns the confirmed offloading policy to the first device, and performs data stream transmission based on the confirmed offloading policy.
  • the routing rule confirmed by the second device is compared with the new routing rule generated by the first device received, and the number does not change, only some of the routing rules are modified.
  • the second device when the second device is the UE, where the confirmed offloading policy is the confirmed routing rule, the second device returns the confirmed offloading policy to the first device, including:
  • the second device carries the confirmed routing rule and the NAS message to the MME; after the MME receives the confirmed routing rule, the advertised routing rule is carried in the bearer update response or the bearer new response and transmitted to the first Equipment; or
  • the second device carries the confirmed routing rule in the specified WLCP message and transmits it to the TWAG, so that after receiving the confirmed routing rule, the TWAG carries the confirmed routing rule in the bearer update response or the bearer new response.
  • the first device or
  • the second device carries the confirmed routing rule in the IKEv2 message and transmits it to the ePDG, so that after receiving the confirmed routing rule, the ePDG carries the confirmed routing rule in the bearer update response or the bearer new response and transmits the first to the first device.
  • the second device carries the confirmed routing rule in the NAS message and transmits the message to the MME, including:
  • the second device adds the confirmed routing rule as a new parameter to the NAS message and transmits it to the MME.
  • the second device adds the confirmed routing rule to the PCO in the NAS message and transmits the result to the MME.
  • the MME transmits the confirmed routing rule to the first device in the bearer update response or the bearer new response, including:
  • the MME adds the confirmed routing rule as a new parameter to the bearer update response or the bearer new response to be transmitted to the first device; or The MME adds the confirmed routing rule to the bearer context in the bearer update response or the bearer new response to be transmitted to the first device; or
  • the MME adds the confirmed routing rule to the PCO in the bearer update response or bearer new response and transmits it to the first device.
  • the second device returns the confirmed offloading policy to the first device, and further includes: sending, by the second device, a bearer update process generated by the confirmed offloading policy or a determination result of the bearer new modification process.
  • the confirmed offloading policy includes at least one of the confirmed routing rule and the confirmed default access indication, and the second device returns the confirmed offloading policy to the
  • the first device includes:
  • the second device transmits the confirmed offloading policy to the bearer update request or the bearer new request to be transmitted to the MME, so that the MME receives the acknowledged offloading policy.
  • the spoofing policy is carried in the NAS message and transmitted to the first device; or the second device is sent to the first device in the PDP context modification request or the PDP context new request in the PDP context modification request; Or
  • the second device sends the confirmed default access indication to the MME in the session newly created response, so that the MME receives the acknowledged After the default access indication, the acknowledgment default access indication is carried in the NAS message and sent to the first device; or the second device carries the confirmed default access indication in the session new response. And sending the TWAG to the TWAG, so that the TWAG receives the queried default access indication, and sends the confirmed default access indication to the first device in the WLCP PDN connection response; or, the second device The acknowledgment default access indication is carried in the session new response and sent to the ePDG, so that the ePDG receives the queried default access indication, and carries the confirmed default access indication in the IKEv2 message. Sent to the first device.
  • the spoofed offloading policy is carried in the NAS message and transmitted to the first device, including:
  • the confirmed offloading policy is added to the PCO in the NAS message and transmitted to the first device.
  • the confirmed offloading policy is the default access indication after the confirmation
  • the confirmed default access indication is sent in the NAS message, the session new response, or the WLCP PDN connection response, including:
  • the acknowledgment default access indication is carried in the IKEv2 message, including:
  • the confirmed default access indication is added as a new parameter to the IKEv2 message for transmission.
  • routing rule negotiation method provided in the foregoing embodiment, a specific example of routing rule negotiation in five different scenarios is also provided in the embodiment of the present invention.
  • Example 1 The embodiment of the present invention provides a routing rule negotiation mechanism initiated by the network side.
  • the network side negotiates with the UE through the bearer resource update process.
  • the specific process of the routing rule negotiation is as follows:
  • the UE simultaneously accesses a PDN connection from a 3GPP network and a non-3GPP network, and at the same time, there are multiple data flow routing information between the UE and the P-GW.
  • Step 301 The Home PCRF (hPCRF) initiates an IP connection access network session to modify the IP-CAN Session Modification process, and modifies parameters of some data flows, such as changing the routing access technology of a certain data flow from 3GPP to non- 3GPP.
  • hPCRF Home PCRF
  • Step 302 The P-GW determines to create or modify a routing rule based on at least one type of information, such as rule information (such as a charging policy) sent by the hPCRF, indication information sent by the UE, local configuration information, and current network status, to generate a new The routing rule, the P-GW initiates a bearer update procedure according to the new routing rule, that is, sends a bearer update request Update Bearer Request, and sends a new routing rule generated by the P-GW to the UE.
  • rule information such as a charging policy
  • a new routing rule generated by the P-GW such as the first extended routing rule or the second extended routing rule provided by the foregoing embodiment.
  • the number of new routing rules generated by the P-GW can be one or Thought more than one.
  • the bearer update process may be triggered on the 3GPP side, or may be triggered on the non-3GPP side, or may be triggered on the 3GPP side and the non-3GPP side.
  • the embodiment of the present invention does not limit this. In this embodiment, only the 3GPP side is used. Take the bearer update process as an example.
  • Step 303 The P-GW sends an Update Bearer Request message to the S-GW on the 3GPP side, where the Update Bearer Request carries a new routing rule generated by the P-GW.
  • the routing rule is not limited to be transmitted through the new parameter in the Update Bearer Request message, and the routing rule may be transmitted through the bearer context bearer context in the Update Bearer Request message, and may also pass The Protocol Configuration Option (PCO) in the Update Bearer Request message is transmitted. In this embodiment, only the routing rule is transmitted through the Update Bearer Request as an example.
  • PCO Protocol Configuration Option
  • Step 304 The S-GW sends the routing rule to the MME through the Update Bearer Request.
  • the NAS message in the Downlink NAS transport message carries the routing rule, and may be, but is not limited to, the routing rule being stored in the NAS message as a new parameter, and may also be stored in the PCO in the NAS message.
  • Step 306 After receiving the Downlink NAS transport message carrying the routing rule, the eNB directly sends the NAS message carrying the routing rule to the UE.
  • Step 307 After receiving the updated routing rule, the UE confirms the routing rule, and transmits the confirmed routing rule to the eNB through the NAS message.
  • the UE may modify the routing rule included in the routing rule to allow the negotiation rule to be used.
  • the UE may modify the routing rule (non-prohibited routing rule) indicated by the routing access technology included in the routing rule to be a non-specified value.
  • the UE may modify the routing rule that can be modified according to at least one of its own configuration information and the current network state. Generally, the UE modifies the routing access technology in the routing rule to an access technology selected by the UE, such as 3GPP or WLAN, etc. For no modification or modification The routing rule, the UE keeps the original routing entry unchanged.
  • the updated routing rule includes the unchanged routing rule and the modified routing rule to be sent to the network side.
  • the UE receives 10 routing rules and modifies 2 routing rules according to its configuration.
  • the routing rules updated by the UE are 8 unchanged routing rules and 2 modified routing rules, and the UE will Ten updated routing rules are sent to the network side.
  • the UE When the UE sends the unchanged routing rule to the network side, it can also return the identifier corresponding to the unchanged routing rule to the network side to save network resources.
  • Step 308 After receiving the updated routing rule, the eNB sends the Uplink NAS Transport message to the MME through the uplink non-access stratum.
  • the updated routing rule is transmitted as a separate parameter in the NAS message in the Uplink NAS Transport message or transmitted through the PCO message in the NAS message.
  • Step 309 After receiving the updated routing rule, the MME sends the updated routing rule to the S-GW by sending a bearer update response Update Bearer Response message.
  • Step 310 The S-GW sends the received updated routing rule to the PGW through the Update Bearer Response.
  • Step 311 The P-GW sends an IP-CAN Session Modification message to the hPCRF, and sends the routing information negotiated by the UE, that is, the routing rule updated by the UE, to the hPCRF.
  • Step 312 In the subsequent work, the P-GW initiates a subsequent bearer creation process, bearer update process, or bearer deletion process based on the updated routing rule confirmed by the UE.
  • the updated routing rule indicates that it is transmitted on the 3GPP side, and the current 3GPP side does not have any bearer that can be used to transmit the foregoing data flow, and the P-GW initiates a bearer resource creation or bearer resource update process on the 3GPP side. That is, the bearer newly created request Create Bearer Request message or Update Bearer Request is sent to the S-GW and the MME to create or modify a dedicated bearer.
  • the specific operation is the same as the existing process, and is not described here.
  • the updated routing rule indicates that it is transmitted on the non-3GPP side, but currently
  • the 3GPP side has a dedicated bearer corresponding to the data stream
  • the P-GW first initiates a bearer resource creation process or a bearer update process in the non-3GGP, and then deletes the dedicated bearer corresponding to the 3GPP, that is, sends a bearer deletion request Delete Bearer Request message to the S.
  • the GW and the MME perform the deletion of the dedicated bearer, and the specific operations are the same as the existing processes, and are not described here.
  • the example 1 is applicable to the network architecture of the 3GPP and the non-3GPP network interworking.
  • the embodiment of the present invention can also be used in the architecture of the 2/3G network and the non-3GPP network interworking.
  • the P-GW generates a new one.
  • the routing rule can be sent to the UE through a Packet Data Protocol (PDP) context modification request.
  • PDP Packet Data Protocol
  • the 3GPP side sends a new routing rule to the UE.
  • a specified signaling message is required to perform routing rule transmission.
  • the routing rule is sent from the non-3GPP side to the UE, the new message between the TWAN and the UE needs to be defined to interact, such as defining a WLCP NB_IFOM Request/Response message, and carrying the routing rule in the message.
  • Example 2 the embodiment of the present invention further provides another routing rule negotiation mechanism initiated by the network side, and the network side negotiates with the UE through the bearer resource creation process or the bearer update process, as shown in FIG. 4, the routing rule negotiation
  • the specific process is:
  • the UE accesses a PDN connection from a 3GPP network and a non-3GPP network, TWAN.
  • Step 401 The hPCRF initiates an IP-CAN Session Modification process to modify parameters of some data streams, such as changing the access technology of a certain data stream from 3GPP to non-3GPP, and generating a new routing rule.
  • the P-GW determines to create or modify a routing rule based on at least one type of information, such as rule information (such as PCC rules), local configuration information, and current network status, which is sent by the PCRF, to generate a new routing rule, and initiates according to the new routing rule.
  • Rule information such as PCC rules
  • local configuration information such as PCC rules
  • current network status which is sent by the PCRF
  • bearer new process bearer update process:
  • the new routing rule generated by the P-GW indicates that it is transmitted on the 3GPP side, but currently The 3GPP side does not have any bearer that can be used to transmit the data stream.
  • the P-GW initiates a bearer resource creation or bearer resource update process on the 3GPP side, that is, sends a bearer new request Create Bearer Request message or a bearer update request Update Bearer Request to the S-GW. Create or modify a dedicated bearer.
  • the process of the bearer creation process and the bearer modification update process may be triggered on the 3GPP side, or may be triggered on the non-3GPP side, or may be triggered simultaneously on the 3GPP side and the non-3GPP side, which is not limited in the embodiment of the present invention.
  • the bearer new process and the bearer update process are performed on the 3GPP side.
  • the new routing rule generated by the P-GW is the first extended routing rule or the second extended routing rule provided by the foregoing embodiment.
  • the number of new routing rules generated by the P-GW can be one or multiple.
  • Step 402 The P-GW sends a Create Bearer Request or Update Bearer Request to the S-GW, and the S-GW sends a Create Bearer Request or Update Bearer Request to the MME.
  • the Create Bearer Request or Update Bearer Request carries the new routing rules generated by the P-GW.
  • the Create Bearer Request or the Update Bearer Request further includes a new or updated Traffic Flow Template (TFT) information, where the TFT information includes related flow description information.
  • TFT Traffic Flow Template
  • the TFT that carries the data flow description information is sent in the Create bearer Request message, where the TFT includes: a destination IP address of the data flow source, and a source destination port. At least one parameter, such as the type of protocol used.
  • the TFT that carries the data flow description is sent in the Update bearer Request message, and the TFT also includes: the destination IP address of the data flow source, and the source destination. At least one parameter such as the port number, the protocol type used, and so on.
  • the routing rule is not limited to being transmitted through a separate parameter in the Create Bearer Request or the Update Bearer Request, and the routing rule may be transmitted through the bearer context bearer context in the Create Bearer Request or the Update Bearer Request. It can also be transmitted through the Protocol Configuration Option (PCO) message in Create Bearer Request or Update Bearer Request. In this implementation In the example, only the routing rule is transmitted through the Update Bearer Request as an example.
  • PCO Protocol Configuration Option
  • Step 403 The MME sends the routing rule to the eNB through the downlink non-access stratum transmission Downlink NAS transport message.
  • the MME transmits the routing rule by using the NAS message in the Downlink NAS transport message, where the NAS message in the Downlink NAS transport message carries the routing rule, and may be, but is not limited to, storing the routing rule as a new parameter in the NAS. In the message, it can also be stored in the PCO in the NAS message.
  • the new or modified TFT is also sent at the same time as the routing rule is sent.
  • Step 404 After receiving the Downlink NAS transport message carrying the routing rule, the eNB sends the routing rule to the UE by using the NAS message.
  • the eNB also sends a newly created or modified TFT while sending the routing rule.
  • the NAS message carries the routing rule, and may be, but is not limited to, the routing rule being stored in the N AS message as a new parameter, and may also be stored in the PCO in the NAS message.
  • Step 405 After receiving the routing rule, the UE confirms the routing rule, and after the confirmation is completed, sends the updated routing rule to the eNB through the NAS message.
  • the process of confirming the received routing rule by the UE is the same as the step 307.
  • the routing rule that is not allowed to be specified in the negotiation indication or the included routing access technology is modified, and is not described here.
  • the updated routing rule includes the unchanged routing rule and the modified routing rule to be sent to the network side.
  • the UE determines whether to accept the bearer new process initiated by the network side or the update process based on the confirmed routing rule.
  • the UE accepts the bearer new process or bearer update; otherwise, The UE may reject the bearer new flow or bearer update request.
  • the UE selects the non-3GPP as the transmission channel that carries the new flow or the corresponding data flow in the update process, the UE carries the special cause value to indicate that the network side rejects the bearer new process and the bearer update process.
  • the foregoing special cause value may be a UE refuses (existing cause value), an IP traffic remove, an N3GPP preferred, etc., and is not limited in this embodiment of the present invention.
  • Step 406 After receiving the updated routing rule, the eNB sends the Uplink NAS Transport message to the MME through the uplink non-access stratum.
  • the updated routing rule may be transmitted not only as a separate parameter in the NAS message but also through the PCO message.
  • Step 407 After receiving the updated routing rule, the MME sends the new bearer response Create Bearer Response or the update response Update Bearer Response to the S-GW/P-GW.
  • the Create Bearer Response or the Update Bearer Response message carries not only the routing rule confirmed by the UE but also the message processing result, that is, whether the bearer new process or the bearer update process is accepted by the UE. If the UE refuses to carry the new process or the bearer update process, the MME, the S-GW, and the P-GW also need to delete the new bearer or restore the modified bearer resource based on the cause value indicated by the UE, and the specific operation is the same as the existing process. This will not be repeated.
  • the network architecture of the example 2 is the same as that of the network architecture of the 3GPP and the non-3GPP network.
  • the embodiment of the present invention can also be used in the architecture of the 2/3G network and the non-3GPP network.
  • the new routing rule generated by the P-GW can be sent to the UE through a Packet Data Protocol (PDP) context modification request.
  • PDP Packet Data Protocol
  • the 3GPP side sends a new routing rule to the UE.
  • a specified signaling message is required to perform routing rule transmission.
  • a new routing rule is sent from the non-3GPP side to the UE, a new message between the TWAN and the UE needs to be defined to interact, such as defining a WLCP Create Bearer Request/Response or a WLCP Update Bearer Request/Response message, and The above message carries a routing rule.
  • the embodiment of the present invention further provides a traffic distribution policy negotiation mechanism initiated by the UE, where the UE performs the traffic distribution policy negotiation with the network side by using the bearer resource update process, as shown in FIG.
  • the specific process of negotiation is as follows:
  • Step 501 The UE generates at least one of a new routing rule and a default access indication according to at least one of its own configuration information and the current network state.
  • the UE sends a bearer resource modification request Request Bearer Resource Modification message to the eNB.
  • the UE-supplied traffic policy negotiation process may be performed on the 3GPP side, or on the non-3GPP side, or the 3GPP side and the non-3GPP side, and the embodiment of the present invention does not limit this. In this embodiment, only the 3GPP side is used. Initiated as an example.
  • the new routing rule generated by the UE such as the first extended routing rule or the second extended routing rule provided by the foregoing embodiment.
  • the number of new routing rules generated by the UE may be one or multiple. If the new routing rule generated by the UE is the first extended routing rule, the negotiation indication included in the routing rule is empty; if the new routing rule generated by the UE is the second extended routing rule, the routing rule The priority of the route access technology included in the route is not specified. That is, the new route rule generated by the UE is a non-prohibited route rule.
  • the UE needs to update the default access technology, the UE sends a default access technology indication to the network side in the PCO.
  • the generated new traffic distribution policy also includes bearer resource modification information such as Traffic Aggregate Description (TAD).
  • TAD Traffic Aggregate Description
  • the offloading policy is not limited to being transmitted as a separate parameter in the NAS message in the Request Bearer Resource Modification, and the offloading policy may also be transmitted through the PCO in the NAS message.
  • Step 502 The eNB continues to send the received traffic distribution policy and the bearer modification information such as TAD to the MME by using a Request Bearer Resource Modification message.
  • Step 503 The MME continues to send the received traffic distribution policy and the bearer modification information such as the TAD to the S-GW by using the Bearer Resource Command message.
  • Step 504 The S-GW continues to send the received separation policy and bearer modification information such as TAD to the P-GW through the Bearer Resource Command message.
  • Step 505 After receiving the offloading policy, the P-GW initiates an IP-CAN session to modify the IP-CAN Session Modification process.
  • the P-GW notifies the H-PCRF of the routing information of the data flow based on the new traffic-dividing policy generated by the UE, and the h-PCRF determines the traffic-dividing policy of the data flow to notify the P-GW.
  • Step 506 The P-GW confirms the shunting policy generated by the received UE based on at least one type of information, such as the rule information (such as a charging policy) sent by the hPCRF, the indication information sent by the UE, the local configuration information, and the current network status. And in the subsequent initiated bearer new process or bearer update process, the P-GW confirmed offloading policy is sent to the UE.
  • the rule information such as a charging policy
  • the P-GW may perform the modification of the routing rules that are not enforced on the network side, and modify the routing rules that are not supported by the network side.
  • the routing rule is set to disable the routing rule. For example, if the routing rule is the first extended routing rule, the P-GW sets the negotiation indication of the routing rule to the forbidden negotiation identifier; if the routing rule is the second extended The routing rule, the P-GW sets the route access technology indication of the routing rule to a specified value, that is, the network side does not allow an access technology to transmit a certain data stream, and other routing policies are maintained with the routing policy requested by the UE. Consistent.
  • the P-GW determines that at least one of the received rule information, the local configuration information, and the current network status does not match the default access indication.
  • the default access indication is modified, and the modified default access indication is used as the default access indication after the acknowledgment; otherwise, the default access indication is not modified, and the default access indication is not modified.
  • the default access indication after confirmation As the default access indication after confirmation.
  • Step 507 The P-GW indicates that the IP-CAN Session Modification process ends.
  • Example 3 is the same as the network architecture of the example 1 and the example 2, and is a network architecture in which the 3GPP and the non-3GPP network are interworking.
  • the embodiment of the present invention can also be used in the architecture of the 2/3G network and the non-3GPP network interworking.
  • the P-GW confirmed traffic off policy may be sent to the UE through the PDP context modification request.
  • the embodiment of the present invention further provides a routing rule negotiation mechanism initiated by the UE.
  • the UE performs default access indication negotiation with the network side by using the PDN connection establishment process on the 3GPP side, as shown in FIG.
  • the specific process of the access indication negotiation is as follows:
  • the UE starts the PDN connection establishment process on the 3GPP side.
  • the UE may have established the PDN connection on the non-3GPP side, or the UE does not establish a PDN connection on the non-3GPP side.
  • Step 601 The UE generates a default access indication according to the configuration information of the UE.
  • the UE initiates a PDN connection establishment procedure on the 3GPP side, and sends a PDN Connectivity Request to the MME, where the PCO included in the PDN Connectivity Request message carries the UE.
  • the generated default access indication is the default access indication.
  • the default route indication generated by the UE indicates that the route access technology transmission using the default access indication when the service flow does not match any routing rule.
  • Step 602 After receiving the PDN Connectivity Request sent by the UE, the MME sends a session creation request Create Session Request carrying the default access indication to the S-GW.
  • Step 603 The S-GW continues to send the Create Session Request carrying the default access indication to the P-GW.
  • Step 604 In the IP-CAN session establishment process between the P-GW and the PCRF, the PCRF sends the routing policy information corresponding to the data flow to the P-GW.
  • Step 605 The P-GW generates a default access indication for the received UE based on at least one type of information, such as rule information (such as a charging policy, etc.) sent by the PCRF, indication information sent by the UE, local configuration information, and current network status. Confirm, and send a session new response Create Session Response, and send the default access indication confirmed by the P-GW to the S-GW.
  • rule information such as a charging policy, etc.
  • the P-GW confirmed routing rule can be transmitted not only through Create Session Response, but also through PDN Connectivity Accept, Create Bearer Request, Bearer Setup Request, N AS message, and the like.
  • Step 606 The S-GW continues to send the Create Session Response, and sends the default access indication confirmed by the P-GW to the MME.
  • Step 607 The MME sends the PCO with the default access indication to the UE by using the NAS message.
  • Step 609 The UE receives the confirmed default access indication sent by the network side.
  • the default access indication when the default access indication is transmitted, the default access indication is sent by using the PCO carrying message, that is, all the information of the default access indication is included in the PCO, where the PCO carries the default access. Instructions.
  • the embodiment of the present invention further provides a default access indication negotiation mechanism initiated by the UE, and the UE performs default access indication negotiation with the network side by using the PDN connection establishment process on the non-3GPP side, as shown in FIG. 7
  • the specific process of the default access indication negotiation is as follows:
  • Step 701 The UE generates a default access indication according to at least one of its own configuration information and the current network state.
  • the UE initiates a PDN connection establishment procedure in the non-3GPP network, such as the WLAN side, and the UE sends the PDCCH to the TWAG.
  • the WLCP PDN connection request WLCP PDN Connection Request, where the WLCP PDN Connection Request request carries the default access indication generated by the UE, or the UE sends an IKEv2 message to the ePDG, where the IKEv2 message carries the default connection generated by the UE. Enter the instructions.
  • Step 702 The TWAG or ePDG sends a session creation request Create Session Request carrying the default access indication to the P-GW.
  • Step 703 In the IP-CAN session establishment process between the P-GW and the hPCRF, the hPCRF sends the routing policy information corresponding to the data flow to the P-GW.
  • Step 704 Update the PDN gateway address between the P-GW and the HSS.
  • Step 705 The default access indication generated by the P-GW to the received UE based on at least one type of information, such as rule information (such as a charging policy, etc.) sent by the hPCRF, indication information sent by the UE, local configuration information, and current network status.
  • Rule information such as a charging policy, etc.
  • the acknowledgment is performed, and the session creation response Create Session Response is sent, and the default access indication confirmed by the P-GW is sent to the TWAG or the ePDG.
  • the P-GW may also initiate a bearer new procedure or a bearer update procedure to send the confirmed default access indication to the UE.
  • the P-GW may perform the default access indication that is not enforced on the non-network side, and remains unchanged, and is not modified, and is not supported by the network side.
  • the default access indication is modified.
  • Step 706 Establish a GPRS Tunnel Protocol (GTP Tunnel) GTP tunnel between the TWAG/ePDG and the P-GW.
  • GTP Tunnel GPRS Tunnel Protocol
  • Step 707 The TWAG sends the acknowledged default access indication sent by the P-GW to the UE through the WLCP PDN connection response WLCP DPN Connection Response message, or the ePDG passes the confirmed default access indication sent by the P-GW through the IKEv2. Send to the UE.
  • the message that transmits the default access indication except the IKEv2 message is the default access indication by using the PCO carrying message, that is, the default access indication is transmitted.
  • All information includes a PCO, where the default access indication is carried in the PCO.
  • the default access indication is passed as a new parameter.
  • the embodiment of the present invention further provides a traffic distribution policy negotiation device, where the device includes: a sending unit 801 and a receiving unit 802, where
  • the sending unit 801 is configured to send the offloading policy to the second device, where the offloading policy includes at least one of: a default access indication and at least one routing rule;
  • the receiving unit 802 is configured to receive and store the confirmed offloading policy returned by the second device for the offloading policy, and perform data stream transmission based on the confirmed offloading policy.
  • the offloading policy negotiation device is a core network device or a user equipment UE.
  • the offloading policy negotiation device further includes:
  • the generating unit 800 is configured to: before the sending unit 801 sends the offloading policy to the second device, the component streaming policy, the generating unit 800 is specifically configured to:
  • the generating unit 800 When the offloading policy negotiation device is the core network device, the generating unit 800 generates at least one routing rule as a traffic distribution policy according to at least one of the received rule information, the indication information sent by the UE, the local configuration information, and the current network state; or
  • the generating unit 800 When the offloading policy negotiation device is the UE, the generating unit 800 generates at least one of the at least one routing rule and the default access indication according to at least one of its own configuration information and the current network state, as the trafficking policy.
  • the routing rules include: a route access technology, a flow description information, a negotiation indication, and a a routing rule identifier information, where the first routing rule identifier information is at least one of a rule name and a rule priority; or
  • the routing rule includes: a route access technology, a flow description information, a route access technology indication, and a second routing rule identifier information, where the second routing rule identifier information is at least one of a rule name and a rule priority.
  • the negotiation indication is used to identify the modification permission of the UE to the routing rule, and the value is the permission negotiation identifier or the prohibition.
  • the negotiation identifier when the negotiation indication value is the permission negotiation identifier, indicates that the UE selects the route access technology or other access technology in the routing rule; when the negotiation indication value is the forbidden negotiation identifier, the UE selects the routing rule. Or routing access technology; or, when the routing rule includes: a route access technology, a flow description information, a route access technology indication, and a second routing rule identifier information, the route access technology indication is used to identify a route in the route rule.
  • the access permission of the access technology is a forbidden value or an allowable value.
  • the route access technology indicates that the value is a forbidden value, the route access technology in the routing rule is forbidden; or when the route access technology indicates When the value is allowed, it indicates that the route access technology in the routing rule is allowed.
  • the routing rule to which the negotiation indication belongs is a routing rule that prohibits negotiation
  • the route access technology indicates that the value is a forbidden value, it indicates that the route access technology indicates that the route rule belongs to the route rule that prohibits negotiation.
  • the routing access technology indicates that the rule priority of the routing rule corresponding to the forbidden value is higher than the rule priority of the routing rule indicated by the routing access technology as the allowed value.
  • the negotiation indication in the routing rule is empty
  • the route access technology indication contained in the routing rule is equal to the allowed value.
  • the sending unit 801 is specifically configured to: send, by the sending unit 801, the routing rule, in the bearer update request or the bearer new request, to the mobility management entity MME, so that the MME receives After the routing rule is passed, the routing rule is carried over the non-connected The inbound NAS message is transmitted to the second device; or
  • the sending unit 801 carries the routing rule to the trusted access gateway TWAG in the bearer update request or the bearer new request, so that after the TWAG receives the routing rule, the routing rule is carried in the specified WLAN control plane protocol WLCP message.
  • the second device or
  • the sending unit 801 carries the routing rule to the non-trusted access gateway ePDG in the bearer update request or the bearer new request, so that after the ePDG receives the routing rule, the routing rule is carried in the network key agreement protocol IKEv2 message and transmitted to the Second device; or
  • the sending unit 801 sends the routing rule to the second device in the packet data protocol PDP context modification request or the PDP new request.
  • the sending unit 801 when the sending unit carries the routing rule in the bearer update request or the bearer new request, the sending unit 801 is specifically configured to:
  • the sending unit 801 adds the routing rule as a new parameter to the bearer update request or the bearer new request in the transmission; or
  • the sending unit 801 adds the routing rule to the bearer context in the bearer update request or the bearer new request; or
  • the sending unit 801 adds the routing rule to the protocol in the bearer update request or the bearer new request configuration option PCO.
  • the sending unit 801 is configured to: when the MME carries the routing rule in the non-access stratum NAS message, specifically:
  • the sending unit 801 causes the MME to add the routing rule as a new parameter to the NAS message for transmission; or
  • the sending unit 801 causes the MME to add a routing rule to the PCO in the NAS message for transmission.
  • the sending unit 801 is specifically configured to: when the offloading policy includes the routing rule, the sending unit 801 carries the offloading policy in the NAS message and sends the message to the MME, so that the MME receives the offloading After the policy, the offloading policy is carried in the bearer resource command to send the second device; or
  • the sending unit 801 When the offloading policy is the default access indication, the sending unit 801 carries the default access indication to the NAS.
  • the message is sent to the MME, so that after receiving the default access indication, the MME carries the default access indication in the session new request and sends it to the second device; or, the sending unit 801 carries the default access indication to the WLCP.
  • the packet data network PDN connection request is sent to the TWAG, so that after the TWAG receives the default access indication, the default access indication is carried in the session new request and sent to the second device; or, the sending unit 801 is connected by default.
  • the ingress indication is carried in the network key agreement protocol IKEv2 message and sent to the non-trusted access gateway ePDG, so that after receiving the default access indication, the ePDG carries the default access indication in the session new request and sends it to the second. device.
  • the sending unit 801 is configured to: when the offloading policy is sent in the NAS message, specifically:
  • the sending unit 801 adds the offloading policy as a new parameter to the NAS message for sending; or the sending unit 801 adds the offloading policy to the PCO in the NAS message for transmission.
  • the sending unit 801 is configured to: when the default access indication is carried in the NAS message or the WLCP PDN connection request, specifically:
  • the sending unit 801 adds the default access indication to the PCO in the NAS message or the WLCP PDN connection request; or
  • the sending unit 801 enables the MME or the TWAG to carry the default access indication in the session new request, specifically for:
  • the sending unit 801 causes the MME or TWAG to add a default access indication to the PCO in the session new request to send; or
  • the sending unit 801 when the offloading policy is the default access indication, is specifically used to:
  • the sending unit 801 adds the default access indication as a new parameter to the IKEv2 message for transmission.
  • the receiving unit 802 is specifically configured to: if the second device routes at least one of the received routing rules according to at least one of the configuration information and the current network state After the rule is modified, the receiving unit 802 receives other routing rules that are not modified in the routing rule sent by the second device, and updated routing rules that modify the at least one routing rule; or If the second device does not modify the received routing rule, the receiving unit 802 receives the unmodified routing rule.
  • the negotiation indication included in the at least one routing rule modified by the second device is to allow the negotiation identifier
  • the route access technology indication included in the at least one routing rule modified by the second device is equal to the allowed value.
  • the receiving unit 802 is further configured to:
  • the receiving unit 802 is specifically configured to: receive, by the receiving unit 802, at least one of the confirmed routing rule returned by the second device and the confirmed default access indication;
  • the receiving unit 802 is specifically configured to: when receiving the default access indication after the acknowledgment returned by the second device:
  • the receiving unit 802 receives the modification returned by the second device.
  • Default access indication or
  • the receiving unit 802 receives the unmodified default access indication returned by the second device;
  • the receiving unit 802 is configured to: if the second device is configured according to the received rule information, the indication information sent by the UE, the local configuration information, and the current network state, according to the queried routing rule returned by the second device, Receiving, by the receiving unit 802, the other routing rules that are not modified in the routing rule sent by the second device, and the updated routing rule that is modified after modifying the at least one routing rule; or
  • the receiving unit 802 receives the unmodified routing rule.
  • association included in the updated routing rule modified by at least one routing rule is to prohibit the negotiation logo;
  • the route access technology indication included in the updated routing rule modified by at least one routing rule is a forbidden value.
  • the embodiment of the present invention further provides a traffic distribution policy negotiation device, where the device includes: a confirmation unit 901 and a processing unit 902, where
  • the determining unit 901 is configured to receive the offloading policy sent by the first device, and confirm the offloading policy, where the offloading policy includes at least one of the following: a default access indication and at least one routing rule; and a processing unit 902, configured to store After the confirmed offloading policy, the confirmed offloading policy is returned to the first device, and the data flow is transmitted based on the confirmed offloading policy.
  • the offloading policy negotiation device is a user equipment UE or a core network device.
  • the offloading policy negotiation device is a UE
  • the offloading policy is at least one routing rule sent by the first device
  • the traffic distribution policy is at least one of at least one routing rule and a default access indication sent by the first device.
  • the routing rule sent by the first device includes: a route access technology, a flow description information, a negotiation indication, and a first routing rule identifier information, where the first routing rule identifier information is in a rule name and a rule priority. At least one item; or
  • the routing rule sent by the first device includes: a route access technology, a flow description information, a route access technology indication, and a second routing rule identifier information, where the second routing rule identifier information is at least one of a rule name and a rule priority.
  • the negotiation indication is used to identify the modification permission of the UE to the routing rule, and the value is the permission negotiation identifier or the prohibition.
  • the negotiation identifier when the negotiation indication value is the permission negotiation identifier, indicates that the UE selects the route access technology or other access technology in the routing rule; when the negotiation indication value is the forbidden negotiation identifier, the UE selects the routing rule. Or routing access technology; or, when the routing rule includes: a route access technology, a flow description information, a route access technology indication, and a second routing rule identifier information, the route access technology indication is used to identify a route in the route rule.
  • the access permission of the access technology is a forbidden value or an allowable value.
  • the route access technology indicates that the value is a forbidden value, the route access technology in the routing rule is forbidden; or when the route access technology indicates When the value is allowed, it indicates that the route access technology in the routing rule is allowed.
  • the routing rule to which the negotiation indication belongs is a routing rule that prohibits negotiation
  • the route access technology indicates that the value is a forbidden value, it indicates that the route access technology indicates that the route rule belongs to the route rule that prohibits negotiation.
  • the routing access technology indicates that the rule priority of the routing rule corresponding to the forbidden value is higher than the rule priority of the routing rule indicated by the routing access technology as the allowed value.
  • the negotiation indication in the routing rule sent by the first device is blank;
  • the route access technology indication in the routing rule sent by the first device is equal to the allowed value.
  • the confirming unit 901 is configured to:
  • the confirmation unit 901 confirms the routing rule, it is specifically used to:
  • the confirmation unit 901 determines that at least one of the configuration information and the current network state does not match at least one routing rule in the routing rule, and at least one routing rule is not a routing rule that prohibits negotiation, and at least one routing rule is modified, and Generating the modified updated routing rule, and using the other routing rules that are not modified in the routing rule and the updated routing rules that modify the at least one routing rule as the confirmed routing rule; or
  • the confirmation unit 901 determines that at least one of its own configuration information and the current network state matches all routing rules in the routing rule, or at least one of its own configuration information and the current network state does not match the routing rule in the routing rule.
  • the negotiated routing rule is forbidden, the routing rule is not modified, and the unmodified routing rule is used as the confirmed routing rule.
  • the determining unit 901 is configured to: confirm the default access indication in the trafficking policy, and/or confirm the routing rule in the trafficking policy;
  • the determining unit 901 is configured to: determine, by the determining unit 901, at least one of the received rule information, the indication information sent by the UE, the local configuration information, and the current network state.
  • the incoming indication does not match, the default access indication is modified, and the modified default access indication is used as the default access indication after confirmation; or
  • the confirmation unit 901 determines that the received rule information, the indication information sent by the UE, the local configuration information, and the current network status match the default access indication, the default access indication is not modified, and the unmodified default access indication is used as the default access indication.
  • the default access indication after confirmation;
  • the confirmation unit 901 confirms the routing rule, it is specifically used to:
  • the confirmation unit 901 determines that at least one of the received rule information, the indication information sent by the UE, the local configuration information, and the current network state does not match at least one routing rule in the routing rule, and modifies at least one routing rule, and generates a modification. After the updated routing rule, the other routing rules that are not modified in the routing rule and the updated routing rules that modify the at least one routing rule are used as the confirmed routing rules; or
  • the confirmation unit 901 determines that the received rule information, the indication information sent by the UE, the local configuration information, and the current network status match all the routing rules in the routing rule, the routing rule is not modified, and the unmodified routing rule is used as the confirmed routing rule. .
  • the determining unit 901 modifies the routing access technology included in the at least one routing rule, and when the at least one routing rule includes the negotiation indication, The negotiation indication included in the at least one routing rule is set to the forbidden negotiation identifier.
  • the route access technology indication included in the at least one routing rule is set to a forbidden value.
  • the processing unit 902 is specifically configured to: the processing unit 902: the advertised routing rule is carried in the non-access stratum NAS message and transmitted to the mobility management entity MME, so that the MME receives After the acknowledgment of the routing rule, the advertised routing rule is carried in the bearer update response or the bearer new response to be transmitted to the first device; or
  • the processing unit 902 carries the confirmed routing rule in the specified WLAN control plane protocol WLCP message and transmits it to the trusted access gateway TWAG, so that the TWAG receives the confirmed route. After the rule, the confirmed routing rule is carried in the bearer update response or the bearer new response to be transmitted to the first device; or
  • the processing unit 902 carries the confirmed routing rule in the network key agreement protocol IKEv2 message to the untrusted access gateway ePDG, so that the ePDG carries the confirmed routing rule and carries the confirmed routing rule on the bearer.
  • the update response or the bearer new response is transmitted to the first device.
  • the processing unit 902 when the advertised routing rule is carried in the NAS message and transmitted to the MME, is specifically used to:
  • the processing unit 902 adds the confirmed routing rule as a new parameter to the NAS message and transmits it to the MME; or
  • the processing unit 902 adds the confirmed routing rule to the protocol configuration option PCO in the NAS message and transmits it to the MME.
  • the processing unit 902 is configured to: when the MME, the TWAG, or the ePDG carries the confirmed routing rule in the bearer update response or the bearer new response to be transmitted to the first device, specifically:
  • the processing unit 902 causes the MME, TWAG, or ePDG to add the confirmed routing rule as a new parameter to the bearer update response or the bearer new response to be transmitted to the first device; or
  • the processing unit 902 causes the MME, TWAG, or ePDG to add the confirmed routing rule to the bearer context in the bearer update response or the bearer new response to transmit to the first device; or
  • the processing unit 902 causes the MME, TWAG, or ePDG to add the confirmed routing rule to the PCO in the bearer update response or the new response to transmit to the first device.
  • processing unit 902 is further configured to:
  • the sending offloading policy negotiation device is based on the bearer update process generated by the confirmed offloading policy or the determination result of the newly created modification process.
  • the processing unit 902 is specifically configured to: when the confirmed traffic distribution policy includes the confirmed routing rule, the processing unit 902 carries the confirmed traffic distribution policy on the bearer
  • the update request or the bearer new request is transmitted to the MME; after the MME receives the acknowledgment of the offloading policy, the advertised shunting policy is carried in the NAS message and transmitted to the first device; or, the processing unit 902 performs the shunt after the acknowledgment.
  • Strategy carried in packet data The protocol PDP context modification request or the PDP context new request is sent to the first device; or when the confirmed offload policy is the confirmed default access indication, the processing unit 902 carries the confirmed default access indication to the session.
  • the new response is sent to the MME, so that the MME receives the acknowledgment default access indication, and then sends the confirmed default access indication to the first device in the NAS message; or, after the processing unit 902 confirms
  • the default access indication is carried in the session new response and sent to the trusted access gateway TWAG, so that after receiving the confirmed default access indication, the TWAG carries the confirmed default access indication to the WLAN control.
  • the WLCP packet data network PDN connection response is sent to the first device; or the processing unit 902 carries the confirmed default access indication in the session new response to the untrusted access gateway ePDG, so that the ePDG receives
  • the acknowledgment default access indication is carried in the network key agreement protocol IKEv2 message and sent to the first device.
  • the processing unit 902 when the confirmed offloading policy includes the confirmed routing rule, the processing unit 902 enables the MME to carry the confirmed offloading policy in the NAS message to the first device, where specifically, the processing unit 902 causes the MME to The confirmed offloading policy is added as a new parameter to the NAS message and transmitted to the first device; or
  • the processing unit 902 causes the MME to add the confirmed offload policy to the PCO in the NAS message and transmit it to the first device.
  • the processing unit 902 when the confirmed offloading policy is the default access indication after the acknowledgment, the processing unit 902, when the acknowledgment default access indication is carried in the session new response, is specifically used to:
  • the processing unit 902 adds the confirmed default access indication to the PCO in the session new response to send;
  • the processing unit 902 When the spoofing policy is the default access indication after the acknowledgment, the processing unit 902 enables the MME to carry the acknowledgment default access indication in the NAS message, specifically for:
  • the processing unit 902 causes the MME to add the confirmed default access indication to the PCO in the NAS message for sending;
  • the processing unit 902 causes the TWAG to carry the acknowledgment default access indication in the WLCP PDN connection response, specifically for: The processing unit 902 causes the TWAG to add the confirmed default access indication to the PCO in the WLCP PDN connection response for transmission;
  • the processing unit 902 When the spoofed spoofing policy is the default access indication after the acknowledgment, the processing unit 902 enables the ePDG to carry the acknowledgment default access indication in the IKEv2 message, specifically for:
  • Processing unit 902 causes the ePDG to add the acknowledgment default access indication as a new parameter to the IKEv2 message for transmission.
  • an embodiment of the present invention further provides a traffic distribution policy negotiation device, where the device includes: a transceiver 1001, a memory 1002, and a processor 1003, where the transceiver 1001 is configured to perform offloading.
  • the policy is sent to the second device, where the offloading policy includes at least one of the following: a default access indication and at least one routing rule; receiving the confirmed offloading policy returned by the second device for the offloading policy;
  • the storage unit 1002 is configured to store a confirmed offloading policy returned by the second device for the offloading policy; and store the program.
  • the processor 1003 is configured to perform data stream transmission according to the acknowledged offload policy returned by the second device in the memory 1002 for the offload policy, and execute the program stored in the memory 1002.
  • the offloading policy negotiation device is a core network device or a user equipment UE.
  • the processor 1003 is configured to generate a offloading policy before the transceiver 1001 sends the offloading policy to the second device, where the processor 1003 is specifically configured to:
  • the generating unit 800 When the traffic distribution policy negotiation device is the core network device, the generating unit 800 generates at least one routing rule as a traffic distribution policy according to at least one of the received rule information, the indication information sent by the UE, the local configuration information, and the current network state; or
  • the generating unit 800 When the offloading policy negotiation device is the UE, the generating unit 800 generates at least one of the at least one routing rule and the default access indication according to at least one of its own configuration information and the current network state, as the trafficking policy.
  • the routing rule includes: a route access technology, a flow description information, a negotiation indication, and a first routing rule identifier information, where the first routing rule identifier information is at least one of a rule name and a rule priority; or
  • the routing rule includes: a route access technology, a flow description information, a route access technology indication, and a second routing rule identifier information, where the second routing rule identifier information is at least one of a rule name and a rule priority.
  • the negotiation indication is used to identify the modification permission of the UE to the routing rule, and the value is the permission negotiation identifier or the prohibition.
  • the negotiation identifier when the negotiation indication value is the permission negotiation identifier, indicates that the UE selects the route access technology or other access technology in the routing rule; when the negotiation indication value is the forbidden negotiation identifier, the UE selects the routing rule. Or routing access technology; or, when the routing rule includes: a route access technology, a flow description information, a route access technology indication, and a second routing rule identifier information, the route access technology indication is used to identify a route in the route rule.
  • the access permission of the access technology is a forbidden value or an allowable value.
  • the route access technology indicates that the value is a forbidden value, the route access technology in the routing rule is forbidden; or when the route access technology indicates When the value is allowed, it indicates that the route access technology in the routing rule is allowed.
  • the routing rule to which the negotiation indication belongs is a routing rule that prohibits negotiation
  • the route access technology indicates that the value is a forbidden value, it indicates that the route access technology indicates that the route rule belongs to the route rule that prohibits negotiation.
  • the routing access technology indicates that the rule priority of the routing rule corresponding to the forbidden value is higher than the rule priority of the routing rule indicated by the routing access technology as the allowed value.
  • the negotiation indication in the routing rule is empty
  • the route access technology indication contained in the routing rule is equal to the allowed value.
  • the transceiver 1001 is specifically configured to: the transceiver 1001 carries the routing rule in the bearer update request or the bearer new request to be transmitted to the mobility management entity MME, so that the MME receives After the routing rule is sent, the routing rule is carried in the non-access stratum NAS message and transmitted to the second device; or
  • the transceiver 1001 carries the routing rule in the bearer update request or the bearer new request to be transmitted to the The access gateway TWAG, after the TWAG receives the routing rule, carries the routing rule in the specified WLAN control plane protocol WLCP message to the second device; or
  • the transceiver 1001 carries the routing rule in the bearer update request or the bearer new request to the untrusted access gateway ePDG, so that after receiving the routing rule, the ePDG carries the routing rule in the network key agreement protocol IKEv2 message to Second device; or
  • the transceiver 1001 sends the routing rule to the second device in the packet data protocol PDP context modification request or the PDP new request.
  • the transceiver 1001 when the transceiver 1001 carries the routing rule in the bearer update request or the bearer new request, the transceiver 1001 is specifically configured to:
  • the transceiver 1001 adds the routing rule as a new parameter to the bearer update request or the bearer new request for transmission; or
  • the transceiver 1001 adds the routing rule to the bearer update request or the bearer in the bearer new request for transmission; or
  • the transceiver 1001 adds the routing rule to the bearer update request or the protocol configuration option PCO in the bearer new request.
  • the transceiver 1001 enables the MME to carry the routing rule in the non-access stratum NAS message, specifically for:
  • the transceiver 1001 causes the MME to add a routing rule as a new parameter to the NAS message for transmission; or
  • Transceiver 1001 causes the MME to add routing rules to the PCO in the NAS message for transmission.
  • the transceiver 1001 is specifically configured to: when the offloading policy includes the routing rule, the transceiver 1001 sends the offloading policy to the MME in the NAS message, so that the MME receives the offloading After the policy, the offloading policy is carried in the bearer resource command to send the second device; or
  • the transceiver 1001 When the offloading policy is the default access indication, the transceiver 1001 carries the default access indication in the NAS message and sends it to the MME, so that after receiving the default access indication, the MME carries the default access indication in the session.
  • the new request is sent to the second device; or, the transceiver 1001 carries the default access indication
  • the TWAG After being sent to the TWAG in the WLCP packet data network PDN connection request, after the TWAG receives the default access indication, the TWAG is carried in the session new request and sent to the second device; or, the transceiver 1001
  • the default access indication is carried in the network key agreement protocol IKEv2 message and sent to the non-trusted access gateway ePDG, so that after receiving the default access indication, the ePDG carries the default access indication in the session new request.
  • IKEv2 network key agreement protocol
  • the transceiver 1001 carries the offloading policy to
  • the transceiver 1001 adds the offload policy as a new parameter to the NAS message for transmission; or the transceiver 1001 adds the offload policy to the PCO in the NAS message for transmission.
  • the transceiver 1001 when the offloading policy is the default access indication, when the transceiver 1001 sends the default access indication to the NAS message or the WLCP PDN connection request, the transceiver 1001 is specifically configured to:
  • the transceiver 1001 adds a default access indication to the PCO in the NAS message or the WLCP PDN connection request; or
  • the transceiver 1001 When the offloading policy is the default access indication, the transceiver 1001 enables the MME or the TWAG to carry the default access indication when it is sent in the session new request, specifically for:
  • the transceiver 1001 causes the MME or TWAG to add a default access indication to the session new request.
  • the transceiver 1001 When the offloading policy is the default access indication, the transceiver 1001 carries the default access indication.
  • Transceiver 1001 adds the default access indication as a new parameter to the IKEv2 message for transmission.
  • the transceiver 1001 is specifically configured to: if the second device routes at least one of the received routing rules according to at least one of the configuration information and the current network state After the rule is modified, the transceiver 1001 receives other routing rules that are not modified in the routing rule sent by the second device, and updated routing rules that modify the at least one routing rule; or
  • the transceiver 1001 receives the unmodified routing rule.
  • the negotiation indication included in the at least one routing rule modified by the second device is to allow the negotiation identifier; or
  • the route access technology indication included in the at least one routing rule modified by the second device is equal to the allowed value.
  • the transceiver 1001 is further configured to:
  • the transceiver 1001 is specifically configured to: the transceiver 1001 receive at least one of the confirmed routing rule returned by the second device and the confirmed default access indication;
  • the transceiver 1001 when receiving the default access indication after the confirmation returned by the second device, is specifically used to:
  • the transceiver 1001 receives the modification returned by the second device.
  • Default access indication or
  • the transceiver 1001 receives the unmodified default access indication returned by the second device;
  • the transceiver 1001 When receiving the queried routing rule returned by the second device, the transceiver 1001 is specifically configured to: if the second device according to the received rule information, the indication information sent by the UE, the local configuration information, and the current network state The at least one routing rule in the received routing rule is modified, and the transceiver 1001 receives other routing rules that are not modified in the routing rule sent by the second device, and the updated routing rule that is modified after modifying at least one routing rule; or
  • the transceiver 1001 receives the unmodified routing rule.
  • the negotiation indication included in the updated routing rule modified by the at least one routing rule is a forbidden negotiation identifier
  • Route access technology included in the updated routing rule modified by at least one routing rule The instruction is a prohibited value.
  • the embodiment of the present invention further provides a traffic distribution policy negotiation device, where the device includes: a transceiver 1101, a memory 1002, and a process 1003, where the transceiver 1101 is configured to receive the first The offloading policy is sent by the device, and the spoofed traffic policy is returned to the first device, where the traffic distribution policy includes at least one of the following: a default access indication and at least one routing rule;
  • the storage 1102 is configured to store the confirmed offloading policy, and store the program
  • the processor 1103 is configured to confirm the offload policy, and perform data stream transmission based on the confirmed offload policy.
  • the offloading policy negotiation device is a user equipment UE or a core network device.
  • the offloading policy negotiation device is a UE
  • the offloading policy is at least one routing rule sent by the first device
  • the traffic distribution policy is at least one of at least one routing rule and a default access indication sent by the first device.
  • the routing rule sent by the first device includes: a route access technology, a flow description information, a negotiation indication, and a first routing rule identifier information, where the first routing rule identifier information is in a rule name and a rule priority. At least one item; or
  • the routing rule sent by the first device includes: a route access technology, a flow description information, a route access technology indication, and a second routing rule identifier information, where the second routing rule identifier information is at least one of a rule name and a rule priority.
  • the negotiation indication is used to identify the modification permission of the UE to the routing rule, and the value is the permission negotiation identifier or the prohibition.
  • the negotiation identifier when the negotiation indication value is the permission negotiation identifier, indicates that the UE selects the route access technology or other access technology in the routing rule; when the negotiation indication value is the forbidden negotiation identifier, the UE selects the routing rule. Or routing access technology; or, when the routing rule includes: a route access technology, a flow description information, a route access technology indication, and a second routing rule identifier information, the route access technology indication is used to identify a route in the route rule.
  • the access permission of the access technology is a forbidden value or an allowable value.
  • the route access technology indicates that the value is a forbidden value, the route access technology in the routing rule is forbidden; or when the route access technology indicates When the value is allowed, it indicates that the route access technology in the routing rule is allowed.
  • the routing rule to which the negotiation indication belongs is a routing rule that prohibits negotiation
  • the route access technology indicates that the value is a forbidden value, it indicates that the route access technology indicates that the route rule belongs to the route rule that prohibits negotiation.
  • the routing access technology indicates that the rule priority of the routing rule corresponding to the forbidden value is higher than the rule priority of the routing rule indicated by the routing access technology as the allowed value.
  • the negotiation indication in the routing rule sent by the first device is blank;
  • the route access technology indication in the routing rule sent by the first device is equal to the allowed value.
  • the processor 1103 is configured to:
  • the processor 1103 confirms the routing rule, it is specifically used to:
  • the processor 1103 determines that at least one of the configuration information and the current network state does not match at least one routing rule in the routing rule, and at least one routing rule is not a routing rule that prohibits negotiation, and at least one routing rule is modified, and Generating the modified updated routing rule, and using the other routing rules that are not modified in the routing rule and the updated routing rules that modify the at least one routing rule as the confirmed routing rule; or
  • the processor 1103 determines that at least one of its own configuration information and the current network state matches all routing rules in the routing rule, or at least one of its own configuration information and the current network state does not match the routing rule in the routing rule.
  • the negotiated routing rule is forbidden, the routing rule is not modified, and the unmodified routing rule is used as the confirmed routing rule.
  • the processor 1103 is configured to: confirm the default access indication in the traffic off policy, and/or confirm the routing rule in the traffic off policy;
  • the processor 1103 is configured to: determine, by the processor 1103, at least one of the received rule information, the indication information sent by the UE, the local configuration information, and the current network state, and the default
  • the processor 1103 is configured to: determine, by the processor 1103, at least one of the received rule information, the indication information sent by the UE, the local configuration information, and the current network state, and the default
  • the default access indication is modified, and the modified default access indication is used as the default access indication after confirmation; or
  • the processor 1103 determines that the received rule information, the indication information sent by the UE, the local configuration information, and the current network status match the default access indication, the default access indication is not modified, and the unmodified default access indication is used as the default access indication.
  • the default access indication after confirmation;
  • the processor 1103 confirms the routing rule, it is specifically used to:
  • the processor 1103 determines, when the at least one item of the received rule information, the indication information sent by the UE, the local configuration information, and the current network status does not match the at least one routing rule in the routing rule, the at least one routing rule is modified, and the modification is generated. After the updated routing rule, the other routing rules that are not modified in the routing rule and the updated routing rules that modify the at least one routing rule are used as the confirmed routing rules; or
  • the processor 1103 determines that the received rule information, the indication information sent by the UE, the local configuration information, and the current network status match all the routing rules in the routing rule, the routing rule is not modified, and the unmodified routing rule is used as the confirmed routing rule. .
  • the processor 1103 when the processor 1103 is configured to modify the at least one routing rule, the processor 1103 is configured to modify the routing access technology included in the at least one routing rule, and when the at least one routing rule includes the negotiation indication, The negotiation indication included in the at least one routing rule is set to the forbidden negotiation identifier. When the at least one routing rule includes the route access technology indication, the route access technology indication included in the at least one routing rule is set to a forbidden value.
  • the transceiver 1101 when the offloading policy negotiation device is the UE, the transceiver 1101 is specifically configured to: the transceiver 1101 carries the confirmed routing rule in the non-access stratum NAS message and transmits the traversal rule to the mobility management entity MME, so that the MME receives the MME. After the acknowledgment of the routing rule, the advertised routing rule is carried in the bearer update response or the bearer new response to be transmitted to the first device; or
  • the transceiver 1101 carries the confirmed routing rule in the specified WLAN control plane protocol WLCP message and transmits it to the trusted access gateway TWAG, so that the TWAG receives the confirmed route. After the rule, the confirmed routing rule is carried in the bearer update response or the bearer new response to be transmitted to the first device; or
  • the transceiver 1101 carries the confirmed routing rule in the network key agreement protocol IKEv2 message to the untrusted access gateway ePDG, so that the ePDG carries the confirmed routing rule and carries the confirmed routing rule on the bearer.
  • the update response or the bearer new response is transmitted to the first device.
  • the transceiver 1101 when the advertised routing rule is carried in the NAS message and transmitted to the MME, is specifically used to:
  • the transceiver 1101 adds the confirmed routing rule as a new parameter to the NAS message and transmits it to the MME; or
  • the transceiver 1101 adds the confirmed routing rule to the protocol configuration option PCO in the NAS message and transmits it to the MME.
  • the transceiver 1101 is configured to: when the MME, the TWAG, or the ePDG carries the confirmed routing rule in the bearer update response or the bearer new response to be transmitted to the first device, specifically:
  • the transceiver 1101 causes the MME, TWAG or ePDG to add the confirmed routing rule as a new parameter to the bearer update response or the bearer new response to be transmitted to the first device; or
  • the transceiver 1101 causes the MME, TWAG or ePDG to add the confirmed routing rule to the bearer context in the bearer update response or the bearer new response to transmit to the first device; or
  • the transceiver 1101 causes the MME, TWAG or ePDG to add the confirmed routing rule to the PCO in the bearer update response or the 7-load new response to transmit to the first device.
  • the transceiver 1101 is further configured to:
  • the sending offloading policy negotiation device is based on the bearer update process generated by the confirmed offloading policy or the determination result of the newly created modification process.
  • the transceiver 1101 when the offloading policy negotiation device is a core network device, the transceiver 1101 is specifically configured to: when the confirmed offloading policy includes the confirmed routing rule, the transceiver 1101 carries the confirmed offloading policy on the bearer. The MME is transmitted to the MME in the update request or the bearer new request. After the MME receives the acknowledgment of the offloading policy, the IPSec policy is carried in the NAS message and transmitted to the first device. Alternatively, the transceiver 1101 will perform the shunt after the acknowledgment.
  • the PDP context modification request or the PDP context new request is sent to the first device; or when the confirmed offload policy is the confirmed default access indication, the transceiver 1101 carries the confirmed default access indication in the session.
  • the new response is sent to the MME, so that the MME receives the acknowledgment default access indication, and then sends the confirmed default access indication to the first device in the NAS message; or, after the transceiver 1101 confirms
  • the default access indication is carried in the session new response and sent to the trusted access gateway TWAG, so that after receiving the confirmed default access indication, the TWAG carries the confirmed default access indication to the WLAN control.
  • the WLCP packet data network PDN connection response is sent to the first device; or the transceiver 1101 carries the confirmed default access indication in the session new response to the untrusted access gateway ePDG, so that the ePDG receives After the acknowledgment default access indication, the acknowledgment default access indication is carried in the network key agreement protocol IKEv2 message and sent to the first device.
  • the transceiver 1101 when the acknowledged offloading policy includes the confirmed routing rule, the transceiver 1101 enables the MME to carry the confirmed offloading policy in the NAS message to the first device, where specifically, the transceiver 1101 causes the MME to The confirmed offloading policy is added as a new parameter to the NAS message and transmitted to the first device; or
  • the transceiver 1101 causes the MME to add the confirmed offload policy to the PCO in the NAS message and transmit it to the first device.
  • the transceiver 1101 when the confirmed offloading policy is the default access indication after the acknowledgment, the transceiver 1101, when the acknowledgment default access indication is carried in the session new response, is specifically used to:
  • the transceiver 1101 adds the confirmed default access indication to the PCO in the session new response to send;
  • the transceiver 1101 When the spoofing policy is the default access indication after the acknowledgment, the transceiver 1101 enables the MME to carry the acknowledgment default access indication in the NAS message, specifically for:
  • the transceiver 1101 causes the MME to add the confirmed default access indication to the PCO in the NAS message for sending;
  • the transceiver 1101 When the confirmed offloading policy is the default access indication after the acknowledgment, the transceiver 1101 causes the TWAG to carry the acknowledgment default access indication in the WLCP PDN connection response, specifically for: The transceiver 1101 causes the TWAG to add the confirmed default access indication to the PCO in the WLCP PDN connection response for transmission;
  • the transceiver 1101 When the spoofed spoofing policy is the default access indication after the acknowledgment, the transceiver 1101 enables the ePDG to carry the acknowledgment default access indication in the IKEv2 message, specifically for:
  • the transceiver 1101 causes the ePDG to add the acknowledgment default access indication as a new parameter to the IKEv2 message for transmission.
  • a method and a device for negotiating a traffic distribution policy are as follows:
  • the first device sends a traffic distribution policy to a second device, where the traffic distribution policy includes a default access indication and a routing rule;
  • the first device receives and stores the confirmed offloading policy returned by the second device for the offloading policy, and performs data stream transmission based on the confirmed offloading policy.
  • a routing rule that is acceptable on both sides can be obtained through negotiation between the network side and the UE, which improves the data stream transmission efficiency and solves the data flow switching initiated by the UE in the prior art.
  • the applicability of the method is low, and the network side cannot control and manage the UE, which reduces the user experience.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can be embodied in the form of one or more computer program products embodied on a computer-usable storage medium (including but not limited to disk storage, CD-ROM, optical storage, etc.) in which computer usable program code is embodied.
  • a computer-usable storage medium including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Communication Control (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

本发明提供了一种分流策略协商方法及装置,用以解决现有技术中UE发起的数据流切换的方法适用性较低,且网络侧无法对UE进行控制管理,降低用户体验的问题,该方法为:第一设备发送分流策略至第二设备,其中,该分流策略中包括缺省接入指示和路由规则;第一设备接收并存储第二设备针对该分流策略返回的确认后的分流策略,基于该确认后的分流策略进行数据流传输。这样,在更新数据流分流策略时,可以通过网络侧和UE的协商,获取一个两侧都可以接受的路由规则,提高了数据流传输效率,解决了现有技术中UE发起的数据流切换的方法适用性较低,且网络侧无法对UE进行控制管理,降低用户体验的问题。

Description

一种分流策略协商方法及装置
技术领域
本发明涉及通信领域, 尤其涉及一种分流策略协商方法及装置。 背景技术
在第三代伙伴计划 ( The 3th Generation partnership Project, 3GPP ) 网络 的核心网中, 主要包含移动管理实体(Mobility Management Entity, MME )、 服务网关( Serving Gateway S-GW )以及分组数据网网关( Packet Data Network Gateway, P-GW )三个逻辑功能体。 MME是移动管理网元, 负责与用户设备
( User Equipment, UE )之间的非接入层( Non Access Stratum, NAS )信令 和 NAS信令加密, 为 UE分配临时身份标识, 选择 S-GW和 P-GW等核心网 网元, 以及提供漫游、 跟踪、 安全等功能; S-GW是本地基站 eNodeB之间切 换的移动性锚点, 提供合法监听等相关功能; P-GW负责用户地址分配、 策略 控制、 计费规则的执行, 以及合法监听等相关功能; 归属签约用户服务器
( Home Subscriber Server, HSS )用于存储用户的签约信息; 策略与计费规则 功能( Policy and Charging Rules Function ) PCRF用于提供策略和计费控制规 则。
当非 3GPP网络接入 3GPP网络的核心网时, 非 3GPP网络可以通过 S2a 接口与 3GPP网络中的 P-GW建立连接, 从而接入 3GPP网络, 或者, 基于 UE通过 S2c接口与 3GPP网络中的 P-GW建立连接。
目前, 3GPP标准协议支持 UE同时接入一个 3GPP网络和一个非 3GPP 网络,并且,进一步地, UE可以基于同一个分组数据网( Packet Data Network, PDN )连接同时接入该 3GPP网络和非 3GPP网络, 即同一个 PDN连接中的 不同数据流可以分布在一个 3GPP网络和一个非 3GPP网络中,以达到有效分 流, 网络资源合理利用的目的。
当新业务建立时, UE可以根据静态配置的策略、 动态接收的策略或者用 户偏好等选择网络。 现有技术给出了当前基于双栈移动 IPv6 ( Dual Stack Mobile IPv6, DSMIPv6 ) 的 UE和网络侧之间路由信息的同步以及数据流移 动过程。 例如, 当前 3GPP标准协议中 DSMIPv6的多接入场景下, UE发起 的数据流切换的过程:
1. UE同时接入了一个 3GPP网络和一个非 3GPP网络, 并在这两个网络 中同时使用一个 PDN连接;
2. UE向网络侧发送绑定更新消息 Binding Update, 请求更新路由规则;
3. 网络侧提供新的路由规则, 并存储更新的路由地址和接入网络之间的 映射关系, 最后发送绑定确认消息 Binding Acknowledgement给 UE, 指示哪 些更新的路由规贝 'J被接受;
4. UE和网络侧基于被接受的更新的路由规则进行数据流切换, 例如, 对 于那些切换到非 3GPP系统的数据流, 3GPP网络会发起资源释放过程。
目前 3GPP所使用的移动性协议有: 通用分组无线业务通道协议( GPRS Tunneling Protocol, GTP )、 代理移动 IPv6 ( Proxy Mobile IPv6 , ΡΜΙΡνό ) 以 及 DSMIPv6, 然而, 目前标准中只有 DSMIP协议适用于数据流移动的场景, 因此, 传统的方法 UE发起的数据流切换适用性较低, 并且由于该方法是由 UE控制的, 而网络侧的网关无法检测 UE是否按照网络侧指定的策略执行, 因此, 造成网络侧无法对 UE进行控制管理, 降低用户体验。 发明内容
本发明实施例提供了一种分流策略协商方法及装置, 用以解决现有技术 中 UE发起的数据流切换的方法适用性较低,且网络侧无法对 UE进行控制管 理, 降低用户体验的问题。
第一方面, 一种分流策略协商方法, 包括:
第一设备将分流策略发送至第二设备, 其中, 所述分流策略包括以下至 少一项: 缺省接入指示和至少一条路由规则;
所述第一设备接收并存储所述第二设备针对所述分流策略返回的确认后 的分流策略, 基于所述确认后的分流策略进行数据流传输。
结合第一方面, 在第一种可能的实现方式中, 所述第一设备为核心网设 备或者用户设备 UE。
结合第一方面的第一种可能的实现方式, 在第二种可能的实现方式中, 所述第一设备将分流策略发送至第二设备之前, 还包括:
所述第一设备生成分流策略, 具体包括:
当所述第一设备为核心网设备时, 所述第一设备根据接收的规则信息、 UE发送的指示信息、本地配置信息以及当前网络状态中的至少一项生成至少 一条路由规则作为分流策略; 或者
当所述第一设备为 UE时,所述第一设备根据自身的配置信息以及当前网 络状态中的至少一项生成至少一条路由规则和缺省接入指示中的至少一项, 作为分流策略。
结合第一方面的第二种可能的实现方式, 在第三种可能的实现方式中, 所述路由规则包括: 路由接入技术、 流描述信息、 协商指示以及第一路由规 则标识信息, 其中, 所述第一路由规则标识信息为规则名称、 规则优先级中 的至少一项; 或者
所述路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示以 及第二路由规则标识信息, 其中, 所述第二路由规则标识信息为规则名称以 及规则优先级中的至少一项。
结合第一方面的第三种可能的实现方式, 在第四种可能的实现方式中, 当所述路由规则包括: 路由接入技术、 流描述信息、 协商指示以及第一路由 规则标识信息时, 所述协商指示用来标识 UE对路由规则的修改权限,取值为 允许协商标识或者禁止协商标识, 当协商指示取值为允许协商标识时, 表示 UE选择该路由规则中的路由接入技术或者其它接入技术; 当协商指示取值为 禁止协商标识时, 表示 UE选择该路由规则中的路由接入技术; 或者,
当所述路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示 以及第二路由规则标识信息时, 所述路由接入技术指示用来标识对路由规则 中的路由接入技术的使用权限, 取值为禁止值或者允许值, 当路由接入技术 指示取值为禁止值时, 表示禁止使用路由规则中的路由接入技术; 或者, 当 路由接入技术指示取值为允许值时, 表示允许使用路由规则中的路由接入技 术。
结合第一方面的第四种可能的实现方式, 在第五种可能的实现方式中, 当协商指示取值为禁止协商标识时, 表示协商指示所属的路由规则为禁止协 商的路由规则; 或者,
当路由接入技术指示取值为禁止值时, 表示路由接入技术指示所属的路 由规则为禁止协商的路由规则。
结合第一方面的第四种或第五种可能的实现方式, 在第六种可能的实现 方式中, 路由接入技术指示为禁止值对应的路由规则的规则优先级高于路由 接入技术指示为允许值对应的路由规则的规则优先级。
结合第一方面的第四种可能的实现方式, 在第七种可能的实现方式中, 当所述第一设备为 UE时, 所述路由规则中的协商指示为空; 或者
所述路由规则中包含的路由接入技术指示等于允许值。
结合第一方面的第二至第七中的任一种可能的实现方式, 在第八种可能 的实现方式中, 当所述第一设备为核心网设备时, 所述第一设备将所述分流 策略发送至第二设备, 包括:
所述第一设备将所述路由规则携带于承载更新请求或承载新建请求中传 输至移动管理实体 MME, 以使 MME接收到所述路由规则后, 将所述路由规 则携带于非接入层 NAS消息中传输至所述第二设备; 或者
所述第一设备将所述路由规则携带于承载更新请求或承载新建请求中传 输至可信接入网关 TWAG, 以使所述 TWAG接收到所述路由规则后, 将所述 路由规则携带于指定的无线局域网控制面协议 WLCP消息中传输至所述第二 设备; 或者
所述第一设备将所述路由规则携带于承载更新请求或承载新建请求中传 输至非可信接入网关 ePDG, 以使所述 ePDG接收到所述路由规则后, 将所述 路由规则携带于网络密钥协商协议 IKEv2消息中传输至所述第二设备; 或者 所述第一设备将所述路由规则携带于分组数据协议 PDP上下文修改请求 或者 PDP新建请求中发送至所述第二设备。
结合第一方面的第八种可能的实现方式, 在第九种可能的实现方式中, 所述第一设备将所述路由规则携带于承载更新请求或承载新建请求中传输, 包括:
所述第一设备将所述路由规则作为新的参数添加至所述承载更新请求或 承载新建请求中传输; 或者
所述第一设备将所述路由规则添加至所述承载更新请求或承载新建请求 中的承载上下文中传输; 或者
所述第一设备将所述路由规则添加至所述承载更新请求或承载新建请求 中的协议配置选项 PCO中传输。
结合第一方面的第八种可能的实现方式, 在第十种可能的实现方式中, 所述第一设备使所述 MME将所述路由规则携带于非接入层 NAS消息中传输, 包括:
所述第一设备使所述 MME将所述路由规则作为新的参数添加至所述 NAS消息中传输; 或者
所述第一设备使所述 MME将所述路由规则添加至所述 NAS 消息中的 PCO中传输。
结合第一方面中的第二至第七中的任一种可能的实现方式, 在第十一种 可能的实现方式中, 当所述第一设备为 UE时, 所述第一设备将所述分流策略 发送至第二设备, 包括:
当所述分流策略包括所述路由规则时, 所述第一设备将所述分流策略携 带于 NAS消息中发送至 MME, 以使所述 MME接收到所述分流策略后, 将 所述分流策略携带于承载资源命令中发送所述第二设备; 或者
当所述分流策略为缺省接入指示时, 所述第一设备将所述缺省接入指示 携带于 NAS消息中发送至 MME, 以使所述 MME接收到所述缺省接入指示 后, 将所述缺省接入指示携带于会话新建请求中发送至第二设备; 或者, 所 述第一设备将所述缺省接入指示携带于 WLCP分组数据网 PDN连接请求中发 送至 TWAG, 以使所述 TWAG接收到所述缺省接入指示后, 将所述缺省接入 指示携带于会话新建请求中发送至第二设备; 或者, 所述第一设备将所述缺 省接入指示携带于网络密钥协商协议 IKEv2 消息中发送至非可信接入网关 ePDG, 以使所述 ePDG接收到所述缺省接入指示后, 将所述缺省接入指示携 带于会话新建请求中发送至第二设备。
结合第一方面的第十一种可能的实现方式, 在第十二种可能的实现方式 中, 当所述分流策略包括所述路由规则时, 所述第一设备将所述分流策略携 带于 NAS消息中发送, 包括:
所述第一设备将所述分流策略作为新的参数添加至所述 NAS 消息中发 送; 或者
所述第一设备将所述分流策略添加至所述 NAS消息中的 PCO中发送。 结合第一方面的第十一种可能的实现方式, 在第十三种可能的实现方式 中, 当所述分流策略为缺省接入指示时, 所述第一设备在将所述缺省接入指 示携带于 NAS消息或者所述 WLCP PDN连接请求中发送, 包括:
所述第一设备将所述缺省接入指示添加至所述 NAS消息或者所述 WLCP PDN连接请求中的 PCO中发送; 或者
当所述分流策略为缺省接入指示时, 所述第一设备使所述 MME或所述 TWAG将所述缺省接入指示携带于所述会话新建请求中发送时, 具体用于: 所述第一设备使所述 MME或所述 TWAG将所述缺省接入指示添加至所 述会话新建请求中的 PCO中发送; 或者
当所述分流策略为缺省接入指示时, 所述第一设备将所述缺省接入指示 携带于所述 IKEv2消息中发送时, 具体用于:
所述第一设备将所述缺省接入指示作为新的参数添加至所述 IKEv2消息 中发送。
结合第一方面的第四至第六中的任一种可能的实现方式, 在第十四种可 能的实现方式中, 当所述第一设备为核心网设备时, 所述第一设备接收所述 第二设备针对所述分流策略返回的确认后的分流策略, 包括:
若所述第二设备根据自身的配置信息以及当前网络状态中的至少一项对 接收的路由规则中至少一条路由规则进行修改, 则所述第一设备接收所述第 二设备发送的所述路由规则中未修改的其它路由规则以及对所述至少一条路 由规则进行修改后的更新的路由规则; 或者
若所述第二设备未对接收的所述路由规则进行修改, 则所述第一设备接 收未修改的所述路由规则。
结合第一方面的第十四种可能的实现方式, 在第十五种可能的实现方式 中, 所述第二设备修改的所述至少一条路由规则中包含的协商指示为允许协 商标识; 或者
所述第二设备修改的所述至少一条路由规则中包含的路由接入技术指示 等于允许值。
结合第一方面的第十四种可能的实现方式, 在第十六种可能的实现方式 中, 所述第一设备接收所述第二设备针对所述分流策略返回的所述确认后的 分流策略, 还包括:
接收所述第二设备基于所述确认后的分流策略产生的承载更新流程或承 载新建修改流程的确定结果。
结合第一方面的第四至第六中的任一种可能的实现方式, 在第十七种可 能的实现方式中, 当所述第一设备为 UE时, 所述第一设备接收所述第二设备 针对所述分流策略返回的所述确认后的分流策略, 包括:
所述第一设备接收所述第二设备返回的确认后的路由规则和确认后的缺 省接入指示中的至少一项;
其中, 所述第一设备接收所述第二设备返回的所述确认后的缺省接入指 示, 包括:
若所述第二设备根据接收的规则信息、 UE发送的指示信息、 本地配置信 息以及当前网络状态中的至少一项对接收的所述缺省接入指示进行修改, 则 所述第一设备接收所述第二设备返回的修改后的缺省接入指示; 或者 若所述第二设备未对所述缺省接入指示进行修改, 则所述第一设备接收 所述第二设备返回的未修改的缺省接入指示;
所述第一设备接收所述第二设备返回的所述确认后的路由规则, 包括: 若所述第二设备根据接收的规则信息、 UE发送的指示信息、 本地配置信 息以及当前网络状态中的至少一项对接收的所述路由规则中至少一条路由规 则进行修改, 则所述第一设备接收所述第二设备发送的所述路由规则中未修 改的其它路由规则以及对所述至少一条路由规则进行修改后的更新的路由规 则; 或者
若所述第二设备未对接收的所述路由规则进行修改, 则所述第一设备接 收的未修改的所述路由规则。
结合第一方面的第十七种可能的实现方式, 在第十八种可能的实现方式 中, 对所述至少一条路由规则进行修改后的更新的路由规则中包含的协商指 示为禁止协商标识; 或者
对所述至少一条路由规则进行修改后的更新的路由规则中包含的路由接 入技术指示为禁止值。
第二方面, 一种分流策略协商方法, 包括:
第二设备接收第一设备发送的分流策略, 并对所述分流策略进行确认, 其中, 所述分流策略包括以下至少一项: 缺省接入指示和至少一条路由规则; 所述第二设备存储确认后的分流策略, 并将所述确认后的分流策略返回 至所述第一设备, 基于所述确认后的分流策略进行数据流传输。
结合第二方面, 在第一种可能的实现方式中, 所述第二设备为用户设备 UE或者核心网设备。
结合第二方面的第一种可能的实现方式, 在第二种可能的实现方式中, 当所述第二设备为 UE时,所述分流策略为所述第一设备发送的至少一条路由 规则; 或者
当所述第二设备为核心网设备时, 所述分流策略为第一设备发送的至少 一条路由规则和缺省接入指示中的至少一项。
结合第二方面的第二种可能的实现方式, 在第三种可能的实现方式中, 所述第一设备发送的所述路由规则中包括: 路由接入技术、 流描述信息、 协 商指示以及第一路由规则标识信息, 其中, 所述第一路由规则标识信息为规 则名称、 规则优先级中的至少一项; 或者
所述第一设备发送的所述路由规则中包括: 路由接入技术、 流描述信息、 路由接入技术指示以及第二路由规则标识信息, 其中, 所述第二路由规则标 识信息为规则名称以及规则优先级中的至少一项。
结合第二方面的第三种可能的实现方式, 在第四种可能的实现方式中, 当所述路由规则包括: 路由接入技术、 流描述信息、 协商指示以及第一路由 规则标识信息时, 所述协商指示用来标识 UE对路由规则的修改权限,取值为 允许协商标识或者禁止协商标识, 当协商指示取值为允许协商标识时, 表示 UE选择该路由规则中的路由接入技术或者其它接入技术; 当协商指示取值为 禁止协商标识时, 表示 UE选择该路由规则中的路由接入技术; 或者,
当所述路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示 以及第二路由规则标识信息时, 所述路由接入技术指示用来标识对路由规则 中的路由接入技术的使用权限, 取值为禁止值或者允许值, 当路由接入技术 指示取值为禁止值时, 表示禁止使用路由规则中的路由接入技术; 或者, 当 路由接入技术指示取值为允许值时, 表示允许使用路由规则中的路由接入技 术。
结合第二方面的第四种可能的实现方式, 在第五种可能的实现方式中, 当协商指示取值为禁止协商标识时, 表示协商指示所属的路由规则为禁止协 商的路由规则; 或者,
当路由接入技术指示取值为禁止值时, 表示路由接入技术指示所属的路 由规则为禁止协商的路由规则。
结合第二方面的第四或第五种可能的实现方式, 在第六种可能的实现方 式中, 路由接入技术指示为禁止值对应的路由规则的规则优先级高于路由接 入技术指示为允许值对应的路由规则的规则优先级。
结合第二方面的第四种可能的实现方式, 在第七种可能的实现方式中, 当所述第一设备为 UE时,所述第一设备发送的所述路由规则中的协商指示为 空; 或者
所述第一设备发送的所述路由规则中的路由接入技术指示等于允许值。 结合第二方面的第五至第七中任一种可能的实现方式, 在第八种可能的 实现方式中, 当所述第二设备为 UE时, 所述第二设备对所述分流策略进行确 认, 包括:
所述第二设备对所述路由规则进行确认, 具体包括:
所述第二设备判定自身的配置信息以及当前网络状态中的至少一项与所 述路由规则中至少一条路由规则不匹配, 且所述至少一条路由规则不是禁止 协商的路由规则时, 对所述至少一条路由规则进行修改, 并生成修改后的更 新的路由规则, 将所述路由规则中未修改的其它路由规则以及对所述至少一 条路由规则进行修改后的更新的路由规则作为确认后的路由规则; 或者
所述第二设备判定自身的配置信息以及当前网络状态中的至少一项与所 述路由规则中所有路由规则匹配, 或者自身的配置信息以及当前网络状态中 的至少一项与所述路由规则中不匹配的路由规则为禁止协商的路由规则时, 不对所述路由规则进行修改, 将未修改的所述路由规则作为确认后的路由规 则。
结合第二方面的第五至第七中任一种可能的实现方式, 在第九种可能的 实现方式中, 当所述第二设备为核心网设备时, 所述第二设备对所述分流策 略进行确认, 包括:
所述第二设备对所述分流策略中的缺省接入指示进行确认, 和 /或, 所述 第二设备对所述分流策略中的路由规则进行确认;
其中, 所述第二设备对所述缺省接入指示进行确认, 包括:
所述第二设备判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态中的至少一项与所述缺省接入指示不匹配时, 对所述缺省 接入指示进行修改, 将修改后的缺省接入指示作为确认后的缺省接入指示; 或者
所述第二设备判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态与所述缺省接入指示匹配时, 不对所述缺省接入指示进行 修改, 将未修改的所述缺省接入指示作为确认后的缺省接入指示;
所述第二设备对所述路由规则进行确认, 包括:
所述第二设备判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态中的至少一项与所述路由规则中至少一条路由规则不匹配 时, 对所述至少一条路由规则进行修改, 并生成修改后的更新的路由规则, 将所述路由规则中未修改的其它路由规则以及对所述至少一条路由规则进行 修改后的更新的路由规则作为确认后的路由规则; 或者
所述第二设备判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态与所述路由规则中所有路由规则匹配时, 不对所述路由规 则进行修改, 将未修改的所述路由规则作为确认后的路由规则。
结合第二方面的第九种可能的实现方式, 在第十种可能的实现方式中, 所述第二设备对所述至少一条路由规则进行修改包括:
所述第二设备对所述至少一条路由规则中包含的路由接入技术进行修 改, 并
在所述至少一条路由规则中包含协商指示时, 将所述至少一条路由规则 中包含的协商指示设置为禁止协商标识; 在所述至少一条路由规则包含路由 接入技术指示时, 将所述至少一条路由规则中包含的路由接入技术指示设置 为禁止值。
结合第二方面的第八种可能的实现方式, 在第十一种可能的实现方式中, 当所述第二设备为 UE时,所述第二设备将所述确认后的分流策略返回至所述 第一设备, 包括:
所述第二设备将所述确认后的路由规则携带于非接入层 NAS消息中传输 至移动管理实体 MME, 以使 MME接收到所述确认后的路由规则后, 将所述 确认后的路由规则携带于承载更新响应或承载新建响应中传输至所述第一设 备; 或者
所述第二设备将所述确认后的路由规则携带于指定的无线局域网控制面 协议 WLCP消息中传输至可信接入网关 TWAG,以使所述 TWAG接收到所述 确认后的路由规则后, 将所述确认后的路由规则携带于承载更新响应或承载 新建响应中传输至所述第一设备; 或者
所述第二设备将所述确认后的路由规则携带于网络密钥协商协议 IKEv2 消息中传输至非可信接入网关 ePDG, 以使所述 ePDG接收到所述确认后的路 由规则后, 将所述确认后的路由规则携带于承载更新响应或承载新建响应中 传输至所述第一设备。
结合第二方面的第十一种可能的实现方式, 在第十二种可能的实现方式 中,所述第二设备将所述确认后的路由规则携带于 NAS消息中传输至 MME, 包括:
所述第二设备将所述确认后的路由规则作为新的参数添加至所述 NAS消 息中传输至 MME; 或者
所述第二设备将所述确认后的路由规则添加至所述 NAS消息中的协议配 置选项 PCO中传输至 MME。
结合第二方面的第十一种可能的实现方式, 在第十三种可能的实现方式 中, 将所述确认后的路由规则携带于承载更新响应或承载新建响应中传输至 所述第一设备, 包括:
将所述确认后的路由规则作为新的参数添加至所述承载更新响应或承载 新建响应中传输至所述第一设备; 或者
将所述确认后的路由规则添加至所述承载更新响应或承载新建响应中的 承载上下文中传输至所述第一设备; 或者
将所述确认后的路由规则添加至所述承载更新响应或承载新建响应中的 PCO中传输至所述第一设备。
结合第二方面的第十一至第十三中任一种种可能的实现方式, 在第十四 种可能的实现方式中, 所述第二设备将确认后的分流策略返回至第一设备, 还包括:
发送所述第二设备基于所述确认后的分流策略产生的承载更新流程或承 载新建修改流程的确定结果。
结合第二方面的第九种可能的实现方式, 在第十五种可能的实现方式中, 当所述第二设备为核心网设备时, 所述第二设备将所述确认后的分流策略返 回至所述第一设备, 包括:
当所述确认后的分流策略包括所述确认后的路由规则时, 所述第二设备 通过将所述确认后的分流策略携带于承载更新请求或承载新建请求中传输至
MME; 以使 MME接收到所述确认后的分流策略后, 将所述确认后的分流策 略携带于 NAS消息中传输至所述第一设备; 或者, 所述第二设备将所述确认 后的分流策略携带于分组数据协议 PDP上下文修改请求或者 PDP上下文新建 请求中发送至所述第一设备; 或者
当所述确认后的分流策略为确认后的缺省接入指示时, 所述第二设备将 所述确认后的缺省接入指示携带于会话新建响应中发送至 MME, 以使所述 MME接收到所述确认后的缺省接入指示后,将所述确认后的缺省接入指示携 带于 NAS消息中发送至所述第一设备; 或者, 所述第二设备将所述确认后的 缺省接入指示携带于会话新建响应中发送至可信接入网关 TWAG, 以使所述 TWAG接收到所述确认后的缺省接入指示后, 将所述确认后的缺省接入指示 携带于无线局域网控制面协议 WLCP分组数据网 PDN连接响应中发送至所述 第一设备; 或者, 所述第二设备将所述确认后的缺省接入指示携带于会话新 建响应中发送至非可信接入网关 ePDG, 以使所述 ePDG接收到所述确认后的 缺省接入指示,将所述确认后的缺省接入指示携带于网络密钥协商协议 IKEv2 消息中发送至所述第一设备。
结合第二方面的第十五种可能的实现方式, 在第十六种可能的实现方式 中, 当所述确认后的分流策略包括确认后的路由规则时, 所述第二设备使 MME将所述确认后的分流策略携带于 NAS消息中传输至所述第一设备, 包 括:
所述第二设备使 MME将所述确认后的分流策略作为新的参数添加至所 述 NAS消息中传输至所述第一设备; 或者
所述第二设备使 MME将所述确认后的分流策略添加至所述 NAS消息中 的 PCO中传输至所述第一设备。
结合第二方面的第十五种可能的实现方式, 在第十七种可能的实现方式 中, 当所述确认后的分流策略为确认后的缺省接入指示时, 所述第二设备将 所述确认后的缺省接入指示携带于所述会话新建响应中发送, 包括:
所述第二设备将所述确认后的缺省接入指示添加至所述会话新建响应中 的 PCO中发送;
当所述确认后的分流策略为确认后的缺省接入指示, 所述第二设备使 MME将所述确认后的缺省接入指示携带于所述 NAS消息中发送, 包括: 所述第二设备使 MME将所述确认后的缺省接入指示添加至所述 NAS消 息中的 PCO中发送;
当所述确认后的分流策略为确认后的缺省接入指示, 所述第二设备使 TWAG将所述确认后的缺省接入指示携带于所述 WLCP PDN连接响应中发送 时, 具体用于:
所述第二设备使 TWAG将所述确认后的缺省接入指示添加至所述 WLCP PDN连接响应中的 PCO中发送;
当所述确认后的分流策略为确认后的缺省接入指示时, 所述第二设备使 ePDG将所述确认后的缺省接入指示携带于所述 IKEv2消息中发送, 包括: 所述第二设备使 ePDG将所述确认后缺省接入指示作为新的参数添加至 所述 IKEv2消息中发送。
第三方面, 一种分流策略协商装置, 包括:
发送单元, 用于将分流策略发送至第二设备, 其中, 所述分流策略包括 以下至少一项: 缺省接入指示和至少一条路由规则;
接收单元, 用于接收并存储所述第二设备针对所述分流策略返回的确认 后的分流策略, 基于所述确认后的分流策略进行数据流传输。
结合第三方面, 在第一种可能的实现方式中, 所述分流策略协商装置为 核心网设备或者用户设备 UE。
结合第三方面的第一种可能的实现方式, 在第二种可能的实现方式中, 所述分流策略协商装置还包括:
生成单元, 用于在所述发送单元将分流策略发送至第二设备之前, 生成 分流策略, 所述生成单元具体用于:
当所述分流策略协商装置为核心网设备时, 所述生成单元根据接收的规 则信息、 UE发送的指示信息、 本地配置信息以及当前网络状态中的至少一项 生成至少一条路由规则作为分流策略; 或者
当所述分流策略协商装置为 UE时,所述生成单元根据自身的配置信息以 及当前网络状态中的至少一项生成至少一条路由规则和缺省接入指示中的至 少一项, 作为分流策略。
结合第三方面的第二种可能的实现方式, 在第三种可能的实现方式中, 所述路由规则包括: 路由接入技术、 流描述信息、 协商指示以及第一路由规 则标识信息, 其中, 所述第一路由规则标识信息为规则名称、 规则优先级中 的至少一项; 或者
所述路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示以 及第二路由规则标识信息, 其中, 所述第二路由规则标识信息为规则名称以 及规则优先级中的至少一项。
结合第三方面的第三种可能的实现方式, 在第四种可能的实现方式中, 当所述路由规则包括: 路由接入技术、 流描述信息、 协商指示以及第一路由 规则标识信息时, 所述协商指示用来标识 UE对路由规则的修改权限,取值为 允许协商标识或者禁止协商标识, 当协商指示取值为允许协商标识时, 表示 UE选择该路由规则中的路由接入技术或者其它接入技术; 当协商指示取值为 禁止协商标识时, 表示 UE选择该路由规则中的路由接入技术; 或者,
当所述路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示 以及第二路由规则标识信息时, 所述路由接入技术指示用来标识对路由规则 中的路由接入技术的使用权限, 取值为禁止值或者允许值, 当路由接入技术 指示取值为禁止值时, 表示禁止使用路由规则中的路由接入技术; 或者, 当 路由接入技术指示取值为允许值时, 表示允许使用路由规则中的路由接入技 术。
结合第三方面的第四种可能的实现方式, 在第五种可能的实现方式中, 当协商指示取值为禁止协商标识时, 表示协商指示所属的路由规则为禁止协 商的路由规则; 或者,
当路由接入技术指示取值为禁止值时, 表示路由接入技术指示所属的路 由规则为禁止协商的路由规则。
结合第三方面的第四种或第五种可能的实现方式, 在第六种可能的实现 方式中, 路由接入技术指示为禁止值对应的路由规则的规则优先级高于路由 接入技术指示为允许值对应的路由规则的规则优先级。
结合第三方面的第四种可能的实现方式, 在第七种可能的实现方式中, 当所述分流策略协商装置为 UE时, 所述路由规则中的协商指示为空; 或者 所述路由规则中包含的路由接入技术指示等于允许值。
结合第三方面的第二至第七中的任一种可能的实现方式, 在第八种可能 的实现方式中, 当所述分流策略协商装置为核心网设备时, 所述发送单元, 具体用于:
所述发送单元将所述路由规则携带于承载更新请求或承载新建请求中传 输至移动管理实体 MME, 以使 MME接收到所述路由规则后, 将所述路由规 则携带于非接入层 NAS消息中传输至所述第二设备; 或者
所述发送单元将所述路由规则携带于承载更新请求或承载新建请求中传 输至可信接入网关 TWAG, 以使所述 TWAG接收到所述路由规则后, 将所述 路由规则携带于指定的无线局域网控制面协议 WLCP消息中传输至所述第二 设备; 或者
所述发送单元将所述路由规则携带于承载更新请求或承载新建请求中传 输至非可信接入网关 ePDG, 以使所述 ePDG接收到所述路由规则后, 将所述 路由规则携带于网络密钥协商协议 IKEv2消息中传输至所述第二设备; 或者 所述发送单元将所述路由规则携带于分组数据协议 PDP上下文修改请求 或者 PDP新建请求中发送至所述第二设备。
结合第三方面的第八种可能的实现方式, 在第九种可能的实现方式中, 所述发送单元在将所述路由规则携带于承载更新请求或承载新建请求中传输 时, 具体用于:
所述发送单元将所述路由规则作为新的参数添加至所述承载更新请求或 承载新建请求中传输; 或者
所述发送单元将所述路由规则添加至所述承载更新请求或承载新建请求 中的承载上下文中传输; 或者
所述发送单元将所述路由规则添加至所述承载更新请求或承载新建请求 中的协议配置选项 PCO中传输。
结合第三方面的第八种可能的实现方式, 在第十种可能的实现方式中, 所述发送单元使 MME将所述路由规则携带于非接入层 NAS消息中传输时, 具体用于:
所述发送单元使 MME将所述路由规则作为新的参数添加至所述 NAS消 息中传输; 或者
所述发送单元使 MME将所述路由规则添加至所述 NAS消息中的 PCO中 传输。
结合第三方面中的第二至第七中的任一种可能的实现方式, 在第十一种 可能的实现方式中, 当所述分流策略协商装置为 UE时, 所述发送单元, 具体 用于:
当所述分流策略包括所述路由规则时, 所述发送单元将所述分流策略携 带于 NAS消息中发送至 MME, 以使所述 MME接收到所述分流策略后, 将 所述分流策略携带于承载资源命令中发送所述第二设备; 或者
当所述分流策略为缺省接入指示时, 所述发送单元将所述缺省接入指示 携带于 NAS消息中发送至 MME, 以使所述 MME接收到所述缺省接入指示 后, 将所述缺省接入指示携带于会话新建请求中发送至第二设备; 或者, 所 述发送单元将所述缺省接入指示携带于 WLCP分组数据网 PDN连接请求中发 送至 TWAG, 以使所述 TWAG接收到所述缺省接入指示后, 将所述缺省接入 指示携带于会话新建请求中发送至第二设备; 或者, 所述发送单元将所述缺 省接入指示携带于网络密钥协商协议 IKEv2 消息中发送至非可信接入网关 ePDG, 以使所述 ePDG接收到所述缺省接入指示后, 将所述缺省接入指示携 带于会话新建请求中发送至第二设备。
结合第三方面的第十一种可能的实现方式, 在第十二种可能的实现方式 中, 当所述分流策略包括所述路由规则, 所述发送单元在将所述分流策略携 带于 NAS消息中发送时, 具体用于:
所述发送单元将所述分流策略作为新的参数添加至所述 NAS 消息中发 送; 或者
所述发送单元将所述分流策略添加至所述 NAS消息中的 PCO中发送。 结合第三方面的第十一种可能的实现方式, 在第十三种可能的实现方式 中, 当所述分流策略为缺省接入指示, 所述发送单元在将所述缺省接入指示 携带于 NAS消息或者所述 WLCP PDN连接请求中发送时, 具体用于:
所述发送单元将所述缺省接入指示添加至所述 NAS消息或者所述 WLCP PDN连接请求中的 PCO中发送; 或者
当所述分流策略为缺省接入指示时, 所述发送单元使所述 MME或所述 TWAG将所述缺省接入指示携带于所述会话新建请求中发送时, 具体用于: 所述发送单元使所述 MME或所述 TWAG将所述缺省接入指示添加至所 述会话新建请求中的 PCO中发送; 或者
当所述分流策略为缺省接入指示时, 所述发送单元将所述缺省接入指示 携带于所述 IKEv2消息中发送时, 具体用于:
所述发送单元将所述缺省接入指示作为新的参数添加至所述 IKEv2消息 中发送。 结合第三方面的第四至第六中的任一种可能的实现方式, 在第十四种可 能的实现方式中, 当所述分流策略协商装置为核心网设备时, 所述接收单元, 具体用于:
若所述第二设备根据自身的配置信息以及当前网络状态中的至少一项对 接收的路由规则中至少一条路由规则进行修改, 则所述接收单元接收所述第 二设备发送的所述路由规则中未修改的其它路由规则以及对所述至少一条路 由规则进行修改后的更新的路由规则; 或者
若所述第二设备未对接收的所述路由规则进行修改, 则所述接收单元接 收未修改的所述路由规则。
结合第三方面的第十四种可能的实现方式, 在第十五种可能的实现方式 中, 所述第二设备修改的所述至少一条路由规则中包含的协商指示为允许协 商标识; 或者
所述第二设备修改的所述至少一条路由规则中包含的路由接入技术指示 等于允许值。
结合第三方面的第十四种可能的实现方式, 在第十六种可能的实现方式 中, 所述接收单元, 还用于:
接收所述第二设备基于所述确认后的分流策略产生的承载更新流程或承 载新建修改流程的确定结果。
结合第三方面的第四至第六中的任一种可能的实现方式, 在第十七种可 能的实现方式中, 当所述分流策略协商装置为 UE时, 所述接收单元, 具体用 于:
所述接收单元接收所述第二设备返回的确认后的路由规则和确认后的缺 省接入指示中的至少一项;
其中, 所述接收单元在接收所述第二设备返回的所述确认后的缺省接入 指示时, 具体用于:
若所述第二设备根据接收的规则信息、 UE发送的指示信息、 本地配置信 息以及当前网络状态中的至少一项对接收的所述缺省接入指示进行修改, 则 所述接收单元接收所述第二设备返回的修改后的缺省接入指示; 或者 若所述第二设备未对所述缺省接入指示进行修改, 则所述接收单元接收 所述第二设备返回的未修改的缺省接入指示;
所述接收单元在接收所述第二设备返回的所述确认后的路由规则时, 具 体用于:
若所述第二设备根据接收的规则信息、 UE发送的指示信息、 本地配置信 息以及当前网络状态中的至少一项对接收的所述路由规则中至少一条路由规 则进行修改, 则所述接收单元接收所述第二设备发送的所述路由规则中未修 改的其它路由规则以及对所述至少一条路由规则进行修改后的更新的路由规 则; 或者
若所述第二设备未对接收的所述路由规则进行修改, 则所述接收单元接 收的未修改的所述路由规则。
结合第三方面的第十七种可能的实现方式, 在第十八种可能的实现方式 中, 对所述至少一条路由规则进行修改后的更新的路由规则中包含的协商指 示为禁止协商标识; 或者
对所述至少一条路由规则进行修改后的更新的路由规则中包含的路由接 入技术指示为禁止值。
第四方面一种分流策略协商装置, 包括:
确认单元, 用于接收第一设备发送的分流策略, 并对所述分流策略进行 确认, 其中, 所述分流策略包括以下至少一项: 缺省接入指示和至少一条路 由规则;
处理单元, 用于存储确认后的分流策略, 并将所述确认后的分流策略返 回至所述第一设备, 基于所述确认后的分流策略进行数据流传输。
结合第四方面, 在第一种可能的实现方式中, 所述分流策略协商装置为 用户设备 UE或者核心网设备。
结合第四方面的第一种可能的实现方式, 在第二种可能的实现方式中, 当所述分流策略协商装置为 UE时,所述分流策略为所述第一设备发送的至少 一条路由规则; 或者
当所述分流策略协商装置为核心网设备时, 所述分流策略为第一设备发 送的至少一条路由规则和缺省接入指示中的至少一项。
结合第四方面的第二种可能的实现方式, 在第三种可能的实现方式中, 所述第一设备发送的所述路由规则中包括: 路由接入技术、 流描述信息、 协 商指示以及第一路由规则标识信息, 其中, 所述第一路由规则标识信息为规 则名称、 规则优先级中的至少一项; 或者
所述第一设备发送的所述路由规则中包括: 路由接入技术、 流描述信息、 路由接入技术指示以及第二路由规则标识信息, 其中, 所述第二路由规则标 识信息为规则名称以及规则优先级中的至少一项。
结合第四方面的第三种可能的实现方式, 在第四种可能的实现方式中, 当所述路由规则包括: 路由接入技术、 流描述信息、 协商指示以及第一路由 规则标识信息时, 所述协商指示用来标识 UE对路由规则的修改权限,取值为 允许协商标识或者禁止协商标识, 当协商指示取值为允许协商标识时, 表示 UE选择该路由规则中的路由接入技术或者其它接入技术; 当协商指示取值为 禁止协商标识时, 表示 UE选择该路由规则中的路由接入技术; 或者,
当所述路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示 以及第二路由规则标识信息时, 所述路由接入技术指示用来标识对路由规则 中的路由接入技术的使用权限, 取值为禁止值或者允许值, 当路由接入技术 指示取值为禁止值时, 表示禁止使用路由规则中的路由接入技术; 或者, 当 路由接入技术指示取值为允许值时, 表示允许使用路由规则中的路由接入技 术。
结合第四方面的第四种可能的实现方式, 在第五种可能的实现方式中, 当协商指示取值为禁止协商标识时, 表示协商指示所属的路由规则为禁止协 商的路由规则; 或者,
当路由接入技术指示取值为禁止值时, 表示路由接入技术指示所属的路 由规则为禁止协商的路由规则。 结合第四方面的第四或第五种可能的实现方式, 在第六种可能的实现方 式中, 路由接入技术指示为禁止值对应的路由规则的规则优先级高于路由接 入技术指示为允许值对应的路由规则的规则优先级。
结合第四方面的第四种可能的实现方式, 在第七种可能的实现方式中, 当所述第一设备为 UE时,所述第一设备发送的所述路由规则中的协商指示为 空; 或者
所述第一设备发送的所述路由规则中的路由接入技术指示等于允许值。 结合第四方面的第五至第七中任一种可能的实现方式, 在第八种可能的 实现方式中, 当所述分流策略协商装置为 UE时, 所述确认单元, 用于: 对所述路由规则进行确认;
所述确认单元对所述路由规则进行确认时, 具体用于:
所述确认单元判定自身的配置信息以及当前网络状态中的至少一项与所 述路由规则中至少一条路由规则不匹配, 且所述至少一条路由规则不是禁止 协商的路由规则时, 对所述至少一条路由规则进行修改, 并生成修改后的更 新的路由规则, 将所述路由规则中未修改的其它路由规则以及对所述至少一 条路由规则进行修改后的更新的路由规则作为确认后的路由规则; 或者
所述确认单元判定自身的配置信息以及当前网络状态中的至少一项与所 述路由规则中所有路由规则匹配, 或者自身的配置信息以及当前网络状态中 的至少一项与所述路由规则中不匹配的路由规则为禁止协商的路由规则时, 不对所述路由规则进行修改, 将未修改的所述路由规则作为确认后的路由规 则。
结合第四方面的第五至第七中任一种可能的实现方式, 在第九种可能的 实现方式中, 当所述分流策略协商装置为核心网设备时, 所述确认单元, 用 于:
对所述分流策略中的缺省接入指示进行确认, 和 /或, 对所述分流策略中 的路由规则进行确认;
其中, 所述确认单元对所述缺省接入指示进行确认时, 具体用于: 所述确认单元判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态中的至少一项与所述缺省接入指示不匹配时, 对所述缺省 接入指示进行修改, 将修改后的缺省接入指示作为确认后的缺省接入指示; 或者
所述确认单元判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态与所述缺省接入指示匹配时, 不对所述缺省接入指示进行 修改, 将未修改的所述缺省接入指示作为确认后的缺省接入指示;
所述确认单元对所述路由规则进行确认时, 具体用于:
所述确认单元判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态中的至少一项与所述路由规则中至少一条路由规则不匹配 时, 对所述至少一条路由规则进行修改, 并生成修改后的更新的路由规则, 将所述路由规则中未修改的其它路由规则以及对所述至少一条路由规则进行 修改后的更新的路由规则作为确认后的路由规则; 或者
所述确认单元判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态与所述路由规则中所有路由规则匹配时, 不对所述路由规 则进行修改, 将未修改的所述路由规则作为确认后的路由规则。
结合第四方面的第九种可能的实现方式, 在第十种可能的实现方式中, 所述确认单元对所述至少一条路由规则进行修改时, 具体用于:
所述确认单元对所述至少一条路由规则中包含的路由接入技术进行修 改, 并
在所述至少一条路由规则中包含协商指示时, 将所述至少一条路由规则 中包含的协商指示设置为禁止协商标识; 在所述至少一条路由规则包含路由 接入技术指示时, 将所述至少一条路由规则中包含的路由接入技术指示设置 为禁止值。
结合第四方面的第八种可能的实现方式, 在第十一种可能的实现方式中, 当所述分流策略协商装置为 UE时, 所述处理单元, 具体用于:
所述处理单元将所述确认后的路由规则携带于非接入层 NAS消息中传输 至移动管理实体 MME, 以使 MME接收到所述确认后的路由规则后, 将所述 确认后的路由规则携带于承载更新响应或承载新建响应中传输至所述第一设 备; 或者
所述处理单元将所述确认后的路由规则携带于指定的无线局域网控制面 协议 WLCP消息中传输至可信接入网关 TWAG,以使所述 TWAG接收到所述 确认后的路由规则后, 将所述确认后的路由规则携带于承载更新响应或承载 新建响应中传输至所述第一设备; 或者
所述处理单元将所述确认后的路由规则携带于网络密钥协商协议 IKEv2 消息中传输至非可信接入网关 ePDG, 以使所述 ePDG接收到所述确认后的路 由规则后, 将所述确认后的路由规则携带于承载更新响应或承载新建响应中 传输至所述第一设备。
结合第四方面的第十一种可能的实现方式, 在第十二种可能的实现方式 中, 所述处理单元将所述确认后的路由规则携带于 NAS消息中传输至 MME 时, 具体用于:
所述处理单元将所述确认后的路由规则作为新的参数添加至所述 NAS消 息中传输至 MME; 或者
所述处理单元将所述确认后的路由规则添加至所述 NAS消息中的协议配 置选项 PCO中传输至 MME。
结合第四方面的第十一种可能的实现方式, 在第十三种可能的实现方式 中, 所述处理单元使所述 MME、 所述 TWAG或者所述 ePDG将所述确认后 的路由规则携带于承载更新响应或承载新建响应中传输至所述第一设备时, 具体用于:
所述处理单元使所述 MME、 所述 TWAG或者所述 ePDG将所述确认后 的路由规则作为新的参数添加至所述承载更新响应或承载新建响应中传输至 所述第一设备; 或者
所述处理单元使所述 MME、 所述 TWAG或者所述 ePDG将所述确认后 的路由规则添加至所述承载更新响应或承载新建响应中的承载上下文中传输 至所述第一设备; 或者
所述处理单元使所述 MME、 所述 TWAG或者所述 ePDG将所述确认后 的路由规则添加至所述承载更新响应或承载新建响应中的 PCO中传输至所述 第一设备。
结合第四方面的第十一至第十三中任一种种可能的实现方式, 在第十四 种可能的实现方式中, 所述处理单元, 还用于:
发送所述分流策略协商装置基于所述确认后的分流策略产生的承载更新 流程或承载新建修改流程的确定结果。
结合第四方面的第九种可能的实现方式, 在第十五种可能的实现方式中, 当所述分流策略协商装置为核心网设备时, 所述处理单元, 具体用于:
当所述确认后的分流策略包括所述确认后的路由规则时, 所述处理单元 通过将所述确认后的分流策略携带于承载更新请求或承载新建请求中传输至 MME; 以使 MME接收到所述确认后的分流策略后, 将所述确认后的分流策 略携带于 NAS消息中传输至所述第一设备; 或者, 所述处理单元将所述确认 后的分流策略携带于分组数据协议 PDP上下文修改请求或者 PDP上下文新建 请求中发送至所述第一设备; 或者
当所述确认后的分流策略为确认后的缺省接入指示时, 所述处理单元将 所述确认后的缺省接入指示携带于会话新建响应中发送至 MME, 以使所述 MME接收到所述确认后的缺省接入指示后,将所述确认后的缺省接入指示携 带于 NAS消息中发送至所述第一设备; 或者, 所述处理单元将所述确认后的 缺省接入指示携带于会话新建响应中发送至可信接入网关 TWAG, 以使所述 TWAG接收到所述确认后的缺省接入指示后, 将所述确认后的缺省接入指示 携带于无线局域网控制面协议 WLCP分组数据网 PDN连接响应中发送至所述 第一设备; 或者, 所述处理单元将所述确认后的缺省接入指示携带于会话新 建响应中发送至非可信接入网关 ePDG, 以使所述 ePDG接收到所述确认后的 缺省接入指示,将所述确认后的缺省接入指示携带于网络密钥协商协议 IKEv2 消息中发送至所述第一设备。 结合第四方面的第十五种可能的实现方式, 在第十六种可能的实现方式 中, 当所述确认后的分流策略包括确认后的路由规则, 所述处理单元使 MME 将所述确认后的分流策略携带于 NAS消息中传输至所述第一设备时, 具体用 于:
所述处理单元使 MME将所述确认后的分流策略作为新的参数添加至所 述 NAS消息中传输至所述第一设备; 或者
所述处理单元使 MME将所述确认后的分流策略添加至所述 NAS消息中 的 PCO中传输至所述第一设备。
结合第四方面的第十五种可能的实现方式, 在第十七种可能的实现方式 中, 当所述确认后的分流策略为确认后的缺省接入指示, 所述处理单元将所 述确认后的缺省接入指示携带于所述会话新建响应中发送时, 具体用于: 所述处理单元将所述确认后的缺省接入指示添加至所述会话新建响应中 的 PCO中发送;
当所述确认后的分流策略为确认后的缺省接入指示, 所述处理单元使 MME将所述确认后的缺省接入指示携带于所述 NAS消息中发送时, 具体用 于:
所述处理单元使 MME将所述确认后的缺省接入指示添加至所述 NAS消 息中的 PCO中发送;
当所述确认后的分流策略为确认后的缺省接入指示, 所述处理单元使 TWAG将所述确认后的缺省接入指示携带于所述 WLCP PDN连接响应中发送 时, 具体用于:
所述处理单元使 TWAG将所述确认后的缺省接入指示添加至所述 WLCP PDN连接响应中的 PCO中发送;
当所述确认后的分流策略为确认后的缺省接入指示时, 所述处理单元使 ePDG将所述确认后的缺省接入指示携带于所述 IKEv2消息中发送时,具体用 于:
所述处理单元使 ePDG将所述确认后缺省接入指示作为新的参数添加至 所述 IKEv2消息中发送。
在本发明实施例中, 第一设备发送分流策略至第二设备, 其中, 该分流 策略中包括缺省接入指示和路由规则; 第一设备接收并存储第二设备针对该 分流策略返回的确认后的分流策略, 基于该确认后的分流策略进行数据流传 输。 这样, 在更新数据流分流策略时, 可以通过网络侧和 UE的协商, 获取一 个两侧都可以接受的路由规则, 提高了数据流传输效率, 解决了现有技术中 UE发起的数据流切换的方法适用性较低,且网络侧无法对 UE进行控制管理, 降低用户体验的问题。 附图说明
图 1为本发明实施例提供的一种第一设备侧的分流策略协商方法的流程 图;
图 2为本发明实施例提供的一种第二设备侧的分流策略协商方法的流程 图;
图 3为本发明实施例提供的第一种分流策略协商实例流程图;
图 4为本发明实施例提供的第二种分流策略协商实例流程图;
图 5为本发明实施例提供的第三种分流策略协商实例流程图;
图 6为本发明实施例提供的第四种分流策略协商实例流程图;
图 7为本发明实施例提供的第五种分流策略协商实例流程图;
图 8为本发明实施例提供的一种第一设备侧的分流策略协商装置结构图; 图 9为本发明实施例提供的一种第二设备侧的分流策略协商装置结构图; 图 10为本发明实施例提供的一种第一设备侧的分流策略协商设备结构 图;
图 11为本发明实施例提供的一种第二设备侧的分流策略协商设备结构 图。 具体实施方式 釆用本发明技术方案, 第一设备生成新的分流策略后, 将生成的新的分 流策略发送给第二设备, 待第二设备确认并保存后, 将确认后的分流策略返 回给第一设备, 第一设备保存该确认后的分流策略后, 第一设备和第二设备 基于该确认后的分流策略进行数据流传输, 这样, 在生成数据流的分流策略 过程中,可以通过网络侧和 UE的协商,获取一个两侧都可以接受的分流策略, 提高了数据流传输效率,解决了现有技术中 UE发起的数据流切换的方法适用 性较低, 且网络侧无法对 UE进行控制管理, 降低用户体验的问题。
在本发明实施例中, 分流策略包括路由规则和缺省接入指示中的至少一 项, 其中, 缺省接入指示, 即匹配数据流时, 在本地存储的所有路由规则中 未查到相应的路由规则与该数据流匹配, 则选择缺省接入指示中指定的接入 技术对该数据流进行传输, 如该缺省接入指示可以取值为 3GPP、 WLAN等。
本发明实施例提供了一种扩展的路由规则, 该路由规则中包括: 路由接 入技术、 流描述信息、 协商指示以及第一路由规则标识信息, 其中, 第一路 由规则标识信息为规则名称、 规则优先级中的至少一项。 可选的, 该路由规 则还可以包括路由接入技术优先级。 在本实施例中, 仅以路由规则包含路由 接入技术、 流描述信息、 协商指示、 规则名称、 规则优先级为例, 参阅表 1 所示。
表 1 第一种扩展的路由规则
Figure imgf000030_0001
其中, 规则名称可以唯一标识每条路由规则 (即路由表项);
每条路由规则中的路由接入技术为该路由规则推荐的接入技术标识, 可 以取值 3GPP、 WLAN, 非 3GPP或 WinMax等; 值, 数值越小优先级越高;
流描述信息指示了数据流描述信息, 具体的, 该数据流描述信息可以包 含源目的 IP地址、 源目的端口号、 协议类型等的至少一种参数;
协商指示用来实现路由规则的协商,协商指示用来标识 UE对路由规则的 修改权限, 取值为允许协商标识和禁止协商标识, 当协商指示取值为允许协 商标识时,表示 UE可以选择该路由规则中的路由接入技术,也可以选择其它 接入技术; 当协商指示取值为禁止协商标识时,表示 UE只能选择该路由规则 中的路由接入技术。 具体的, 协商指示用来指示当前路由规则是否可以被 UE 修改, 协商指示一般可以为允许协商标识和禁止协商标识两类取值, 如可以 但不局限于釆用布尔量数值进行定义, 在本实施例中, 仅以布尔数值为例, 对于一条具体的路由规则, 若协商指示取值为 1,表示该条路由规则允许被协 商, 即允许 UE对其进行修改; 如果协商指示取值为 0表示该条路由规则不允 许被协商, 即不允许 UE对其进行修改, 因此, 1即为允许协商指示, 0即为 禁止协商指示。
当协商指示取值为禁止协商标识时, 表示协商指示所属的路由规则为禁 止协商的路由规则
在选择接入技术传输数据流时, 可以根据参阅表 1 中的路由规则确定传 输该数据流所用的接入技术。
具体的, 获取接收的数据流的特征, 根据获取的数据流特征与本地存储 的路由规则的流描述信息进行匹配, 将包含该数据流的特征对应的流描述信 息的路由规则作为备选路由规则;
当获得的备选路由规则数目为 0 时, 则选择本地存储的缺省接入指示中 设置的路由接入技术对该数据流进行传输;
当获得的备选路由规则数目为 1 时, 则直接选择该路由规则中包含的路 由接入技术对该数据流进行传输;
当获得的备选路由规则数目大于 1 时, 则可以在备选路由规则中选择规 则优先级最高的路由规则作为目标路由规则, 选择该目标路由规则中包含的 路由接入技术对该数据流进行传输。
例如,仍以表 1中的路由规则为例,若 UE接收到数据流的特征为数据流 描述信息 1 的数据流, 则可以在本地存储的路由规则中检索到规则名称为 1 的路由规则,并根据该路由规则中规定的路由接入技术 3GPP对该数据流进行 传输。
本发明实施例还提供了另外一种扩展的路由规则, 该路由规则中包括: 路由接入技术、 流描述信息、 路由接入技术指示以及第二路由规则标识信息, 其中, 第二路由规则标识信息为规则名称以及规则优先级中的至少一项。 在 本实施例中, 以路由规则包含路由接入技术、 流描述信息、 规则名称、 路由 接入技术指示以及规则优先级为例, 参阅表 2所示。
表 2 第二种扩展的路由规则
Figure imgf000032_0001
其中, 规则名称、 路由接入技术、 规则优先级以及流描述信息与第一种 扩展的路由规则中的意义相同, 在此处不再赘述。
在本发明实施例提供的第一种扩展的路由规则中, 是通过设置协商指示, 来实现路由规则的协商, 而在本发明实施例提供的第二种扩展的路由规则中 是通过路由接入技术指示来实现的。
路由接入技术指示体现路由接入技术是允许使用还是禁止使用, 路由接 入技术指示用来标识对路由规则中的路由接入技术的使用权限, 当路由接入 技术指示取值为禁止值时, 表示禁止使用路由规则中的路由接入技术, 当路 由接入技术指示取值为允许值时, 表示允许使用路由规则中的路由接入技术; 且路由接入技术指示取值为禁止值时, 表示路由接入技术指示所属的路由规 则为禁止协商的路由规则。 路由接入技术指示为禁止值对应的路由规则的规 则优先级高于路由接入技术指示为允许值对应的路由规则的规则优先级。 具 体来讲, 当路由接入技术指示为允许时, 表示匹配上流描述信息的数据流可 以使用路由接入技术中指示的接入技术传输。 相反, 当路由接入技术指示为 禁止时, 表明匹配上流描述信息的数据流禁止使用路由接入技术中指示的接 入技术传输。 在本实施例中, 仍以布尔取值为例, 当取值为 1 时表示允许使 用相应路由接入技术传输, 当取值为 0时表示禁止使用该路由接入技术传输。 此外, 当取值为 0时, UE必须严格遵守该策略指示, 禁止在相应的接入技术 上传输匹配的数据流, 即策略不能被 UE修改, 为禁止协商策略。 相反, 如果 取值为 1, UE也可以选择其他接入技术传输匹配数据流, 为允许协商策略。
当路由接入技术指示取值为禁止值时, 表示路由接入技术指示所属的路 由规则为禁止协商的路由规则。
进一步来讲, 若根据接收到的数据流匹配到路由接入技术指示取值为 0 的禁止协商的路由规则, 则选择除该禁止协商的路由规则中包含的路由接入 技术之外的其它路由接入技术对该数据流进行传输。 UE不能对该禁止协商的 路由规则进行修改, 可以对路由接入技术指示取值为 1 的允许协商的路由规 则外的其它路由规则进行修改,即 UE必须釆用禁止协商的路由规则中规定的 路由接入技术之外的其它路由接入技术对数据流进行传输, 而可以釆用允许 协商的路由规则中规定的路由接入技术对数据流进行传输, 还可以釆用允许 协商的路由规则中规定的路由接入技术外的其它路由接入技术对数据流进行 传输。
在选择接入技术传输数据流时, 可以根据参阅表 2 中的路由规则确定传 输该数据流所用的接入技术。
具体的, 获取接收的数据流的特征, 根据获取的数据流特征与本地存储 的路由规则的流描述信息进行匹配, 将包含该数据流的特征对应的流描述信 息的路由规则作为备选路由规则;
当获得的备选路由规则数目为 0 时, 则选择本地存储的缺省接入指示中 设置的路由接入技术对该数据流进行传输;
当备选路由规则数目为 1, 且路由接入技术指示为非指定的数值 0时, 则 根据该备选路由规则中包含的路由接入技术对该数据流进行传输, 若接收该 数据流的设备为 UE, 则 UE还可以使用其他路由接入技术对该数据流进行传 输;
当备选路由规则数目为 1, 且路由接入技术指示为指定的数值 0时, 即该 备选路由规则为禁止协商的路由规则, 则选择除该禁止路由规则中包含的路 由接入技术之外的路由接入技术对该数据流进行传输;
当备选路由规则数目大于 1,则可以在备选路由规则中选择规则优先级最 高的路由规则作为目标路由规则, 根据该目标路由规则中包含的路由接入技 术对该数据流进行传输。
一般的, 可以设置禁止协商的路由规则的规则优先级高于允许协商的路 由规则的规则优先级, 即路由接入技术指示为禁止值对应的路由规则的规则 优先级高于路由接入技术指示为允许值对应的路由规则的规则优先级。
本发明实施例提供了一种分流策略协商方法, 适用于处理数据流切换业 务的 UE和网络侧设备, 如 P-GW, 下面结合附图对本发明优选的实施方式进 行详细说明。
参阅图 1 所示, 本发明实施例提供的一种分流策略协商方法的具体处理 流程包括:
步骤 101 : 第一设备将分流策略发送至第二设备, 其中, 该分流策略中包 括以下至少一项缺省接入指示和至少一条路由规则。
第一设备发送的分类策略一般为第一设备生成的分类策略。
第一设备生成的分流策略可以包括新建立的分流策略以及在原分流策略 中修改得到的新的分流策略。
其中, 第一设备为根据分流策略进行数据流传输的设备, 具体的, 可以 为核心网设备(如 P-GW )或者 UE, 在本实施例中, 仅以第一设备为 P-GW 或 UE为例。 同理, 第二设备也为根据分流策略进行数据流传输的设备, 由于第一设 备与第二设备进行路由规则协商, 因此, 当第一设备为核心网设备时, 第二 设备为 UE; 当第一设备为 UE时, 第二设备为核心网设备。
由于第一设备可以为核心网设备或 UE, 因此, 第一设备生成分流策略, 包括两种方式:
第一种方式: 当第一设备为核心网设备时, 该第一设备根据接收的规则 信息 (如, PCRF发送的 PCC规则, 或 UE发送指示信息等)、 本地配置信息 以及当前网络状态中的至少一项生成或修改至少一条路由规则作为分流策 略; 或者
第二种方式: 当第一设备为 UE时,该第一设备根据自身的配置信息以及 当前网络状态中的至少一项生成或修改至少一条路由规则和缺省接入指示中 的至少一项, 作为分流策略。
具体的, 当第一设备为核心网设备时, 例如 P-GW时, P-GW可以基于 PCRF下发的规则信息 (如 PCC规则等)、 UE发送的指示信息 (如 UE发送 的缺省接入指示)、 本地配置信息以及当前网络状态等至少一种信息决定新建 或修改路由规则, 上述信息包括例如指定某些数据流必须通过 3GPP 网络传 输, 当前网络状态例如 3GPP网络畅通, 非 3GPP网络故障或信号质量差等。
而当第二设备为 UE时, 自身的配置信息如用户设置在 UE中的具体的应 用选择哪种接入技术。 当 UE在该应用运行时, 则根据上述自身的配置信息以 及当前的网络状态生成或修改路由规则。
在本实施例中, 定义了两种新的扩展的路由规则形式, 例如上述表 1 和 表 2中的扩展的路由规则:
第一种形式: 第一设备生成的路由规则中包括: 路由接入技术、 流描述 信息、 协商指示以及第一路由规则标识信息, 其中, 第一路由规则标识信息 为规则名称、 规则优先级中的至少一项;
第二种形式: 第一设备生成的路由规则中包括: 路由接入技术、 流描述 信息、 路由接入技术指示以及第二路由规则标识信息, 其中, 第二路由规则 标识信息为规则名称、 以及规则优先级中的至少一项。
为了更好的实现路由规则协商的效果, 在本实施例仅以第一种形式中, 包括路由接入技术、 流描述信息、 协商指示、 规则名称以及规则优先级的路 由规则为例; 以及仅以第二种形式中的, 包括路由接入技术、 流描述信息、 规则名称、 路由接入技术指示以及规则优先级的路由规则为例。
当路由规则包括: 路由接入技术、 流描述信息、 协商指示以及第一路由 规则标识信息时,协商指示用来标识 UE对路由规则的修改权限,取值为允许 协商标识或者禁止协商标识, 当协商指示取值为允许协商标识时,表示 UE选 择该路由规则中的路由接入技术或者其它接入技术; 当协商指示取值为禁止 协商标识时, 表示 UE选择该路由规则中的路由接入技术; 或者,
当路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示以及 第二路由规则标识信息时, 路由接入技术指示用来标识对路由规则中的路由 接入技术的使用权限, 取值为禁止值或者允许值, 当路由接入技术指示取值 为禁止值时, 表示禁止使用路由规则中的路由接入技术; 或者, 当路由接入 技术指示取值为允许值时, 表示允许使用路由规则中的路由接入技术。
当协商指示取值为禁止协商标识时, 表示协商指示所属的路由规则为禁 止协商的路由规则; 或者,
当路由接入技术指示取值为禁止值时, 表示路由接入技术指示所属的路 由规则为禁止协商的路由规则。
路由接入技术指示为禁止值对应的路由规则的规则优先级高于路由接入 技术指示为允许值对应的路由规则的规则优先级。
其中,当第一设备为 UE时,第一设备生成的路由规则中的协商指示为空; 或者
第一设备生成的路由规则中包含的路由接入技术指示等于允许值。
具体的, 当该第一设备为核心网设备 (如 P-GW )时, 第一设备生成或修 改的分流策略为路由规则, 第一设备将分流策略发送至第二设备, 包括: 第一设备将该路由规则携带于承载更新请求或承载新建请求传输至 MME; 以使 MME接收到该路由规则后,将该路由规则携带于非接入层( Non Access Stratum, NAS ) 消息传输至第二设备; 或者
第一设备将该路由规则携带于承载更新请求或承载新建请求中传输至可 信接入网关( Trusted WLAN Access Gateway, TWAG ); 以使该 TWAG接收到 该路由规则后, 将该路由规则携带于指定的无线局域网控制面协议 WLCP消 息中传输至第二设备; 或者
第一设备将该路由规则携带于承载更新请求或承载新建请求中传输至非 可信接入网关(evolved Packet Date Gateway, ePDG ), 以使该 ePDG接收到 该路由规则后,将该路由规则携带于网络密钥协商协议( Internet Key Exchange version 2, IKEv2 ) 消息中传输至第二设备; 或者
第一设备将该路由规则携带于分组数据协议 ( Packet Data Protocol, PDP ) 上下文修改请求或者 PDP新建请求中发送至第二设备。
其中指定的 WLCP消息包括: WLCP NB_IFOM Request/Response消息、 WLCP Create Bearer Request/Response、 WLCP Update Bearer Request/Response 等。 其中, 如果生成的路由规则是从非 3GPP侧(如 TWAN网络)发送给 UE 的, 则需要定义可信 WLAN接入网( Trusted WLAN access network., TWAN ) 与 UE 之间的消息作为制定的信令消息, 例如, 定义 WLCP NB_IFOM Request/Response消息, 然后在该消息中携带生成的路由规则发送至 UE。
其中, 承载更新请求或承载新建请求可以通过以下几种形式传输路由规 则:
第一种, 第一设备将路由规则作为新的参数添加至所述承载更新请求或 承载新建请求中传输。
第二种, 第一设备将路由规则添加至承载更新请求或承载新建请求中的 承载上下文中传输。
第三种, 第一设备将路由规则添加至承载更新请求或承载新建请求中的 协议配置选项 (Protocol Configuration Option, PCO ) 中传输。
NAS消息通过以下两种方式传输路由规则: 第一种, 第一设备使 MME将路由规则作为新的参数添加至 NAS消息中 传输, 即路由规则可以作为单独的参数在 NAS消息中传递。
第二种,第一设备使 MME将路由规则添加至 N AS消息中的 PCO中传输。 较佳地, 当路由规则在存储于承载更新请求或承载新建请求中的 PCO中 传输至 MME后, MME继续将该路由规则存储于 NAS消息中的 PCO中传递。
具体的, 当第一设备为 UE时, 第一设备生成的分流策略包括路由规则和 缺省接入指示中的至少一项, 第一设备将生成的分流策略发送至第二设备, 包括:
当分流策略至少包括路由规则时, 第一设备通过将分流策略携带于 NAS 消息中发送至 MME, 以使 MME接收到该分流策略后, 将该分流策略携带于 承载资源命令中发送第二设备; 或者
当分流策略为缺省接入指示时, 第一设备将生成的缺省接入指示携带 NAS消息中发送至 MME, 以使 MME接收到该缺省接入指示后,将该缺省接 入指示携带于会话新建请求中发送至第二设备; 或者, 第一设备将该缺省接 入指示携带于 WLCP PDN连接请求中发送至 TWAG, 以使该 TWAG接收到 缺省接入指示后, 将该缺省接入指示携带于会话新建请求中发送至第二设备; 或者, 第一设备将该缺省接入指示携带于网络密钥协商协议(Internet Key Exchange version 2 , IKEv2 )消息中发送至非可信接入网关( evolved Packet Date Gateway, ePDG ), 以使该 ePDG接收到缺省接入指示后, 将该缺省接入指示 携带于会话新建请求中发送至第二设备。
其中, 当分流策略包括路由规则时, 第一设备将该分流策略作为新的参 数添加至 NAS消息中发送, 或者, 第一设备将该分流策略添加至 NAS消息 中的 PCO中发送, 即分流策略可以作为单独的参数在 NAS消息中传递, 也 可以存储于 NAS消息中的 PCO中传递。
当分流策略为缺省接入指示时, 将该缺省接入指示携带于 NAS消息、 会 话新建请求或 WLCP PDN 连接请求中发送包括: 将该缺省接入指示添加至 NAS消息、 会话新建请求或者 WLCP PDN连接请求中的 PCO中发送; 将该 缺省接入指示携带于 IKEv2消息中发送, 包括: 将该缺省接入指示作为新的 参数添加至 IKEv2消息中发送。
步骤 102:第一设备接收并存储第二设备针对分流策略返回的确认后的分 流策略, 基于该确认后的分流策略进行数据流传输。
具体的, 当第一设备为核心网设备时, 第一设备生成的分流策略为路由 规则, 因此, 确认后的分流策略为确认后的路由规则, 第一设备接收第二设 备返回的确认后的分流策略, 包括:
若第二设备根据自身的配置信息以及当前网络状态中的至少一项对接收 的路由规则中至少一条路由规则进行修改, 则第一设备接收第二设备发送的 该路由规则中未修改的其它路由规则以及对至少一条路由规则进行修改后的 更新的路由规则; 或者
若第二设备未对接收的路由规则进行修改, 则第一设备接收的未修改的 该路由规则。
其中, 第二设备在返回未修改的路由规则时, 可以返回该未修改的路由 规则, 还可以只返回该未修改的路由规则标识。
具体的, 对路由规则进行修改, 即修改路由规则中的路由接入技术。 其中, 第二设备修改的该至少一条路由规则中包含的协商指示为允许协 商标识; 或者
第二设备修改的所述至少一条路由规则中包含的路由接入技术指示等于 允许值, 即第二设备 UE在确认路由规则时, 只能针对设置为 UE可以修改的 路由规则进行修改。
可选的, 在网络侧通过承载更新流程或承载新建流程的同时进行分流策 略协商的过程中, 在第一设备接收第二设备针对分流策略返回的确认后的分 流策略, 还包括:
接收第二设备基于该确认后的分流策略产生的承载更新流程或承载新建 修改流程的确定结果。
其中, 确定结果包括: UE接受网络侧发起的承载更新流程或承载新建修 改流程,或者 UE不接受网络侧发起的承载更新流程或承载新建修改流程, 同 时还包括 UE的特殊原因值, 如 UE refuse、 IP traffic remove、 N3GPP preferred 等。
具体的, 当第一设备为 UE时, 第一设备生成的分类策略包括路由规则和 缺省接入指示中的至少一项, 第一设备接收第二设备针对分流策略返回的确 认后的分流策略, 包括:
第一设备接收第二设备返回的确认后的路由规则和确认后的缺省接入指 示中的至少一项;
其中, 第一设备接收第二设备返回的确认后的缺省接入指示, 包括: 若第二设备根据接收的规则信息、 本地配置信息以及当前网络状态中的 至少一项对接收的缺省接入指示进行修改, 则第一设备接收第二设备返回的 修改后的缺省接入指示; 或者
若第二设备未对该缺省接入指示进行修改, 则第一设备接收第二设备返 回的未修改的缺省接入指示。
第一设备接收第二设备返回的确认后的路由规则, 包括:
若第二设备根据接收的规则信息、 本地配置信息以及当前网络状态中的 至少一项对接收的路由规则中至少一条路由规则进行修改, 则第一设备接收 第二设备发送的该路由规则中未修改的其它路由规则以及对至少一条路由规 则进行修改后的更新的路由规则; 或者
若第二设备未对接收的路由规则进行修改, 则第一设备接收未修改的该 路由规则。
其中, 对该至少一条路由规则进行修改后的更新的路由规则中包含的协 商指示为禁止协商标识; 或者, 对该至少一条路由规则进行修改后的更新的 路由规则中包含的路由接入技术指示为禁止值。
这样, 网络侧接收到 UE生成的路由规则后, 对该路由规则进行确认, 即 对网络侧不允许某种路由接入技术传输某数据流时, 将对应的路由规则进行 强制修改, 并将修改后的更新的路由规则设置为禁止 UE再次修改, UE必须 按该路由规则的规定执行数据流传输的路由规则。
基于上述实施例, 参阅图 2所示, 本发明实施例还提供的一种分流策略 协商方法, 具体处理流程包括:
步骤 201 : 第二设备接收第一设备发送的分流策略, 并对该分流策略进行 确认, 其中, 分流策略包括以下至少一项: 缺省接入指示和至少一条路由规 则。
其中, 第二设备为根据分流策略进行数据流传输的设备, 具体的, 可以 为核心网设备(如 P-GW )或者 UE, 在本实施例中, 仅以第二设备为 P-GW 或 UE为例。
同理, 第一设备也为根据分流策略进行数据流传输的设备, 由于第一设 备与第二设备进行路由规则协商, 因此, 当第二设备为核心网设备时, 第一 设备为 UE; 当第二设备为 UE时, 第一设备为核心网设备。
当第二设备为 UE时,第二设备接收的分流策略为第一设备发送的至少一 条路由规则; 或者
当第二设备为核心网设备时, 第二设备接收的分流策略为第一设备发送 的至少一条路由规则和缺省接入指示中的至少一项。
第一设备发送的路由规则中包括两种形式:
第一种形式: 第一设备发送的路由规则中包括: 路由接入技术、 流描述 信息、 协商指示以及第一路由规则标识信息, 其中, 第一路由规则标识信息 为规则名称、 规则优先级中的至少一项; 或者
第二种形式: 第一设备发送的路由规则中包括: 路由接入技术、 流描述 信息、 路由接入技术指示以及第二路由规则标识信息, 其中, 第二路由规则 标识信息为规则名称以及规则优先级中的至少一项。
为了更好的实现路由规则协商的效果, 在本实施例仅以第一种形式中, 包括路由接入技术、 流描述信息、 协商指示、 规则名称以及规则优先级的路 由规则为例; 以及仅以第二种形式中的, 包括路由接入技术、 流描述信息、 规则名称、 路由接入技术指示以及规则优先级的路由规则为例。 当路由规则包括: 路由接入技术、 流描述信息、 协商指示以及第一路由 规则标识信息时,协商指示用来标识 UE对路由规则的修改权限,取值为允许 协商标识或者禁止协商标识, 当协商指示取值为允许协商标识时,表示 UE选 择该路由规则中的路由接入技术或者其它接入技术; 当协商指示取值为禁止 协商标识时, 表示 UE选择该路由规则中的路由接入技术; 或者,
当路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示以及 第二路由规则标识信息时, 路由接入技术指示用来标识对路由规则中的路由 接入技术的使用权限, 取值为禁止值或者允许值, 当路由接入技术指示取值 为禁止值时, 表示禁止使用路由规则中的路由接入技术; 或者, 当路由接入 技术指示取值为允许值时, 表示允许使用路由规则中的路由接入技术。
当协商指示取值为禁止协商标识时, 表示协商指示所属的路由规则为禁 止协商的路由规则; 或者,
当路由接入技术指示取值为禁止值时, 表示路由接入技术指示所属的路 由规则为禁止协商的路由规则。
路由接入技术指示为禁止值对应的路由规则的规则优先级高于路由接入 技术指示为允许值对应的路由规则的规则优先级。
其中,当第一设备为 UE时,第一设备发送的路由规则中的协商指示为空; 或者
第一设备发送的路由规则中包含的路由接入技术指示等于允许值。
具体的, 当第二设备为 UE时, 第二设备接收的分流策略为第一设备发送 的路由规则, 第二设备对分流策略进行确认, 包括:
第二设备对该路由规则进行确认, 具体包括:
第二设备判定自身的配置信息以及当前网络状态中的至少一项与该路由 规则中至少一条路由规则不匹配, 且该至少一条路由规则不是禁止协商的路 由规则时, 对该至少一条路由规则进行修改, 并生成修改后的更新的路由规 则, 将该路由规则中未修改的其它路由规则以及对该至少一条路由规则进行 修改后的更新的路由规则作为确认后的路由规则; 或者 第二设备判定自身的配置信息以及当前网络状态中的至少一项与该路由 规则中所有路由规则匹配, 或者自身的配置信息以及当前网络状态中的至少 一项与该路由规则中不匹配的路由规则为禁止协商的路由规则时, 不对该新 的路由规则进行修改, 将未修改的该路由规则作为确认后的路由规则。
具体的, 当第二设备为核心网设备时, 第二设备接收的分流策略为第一 设备发送的路由规则和缺省接入指示中的至少一项, 第二设备对该分流策略 进行确认, 包括:
第二设备对该分流策略中的缺省接入指示进行确认, 和 /或, 第二设备对 该分流策略中的路由规则进行确认。
其中, 第二设备对该缺省接入指示进行确认, 包括:
第二设备判定接收的规则信息、 UE发送的指示信息、 本地配置信息以及 当前网络状态中的至少一项与该缺省接入指示不匹配时, 对该缺省接入指示 进行修改, 将修改后的缺省接入指示作为确认后的缺省接入指示; 或者
第二设备判定接收的规则信息、 UE发送的指示信息、 本地配置信息以及 当前网络状态与该缺省接入指示匹配时, 不对该缺省接入指示进行修改, 将 未修改的该缺省接入指示作为确认后的缺省接入指示。
第二设备对该路由规则进行确认, 包括:
第二设备判定接收的规则信息、 UE发送的指示信息、 本地配置信息以及 当前网络状态中的至少一项与该路由规则中至少一条路由规则不匹配时, 对 至少一条路由规则进行修改, 并生成修改后的更新的路由规则, 将该路由规 则中未修改的其它路由规则以及对至少一条路由规则进行修改后的更新的路 由规则作为确认后的路由规则; 或者
第二设备判定接收的规则信息、 UE发送的指示信息、 本地配置信息以及 当前网络状态与该路由规则中所有路由规则匹配时, 不对该路由规则进行修 改, 将未修改的该路由规则作为确认后的路由规则。
其中, 第二设备对至少一条路由规则进行修改包括:
第二设备对该至少一条路由规则中包含的路由接入技术进行修改, 并 在该至少一条路由规则中包含协商指示时, 将该至少一条路由规则中包 含的协商指示设置为禁止协商标识; 在该至少一条路由规则包含路由接入技 术指示时, 将该至少一条路由规则中包含的路由接入技术指示设置为禁止值。
步骤 202: 第二设备存储确认后的分流策略, 并将确认后的分流策略返回 至第一设备, 基于该确认后的分流策略进行数据流传输。
第二设备确认后的路由规则与接收的第一设备生成的新的路由规则相 比, 数目未发生变化, 只是将其中某些路由规则进行修改。
具体的, 当第二设备为 UE时, 其中, 确认后的分流策略为确认后的路由 规则, 第二设备将确认后的分流策略返回至第一设备, 包括:
第二设备将确认后的路由规则携带与 NAS 消息中传输至 MME; 以使 MME接收到确认后的路由规则后,将确认后的路由规则携带于承载更新响应 或承载新建响应中传输至第一设备; 或者
第二设备将确认后的路由规则携带于指定的 WLCP 消息中传输至 TWAG, 以使该 TWAG接收到确认后的路由规则后, 将确认后的路由规则携 带于承载更新响应或承载新建响应中传输至第一设备; 或者
第二设备将确认后的路由规则携带于 IKEv2 消息中传输至 ePDG, 以使 ePDG接收到确认后的路由规则后,将确认后的路由规则携带于承载更新响应 或承载新建响应中传输至第一设备。
其中, 第二设备将确认后的路由规则携带于 NAS消息中传输至 MME, 包括:
第二设备将确认后的路由规则作为新的参数添加至 NAS 消息中传输至 MME; 或者, 第二设备将确认后的路由规则添加至 NAS消息中的 PCO中传 输至 MME。
MME将确认后的路由规则携带于承载更新响应或承载新建响应中传输 至第一设备, 包括:
MME将确认后的路由规则作为新的参数添加至承载更新响应或承载新 建响应中传输至第一设备; 或者 MME将确认后的路由规则添加至承载更新响应或承载新建响应中的承 载上下文中传输至第一设备; 或者
MME 将确认后的路由规则添加至承载更新响应或承载新建响应中的 PCO中传输至第一设备。
可选的, 第二设备将确认后的分流策略返回至第一设备, 还包括: 发送第二设备基于该确认后的分流策略产生的承载更新流程或承载新建 修改流程的确定结果。
具体的, 当第二设备为核心网设备时, 确认后的分流策略包括确认后的 路由规则和确认后的缺省接入指示中的至少一项, 第二设备将确认后的分流 策略返回至第一设备, 包括:
当确认后的分流策略包括确认后的路由规则时, 第二设备通过将该确认 后的分流策略携带于承载更新请求或承载新建请求中传输至 MME; 以使 MME接收到该确认后的分流策略后, 将该确认后的分流策略携带于 NAS消 息中传输至第一设备; 或者, 第二设备将该确认后的分流策略携带于 PDP上 下文修改请求或者 PDP上下文新建请求中发送至第一设备; 或者
当该确认后的分流策略为确认后的缺省接入指示时, 第二设备将该确认 后的缺省接入指示携带于会话新建响应中发送至 MME, 以使 MME接收到该 确认后的缺省接入指示后, 将该确认后的缺省接入指示携带于 NAS消息中发 送至所述第一设备; 或者, 第二设备将该确认后的缺省接入指示携带于会话 新建响应中发送至 TWAG,以使该 TWAG接收到该确认后的缺省接入指示后, 将该确认后的缺省接入指示携带于 WLCP PDN连接响应中发送至第一设备; 或者, 第二设备将该确认后的缺省接入指示携带于会话新建响应中发送至 ePDG, 以使该 ePDG接收到该确认后的缺省接入指示, 将该确认后的缺省接 入指示携带于 IKEv2消息中发送至第一设备。
其中, 当确认后的分流策略包括确认后的路由规则时, 将该确认后的分 流策略携带于 NAS消息中传输至第一设备, 包括:
将该确认后的分流策略作为新的参数添加至 NAS 消息中传输至第一设 备; 或者
将该确认后的分流策略添加至 NAS消息中的 PCO中传输至第一设备。 当确认后的分流策略为确认后的缺省接入指示时, 将该确认后的缺省接 入指示携带于 NAS消息、 会话新建响应或 WLCP PDN连接响应中发送, 包 括:
将确认后的缺省接入指示添加至 NAS 消息、 会话新建响应或者 WLCP PDN连接响应中的 PCO中发送; 或者
当确认后的分流策略为确认后的缺省接入指示时, 将确认后的缺省接入 指示携带于 IKEv2消息中发送, 包括:
将确认后的缺省接入指示作为新的参数添加至 IKEv2消息中发送。
基于以上实施例中的提供的一种路由规则协商方法, 在本发明实施例中 还提供的在 5种不同的场景下的路由规则协商具体实例。
例 1, 本发明实施例提供了一种由网络侧发起的路由规则协商机制, 网络 侧通过承载资源更新流程与 UE进行路由规则协商,参阅图 3所示,路由规则 协商具体流程为:
首先, UE从一个 3GPP网络和一个非 3GPP网络同时接入一个 PDN连接, 同时, UE和 P-GW之间有多个数据流的路由信息。
步骤 301: 家乡 PCRF ( Home PCRF, hPCRF )发起 IP连接接入网会话 修改 IP-CAN Session Modification过程, 修改某些数据流的参数, 如将某一数 据流的路由接入技术从 3GPP改为非 3GPP。
步骤 302: P-GW基于 hPCRF下发的规则信息 (如计费策略等)、 UE发 送的指示信息、 本地配置信息以及当前网络状态等至少一种信息决定新建或 修改路由规则,从而产生新的路由规则, P-GW根据新的路由规则发起承载更 新流程, 即发送承载更新请求 Update Bearer Request, 将 P-GW产生的新的路 由规则发送至 UE。
P-GW生成的新的路由规则,如上述实施例提供的第一种扩展的路由规则 或第二种扩展的路由规则。 P—GW生成的新的路由规则的数目可以为 1条也可 以为多条。
其中, 承载更新流程可以在 3GPP侧触发, 也可在非 3GPP侧触发, 或同 时在 3GPP侧与非 3GPP侧触发, 本发明实施例对此不做限制, 在本实施例中 仅以在 3GPP侧进行承载更新流程为例。
步骤 303: P-GW在 3GPP侧发送 Update Bearer Request消息给 S-GW, 其中, Update Bearer Request中携带有 P-GW生成的新的路由规则。
在本发明实施例中,不局限于将路由规则通过 Update Bearer Request消息 中的新增参数进行传输, 也可以将该路由规则通过该 Update Bearer Request 消息中的承载上下文 bearer context 进行传输, 还可以通过 Update Bearer Request消息中的协议配置选项( Protocol Configuration Option, PCO )进行传 输。 在本实施例中, 仅将路由规则通过 Update Bearer Request进行传输为例。
步骤 304: S-GW将路由规则通过 Update Bearer Request发送至 MME。 步骤 305 : MME 将路由规则通过下行非接入层传输 Downlink NAS transport消息发送至基站 eNB。 其中, Downlink NAS transport消息中的 NAS 消息中携带有该路由规则, 可以但不限于将该路由规则作为新增的参数存储 在 NAS消息中, 还可以存储在 NAS消息中的 PCO中。
步骤 306: eNB接收到携带路由规则的 Downlink NAS transport消息后, 直接将携带路由规则的 NAS消息发送至 UE。
步骤 307: UE在接收到更新的路由规则后, 对该路由规则进行确认, 并 将确认后的路由规则通过 NAS消息传输给 eNB。
针对于本发明实施例提供的第一种扩展的路由规则, UE可以修改路由规 则中包括的协商指示为允许协商标识的路由规则; 针对于本方面实施例提供 的第二种扩展的路由规则, UE可以修改路由规则中包括的路由接入技术指示 为非指定值的路由规则 (非禁止路由规则)。
UE 可以根据自身的配置信息以及当前网络状态中的至少一项对上述可 以进行修改的路由规则进行修改,通常 UE将路由规则中的路由接入技术修改 为 UE选择的接入技术, 如 3GPP或 WLAN等。 对于不需要修改或不能修改 的路由规则, UE保持原路由表项不变。
UE确认完成后, 将更新的路由规则包括维持不变的路由规则与修改后的 路由规则发送给网络侧。
例如, UE接收到 10条路由规则, 并根据自身的配置修改其中的 2条路 由规则,最后 UE更新的路由规则为 8条维持不变的路由规则和 2条修改后的 路由规则, UE将这 10条更新的路由规则发送至网络侧。
UE将维持不变的路由规则发送给网络侧时,还可以将维持不变的路由规 则对应的标识返回给网络侧, 以节省网络资源。
步骤 308: eNB接收到更新的路由规则后通过上行非接入层传输 Uplink NAS Transport消息中发送至 MME。
在本发明实施例中,该更新的路由规则通过在 Uplink NAS Transport消息 中的 NAS消息中作为单独的参数进行传输或通过 NAS消息中的 PCO消息进 行传输。
步骤 309: MME接收到更新的路由规则后,通过发送承载更新响应 Update Bearer Response消息将更新的路由规则发送给 S-GW。
步骤 310 : S-GW 将接收到的更新的路由规则再通过 Update Bearer Response发给 PGW。
步骤 311 : P-GW发送 IP-CAN Session Modification消息给 hPCRF,将与 UE协商后的路由信息即 UE更新的路由规则发送给 hPCRF。
步骤 312: P-GW在后续的工作中, 基于 UE确认后的更新的路由规则发 起后续的承载新建流程、 承载更新流程或承载删除流程。
如对于某条数据流,更新的路由规则指示其在 3GPP侧传输,而当前 3GPP 侧没有任何承载可以用来传输上述数据流,则 P-GW在 3GPP侧发起承载资源 新建或承载资源更新流程, 即发送承载新建请求 Create Bearer Request消息或 Update Bearer Request给 S-GW、 MME进行新建或修改专有承载, 具体操作 同现有流程, 在此处不再赘述。
如对于某条数据流, 更新的路由规则指示其在非 3GPP侧传输, 但当前 3GPP侧有该数据流对应的专有承载,则 P-GW首先在非 3GGP发起承载资源 新建流程或承载更新流程, 然后删除 3GPP对应的专有承载, 即发送承载删除 请求 Delete Bearer Request消息给 S-GW、 MME进行删除专有承载, 具体操 作同现有流程, 在此处不再赘述。
例 1适用于 3GPP和非 3GPP网络互通的网络架构中, 然而, 本发明实施 例也可以用于 2/3G网络与非 3GPP网络互通的架构中, 在此架构中, P-GW 生成的新的路由规则可以通过分组数据协议( Packet Data Protocol, PDP )上 下文修改请求中发送给 UE。
3GPP侧发送新的路由规则给 UE, 在这种情况下, 需要指定的信令消息进行 路由规则的传输。 例如, 若路由规则从非 3GPP 侧发送给 UE, 则需要定义 TWAN 与 UE 之间的新的消息进行交互, 如定义 WLCP NB_IFOM Request/Response消息, 并在上述消息中携带路由规则。
需要说明的是: 所有涉及到扩展的路由规则传输的流程, 其协议都需要 被扩展增强以便支持扩展的路由规则传输。
例 2, 本发明实施例还提供了另一种由网络侧发起的路由规则协商机制, 网络侧通过承载资源新建流程或承载更新流程与 UE进行路由规则协商,参阅 图 4所示, 路由规则协商具体流程为:
首先, UE从一个 3GPP网络和一个非 3GPP网络即 TWAN, 同时接入一 个 PDN连接。
步骤 401: hPCRF发起 IP-CAN Session Modification过程, 修改某些数据 流的参数, 如将某一数据流的接入技术从 3GPP改为非 3GPP, 并生成新的路 由规则。
P-GW基于 PCRF下发的规则信息(如 PCC规则等)、 本地配置信息以及 当前网络状态等至少一种信息决定新建或修改路由规则, 从而产生新的路由 规则, 并根据新的路由规则发起后续的承载新建流程、 承载更新流程: 如对 于某条数据流, P-GW生成的新的路由规则指示其在 3GPP侧传输, 而当前 3GPP侧没有任何承载可以用来传输该数据流, 则 P-GW在 3GPP侧发起承载 资源新建或承载资源更新流程, 即发送承载新建请求 Create Bearer Request消 息或承载更新请求 Update Bearer Request给 S-GW进行新建或修改专有承载。
其中, 上述承载新建流程、 承载修改更新流程可以在 3GPP侧触发, 也可 在非 3GPP侧触发, 或在 3GPP侧与非 3GPP侧同时触发, 本发明实施例对此 不做限制, 在例 2中仅以在 3GPP侧进行承载新建流程、 承载更新流程为例。
具体的, P-GW生成的新的路由规则,如上述实施例提供的第一种扩展的 路由规则或第二种扩展的路由规则。 P-GW生成的新的路由规则的数目可以为 1条也可以为多条。
步骤 402: P-GW发送 Create Bearer Request或 Update Bearer Request给 S-GW, S-GW在发送 Create Bearer Request或 Update Bearer Request给 MME。 其中, Create Bearer Request或 Update Bearer Request中携带有 P-GW生成的 新的路由规则。
具体的, Create Bearer Request或 Update Bearer Request中还携带有新建 或更新的流描述模板 ( Traffic Flow Template, TFT )信息, 其中, TFT信息中 包含相关流描述信息。
例如,若基于路由规则某数据流需要在 3GPP侧新建专有承载,则在 Create bearer Request消息中发送携带该数据流描述信息的 TFT, 该 TFT中包括: 数 据流源目的 IP地址、 源目的端口号、 使用的协议类型等至少一种参数。
又例如, 若基于路由规则某数据流需要在 3GPP侧修改专有承载, 则在 Update bearer Request消息中发送携带该数据流描述的 TFT,该 TFT中也包括: 数据流源目的 IP地址、 源目的端口号、 使用的协议类型等至少一种参数。
在本发明实施例中, 不局限于将路由规则通过 Create Bearer Request或 Update Bearer Request 中的单独参数进行传输, 也可以将该路由规则通过 Create Bearer Request或 Update Bearer Request中的承载上下文 bearer context 进行传输, 还可以通过 Create Bearer Request或 Update Bearer Request中的协 议配置选项 (Protocol Configuration Option, PCO ) 消息进行传输。 在本实施 例中, 仅将路由规则通过 Update Bearer Request进行传输为例。
步骤 403 : MME 将路由规则通过下行非接入层传输 Downlink NAS transport消息发送至 eNB。
具体的, MME通过 Downlink NAS transport消息中的 NAS消息传输路由 规则,其中, Downlink NAS transport消息中的 NAS消息中携带有该路由规则, 可以但不限于将该路由规则作为新增的参数存储在 NAS消息中, 还可以存储 在 NAS消息中的 PCO中。
其中, 在发送路由规则的同时, 还发送新建或修改的 TFT。
步骤 404: eNB接收到携带路由规则的 Downlink NAS transport消息后, 将该路由规则通过 NAS消息发送至 UE。
其中, eNB在发送路由规则的同时, 还发送新建或修改的 TFT。
NAS 消息中携带有该路由规则, 可以但不限于将该路由规则作为新增的 参数存储在 N AS消息中, 还可以存储在 NAS消息中的 PCO中。
步骤 405: UE在接收到路由规则后, 对该路由规则进行确认, 确认完成 后, 将更新的路由规则通过 NAS消息发送至 eNB。
UE对接收的路由规则进行确认的过程同步骤 307, 只是针对协商指示为 允许协商标识或包括的路由接入技术指示为非指定值的路由规则进行修改, 此处不再赘述。
UE确认完成后, 将更新的路由规则包括维持不变的路由规则与修改后的 路由规则发送给网络侧。
此外, UE基于确认的路由规则决定是否接受网络侧发起的承载新建流程 或 ^载更新流程。
例如, 若网络侧发起的承载新建流程或承载更新流程对应的数据流的特 征与路由规则中不可被修改的路由规则中的流描述信息相匹配,则 UE接受承 载新建流程或承载更新; 否则, UE可以拒绝上述承载新建流程或承载更新请 求。 UE选择非 3GPP作为承载新建流程或承载更新流程中对应数据流的传输 通道时, UE携带特殊原因值指示网络侧拒绝承载新建流程与承载更新流程, 上述特殊原因值可以为 UE refuses (现有原因值)、 IP traffic remove、 N3GPP preferred等, 对此本发明实施例不做限制。
步骤 406: eNB接收到更新的路由规则后通过上行非接入层传输 Uplink NAS Transport消息中发送至 MME。
在本发明实施例中, 该更新的路由规则不仅可以在 NAS消息中作为单独 的参数进行传输, 还可以通过 PCO消息进行传输。
步骤 407: MME接收到更新的路由规则后,通过发送承载新建响应 Create Bearer Response或 载更新响应 Update Bearer Response发送给 S-GW/P-GW。
其中, 上述 Create Bearer Response或 Update Bearer Response消息中不仅 携带 UE确认后的路由规则,还包括消息处理结果, 即承载新建流程或承载更 新流程是否被 UE接受。若 UE拒绝承载新建流程或承载更新流程, 则 MME, S-GW与 P-GW还需要基于 UE指示的原因值删除新建承载或恢复被修改的承 载资源, 具体操作同现有流程, 在本实施例中将不再赘述。
例 2与例 1的网络架构相同,均为 3GPP和非 3GPP网络互通的网络架构, 然而, 本发明实施例也可以用于 2/3G网络与非 3GPP网络互通的架构中, 在 此架构中, P-GW 生成的新的路由规则可以通过分组数据协议( Packet Data Protocol, PDP )上下文修改请求中发送给 UE。
3GPP侧发送新的路由规则给 UE, 在这种情况下, 需要指定的信令消息进行 路由规则的传输。 例如, 若将新的路由规则从非 3GPP侧发送给 UE, 则需要 定义 TWAN与 UE之间的新的消息进行交互, 如定义 WLCP Create Bearer Request/ Response或 WLCP Update Bearer Request/Response消息,并在上述消 息中携带路由规则。
需要说明的是: 所有涉及到扩展的路由规则传输的流程, 其协议都需要 被扩展增强以便支持扩展的路由规则传输。
例 3, 本发明实施例还提供了一种由 UE发起的分流策略协商机制, UE 通过承载资源更新流程与网络侧进行分流策略协商, 参阅图 5 所示, 分流策 略协商具体流程为:
首先, UE从一个 3GPP网络和一个非 3GPP网络同时接入一个 PDN连接。 步骤 501: UE根据自身的配置信息以及当前网络状态中的至少一项生成 新的路由规则和缺省接入指示至少一项; UE发送承载资源修改请求 Request Bearer Resource Modification消息至 eNB。
UE发起的分流策略协商过程可以在 3GPP侧进行, 或者在非 3GPP侧进 行, 或 3GPP侧和非 3GPP侧同时进行, 本发明实施例对此不做限制, 在本实 施例中仅以在 3GPP侧发起为例。
具体的, UE生成的新的路由规则, 如上述实施例提供的第一种扩展的路 由规则或第二种扩展的路由规则。 UE生成的新的路由规则的数目可以为 1条 也可以为多条。 其中, 若 UE生成的新的路由规则为第一种扩展的路由规则, 则路由规则中包含的协商指示为空;若 UE生成的新的路由规则为第二种扩展 的路由规则, 则路由规则中包含的路由接入技术优先级非指定值, 即 UE生成 的新的路由规则均为非禁止路由规则。此外,如果 UE需要更新缺省接入技术, 则 UE在 PCO中发送缺省接入技术指示给网络侧。 生成的新的分流策略,还包括流聚合描述( Traffic Aggregate Description, TAD ) 等承载资源修改信息。
在本发明实施例中, 不局限于将分流策略作为 Request Bearer Resource Modification中的 NAS消息中的单独参数进行传输, 也可以将该分流策略通 过该 NAS消息中的 PCO进行传输。
步骤 502: eNB继续通过 Request Bearer Resource Modification消息将接 收的分流策略及 TAD等承载修改信息发送至 MME。
步骤 503: MME继续通过承载资源命令 Bearer Resource Command消息 将接收到的分流策略及 TAD等承载修改信息发送至 S-GW。
步骤 504: S-GW继续通过 Bearer Resource Command消息将接收到的分 离策略及 TAD等承载修改信息发送至 P-GW。 步骤 505: P-GW接收到分流策略后, 发起 IP-CAN会话修改 IP-CAN Session Modification过程。
具体的, P-GW基于 UE生成的新的分流策略将数据流的路由信息通知 hPCRF, hPCRF决策数据流的分流策略后通知 P-GW。
步骤 506: P-GW基于 hPCRF下发的规则信息 (如计费策略等)、 UE发 送的指示信息、 本地配置信息以及当前网络状态等的至少一种信息对接收的 UE生成的分流策略进行确认, 并在后续发起的承载新建流程或承载更新流程 中, 将 P-GW确认后的分流策略发送至 UE。
P-GW对 UE生成的路由规则进行确认的过程中,可以对非网络侧强制执 行的路由规则, 维持不变, 不予修改, 对网络侧不支持的路由规则, 进行修 改, 修改后将该路由规则设置为禁止路由规则, 例如, 若该路由规则为第一 种扩展的路由规则, 则 P-GW将该路由规则的协商指示设为禁止协商标识; 若该路由规则为第二种扩展的路由规则, 则 P-GW将该路由规则的路由接入 技术指示设置为指定值, 即排除网络侧不允许某种接入技术传输某数据流之 外, 其他路由策略与 UE请求的路由策略保持一致。
P-GW对 UE生成的缺省接入指示进行确认的过程中, P-GW判定接收的 规则信息、 本地配置信息以及当前网络状态中的至少一项与所述缺省接入指 示不匹配时, 对缺省接入指示进行修改, 将修改后的缺省接入指示作为确认 后的缺省接入指示; 否则, 不对该缺省接入指示进行修改, 将未修改的缺省 接入指示作为确认后的缺省接入指示。
步骤 507: P-GW指示 IP-CAN Session Modification过程结束。
例 3与例 1、 例 2的网络架构相同, 均为 3GPP和非 3GPP网络互通的网 络架构, 然而, 本发明实施例也可以用于 2/3G网络与非 3GPP网络互通的架 构中, 在此架构中, P-GW确认的分流策略可以通过 PDP上下文修改请求中 发送给 UE。
需要说明的是: 所有涉及到扩展的路由规则传输的流程, 其协议都需要 被扩展增强以便支持扩展的路由规则传输。 例 4, 本发明实施例还提供了一种由 UE发起的路由规则协商机制, UE 通过在 3GPP侧的 PDN连接建立流程与网络侧进行缺省接入指示协商, 参阅 图 6所示, 缺省接入指示协商具体流程为:
UE开始在 3GPP侧发起 PDN连接建立流程, 此时, UE在非 3GPP侧可 以已经建立了该 PDN连接, 或者 UE未在非 3GPP侧建立 PDN连接, 在本发 明是实例中, 对此没有限制。
步骤 601 : UE根据自身的配置信息生成缺省接入指示; UE发起 3GPP侧 的 PDN连接建立流程,向 MME发送 PDN连接请求 PDN Connectivity Request, 其中, PDN Connectivity Request消息中包含的 PCO中携带有 UE生成的缺省 接入指示。
具体的, UE生成的缺省路由指示表示当业务流没有匹配上任何路由规则 时使用该缺省接入指示的路由接入技术传输。
步骤 602: MME接收到 UE发送的 PDN Connectivity Request后,向 S-GW 发送携带缺省接入指示的会话新建请求 Create Session Request。
步骤 603: S-GW向 P-GW继续发送携带缺省接入指示的 Create Session Request。
步骤 604: 在 P-GW和 PCRF之间的 IP-CAN会话建立 IP-CAN Session Establishment流程中, PCRF将数据流对应的路由策略信息发送给 P-GW。
步骤 605: P-GW基于 PCRF下发的规则信息(如计费策略等)、 UE发送 的指示信息、本地配置信息以及当前网络状态等至少一种信息对接收的 UE生 成缺省接入指示进行确认, 并发送会话新建响应 Create Session Response, 将 P-GW确认后的缺省接入指示发送至 S-GW。
在本实施例中, P-GW 确认后的路由规则不仅可以通过 Create Session Response 进行传输, 还可以通过 PDN Connectivity Accept、 Create Bearer Request、 Bearer Setup Request, N AS消息等。
步骤 606: S-GW继续发送 Create Session Response,将 P-GW确认后的缺 省接入指示发送至 MME。 步骤 607: MME通过 NAS消息将含有缺省接入指示的 PCO发送给 UE。 步骤 609: UE接收到网络侧发送的确认后的缺省接入指示。
具体的, 在传输缺省接入指示时, 均是通过携带 PCO的消息将该缺省接 入指示, 即传输缺省接入指示的所有信息均包含 PCO, 其中 PCO中携带该缺 省接入指示。
例 5, 本发明实施例还提供了一种由 UE发起的缺省接入指示协商机制, UE通过在非 3GPP侧的 PDN连接建立流程与网络侧进行缺省接入指示协商, 参阅图 7所示, 缺省接入指示协商具体流程为:
步骤 701: UE根据自身的配置信息以及当前网络状态中的至少一项生成 缺省接入指示; UE在非 3GPP网络中如 WLAN侧发起 PDN连接建立流程, 同现有技术, 即 UE 向 TWAG 发送 WLCP PDN 连接请求 WLCP PDN Connection Request, 其中, 该 WLCP PDN Connection Request请求中携带有 UE生成的缺省接入指示,或者, UE向 ePDG发送 IKEv2消息,其中该 IKEv2 消息中携带 UE生成的缺省接入指示。
步骤 702: TWAG或 ePDG向 P-GW发送携带有缺省接入指示的会话新建 请求 Create Session Request。
步骤 703: 在 P-GW和 hPCRF之间的 IP-CAN会话建立 IP-CAN Session Establishment流程中, hPCRF将数据流对应的路由策略信息发送给 P-GW。
步骤 704: P-GW和 HSS之间进行更新 PDN网关地址。
步骤 705: P-GW基于 hPCRF下发的规则信息 (如计费策略等)、 UE发 送的指示信息、本地配置信息以及当前网络状态等至少一种信息对接收的 UE 生成的缺省接入指示进行确认,并发送会话新建响应 Create Session Response, 将 P-GW确认后的缺省接入指示发送至 TWAG或 ePDG。
P-GW还可以发起承载新建流程或承载更新流程将确认后的缺省接入指 示发送至 UE。
具体的, P-GW对 UE生成的缺省接入指示进行确认的过程中, 可以对非 网络侧强制执行的缺省接入指示, 维持不变, 不予修改, 对网络侧不支持的 缺省接入指示, 进行修改。
步骤 706: 建立 TWAG/ePDG和 P-GW之间的 GPRS 隧道协议( GPRS Tunnel Protocol ) GTP隧道。
步骤 707: TWAG将 P-GW发送的确认后的缺省接入指示通过 WLCP PDN 连接响应 WLCP DPN Connection Response消息给 UE, 或者, ePDG将 P-GW 发送的确认后的缺省接入指示通过 IKEv2发送给 UE。
具体的, 在传输缺省接入指示时, 除 IKEv2消息之外的传输缺省接入指 示的消息中, 均是通过携带 PCO的消息将该缺省接入指示, 即传输缺省接入 指示的所有信息均包含 PCO, 其中 PCO 中携带该缺省接入指示。 在 IKEV2 消息中, 缺省接入指示作为新增参数传递。
基于上述实施例, 参阅图 8所示, 本发明实施例还提供了一种分流策略 协商装置, 该装置包括: 发送单元 801和接收单元 802, 其中,
发送单元 801, 用于将分流策略发送至第二设备, 其中, 分流策略包括以 下至少一项: 缺省接入指示和至少一条路由规则;
接收单元 802,用于接收并存储第二设备针对分流策略返回的确认后的分 流策略, 基于确认后的分流策略进行数据流传输。
可选的, 分流策略协商装置为核心网设备或者用户设备 UE。
可选的, 分流策略协商装置还包括:
生成单元 800, 用于在发送单元 801将分流策略发送至第二设备之前, 生 成分流策略, 生成单元 800具体用于:
当分流策略协商装置为核心网设备时, 生成单元 800根据接收的规则信 息、 UE发送的指示信息、 本地配置信息以及当前网络状态中的至少一项生成 至少一条路由规则作为分流策略; 或者
当分流策略协商装置为 UE时,生成单元 800根据自身的配置信息以及当 前网络状态中的至少一项生成至少一条路由规则和缺省接入指示中的至少一 项, 作为分流策略。
可选的, 路由规则包括: 路由接入技术、 流描述信息、 协商指示以及第 一路由规则标识信息, 其中, 第一路由规则标识信息为规则名称、 规则优先 级中的至少一项; 或者
路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示以及第 二路由规则标识信息, 其中, 第二路由规则标识信息为规则名称以及规则优 先级中的至少一项。
可选的, 当路由规则包括: 路由接入技术、 流描述信息、 协商指示以及 第一路由规则标识信息时,协商指示用来标识 UE对路由规则的修改权限,取 值为允许协商标识或者禁止协商标识, 当协商指示取值为允许协商标识时, 表示 UE选择该路由规则中的路由接入技术或者其它接入技术;当协商指示取 值为禁止协商标识时, 表示 UE选择该路由规则中的路由接入技术; 或者, 当路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示以及 第二路由规则标识信息时, 路由接入技术指示用来标识对路由规则中的路由 接入技术的使用权限, 取值为禁止值或者允许值, 当路由接入技术指示取值 为禁止值时, 表示禁止使用路由规则中的路由接入技术; 或者, 当路由接入 技术指示取值为允许值时, 表示允许使用路由规则中的路由接入技术。
可选的, 当协商指示取值为禁止协商标识时, 表示协商指示所属的路由 规则为禁止协商的路由规则; 或者,
当路由接入技术指示取值为禁止值时, 表示路由接入技术指示所属的路 由规则为禁止协商的路由规则。
可选的, 路由接入技术指示为禁止值对应的路由规则的规则优先级高于 路由接入技术指示为允许值对应的路由规则的规则优先级。
可选的, 当分流策略协商装置为 UE时, 路由规则中的协商指示为空; 或 者
路由规则中包含的路由接入技术指示等于允许值。
可选的, 当分流策略协商装置为核心网设备时,发送单元 801,具体用于: 发送单元 801 将路由规则携带于承载更新请求或承载新建请求中传输至 移动管理实体 MME, 以使 MME接收到路由规则后, 将路由规则携带于非接 入层 NAS消息中传输至第二设备; 或者
发送单元 801 将路由规则携带于承载更新请求或承载新建请求中传输至 可信接入网关 TWAG, 以使 TWAG接收到路由规则后, 将路由规则携带于指 定的无线局域网控制面协议 WLCP消息中传输至第二设备; 或者
发送单元 801 将路由规则携带于承载更新请求或承载新建请求中传输至 非可信接入网关 ePDG, 以使 ePDG接收到路由规则后, 将路由规则携带于网 络密钥协商协议 IKEv2消息中传输至第二设备; 或者
发送单元 801将路由规则携带于分组数据协议 PDP上下文修改请求或者 PDP新建请求中发送至第二设备。
可选的, 发送单元 801 在将路由规则携带于承载更新请求或承载新建请 求中传输时, 具体用于:
发送单元 801 将路由规则作为新的参数添加至承载更新请求或承载新建 请求中传输; 或者
发送单元 801 将路由规则添加至承载更新请求或承载新建请求中的承载 上下文中传输; 或者
发送单元 801 将路由规则添加至承载更新请求或承载新建请求中的协议 配置选项 PCO中传输。
可选的, 发送单元 801使 MME将路由规则携带于非接入层 NAS消息中 传输时, 具体用于:
发送单元 801使 MME将路由规则作为新的参数添加至 NAS消息中传输; 或者
发送单元 801使 MME将路由规则添加至 NAS消息中的 PCO中传输。 可选的, 当分流策略协商装置为 UE时, 发送单元 801, 具体用于: 当分流策略包括路由规则时, 发送单元 801将分流策略携带于 NAS消息 中发送至 MME, 以使 MME接收到分流策略后, 将分流策略携带于承载资源 命令中发送第二设备; 或者
当分流策略为缺省接入指示时,发送单元 801将缺省接入指示携带于 NAS 消息中发送至 MME, 以使 MME接收到缺省接入指示后, 将缺省接入指示携 带于会话新建请求中发送至第二设备; 或者, 发送单元 801 将缺省接入指示 携带于 WLCP分组数据网 PDN连接请求中发送至 TWAG, 以使 TWAG接收 到缺省接入指示后, 将缺省接入指示携带于会话新建请求中发送至第二设备; 或者, 发送单元 801将缺省接入指示携带于网络密钥协商协议 IKEv2消息中 发送至非可信接入网关 ePDG, 以使 ePDG接收到缺省接入指示后, 将缺省接 入指示携带于会话新建请求中发送至第二设备。
可选的, 当分流策略包括路由规则, 发送单元 801 在将分流策略携带于 NAS消息中发送时, 具体用于:
发送单元 801将分流策略作为新的参数添加至 NAS消息中发送; 或者 发送单元 801将分流策略添加至 NAS消息中的 PCO中发送。
可选的, 当分流策略为缺省接入指示, 发送单元 801 在将缺省接入指示 携带于 NAS消息或者 WLCP PDN连接请求中发送时, 具体用于:
发送单元 801将缺省接入指示添加至 NAS消息或者 WLCP PDN连接请 求中的 PCO中发送; 或者
当分流策略为缺省接入指示时, 发送单元 801使 MME或 TWAG将缺省 接入指示携带于会话新建请求中发送时, 具体用于:
发送单元 801使 MME或 TWAG将缺省接入指示添加至会话新建请求中 的 PCO中发送; 或者
当分流策略为缺省接入指示时, 发送单元 801 将缺省接入指示携带于 IKEv2消息中发送时, 具体用于:
发送单元 801将缺省接入指示作为新的参数添加至 IKEv2消息中发送。 可选的, 当分流策略协商装置为核心网设备时,接收单元 802,具体用于: 若第二设备根据自身的配置信息以及当前网络状态中的至少一项对接收 的路由规则中至少一条路由规则进行修改, 则接收单元 802接收第二设备发 送的路由规则中未修改的其它路由规则以及对至少一条路由规则进行修改后 的更新的路由规则; 或者 若第二设备未对接收的路由规则进行修改, 则接收单元 802接收未修改 的路由规则。
可选的, 第二设备修改的至少一条路由规则中包含的协商指示为允许协 商标识; 或者
第二设备修改的至少一条路由规则中包含的路由接入技术指示等于允许 值。
可选的, 接收单元 802, 还用于:
接收第二设备基于确认后的分流策略产生的承载更新流程或承载新建修 改流程的确定结果。
可选的, 当分流策略协商装置为 UE时, 接收单元 802, 具体用于: 接收单元 802接收第二设备返回的确认后的路由规则和确认后的缺省接 入指示中的至少一项;
其中, 接收单元 802在接收第二设备返回的确认后的缺省接入指示时, 具体用于:
若第二设备根据接收的规则信息、 UE发送的指示信息、 本地配置信息以 及当前网络状态中的至少一项对接收的缺省接入指示进行修改, 则接收单元 802接收第二设备返回的修改后的缺省接入指示; 或者
若第二设备未对缺省接入指示进行修改, 则接收单元 802接收第二设备 返回的未修改的缺省接入指示;
接收单元 802在接收第二设备返回的确认后的路由规则时, 具体用于: 若第二设备根据接收的规则信息、 UE发送的指示信息、 本地配置信息以 及当前网络状态中的至少一项对接收的路由规则中至少一条路由规则进行修 改, 则接收单元 802接收第二设备发送的路由规则中未修改的其它路由规则 以及对至少一条路由规则进行修改后的更新的路由规则; 或者
若第二设备未对接收的路由规则进行修改, 则接收单元 802接收的未修 改的路由规则。
可选的, 对至少一条路由规则进行修改后的更新的路由规则中包含的协 商指示为禁止协商标识; 或者
对至少一条路由规则进行修改后的更新的路由规则中包含的路由接入技 术指示为禁止值。
基于上述实施例, 参阅图 9所示, 本发明实施例还提供了一种分流策略 协商装置, 该装置包括: 确认单元 901和处理单元 902, 其中,
确认单元 901, 用于接收第一设备发送的分流策略, 并对分流策略进行确 认, 其中, 分流策略包括以下至少一项: 缺省接入指示和至少一条路由规则; 处理单元 902, 用于存储确认后的分流策略, 并将确认后的分流策略返回 至第一设备, 基于确认后的分流策略进行数据流传输。
可选的, 分流策略协商装置为用户设备 UE或者核心网设备。
可选的, 当分流策略协商装置为 UE时, 分流策略为第一设备发送的至少 一条路由规则; 或者
当分流策略协商装置为核心网设备时, 分流策略为第一设备发送的至少 一条路由规则和缺省接入指示中的至少一项。
可选的, 第一设备发送的路由规则中包括: 路由接入技术、 流描述信息、 协商指示以及第一路由规则标识信息, 其中, 第一路由规则标识信息为规则 名称、 规则优先级中的至少一项; 或者
第一设备发送的路由规则中包括: 路由接入技术、 流描述信息、 路由接 入技术指示以及第二路由规则标识信息, 其中, 第二路由规则标识信息为规 则名称以及规则优先级中的至少一项。
可选的, 当路由规则包括: 路由接入技术、 流描述信息、 协商指示以及 第一路由规则标识信息时,协商指示用来标识 UE对路由规则的修改权限,取 值为允许协商标识或者禁止协商标识, 当协商指示取值为允许协商标识时, 表示 UE选择该路由规则中的路由接入技术或者其它接入技术;当协商指示取 值为禁止协商标识时, 表示 UE选择该路由规则中的路由接入技术; 或者, 当路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示以及 第二路由规则标识信息时, 路由接入技术指示用来标识对路由规则中的路由 接入技术的使用权限, 取值为禁止值或者允许值, 当路由接入技术指示取值 为禁止值时, 表示禁止使用路由规则中的路由接入技术; 或者, 当路由接入 技术指示取值为允许值时, 表示允许使用路由规则中的路由接入技术。
可选的, 当协商指示取值为禁止协商标识时, 表示协商指示所属的路由 规则为禁止协商的路由规则; 或者,
当路由接入技术指示取值为禁止值时, 表示路由接入技术指示所属的路 由规则为禁止协商的路由规则。
可选的, 路由接入技术指示为禁止值对应的路由规则的规则优先级高于 路由接入技术指示为允许值对应的路由规则的规则优先级。
可选的, 当第一设备为 UE时, 第一设备发送的路由规则中的协商指示为 空; 或者
第一设备发送的路由规则中的路由接入技术指示等于允许值。
可选的, 当分流策略协商装置为 UE时, 确认单元 901, 用于:
对路由规则进行确认;
确认单元 901对路由规则进行确认时, 具体用于:
确认单元 901 判定自身的配置信息以及当前网络状态中的至少一项与路 由规则中至少一条路由规则不匹配, 且至少一条路由规则不是禁止协商的路 由规则时, 对至少一条路由规则进行修改, 并生成修改后的更新的路由规则, 将路由规则中未修改的其它路由规则以及对至少一条路由规则进行修改后的 更新的路由规则作为确认后的路由规则; 或者
确认单元 901 判定自身的配置信息以及当前网络状态中的至少一项与路 由规则中所有路由规则匹配, 或者自身的配置信息以及当前网络状态中的至 少一项与路由规则中不匹配的路由规则为禁止协商的路由规则时, 不对路由 规则进行修改, 将未修改的路由规则作为确认后的路由规则。
可选的, 当分流策略协商装置为核心网设备时, 确认单元 901, 用于: 对分流策略中的缺省接入指示进行确认, 和 /或, 对分流策略中的路由规 则进行确认; 其中, 确认单元 901对缺省接入指示进行确认时, 具体用于: 确认单元 901判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态中的至少一项与缺省接入指示不匹配时, 对缺省接入指示 进行修改, 将修改后的缺省接入指示作为确认后的缺省接入指示; 或者
确认单元 901判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态与缺省接入指示匹配时, 不对缺省接入指示进行修改, 将 未修改的缺省接入指示作为确认后的缺省接入指示;
确认单元 901对路由规则进行确认时, 具体用于:
确认单元 901判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态中的至少一项与路由规则中至少一条路由规则不匹配时, 对至少一条路由规则进行修改, 并生成修改后的更新的路由规则, 将路由规 则中未修改的其它路由规则以及对至少一条路由规则进行修改后的更新的路 由规则作为确认后的路由规则; 或者
确认单元 901判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态与路由规则中所有路由规则匹配时, 不对路由规则进行修 改, 将未修改的路由规则作为确认后的路由规则。
可选的, 确认单元 901对至少一条路由规则进行修改时, 具体用于: 确认单元 901对至少一条路由规则中包含的路由接入技术进行修改, 并 在至少一条路由规则中包含协商指示时, 将至少一条路由规则中包含的 协商指示设置为禁止协商标识; 在至少一条路由规则包含路由接入技术指示 时, 将至少一条路由规则中包含的路由接入技术指示设置为禁止值。
可选的, 当分流策略协商装置为 UE时, 处理单元 902, 具体用于: 处理单元 902将确认后的路由规则携带于非接入层 NAS消息中传输至移 动管理实体 MME, 以使 MME接收到确认后的路由规则后, 将确认后的路由 规则携带于承载更新响应或承载新建响应中传输至第一设备; 或者
处理单元 902将确认后的路由规则携带于指定的无线局域网控制面协议 WLCP消息中传输至可信接入网关 TWAG, 以使 TWAG接收到确认后的路由 规则后, 将确认后的路由规则携带于承载更新响应或承载新建响应中传输至 第一设备; 或者
处理单元 902将确认后的路由规则携带于网络密钥协商协议 IKEv2消息 中传输至非可信接入网关 ePDG, 以使 ePDG接收到确认后的路由规则后, 将 确认后的路由规则携带于承载更新响应或承载新建响应中传输至第一设备。
可选的, 处理单元 902将确认后的路由规则携带于 NAS 消息中传输至 MME时, 具体用于:
处理单元 902将确认后的路由规则作为新的参数添加至 NAS消息中传输 至 MME; 或者
处理单元 902将确认后的路由规则添加至 NAS 消息中的协议配置选项 PCO中传输至 MME。
可选的, 处理单元 902使 MME、 TWAG或者 ePDG将确认后的路由规则 携带于承载更新响应或承载新建响应中传输至第一设备时, 具体用于:
处理单元 902使 MME、 TWAG或者 ePDG将确认后的路由规则作为新的 参数添加至承载更新响应或承载新建响应中传输至第一设备; 或者
处理单元 902使 MME、 TWAG或者 ePDG将确认后的路由规则添加至承 载更新响应或承载新建响应中的承载上下文中传输至第一设备; 或者
处理单元 902使 MME、 TWAG或者 ePDG将确认后的路由规则添加至承 载更新响应或 7 载新建响应中的 PCO中传输至第一设备。
可选的, 处理单元 902, 还用于:
发送分流策略协商装置基于确认后的分流策略产生的承载更新流程或承 载新建修改流程的确定结果。
可选的, 当分流策略协商装置为核心网设备时,处理单元 902,具体用于: 当确认后的分流策略包括确认后的路由规则时, 处理单元 902通过将确 认后的分流策略携带于承载更新请求或承载新建请求中传输至 MME; 以使 MME接收到确认后的分流策略后, 将确认后的分流策略携带于 NAS消息中 传输至第一设备; 或者, 处理单元 902将确认后的分流策略携带于分组数据 协议 PDP上下文修改请求或者 PDP上下文新建请求中发送至第一设备;或者 当确认后的分流策略为确认后的缺省接入指示时, 处理单元 902将确认 后的缺省接入指示携带于会话新建响应中发送至 MME, 以使 MME接收到确 认后的缺省接入指示后, 将确认后的缺省接入指示携带于 NAS消息中发送至 第一设备; 或者, 处理单元 902将确认后的缺省接入指示携带于会话新建响 应中发送至可信接入网关 TWAG, 以使 TWAG接收到确认后的缺省接入指示 后, 将确认后的缺省接入指示携带于无线局域网控制面协议 WLCP分组数据 网 PDN连接响应中发送至第一设备; 或者, 处理单元 902将确认后的缺省接 入指示携带于会话新建响应中发送至非可信接入网关 ePDG, 以使 ePDG接收 到确认后的缺省接入指示, 将确认后的缺省接入指示携带于网络密钥协商协 议 IKEv2消息中发送至第一设备。
可选的, 当确认后的分流策略包括确认后的路由规则, 处理单元 902使 MME将确认后的分流策略携带于 NAS消息中传输至第一设备时,具体用于: 处理单元 902使 MME将确认后的分流策略作为新的参数添加至 NAS消 息中传输至第一设备; 或者
处理单元 902使 MME将确认后的分流策略添加至 NAS消息中的 PCO中 传输至第一设备。
可选的, 当确认后的分流策略为确认后的缺省接入指示, 处理单元 902 将确认后的缺省接入指示携带于会话新建响应中发送时, 具体用于:
处理单元 902将确认后的缺省接入指示添加至会话新建响应中的 PCO中 发送;
当确认后的分流策略为确认后的缺省接入指示, 处理单元 902使 MME 将确认后的缺省接入指示携带于 NAS消息中发送时, 具体用于:
处理单元 902使 MME将确认后的缺省接入指示添加至 NAS 消息中的 PCO中发送;
当确认后的分流策略为确认后的缺省接入指示, 处理单元 902使 TWAG 将确认后的缺省接入指示携带于 WLCP PDN连接响应中发送时, 具体用于: 处理单元 902使 TWAG将确认后的缺省接入指示添加至 WLCP PDN连接 响应中的 PCO中发送;
当确认后的分流策略为确认后的缺省接入指示时,处理单元 902使 ePDG 将确认后的缺省接入指示携带于 IKEv2消息中发送时, 具体用于:
处理单元 902使 ePDG将确认后缺省接入指示作为新的参数添加至 IKEv2 消息中发送。
基于上述实施例, 参阅图 10所示, 本发明实施例还提供了一种分流策略 协商设备, 该设备包括: 收发器 1001、 存储器 1002和处理器 1003, 其中, 收发器 1001, 用于将分流策略发送至第二设备, 其中, 分流策略包括以 下至少一项: 缺省接入指示和至少一条路由规则; 接收第二设备针对分流策 略返回的确认后的分流策略;
存储器 1002,用于存储第二设备针对分流策略返回的确认后的分流策略; 以及存储程序。
处理器 1003,用于根据存储器 1002中存储的第二设备针对分流策略返回 的确认后的分流策略进行数据流传输, 以及执行存储器 1002所存放的程序。
可选的, 分流策略协商设备为核心网设备或者用户设备 UE。
处理器 1003, 用于在收发器 1001将分流策略发送至第二设备之前, 生成 分流策略, 处理器 1003具体用于:
当分流策略协商设备为核心网设备时, 生成单元 800根据接收的规则信 息、 UE发送的指示信息、 本地配置信息以及当前网络状态中的至少一项生成 至少一条路由规则作为分流策略; 或者
当分流策略协商设备为 UE时,生成单元 800根据自身的配置信息以及当 前网络状态中的至少一项生成至少一条路由规则和缺省接入指示中的至少一 项, 作为分流策略。
可选的, 路由规则包括: 路由接入技术、 流描述信息、 协商指示以及第 一路由规则标识信息, 其中, 第一路由规则标识信息为规则名称、 规则优先 级中的至少一项; 或者 路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示以及第 二路由规则标识信息, 其中, 第二路由规则标识信息为规则名称以及规则优 先级中的至少一项。
可选的, 当路由规则包括: 路由接入技术、 流描述信息、 协商指示以及 第一路由规则标识信息时,协商指示用来标识 UE对路由规则的修改权限,取 值为允许协商标识或者禁止协商标识, 当协商指示取值为允许协商标识时, 表示 UE选择该路由规则中的路由接入技术或者其它接入技术;当协商指示取 值为禁止协商标识时, 表示 UE选择该路由规则中的路由接入技术; 或者, 当路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示以及 第二路由规则标识信息时, 路由接入技术指示用来标识对路由规则中的路由 接入技术的使用权限, 取值为禁止值或者允许值, 当路由接入技术指示取值 为禁止值时, 表示禁止使用路由规则中的路由接入技术; 或者, 当路由接入 技术指示取值为允许值时, 表示允许使用路由规则中的路由接入技术。
可选的, 当协商指示取值为禁止协商标识时, 表示协商指示所属的路由 规则为禁止协商的路由规则; 或者,
当路由接入技术指示取值为禁止值时, 表示路由接入技术指示所属的路 由规则为禁止协商的路由规则。
可选的, 路由接入技术指示为禁止值对应的路由规则的规则优先级高于 路由接入技术指示为允许值对应的路由规则的规则优先级。
可选的, 当分流策略协商设备为 UE时, 路由规则中的协商指示为空; 或 者
路由规则中包含的路由接入技术指示等于允许值。
可选的, 当分流策略协商设备为核心网设备时, 收发器 1001, 具体用于: 收发器 1001将路由规则携带于承载更新请求或承载新建请求中传输至移 动管理实体 MME, 以使 MME接收到路由规则后, 将路由规则携带于非接入 层 NAS消息中传输至第二设备; 或者
收发器 1001将路由规则携带于承载更新请求或承载新建请求中传输至可 信接入网关 TWAG, 以使 TWAG接收到路由规则后, 将路由规则携带于指定 的无线局域网控制面协议 WLCP消息中传输至第二设备; 或者
收发器 1001将路由规则携带于承载更新请求或承载新建请求中传输至非 可信接入网关 ePDG, 以使 ePDG接收到路由规则后, 将路由规则携带于网络 密钥协商协议 IKEv2消息中传输至第二设备; 或者
收发器 1001将路由规则携带于分组数据协议 PDP上下文修改请求或者 PDP新建请求中发送至第二设备。
可选的, 收发器 1001在将路由规则携带于承载更新请求或承载新建请求 中传输时, 具体用于:
收发器 1001将路由规则作为新的参数添加至承载更新请求或承载新建请 求中传输; 或者
收发器 1001将路由规则添加至承载更新请求或承载新建请求中的承载上 下文中传输; 或者
收发器 1001将路由规则添加至承载更新请求或承载新建请求中的协议配 置选项 PCO中传输。
可选的,收发器 1001使 MME将路由规则携带于非接入层 NAS消息中传 输时, 具体用于:
收发器 1001使 MME将路由规则作为新的参数添加至 NAS消息中传输; 或者
收发器 1001使 MME将路由规则添加至 NAS消息中的 PCO中传输。 可选的, 当分流策略协商设备为 UE时, 收发器 1001, 具体用于: 当分流策略包括路由规则时, 收发器 1001将分流策略携带于 NAS消息 中发送至 MME, 以使 MME接收到分流策略后, 将分流策略携带于承载资源 命令中发送第二设备; 或者
当分流策略为缺省接入指示时,收发器 1001将缺省接入指示携带于 NAS 消息中发送至 MME, 以使 MME接收到缺省接入指示后, 将缺省接入指示携 带于会话新建请求中发送至第二设备; 或者, 收发器 1001将缺省接入指示携 带于 WLCP分组数据网 PDN连接请求中发送至 TWAG, 以使 TWAG接收到 缺省接入指示后, 将缺省接入指示携带于会话新建请求中发送至第二设备; 或者,收发器 1001将缺省接入指示携带于网络密钥协商协议 IKEv2消息中发 送至非可信接入网关 ePDG, 以使 ePDG接收到缺省接入指示后, 将缺省接入 指示携带于会话新建请求中发送至第二设备。
可选的, 当分流策略包括路由规则, 收发器 1001 在将分流策略携带于
NAS消息中发送时, 具体用于:
收发器 1001将分流策略作为新的参数添加至 NAS消息中发送; 或者 收发器 1001将分流策略添加至 NAS消息中的 PCO中发送。
可选的, 当分流策略为缺省接入指示, 收发器 1001在将缺省接入指示携 带于 NAS消息或者 WLCP PDN连接请求中发送时, 具体用于:
收发器 1001将缺省接入指示添加至 NAS消息或者 WLCP PDN连接请求 中的 PCO中发送; 或者
当分流策略为缺省接入指示时,收发器 1001使 MME或 TWAG将缺省接 入指示携带于会话新建请求中发送时, 具体用于:
收发器 1001使 MME或 TWAG将缺省接入指示添加至会话新建请求中的
PCO中发送; 或者
当分流策略为缺省接入指示时, 收发器 1001 将缺省接入指示携带于
IKEv2消息中发送时, 具体用于:
收发器 1001将缺省接入指示作为新的参数添加至 IKEv2消息中发送。 可选的, 当分流策略协商设备为核心网设备时, 收发器 1001, 具体用于: 若第二设备根据自身的配置信息以及当前网络状态中的至少一项对接收 的路由规则中至少一条路由规则进行修改, 则收发器 1001接收第二设备发送 的路由规则中未修改的其它路由规则以及对至少一条路由规则进行修改后的 更新的路由规则; 或者
若第二设备未对接收的路由规则进行修改, 则收发器 1001接收未修改的 路由规则。 可选的, 第二设备修改的至少一条路由规则中包含的协商指示为允许协 商标识; 或者
第二设备修改的至少一条路由规则中包含的路由接入技术指示等于允许 值。
可选的, 收发器 1001, 还用于:
接收第二设备基于确认后的分流策略产生的承载更新流程或承载新建修 改流程的确定结果。
可选的, 当分流策略协商设备为 UE时, 收发器 1001, 具体用于: 收发器 1001接收第二设备返回的确认后的路由规则和确认后的缺省接入 指示中的至少一项;
其中, 收发器 1001在接收第二设备返回的确认后的缺省接入指示时, 具 体用于:
若第二设备根据接收的规则信息、 UE发送的指示信息、 本地配置信息以 及当前网络状态中的至少一项对接收的缺省接入指示进行修改, 则收发器 1001接收第二设备返回的修改后的缺省接入指示; 或者
若第二设备未对缺省接入指示进行修改, 则收发器 1001接收第二设备返 回的未修改的缺省接入指示;
收发器 1001在接收第二设备返回的确认后的路由规则时, 具体用于: 若第二设备根据接收的规则信息、 UE发送的指示信息、 本地配置信息以 及当前网络状态中的至少一项对接收的路由规则中至少一条路由规则进行修 改, 则收发器 1001接收第二设备发送的路由规则中未修改的其它路由规则以 及对至少一条路由规则进行修改后的更新的路由规则; 或者
若第二设备未对接收的路由规则进行修改, 则收发器 1001接收的未修改 的路由规则。
可选的, 对至少一条路由规则进行修改后的更新的路由规则中包含的协 商指示为禁止协商标识; 或者
对至少一条路由规则进行修改后的更新的路由规则中包含的路由接入技 术指示为禁止值。
基于上述实施例, 参阅图 11所示, 本发明实施例还提供了一种分流策略 协商设备, 该设备包括: 收发器 1101、 存储器 1002和处理 1003, 其中, 收发器 1101, 用于接收第一设备发送的分流策略, 并将并将确认后的分 流策略返回至第一设备, 其中, 分流策略包括以下至少一项: 缺省接入指示 和至少一条路由规则;
存储器 1102, 用于存储确认后的分流策略, 以及存储程序;
处理器 1103, 用于对分流策略进行确认, 并基于确认后的分流策略进行 数据流传输。
可选的, 分流策略协商装置为用户设备 UE或者核心网设备。
可选的, 当分流策略协商装置为 UE时, 分流策略为第一设备发送的至少 一条路由规则; 或者
当分流策略协商装置为核心网设备时, 分流策略为第一设备发送的至少 一条路由规则和缺省接入指示中的至少一项。
可选的, 第一设备发送的路由规则中包括: 路由接入技术、 流描述信息、 协商指示以及第一路由规则标识信息, 其中, 第一路由规则标识信息为规则 名称、 规则优先级中的至少一项; 或者
第一设备发送的路由规则中包括: 路由接入技术、 流描述信息、 路由接 入技术指示以及第二路由规则标识信息, 其中, 第二路由规则标识信息为规 则名称以及规则优先级中的至少一项。
可选的, 当路由规则包括: 路由接入技术、 流描述信息、 协商指示以及 第一路由规则标识信息时,协商指示用来标识 UE对路由规则的修改权限,取 值为允许协商标识或者禁止协商标识, 当协商指示取值为允许协商标识时, 表示 UE选择该路由规则中的路由接入技术或者其它接入技术;当协商指示取 值为禁止协商标识时, 表示 UE选择该路由规则中的路由接入技术; 或者, 当路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示以及 第二路由规则标识信息时, 路由接入技术指示用来标识对路由规则中的路由 接入技术的使用权限, 取值为禁止值或者允许值, 当路由接入技术指示取值 为禁止值时, 表示禁止使用路由规则中的路由接入技术; 或者, 当路由接入 技术指示取值为允许值时, 表示允许使用路由规则中的路由接入技术。
可选的, 当协商指示取值为禁止协商标识时, 表示协商指示所属的路由 规则为禁止协商的路由规则; 或者,
当路由接入技术指示取值为禁止值时, 表示路由接入技术指示所属的路 由规则为禁止协商的路由规则。
可选的, 路由接入技术指示为禁止值对应的路由规则的规则优先级高于 路由接入技术指示为允许值对应的路由规则的规则优先级。
可选的, 当第一设备为 UE时, 第一设备发送的路由规则中的协商指示为 空; 或者
第一设备发送的路由规则中的路由接入技术指示等于允许值。
可选的, 当分流策略协商装置为 UE时, 处理器 1103, 用于:
对路由规则进行确认;
处理器 1103对路由规则进行确认时, 具体用于:
处理器 1103判定自身的配置信息以及当前网络状态中的至少一项与路由 规则中至少一条路由规则不匹配, 且至少一条路由规则不是禁止协商的路由 规则时, 对至少一条路由规则进行修改, 并生成修改后的更新的路由规则, 将路由规则中未修改的其它路由规则以及对至少一条路由规则进行修改后的 更新的路由规则作为确认后的路由规则; 或者
处理器 1103判定自身的配置信息以及当前网络状态中的至少一项与路由 规则中所有路由规则匹配, 或者自身的配置信息以及当前网络状态中的至少 一项与路由规则中不匹配的路由规则为禁止协商的路由规则时, 不对路由规 则进行修改, 将未修改的路由规则作为确认后的路由规则。
可选的, 当分流策略协商装置为核心网设备时, 处理器 1103, 用于: 对分流策略中的缺省接入指示进行确认, 和 /或, 对分流策略中的路由规 则进行确认; 其中, 处理器 1103对缺省接入指示进行确认时, 具体用于: 处理器 1103判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态中的至少一项与缺省接入指示不匹配时, 对缺省接入指示 进行修改, 将修改后的缺省接入指示作为确认后的缺省接入指示; 或者
处理器 1103判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态与缺省接入指示匹配时, 不对缺省接入指示进行修改, 将 未修改的缺省接入指示作为确认后的缺省接入指示;
处理器 1103对路由规则进行确认时, 具体用于:
处理器 1103判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态中的至少一项与路由规则中至少一条路由规则不匹配时, 对至少一条路由规则进行修改, 并生成修改后的更新的路由规则, 将路由规 则中未修改的其它路由规则以及对至少一条路由规则进行修改后的更新的路 由规则作为确认后的路由规则; 或者
处理器 1103判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态与路由规则中所有路由规则匹配时, 不对路由规则进行修 改, 将未修改的路由规则作为确认后的路由规则。
可选的, 处理器 1103对至少一条路由规则进行修改时, 具体用于: 处理器 1103对至少一条路由规则中包含的路由接入技术进行修改, 并 在至少一条路由规则中包含协商指示时, 将至少一条路由规则中包含的 协商指示设置为禁止协商标识; 在至少一条路由规则包含路由接入技术指示 时, 将至少一条路由规则中包含的路由接入技术指示设置为禁止值。
可选的, 当分流策略协商装置为 UE时, 收发器 1101, 具体用于: 收发器 1101将确认后的路由规则携带于非接入层 NAS消息中传输至移 动管理实体 MME, 以使 MME接收到确认后的路由规则后, 将确认后的路由 规则携带于承载更新响应或承载新建响应中传输至第一设备; 或者
收发器 1101 将确认后的路由规则携带于指定的无线局域网控制面协议 WLCP消息中传输至可信接入网关 TWAG, 以使 TWAG接收到确认后的路由 规则后, 将确认后的路由规则携带于承载更新响应或承载新建响应中传输至 第一设备; 或者
收发器 1101将确认后的路由规则携带于网络密钥协商协议 IKEv2消息中 传输至非可信接入网关 ePDG, 以使 ePDG接收到确认后的路由规则后, 将确 认后的路由规则携带于承载更新响应或承载新建响应中传输至第一设备。
可选的, 收发器 1101 将确认后的路由规则携带于 NAS 消息中传输至 MME时, 具体用于:
收发器 1101将确认后的路由规则作为新的参数添加至 NAS消息中传输 至 MME; 或者
收发器 1101 将确认后的路由规则添加至 NAS 消息中的协议配置选项 PCO中传输至 MME。
可选的, 收发器 1101使 MME、 TWAG或者 ePDG将确认后的路由规则 携带于承载更新响应或承载新建响应中传输至第一设备时, 具体用于:
收发器 1101使 MME、 TWAG或者 ePDG将确认后的路由规则作为新的 参数添加至承载更新响应或承载新建响应中传输至第一设备; 或者
收发器 1101使 MME、 TWAG或者 ePDG将确认后的路由规则添加至承 载更新响应或承载新建响应中的承载上下文中传输至第一设备; 或者
收发器 1101使 MME、 TWAG或者 ePDG将确认后的路由规则添加至承 载更新响应或 7 载新建响应中的 PCO中传输至第一设备。
可选的, 收发器 1101, 还用于:
发送分流策略协商装置基于确认后的分流策略产生的承载更新流程或承 载新建修改流程的确定结果。
可选的, 当分流策略协商装置为核心网设备时, 收发器 1101, 具体用于: 当确认后的分流策略包括确认后的路由规则时, 收发器 1101通过将确认 后的分流策略携带于承载更新请求或承载新建请求中传输至 MME; 以使 MME接收到确认后的分流策略后, 将确认后的分流策略携带于 NAS消息中 传输至第一设备; 或者, 收发器 1101将确认后的分流策略携带于分组数据协 议 PDP上下文修改请求或者 PDP上下文新建请求中发送至第一设备; 或者 当确认后的分流策略为确认后的缺省接入指示时, 收发器 1101将确认后 的缺省接入指示携带于会话新建响应中发送至 MME, 以使 MME接收到确认 后的缺省接入指示后, 将确认后的缺省接入指示携带于 NAS消息中发送至第 一设备; 或者, 收发器 1101将确认后的缺省接入指示携带于会话新建响应中 发送至可信接入网关 TWAG, 以使 TWAG接收到确认后的缺省接入指示后, 将确认后的缺省接入指示携带于无线局域网控制面协议 WLCP 分组数据网 PDN连接响应中发送至第一设备; 或者, 收发器 1101将确认后的缺省接入指 示携带于会话新建响应中发送至非可信接入网关 ePDG, 以使 ePDG接收到确 认后的缺省接入指示, 将确认后的缺省接入指示携带于网络密钥协商协议 IKEv2消息中发送至第一设备。
可选的, 当确认后的分流策略包括确认后的路由规则, 收发器 1101 使 MME将确认后的分流策略携带于 NAS消息中传输至第一设备时,具体用于: 收发器 1101使 MME将确认后的分流策略作为新的参数添加至 NAS消息 中传输至第一设备; 或者
收发器 1101使 MME将确认后的分流策略添加至 NAS消息中的 PCO中 传输至第一设备。
可选的, 当确认后的分流策略为确认后的缺省接入指示, 收发器 1101将 确认后的缺省接入指示携带于会话新建响应中发送时, 具体用于:
收发器 1101将确认后的缺省接入指示添加至会话新建响应中的 PCO中 发送;
当确认后的分流策略为确认后的缺省接入指示, 收发器 1101使 MME将 确认后的缺省接入指示携带于 NAS消息中发送时, 具体用于:
收发器 1101使 MME将确认后的缺省接入指示添加至 NAS消息中的 PCO 中发送;
当确认后的分流策略为确认后的缺省接入指示,收发器 1101使 TWAG将 确认后的缺省接入指示携带于 WLCP PDN连接响应中发送时, 具体用于: 收发器 1101使 TWAG将确认后的缺省接入指示添加至 WLCP PDN连接 响应中的 PCO中发送;
当确认后的分流策略为确认后的缺省接入指示时, 收发器 1101使 ePDG 将确认后的缺省接入指示携带于 IKEv2消息中发送时, 具体用于:
收发器 1101使 ePDG将确认后缺省接入指示作为新的参数添加至 IKEv2 消息中发送。
综上所述, 通过本发明实施例中提供的一种分流策略协商方法及装置, 该方法为: 第一设备发送分流策略至第二设备, 其中, 该分流策略中包括缺 省接入指示和路由规则; 第一设备接收并存储第二设备针对该分流策略返回 的确认后的分流策略, 基于该确认后的分流策略进行数据流传输。 这样, 在 更新数据流分流策略时,可以通过网络侧和 UE的协商,获取一个两侧都可以 接受的路由规则,提高了数据流传输效率,解决了现有技术中 UE发起的数据 流切换的方法适用性较低,且网络侧无法对 UE进行控制管理, 降低用户体验 的问题。
本领域内的技术人员应明白, 本发明的实施例可提供为方法、 系统、 或 计算机程序产品。 因此, 本发明可釆用完全硬件实施例、 完全软件实施例、 或结合软件和硬件方面的实施例的形式。 而且, 本发明可釆用在一个或多个 其中包含有计算机可用程序代码的计算机可用存储介质 (包括但不限于磁盘 存储器、 CD-ROM、 光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、 设备(系统)、 和计算机程序产 品的流程图和 /或方框图来描述的。 应理解可由计算机程序指令实现流程图 和 /或方框图中的每一流程和 /或方框、 以及流程图和 /或方框图中的流程 和 /或方框的结合。 可提供这些计算机程序指令到通用计算机、 专用计算机、 嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器, 使得通 过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流 程图一个流程或多个流程和 /或方框图一个方框或多个方框中指定的功能的 装置。 这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设 备以特定方式工作的计算机可读存储器中, 使得存储在该计算机可读存储器 中的指令产生包括指令装置的制造品, 该指令装置实现在流程图一个流程或 多个流程和 /或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上, 使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的 处理, 从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图 一个流程或多个流程和 /或方框图一个方框或多个方框中指定的功能的步 骤。
尽管已描述了本发明的优选实施例, 但本领域内的技术人员一旦得知了 基本创造性概念, 则可对这些实施例作出另外的变更和修改。 所以, 所附权 利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和修改。 脱离本发明实施例的精神和范围。 这样, 倘若本发明实施例的这些修改和变 型属于本发明权利要求及其等同技术的范围之内, 则本发明也意图包含这些 改动和变型在内。

Claims

权 利 要 求
1、 一种分流策略协商方法, 其特征在于, 包括:
第一设备将分流策略发送至第二设备, 其中, 所述分流策略包括以下至 少一项: 缺省接入指示和至少一条路由规则;
所述第一设备接收并存储所述第二设备针对所述分流策略返回的确认后 的分流策略, 基于所述确认后的分流策略进行数据流传输。
2、 如权利要求 1所述的方法, 其特征在于, 所述第一设备为核心网设备 或者用户设备 UE。
3、 如权利要求 2所述的方法, 其特征在于, 所述第一设备将分流策略发 送至第二设备之前, 还包括:
所述第一设备生成分流策略, 具体包括:
当所述第一设备为核心网设备时, 所述第一设备根据接收的规则信息、 UE发送的指示信息、本地配置信息以及当前网络状态中的至少一项生成至少 一条路由规则作为分流策略; 或者
当所述第一设备为 UE时,所述第一设备根据自身的配置信息以及当前网 络状态中的至少一项生成至少一条路由规则和缺省接入指示中的至少一项, 作为分流策略。
4、 如权利要求 3所述的方法, 其特征在于, 所述路由规则包括: 路由接 入技术、 流描述信息、 协商指示以及第一路由规则标识信息, 其中, 所述第 一路由规则标识信息为规则名称、 规则优先级中的至少一项; 或者
所述路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示以 及第二路由规则标识信息, 其中, 所述第二路由规则标识信息为规则名称以 及规则优先级中的至少一项。
5、 如权利要求 4所述的方法, 其特征在于, 当所述路由规则包括: 路由 接入技术、 流描述信息、 协商指示以及第一路由规则标识信息时, 所述协商 指示用来标识 UE对路由规则的修改权限,取值为允许协商标识或者禁止协商 标识, 当协商指示取值为允许协商标识时,表示 UE选择该路由规则中的路由 接入技术或者其它接入技术; 当协商指示取值为禁止协商标识时,表示 UE选 择该路由规则中的路由接入技术; 或者,
当所述路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示 以及第二路由规则标识信息时, 所述路由接入技术指示用来标识对路由规则 中的路由接入技术的使用权限, 取值为禁止值或者允许值, 当路由接入技术 指示取值为禁止值时, 表示禁止使用路由规则中的路由接入技术; 或者, 当 路由接入技术指示取值为允许值时, 表示允许使用路由规则中的路由接入技 术。
6、 如权利要求 5所述的方法, 其特征在于, 当协商指示取值为禁止协商 标识时, 表示协商指示所属的路由规则为禁止协商的路由规则; 或者,
当路由接入技术指示取值为禁止值时, 表示路由接入技术指示所属的路 由规则为禁止协商的路由规则。
7、 如权利要求 5或 6所述的方法, 其特征在于, 路由接入技术指示为禁 止值对应的路由规则的规则优先级高于路由接入技术指示为允许值对应的路 由规则的规则优先级。
8、 如权利要求 5所述的方法, 其特征在于, 当所述第一设备为 UE时, 所述路由规则中的协商指示为空; 或者
所述路由规则中包含的路由接入技术指示等于允许值。
9、 如权利要求 3-8任一项所述的方法, 其特征在于, 当所述第一设备为 核心网设备时, 所述第一设备将所述分流策略发送至第二设备, 包括:
所述第一设备将所述路由规则携带于承载更新请求或承载新建请求中传 输至移动管理实体 MME, 以使 MME接收到所述路由规则后, 将所述路由规 则携带于非接入层 NAS消息中传输至所述第二设备; 或者
所述第一设备将所述路由规则携带于承载更新请求或承载新建请求中传 输至可信接入网关 TWAG, 以使所述 TWAG接收到所述路由规则后, 将所述 路由规则携带于指定的无线局域网控制面协议 WLCP消息中传输至所述第二 设备; 或者
所述第一设备将所述路由规则携带于承载更新请求或承载新建请求中传 输至非可信接入网关 ePDG, 以使所述 ePDG接收到所述路由规则后, 将所述 路由规则携带于网络密钥协商协议 IKEv2消息中传输至所述第二设备; 或者 所述第一设备将所述路由规则携带于分组数据协议 PDP上下文修改请求 或者 PDP新建请求中发送至所述第二设备。
10、 如权利要求 9所述的方法, 其特征在于, 所述第一设备将所述路由 规则携带于承载更新请求或承载新建请求中传输, 包括:
所述第一设备将所述路由规则作为新的参数添加至所述承载更新请求或 承载新建请求中传输; 或者
所述第一设备将所述路由规则添加至所述承载更新请求或承载新建请求 中的承载上下文中传输; 或者
所述第一设备将所述路由规则添加至所述承载更新请求或承载新建请求 中的协议配置选项 PCO中传输。
11、 如权利要求 9所述的方法, 其特征在于, 所述第一设备使所述 MME 将所述路由规则携带于非接入层 NAS消息中传输, 包括:
所述第一设备使所述 MME将所述路由规则作为新的参数添加至所述 NAS消息中传输; 或者
所述第一设备使所述 MME将所述路由规则添加至所述 NAS 消息中的 PCO中传输。
12、 如权利要求 3-8任一项所述的方法, 其特征在于, 当所述第一设备为 UE时, 所述第一设备将所述分流策略发送至第二设备, 包括:
当所述分流策略包括所述路由规则时, 所述第一设备将所述分流策略携 带于 NAS消息中发送至 MME, 以使所述 MME接收到所述分流策略后, 将 所述分流策略携带于承载资源命令中发送所述第二设备; 或者
当所述分流策略为缺省接入指示时, 所述第一设备将所述缺省接入指示 携带于 NAS消息中发送至 MME, 以使所述 MME接收到所述缺省接入指示 后, 将所述缺省接入指示携带于会话新建请求中发送至第二设备; 或者, 所 述第一设备将所述缺省接入指示携带于 WLCP分组数据网 PDN连接请求中发 送至 TWAG, 以使所述 TWAG接收到所述缺省接入指示后, 将所述缺省接入 指示携带于会话新建请求中发送至第二设备; 或者, 所述第一设备将所述缺 省接入指示携带于网络密钥协商协议 IKEv2 消息中发送至非可信接入网关 ePDG, 以使所述 ePDG接收到所述缺省接入指示后, 将所述缺省接入指示携 带于会话新建请求中发送至第二设备。
13、 如权利要求 12所述的方法, 其特征在于, 当所述分流策略包括所述 路由规则时, 所述第一设备将所述分流策略携带于 NAS消息中发送, 包括: 所述第一设备将所述分流策略作为新的参数添加至所述 NAS 消息中发 送; 或者
所述第一设备将所述分流策略添加至所述 NAS消息中的 PCO中发送。
14、 如权利要求 12所述的方法, 其特征在于, 当所述分流策略为缺省接 入指示时, 所述第一设备在将所述缺省接入指示携带于 NAS 消息或者所述 WLCP PDN连接请求中发送, 包括:
所述第一设备将所述缺省接入指示添加至所述 NAS消息或者所述 WLCP PDN连接请求中的 PCO中发送; 或者
当所述分流策略为缺省接入指示时, 所述第一设备使所述 MME或所述 TWAG将所述缺省接入指示携带于所述会话新建请求中发送时, 具体用于: 所述第一设备使所述 MME或所述 TWAG将所述缺省接入指示添加至所 述会话新建请求中的 PCO中发送; 或者
当所述分流策略为缺省接入指示时, 所述第一设备将所述缺省接入指示 携带于所述 IKEv2消息中发送时, 具体用于:
所述第一设备将所述缺省接入指示作为新的参数添加至所述 IKEv2消息 中发送。
15、 如权利要求 5-7任一项所述的方法, 其特征在于, 当所述第一设备为 核心网设备时, 所述第一设备接收所述第二设备针对所述分流策略返回的确 认后的分流策略, 包括:
若所述第二设备根据自身的配置信息以及当前网络状态中的至少一项对 接收的路由规则中至少一条路由规则进行修改, 则所述第一设备接收所述第 二设备发送的所述路由规则中未修改的其它路由规则以及对所述至少一条路 由规则进行修改后的更新的路由规则; 或者
若所述第二设备未对接收的所述路由规则进行修改, 则所述第一设备接 收未修改的所述路由规则。
16、 如权利要求 15所述的方法, 其特征在于, 所述第二设备修改的所述 至少一条路由规则中包含的协商指示为允许协商标识; 或者
所述第二设备修改的所述至少一条路由规则中包含的路由接入技术指示 等于允许值。
17、 如权利要求 15所述的方法, 其特征在于, 所述第一设备接收所述第 二设备针对所述分流策略返回的所述确认后的分流策略, 还包括:
接收所述第二设备基于所述确认后的分流策略产生的承载更新流程或承 载新建修改流程的确定结果。
18、 如权利要求 5-7任一项所述的方法, 其特征在于, 当所述第一设备为 UE时, 所述第一设备接收所述第二设备针对所述分流策略返回的所述确认后 的分流策略, 包括:
所述第一设备接收所述第二设备返回的确认后的路由规则和确认后的缺 省接入指示中的至少一项;
其中, 所述第一设备接收所述第二设备返回的所述确认后的缺省接入指 示, 包括:
若所述第二设备根据接收的规则信息、 UE发送的指示信息、 本地配置信 息以及当前网络状态中的至少一项对接收的所述缺省接入指示进行修改, 则 所述第一设备接收所述第二设备返回的修改后的缺省接入指示; 或者
若所述第二设备未对所述缺省接入指示进行修改, 则所述第一设备接收 所述第二设备返回的未修改的缺省接入指示; 所述第一设备接收所述第二设备返回的所述确认后的路由规则, 包括: 若所述第二设备根据接收的规则信息、 UE发送的指示信息、 本地配置信 息以及当前网络状态中的至少一项对接收的所述路由规则中至少一条路由规 则进行修改, 则所述第一设备接收所述第二设备发送的所述路由规则中未修 改的其它路由规则以及对所述至少一条路由规则进行修改后的更新的路由规 则; 或者
若所述第二设备未对接收的所述路由规则进行修改, 则所述第一设备接 收的未修改的所述路由规则。
19、 如权利要求 18所述的方法, 其特征在于, 对所述至少一条路由规则 进行修改后的更新的路由规则中包含的协商指示为禁止协商标识; 或者
对所述至少一条路由规则进行修改后的更新的路由规则中包含的路由接 入技术指示为禁止值。
20、 一种分流策略协商方法, 其特征在于, 包括:
第二设备接收第一设备发送的分流策略, 并对所述分流策略进行确认, 其中, 所述分流策略包括以下至少一项: 缺省接入指示和至少一条路由规则; 所述第二设备存储确认后的分流策略, 并将所述确认后的分流策略返回 至所述第一设备, 基于所述确认后的分流策略进行数据流传输。
21、 如权利要求 20所述的方法, 其特征在于, 所述第二设备为用户设备 UE或者核心网设备。
22、 如权利要求 21所述的方法, 其特征在于, 当所述第二设备为 UE时, 所述分流策略为所述第一设备发送的至少一条路由规则; 或者
当所述第二设备为核心网设备时, 所述分流策略为第一设备发送的至少 一条路由规则和缺省接入指示中的至少一项。
23、 如权利要求 22所述的方法, 其特征在于, 所述第一设备发送的所述 路由规则中包括: 路由接入技术、 流描述信息、 协商指示以及第一路由规则 标识信息, 其中, 所述第一路由规则标识信息为规则名称、 规则优先级中的 至少一项; 或者 所述第一设备发送的所述路由规则中包括: 路由接入技术、 流描述信息、 路由接入技术指示以及第二路由规则标识信息, 其中, 所述第二路由规则标 识信息为规则名称以及规则优先级中的至少一项。
24、 如权利要求 23所述的方法, 其特征在于, 当所述路由规则包括: 路 由接入技术、 流描述信息、 协商指示以及第一路由规则标识信息时, 所述协 商指示用来标识 UE对路由规则的修改权限,取值为允许协商标识或者禁止协 商标识, 当协商指示取值为允许协商标识时,表示 UE选择该路由规则中的路 由接入技术或者其它接入技术; 当协商指示取值为禁止协商标识时, 表示 UE 选择该路由规则中的路由接入技术; 或者,
当所述路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示 以及第二路由规则标识信息时, 所述路由接入技术指示用来标识对路由规则 中的路由接入技术的使用权限, 取值为禁止值或者允许值, 当路由接入技术 指示取值为禁止值时, 表示禁止使用路由规则中的路由接入技术; 或者, 当 路由接入技术指示取值为允许值时, 表示允许使用路由规则中的路由接入技 术。
25、 如权利要求 24所述的方法, 其特征在于, 当协商指示取值为禁止协 商标识时, 表示协商指示所属的路由规则为禁止协商的路由规则; 或者, 当路由接入技术指示取值为禁止值时, 表示路由接入技术指示所属的路 由规则为禁止协商的路由规则。
26、 如权利要求 24或 25所述的方法, 其特征在于, 路由接入技术指示 为禁止值对应的路由规则的规则优先级高于路由接入技术指示为允许值对应 的路由规则的规则优先级。
27、 如权利要求 24所述的方法, 其特征在于, 当所述第一设备为 UE时, 所述第一设备发送的所述路由规则中的协商指示为空; 或者
所述第一设备发送的所述路由规则中的路由接入技术指示等于允许值。
28、 如权利要求 25-27任一项所述的方法, 其特征在于, 当所述第二设备 为 UE时, 所述第二设备对所述分流策略进行确认, 包括: 所述第二设备对所述路由规则进行确认, 具体包括:
所述第二设备判定自身的配置信息以及当前网络状态中的至少一项与所 述路由规则中至少一条路由规则不匹配, 且所述至少一条路由规则不是禁止 协商的路由规则时, 对所述至少一条路由规则进行修改, 并生成修改后的更 新的路由规则, 将所述路由规则中未修改的其它路由规则以及对所述至少一 条路由规则进行修改后的更新的路由规则作为确认后的路由规则; 或者
所述第二设备判定自身的配置信息以及当前网络状态中的至少一项与所 述路由规则中所有路由规则匹配, 或者自身的配置信息以及当前网络状态中 的至少一项与所述路由规则中不匹配的路由规则为禁止协商的路由规则时, 不对所述路由规则进行修改, 将未修改的所述路由规则作为确认后的路由规 则。
29、 如权利要求 25-27任一项所述的方法, 其特征在于, 当所述第二设备 为核心网设备时, 所述第二设备对所述分流策略进行确认, 包括:
所述第二设备对所述分流策略中的缺省接入指示进行确认, 和 /或, 所述 第二设备对所述分流策略中的路由规则进行确认;
其中, 所述第二设备对所述缺省接入指示进行确认, 包括:
所述第二设备判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态中的至少一项与所述缺省接入指示不匹配时, 对所述缺省 接入指示进行修改, 将修改后的缺省接入指示作为确认后的缺省接入指示; 或者
所述第二设备判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态与所述缺省接入指示匹配时, 不对所述缺省接入指示进行 修改, 将未修改的所述缺省接入指示作为确认后的缺省接入指示;
所述第二设备对所述路由规则进行确认, 包括:
所述第二设备判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态中的至少一项与所述路由规则中至少一条路由规则不匹配 时, 对所述至少一条路由规则进行修改, 并生成修改后的更新的路由规则, 将所述路由规则中未修改的其它路由规则以及对所述至少一条路由规则进行 修改后的更新的路由规则作为确认后的路由规则; 或者
所述第二设备判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态与所述路由规则中所有路由规则匹配时, 不对所述路由规 则进行修改, 将未修改的所述路由规则作为确认后的路由规则。
30、 如权利要求 29所述的方法, 其特征在于, 所述第二设备对所述至少 一条路由规则进行修改包括:
所述第二设备对所述至少一条路由规则中包含的路由接入技术进行修 改, 并
在所述至少一条路由规则中包含协商指示时, 将所述至少一条路由规则 中包含的协商指示设置为禁止协商标识; 在所述至少一条路由规则包含路由 接入技术指示时, 将所述至少一条路由规则中包含的路由接入技术指示设置 为禁止值。
31、 如权利要求 28所述的方法, 其特征在于, 当所述第二设备为 UE时, 所述第二设备将所述确认后的分流策略返回至所述第一设备, 包括:
所述第二设备将所述确认后的路由规则携带于非接入层 NAS消息中传输 至移动管理实体 MME, 以使 MME接收到所述确认后的路由规则后, 将所述 确认后的路由规则携带于承载更新响应或承载新建响应中传输至所述第一设 备; 或者
所述第二设备将所述确认后的路由规则携带于指定的无线局域网控制面 协议 WLCP消息中传输至可信接入网关 TWAG,以使所述 TWAG接收到所述 确认后的路由规则后, 将所述确认后的路由规则携带于承载更新响应或承载 新建响应中传输至所述第一设备; 或者
所述第二设备将所述确认后的路由规则携带于网络密钥协商协议 IKEv2 消息中传输至非可信接入网关 ePDG, 以使所述 ePDG接收到所述确认后的路 由规则后, 将所述确认后的路由规则携带于承载更新响应或承载新建响应中 传输至所述第一设备。
32、 如权利要求 31所述的方法, 其特征在于, 所述第二设备将所述确认 后的路由规则携带于 NAS消息中传输至 MME, 包括:
所述第二设备将所述确认后的路由规则作为新的参数添加至所述 NAS消 息中传输至 MME; 或者
所述第二设备将所述确认后的路由规则添加至所述 NAS消息中的协议配 置选项 PCO中传输至 MME。
33、 如权利要求 31所述的方法, 其特征在于, 将所述确认后的路由规则 携带于承载更新响应或承载新建响应中传输至所述第一设备, 包括:
将所述确认后的路由规则作为新的参数添加至所述承载更新响应或承载 新建响应中传输至所述第一设备; 或者
将所述确认后的路由规则添加至所述承载更新响应或承载新建响应中的 承载上下文中传输至所述第一设备; 或者
将所述确认后的路由规则添加至所述承载更新响应或承载新建响应中的 PCO中传输至所述第一设备。
34、 如权利要求 31-33任一项所述的方法, 其特征在于, 所述第二设备将 确认后的分流策略返回至第一设备, 还包括:
发送所述第二设备基于所述确认后的分流策略产生的承载更新流程或承 载新建修改流程的确定结果。
35、 如权利要求 29所述的方法, 其特征在于, 当所述第二设备为核心网 设备时, 所述第二设备将所述确认后的分流策略返回至所述第一设备, 包括: 当所述确认后的分流策略包括所述确认后的路由规则时, 所述第二设备 通过将所述确认后的分流策略携带于承载更新请求或承载新建请求中传输至 MME; 以使 MME接收到所述确认后的分流策略后, 将所述确认后的分流策 略携带于 NAS消息中传输至所述第一设备; 或者, 所述第二设备将所述确认 后的分流策略携带于分组数据协议 PDP上下文修改请求或者 PDP上下文新建 请求中发送至所述第一设备; 或者
当所述确认后的分流策略为确认后的缺省接入指示时, 所述第二设备将 所述确认后的缺省接入指示携带于会话新建响应中发送至 MME, 以使所述 MME接收到所述确认后的缺省接入指示后,将所述确认后的缺省接入指示携 带于 NAS消息中发送至所述第一设备; 或者, 所述第二设备将所述确认后的 缺省接入指示携带于会话新建响应中发送至可信接入网关 TWAG, 以使所述 TWAG接收到所述确认后的缺省接入指示后, 将所述确认后的缺省接入指示 携带于无线局域网控制面协议 WLCP分组数据网 PDN连接响应中发送至所述 第一设备; 或者, 所述第二设备将所述确认后的缺省接入指示携带于会话新 建响应中发送至非可信接入网关 ePDG, 以使所述 ePDG接收到所述确认后的 缺省接入指示,将所述确认后的缺省接入指示携带于网络密钥协商协议 IKEv2 消息中发送至所述第一设备。
36、 如权利要求 35所述的方法, 其特征在于, 当所述确认后的分流策略 包括确认后的路由规则时,所述第二设备使 MME将所述确认后的分流策略携 带于 NAS消息中传输至所述第一设备, 包括:
所述第二设备使 MME将所述确认后的分流策略作为新的参数添加至所 述 NAS消息中传输至所述第一设备; 或者
所述第二设备使 MME将所述确认后的分流策略添加至所述 NAS消息中 的 PCO中传输至所述第一设备。
37、 如权利要求 35所述的方法, 其特征在于, 当所述确认后的分流策略 为确认后的缺省接入指示时, 所述第二设备将所述确认后的缺省接入指示携 带于所述会话新建响应中发送, 包括:
所述第二设备将所述确认后的缺省接入指示添加至所述会话新建响应中 的 PCO中发送;
当所述确认后的分流策略为确认后的缺省接入指示, 所述第二设备使 MME将所述确认后的缺省接入指示携带于所述 NAS消息中发送, 包括: 所述第二设备使 MME将所述确认后的缺省接入指示添加至所述 NAS消 息中的 PCO中发送;
当所述确认后的分流策略为确认后的缺省接入指示, 所述第二设备使 TWAG将所述确认后的缺省接入指示携带于所述 WLCP PDN连接响应中发送 时, 具体用于:
所述第二设备使 TWAG将所述确认后的缺省接入指示添加至所述 WLCP PDN连接响应中的 PCO中发送;
当所述确认后的分流策略为确认后的缺省接入指示时, 所述第二设备使 ePDG将所述确认后的缺省接入指示携带于所述 IKEv2消息中发送, 包括: 所述第二设备使 ePDG将所述确认后缺省接入指示作为新的参数添加至 所述 IKEv2消息中发送。
38、 一种分流策略协商装置, 其特征在于, 包括:
发送单元, 用于将分流策略发送至第二设备, 其中, 所述分流策略包括 以下至少一项: 缺省接入指示和至少一条路由规则;
接收单元, 用于接收并存储所述第二设备针对所述分流策略返回的确认 后的分流策略, 基于所述确认后的分流策略进行数据流传输。
39、 如权利要求 38所述的装置, 其特征在于, 所述分流策略协商装置为 核心网设备或者用户设备 UE。
40、 如权利要求 39所述的装置, 其特征在于, 所述分流策略协商装置还 包括:
生成单元, 用于在所述发送单元将分流策略发送至第二设备之前, 生成 分流策略, 所述生成单元具体用于:
当所述分流策略协商装置为核心网设备时, 所述生成单元根据接收的规 则信息、 UE发送的指示信息、 本地配置信息以及当前网络状态中的至少一项 生成至少一条路由规则作为分流策略; 或者
当所述分流策略协商装置为 UE时,所述生成单元根据自身的配置信息以 及当前网络状态中的至少一项生成至少一条路由规则和缺省接入指示中的至 少一项, 作为分流策略。
41、 如权利要求 40所述的装置, 其特征在于, 所述路由规则包括: 路由 接入技术、 流描述信息、 协商指示以及第一路由规则标识信息, 其中, 所述 第一路由规则标识信息为规则名称、 规则优先级中的至少一项; 或者 所述路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示以 及第二路由规则标识信息, 其中, 所述第二路由规则标识信息为规则名称以 及规则优先级中的至少一项。
42、 如权利要求 41所述的装置, 其特征在于, 当所述路由规则包括: 路 由接入技术、 流描述信息、 协商指示以及第一路由规则标识信息时, 所述协 商指示用来标识 UE对路由规则的修改权限,取值为允许协商标识或者禁止协 商标识, 当协商指示取值为允许协商标识时,表示 UE选择该路由规则中的路 由接入技术或者其它接入技术; 当协商指示取值为禁止协商标识时, 表示 UE 选择该路由规则中的路由接入技术; 或者,
当所述路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示 以及第二路由规则标识信息时, 所述路由接入技术指示用来标识对路由规则 中的路由接入技术的使用权限, 取值为禁止值或者允许值, 当路由接入技术 指示取值为禁止值时, 表示禁止使用路由规则中的路由接入技术; 或者, 当 路由接入技术指示取值为允许值时, 表示允许使用路由规则中的路由接入技 术。
43、 如权利要求 42所述的装置, 其特征在于, 当协商指示取值为禁止协 商标识时, 表示协商指示所属的路由规则为禁止协商的路由规则; 或者, 当路由接入技术指示取值为禁止值时, 表示路由接入技术指示所属的路 由规则为禁止协商的路由规则。
44、 如权利要求 42或 43所述的装置, 其特征在于, 路由接入技术指示 为禁止值对应的路由规则的规则优先级高于路由接入技术指示为允许值对应 的路由规则的规则优先级。
45、 如权利要求 42所述的装置, 其特征在于, 当所述分流策略协商装置 为 UE时, 所述路由规则中的协商指示为空; 或者
所述路由规则中包含的路由接入技术指示等于允许值。
46、 如权利要求 40-45任一项所述的装置, 其特征在于, 当所述分流策略 协商装置为核心网设备时, 所述发送单元, 具体用于:
所述发送单元将所述路由规则携带于承载更新请求或承载新建请求中传 输至移动管理实体 MME, 以使 MME接收到所述路由规则后, 将所述路由规 则携带于非接入层 NAS消息中传输至所述第二设备; 或者
所述发送单元将所述路由规则携带于承载更新请求或承载新建请求中传 输至可信接入网关 TWAG, 以使所述 TWAG接收到所述路由规则后, 将所述 路由规则携带于指定的无线局域网控制面协议 WLCP消息中传输至所述第二 设备; 或者
所述发送单元将所述路由规则携带于承载更新请求或承载新建请求中传 输至非可信接入网关 ePDG, 以使所述 ePDG接收到所述路由规则后, 将所述 路由规则携带于网络密钥协商协议 IKEv2消息中传输至所述第二设备; 或者 所述发送单元将所述路由规则携带于分组数据协议 PDP上下文修改请求 或者 PDP新建请求中发送至所述第二设备。
47、 如权利要求 46所述的装置, 其特征在于, 所述发送单元在将所述路 由规则携带于承载更新请求或承载新建请求中传输时, 具体用于:
所述发送单元将所述路由规则作为新的参数添加至所述承载更新请求或 承载新建请求中传输; 或者
所述发送单元将所述路由规则添加至所述承载更新请求或承载新建请求 中的承载上下文中传输; 或者
所述发送单元将所述路由规则添加至所述承载更新请求或承载新建请求 中的协议配置选项 PCO中传输。
48、 如权利要求 46所述的装置, 其特征在于, 所述发送单元使 MME将 所述路由规则携带于非接入层 NAS消息中传输时, 具体用于:
所述发送单元使 MME将所述路由规则作为新的参数添加至所述 NAS消 息中传输; 或者
所述发送单元使 MME将所述路由规则添加至所述 NAS消息中的 PCO中 传输。
49、 如权利要求 40-45任一项所述的装置, 其特征在于, 当所述分流策略 协商装置为 UE时, 所述发送单元, 具体用于:
当所述分流策略包括所述路由规则时, 所述发送单元将所述分流策略携 带于 NAS消息中发送至 MME, 以使所述 MME接收到所述分流策略后, 将 所述分流策略携带于承载资源命令中发送所述第二设备; 或者
当所述分流策略为缺省接入指示时, 所述发送单元将所述缺省接入指示 携带于 NAS消息中发送至 MME, 以使所述 MME接收到所述缺省接入指示 后, 将所述缺省接入指示携带于会话新建请求中发送至第二设备; 或者, 所 述发送单元将所述缺省接入指示携带于 WLCP分组数据网 PDN连接请求中发 送至 TWAG, 以使所述 TWAG接收到所述缺省接入指示后, 将所述缺省接入 指示携带于会话新建请求中发送至第二设备; 或者, 所述发送单元将所述缺 省接入指示携带于网络密钥协商协议 IKEv2 消息中发送至非可信接入网关 ePDG, 以使所述 ePDG接收到所述缺省接入指示后, 将所述缺省接入指示携 带于会话新建请求中发送至第二设备。
50、 如权利要求 49所述的装置, 其特征在于, 当所述分流策略包括所述 路由规则, 所述发送单元在将所述分流策略携带于 NAS消息中发送时, 具体 用于:
所述发送单元将所述分流策略作为新的参数添加至所述 NAS 消息中发 送; 或者
所述发送单元将所述分流策略添加至所述 NAS消息中的 PCO中发送。
51、 如权利要求 49所述的装置, 其特征在于, 当所述分流策略为缺省接 入指示, 所述发送单元在将所述缺省接入指示携带于 NAS 消息或者所述 WLCP PDN连接请求中发送时, 具体用于:
所述发送单元将所述缺省接入指示添加至所述 NAS消息或者所述 WLCP PDN连接请求中的 PCO中发送; 或者
当所述分流策略为缺省接入指示时, 所述发送单元使所述 MME或所述 TWAG将所述缺省接入指示携带于所述会话新建请求中发送时, 具体用于: 所述发送单元使所述 MME或所述 TWAG将所述缺省接入指示添加至所 述会话新建请求中的 PCO中发送; 或者
当所述分流策略为缺省接入指示时, 所述发送单元将所述缺省接入指示 携带于所述 IKEv2消息中发送时, 具体用于:
所述发送单元将所述缺省接入指示作为新的参数添加至所述 IKEv2消息 中发送。
52、 如权利要求 42-44任一项所述的装置, 其特征在于, 当所述分流策略 协商装置为核心网设备时, 所述接收单元, 具体用于:
若所述第二设备根据自身的配置信息以及当前网络状态中的至少一项对 接收的路由规则中至少一条路由规则进行修改, 则所述接收单元接收所述第 二设备发送的所述路由规则中未修改的其它路由规则以及对所述至少一条路 由规则进行修改后的更新的路由规则; 或者
若所述第二设备未对接收的所述路由规则进行修改, 则所述接收单元接 收未修改的所述路由规则。
53、 如权利要求 52所述的装置, 其特征在于, 所述第二设备修改的所述 至少一条路由规则中包含的协商指示为允许协商标识; 或者
所述第二设备修改的所述至少一条路由规则中包含的路由接入技术指示 等于允许值。
54、 如权利要求 52所述的装置, 其特征在于, 所述接收单元, 还用于: 接收所述第二设备基于所述确认后的分流策略产生的承载更新流程或承 载新建修改流程的确定结果。
55、 如权利要求 42-44任一项所述的装置, 其特征在于, 当所述分流策略 协商装置为 UE时, 所述接收单元, 具体用于:
所述接收单元接收所述第二设备返回的确认后的路由规则和确认后的缺 省接入指示中的至少一项;
其中, 所述接收单元在接收所述第二设备返回的所述确认后的缺省接入 指示时, 具体用于: 若所述第二设备根据接收的规则信息、 UE发送的指示信息、 本地配置信 息以及当前网络状态中的至少一项对接收的所述缺省接入指示进行修改, 则 所述接收单元接收所述第二设备返回的修改后的缺省接入指示; 或者
若所述第二设备未对所述缺省接入指示进行修改, 则所述接收单元接收 所述第二设备返回的未修改的缺省接入指示;
所述接收单元在接收所述第二设备返回的所述确认后的路由规则时, 具 体用于:
若所述第二设备根据接收的规则信息、 UE发送的指示信息、 本地配置信 息以及当前网络状态中的至少一项对接收的所述路由规则中至少一条路由规 则进行修改, 则所述接收单元接收所述第二设备发送的所述路由规则中未修 改的其它路由规则以及对所述至少一条路由规则进行修改后的更新的路由规 则; 或者
若所述第二设备未对接收的所述路由规则进行修改, 则所述接收单元接 收的未修改的所述路由规则。
56、 如权利要求 55所述的装置, 其特征在于, 对所述至少一条路由规则 进行修改后的更新的路由规则中包含的协商指示为禁止协商标识; 或者
对所述至少一条路由规则进行修改后的更新的路由规则中包含的路由接 入技术指示为禁止值。
57、 一种分流策略协商装置, 其特征在于, 包括:
确认单元, 用于接收第一设备发送的分流策略, 并对所述分流策略进行 确认, 其中, 所述分流策略包括以下至少一项: 缺省接入指示和至少一条路 由规则;
处理单元, 用于存储确认后的分流策略, 并将所述确认后的分流策略返 回至所述第一设备, 基于所述确认后的分流策略进行数据流传输。
58、 如权利要求 57所述的装置, 其特征在于, 所述分流策略协商装置为 用户设备 UE或者核心网设备。
59、 如权利要求 58所述的装置, 其特征在于, 当所述分流策略协商装置 为 UE时, 所述分流策略为所述第一设备发送的至少一条路由规则; 或者 当所述分流策略协商装置为核心网设备时, 所述分流策略为第一设备发 送的至少一条路由规则和缺省接入指示中的至少一项。
60、 如权利要求 59所述的装置, 其特征在于, 所述第一设备发送的所述 路由规则中包括: 路由接入技术、 流描述信息、 协商指示以及第一路由规则 标识信息, 其中, 所述第一路由规则标识信息为规则名称、 规则优先级中的 至少一项; 或者
所述第一设备发送的所述路由规则中包括: 路由接入技术、 流描述信息、 路由接入技术指示以及第二路由规则标识信息, 其中, 所述第二路由规则标 识信息为规则名称以及规则优先级中的至少一项。
61、 如权利要求 60所述的装置, 其特征在于, 当所述路由规则包括: 路 由接入技术、 流描述信息、 协商指示以及第一路由规则标识信息时, 所述协 商指示用来标识 UE对路由规则的修改权限,取值为允许协商标识或者禁止协 商标识, 当协商指示取值为允许协商标识时,表示 UE选择该路由规则中的路 由接入技术或者其它接入技术; 当协商指示取值为禁止协商标识时, 表示 UE 选择该路由规则中的路由接入技术; 或者,
当所述路由规则包括: 路由接入技术、 流描述信息、 路由接入技术指示 以及第二路由规则标识信息时, 所述路由接入技术指示用来标识对路由规则 中的路由接入技术的使用权限, 取值为禁止值或者允许值, 当路由接入技术 指示取值为禁止值时, 表示禁止使用路由规则中的路由接入技术; 或者, 当 路由接入技术指示取值为允许值时, 表示允许使用路由规则中的路由接入技 术。
62、 如权利要求 61所述的装置, 其特征在于, 当协商指示取值为禁止协 商标识时, 表示协商指示所属的路由规则为禁止协商的路由规则; 或者, 当路由接入技术指示取值为禁止值时, 表示路由接入技术指示所属的路 由规则为禁止协商的路由规则。
63、 如权利要求 61或 62所述的装置, 其特征在于, 路由接入技术指示 为禁止值对应的路由规则的规则优先级高于路由接入技术指示为允许值对应 的路由规则的规则优先级。
64、 如权利要求 61所述的装置, 其特征在于, 当所述第一设备为 UE时, 所述第一设备发送的所述路由规则中的协商指示为空; 或者
所述第一设备发送的所述路由规则中的路由接入技术指示等于允许值。
65、 如权利要求 62-64任一项所述的装置, 其特征在于, 当所述分流策略 协商装置为 UE时, 所述确认单元, 用于:
对所述路由规则进行确认;
所述确认单元对所述路由规则进行确认时, 具体用于:
所述确认单元判定自身的配置信息以及当前网络状态中的至少一项与所 述路由规则中至少一条路由规则不匹配, 且所述至少一条路由规则不是禁止 协商的路由规则时, 对所述至少一条路由规则进行修改, 并生成修改后的更 新的路由规则, 将所述路由规则中未修改的其它路由规则以及对所述至少一 条路由规则进行修改后的更新的路由规则作为确认后的路由规则; 或者
所述确认单元判定自身的配置信息以及当前网络状态中的至少一项与所 述路由规则中所有路由规则匹配, 或者自身的配置信息以及当前网络状态中 的至少一项与所述路由规则中不匹配的路由规则为禁止协商的路由规则时, 不对所述路由规则进行修改, 将未修改的所述路由规则作为确认后的路由规 则。
66、 如权利要求 62-64任一项所述的装置, 其特征在于, 当所述分流策略 协商装置为核心网设备时, 所述确认单元, 用于:
对所述分流策略中的缺省接入指示进行确认, 和 /或, 对所述分流策略中 的路由规则进行确认;
其中, 所述确认单元对所述缺省接入指示进行确认时, 具体用于: 所述确认单元判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态中的至少一项与所述缺省接入指示不匹配时, 对所述缺省 接入指示进行修改, 将修改后的缺省接入指示作为确认后的缺省接入指示; 或者
所述确认单元判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态与所述缺省接入指示匹配时, 不对所述缺省接入指示进行 修改, 将未修改的所述缺省接入指示作为确认后的缺省接入指示;
所述确认单元对所述路由规则进行确认时, 具体用于:
所述确认单元判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态中的至少一项与所述路由规则中至少一条路由规则不匹配 时, 对所述至少一条路由规则进行修改, 并生成修改后的更新的路由规则, 将所述路由规则中未修改的其它路由规则以及对所述至少一条路由规则进行 修改后的更新的路由规则作为确认后的路由规则; 或者
所述确认单元判定接收的规则信息、 UE发送的指示信息、 本地配置信息 以及当前网络状态与所述路由规则中所有路由规则匹配时, 不对所述路由规 则进行修改, 将未修改的所述路由规则作为确认后的路由规则。
67、 如权利要求 66所述的装置, 其特征在于, 所述确认单元对所述至少 一条路由规则进行修改时, 具体用于:
所述确认单元对所述至少一条路由规则中包含的路由接入技术进行修 改, 并
在所述至少一条路由规则中包含协商指示时, 将所述至少一条路由规则 中包含的协商指示设置为禁止协商标识; 在所述至少一条路由规则包含路由 接入技术指示时, 将所述至少一条路由规则中包含的路由接入技术指示设置 为禁止值。
68、 如权利要求 65所述的装置, 其特征在于, 当所述分流策略协商装置 为 UE时, 所述处理单元, 具体用于:
所述处理单元将所述确认后的路由规则携带于非接入层 NAS消息中传输 至移动管理实体 MME, 以使 MME接收到所述确认后的路由规则后, 将所述 确认后的路由规则携带于承载更新响应或承载新建响应中传输至所述第一设 备; 或者 所述处理单元将所述确认后的路由规则携带于指定的无线局域网控制面 协议 WLCP消息中传输至可信接入网关 TWAG,以使所述 TWAG接收到所述 确认后的路由规则后, 将所述确认后的路由规则携带于承载更新响应或承载 新建响应中传输至所述第一设备; 或者
所述处理单元将所述确认后的路由规则携带于网络密钥协商协议 IKEv2 消息中传输至非可信接入网关 ePDG, 以使所述 ePDG接收到所述确认后的路 由规则后, 将所述确认后的路由规则携带于承载更新响应或承载新建响应中 传输至所述第一设备。
69、 如权利要求 68所述的装置, 其特征在于, 所述处理单元将所述确认 后的路由规则携带于 NAS消息中传输至 MME时, 具体用于:
所述处理单元将所述确认后的路由规则作为新的参数添加至所述 NAS消 息中传输至 MME; 或者
所述处理单元将所述确认后的路由规则添加至所述 NAS消息中的协议配 置选项 PCO中传输至 MME。
70、如权利要求 68所述的装置,其特征在于,所述处理单元使所述 MME、 所述 TWAG或者所述 ePDG将所述确认后的路由规则携带于承载更新响应或 承载新建响应中传输至所述第一设备时, 具体用于:
所述处理单元使所述 MME、 所述 TWAG或者所述 ePDG将所述确认后 的路由规则作为新的参数添加至所述承载更新响应或承载新建响应中传输至 所述第一设备; 或者
所述处理单元使所述 MME、 所述 TWAG或者所述 ePDG将所述确认后 的路由规则添加至所述承载更新响应或承载新建响应中的承载上下文中传输 至所述第一设备; 或者
所述处理单元使所述 MME、 所述 TWAG或者所述 ePDG将所述确认后 的路由规则添加至所述承载更新响应或承载新建响应中的 PCO中传输至所述 第一设备。
71、 如权利要求 68-70任一项所述的装置, 其特征在于, 所述处理单元, 还用于:
发送所述分流策略协商装置基于所述确认后的分流策略产生的承载更新 流程或承载新建修改流程的确定结果。
72、 如权利要求 66所述的装置, 其特征在于, 当所述分流策略协商装置 为核心网设备时, 所述处理单元, 具体用于:
当所述确认后的分流策略包括所述确认后的路由规则时, 所述处理单元 通过将所述确认后的分流策略携带于承载更新请求或承载新建请求中传输至 MME; 以使 MME接收到所述确认后的分流策略后, 将所述确认后的分流策 略携带于 NAS消息中传输至所述第一设备; 或者, 所述处理单元将所述确认 后的分流策略携带于分组数据协议 PDP上下文修改请求或者 PDP上下文新建 请求中发送至所述第一设备; 或者
当所述确认后的分流策略为确认后的缺省接入指示时, 所述处理单元将 所述确认后的缺省接入指示携带于会话新建响应中发送至 MME, 以使所述 MME接收到所述确认后的缺省接入指示后,将所述确认后的缺省接入指示携 带于 NAS消息中发送至所述第一设备; 或者, 所述处理单元将所述确认后的 缺省接入指示携带于会话新建响应中发送至可信接入网关 TWAG, 以使所述 TWAG接收到所述确认后的缺省接入指示后, 将所述确认后的缺省接入指示 携带于无线局域网控制面协议 WLCP分组数据网 PDN连接响应中发送至所述 第一设备; 或者, 所述处理单元将所述确认后的缺省接入指示携带于会话新 建响应中发送至非可信接入网关 ePDG, 以使所述 ePDG接收到所述确认后的 缺省接入指示,将所述确认后的缺省接入指示携带于网络密钥协商协议 IKEv2 消息中发送至所述第一设备。
73、 如权利要求 72所述的装置, 其特征在于, 当所述确认后的分流策略 包括确认后的路由规则,所述处理单元使 MME将所述确认后的分流策略携带 于 NAS消息中传输至所述第一设备时, 具体用于:
所述处理单元使 MME将所述确认后的分流策略作为新的参数添加至所 述 NAS消息中传输至所述第一设备; 或者 所述处理单元使 MME将所述确认后的分流策略添加至所述 NAS消息中 的 PCO中传输至所述第一设备。
74、 如权利要求 72所述的装置, 其特征在于, 当所述确认后的分流策略 为确认后的缺省接入指示, 所述处理单元将所述确认后的缺省接入指示携带 于所述会话新建响应中发送时, 具体用于:
所述处理单元将所述确认后的缺省接入指示添加至所述会话新建响应中 的 PCO中发送;
当所述确认后的分流策略为确认后的缺省接入指示, 所述处理单元使 MME将所述确认后的缺省接入指示携带于所述 NAS消息中发送时, 具体用 于:
所述处理单元使 MME将所述确认后的缺省接入指示添加至所述 NAS消 息中的 PCO中发送;
当所述确认后的分流策略为确认后的缺省接入指示, 所述处理单元使 TWAG将所述确认后的缺省接入指示携带于所述 WLCP PDN连接响应中发送 时, 具体用于:
所述处理单元使 TWAG将所述确认后的缺省接入指示添加至所述 WLCP PDN连接响应中的 PCO中发送;
当所述确认后的分流策略为确认后的缺省接入指示时, 所述处理单元使 ePDG将所述确认后的缺省接入指示携带于所述 IKEv2消息中发送时,具体用 于:
所述处理单元使 ePDG将所述确认后缺省接入指示作为新的参数添加至 所述 IKEv2消息中发送。
PCT/CN2014/086073 2014-09-05 2014-09-05 一种分流策略协商方法及装置 WO2016033811A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
CN201910611911.0A CN110461012B (zh) 2014-09-05 2014-09-05 一种分流策略协商方法及装置
ES19204616T ES2926077T3 (es) 2014-09-05 2014-09-05 Método y aparato de negociación de las políticas de descarga
PCT/CN2014/086073 WO2016033811A1 (zh) 2014-09-05 2014-09-05 一种分流策略协商方法及装置
EP19204616.7A EP3668023B1 (en) 2014-09-05 2014-09-05 Offloading policy negotiation method and apparatus
CN201480032643.2A CN105594165B (zh) 2014-09-05 2014-09-05 一种分流策略协商方法及装置
EP14901168.6A EP3182654B1 (en) 2014-09-05 2014-09-05 Offload strategy negotiation method and apparatus
US15/449,028 US11178057B2 (en) 2014-09-05 2017-03-03 Offloading policy negotiation method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/086073 WO2016033811A1 (zh) 2014-09-05 2014-09-05 一种分流策略协商方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/449,028 Continuation US11178057B2 (en) 2014-09-05 2017-03-03 Offloading policy negotiation method and apparatus

Publications (1)

Publication Number Publication Date
WO2016033811A1 true WO2016033811A1 (zh) 2016-03-10

Family

ID=55439054

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/086073 WO2016033811A1 (zh) 2014-09-05 2014-09-05 一种分流策略协商方法及装置

Country Status (5)

Country Link
US (1) US11178057B2 (zh)
EP (2) EP3182654B1 (zh)
CN (2) CN105594165B (zh)
ES (1) ES2926077T3 (zh)
WO (1) WO2016033811A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018175029A1 (en) * 2017-03-20 2018-09-27 Qualcomm Incorporated Policy communication via control plane signaling

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8863416B2 (en) 2011-10-28 2014-10-21 Polygroup Macau Limited (Bvi) Powered tree construction
CN106162801A (zh) * 2015-03-27 2016-11-23 中兴通讯股份有限公司 实现缺省路由决策的方法、核心网网元、用户设备及系统
CN108307698B (zh) * 2015-04-07 2022-01-04 夏普株式会社 终端装置、分组数据网络网关及可信无线区域网络接入网关
WO2017075813A1 (zh) * 2015-11-06 2017-05-11 华为技术有限公司 一种业务数据流报文的传输方法及装置、系统
US20190028931A1 (en) * 2017-07-19 2019-01-24 Nokia Of America Corporation Method and apparatus for quality of service differentiation via a trusted wireless local area network
EP3965367A1 (en) * 2017-10-20 2022-03-09 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data transmission method, terminal device, and network device
CN111372322B (zh) * 2018-12-25 2022-04-12 华为技术有限公司 一种通信方法及装置
WO2021093158A1 (en) * 2020-01-13 2021-05-20 Zte Corporation A method for adaptively configuring transmission of data flows
CN115442850A (zh) * 2021-06-01 2022-12-06 中兴通讯股份有限公司 网络接入方法、网络设备和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101150418A (zh) * 2007-10-17 2008-03-26 中兴通讯股份有限公司 一种策略计费控制服务器的选择方法
CN101895476A (zh) * 2010-07-30 2010-11-24 中国电信股份有限公司 多接入方式并发传输的方法、系统、网络侧设备和终端
CN102014448A (zh) * 2009-09-04 2011-04-13 华为技术有限公司 一种业务流的绑定方法、设备及系统
CN103748926A (zh) * 2011-06-22 2014-04-23 阿尔卡特朗讯 在受信任的非3gpp接入上的ip连接支持

Family Cites Families (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101213789B (zh) * 2005-06-29 2012-12-05 艾利森电话股份有限公司 用于代表多运营商无线通信系统中的移动环境网络进行协商的网络组件及其使用方法
US8503430B2 (en) * 2006-11-21 2013-08-06 Qualcomm Incorporated Dynamic operational mode management for a wireless terminal
DE602007011676D1 (de) * 2007-08-20 2011-02-10 Ericsson Telefon Ab L M Lokalen breakout in einem mobilnetz
US8228861B1 (en) * 2008-09-12 2012-07-24 Nix John A Efficient handover of media communications in heterogeneous IP networks using handover procedure rules and media handover relays
EP2368380B1 (en) * 2008-12-19 2019-02-27 NEC Corporation A radio network and a method for operating a radio network
CN102014517A (zh) * 2009-09-08 2011-04-13 中兴通讯股份有限公司 漫游场景下承载控制模式的发送方法和系统
US8498651B2 (en) * 2009-11-06 2013-07-30 Alcatel Lucent Method of call admission control for home femtocells
US8737318B2 (en) * 2009-12-01 2014-05-27 At&T Intellectual Property I, L.P. Service models for roaming mobile device
EP2553989B1 (en) * 2010-03-31 2017-10-25 Telefonaktiebolaget LM Ericsson (publ) Access feedback by a multimode terminal
EP2574133B1 (en) * 2010-08-20 2019-03-13 Huawei Technologies Co., Ltd. Method and apparatus for reporting radio bearer loss message
CN102469431B (zh) * 2010-11-05 2015-04-01 中兴通讯股份有限公司 漫游场景下支持ip流迁移的策略计费控制方法和系统
CN102958035B (zh) * 2011-08-22 2016-08-03 北京配天智慧云技术有限公司 多网络ip业务流无缝融合的方法及通信系统和相关装置
US8942099B2 (en) * 2011-09-21 2015-01-27 Mediatek Inc. Method and apparatus of IP flow mobility in 4G wireless communication networks
CN104221415A (zh) * 2012-02-25 2014-12-17 英特尔公司 用于管理频谱服务的动态共享的方法和设备
CN103582079A (zh) * 2012-08-10 2014-02-12 中兴通讯股份有限公司 一种联合传输的实现方法和系统
US9521005B2 (en) * 2012-11-06 2016-12-13 Nokia Technologies Oy Access network selection
US9179383B2 (en) * 2013-01-20 2015-11-03 Lg Electronics Inc. Method and terminal for determining handover for traffic offloaded onto WLAN
US20140211616A1 (en) * 2013-01-31 2014-07-31 Cisco Technology, Inc. Network Assisted Data Flow Mobility
US9326118B2 (en) * 2013-03-15 2016-04-26 Billing Services Group System and method for rating, clearing and settlement of wireless roaming and offloading
US10560887B2 (en) * 2013-05-06 2020-02-11 Qualcomm Incorporated Routing modification based on handover detection
WO2014180517A1 (en) * 2013-05-08 2014-11-13 Telefonaktiebolaget L M Ericsson (Publ) Improved handling of simultaneous network communication transmission and d2d communication reception or simultaneous network communication reception and d2d communication transmission
US10039039B2 (en) * 2013-07-02 2018-07-31 Lg Electronics Inc. Method and apparatus for performing handover in wireless communication system
CN105025544B (zh) * 2014-04-18 2019-03-05 电信科学技术研究院 一种ip流路由规则的确定方法和设备
US20150327114A1 (en) * 2014-05-08 2015-11-12 Intel IP Corporation Updates to support network based internet protocol flow mobility
US9930716B2 (en) * 2014-06-30 2018-03-27 Apple Inc. Methods and apparatus to support network-based IP flow mobility via multiple wireless accesses for a wireless device
JP2017526242A (ja) * 2014-06-30 2017-09-07 インターデイジタル パテント ホールディングス インコーポレイテッド 多重接続性デバイスに対するネットワークベースのフローモビリティ
US20160277980A1 (en) * 2014-11-07 2016-09-22 Telefonaktiebolaget L M Ericsson (Publ) Handing Over a Data Bearer Between Access Networks
BR112017012165A2 (pt) * 2015-01-20 2018-01-02 Intel Ip Corp aparelho e método para controle de mobilidade de fluxo de ip bidirecional

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101150418A (zh) * 2007-10-17 2008-03-26 中兴通讯股份有限公司 一种策略计费控制服务器的选择方法
CN102014448A (zh) * 2009-09-04 2011-04-13 华为技术有限公司 一种业务流的绑定方法、设备及系统
CN101895476A (zh) * 2010-07-30 2010-11-24 中国电信股份有限公司 多接入方式并发传输的方法、系统、网络侧设备和终端
CN103748926A (zh) * 2011-06-22 2014-04-23 阿尔卡特朗讯 在受信任的非3gpp接入上的ip连接支持

Non-Patent Citations (1)

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

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018175029A1 (en) * 2017-03-20 2018-09-27 Qualcomm Incorporated Policy communication via control plane signaling
US10231250B2 (en) 2017-03-20 2019-03-12 Qualcomm Incorporated Policy communication via control plane signaling
CN110431805A (zh) * 2017-03-20 2019-11-08 高通股份有限公司 经由控制平面信令的策略通信

Also Published As

Publication number Publication date
CN105594165B (zh) 2019-07-09
US11178057B2 (en) 2021-11-16
EP3182654A4 (en) 2017-10-18
CN110461012B (zh) 2022-09-02
EP3668023B1 (en) 2022-06-08
CN110461012A (zh) 2019-11-15
US20170180259A1 (en) 2017-06-22
ES2926077T3 (es) 2022-10-21
EP3182654B1 (en) 2019-11-06
CN105594165A (zh) 2016-05-18
EP3182654A1 (en) 2017-06-21
EP3668023A1 (en) 2020-06-17

Similar Documents

Publication Publication Date Title
CN110461012B (zh) 一种分流策略协商方法及装置
US10462229B2 (en) Method and apparatus for initiating and maintaining sessions between endpoints
JP5010690B2 (ja) セキュリティ機能ネゴシエーション方法、システム、および装置
JP6074520B2 (ja) オープンフロー可能なWiFi管理エンティティアーキテクチャ
US9717019B2 (en) Data flow control method, and related device and communications system
TWI583154B (zh) 對無線裝置經由多個無線存取來支援基於網路之ip流移動率的方法及設備
WO2020034864A1 (zh) 一种用户面安全策略实现方法、装置及系统
WO2014124602A1 (zh) 网络接入处理方法和用户设备
JP2014520439A (ja) Wlanとwwanとの間で対話するための方法、ユーザ装置、および基地局
US10484910B2 (en) Traffic flow splitting method and apparatus
WO2014134975A2 (zh) 一种数据流传输方法及装置
KR102176428B1 (ko) 무선 랜으로 미디어 전송 시 사용자 체감 서비스 품질을 높이는 방법 및 장치
WO2016011832A1 (zh) 一种关于流迁移触发的相关实现方法、设备及存储介质
WO2015158285A1 (zh) 一种ip流路由规则的确定方法和设备
WO2016106702A1 (zh) 业务流分流方法及装置
Ahmed et al. Multi access data network connectivity and IP flow mobility in Evolved Packet System (EPS)
WO2011157106A2 (zh) 一种实现业务数据流分流的方法、系统及相关装置
WO2024001524A1 (zh) 一种通信方法及装置
WO2012065293A1 (zh) 业务的接入控制方法、装置及用户设备

Legal Events

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

Ref document number: 14901168

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2014901168

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2014901168

Country of ref document: EP