WO2015196599A1 - 流量控制方法及装置 - Google Patents

流量控制方法及装置 Download PDF

Info

Publication number
WO2015196599A1
WO2015196599A1 PCT/CN2014/087125 CN2014087125W WO2015196599A1 WO 2015196599 A1 WO2015196599 A1 WO 2015196599A1 CN 2014087125 W CN2014087125 W CN 2014087125W WO 2015196599 A1 WO2015196599 A1 WO 2015196599A1
Authority
WO
WIPO (PCT)
Prior art keywords
traffic
pgw
layer application
upper layer
monitoring
Prior art date
Application number
PCT/CN2014/087125
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 US15/321,197 priority Critical patent/US20170163545A1/en
Priority to EP14895969.5A priority patent/EP3160184B1/en
Publication of WO2015196599A1 publication Critical patent/WO2015196599A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2416—Real-time traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
    • H04L12/1471—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network splitting of costs
    • H04L12/1475—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network splitting of costs the splitting involving a third party
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1485—Tariff-related aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/20—Traffic policing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2475—Traffic characterised by specific attributes, e.g. priority or QoS for supporting traffic characterised by the type of applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/803—Application aware
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/822—Collecting or measuring resource availability data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/07—Split billing, i.e. both A-party and B-party charged for the communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/64—On-line charging system [OCS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8016—Rating or billing plans; Tariff determination aspects based on quality of service [QoS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing

Definitions

  • the present invention relates to the field of communications, and in particular to a flow control method and apparatus.
  • the Gy interface is mainly used for real-time charging in the 3rd Generation Partnership Project (3GPP) network architecture, which can partially meet the demand for traffic control, but since OCS is only for some users, it cannot consider all users, and it is not for traffic. Defined by control. Therefore, the interface cannot meet the flow control requirements of all users.
  • 3GPP 3rd Generation Partnership Project
  • FIG. 1 is an architecture diagram of performing policy control by adding a Sy interface in 3GPP according to the related art.
  • the Policy and Charging Rules Function can be used to report the current policy counter as the control capability interface of the OCS to the service policy (for example, the OCS can select which service policy is currently used).
  • the Sy interface is only used for policy control, and no traffic is reported or flow control is performed. If the PCRF is not reported, the OCS side cannot control the policy. At the same time, the PCRF can still adopt the local policy.
  • the upper layer service has no control right. Therefore, the user side can still use the traffic in the network layer, and the over-traffic usage still exists.
  • the upper application or application function AF
  • the entity can control the PCRF through the Rx interface. However, it is only used to implement policy delivery, so there is still no specific flow control function.
  • the Sy protocol itself is only used to report real-time policy monitoring, but it cannot deliver traffic fragments and monitor in the service layer such as AF.
  • the Rx interface also focuses on the control of the source and destination used by the user and the quality of service (QOS), but it cannot control the traffic of the service.
  • the present invention provides a flow control method and apparatus to at least solve the problem that the application cannot implement fine control of traffic in the related art.
  • a flow control method is provided.
  • the flow control method includes: receiving a service request from the PGW and an Internet access policy corresponding to the service requirement; and obtaining flow control information from the upper-layer application according to the service requirement and the Internet access policy, where the flow control information includes: to be monitored The policy counter status information and the traffic slice corresponding to the policy counter status information; the policy counter status information and the traffic slice are sent to the PGW.
  • the obtaining the flow control information from the upper layer application according to the service requirement and the Internet access policy comprises: sending a spending request (SLR) message to the upper layer application according to the service requirement and the Internet access policy; and receiving the expenditure response (SLA) corresponding to the SLR message from the upper layer application. a message, wherein the SLA message carries flow control information.
  • SLR spending request
  • SLA expenditure response
  • the method further includes: receiving a result of using the traffic slice reported by the PGW and requesting a service request of the next traffic slice; and reporting the usage result of the traffic slice to the The upper layer application, and obtains the next traffic slice from the upper layer application according to the service request.
  • the method further includes: when determining that all the traffic fragments delivered to the PGW are used and the PGW no longer applies for a new traffic slice, using the PGW
  • the result of the last traffic slice is reported to the upper application, and a session abort request (STR) message is sent to the upper layer application; a session abort response (STA) message is received from the upper application, and the flow control of the PGW is stopped.
  • STR session abort request
  • STA session abort response
  • the method further includes: receiving a expenditure status notification (SNR) message from the upper layer application, where the SNR message is used to indicate the policy counter The status information and the traffic slice are adjusted; the PGW is notified to adjust the policy counter status information and the traffic slice; after determining that the PGW completes the adjustment of the policy counter status information and the traffic slice, the upper layer application returns a Payment Status Notification Response (SNA) message.
  • SNR expenditure status notification
  • SNA Payment Status Notification Response
  • the flow control information is obtained from the upper layer application via the extended Sy interface
  • the extended Sy interface includes: usage monitoring information (Usage-Monitoring-Information)
  • the Usage-Monitoring-Information includes: object monitoring value (Monitoring-Key) Used to determine policy counter status information; Granted-Service-Unit for carrying traffic slices; Used-Service-Unit for reporting the results of traffic slices; Usage monitoring report (Usage) -Monitoring-Report), which is used by the upper-layer application to actively query the number of used traffic slices; Usage-Monitoring-Support is used for the upper-layer application to actively close traffic monitoring.
  • usage monitoring information Usage-Monitoring-Information
  • the Usage-Monitoring-Information includes: object monitoring value (Monitoring-Key) Used to determine policy counter status information; Granted-Service-Unit for carrying traffic slices; Used-Service-Unit for reporting the results of traffic slices; Usage monitoring report (Usage) -Monitoring
  • a flow control device is provided.
  • the flow control device includes: a first receiving module, configured to receive a service request from the PGW and an Internet access policy corresponding to the service requirement; and the first acquiring module is configured to apply from the upper layer according to the service requirement and the Internet access policy.
  • Obtaining flow control information where the flow control information includes: policy counter status information to be monitored and a traffic slice corresponding to the policy counter status information; and a sending module, configured to send the policy counter status information and the traffic slice to the PGW.
  • the first obtaining module includes: a sending unit, configured to send an SLR message to the upper layer application according to the service requirement and the Internet access policy; and the receiving unit is configured to receive an SLA message corresponding to the SLR message from the upper layer application, where the SLA message It carries flow control information.
  • the device further includes: a second receiving module, configured to receive a result of using the traffic slice reported by the PGW and requesting a service request of the next traffic slice; and the second acquiring module is configured to report the use result of the traffic slice Go to the upper application and get the next traffic slice to the upper application based on the service request.
  • a second receiving module configured to receive a result of using the traffic slice reported by the PGW and requesting a service request of the next traffic slice
  • the second acquiring module is configured to report the use result of the traffic slice Go to the upper application and get the next traffic slice to the upper application based on the service request.
  • the device further includes: a sending module, configured to use the last traffic slice used by the PGW in the case that all the traffic slices sent to the PGW are used and the PGW no longer applies for a new traffic slice.
  • the report is sent to the upper layer application, and the STR message is sent to the upper layer application.
  • the third receiving module is configured to receive the STA message from the upper layer application, and stop the flow control on the PGW.
  • the apparatus further includes: a fourth receiving module, configured to receive an SNR message from an upper layer application, where the SNR message is used to indicate adjustment of policy counter status information and a traffic slice; and the notification module is configured to notify the PGW pair Policy counter status information and traffic slice are adjusted; feedback module, set to be After the PGW completes the adjustment of the policy counter status information and the traffic slice, the upper layer application returns an SNA message.
  • a fourth receiving module configured to receive an SNR message from an upper layer application, where the SNR message is used to indicate adjustment of policy counter status information and a traffic slice
  • the notification module is configured to notify the PGW pair Policy counter status information and traffic slice are adjusted
  • feedback module set to be After the PGW completes the adjustment of the policy counter status information and the traffic slice, the upper layer application returns an SNA message.
  • the first obtaining module is configured to acquire flow control information from the upper layer application via the extended Sy interface, where the extended Sy interface includes: Usage-Monitoring-Information, and Usage-Monitoring-Information includes: Monitoring-Key, Determine the status of the policy counter; the Granted-Service-Unit is used to carry the traffic slice; the Used-Service-Unit is used to report the usage result of the traffic slice; and the Usage-Monitoring-Report is used by the upper application to actively query the used traffic. The number of slices; Usage-Monitoring-Support, for upper-layer applications to actively close traffic monitoring.
  • the extended Sy interface includes: Usage-Monitoring-Information
  • Usage-Monitoring-Information includes: Monitoring-Key, Determine the status of the policy counter
  • the Granted-Service-Unit is used to carry the traffic slice
  • the Used-Service-Unit is used to report the usage result of the traffic slice
  • the Usage-Monitoring-Report is used by the upper application to
  • the traffic control information is obtained from the upper-layer application according to the service requirement and the Internet access policy, and the traffic control information includes: the policy counter status to be monitored, according to the embodiment of the present invention, the service request from the PGW and the Internet access policy corresponding to the service requirement are received.
  • the information and the traffic slice corresponding to the policy counter status information; the policy counter status information and the traffic fragment are sent to the PGW, which solves the problem that the application cannot implement the fine control of the traffic in the related technology, and obtains fine traffic at the application layer.
  • the technological advancement of the control has achieved the effect of open flow control on the upper layer application, saving unnecessary network layer overhead and investment, and improving the ability of the system to rapidly deploy traffic refined applications.
  • 1 is an architectural diagram of performing policy control by adding a Sy interface in 3GPP according to the related art
  • FIG. 2 is a flow chart of a flow control method according to an embodiment of the present invention.
  • 3 is an architectural diagram of performing flow control by adding a Sy' interface in 3GPP according to an embodiment of the present invention
  • FIG. 4 is a block diagram showing the structure of a flow control device according to an embodiment of the present invention.
  • Figure 5 is a block diagram showing the structure of a flow control device in accordance with a preferred embodiment of the present invention.
  • FIG. 2 is a flow chart of a flow control method in accordance with an embodiment of the present invention. As shown in FIG. 2, the method may include the following processing steps:
  • Step S202 Receive a service request from the PGW and an Internet access policy corresponding to the service requirement.
  • Step S204 Obtain flow control information from the upper-layer application according to the service requirement and the Internet access policy, where the flow control information includes: policy counter status information to be monitored and a traffic slice corresponding to the policy counter status information;
  • Step S206 The policy counter status information and the traffic slice are sent to the PGW.
  • the Sy interface has been proposed in the 3GPP, it is mainly used for interactive control of traffic service rules, and there is no related flow control function, and the Rx interface is mainly used for AF control of QOS related bearers.
  • the Rx interface is mainly used for AF control of QOS related bearers.
  • it is not flow control, which makes it impossible to implement fine-grained control of traffic in related technologies.
  • the policy counter status information to be monitored and the policy counter status information corresponding to the OCS and the upper layer application other than the OFCS are obtained by the service request received from the PGW and the Internet access policy corresponding to the service request.
  • the traffic slice is sent to the PGW by the obtained policy counter status information and the traffic slice to implement the flow control requirement of the upper layer service.
  • the extended Sy protocol is referred to as a Sy' protocol, that is, a Sy extended protocol.
  • the flow control information is obtained from the upper layer application via the extended Sy interface, where the extended Sy interface may include: usage monitoring information (Usage-Monitoring-Information);
  • the Usage-Monitoring-Information may include but is not limited to the following:
  • Usage-Monitoring-Support is used to actively close traffic monitoring in the upper layer application.
  • an extended Sy interface can be added between the PCRF and the upper layer application, and the Sy protocol is extended to implement the flow control requirement of the upper layer service.
  • the related upper layer application and PCRF need to be modified to support the above extended SY' interface protocol and related logic processing.
  • Configure related counters on the PCRF side can be configured according to different service policies, usually using a package scheme). After the user goes online, the PCRF applies the traffic counter and the corresponding traffic slice through the extended Sy interface.
  • the upper layer application controls the subsequent counters and the corresponding traffic slices to be delivered according to the internal logic.
  • obtaining the flow control information from the upper application according to the service requirement and the Internet access policy may include the following operations:
  • Step S1 Send an SLR message to the upper layer application according to the service requirement and the Internet access policy
  • Step S2 Receive an SLA message corresponding to the SLR message from the upper layer application, where the SLA message carries the flow control information.
  • the user accesses the Internet via the mobile terminal.
  • the PGW obtains the Internet access policy and service from the PCRF through the Gx interface.
  • the PCRF obtains the flow control information through the Sy' interface to the upper layer service, where the flow control information may include, but is not limited to, a counter to be monitored (the service may be carried in a Policy-Counter-Identifier), and the used message is an SLR.
  • the upper-layer service sends a counter to be monitored (Policy-Counter-Statues) and delivers the traffic slice (carried in the Granted-Service-Unit AVP).
  • the PCRF delivers user policies and available traffic fragments to the PGW based on the traffic fragments delivered by the service and the service requirements.
  • the following operations may also be included:
  • Step S3 receiving the use result of the traffic slice reported by the PGW and requesting the service request of the next traffic slice;
  • step S4 the usage result of the traffic slice is reported to the upper layer application, and the next traffic slice is acquired by the upper layer application according to the service request.
  • the upper layer applies the traffic slice, and the PCRF and the PGW on the network side allow the user to use the network traffic according to the traffic slice.
  • the PGW and the PCRF need to apply for the next traffic slice through the Sy interface.
  • the new traffic slice is obtained, the user can continue to use the service normally. That is, after the PGW uses the currently delivered traffic slice, the traffic usage result is reported, and the PCRF passes through the Sy' interface.
  • the upper-layer application reports the traffic result (for example, it can be reported through the Used-Service-Unit parameter), and the upper-layer application continues to deliver the new traffic slice.
  • the following operations may also be included:
  • Step S5 When it is determined that all the traffic slices sent to the PGW are used and the PGW no longer applies for a new traffic slice, the usage result of the last traffic slice used by the PGW is reported to the upper application, and is sent to the upper application. STR message;
  • Step S6 Receive the STA message from the upper application, and stop the flow control on the PGW.
  • the PGW reports the last traffic slice, and the PCRF sends a Session-Termination-Request (STR) message to the upper-layer service to indicate that the service is offline.
  • STR Session-Termination-Request
  • the result of the use of the last traffic slice is reported to the upper application.
  • the upper layer application returns a Session-Termination-Answer (STA) message and performs internal settlement.
  • STA Session-Termination-Answer
  • step S206 After the policy counter status information and the traffic slice are sent to the PGW in step S206, the following steps may be further included:
  • Step S7 receiving an SNR message from an upper layer application, where the SNR message is used to indicate that the policy counter status information and the traffic slice are adjusted;
  • Step S8 Notifying the PGW to adjust the policy counter status information and the traffic slice;
  • Step S9 After determining that the PGW completes adjustment of the policy counter status information and the traffic slice, the upper layer application returns an SNA message.
  • the upper layer service can adjust the counter and the corresponding traffic slice at any time according to its own service characteristics (through the SNR message), and the PCRF will send the corresponding control content to the PGW according to the indication in the above message to indicate The PGW adjusts accordingly.
  • FIG. 3 is an architectural diagram of performing flow control by adding a Sy' interface in 3GPP according to an embodiment of the present invention.
  • the upper layer application can control the PCRF through the Sy' interface and deliver the traffic slice through the PCRF, so that precise control of the user's usage flow can be realized.
  • the protocol extension is as follows:
  • the protocol extension needs to modify the PCRF side to increase the extension of the new parameter of Usage-Monitoring-Information and the corresponding logic processing.
  • Spending-Limit-Request SLR
  • Spending-Limit-Answer SLA
  • Spending-Status-Notification-Request SNR
  • An attribute value pair AVP is respectively extended in the Spending-Status-Notification-Answer (SNA) message: *[Usage-Monitoring-Information], where *[Usage-Monitoring-Information] This can include, but is not limited to, the following:
  • Monitoring-Key is an extended AVP, based on the relevant definition in the Sy protocol, in order to identify which counter (a certain policy) is subscribed.
  • the Monitoring-Key can be set equal to the Policy-Counter-Identifier
  • Granted-Service-Unit is used to deliver quota fragments to upper-layer services.
  • Used-Service-Unit is used for PCRF reporting
  • Usage-Monitoring-Report is used to carry this AVP when the upper-layer service wants to actively query the usage.
  • Usage-Monitoring-Support is used to carry this AVP when the upper-layer service wants to actively shut down the usage monitoring. It is set to DISABLED.
  • the flow control device can be applied to the PCRF.
  • the flow control device may include: a first receiving module 100, configured to receive a service request from the PGW and an Internet access policy corresponding to the service requirement; and the first obtaining module 102 is configured to meet the service requirement and access the Internet.
  • the policy obtains flow control information from an upper application, where the flow control information includes: The policy counter status information to be monitored and the traffic slice corresponding to the policy counter status information; the sending module 104 is configured to send the policy counter status information and the traffic slice to the PGW.
  • the device shown in FIG. 4 is used to solve the problem that the application can not realize the fine control of the flow in the related art, and the technical progress of the fine control of the flow at the application layer is achieved, and the effect of the open flow control on the upper layer application is achieved. It saves unnecessary network layer overhead and investment, and improves the ability of the system to rapidly deploy traffic refined applications.
  • the first obtaining module 102 is configured to obtain flow control information from an upper layer application via an extended Sy interface, where the extended Sy interface may include: usage monitoring information (Usage-Monitoring-Information);
  • the Usage-Monitoring-Information may include but is not limited to the following:
  • Usage-Monitoring-Support is used to actively close traffic monitoring in the upper layer application.
  • the first obtaining module 102 may include: a sending unit 1020, configured to send an SLR message to the upper layer application according to the service requirement and the Internet access policy; and the receiving unit 1022 is configured to receive the SLR from the upper application.
  • the foregoing apparatus may further include: a second receiving module 106, configured to receive a result of using the traffic slice reported by the PGW and requesting a service request of the next traffic slice; and the second obtaining module 108, setting To report the usage result of the traffic slice to the upper-layer application, and obtain the next traffic slice from the upper-layer application according to the service request.
  • a second receiving module 106 configured to receive a result of using the traffic slice reported by the PGW and requesting a service request of the next traffic slice
  • the second obtaining module 108 setting To report the usage result of the traffic slice to the upper-layer application, and obtain the next traffic slice from the upper-layer application according to the service request.
  • the foregoing apparatus may further include: a sending module 110, configured to use the PGW when all the traffic slices sent to the PGW are determined to be used and the PGW no longer applies for a new traffic slice.
  • the result of the use of the last traffic slice is reported to the upper layer application, and the STR message is sent to the upper layer application;
  • the third receiving module 112 is configured to receive the STA message from the upper layer application, and stop the flow control on the PGW.
  • the foregoing apparatus may further include: a fourth receiving module 114, configured to receive an SNR message from an upper layer application, where the SNR message is used to indicate that the policy counter status information and the traffic slice are adjusted;
  • the notification module 116 is configured to notify the PGW to adjust the policy counter status information and the traffic slice.
  • the feedback module 118 is configured to return an SNA message to the upper layer application after determining that the PGW completes the adjustment of the policy counter status information and the traffic slice.
  • the Sy interface enables the upper-layer application to obtain direct control over the traffic used by the user, so that the flexible Internet application can obtain the flow control of the user through the above interface (for example, the application of the traffic card type).
  • the technical progress of fine-grained control of the traffic at the application layer is achieved, the effect of open flow control on the upper layer application is achieved, the unnecessary network layer overhead and investment are saved, and the ability of the system to rapidly deploy the traffic refined application is improved.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the flow control method and apparatus have the following beneficial effects: by extending the Sy interface, the upper layer application obtains a direct control function for the user to use the traffic, thereby obtaining the traffic at the application layer.
  • the technical advancement of refined control has achieved the effect of open flow control on the upper layer application, saving unnecessary network layer overhead and investment, and improving the ability of the system to rapidly deploy traffic refined applications.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Quality & Reliability (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明公开了一种流量控制方法及装置，在上述方法中，接收来自于PGW的业务要求以及与业务要求对应的上网策略；按照业务要求和上网策略从上层应用获取流量控制信息，其中，流量控制信息包括：待监控的策略计数器状态信息以及与策略计数器状态信息对应的流量片；将策略计数器状态信息和流量片下发至PGW。根据本发明提供的技术方案，达到了对上层应用开放流量控制的效果，节省了不必要的网络层的开销及投资，提高了系统快速部署流量精细化应用的能力。

Description

流量控制方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及一种流量控制方法及装置。
背景技术
随着移动通讯技术的迅猛发展，在用户采用移动终端上网的过程中对高带宽的要求已经实现，例如：在第三代移动通信技术(3G)或第四代移动通信技术(4G)网络中，带宽已经可以达到数兆甚至上百兆。但是，伴随着网速的提升所诱发的问题在于：如果缺乏对网络流量的实时监控机制，很可能会出现用户在完全不知情的情况下超流量使用却未被告知，由此产生过度的移动通信费用的开销。
相关技术中通常对网络流量采用以下几种计费模式：
(1)粗放式的计费模式；
(2)采用准实时的话单结算；
(3)通过在线计费系统(OCS)与网关GPRS支持节点(GGSN)/分组数据网网关(PGW)之间的Gy接口进行实时监控。
但是，采用准实时的话单结算存在延迟现象，很容易造成超流量使用。Gy接口在第三代合作伙伴计划(3GPP)网络架构中主要用于实时计费，其可以部分满足对流量控制的需求，但由于OCS仅针对部分用户而无法顾及全部用户，且其并非为了流量控制而定义。因此该接口无法满足全部用户的流量控制需求。
对于灵活多变的互联网应用，现有的技术架构已经无法满足各行业对用户流量的精细化控制要求。3GPP中提出了流量业务规则控制的概念，图1是根据相关技术的通过在3GPP中增加Sy接口执行策略控制的架构图。如图1所示，通过增加一个Sy接口可以要求策略与计费规则功能(PCRF)上报当前的策略计数器，作为OCS对业务策略的控制能力接口(例如：OCS可以选择当前使用哪个业务策略)。但是在上述协议中，Sy接口仅用于策略控制，而并没有进行流量上报，也没有进行流量控制，即PCRF如果不上报的话，那么OCS侧也无法控制策略；同时PCRF仍可以采用本地的策略而不需要获得OCS的确认。上层业务就更没有控制权，因此，用户侧仍然可以使用网络层中的流量，超流量使用的情况依旧存在。另外，上层应用或应用功能(AF) 实体可以通过Rx接口对PCRF进行控制。但其也仅用于执行策略下发，因此，仍缺乏具体的流量控制功能。
由此可见，Sy协议本身仅用于对实时策略监控进行上报，却无法下发流量片以及在AF等业务层实现监控。Rx接口也仅关注于对用户使用的源和目的地以及服务质量(QOS)的相关控制，却无法实现业务对流量的控制。
综上所述，相关技术中无法实现应用对流量的精细化控制，从而无法从根本上解决目前存在的粗放式流量控制。
发明内容
本发明提供了一种流量控制方法及装置，以至少解决相关技术中无法实现应用对流量的精细化控制的问题。
根据本发明的一个方面，提供了一种流量控制方法。
根据本发明实施例的流量控制方法包括：接收来自于PGW的业务要求以及与业务要求对应的上网策略；按照业务要求和上网策略从上层应用获取流量控制信息，其中，流量控制信息包括：待监控的策略计数器状态信息以及与策略计数器状态信息对应的流量片；将策略计数器状态信息和流量片下发至PGW。
优选地，按照业务要求和上网策略从上层应用获取流量控制信息包括：根据业务要求和上网策略向上层应用发送支出请求(SLR)消息；接收来自于上层应用的与SLR消息对应的支出响应(SLA)消息，其中，SLA消息中携带有流量控制信息。
优选地，在将策略计数器状态信息和流量片下发至PGW之后，还包括：接收PGW上报的对流量片的使用结果以及申请下一个流量片的业务请求；将对流量片的使用结果上报至上层应用，并根据业务请求向上层应用获取下一个流量片。
优选地，在将策略计数器状态信息和流量片下发至PGW之后，还包括：在确定向PGW下发的全部流量片均使用完毕且PGW不再申请新的流量片的情况下，将PGW使用的最后一个流量片的使用结果上报至上层应用，并向上层应用发送会话中止请求(STR)消息；接收来自于上层应用的会话中止响应(STA)消息，停止对PGW进行流量控制。
优选地，在将策略计数器状态信息和流量片下发至PGW之后，还包括：接收来自于上层应用的支出状态通知(SNR)消息，其中，SNR消息用于指示对策略计数器 状态信息和流量片进行调整；通知PGW对策略计数器状态信息和流量片进行调整；在确定PGW完成对策略计数器状态信息和流量片进行调整之后，向上层应用返回支出状态通知响应(SNA)消息。
优选地，经由扩展的Sy接口从上层应用获取流量控制信息，其中，扩展的Sy接口包括：用量监控信息(Usage-Monitoring-Information)，Usage-Monitoring-Information包括：对象监控值(Monitoring-Key)，用于确定策略计数器状态信息；可用量(Granted-Service-Unit)，用于携带流量片；已用量(Used-Service-Unit)，用于上报对流量片的使用结果；用量监控报告(Usage-Monitoring-Report)，用于上层应用主动查询已经使用的流量片的数量；用量监控通知(Usage-Monitoring-Support)，用于上层应用主动关闭流量监控。
根据本发明的另一方面，提供了一种流量控制装置。
根据本发明实施例的流量控制装置包括：第一接收模块，设置为接收来自于PGW的业务要求以及与业务要求对应的上网策略；第一获取模块，设置为按照业务要求和上网策略从上层应用获取流量控制信息，其中，流量控制信息包括：待监控的策略计数器状态信息以及与策略计数器状态信息对应的流量片；下发模块，设置为将策略计数器状态信息和流量片下发至PGW。
优选地，第一获取模块包括：发送单元，设置为根据业务要求和上网策略向上层应用发送SLR消息；接收单元，设置为接收来自于上层应用的与SLR消息对应的SLA消息，其中，SLA消息中携带有流量控制信息。
优选地，上述装置还包括：第二接收模块，设置为接收PGW上报的对流量片的使用结果以及申请下一个流量片的业务请求；第二获取模块，设置为将对流量片的使用结果上报至上层应用，并根据业务请求向上层应用获取下一个流量片。
优选地，上述装置还包括：发送模块，设置为在确定向PGW下发的全部流量片均使用完毕且PGW不再申请新的流量片的情况下，将PGW使用的最后一个流量片的使用结果上报至上层应用，并向上层应用发送STR消息；第三接收模块，设置为接收来自于上层应用的STA消息，停止对PGW进行流量控制。
优选地，上述装置还包括：第四接收模块，设置为接收来自于上层应用的SNR消息，其中，SNR消息用于指示对策略计数器状态信息和流量片进行调整；通知模块，设置为通知PGW对策略计数器状态信息和流量片进行调整；反馈模块，设置为在确 定PGW完成对策略计数器状态信息和流量片进行调整之后，向上层应用返回SNA消息。
优选地，第一获取模块，设置为经由扩展的Sy接口从上层应用获取流量控制信息，其中，扩展的Sy接口包括：Usage-Monitoring-Information，Usage-Monitoring-Information包括：Monitoring-Key，用于确定策略计数器状态信息；Granted-Service-Unit，用于携带流量片；Used-Service-Unit，用于上报对流量片的使用结果；Usage-Monitoring-Report，用于上层应用主动查询已经使用的流量片的数量；Usage-Monitoring-Support，用于上层应用主动关闭流量监控。
通过本发明实施例，采用接收来自于PGW的业务要求以及与业务要求对应的上网策略；按照业务要求和上网策略从上层应用获取流量控制信息，其中，流量控制信息包括：待监控的策略计数器状态信息以及与策略计数器状态信息对应的流量片；将策略计数器状态信息和流量片下发至PGW，解决了相关技术中无法实现应用对流量的精细化控制的问题，取得了在应用层对流量精细化控制的技术进步，达到了对上层应用开放流量控制的效果，节省了不必要的网络层的开销及投资，提高了系统快速部署流量精细化应用的能力。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据相关技术的通过在3GPP中增加Sy接口执行策略控制的架构图；
图2是根据本发明实施例的流量控制方法的流程图；
图3是根据本发明实施例的通过在3GPP中增加Sy’接口执行流量控制的架构图；
图4是根据本发明实施例的流量控制装置的结构框图；
图5是根据本发明优选实施例的流量控制装置的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
图2是根据本发明实施例的流量控制方法的流程图。如图2所示，该方法可以包括以下处理步骤：
步骤S202：接收来自于PGW的业务要求以及与业务要求对应的上网策略；
步骤S204：按照业务要求和上网策略从上层应用获取流量控制信息，其中，流量控制信息包括：待监控的策略计数器状态信息以及与策略计数器状态信息对应的流量片；
步骤S206：将策略计数器状态信息和流量片下发至PGW。
相关技术中在3GPP中虽然已经提出了Sy接口，但是其主要用于进行流量业务规则的交互控制，并未存在相关的流量控制功能，而Rx接口则主要用于AF对QOS相关承载的控制，但却不是流量控制，从而导致相关技术中无法实现应用对流量的精细化控制。采用如图2所示的方法，通过从PGW接收到的业务要求以及与业务要求对应的上网策略向OCS以及OFCS之外的上层应用获取待监控的策略计数器状态信息以及与策略计数器状态信息对应的流量片，然后再将获取到的策略计数器状态信息和流量片下发至PGW，以实现上层业务对流量控制的需求。由此解决了相关技术中无法实现应用对流量的精细化控制的问题，取得了在应用层对流量精细化控制的技术进步，达到了对上层应用开放流量控制的效果，节省了不必要的网络层的开销及投资，提高了系统快速部署流量精细化应用的能力。
需要说明的是，在本发明提供的以下优选实施例中将扩展后的Sy协议称为Sy’协议，即Sy扩展协议。
在优选实施过程中，经由扩展的Sy接口从上层应用获取流量控制信息，其中，扩展的Sy接口可以包括：用量监控信息(Usage-Monitoring-Information)；
该Usage-Monitoring-Information可以包括但不限于以下内容：
(1)对象监控值(Monitoring-Key)，用于确定策略计数器状态信息；
(2)可用量(Granted-Service-Unit)，用于携带流量片；
(3)已用量(Used-Service-Unit)，用于上报对流量片的使用结果；
(4)用量监控报告(Usage-Monitoring-Report)，用于上层应用主动查询已经使用的流量片的数量；
(5)用量监控通知(Usage-Monitoring-Support)，用于上层应用主动关闭流量监控。
在优选实施例中，可以在PCRF与上层应用之间增加扩展的Sy接口，通过扩展Sy协议，可以实现上层业务对流量控制的需求。相关的上层应用及PCRF需要进行改造，支持上述扩展SY’接口协议及相关的逻辑处理。在PCRF侧配置相关的计数器(可以根据不同的业务策略进行配置，通常采用套餐方案)。在用户上线后，由PCRF通过扩展Sy接口对流量计数器及对应的流量片进行申请。上层应用根据内部逻辑控制后续的计数器及对应的流量片下发。
优选地，在步骤S204中，按照业务要求和上网策略从上层应用获取流量控制信息可以包括以下操作：
步骤S1：根据业务要求和上网策略向上层应用发送SLR消息；
步骤S2：接收来自于上层应用的与SLR消息对应的SLA消息，其中，SLA消息中携带有流量控制信息。
在优选实施例中，用户通过移动终端上网。PGW通过Gx接口向PCRF获取上网策略及业务。PCRF通过Sy’接口向上层业务获取流量控制信息，其中，该流量控制信息可以包括但不限于：待监控的计数器(业务，可以携带在Policy-Counter-Identifier)，所采用的消息为SLR。上层业务下发待监控的计数器(Policy-Counter-Statues)，同时下发流量片(携带在Granted-Service-Unit这个AVP)。PCRF根据业务下发的流量片并结合业务要求向PGW下发用户策略以及可用流量片。
优选地，在步骤S206，将策略计数器状态信息和流量片下发至PGW之后，还可以包括以下操作：
步骤S3：接收PGW上报的对流量片的使用结果以及申请下一个流量片的业务请求；
步骤S4：将对流量片的使用结果上报至上层应用，并根据业务请求向上层应用获取下一个流量片。
在优选实施例中，上层应用下发流量片，网络侧的PCRF以及PGW根据上述流量片允许用户使用网络流量。当流量片使用完毕后，PGW以及PCRF需要通过Sy接口申请下一个流量片，在获取到新的流量片之后，用户才能够继续正常使用业务。即在PGW对当前下发的流量片使用完毕后，上报流量使用结果，PCRF通过Sy’接口向 上层应用上报流量结果(例如：可以通过Used-Service-Unit参数上报)，而上层应用再继续下发新的流量片。
优选地，在步骤S206，将策略计数器状态信息和流量片下发至PGW之后，还可以包括以下操作：
步骤S5：在确定向PGW下发的全部流量片均使用完毕且PGW不再申请新的流量片的情况下，将PGW使用的最后一个流量片的使用结果上报至上层应用，并向上层应用发送STR消息；
步骤S6：接收来自于上层应用的STA消息，停止对PGW进行流量控制。
在优选实施例中，用户在使用结束下线后，PGW上报最后一个流量片，PCRF向上层业务发送会话中止请求(Session-Termination-Request，简称为STR)消息，以表示业务下线，同时将最后一个流量片的使用结果上报至上层应用。上层应用返回会话中止响应(Session-Termination-Answer，简称为STA)消息，并进行内部结算。
优选地，在步骤S206，将策略计数器状态信息和流量片下发至PGW之后，还可以包括以下步骤：
步骤S7：接收来自于上层应用的SNR消息，其中，SNR消息用于指示对策略计数器状态信息和流量片进行调整；
步骤S8：通知PGW对策略计数器状态信息和流量片进行调整；
步骤S9：在确定PGW完成对策略计数器状态信息和流量片进行调整之后，向上层应用返回SNA消息。
在优选实施例中，上层业务可以根据自身的业务特点，随时对计数器及对应的流量片进行调整(通过SNR消息)，PCRF将根据上述消息中的指示，下发相应的控制内容给PGW以指示PGW进行相应地调整。
下面将结合图3所示的优选实施方式对上述优选实施过程作进一步的描述。
图3是根据本发明实施例的通过在3GPP中增加Sy’接口执行流量控制的架构图。如图3所示，上层应用可以通过Sy’接口控制PCRF，并通过PCRF下发流量片，从而可以实现对用户使用流量的精确控制。通过扩展Sy’接口，使得上层应用具备对用户使用流量的控制能力成为可能。协议扩展方式如下：
该协议扩展需要对PCRF侧进行修改，增加对用量监控信息(Usage-Monitoring-Information)这个新增参数的扩展及相应的逻辑处理。对标准Sy协议中的支出请求(Spending-Limit-Request，简称为SLR)，支出响应(Spending-Limit-Answer，简称为SLA)，支出状态通知(Spending-Status-Notification-Request，简称为SNR)，支出状态通知响应(Spending-Status-Notification-Answer，简称为SNA)消息中分别扩展一个属性值对(AVP)：即*[Usage-Monitoring-Information]，其中，*[Usage-Monitoring-Information]可以包括但不限于以下内容：
Usage-Monitoring-Information::＝<AVP Header:1067>
                [Monitoring-Key]
                [Granted-Service-Unit]
                [Used-Service-Unit]
                [Usage-Monitoring-Report]
                [Usage-Monitoring-Support]
               *[AVP]
需要说明的是，上述对象监控值(Monitoring-Key)为扩展AVP，基于Sy协议中的相关定义，为了标识订阅的是哪种计数器(某种策略)。
Monitoring-Key可设置为与策略计数标识(Policy-Counter-Identifier)相等；
可用量(Granted-Service-Unit)用于上层业务下发配额分片；
已用量(Used-Service-Unit)用于PCRF上报用量；
用量监控报告(Usage-Monitoring-Report)用于在上层业务希望主动查询用量时，携带此AVP；
用量监控通知(Usage-Monitoring-Support)用于在上层业务希望主动关闭用量监控时，携带此AVP，其设置为非使能(DISABLED)。
图4是根据本发明实施例的流量控制装置的结构框图。该流量控制装置可以应用于PCRF中。如图4所示，该流量控制装置可以包括：第一接收模块100，设置为接收来自于PGW的业务要求以及与业务要求对应的上网策略；第一获取模块102，设置为按照业务要求和上网策略从上层应用获取流量控制信息，其中，流量控制信息包括： 待监控的策略计数器状态信息以及与策略计数器状态信息对应的流量片；下发模块104，设置为将策略计数器状态信息和流量片下发至PGW。
采用如图4所示的装置，解决了相关技术中无法实现应用对流量的精细化控制的问题，取得了在应用层对流量精细化控制的技术进步，达到了对上层应用开放流量控制的效果，节省了不必要的网络层的开销及投资，提高了系统快速部署流量精细化应用的能力。
在优选实施过程中，第一获取模块102，设置为经由扩展的Sy接口从上层应用获取流量控制信息，其中，扩展的Sy接口可以包括：用量监控信息(Usage-Monitoring-Information)；
该Usage-Monitoring-Information可以包括但不限于以下内容：
(1)对象监控值(Monitoring-Key)，用于确定策略计数器状态信息；
(2)可用量(Granted-Service-Unit)，用于携带流量片；
(3)已用量(Used-Service-Unit)，用于上报对流量片的使用结果；
(4)用量监控报告(Usage-Monitoring-Report)，用于上层应用主动查询已经使用的流量片的数量；
(5)用量监控通知(Usage-Monitoring-Support)，用于上层应用主动关闭流量监控。
优选地，如图5所示，第一获取模块102可以包括：发送单元1020，设置为根据业务要求和上网策略向上层应用发送SLR消息；接收单元1022，设置为接收来自于上层应用的与SLR消息对应的SLA消息，其中，SLA消息中携带有流量控制信息。
优选地，如图5所示，上述装置还可以包括：第二接收模块106，设置为接收PGW上报的对流量片的使用结果以及申请下一个流量片的业务请求；第二获取模块108，设置为将对流量片的使用结果上报至上层应用，并根据业务请求向上层应用获取下一个流量片。
优选地，如图5所示，上述装置还可以包括：发送模块110，设置为在确定向PGW下发的全部流量片均使用完毕且PGW不再申请新的流量片的情况下，将PGW使用的最后一个流量片的使用结果上报至上层应用，并向上层应用发送STR消息；第三接收模块112，设置为接收来自于上层应用的STA消息，停止对PGW进行流量控制。
优选地，如图5所示，上述装置还可以包括：第四接收模块114，设置为接收来自于上层应用的SNR消息，其中，SNR消息用于指示对策略计数器状态信息和流量片进行调整；通知模块116，设置为通知PGW对策略计数器状态信息和流量片进行调整；反馈模块118，设置为在确定PGW完成对策略计数器状态信息和流量片进行调整之后，向上层应用返回SNA消息。
从以上的描述中，可以看出，上述实施例实现了如下技术效果(需要说明的是这些效果是某些优选实施例可以达到的效果)：采用本发明实施例所提供的技术方案，通过扩展Sy接口，使得上层应用获得了对用户使用流量的直接控制功能，这样，灵活的互联网应用就可以通过上述接口来获取到对用户的流量控制(例如：流量卡类的应用)。由此取得了在应用层对流量精细化控制的技术进步，达到了对上层应用开放流量控制的效果，节省了不必要的网络层的开销及投资，提高了系统快速部署流量精细化应用的能力。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，本发明实施例提供的一种流量控制方法及装置具有以下有益效果：通过扩展Sy接口，使得上层应用获得了对用户使用流量的直接控制功能，由此取得了在应用层对流量精细化控制的技术进步，达到了对上层应用开放流量控制的效果，节省了不必要的网络层的开销及投资，提高了系统快速部署流量精细化应用的能力。

Claims (12)

  1. 一种流量控制方法，包括：
    接收来自于分组数据网网关PGW的业务要求以及与所述业务要求对应的上网策略；
    按照所述业务要求和所述上网策略从上层应用获取流量控制信息，其中，所述流量控制信息包括：待监控的策略计数器状态信息以及与所述策略计数器状态信息对应的流量片；
    将所述策略计数器状态信息和所述流量片下发至所述PGW。
  2. 根据权利要求1所述的方法，其中，按照所述业务要求和所述上网策略从所述上层应用获取所述流量控制信息包括：
    根据所述业务要求和所述上网策略向所述上层应用发送支出请求SLR消息；
    接收来自于所述上层应用的与所述SLR消息对应的支出响应SLA消息，其中，所述SLA消息中携带有所述流量控制信息。
  3. 根据权利要求1所述的方法，其中，在将所述策略计数器状态信息和所述流量片下发至所述PGW之后，还包括：
    接收所述PGW上报的对所述流量片的使用结果以及申请下一个流量片的业务请求；
    将对所述流量片的使用结果上报至所述上层应用，并根据所述业务请求向所述上层应用获取所述下一个流量片。
  4. 根据权利要求3所述的方法，其中，在将所述策略计数器状态信息和所述流量片下发至所述PGW之后，还包括：
    在确定向所述PGW下发的全部流量片均使用完毕且所述PGW不再申请新的流量片的情况下，将所述PGW使用的最后一个流量片的使用结果上报至所述上层应用，并向所述上层应用发送会话中止请求STR消息；
    接收来自于所述上层应用的会话中止响应STA消息，停止对所述PGW进行流量控制。
  5. 根据权利要求4所述的方法，其中，在将所述策略计数器状态信息和所述流量片下发至所述PGW之后，还包括：
    接收来自于所述上层应用的支出状态通知SNR消息，其中，所述SNR消息用于指示对所述策略计数器状态信息和所述流量片进行调整；
    通知所述PGW对所述策略计数器状态信息和所述流量片进行调整；
    在确定所述PGW完成对所述策略计数器状态信息和所述流量片进行调整之后，向所述上层应用返回支出状态通知响应SNA消息。
  6. 根据权利要求1至5中任一项所述的方法，其中，经由扩展的Sy接口从上层应用获取所述流量控制信息，其中，所述扩展的Sy接口包括：用量监控信息Usage-Monitoring-Information，所述Usage-Monitoring-Information包括：
    对象监控值Monitoring-Key，用于确定所述策略计数器状态信息；
    可用量Granted-Service-Unit，用于携带所述流量片；
    已用量Used-Service-Unit，用于上报对所述流量片的使用结果；
    用量监控报告Usage-Monitoring-Report，用于所述上层应用主动查询已经使用的流量片的数量；
    用量监控通知Usage-Monitoring-Support，用于所述上层应用主动关闭流量监控。
  7. 一种流量控制装置，包括：
    第一接收模块，设置为接收来自于分组数据网网关PGW的业务要求以及与所述业务要求对应的上网策略；
    第一获取模块，设置为按照所述业务要求和所述上网策略从上层应用获取流量控制信息，其中，所述流量控制信息包括：待监控的策略计数器状态信息以及与所述策略计数器状态信息对应的流量片；
    下发模块，设置为将所述策略计数器状态信息和所述流量片下发至所述PGW。
  8. 根据权利要求7所述的装置，其中，所述第一获取模块包括：
    发送单元，设置为根据所述业务要求和所述上网策略向所述上层应用发送支出请求SLR消息；
    接收单元，设置为接收来自于所述上层应用的与所述SLR消息对应的支出响应SLA消息，其中，所述SLA消息中携带有所述流量控制信息。
  9. 根据权利要求7所述的装置，其中，所述装置还包括：
    第二接收模块，设置为接收所述PGW上报的对所述流量片的使用结果以及申请下一个流量片的业务请求；
    第二获取模块，设置为将对所述流量片的使用结果上报至所述上层应用，并根据所述业务请求向所述上层应用获取所述下一个流量片。
  10. 根据权利要求9所述的装置，其中，所述装置还包括：
    发送模块，设置为在确定向所述PGW下发的全部流量片均使用完毕且所述PGW不再申请新的流量片的情况下，将所述PGW使用的最后一个流量片的使用结果上报至所述上层应用，并向所述上层应用发送会话中止请求STR消息；
    第三接收模块，设置为接收来自于所述上层应用的会话中止响应STA消息，停止对所述PGW进行流量控制。
  11. 根据权利要求10所述的装置，其中，所述装置还包括：
    第四接收模块，设置为接收来自于所述上层应用的支出状态通知SNR消息，其中，所述SNR消息用于指示对所述策略计数器状态信息和所述流量片进行调整；
    通知模块，设置为通知所述PGW对所述策略计数器状态信息和所述流量片进行调整；
    反馈模块，设置为在确定所述PGW完成对所述策略计数器状态信息和所述流量片进行调整之后，向所述上层应用返回支出状态通知响应SNA消息。
  12. 根据权利要求7至11中任一项所述的装置，其中，所述第一获取模块，设置为经由扩展的Sy接口从上层应用获取所述流量控制信息，其中，所述扩展的Sy接口包括：用量监控信息Usage-Monitoring-Information，所述Usage-Monitoring-Information包括：
    对象监控值Monitoring-Key，用于确定所述策略计数器状态信息；
    可用量Granted-Service-Unit，用于携带所述流量片；
    已用量Used-Service-Unit，用于上报对所述流量片的使用结果；
    用量监控报告Usage-Monitoring-Report，用于所述上层应用主动查询已经使用的流量片的数量；
    用量监控通知Usage-Monitoring-Support，用于所述上层应用主动关闭流量监控。
PCT/CN2014/087125 2014-06-23 2014-09-22 流量控制方法及装置 WO2015196599A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/321,197 US20170163545A1 (en) 2014-06-23 2014-09-22 Traffic Control Method and Apparatus
EP14895969.5A EP3160184B1 (en) 2014-06-23 2014-09-22 Traffic control method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410284595.8A CN104053186B (zh) 2014-06-23 2014-06-23 流量控制方法及装置
CN201410284595.8 2014-06-23

Publications (1)

Publication Number Publication Date
WO2015196599A1 true WO2015196599A1 (zh) 2015-12-30

Family

ID=51505452

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/087125 WO2015196599A1 (zh) 2014-06-23 2014-09-22 流量控制方法及装置

Country Status (4)

Country Link
US (1) US20170163545A1 (zh)
EP (1) EP3160184B1 (zh)
CN (1) CN104053186B (zh)
WO (1) WO2015196599A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109150764A (zh) * 2017-06-16 2019-01-04 中兴通讯股份有限公司 流量管理方法、装置、设备及存储介质

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105682001A (zh) * 2014-11-17 2016-06-15 中兴通讯股份有限公司 基于4g网络的流量红包控制方法及系统
CN106332036A (zh) * 2015-06-23 2017-01-11 中兴通讯股份有限公司 消费配额监控方法及装置
US11197202B2 (en) * 2016-02-17 2021-12-07 Nec Corporation System and method for operating a wireless network
CN108512770B (zh) * 2017-02-28 2020-10-23 华为技术有限公司 数据流量分配方法及相关设备
CN110858982B (zh) 2018-08-22 2022-01-14 华为技术有限公司 流量/速率统计方法以及相关设备
CN111225013A (zh) * 2018-11-27 2020-06-02 华为技术有限公司 一种传输策略确定方法、策略控制方法及装置
CN109413675A (zh) * 2018-12-05 2019-03-01 斑马网络技术有限公司 车联网流量控制方法、装置及车载终端
CN112312338B (zh) * 2019-07-26 2022-03-01 中国电信股份有限公司 网速控制方法、装置、系统和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102075897A (zh) * 2009-11-20 2011-05-25 中国移动通信集团江苏有限公司 一种移动数据业务的计费方法和系统
CN102984768A (zh) * 2012-11-09 2013-03-20 华为技术有限公司 一种实时调整共享计费规则下在线用户带宽的方法及装置
CN103716765A (zh) * 2012-09-29 2014-04-09 阿尔卡特朗讯公司 策略和在线计费控制系统
CN103843374A (zh) * 2011-10-03 2014-06-04 阿尔卡特朗讯公司 基于sy的集成的策略和计费控制

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101516109B (zh) * 2008-02-21 2010-11-03 大唐移动通信设备有限公司 一种流量控制方法、系统及装置
US9332133B2 (en) * 2010-12-09 2016-05-03 Allot Communications Ltd. System, device, and method of traffic detection
CN103477587B (zh) * 2011-04-27 2017-03-29 阿尔卡特朗讯 用于控制访客用户的qos和/或策略和计费控制的方法和设备
WO2013103960A1 (en) * 2012-01-05 2013-07-11 Tekelec, Inc. Methods, systems, and computer readable media for utilizing quota usage policy control in a diameter-based communication network
JP6437911B2 (ja) * 2012-03-21 2018-12-12 インターデイジタル パテント ホールディングス インコーポレイテッド ワイヤレスネットワークにおいて移動局セッションを別の移動局によって資金援助すること
US9860323B2 (en) * 2012-05-15 2018-01-02 At&T Intellectual Property I, L.P. System and apparatus for providing policy control and charging to support communications
US9912488B2 (en) * 2012-05-15 2018-03-06 At&T Intellectual Property I, L.P. System and apparatus for providing subscriber management to support communications
US8995305B2 (en) * 2012-08-29 2015-03-31 Alcatel Lucent Sy session creation and recovering from inconsistent session state between PCRF and OCS
CN103686652A (zh) * 2012-08-31 2014-03-26 阿尔卡特朗讯 在vplmn中为漫游用户设备进行独立漫游计费的方法与设备
US9185237B2 (en) * 2013-03-15 2015-11-10 Tekelec, Inc. Methods, systems, and computer readable media for adjusting a quota consumption rate
EP2947816B1 (en) * 2013-04-24 2018-01-17 Huawei Technologies Co., Ltd. Method for charging for application, and charging device and system
WO2015014396A1 (en) * 2013-07-31 2015-02-05 Telefonaktiebolaget L M Ericsson (Publ) Confidence degree of data packet flow classification
US20150244537A1 (en) * 2014-02-23 2015-08-27 Tata Communications (America) Inc. System and methods for enabling policy exchange across multiple carriers

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102075897A (zh) * 2009-11-20 2011-05-25 中国移动通信集团江苏有限公司 一种移动数据业务的计费方法和系统
CN103843374A (zh) * 2011-10-03 2014-06-04 阿尔卡特朗讯公司 基于sy的集成的策略和计费控制
CN103716765A (zh) * 2012-09-29 2014-04-09 阿尔卡特朗讯公司 策略和在线计费控制系统
CN102984768A (zh) * 2012-11-09 2013-03-20 华为技术有限公司 一种实时调整共享计费规则下在线用户带宽的方法及装置

Non-Patent Citations (1)

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

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109150764A (zh) * 2017-06-16 2019-01-04 中兴通讯股份有限公司 流量管理方法、装置、设备及存储介质
CN109150764B (zh) * 2017-06-16 2023-07-18 中兴通讯股份有限公司 流量管理方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN104053186A (zh) 2014-09-17
EP3160184B1 (en) 2019-10-30
US20170163545A1 (en) 2017-06-08
EP3160184A4 (en) 2017-08-02
CN104053186B (zh) 2018-12-04
EP3160184A1 (en) 2017-04-26

Similar Documents

Publication Publication Date Title
WO2015196599A1 (zh) 流量控制方法及装置
US10764727B2 (en) Method for charging inter-PLMN roaming data service online, and device
US8630925B2 (en) Method and apparatus for controlling service traffic in a communication network
US11601555B2 (en) Methods and apparatuses for service layer charging correlation with underlying networks
CN104429103B (zh) 用于基于策略的本地分流(lbo)的方法、系统和计算机可读介质
US20150289167A1 (en) System and method for orchestrating policy in a mobile environment
JP6213972B2 (ja) アプリケーション課金方法、デバイス、およびシステム
CN104685919A (zh) 用于无线接入网(ran)的拥塞控制
MX2012013659A (es) Servicios asistidos por dispositivo para proteger la capacidad de una red.
CN103843374B (zh) 基于sy的集成的策略和计费控制
US20140376412A1 (en) Method and apparatus for performing charging control to application-layer data
JP2016526357A (ja) Ｐｃｒｆを決定するための方法および装置
US20210234966A1 (en) Adaptive quota allocation
US10257366B2 (en) Method, system and apparatus for managing communication sessions using joint storage
WO2015143851A1 (zh) 用量监控方法、装置和系统
US8706080B2 (en) Charging correlation for dedicated bearers
US20180309584A1 (en) Data Service Charging Method, Apparutus, and System
WO2012083779A1 (zh) 策略控制方法及装置
US20170134178A1 (en) Charging Method, Charging Device, and Charging System
WO2016107374A1 (zh) 一种带宽控制的方法、装置及系统
WO2017084394A1 (zh) 漫游计费方法、相关装置及在线计费系统
EP3618468B1 (en) Wireless communication method and device
WO2017161522A1 (zh) 流量使用量统计方法、装置及系统
CN109417683B (zh) 中间网络交通转向的核心网络在线计费控制
WO2015142229A1 (en) Method and apparatus for control of communication services

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

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

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2014895969

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 15321197

Country of ref document: US