WO2016054777A1 - 一种背景流量下载方法、设备及系统 - Google Patents

一种背景流量下载方法、设备及系统 Download PDF

Info

Publication number
WO2016054777A1
WO2016054777A1 PCT/CN2014/088156 CN2014088156W WO2016054777A1 WO 2016054777 A1 WO2016054777 A1 WO 2016054777A1 CN 2014088156 W CN2014088156 W CN 2014088156W WO 2016054777 A1 WO2016054777 A1 WO 2016054777A1
Authority
WO
WIPO (PCT)
Prior art keywords
background traffic
policy
download
user group
downloading
Prior art date
Application number
PCT/CN2014/088156
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 PCT/CN2014/088156 priority Critical patent/WO2016054777A1/zh
Priority to CN201480081842.2A priority patent/CN106688256B/zh
Publication of WO2016054777A1 publication Critical patent/WO2016054777A1/zh
Priority to US15/482,532 priority patent/US10211995B2/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403Architecture for metering, charging or billing
    • H04L12/1407Policy-and-charging control [PCC] architecture
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1453Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
    • H04L12/1457Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network using an account
    • 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/27Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/1063Application servers providing network services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66Policy and charging system
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24Accounting or billing

Definitions

  • the present invention relates to the field of communications, and in particular, to a background traffic downloading method, device, and system.
  • the basic telecommunications business market has expanded and matured.
  • Many users in the government and enterprise industries connect to the carrier network through a third-party application server, and use the public network for user group communication.
  • the user group mentioned here is composed of all user terminals or partial user terminals of the industry users under the third-party application server.
  • each user terminal in the user group will go to the third party.
  • the application server sends a background traffic download request, and the third-party application server forwards the background traffic download request to the PCRF (Policy and Charging Rule Function) in the carrier network, where the PCRF is in the user group.
  • PCRF Policy and Charging Rule Function
  • Each user terminal separately formulates a background traffic downloading policy, and according to the background traffic downloading policy of each user terminal, formulates a specific network transmission policy that can satisfy the background traffic download request of the user group, that is, formulates each user terminal for background traffic downloading. Policy control and billing control.
  • the background traffic that needs to be downloaded by the user terminal in a group may be the same.
  • the PCRF needs to repeatedly respond to the same background traffic download request forwarded by the third-party application server, resulting in unnecessary network. Overhead.
  • the embodiment of the invention provides a background traffic downloading method, device and system, which solves the problem that the background traffic downloading for the same user group, the policy making unit repeatedly responds, and the network overhead is large.
  • a background traffic download method comprising:
  • the network-aware scheduling device receives the background traffic download request message sent by the application server, where the background traffic download request message carries the demand information required for the background traffic download of the user group;
  • the network-aware scheduling device receives the identifier of the background traffic downloading policy sent by the policy and the charging and formulating device, and determines the background traffic downloading policy of the user group according to the identifier of the background traffic downloading policy, where the The background traffic download policy is sent to the policy and charging device, so that the policy and charging device determines the policy and charging control of the background traffic download according to the background traffic download policy.
  • the demand information includes at least one of the following: a traffic value required for the user group to perform background traffic download, a time window required for the user group to perform background traffic download, and an area of the user group. information.
  • the allowed download time window the billing information of a single user terminal, the maximum download rate of a single user terminal, the maximum value of the aggregate download rate of the user group, and the charging policy at different aggregate download rates.
  • the background traffic download policy includes the allowed download time window; wherein the user group performs background traffic downloading Time window includes the allowed download time window;
  • the background traffic download policy includes a maximum value of the aggregate download rate of the user group or the user group. Maximum download rate of a single user terminal; wherein the maximum value of the aggregate download rate of the user group or the maximum download rate of a single user terminal in the user group is used by the user group for background traffic downloading The value is determined.
  • the demand information includes a time window required for the user group to perform background traffic downloading
  • the method further includes: before the network-aware scheduling device generates the background traffic downloading policy of the user group and the identifier of the background traffic downloading policy according to the requirement information, the method further includes:
  • the network aware scheduling device determines that the network can satisfy the background traffic download request of the application server within a time window required for the user group to perform background traffic download.
  • a background traffic download method comprising:
  • the policy and charging setting device receives a background traffic download enable request sent by the application server, where the background traffic download enable request carries an identifier of the background traffic download policy of the user group;
  • the policy and charging setting device determines the policy and charging control of the background traffic download according to the background traffic downloading policy.
  • the background traffic download enable request further includes an IP address of each user terminal in the user group that needs to download background traffic, Policy and billing development equipment
  • the background traffic download policy determines the policy and charging control for background traffic downloading including:
  • the policy and the charging and formulating device determine, according to the background traffic downloading policy, the IP addresses of the user terminals that need to download the background traffic in the user group, and determine, for each user terminal in the user group that needs to download background traffic.
  • the method further includes:
  • the policy and charging device sends the policy and charging control to the policy and charging execution device, so that the policy and charging executing device allocates bearer resources for background traffic download according to the policy and charging control.
  • a background traffic download method comprising:
  • the application server sends a background traffic download request message to the network-aware scheduling device, where the background traffic download request message carries the demand information required for the background traffic download of the user group;
  • the application server sends a background traffic download enable request to the policy and billing setting device, where the background traffic download enable request carries the identifier of the background traffic download policy, so that the policy and billing device performs the background traffic according to the background traffic.
  • the download enable request acquires the background traffic download policy of the user group, and determines the policy and charging control of the background traffic download.
  • the requirement information includes at least one of the following information: a traffic value required for the user group to perform background traffic download, the user The time window required for the group to perform background traffic download, and the area information of the user group.
  • the method further includes:
  • the application server acquires the demand information.
  • the method further includes:
  • the application server acquires an IP address of each user terminal in the user group that needs to download background traffic
  • the background traffic download enablement request further includes an IP address of each user terminal in the user group that needs to download background traffic.
  • a network sensing and scheduling device including:
  • a receiving unit configured to receive a background traffic download request message sent by the application server, where the background traffic download request message carries requirement information required for background traffic downloading of the user group;
  • a generating unit configured to generate, according to the requirement information, a background traffic downloading policy of the user group and an identifier of the background traffic downloading policy
  • a sending unit configured to send, to the application server, an identifier of the background traffic downloading policy
  • the receiving unit is further configured to receive an identifier of the background traffic download policy sent by the policy and the charging and formulating device;
  • a determining unit configured to determine, according to the identifier of the background traffic downloading policy, the background traffic downloading policy of the user group;
  • the sending unit is further configured to send the background traffic downloading policy to the policy and charging setting device, so that the policy and charging setting device determines a background traffic downloading policy and a meter according to the background traffic downloading policy. Fee control.
  • a policy and charging device including:
  • a sending unit configured to send the identifier of the background traffic downloading policy to a network sense Know scheduling equipment
  • the receiving unit is further configured to receive a background traffic downloading policy of the user group returned by the network aware scheduling device;
  • a generating unit configured to determine a policy and charging control of the background traffic download according to the background traffic downloading policy.
  • an application server including:
  • a sending unit configured to send a background traffic download request message to the network-aware scheduling device, where the background traffic download request message carries requirement information required for background traffic downloading of the user group;
  • a receiving unit configured to receive an identifier of a background traffic download policy of the user group sent by the network aware scheduling device
  • the sending unit is further configured to: send a background traffic download enable request to the policy and charging setting device, where the background traffic download enable request carries the identifier of the background traffic download policy, so that the policy and charging device is configured according to the
  • the background traffic download enablement request acquires a background traffic download policy of the user group, and determines a policy and charging control of the background traffic download.
  • a network sensing and scheduling device including:
  • a receiver configured to receive a background traffic download request message sent by the application server, where the background traffic download request message carries required information required for background traffic downloading of the user group;
  • a processor configured to generate, according to the requirement information, a background traffic download policy of the user group and an identifier of the background traffic download policy
  • a transmitter configured to send an identifier of the background traffic download policy to the application server
  • the receiver is further configured to receive an identifier of the background traffic download policy sent by the policy and the charging and formulating device;
  • the processor is configured to determine, according to the identifier of the background traffic download policy, the background traffic download policy of the user group;
  • the transmitter is further configured to send the background traffic download policy to the policy And the billing setting device, so that the policy and billing setting device determines the policy and charging control of the background traffic download according to the background traffic downloading policy.
  • a policy and charging device including:
  • a receiver configured to receive a background traffic download enable request sent by the application server, where the background traffic download enable request carries an identifier of a background traffic download policy of the user group;
  • a transmitter configured to send an identifier of the background traffic download policy to a network aware scheduling device
  • the receiver is further configured to receive a background traffic downloading policy of the user group returned by the network aware scheduling device;
  • the processor is configured to determine a policy and charging control of the background traffic download according to the background traffic downloading policy.
  • an application server including:
  • a transmitter configured to send a background traffic download request message to the network aware scheduling device, where the background traffic download request message carries required information required for background traffic downloading of the user group;
  • a receiver configured to receive an identifier of a background traffic download policy of the user group sent by the network aware scheduling device
  • the transmitter is further configured to send a background traffic download enable request to the policy and charging device, where the background traffic download enable request carries the identifier of the background traffic download policy, so that the policy and the charging device are
  • the background traffic download enablement request acquires a background traffic download policy of the user group, and determines a policy and charging control of the background traffic download.
  • a system including: a network aware scheduling device, a policy and charging formulation device, and an application server,
  • the network-aware scheduling device is the network-aware scheduling device according to the fourth aspect of the foregoing technical solution.
  • the policy and charging setting device is a policy and charging device according to the fifth aspect of the foregoing technical solution.
  • the application server is the application server described in the sixth aspect of the technical solution.
  • the network-aware scheduling device is the network-aware scheduling device according to the seventh aspect of the foregoing technical solution
  • the policy and charging setting device is a policy and charging device according to the eighth aspect of the foregoing technical solution.
  • the application server is the application server described in the ninth aspect of the technical solution.
  • the application server determines the demand information of the user group, and sends a background traffic download request carrying the demand information to the network aware scheduling device.
  • the network aware scheduling device receives the background traffic download request message sent by the application server, and generates a background traffic download policy for the group.
  • the application server forwards the background traffic download request of each user terminal in the group to the policy and charging device, and the policy and charging device generates background traffic for each user terminal in the group. Download strategy.
  • the network side of the present invention sets a background traffic downloading policy for the group, and does not need to formulate a background traffic downloading policy for each user terminal in the group, that is, avoiding the network side repeatedly responding to the same request from the application server.
  • the application server determines the IP address of the user terminal in the group that needs to download the background traffic, so that the policy and charging setting device generates policy and charging control for the user terminal that needs to download the background traffic, and finally implements the device by the policy and charging control.
  • the bearer resource is allocated to the user terminal that needs to download the background traffic, so that the application server transmits data to the user terminal that needs to download the background traffic. Avoid network congestion due to simultaneous transmission of data to each user terminal in the group.
  • FIG. 1 is a structural diagram of a background traffic management system according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of a background traffic downloading method according to Embodiment 1 of the present invention. intention;
  • FIG. 3 is a schematic flowchart of another background traffic downloading method according to Embodiment 1 of the present invention.
  • FIG. 4 is a schematic flowchart diagram of another background traffic downloading method according to Embodiment 1 of the present invention.
  • FIG. 5 is a schematic flowchart diagram of another background traffic downloading method according to Embodiment 2 of the present invention.
  • FIG. 6 is a schematic flowchart diagram of a background traffic downloading method according to Embodiment 4 of the present invention.
  • FIG. 7 is a schematic diagram of an application server according to Embodiment 5 of the present invention.
  • FIG. 8 is a schematic diagram of a network aware scheduling device according to Embodiment 5 of the present invention.
  • FIG. 9 is a schematic diagram of a policy and charging device according to Embodiment 5 of the present invention.
  • FIG. 10 is a schematic diagram of a background traffic downloading apparatus according to an embodiment of the present invention.
  • FIG. 1 it is a system architecture of SAE (System Architecture Evolution) in 3GPP, which can implement management of background traffic resources.
  • the system may include: a Mobility Management Entity (MME), a RAN payload schedule function (RPSF), a Policy and Charging Rule Function (PCRF), and an application server.
  • MME Mobility Management Entity
  • RPSF RAN payload schedule function
  • PCRF Policy and Charging Rule Function
  • AS can be a third-party server
  • the network capability open layer
  • UE User Equipment
  • the MME is responsible for mobility management of the control plane, such as user context and mobility state management, and assigning user temporary identity identifiers; PCRF for policy control rule formulation and flow-based charging; UE is controlling plane with SAE
  • the user equipment interacts with the terminal device; the RPSF uses network status information (real-time information and historical information) to collect, analyze, and predict, and supports resource scheduling and load control for the application server access service (such as background traffic service).
  • the RPSF is connected to the PCRF through the Np interface, and is connected to the mobility management network element through the Nq interface.
  • the industrial users (which can be users in the government and enterprise related industries) can use the application server to connect to the carrier network through the carrier's network capability open layer.
  • the network capability open layer can perform the opening of the operator network capability, and the application server can be a three-party server, such as a government, public security, fire, traffic, or other enterprise dedicated server.
  • the background traffic downloading in the embodiment of the present invention refers to a non-emergency (can be transmitted when the network is idle) data transmission, and the server may transmit non-emergency data to the user equipment during a relatively idle period of the network.
  • the data may be upgraded data for the application, data of the push message, and the like.
  • the PCRF will formulate a background traffic download policy for each user terminal.
  • the data requested by each user terminal may be the same, and the time window of the request may be the same. This means that the PCRF needs to respond repeatedly (develop multiple multiple background traffic download strategies) and increase network overhead.
  • the download time windows determined by the network side for each user terminal are the same, the network side simultaneously initiates background traffic transmission to each user terminal. If there are a large number of user terminals in the adjacent area, and the network side transmits data to each user terminal at the same time, it is likely to cause congestion of the network in the area.
  • the method provided by the embodiment of the present invention is to formulate a background traffic downloading policy for the group, so as to prevent the PCRF from repeatedly responding to requests from the application server, and avoid network congestion caused by the background traffic downloading service.
  • the embodiment of the present invention further provides a background traffic downloading method, where the execution subject may be a network-aware scheduling device, and the network-aware scheduling device may be a network-aware scheduling unit RPSF deployed on an operator network, as shown in FIG. 2
  • the method includes the following steps:
  • the network-aware scheduling device receives the background traffic download request message sent by the application server, where the background traffic download request message carries the demand information required for the background traffic download of the user group.
  • the requirement information includes at least one of the following information: a traffic value required for the user group to perform background traffic download, a time window required for the user group to perform background traffic download, and the user group.
  • the user group is one of a plurality of user groups served by the application server.
  • the network-aware scheduling device may collect status information of the carrier network to determine whether the carrier network supports the background traffic download request of the application server (the application server is the background traffic download request initiated by the first group).
  • Background traffic download is a non-emergency (can be transmitted when the network is idle) data service transmission, such as upgrading the terminal application, updating the terminal database, message push, and the like.
  • the network-aware scheduling device generates, according to the requirement information, a background traffic download policy of the user group and an identifier of the background traffic download policy.
  • the network aware scheduling device can formulate a background traffic downloading policy for the user group.
  • the background traffic downloading policy is a policy information for the user group to perform background traffic downloading, and the background traffic downloading policy is used to provide a group service for the user group, which satisfies the background traffic downloading requirement of each user terminal.
  • the network aware scheduling unit creates a background traffic downloading policy for background traffic downloading for the user group, and does not need to generate a background traffic downloading policy for each user terminal, thereby avoiding the operator's policy unit (strategy and The billing device) responds repeatedly to requests of the same type from the application server.
  • the identifier of the background traffic download policy is related to the background The unique identifier of the traffic downloading policy, that is, the identifier corresponding to the different background traffic downloading policies is different.
  • the network-aware scheduling device only needs to determine the background traffic downloading policy according to the identifier of the background traffic downloading policy.
  • the application server may correspond to multiple groups, after the network-aware scheduling device generates a corresponding background traffic download policy for the background traffic download service of each group, a unique corresponding policy identifier is generated for each background traffic download policy, so that A background traffic download policy can be quickly locked based on the policy ID.
  • the background traffic downloading policy may further include the identifier information of the user group, and the background traffic downloading policy corresponding to the identifier of the background traffic downloading policy may be determined by the network-aware scheduling device as the user group group. The group performs the background traffic download strategy generated by the background traffic download.
  • the network aware scheduling device sends an identifier of the background traffic download policy to the application server.
  • the network aware scheduling device may send the policy identifier to the application server through an open platform.
  • the open platform ie, the network capability open layer exposure layer
  • the open platform may have a protocol conversion function.
  • the network aware scheduling device sends the policy identifier to the application server, so that the application server includes the policy identifier in the background traffic download enable request and sends the policy identifier to the policy and billing device.
  • the network-aware scheduling device receives the identifier of the background traffic download policy sent by the policy and the charging device, and determines the background traffic download policy of the user group according to the identifier of the background traffic download policy.
  • the background traffic downloading policy is sent to the policy and charging device, so that the policy and charging device determines the policy and charging control of the background traffic download according to the background traffic downloading policy.
  • the policy and charging setting device may be a policy and charging formulating unit PCRF.
  • the policy and charging setting device receives the background traffic downloading policy sent by the network-aware scheduling device, the policy and the device for downloading the background traffic according to the background traffic downloading policy are generated. Fee control, that is, to determine energy A specific network transmission policy that satisfies the background traffic download request of the user group.
  • the policy and charging setting device then sends the policy and charging control to the policy and charging control device.
  • the policy and charging control device allocates a bearer resource for the background traffic download of the user group according to the policy and charging control.
  • the application server transmits data to each user terminal.
  • the network aware scheduling device may have a corresponding background traffic downloading policy for multiple groups. In this way, the network-aware scheduling device can uniquely determine a background traffic download policy according to the policy identifier sent by the policy and the charging-making device.
  • the background traffic downloading policy includes at least one of the following information:
  • the allowed download time window the billing information of a single user terminal, the maximum download rate of a single user terminal, the maximum value of the aggregate download rate of the user group, and the charging policy at different aggregate download rates.
  • the allowable download time window may be an allowed download time window, or may be a time window determined by other factors, which is not limited herein.
  • the background traffic downloading strategy may be the following:
  • the allowed download time window the maximum download rate of a single user, and the billing information of a single user.
  • the allowed download time window, the maximum value of the aggregate download rate of the user group, and the charging policy at different aggregate download rates may be: a charging policy when the aggregate downloading rate is less than or equal to a maximum value, and a charging policy when the aggregated downloading rate is greater than a maximum value.
  • the method further includes:
  • the background traffic downloading policy includes the allowed download time window; wherein the time window required for the user group to perform background traffic downloading includes the allowed download time window. It may also be that the allowed download time window is included in a time window required for the user group to perform background traffic download.
  • the background traffic download policy includes a maximum value of the aggregate download rate of the user group or a single user in the user group.
  • the maximum download rate of the terminal wherein the maximum value of the aggregate download rate of the user group or the maximum download rate of a single user terminal in the user group is determined by the traffic value required for the background traffic download by the user group .
  • the network aware scheduling device determines the maximum value of the aggregate download rate of the user group. If the traffic value required for background traffic downloading by the user group is a unit traffic value of background traffic downloading by a single user terminal in the user group, and the number of user terminals in the user group, the network sensing The scheduling device determines a maximum download rate of the single user terminal in the user group according to the unit flow value and the allowed download time window.
  • the network aware scheduling unit determines whether the network can satisfy the user group according to the network status of the area corresponding to the area information of the user group. Group of background traffic download requests.
  • the demand information includes a time window required for the user group to perform background traffic downloading.
  • the method further includes: before the network-aware scheduling unit generates the background traffic downloading policy of the user group and the identifier of the background traffic downloading policy according to the requirement information, the method further includes:
  • the network aware scheduling unit determines whether the network satisfies the background traffic download of the application server within a time window required for the user group to perform background traffic downloading request. If the network-aware scheduling unit determines that the network can satisfy the background traffic download request of the application server within a time window required for the user group to perform background traffic downloading, performing the “generating the content according to the requirement information.
  • the background traffic download policy of the user group and the identifier of the background traffic download policy are examples of the background traffic download policy.
  • the network aware scheduling unit determines that the network cannot satisfy the background traffic download request of the application server within a time window required for the user group to perform background traffic downloading.
  • the network aware scheduling unit generates a message indicating that the policy generation fails, and sends the message indicating that the policy generation fails to the application server.
  • the method further includes:
  • the network-aware scheduling unit sends the timing information to the application server, so that the application server sends the background traffic download request message to the network-aware scheduling unit through the open platform after the timing information is separated.
  • the network aware scheduling device after receiving the background traffic download request message sent by the application server to establish the background traffic download service for the user group, performs background traffic download according to the user group.
  • the status of the demand information and the network determines whether the network can satisfy the background traffic download request of the application server (the background traffic download request initiated by the application server for the user group).
  • After determining that the network can meet the background traffic download request of the user group generate a background traffic download policy for the user group, and generate a policy identifier of the background traffic download policy, so as to determine the user group according to the policy identifier.
  • Group background traffic download strategy After receiving the background traffic download request message sent by the application server to establish the background traffic download service for the user group, the network aware scheduling device performs background traffic download according to the user group.
  • the status of the demand information and the network determines whether the network can satisfy the background traffic download request of the application server (the background traffic download request initiated by the application server for the user group).
  • the network-aware scheduling device (which may be the network-aware scheduling unit RPSF) generates a background traffic downloading policy for a user group, and does not need to generate a background traffic downloading policy for each user terminal, thereby saving network overhead. .
  • the embodiment of the present invention further provides a background traffic downloading method, where the execution entity is a policy and charging device, and the policy and charging device may be deployed in an operator.
  • the policy and accounting unit PCRF of the network as shown in FIG. 3, the method includes the following steps:
  • the policy and charging setting device receives a background traffic download enable request sent by the application server, where the background traffic download enable request carries an identifier of a background traffic download policy of the user group.
  • the premise is that the network-aware scheduling device determines that the network can meet the background traffic download request of the user group, and formulates a background traffic download policy for the user group, and sends the identifier of the background traffic download policy to the application server. The application server then sends a background traffic download enable request to the policy and billing device.
  • the policy and charging setting device sends the identifier of the background traffic downloading policy to the network aware scheduling device.
  • the policy and the charging and formulating device request the background traffic downloading policy of the user group from the network aware scheduling device according to the identifier of the background traffic downloading policy included in the background traffic downloading and enabling request.
  • the policy and charging device sends the identifier of the background traffic downloading policy to the network-aware scheduling device, so that the network-aware scheduling device generates multiple background traffic download policies (for different user groups).
  • the background traffic download policy generated by the background traffic download service may determine a background traffic download policy according to the identifier of the background traffic download policy included in the background traffic download enable request, that is, the network aware scheduling device performs background for the user group. Background traffic download strategy generated by traffic download.
  • the policy and charging setting device receives a background traffic downloading policy of the user group returned by the network aware scheduling device.
  • the previous background traffic downloading policy and the identifier of the background traffic downloading policy are generated for the user group, because the network aware scheduling device performs the background traffic downloading required information according to the user group.
  • the identifier of the background traffic download policy may include the identification information of the user group. Therefore, the policy and charging device determines that the background traffic download policy is the background flow corresponding to the user group according to the identifier information of the group included in the identifier of the background traffic download policy. Volume download strategy.
  • the policy and charging setting device determines a policy and charging control for background traffic download according to the background traffic downloading policy.
  • the policy and charging setting device determines a specific network transmission policy according to a background traffic downloading policy generated by the network aware scheduling device for the user group.
  • the policy and charging control may include many parameters, some of which are responsible for charging, and some of which are responsible for other control.
  • the policy and charging control may have only a part of the parameters.
  • the policy and charging device is configured.
  • the policy control and charging control required to generate the user group for background traffic downloading includes:
  • the policy and the charging and formulating device determine, according to the background traffic downloading policy, the IP addresses of the user terminals that need to download the background traffic in the user group, and determine, for each user terminal in the user group that needs to download background traffic.
  • the policy and charging setting device sends the policy and charging control to the policy and charging executing device, so that the policy and charging executing device according to the policy
  • the bearer resource is allocated for the background traffic download with the charging control.
  • the policy and charging setting device determines a dedicated bearer setup time and a maximum download rate for each user terminal in the user group that needs to download background traffic, so that the application server can download to the user.
  • the user terminal of the background traffic transmits data. Network congestion due to simultaneous transmission of data to individual user terminals in a user group can be avoided to some extent.
  • the policy and charging setting device determines the policy and charging control of the background traffic download according to the background traffic downloading policy.
  • System including:
  • the policy and charging formulating unit determines, according to the background traffic downloading policy, the same dedicated bearer setup time and the same maximum download rate for each user terminal.
  • the policy and charging determining unit determines, according to the background traffic downloading policy, a dedicated bearer setup time and a maximum download rate for each user terminal, where the bearer setup times of the user terminals are not completely the same, and the users are not identical.
  • the maximum download rate of the terminal is not exactly the same.
  • the bearer setup time of each user terminal is a moment in the allowed download time window included in the background traffic download policy.
  • the bearer establishment time of each user terminal is not limited, as long as it is within the time window in the background traffic download policy.
  • the policy and charging setting device receives the background traffic download enable request sent by the application server (the request sent for the background traffic download of the user group), according to the background traffic download enable request
  • the identifier of the background traffic downloading policy requests the corresponding background traffic downloading policy from the network aware scheduling device.
  • the background traffic download enable request received by the policy and billing device application server includes the IP address of each user terminal in the user group that needs to download the background traffic, the user terminal may generate the download according to the IP address of each user terminal.
  • the policy and charging control of each user terminal of the background traffic so that the policy and charging control execution device allocates bearer resources for each user terminal that needs to download background traffic, so that the application server transmits data to each user terminal that needs to download the background traffic. In this way, network congestion due to simultaneous transmission of data to each of the user terminals in the group is avoided.
  • the embodiment of the invention provides a background traffic downloading method, where the execution entity is an application server, and the application server corresponds to at least one group. As shown in FIG. 4, the method includes the following steps:
  • the application server sends a background traffic download request message to the network-aware scheduling device, where the background traffic download request message carries the background traffic under the user group. Load the required demand information.
  • the requirement information includes at least one of the following information: a traffic value required for the user group to perform background traffic download, a time window required for the user group to perform background traffic download, and the user group. Regional information.
  • the user group is at least one of the groups corresponding to the background traffic download in the group corresponding to the application server.
  • the application server may be a third-party server, such as a server of the government, public security, or the like.
  • the plurality of users or all users in the user group will receive background traffic information from the application server, and the background traffic information may be system information of the group application or periodic information of the unified subscription of the group user. It can also be any type of information with the same content.
  • the traffic value required for the user group to perform the background traffic download is the traffic value required by the application server for the background traffic download by the user group.
  • the area information of the user group refers to the area information of the area selected by the application server to provide the background traffic download service, and the area range is one or more of the tracking area, the eNB, the cell, the routing area, and the service area of the operator. Corresponding.
  • the application server sends the user group to the network-aware scheduling device to generate the required information for the background traffic download, so that the network-aware scheduling device can formulate a background traffic downloading policy for the group, and avoid the network-side
  • the policy formulation unit (which can be a PCRF) responds repeatedly to the same request, saving network overhead.
  • the application server receives an identifier of a background traffic download policy of the user group sent by the network-aware scheduling device.
  • the application server receives the identifier of the background traffic download policy of the user group sent by the network-aware scheduling device, and proves that the network-aware scheduling device determines that the network meets the background traffic download request of the application server, that is, the application server is the user group.
  • the initiated background traffic download request) and a background traffic download policy is generated for the user group. If the application server does not receive the identifier of the background traffic download policy of the user group sent by the network-aware scheduling device, it may receive a message indicating that the policy generation failure is sent by the network-aware scheduling device, and prove that the network-aware scheduling is performed.
  • Equipment Make sure the network cannot meet the background traffic download request of the application server.
  • the identifier of the user group may be carried according to the identifier of the background traffic download policy of the user group, and the background traffic download policy is determined to be a background traffic download policy formulated for the user group.
  • the application server sends a background traffic download enable request to the policy and charging device, where the background traffic download enable request carries the identifier of the background traffic download policy, so that the policy and charging device performs the
  • the background traffic download enable request acquires the background traffic download policy of the user group, and determines the policy and charging control of the background traffic download.
  • the policy and charging device may be a PCRF of the operator network, and is connected to the RPSF through an Np interface to implement a policy and charging function.
  • the application server needs to send a background traffic download enable request to the PCRF, and then the PCRF requests the RPSF to download the background traffic corresponding to the identifier of the background traffic download policy of the user group included in the background traffic download enable request sent by the application server.
  • the policy that is, the background traffic download policy generated by the RPSF for the user group
  • the PCRF obtains the background traffic download policy of the user group according to the background traffic download enablement request, and determines the policy and charging for the background traffic download. control.
  • the PCRF sends the policy and charging control to the policy and charging control executing device, and the policy and charging control executing device allocates a bearer to the user terminal in the user group according to the policy and charging control. Resources.
  • the application server transmits data to the user terminals in the user group.
  • the method before the application server sends a background traffic download request message to the network-aware scheduling device, the method further includes:
  • the application server obtains the demand information, generates a background traffic download request message carrying the demand information, and sends the background traffic download request message to the network aware scheduling unit; so that the network aware scheduling unit is configured according to the
  • the demand information generates a background traffic download policy of the user group and an identifier of the background traffic download policy.
  • the network-aware scheduling device may be an RPSF of the carrier network, and is configured to receive The network status information of the operator network is collected, analyzed, and predicted, and the application server supports the management of the network resources of the operator network.
  • the application server may send a background traffic download request message to the network aware scheduling unit through an open platform (Network Capability Open Layer Exposure layer).
  • the open platform is connected to the application server and the RPSF to implement communication between the application server and the carrier network.
  • the open platform may have a protocol conversion function, and may convert a protocol from an interface in the operator domain with a protocol of an interface used by an external server (for example, an application server described in the embodiment of the present invention).
  • the method further includes:
  • the application server acquires an IP address of each user terminal in the user group that needs to download background traffic
  • the background traffic download enablement request further includes an IP address of each user terminal in the user group that needs to download background traffic, so that the policy and charging setting device determines background traffic according to the user group.
  • the downloaded policy and charging control of each user terminal that is, the dedicated bearer setup time and the maximum download rate of the user terminal in the user group that need to perform background traffic download.
  • the dedicated bearer establishment time of each user terminal is not completely the same, and the maximum download rate of each user terminal is not completely the same.
  • the application server acquires a total traffic value of background traffic downloading by all user terminals in the user group, and uses the total traffic value as background traffic of the user group. Download the required traffic value.
  • the traffic value required for the background traffic download by the user terminal is the same, and the traffic value required for the background traffic download by each user terminal is the same.
  • the application server determines a time window required for the user group to perform background traffic downloading, which specifically includes:
  • the application server acquires a time period required for the user group to perform background traffic download, and determines the time period as a time window required for the user group to perform background traffic download.
  • the area information of the user group is area information of the area corresponding to the user group.
  • the area corresponding to the user group corresponds to one or more of an operator defined tracking area, an evolved base station eNB, a routing area, and a cell.
  • the application server receives a message that is sent by the network-aware scheduling unit and indicates that the policy generation fails.
  • the application server receives the timing information sent by the network-aware scheduling unit, and sends the background traffic download request message to the network-aware scheduling unit through the open platform after the timing information is separated.
  • the application server obtains the demand information required for the background traffic downloading by the group, so that the network aware scheduling device of the operator network generates the background traffic downloading strategy for the background traffic downloading of the group,
  • the network-aware scheduling device can be prevented from repeatedly responding to the same request from the application server, and the same background traffic downloading policy is formulated for each user terminal in the user group.
  • the application server determines the IP address of the user terminal in the group that needs to download the background traffic after determining that the network side meets the background traffic download request of the group, so that the policy and charging device of the operator network determines the user group.
  • the policy and charging control of each user terminal that needs background traffic downloading in the group and the policy and charging control execution device allocates bearer resources to the user terminals in the user group that need to download background traffic, and finally the application server Background flow is required in the user group
  • the downloaded user terminal transmits data. Network congestion caused by simultaneously transmitting data to each user terminal in the group can be avoided to some extent.
  • the embodiment of the present invention provides a background traffic downloading method, which is applied to a background traffic management system, where the background traffic management system includes: an application server, an open platform (network capability open layer exposure layer), and a network that provides network awareness and scheduling functions.
  • a perceptual scheduling device eg, RPSF
  • a policy and accounting device eg, PCRF
  • the application server obtains the requirement information required for the background traffic downloading of the user group, generates a background traffic download request message carrying the requirement information, and sends the background traffic download request message to the network aware scheduling device.
  • the user group includes at least one user terminal.
  • the demand information includes at least one of the following: a traffic value required for the user group to perform background traffic download, a time window required for the user group to perform background traffic download, and an area of the user group. information.
  • the traffic value required for the background traffic downloading by the user group may be the total traffic value required for all users in the user group to perform background traffic downloading.
  • the unit traffic value required to obtain the number of users in the user group and the background traffic of the single user may be determined, and the user group is determined to perform background traffic download according to the number of users in the user group and the unit traffic value.
  • the required flow value It should be noted that, here, it is assumed that the traffic values (received background traffic values) required for each user in the user group to perform background traffic download are the same.
  • the method provided by the embodiment of the present invention determines the requirement information of the group for background traffic downloading, and further causes the network aware scheduling device to generate a background traffic downloading policy for the group.
  • the policy and billing device is prevented from responding repeatedly to the same request, and the same background traffic downloading strategy is generated multiple times, thereby saving network overhead.
  • the network-aware scheduling device only needs to generate a background traffic downloading policy for the 10 user terminals in the group, so that the background traffic downloading service requested by each user terminal can be implemented.
  • the network aware scheduling device receives a background traffic download request message sent by the application server, and determines whether the network can meet the background traffic download request of the user group.
  • the background traffic download request message carries requirement information required for background traffic downloading of the user group.
  • the network aware scheduling device needs to determine whether the network is satisfied in a time window required for the user group to perform background traffic downloading.
  • the background traffic download request of the application server it is assumed that the requirement information includes a time window required for the user group to perform background traffic downloading.
  • the network aware scheduling device determines whether the carrier network can be in the time window required for the user group to perform background traffic downloading. Meet the background traffic download request of the application server. It should be noted that if the requirement information of the user group does not include the time window required for the user group to perform background traffic downloading, the network aware scheduling device may not determine whether the network can satisfy the background traffic download of the application server. Request, proceed directly to step 505.
  • step 503 If it is determined that the network cannot meet the background traffic download request of the application server, proceed to step 503; if it is determined that the network can satisfy the background traffic download request of the application server, proceed to step 505.
  • the network aware scheduling device generates a message indicating that the policy generation fails, and sends the failure message indicating the policy generation failure to the application server, and sends timing information to the application server.
  • the demand information included in the background traffic download by the user group includes Performing a time window required for background traffic downloading for the user group, and the network aware scheduling device determines that the operator network cannot satisfy the background traffic download sent by the application server within a time window required for the user group to perform background traffic downloading The request, the network-aware scheduling device generates a message indicating that the policy generation fails, and the message indicating that the policy generation fails includes a failure cause value that the network condition does not satisfy the condition.
  • the network-aware scheduling device sends the timing information to the application server, so that the application server sends the background traffic download request message to the network-aware scheduling device through the open platform after the timing information is separated. If the network-aware scheduling device determines that the carrier network cannot satisfy the background traffic download request of the application server, the application server may send the background traffic download request message to the network-aware scheduling device again through the open platform after the timing information is separated.
  • the application server receives the timing information sent by the network-aware scheduling device, and sends the background traffic download request message to the network-aware scheduling device through the open platform after the timing information is separated.
  • the network-aware scheduling device generates, according to the requirement information, a background traffic download policy of the user group and an identifier of the background traffic download policy, and sends the identifier of the background traffic download policy to the application server.
  • the identifier of the background traffic download policy may further include identifier information of the user group.
  • the network aware scheduling device may determine whether the network of the corresponding area satisfies the background traffic download request of the user group. .
  • the network-aware scheduling device acquires the network state of the user group area (the area corresponding to the area information of the user group), and specifically includes: the RPSF passes the Np interface, and the Nq interface is configured by the PCRF and the The network status information in the corresponding area obtained by the MME.
  • the network status information includes network load status and congestion status in the area, and may also include information about a network status prediction in a future period of time.
  • the network aware scheduling device generates the background traffic download policy for the user group according to the requirement information of the user group, which has the following possibilities:
  • the network aware scheduling device is in the user group according to the network.
  • Determining the allowed download time window within a time window required for background traffic downloading, and the time window required for the user group to perform background traffic downloading includes the allowed download time window, or the allowed download time window is It is included in the time window required for the user group to perform background traffic download.
  • the network aware scheduling device determines, according to the unit flow value, a maximum download rate of the single user.
  • an application server may correspond to multiple groups, and an application server may request background traffic downloads for multiple groups.
  • the network-aware scheduling device may have to formulate a background traffic downloading strategy for background traffic downloads for multiple groups. Therefore, after the network aware scheduling device generates the background traffic download policy for each group, an identifier of each background traffic download policy is also generated. For example, if the user group is one of the multiple groups corresponding to the application server, the network aware scheduling device may generate the background traffic download policy after generating the background traffic download policy for the user group. An identifier, the identifier may further include identification information of the user group. To determine that the background traffic download policy is a background traffic download policy generated for the user group.
  • the application server receives an identifier of a background traffic download policy of the user group sent by the network-aware scheduling device, and determines an IP address of each user terminal in the user group that needs to download background traffic.
  • the application server receives the identifier of the background traffic download policy of the user group sent by the network-aware scheduling device, and indicates the background traffic of the user group. The download strategy was generated successfully. Further, the application server determines an IP address of each user terminal in the user group that needs to download the background traffic, so that the network side has a target to transmit data to the user terminal that needs to download the background traffic, instead of simultaneously in the group. Each user terminal transmits data, which can alleviate network congestion due to simultaneous transmission of data to each user terminal in the group.
  • the application server sends a background traffic download enable request to the policy and charging device.
  • the background traffic download enable request includes an identifier of a background traffic download policy generated by the network-aware scheduling device for the user group, and an IP address of each user terminal in the user group that needs to download background traffic, so that the policy and the The fee-making device determines a dedicated bearer setup time for each user terminal in the user group that needs to download the background traffic according to the background traffic download policy, the IP address of each user terminal in the user group that needs to download background traffic, and Maximum download rate.
  • the policy and accounting setting device receives the background traffic download enable request sent by the application server, and sends the identifier of the background traffic download policy included in the background traffic download enable request to the network aware scheduling device.
  • the background traffic download enable request includes an identifier of the background traffic download policy generated by the network-aware scheduling device for the user group, and acquires the user from the network-aware scheduling device according to the identifier of the background traffic download policy.
  • the background traffic download strategy for the group includes an identifier of the background traffic download policy generated by the network-aware scheduling device for the user group, and acquires the user from the network-aware scheduling device according to the identifier of the background traffic download policy.
  • the network-aware scheduling device receives the identifier of the background traffic downloading policy sent by the policy and the charging device, determines the background traffic downloading policy of the user group according to the identifier, and sends the background traffic downloading policy of the user group to the The policy and billing device is developed.
  • the network-aware scheduling device determines a background traffic download policy according to the identifier sent by the policy and the charging device in the plurality of background traffic download policies that are formulated, and sends the background traffic download policy to the policy and charging device. So that the policy and charging setting device determines the policy and charging control of the background traffic download according to the background traffic downloading policy.
  • the policy and charging setting device receives a background traffic downloading policy of the user group returned by the network aware scheduling device.
  • the identifier of the background traffic downloading policy may further include the identifier information of the user group, and the policy and the charging and formulating device may obtain the identifier information of the user group according to the identifier of the background traffic downloading policy. Determining that the background traffic download policy is a background traffic download policy generated by the network aware scheduling unit for the user group.
  • the policy and charging device determines the policy and charging control of the background traffic download according to the background traffic downloading policy, and sends the policy and charging control to the policy and charging executing device.
  • the policy and charging setting device sends the policy and charging control to the policy and charging executing device, so that the policy and charging executing device allocates bearer resources for background traffic download according to the policy and charging control.
  • the policy and charging device determines a PCC (Policy and Charging Control) policy of the user terminal that needs to download the background traffic in the user group.
  • PCC Policy and Charging Control
  • Each user terminal described herein is a user terminal that needs to download background traffic.
  • the PCC policy is: a bearer establishment time of a single user terminal, and a maximum download rate of a single user. The triggering time of each user terminal is the same, and both are the bearer establishment time, and the maximum download rate of each user terminal is also the same.
  • the PCC policy is: a bearer establishment time of each user terminal, and a maximum download rate of each user.
  • the triggering times of the user terminals are different, that is, the dedicated bearer setup times are different, and the maximum download rate of each user terminal is also different.
  • the bearer setup time of each user terminal should be a time in the allowed time window included in the background traffic download policy fed back by the network aware scheduling device.
  • the policy and charging execution device allocates a bearer resource to the user terminal that needs to perform background traffic downloading according to the policy and charging control, so that the application server needs to download to the user group. Background traffic for each user end Transfer data.
  • the PCC policy determined by the policy and charging device for the background traffic download service requested by the user group is: a dedicated bearer setup time of the single user terminal, and a maximum download rate of the single user.
  • the application server simultaneously transmits data to each user terminal that needs to download background traffic. If the IP address of each user terminal in the user group that needs to download background traffic is not determined in step 506, the application server simultaneously transmits data to the user terminal in the user group, which may cause network congestion. If only data is transmitted to each user terminal in the user group that needs to download background traffic, network congestion can be avoided to some extent.
  • the PCC policy determined by the policy and charging device for the background traffic download service requested by the user group is: a dedicated bearer setup time of each user terminal, and a maximum download rate of each user. Then, the policy and charging control execution device allocates bearer resources to each user terminal that needs to download the background traffic at each dedicated bearer establishment time of the user terminal that needs to download the background traffic, and then the application server will send each time at different times. The user terminal that needs to download the background traffic transmits data.
  • the background traffic downloading method is provided by the embodiment of the present invention.
  • the application server determines the user group to perform the background traffic downloading demand information, and sends a background traffic download request carrying the demand information to the network aware scheduling unit.
  • the network aware scheduling unit receives the background traffic download request message sent by the application server, and generates a background traffic download service for the group.
  • the application server forwards the background traffic download request of each user terminal in the group to the network side, and the policy and charging device generates a background traffic download policy for each user terminal in the group.
  • the network-aware scheduling unit of the present invention generates a background traffic downloading policy for the group, and does not need to generate a background traffic downloading policy for each user terminal in the group, that is, avoiding the network side repeatedly responding to the same request from the application server.
  • the application server determines the IP address of the user terminal in the group that needs to download the background traffic, so that the application server transmits data to the user terminal that needs to download the background traffic. Avoid network congestion due to simultaneous transmission of data to each user terminal in the group.
  • the embodiment of the present invention provides a background traffic downloading method, which is applied to a background traffic management system, where the background traffic management system includes: an application server, an open platform (network capability open layer exposure layer), and a network that provides network awareness and scheduling functions.
  • a perceptual scheduling device eg, RPSF
  • a policy and accounting device eg, PCRF
  • the background traffic download policy generated in step 505 is an allowed download time window, a maximum value of the aggregate download rate of the user group, a charging policy when the aggregate download rate is less than or equal to a maximum value, and the aggregate download rate is greater than The charging policy at the maximum. Then after step 512, the method further includes:
  • the policy and charging control execution device (which may be an online charging system, OCS) collects the current aggregate download rate, and sends the current aggregate download rate to the policy and charging device; the policy and charging Determining, by the device, whether the current aggregation download rate is greater than the maximum aggregate download rate specified in the background traffic download policy, and sending the charging information at the different aggregate download rate to the policy and charging control execution device; And the charging control execution device correctly charges according to the corresponding charging information.
  • OCS online charging system
  • the current aggregate download rate is less than or equal to the maximum aggregate download rate specified in the background traffic download policy
  • the current aggregate download rate is less than or equal to the aggregate download rate specified in the background traffic download policy.
  • the charging policy at the maximum value is charged.
  • the current aggregate download rate is greater than the maximum aggregate download rate specified in the background traffic download policy, the current aggregate download rate is greater than the aggregate download rate specified in the background traffic download policy.
  • the charging policy at the maximum value is charged.
  • the embodiment of the present invention provides a background traffic downloading method, which is applied to a background traffic management system, where the background traffic management system includes: an AS (3rd application service), a network capability open layer exposure layer, an RPSF, and a PCRF.
  • the method includes the following steps:
  • the AS determines the background traffic download service.
  • the AS determines required information for performing background traffic downloading on the user group, and generates a background traffic download request message that carries the demand information.
  • the AS sends a background traffic download request message to the RPSF through the network capability open layer.
  • the AS and RPSF may correspond to different protocols, and the network capability open layer may have the function of protocol conversion. Therefore, the AS needs to send the background traffic download request message to the RPSF through the network capability open layer.
  • the RPSF generates a background traffic downloading strategy.
  • the RPSF uses the Np interface, and the NQ interface obtains the network status information in the area corresponding to the area information of the user group by the PCRF and the MME.
  • the RPSF may also generate an identifier of the background traffic download policy, and the identifier may further include identifier information of the user group.
  • the RPSF needs to determine whether the network can meet the time window required for the user group to perform background traffic downloading.
  • a background traffic download request sent by the application server if yes, a background traffic download policy is generated for the user group; if not, a message indicating that the policy generation failure is sent to the application server.
  • the RPSF sends the policy identifier of the background traffic download policy to the AS.
  • the AS sends a background traffic download enable request to the PCRF.
  • the background traffic download enable request includes an identifier of the background traffic download policy, and an IP address of the user terminal in the user group that needs to download background traffic.
  • the PCRF acquires, from the RPSF, a background traffic download policy generated by the user group.
  • the PCRF sends the policy identifier of the background traffic downloading policy to the RPSF, so that the RPSF determines the background traffic generated for the user group according to the identifier in the background traffic downloading policy of the plurality of background traffic downloads that the RPSF defines. Download strategy.
  • the PCRF determines a PCC strategy.
  • the PCC policy here is the policy and charging control described in the embodiment of the present invention.
  • the PCRF determines the dedicated bearer setup time of the single user terminal and the maximum download rate of the single user. Alternatively, the dedicated bearer setup time of each user terminal and the maximum download rate of each user are determined.
  • the dedicated bearer setup time of the single user and the dedicated bearer setup time of each user terminal are all moments in the allowed download time window included in the background traffic download policy.
  • the PCRF sends the foregoing PCC policy to the policy and charging control device.
  • the policy and charging control device allocates a bearer resource.
  • the policy and charging execution device allocates bearer resources for background traffic download according to the policy and charging control. It is also possible to allocate bearer resources to each user terminal in the user group that needs to perform background traffic download.
  • the AS transmits data to each user terminal in the user group that needs to download background traffic.
  • the AS transmits data to the corresponding user terminal according to the predetermined IP address of each user terminal in the user group that needs to perform background traffic download.
  • the method further includes: the policy and charging control execution device acquires the current aggregate download rate of the AS, and performs correct charging.
  • the AS determines the demand information of the group for background traffic downloading, and sends a background traffic download request carrying the group demand information to the RPSF, requesting the network side to establish background traffic download for the group. business.
  • the RPSF receives the background traffic download request message sent by the AS, and generates a background traffic download policy for the group.
  • the AS will each user terminal in the group.
  • the background traffic download request is forwarded to the PCRF, and the PCRF generates a background traffic download policy for each user terminal in the group.
  • the RPSF of the present invention sets a background traffic downloading policy for the background traffic downloading service of the group, and does not need to generate a corresponding background traffic downloading policy for each user terminal in the group, that is, the network side is prevented from repeatedly responding to the same request from the application server.
  • the AS determines the IP address of the user terminal in the group that needs to download the background traffic, so that the PCRF generates policy and charging control for the user terminal in the user group that needs to download background traffic, and then the policy and charging control execution device is
  • the user terminal in the user group that needs to download background traffic allocates bearer resources, and the application server transmits data to the user terminal that needs to download the background traffic. Avoid network congestion due to simultaneous transmission of data to each user terminal in the group.
  • An embodiment of the present invention further provides an application server 7.
  • the application server 7 includes an obtaining unit 701, a sending unit 702, and a receiving unit 703.
  • the obtaining unit 701 is configured to acquire requirement information required for background traffic downloading of the user group.
  • the requirement information includes at least one of the following information: a traffic value required for the user group to perform background traffic download, a time window required for the user group to perform background traffic download, and the user group. Regional information.
  • the user group is a group that needs to perform background traffic download in a group corresponding to the application server. Multiple or all users in the user group will receive background traffic from the application server.
  • the background traffic may be system information of the group application, may be periodic information that the group user subscribes to, or may be any type of information with the same content.
  • the traffic value required for the user to perform background traffic downloading is the traffic value required by the obtaining unit 701 to perform the background traffic downloading by the user group, and may be the background traffic downloading by each user terminal in the user group.
  • the traffic value may also be two pieces of information of a unit traffic value of the background traffic download by a single user terminal in the user group and the number of user terminals in the user group.
  • the area information of the user group refers to the background flow selected by the application server.
  • the area-wide area information of the download service the area range corresponding to one or more of the operator's tracking area, the evolved base station eNB, the cell, the routing area, and the service area.
  • the sending unit 702 is configured to send the background traffic download request message to the network aware scheduling unit.
  • the background traffic download request message carries the demand information required for the background traffic downloading of the user group, so that the network aware scheduling unit generates the background traffic downloading strategy for the background traffic download by the user group according to the demand information. And the identity of the background traffic download policy.
  • the network-aware scheduling device may be an RPSF of the carrier network, which collects, analyzes, and predicts network state information of the carrier network, and supports management call of the application server to the network resources of the operator network.
  • the open platform (Exposure layer) is connected to the application server and RPSF to implement communication between the application server and the carrier network.
  • the open platform may have a protocol conversion function, and may convert a protocol from an interface in the operator domain with a protocol of an interface used by an external server (for example, an application server described in the embodiment of the present invention).
  • the receiving unit 703 is configured to receive an identifier of a background traffic download policy of the user group sent by the network aware scheduling device.
  • the receiving unit 703 receives the identifier sent by the network-aware scheduling device, and proves that the network-aware scheduling device determines that the network meets the background traffic download request of the application server (that is, the background traffic download request initiated by the application server for the user group), and The user group has formulated a background traffic download strategy. If the receiving unit 703 does not receive the policy identifier sent by the network-aware scheduling device, it may receive a message indicating that the policy generation failure is sent by the network-aware scheduling device, and prove that the network-aware scheduling device determines that the network cannot meet the background of the application server. A traffic download request (a background traffic download request initiated by the application server for the user group).
  • the identifier of the background traffic download policy may further carry the identifier information of the user group, so that after determining a background traffic download policy according to the identifier, it may be determined that the background traffic download policy is generated for the user group. Background traffic download strategy.
  • the sending unit 702 is further configured to send the background traffic to the policy and charging setting device.
  • the background traffic download enablement request carries the identifier of the background traffic download policy, so that the policy and charging device performs the background traffic download policy of the user group according to the background traffic download enablement request. Determine the policy and charging control for background traffic downloads.
  • the policy and charging device may be a PCRF of the operator network, and is connected to the RPSF through an Np interface to implement a policy and charging function.
  • the sending unit 702 needs to send the background traffic download enable request to the PCRF, and then the PCRF requests the RPSF to the background traffic download policy corresponding to the policy identifier included in the background traffic download enable request sent by the sending unit 702 (ie, the RPSF is the user.
  • the background traffic downloading policy generated by the group, and finally the PCRF formulates the policy and charging control of the background traffic download for the user terminal in the user group, so as to transmit data for each user terminal in the user group.
  • the obtaining unit 701 is further configured to: after the receiving unit 703 receives the identifier of the background traffic download policy of the user group sent by the network-aware scheduling device, acquire the background traffic that needs to be downloaded in the user group.
  • the IP address of each user terminal is further configured to: after the receiving unit 703 receives the identifier of the background traffic download policy of the user group sent by the network-aware scheduling device, acquire the background traffic that needs to be downloaded in the user group.
  • the IP address of each user terminal is further configured to: after the receiving unit 703 receives the identifier of the background traffic download policy of the user group sent by the network-aware scheduling device, acquire the background traffic that needs to be downloaded in the user group. The IP address of each user terminal.
  • the background traffic download enablement request further includes an IP address of each user terminal in the user group that needs to download the background traffic, so that the PCRF determines the background for each user terminal in the user group that needs to download the background traffic. Policy and charging control for traffic downloads.
  • the obtaining unit 701 is specifically configured to acquire a total traffic value of the background traffic downloading by the user terminal in the user group, and use the total traffic value as the traffic value required for the background traffic download by the user group.
  • the obtaining unit 701 is specifically configured to acquire the number of user terminals in the user group and the unit flow value required for the background traffic download by the single user terminal in the user group, according to the unit flow value and the The number of user terminals in the user group determines the traffic value required for the user group to perform background traffic download, wherein the traffic values required for each user terminal to perform background traffic download are the same.
  • the obtaining unit 701 is specifically configured to acquire the user group for background traffic.
  • the required time period is downloaded, and the time period is determined as a time window required for the user group to perform background traffic download.
  • the acquiring unit 701 is specifically configured to acquire a start time of the background traffic download by the user group and timing information from the start time, according to the start time and the start time
  • the timing information determines a time window required for the user group to perform background traffic downloads.
  • the receiving unit 703 is configured to receive, by the network-aware scheduling unit, a message indicating that the policy generation fails, and receive the timing information sent by the network-aware scheduling unit.
  • the sending unit 702 is further configured to: after the timing information is separated, send the background traffic download request message to the network aware scheduling unit by using the open platform.
  • the application server acquires at least one of a time window required for background traffic downloading, a traffic value required for background traffic download, and regional information of the group, so as to be network aware of the carrier network.
  • the scheduling device sets a background traffic downloading policy for the background traffic download for the group, which can prevent the network-aware scheduling device from repeatedly responding to the same request from the application server, and formulating the same background traffic downloading policy multiple times.
  • the IP address of the user terminal that needs to download the background traffic in the group is determined, so that the policy and charging device of the carrier network can provide the user who needs to download the background traffic.
  • the terminal transmits data. Network congestion caused by simultaneously transmitting data to each user terminal in the group can be avoided to some extent.
  • the embodiment of the present invention further provides a network-aware scheduling device 8.
  • the network-aware scheduling device 8 includes a receiving unit 801, a generating unit 802, a sending unit 803, and a determining unit 804.
  • the receiving unit 801 is configured to receive a background traffic download request message sent by the application server, where the background traffic download request message carries requirement information required for background traffic downloading of the user group.
  • the generating unit 802 is configured to generate, according to the requirement information, a background traffic downloading policy of the user group and an identifier of the background traffic downloading policy.
  • the identifier of the background traffic download policy may further include identifier information of the user group.
  • the network-aware scheduling device may be an RPSF of the carrier network, and may collect status information of the carrier network to determine whether the operator supports the background traffic download request of the application server (the background initiated by the application server for the user group) After the traffic download request is determined, or after determining that the operator supports the background traffic download request of the user group, a corresponding background traffic download policy is formulated for the user group.
  • the background traffic download request message sent by the application server includes the traffic value required for the user group to perform background traffic download, the time window required for the user group to perform background traffic download, and the user group.
  • the generating unit 802 can generate a background traffic downloading policy for the user group.
  • the generating unit 802 creates a background traffic downloading policy for the group, and does not need to generate a background traffic downloading policy for each user terminal, so as to prevent the operator's policy unit (the network-aware scheduling device) from repeatedly responding to the same request from the application server.
  • the network-aware scheduling device 8 only needs to download the identifier of the background traffic download policy included in the start request according to the background traffic of the user group, and The background traffic download strategy generated by the user group.
  • the application server may correspond to multiple groups, after the generating unit 802 generates a corresponding background traffic downloading policy for each group, a unique corresponding identifier is generated for each background traffic downloading policy, so that one can be quickly locked according to the identifier.
  • Background traffic download strategy For example, in the embodiment of the present invention, the network aware scheduling device 8 can uniquely determine a background traffic download policy according to the identifier of the background traffic download policy provided by the policy and the charging and formulating unit, and further, because the identifier includes the user The identification information of the group determines that the background traffic download policy is a background traffic download policy generated by the network aware scheduling device for the user group.
  • the sending unit 803 is configured to send an identifier of the background traffic download policy to the application server.
  • the sending unit 803 sends the application to the application server through an open platform.
  • the identifier of the background traffic download policy is a registered trademark of Microsoft Corporation.
  • the receiving unit 801 is further configured to receive an identifier of the background traffic download policy sent by the policy and the charging and formulating device.
  • the determining unit 804 determines the background traffic downloading policy of the user group according to the identifier of the background traffic downloading policy.
  • the sending unit 803 is configured to send the background traffic downloading policy to the policy and charging device, so that the policy and charging device determines the background traffic downloading policy and the meter according to the background traffic downloading policy. Fee control.
  • the generating unit 802 is specifically configured to: if the demand information includes a traffic value required for the background traffic download by the user group, determine, according to the traffic value required for the background traffic download by the user group, The maximum value of the aggregation download rate of the user group; or the unit traffic value of the single user terminal corresponding to the traffic value required for the background traffic download by the user group, and determining the maximum download rate of the single user.
  • the allowed download time window is included in a time window required for the user group to perform background traffic download, or The time window required for the user group to perform background traffic download includes the allowed download time window.
  • the network aware scheduling device 8 also includes a determination unit.
  • the determining unit is configured to: when the generating unit 802 generates the background traffic downloading policy of the user group and the identifier of the background traffic downloading policy according to the requirement information, when the demand information includes the user group When the group performs the time window required for background traffic downloading, it is determined that the network can satisfy the background traffic download request of the application server within a time window required for the user group to perform background traffic downloading.
  • the generating unit 802 is further configured to: after the determining unit determines that the network cannot meet the background traffic download request of the application server within a time window required for the user group to perform background traffic downloading, generate an indication policy generation The message of failure.
  • the sending unit 803 is configured to send, to the application server, the message indicating that the policy generation fails.
  • the sending unit 803 is configured to send the indication policy to the application server. After the failed message is generated, the timing information is sent to the application server, so that the application server sends the background traffic download request message to the network aware scheduling unit through the open platform after the timing information is separated.
  • the network-aware scheduling device after receiving the background traffic download request message sent by the application server for the user group, performs the background traffic downloading demand information according to the user group included in the background traffic download request message. And the status of the network, to determine whether the network can meet the background traffic download request of the application server.
  • the generating unit 802 After determining that the network can meet the background traffic download request of the user group, the generating unit 802 generates a background traffic download policy for the user group and generates an identifier corresponding to the background traffic download policy, so as to be sent according to the application server.
  • the identifier is locked as a background traffic downloading policy.
  • the background traffic downloading policy is determined to be a background traffic downloading policy generated for the background traffic downloading service of the user group according to the identifier information of the user group included in the identifier.
  • the embodiment of the present invention further provides a policy and charging device 9 .
  • the policy and accounting device 9 includes a receiving unit 901 , a sending unit 902 , and a generating unit 903 .
  • the receiving unit 901 is configured to receive a background traffic download enable request sent by the application server, where the background traffic download enable request carries an identifier of the background traffic download policy of the user group.
  • the sending unit 902 is configured to send the identifier of the background traffic download policy to the network aware scheduling device.
  • the receiving unit 901 is further configured to receive a background traffic download policy of the user group returned by the network aware scheduling device.
  • the generating unit 903 is configured to determine a policy and charging control of the background traffic download according to the background traffic downloading policy.
  • the generating unit 903 is specifically configured to: when the background traffic download enable request further includes an IP address of each user terminal in the user group that needs to download the background traffic, download the policy according to the background traffic, and the user The IP address of each user terminal that needs to download the background traffic in the group, and the background traffic needs to be downloaded in the user group.
  • Each user terminal determines a dedicated bearer setup time and a maximum download rate.
  • the sending unit 902 is configured to send the policy and charging control to the policy and charging execution device, so that the policy and charging executing device allocates bearer resources for background traffic download according to the policy and charging control. Finally, the application server transmits data to the user terminals in the user group.
  • the generating unit 903 determines the dedicated for each user terminal in the user group that needs to download the background traffic.
  • the bearer setup time and the maximum download rate, the policy and the charging execution device allocate bearer resources to each user terminal in the user group that needs to download the background traffic.
  • the application server transmits data to each user terminal in the user group that needs to download background traffic. Avoid network congestion due to simultaneous transmission of data to all user terminals.
  • the bearer setup time of each user terminal is a moment in the allowed download time window included in the background traffic download policy.
  • the policy and charging device receives the background traffic download enable request sent by the application server, and requests the corresponding background traffic download policy from the network aware scheduling device according to the identifier included in the background traffic download enable request. And determining, according to the identifier information of the user group that is included in the identifier of the background traffic downloading policy, the background traffic downloading policy that is sent by the network-aware scheduling device is a background traffic downloading policy generated by the network-aware scheduling device. Finally, according to the background traffic download enable request, the IP address of the user terminal that needs to download the background traffic in the user group is generated, and the policy and charging control are generated for each user terminal in the user group that needs to download the background traffic. It is possible to transmit data to user terminals that need to download background traffic, avoiding network congestion caused by simultaneously transmitting data to each user terminal in the user group.
  • the embodiment of the invention further provides a background traffic management system, including: the foregoing application Server 7, network aware scheduling device 8, policy and charging formulation 9.
  • the application server determines the demand information of the background traffic download, and sends a background traffic download request including the group demand information to the network aware scheduling device 8, requesting the network side to establish a background traffic download service for the group.
  • the network aware scheduling device 8 receives the background traffic download request message sent by the application server 7, and generates a background traffic download policy for the group.
  • the network-aware scheduling device 8 of the present invention sets a background traffic downloading policy for the group, and does not need to generate a background traffic downloading policy for each user terminal in the group, that is, the network-aware scheduling device 8 is prevented from repeatedly responding to the same request from the application server 7. There is no need to develop multiple background traffic download strategies.
  • the application server 7 determines the IP address of the user terminal in the group that needs to download the background traffic, so that the policy and charging setting device generates policy and charging control for the user terminal in the user group that needs to download the background traffic. Therefore, data can be transmitted to the user terminal in the user group that needs to download the background traffic, thereby avoiding network congestion caused by the network side transmitting data to each user terminal in the group at the same time.
  • the sending unit for sending a message may be implemented by using a transmitter or by using a transceiver; and the receiving unit for receiving a message may be implemented by using a receiver. Or use a transceiver to achieve.
  • the transmitter or the transceiver may be implemented by one physical entity, or may be implemented by multiple physical entities.
  • the transmitter and the transceiver may be implemented by one physical entity or multiple physical entities. This is not limited; other units, such as the obtaining unit, the generating unit, and the determining unit, may be implemented by one or more processors, which is not limited by the present invention.
  • the embodiment of the present invention further provides a background traffic downloading device 10.
  • the background traffic downloading device 10 includes: a transmitter 1001, a receiver 1002, a memory 1003, and a transmitter 1001, a receiver 1002, and
  • the processor 1004 is connected to the memory 1003.
  • the application server 10 may further include a common component such as a baseband processing component, a medium-frequency processing component, and an input/output device.
  • the embodiment of the present invention does not impose any limitation herein.
  • the memory 1003 stores a set of program codes, and the processor 1004 is configured to call the program code stored in the memory 1003 for executing the map. 2- Method flow of the background traffic download method described in FIG. When performing the method flow of the background traffic download method described in FIG.
  • the background traffic downloading device 10 may be a network-aware scheduling device; when performing the method flow of the background traffic download method described in FIG. 3, the background traffic The downloading device 10 may be a policy and billing setting device; the background traffic downloading device 10 may be an application server when performing the method flow of the background traffic downloading method described in FIG.
  • the foregoing program may be stored in a computer readable storage medium, and when executed, the program includes The steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Abstract

一种背景流量下载方法、设备及系统,涉及通信领域,为用户群组制定背景流量下载策略,解决了策略制定单元重复响应,网络开销较大的问题。包括:网络感知调度设备接收应用服务器发送的背景流量下载请求消息(201);根据需求信息生成用户群组的背景流量下载策略和背景流量下载策略的标识(202);向应用服务器发送背景流量下载策略的标识(203);接收策略与计费制定设备发送的背景流量下载策略的标识,根据背景流量下载策略的标识确定用户群组的背景流量下载策略,将背景流量下载策略发送给策略与计费制定设备,以便策略与计费制定设备根据背景流量下载策略确定背景流量下载的策略与计费控制(204)。

Description

一种背景流量下载方法、设备及系统 技术领域
本发明涉及通信领域,尤其涉及一种背景流量下载方法、设备及系统。
背景技术
随着电信市场的繁荣和发展,基础电信业务市场不断扩大并走向成熟。很多政、企行业等用户通过第三方应用服务器与运营商网络相连,利用公共网络进行用户群组通信。这里所说的用户群组是由第三方应用服务器下的行业用户中的全部用户终端或部分用户终端构成的。
现有技术中,当第三方应用服务器下的某个用户群组需要进行背景流量下载时,例如需要进行升级终端应用或更新终端数据库时,该用户群组中的每个用户终端都会向第三方应用服务器发送背景流量下载请求,第三方应用服务器再将该背景流量下载请求转发给运营商网络中的PCRF(Policy and Charging Rule Function,策略与计费制定单元),由PCRF为用户群组中的各个用户终端分别制定背景流量下载策略,并根据各个用户终端的背景流量下载策略,制定能够满足所述用户群组的背景流量下载请求的具体网络传输策略,即制定各个用户终端进行背景流量下载的策略控制与计费控制。
然而,一个群组内的用户终端需要下载的背景流量可能相同,采用现有技术的方法,PCRF需要对来自第三方应用服务器转发的各个相同的背景流量下载请求做重复响应,造成不必要的网络开销。
发明内容
本发明实施例提供一种背景流量下载方法、设备及系统,解决了针对同一用户群组的背景流量下载,策略制定单元重复响应,网络开销较大的问题。
为达到上述目的,本发明实施例采用的技术方案是,
第一方面,提供一种背景流量下载方法,所述方法包括:
网络感知调度设备接收应用服务器发送的背景流量下载请求消息,所述背景流量下载请求消息携带对用户群组进行背景流量下载所需的需求信息;
所述网络感知调度设备根据所述需求信息生成所述用户群组的背景流量下载策略和所述背景流量下载策略的标识;
所述网络感知调度设备向所述应用服务器发送所述背景流量下载策略的标识;
所述网络感知调度设备接收策略与计费制定设备发送的所述背景流量下载策略的标识,根据所述背景流量下载策略的标识确定所述用户群组的所述背景流量下载策略,将所述背景流量下载策略发送给所述策略与计费制定设备,以便所述策略与计费制定设备根据所述背景流量下载策略确定背景流量下载的策略与计费控制。
结合第一方面,在第一方面的第一种可能的实现方式中,
所述需求信息包括以下信息中的至少一项:所述用户群组进行背景流量下载所需的流量值、所述用户群组进行背景流量下载所需的时间窗、所述用户群组的区域信息。
结合第一方面、第一方面的第一种可能的实现方式,在第一方面的第二种可能的实现方式中,
所述背景流量下载策略包括以下信息中的至少一项:
允许的下载时间窗、单个用户终端的计费信息、单个用户终端的最大下载速率、所述用户群组的汇聚下载速率的最大值、不同汇聚下载速率下的计费策略。
结合第一方面的第二种可能的实现方式,在第一方面的第三种可能的实现方式中,
若所述需求信息包括所述用户群组进行背景流量下载所需的时间窗,则所述背景流量下载策略包括所述允许的下载时间窗;其中,所述用户群组进行背景流量下载所需的时间窗包含所述允许的下载时间窗;
或者,若所述需求信息包括所述用户群组进行背景流量下载所需的流量值,则所述背景流量下载策略包括所述用户群组的汇聚下载速率的最大值或所述用户群组中单个用户终端的最大下载速率;其中,所述用户群组的汇聚下载速率的最大值或所述用户群组中单个用户终端的最大下载速率由所述用户群组进行背景流量下载所需的流量值确定。
结合第一方面、第一方面的第一种可能的实现方式,在第一方面的第四种可能的实现方式中,
若所述需求信息包括所述用户群组进行背景流量下载所需的时间窗,
则,在所述网络感知调度设备根据所述需求信息生成所述用户群组的背景流量下载策略和所述背景流量下载策略的标识之前,所述方法还包括:
所述网络感知调度设备确定在所述用户群组进行背景流量下载所需的时间窗内网络能够满足所述应用服务器的背景流量下载请求。
第二方面,公开了一种背景流量下载方法,所述方法包括:
策略与计费制定设备接收应用服务器发送的背景流量下载启用请求,所述背景流量下载启用请求携带用户群组的背景流量下载策略的标识;
所述策略与计费制定设备将所述背景流量下载策略的标识发送至网络感知调度设备;
所述策略与计费制定设备接收所述网络感知调度设备返回的所述用户群组的背景流量下载策略;
所述策略与计费制定设备根据所述背景流量下载策略,确定背景流量下载的策略与计费控制。
结合第二方面,在第二方面的第一种可能的实现方式中,若所述背景流量下载启用请求中还包括所述用户群组中需要下载背景流量的各用户终端的IP地址,则所述策略与计费制定设备根据所 述背景流量下载策略,确定背景流量下载的策略与计费控制包括:
所述策略与计费制定设备根据所述背景流量下载策略、所述用户群组中需要下载背景流量的各用户终端的IP地址,为所述用户群组中需要下载背景流量的各用户终端确定专用承载建立时刻和最大下载速率。
结合第二方面、第二方面的第一种可能的实现方式,在第二方面的第二种可能的实现方式中,所述方法还包括:
所述策略与计费制定设备将所述策略与计费控制发送给策略与计费执行设备,以便所述策略与计费执行设备根据所述策略与计费控制为背景流量下载分配承载资源。
第三方面,公开了一种背景流量下载方法,所述方法包括:
应用服务器向网络感知调度设备发送背景流量下载请求消息,所述背景流量下载请求消息携带对用户群组进行背景流量下载所需的需求信息;
所述应用服务器接收所述网络感知调度设备发送的所述用户群组的背景流量下载策略的标识;
所述应用服务器向策略与计费制定设备发送背景流量下载启用请求,所述背景流量下载启用请求中携带所述背景流量下载策略的标识,以便所述策略与计费制定设备根据所述背景流量下载启用请求获取所述用户群组的背景流量下载策略,确定背景流量下载的策略与计费控制。
结合第三方面,在第三方面的第一种可能的实现方式中,所述需求信息包括以下信息中的至少一项:所述用户群组进行背景流量下载所需的流量值、所述用户群组进行背景流量下载所需的时间窗、所述用户群组的区域信息。
结合第三方面、第三方面的第一种可能的实现方式,在第三方面的第二种可能的实现方式中,
所述应用服务器向网络感知调度设备发送背景流量下载请求消息之前,所述方法还包括:
所述应用服务器获取所述需求信息。
结合第三方面、第三方面的第一、第二种可能的实现方式,在第三方面的第三种可能的实现方式中,
所述应用服务器接收所述网络感知调度设备发送的所述背景流量下载策略的标识之后,所述方法还包括:
所述应用服务器获取所述用户群组中需要下载背景流量的各用户终端的IP地址;
则,所述背景流量下载启用请求还包括所述用户群组中需要下载背景流量的各用户终端的IP地址。
第四方面,公开了一种网络感知与调度设备,包括:
接收单元,用于接收应用服务器发送的背景流量下载请求消息,所述背景流量下载请求消息携带对用户群组进行背景流量下载所需的需求信息;
生成单元,用于根据所述需求信息生成所述用户群组的背景流量下载策略和所述背景流量下载策略的标识;
发送单元,用于向所述应用服务器发送所述背景流量下载策略的标识;
所述接收单元还用于,接收策略与计费制定设备发送的所述背景流量下载策略的标识;
确定单元,用于根据所述背景流量下载策略的标识确定所述用户群组的所述背景流量下载策略;
所述发送单元还用于,将所述背景流量下载策略发送给所述策略与计费制定设备,以便所述策略与计费制定设备根据所述背景流量下载策略确定背景流量下载的策略与计费控制。
第五方面,公开了一种策略与计费制定设备,包括:
接收单元,接收应用服务器发送的背景流量下载启用请求,所述背景流量下载启用请求携带用户群组的背景流量下载策略的标识;
发送单元,用于将所述背景流量下载策略的标识发送至网络感 知调度设备;
所述接收单元还用于,接收所述网络感知调度设备返回的所述用户群组的背景流量下载策略;
生成单元,用于根据所述背景流量下载策略,确定背景流量下载的策略与计费控制。
第六方面,公开了一种应用服务器,包括:
发送单元,用于向网络感知调度设备发送背景流量下载请求消息,所述背景流量下载请求消息携带对用户群组进行背景流量下载所需的需求信息;
接收单元,用于接收所述网络感知调度设备发送的所述用户群组的背景流量下载策略的标识;
所述发送单元还用于,向策略与计费制定设备发送背景流量下载启用请求,所述背景流量下载启用请求中携带所述背景流量下载策略的标识,以便所述策略与计费制定设备根据所述背景流量下载启用请求获取所述用户群组的背景流量下载策略,确定背景流量下载的策略与计费控制。
第七方面,公开了一种网络感知与调度设备,包括:
接收器,用于接收应用服务器发送的背景流量下载请求消息,所述背景流量下载请求消息携带对用户群组进行背景流量下载所需的需求信息;
处理器,用于根据所述需求信息生成所述用户群组的背景流量下载策略和所述背景流量下载策略的标识;
发射器,用于向所述应用服务器发送所述背景流量下载策略的标识;
所述接收器还用于,接收策略与计费制定设备发送的所述背景流量下载策略的标识;
所述处理器,用于根据所述背景流量下载策略的标识确定所述用户群组的所述背景流量下载策略;
所述发射器还用于,将所述背景流量下载策略发送给所述策略 与计费制定设备,以便所述策略与计费制定设备根据所述背景流量下载策略确定背景流量下载的策略与计费控制。
第八方面,公开了一种策略与计费制定设备,包括:
接收器,用于接收应用服务器发送的背景流量下载启用请求,所述背景流量下载启用请求携带用户群组的背景流量下载策略的标识;
发射器,用于将所述背景流量下载策略的标识发送至网络感知调度设备;
所述接收器还用于,接收所述网络感知调度设备返回的所述用户群组的背景流量下载策略;
处理器,用于根据所述背景流量下载策略,确定背景流量下载的策略与计费控制。
第九方面,公开了一种应用服务器,包括:
发射器,用于向网络感知调度设备发送背景流量下载请求消息,所述背景流量下载请求消息携带对用户群组进行背景流量下载所需的需求信息;
接收器,用于接收所述网络感知调度设备发送的所述用户群组的背景流量下载策略的标识;
所述发射器还用于,向策略与计费制定设备发送背景流量下载启用请求,所述背景流量下载启用请求中携带所述背景流量下载策略的标识,以便所述策略与计费制定设备根据所述背景流量下载启用请求获取所述用户群组的背景流量下载策略,确定背景流量下载的策略与计费控制。
第十方面,公开了一种系统,包括:网络感知调度设备、策略与计费制定设备以及应用服务器,
所述网络感知调度设备为上述技术方案第四方面所述的网络感知调度设备;
所述策略与计费制定设备为上述技术方案第五方面所述的策略与计费制定设备;
所述应用服务器为上述技术方案第六方面所述的应用服务器;
或者,所述网络感知调度设备为上述技术方案第七方面所述的网络感知调度设备;
所述策略与计费制定设备为上述技术方案第八方面所述的策略与计费制定设备;
所述应用服务器为上述技术方案第九方面所述的应用服务器。
本发明实施例提供的一种背景流量下载方法、设备及系统,应用服务器确定用户群组的需求信息,并发送携带所述需求信息的背景流量下载请求给网络感知调度设备。网络感知调度设备接收应用服务器发送的背景流量下载请求消息,并为群组生成一个背景流量下载策略。现有技术中,应用服务器会将群组中的每个用户终端的背景流量下载请求转发给策略与计费制定设备,策略与计费制定设备会为群组中的每个用户终端生成背景流量下载策略。而本发明网络侧为群组制定背景流量下载策略,不必为群组中每个用户终端制定背景流量下载策略,即避免网络侧对来自应用服务器的同类请求做重复响应。另外,应用服务器确定群组中需要下载背景流量的用户终端的IP地址,以便策略与计费制定设备为需要下载背景流量的用户终端生成策略与计费控制,最后由策略与计费控制执行设备为需要下载背景流量的用户终端分配承载资源,以便应用服务器向需要下载背景流量的用户终端传输数据。避免由于同时向群组中的每个用户终端传输数据而造成的网络拥塞。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案,下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本发明的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1为本发明实施例提供的背景流量管理系统架构图;
图2为本发明实施例1提供的一种背景流量下载方法的流程示 意图;
图3为本发明实施例1提供的另一种背景流量下载方法的流程示意图;
图4为本发明实施例1提供的另一种背景流量下载方法的流程示意图;
图5为本发明实施例2提供的另一种背景流量下载方法的流程示意图;
图6为本发明实施例4提供的一种背景流量下载方法的流程示意图;
图7为本发明实施例5提供的一种应用服务器的示意图;
图8为本发明实施例5提供的一种网络感知调度设备的示意图;
图9为本发明实施例5提供的一种策略与计费制定设备的示意图;
图10为本发明实施例提供的一种背景流量下载装置的示意图。
具体实施方式
下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本发明一部分实施例,而不是全部的实施例。基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。
如图1所示,为一种3GPP中SAE(System Architecture Evolution,系统架构演进)系统架构,可以实现对背景流量资源的管理。该系统可以包括:移动性管理实体(MME,Mobility Management Entity)、网络感知和调度网元(RPSF,RAN payload schedule function)、策略与计费制定单元(PCRF,Policy and Charging Rule Function)、应用服务器(如图1中的AS,可以是第三方服务器)、网络能力开放层和用户设备(UE,User Equipment) 等。其中,MME负责控制面的移动性管理,如用户上下文和移动状态管理以及分配用户临时身份标识等;PCRF,用于策略控制规则的制定以及基于流的计费;UE为与SAE进行控制面与用户面交互的终端设备;RPSF用以网络状态信息(实时信息与历史信息)的收集、分析以及预测,支持对应用服务器的接入业务(例如背景流量业务等)进行资源调度和负载控制。RPSF通过Np接口与PCRF相连,通过Nq接口与移动性管理网元相连;行业用户(可以是政企相关行业的用户)可以利用应用服务器通过运营商的网络能力开放层与运营商网络相连接,网络能力开放层可以执行运营商网络能力的开放,应用服务器可以是三方服务器,例如政府、公安、消防、交通,或其他企业的专用服务器。
一个应用服务器下的一个用户群组内的众多用户终端可能有相同的背景流量下载需求。本发明实施例中所述的背景流量下载是指一种非紧急(可以在网络空闲时进行传输)数据业务的传输,可以是在网络较空闲的时间段,服务器向用户设备传输非紧急的数据,这些数据可以是用于应用的升级的数据,也可以是推送消息的数据等。
通常,一个区域内需要存在很多需要下载背景流量的用户终端,PCRF就会为各用户终端制定背景流量下载策略。而各用户终端请求的数据可能相同、请求的时间窗也可能相同。这样就意味着PCRF需要做重复响应(制定多个相同的背景流量下载策略),增加网络开销。另外,如果网络侧为各个用户终端确定的下载时间窗均相同,网络侧同时向各个用户终端发起背景流量传输。如果临近区域存在大量用户终端,网络侧同时向各个用户终端传输数据,就很可能导致该地区网络的拥塞。
本发明实施例提供的方法,旨在为群组制定一个背景流量下载策略,避免PCRF对来自应用服务器的请求作重复响应,同时避免由于背景流量下载业务造成的网络拥塞。
实施例1:
本发明实施例还提供了一种背景流量下载方法,执行主体可以为网络感知调度设备,所述网络感知调度设备可以是部署在运营商网络的网络感知调度单元RPSF,如图2所示,所述方法包括以下步骤:
201、网络感知调度设备接收应用服务器发送的背景流量下载请求消息,所述背景流量下载请求消息携带对用户群组进行背景流量下载所需的需求信息。
其中,所述需求信息包括以下信息中的至少一项:所述用户群组进行背景流量下载所需的流量值、所述用户群组进行背景流量下载所需的时间窗、所述用户群组的区域信息。所述用户群组是所述应用服务器提供服务的多个用户群组中的一个。
需要说明的是,网络感知调度设备可以对运营商网络的状态信息进行收集,以便确定运营商网络是否支持应用服务器的背景流量下载请求(应用服务器为第一群组发起的背景流量下载请求)。背景流量下载是一种非紧急(可以在网络空闲时进行传输)数据业务的传输,例如升级终端应用、更新终端数据库、消息推送等。
202、所述网络感知调度设备根据所述需求信息生成所述用户群组的背景流量下载策略和所述背景流量下载策略的标识。
这里,不论应用服务器发送的背景流量下载请求消息中所述用户群组进行背景流量下载所需的流量值、所述用户群组进行背景流量下载所需的时间窗、所述用户群组的区域信息中的哪几项,网络感知调度设备都可以为所述用户群组制定出一个背景流量下载策略。该背景流量下载策略是所述用户群组进行背景流量下载的策略信息,利用该背景流量下载策略为用户群组提供群组服务,满足各个用户终端的背景流量下载需求。本发明提供的方法,网络感知调度单元为所述用户群组制定一个进行背景流量下载的背景流量下载策略,不需要为每个用户终端生成背景流量下载策略,避免运营商的策略单元(策略与计费制定设备)对来自应用服务器的同类请求做重复响应。另外,所述背景流量下载策略的标识是与所述背景 流量下载策略唯一对应的标识,即不同的背景流量下载策略对应的标识也是不同的。网络感知调度设备只需要根据所述背景流量下载策略的标识,就可以确定出所述背景流量下载策略。
由于应用服务器可能对应多个群组,因此网络感知调度设备为每个群组的背景流量下载业务生成相应的背景流量下载策略之后,都会为各个背景流量下载策略生成一个唯一对应的策略标识,以便可以根据该策略标识快速锁定一个背景流量下载策略。另外,所述背景流量下载策略中还可以包含所述用户群组的标识信息,就可以确定所述背景流量下载策略的标识对应的背景流量下载策略是网络感知调度设备为所述用户群组群组进行背景流量下载所生成的背景流量下载策略。
203、所述网络感知调度设备向所述应用服务器发送所述背景流量下载策略的标识。
具体地,网络感知调度设备可以通过开放平台,发送所述策略标识给应用服务器。该开放平台(即网络能力开放层exposure layer)可能具有协议转化功能。
这里,网络感知调度设备将策略标识发送给应用服务器,以便所述应用服务器将所述策略标识包含在背景流量下载启用请求中发送给策略与计费制定设备。
204、所述网络感知调度设备接收策略与计费制定设备发送的所述背景流量下载策略的标识,根据所述背景流量下载策略的标识确定所述用户群组的所述背景流量下载策略,将所述背景流量下载策略发送给所述策略与计费制定设备,以便所述策略与计费制定设备根据所述背景流量下载策略确定背景流量下载的策略与计费控制。
其中,策略与计费制定设备可以是策略与计费制定单元PCRF。具体实现中,所述策略与计费制定设备接收所述网络感知调度设备发送的所述背景流量下载策略之后,根据所述背景流量下载策略生成所述用户群组进行背景流量下载的策略与计费控制,即为确定能 够满足所述用户群组的背景流量下载请求的具体网络传输策略。所述策略与计费制定设备再将所述策略与计费控制发送给策略与计费控制设备。所述策略与计费控制设备根据所述策略与计费控制为所述用户群组的背景流量下载分配承载资源。最后由应用服务器向各用户终端传输数据。
由于应用服务器可能对应多个群组,因此网络感知调度设备可能为多个群组制定了对应的背景流量下载策略。这样,网络感知调度设备只有根据所述策略与计费制定设备发送的所述策略标识才能唯一确定一个背景流量下载策略。
优选地,在本方明的优选实施例中,所述背景流量下载策略包括以下信息中的至少一项:
允许的下载时间窗、单个用户终端的计费信息、单个用户终端的最大下载速率、所述用户群组的汇聚下载速率的最大值、不同汇聚下载速率下的计费策略。
其中,所述允许的下载时间窗,可以是允许的下载时间窗,也可以是受限于其他因素而确定的时间窗,在此不做限定。另外,所述背景流量下载策略可以是以下几种:
允许的下载时间窗、单用户的最大下载速率以及单用户的计费信息。
或者,允许的下载时间窗、单用户的最大下载速率以及单用户的计费信息。
或者,允许的下载时间窗、所述用户群组的汇聚下载速率的最大值以及不同汇聚下载速率下的计费策略。所述不同汇聚下载速率下的计费策略具体可以是:所述汇聚下载速率小于等于最大值时的计费策略以及所述汇聚下载速率大于最大值时的计费策略。
需要说明的是,生成的背景流量下载策略中,可能有多个允许的下载时间窗,在此不作限定。
优选地,在本方明的优选实施例中,所述方法还包括;
若所述需求信息包括所述用户群组进行背景流量下载所需的 时间窗,则所述背景流量下载策略包括所述允许的下载时间窗;其中,所述用户群组进行背景流量下载所需的时间窗包含所述允许的下载时间窗。也可以是所述允许的下载时间窗被包含在所述用户群组进行背景流量下载所需的时间窗内。
若所述需求信息包括所述用户群组进行背景流量下载所需的流量值,则所述背景流量下载策略包括所述用户群组的汇聚下载速率的最大值或所述用户群组中单个用户终端的最大下载速率;其中,所述用户群组的汇聚下载速率的最大值或所述用户群组中单个用户终端的最大下载速率由所述用户群组进行背景流量下载所需的流量值确定。
具体地,若所述用户群组进行背景流量下载所需的流量值为所述用户群组进行背景流量下载的总流量值,则所述网络感知调度设备根据所述总流量值、所述允许的下载时间窗确定所述用户群组的汇聚下载速率的最大值。若所述用户群组进行背景流量下载所需的流量值为所述用户群组中单个用户终端进行背景流量下载的单位流量值与所述用户群组中用户终端的数量,则所述网络感知调度设备根据所述单位流量值、所述允许的下载时间窗确定所述用户群组中单个用户终端的最大下载速率。
另外,若所述需求信息包括所述用户群组的区域信息,则,所述网络感知调度单元根据所述用户群组的区域信息对应的区域的网络状态,判断网络是否能够满足所述用户群组的背景流量下载请求。
优选地,在本发明的优选实施例中,若所述需求信息包括所述用户群组进行背景流量下载所需的时间窗。
则,在所述网络感知调度单元根据所述需求信息生成所述用户群组的背景流量下载策略和所述背景流量下载策略的标识之前,所述方法还包括:
所述网络感知调度单元判断在所述用户群组进行背景流量下载所需的时间窗内网络是否满足所述应用服务器的背景流量下载 请求。若所述网络感知调度单元确定网络在所述用户群组进行背景流量下载所需的时间窗内能够满足所述应用服务器的背景流量下载请求,则执行所述“根据所述需求信息生成所述用户群组的背景流量下载策略和所述背景流量下载策略的标识”。
优选地,在本发明的优选实施例中,若所述网络感知调度单元确定网络在所述用户群组进行背景流量下载所需的时间窗内不能满足所述应用服务器的背景流量下载请求。
则,所述网络感知调度单元生成指示策略生成失败的消息,并向所述应用服务器发送所述指示策略生成失败的消息。
优选地,在本发明的优选实施例中,在所述网络感知调度单元向所述应用服务器发送所述指示策略生成失败的消息之后,所述方法还包括:
所述网络感知调度单元发送定时信息给所述应用服务器,使得所述应用服务器间隔所述定时信息后通过所述开放平台向所述网络感知调度单元发送所述背景流量下载请求消息。
本发明实施例提供的背景流量下载方法,网络感知调度设备在接收应用服务器请求为用户群组建立背景流量下载业务而发送的背景流量下载请求消息之后,根据所述用户群组进行背景流量下载的需求信息及网络的状态,判断网络是否能够满足应用服务器的背景流量下载请求(应用服务器为所述用户群组发起的背景流量下载请求)。在确定网络能够满足所述用户群组的背景流量下载请求后为所述用户群组生成背景流量下载策略,并生成该背景流量下载策略的策略标识,以便根据所述策略标识确定所述用户群组的背景流量下载策略。本发明实施例提供的方法,网络感知调度设备(可以是网络感知调度单元RPSF)为一个用户群组生成一个背景流量下载策略,不需要为每个用户终端生成背景流量下载策略,节省网路开销。
本发明实施例还提供了一种背景流量下载方法,执行主体为策略与计费制定设备,所述策略与计费制定设备可以是部署在运营商 网络的策略与计费制定单元PCRF,如图3所示,所述方法包括以下步骤:
301、策略与计费制定设备接收应用服务器发送的背景流量下载启用请求,所述背景流量下载启用请求携带用户群组的背景流量下载策略的标识。
这里,前提是网络感知调度设备确定网络能够满足用户群组的背景流量下载请求,且为所述用户群组制定了背景流量下载策略,并将所述背景流量下载策略的标识发送给应用服务器。这样应用服务器再给策略与计费制定设备发送背景流量下载启用请求。
302、所述策略与计费制定设备将所述背景流量下载策略的标识发送至网络感知调度设备。
所述策略与计费制定设备根据背景流量下载启用请求中包含的背景流量下载策略的标识,向网络感知调度设备请求所述用户群组的背景流量下载策略。
具体地,策略与计费制定设备将所述背景流量下载策略的标识发送给所述网络感知调度设备,使得网络感知调度设备在其生成的多个背景流量下载策略(为不同的用户群组的背景流量下载业务生成的背景流量下载策略)中,根据背景流量下载启用请求中包含的背景流量下载策略的标识可以确定出一个背景流量下载策略,即网络感知调度设备为所述用户群组进行背景流量下载生成的背景流量下载策略。
303、所述策略与计费制定设备接收所述网络感知调度设备返回的所述用户群组的背景流量下载策略。
这里,由于之前网络感知调度设备根据所述用户群组进行背景流量下载所需的需求信息为所述用户群组生成对应的背景流量下载策略,以及该背景流量下载策略的标识。另外由于该背景流量下载策略的标识可能包含所述用户群组的标识信息。因此,策略与计费制定设备根据该背景流量下载策略的标识中包含的所述群组的标识信息,确定该背景流量下载策略是所述用户群组对应的背景流 量下载策略。
304、所述策略与计费制定设备根据所述背景流量下载策略,确定背景流量下载的策略与计费控制。
实际上,是所述策略与计费制定设备根据网络感知调度设备为所述用户群组生成的背景流量下载策略,确定具体的网络传输策略。
需要说明的是,策略与计费控制可以包括很多参数,有的参数是负责计费的,有的参数则是负责其他控制。在本发明中,所述策略与计费控制可以只有其中一部分参数。
优选地,在本发明的优选实施例中,若所述背景流量下载启用请求中还包括所述用户群组中需要下载背景流量的各用户终端的IP地址,则所述策略与计费制定设备根据所述背景流量下载策略,生成所述用户群组进行背景流量下载所需的策略控制和计费控制包括:
所述策略与计费制定设备根据所述背景流量下载策略、所述用户群组中需要下载背景流量的各用户终端的IP地址,为所述用户群组中需要下载背景流量的各用户终端确定专用承载建立时刻和最大下载速率。
优选地,在本发明的优选实施例中,所述策略与计费制定设备将所述策略与计费控制发送给策略与计费执行设备,以便所述策略与计费执行设备根据所述策略与计费控制为背景流量下载分配承载资源。
另外在上一优选实施例中,由于所述策略与计费制定设备为所述用户群组中需要下载背景流量的各用户终端确定专用承载建立时刻和最大下载速率,使得应用服务器可以向需要下载背景流量的用户终端传输数据。可以在一定程度上避免由于同时向用户群组中的各个用户终端传输数据造成的网络拥塞。
优选地,在本发明的优选实施例中,所述策略与计费制定设备根据所述背景流量下载策略,确定背景流量下载的策略与计费控 制,具体包括:
所述策略与计费制定单元根据所述背景流量下载策略,为各用户终端确定同一专用承载建立时刻,以及同一最大下载速率。
或,所述策略与计费制定单元根据所述背景流量下载策略,分别为各用户终端确定专用承载建立时刻、最大下载速率;所述各用户终端的承载建立时刻不完全相同,所述各用户终端的最大下载速率不完全相同。
其中,各用户终端的承载建立时刻均为所述背景流量下载策略中包含的允许的下载时间窗内的一个时刻。
需要说明的是,对各个用户终端的承载建立时间并不做限定,只要在背景流量下载策略中的时间窗内即可。
本发明实施提供的背景流量下载方法,策略与计费制定设备接收应用服务器发送的背景流量下载启用请求(为用户群组的背景流量下载发送的请求),根据该背景流量下载启用请求中携带的背景流量下载策略的标识向网络感知调度设备请求对应的背景流量下载策略。根据所述网络感知调度设备返回的背景流量下载策略,生成所述用户群组的背景流量下载的策略与计费控制。另外,若策略与计费制定设备应用服务器接收的背景流量下载启用请求中包含所述用户群组中需要下载背景流量的各用户终端的IP地址,就可以根据各用户终端的IP地址生成需要下载背景流量的各用户终端的策略与计费控制,使得策略与计费控制执行设备为需要下载背景流量的各用户终端分配承载资源,以便应用服务器向需要下载背景流量的各用户终端传输数据。这样,避免由于同时向所述组中的每个用户终端传输数据所造成的网络拥塞。
本发明实施例提供了一种背景流量下载方法,执行主体为应用服务器,所述应用服务器对应至少一个群组。如图4所示,所述方法包括以下步骤:
401、应用服务器向网络感知调度设备发送背景流量下载请求消息,所述背景流量下载请求消息携带对用户群组进行背景流量下 载所需的需求信息。
其中,所述需求信息包括以下信息中的至少一项:所述用户群组进行背景流量下载所需的流量值、所述用户群组进行背景流量下载所需的时间窗、所述用户群组的区域信息。
另外,所述用户群组为该应用服务器对应的群组中,需要进行背景流量下载的群组中的至少一个。所述应用服务器可以是第三方服务器,例如政府、公安等行业的服务器。所述用户群组中的多个用户或全部用户将接收来自于应用服务器的背景流量信息,所述背景流量信息可以是群组应用的系统信息,也可以是群组用户统一订阅的周期性信息,也可以是其他内容相同的任何类型信息。所述用户群组进行背景流量下载所需的流量值为应用服务器预计的、所述用户群组进行背景流量下载需要的流量值。所述用户群组的区域信息指应用服务器所选择的提供背景流量下载服务的区域范围的区域信息,该区域范围与运营商的跟踪区,eNB,小区,路由区,服务区中的一个或多个相对应。
本发明提供的背景流量下载方法中,应用服务器向网络感知调度设备发送用户群组进行背景流量下载所需的需求信息,以便网络感知调度设备为群组制定一个背景流量下载策略,避免网络侧的策略制定单元(可以是PCRF)对同样的请求作重复响应,节省了网络开销。
402、所述应用服务器接收所述网络感知调度设备发送的所述用户群组的背景流量下载策略的标识。
这里,应用服务器接收到了网络感知调度设备发送的所述用户群组的背景流量下载策略的标识,证明网络感知调度设备确定网络满足应用服务器的背景流量下载请求(即应用服务器为所述用户群组发起的背景流量下载请求),并为所述用户群组生成了背景流量下载策略。若应用服务器未接收到所述网络感知调度设备发送的所述用户群组的背景流量下载策略的标识,则会接收到所述网络感知调度设备发送的指示策略生成失败的消息,证明网络感知调度设备 确定网络不能满足应用服务器的背景流量下载请求。
另外,还可以根据所述用户群组的背景流量下载策略的标识携带所述用户群组的标识信息,确定该背景流量下载策略是为所述用户群组制定的背景流量下载策略。
403、所述应用服务器向策略与计费制定设备发送背景流量下载启用请求,所述背景流量下载启用请求中携带所述背景流量下载策略的标识,以便所述策略与计费制定设备根据所述背景流量下载启用请求获取所述用户群组的背景流量下载策略,确定背景流量下载的策略与计费控制。
其中,策略与计费制定设备可以是运营商网络的PCRF,通过Np接口与RPSF相连,实现策略与计费制定功能。
这里,应用服务器需要先向PCRF发送背景流量下载启用请求,再由PCRF向RPSF请求与应用服务器发送的背景流量下载启用请求包含的所述用户群组的背景流量下载策略的标识对应的背景流量下载策略(即RPSF为所述用户群组生成的背景流量下载策略),最后由PCRF根据所述背景流量下载启用请求获取所述用户群组的背景流量下载策略,确定背景流量下载的策略与计费控制。之后,PCRF再将所述策略与计费控制发送给策略与计费控制执行设备,由策略与计费控制执行设备根据所述策略与计费控制为所述用户群组中的用户终端分配承载资源。最后,由应用服务器向所述用户群组中的用户终端传输数据。
优选地,在本发明的优选实施例中,所述应用服务器向网络感知调度设备发送背景流量下载请求消息之前,所述方法还包括:
所述应用服务器获取所述需求信息,生成携带有所述需求信息的背景流量下载请求消息,并将所述背景流量下载请求消息向网络感知调度单元发送;以便于所述网络感知调度单元根据所述需求信息生成所述用户群组的背景流量下载策略以及所述背景流量下载策略的标识。
其中,网络感知调度设备可以是运营商网络的RPSF,用以收 集、分析、预测运营商网络的网络状态信息,支持应用服务器对运营商网络的网络资源的管理调用。另外,应用服务器可以通过开放平台(网络能力开放层Exposure layer)向网络感知调度单元发送背景流量下载请求消息。该开放平台,与应用服务器、RPSF连接,实现应用服务器与运营商网络的通信。该开放平台,可能具有协议转换功能,可以将来自运营商域内接口的协议与外部服务器(例如本发明实施例中所述的应用服务器)所使用接口的协议进行转换。
优选地,在本发明的优选实施例中,所述应用服务器接收所述网络感知调度设备发送的所述背景流量下载策略的标识之后,所述方法还包括:
所述应用服务器获取所述用户群组中需要下载背景流量的各用户终端的IP地址;
则,所述背景流量下载启用请求还包括所述用户群组中需要下载背景流量的各用户终端的IP地址,以便所述策略与计费制定设备根据确定所述用户群组中需要进行背景流量下载的各用户终端的策略与计费控制,即所述用户群组中需要进行背景流量下载的用户终端的专用承载建立时刻以及最大下载速率。其中,各用户终端的专用承载建立时刻不完全相同,各用户终端的最大下载速率不完全相同。
优选地,在本发明的优选实施例中,所述应用服务器获取所述用户群组内所有用户终端进行背景流量下载的总流量值,将所述总流量值作为所述用户群组进行背景流量下载需要的流量值。
或,获取所述用户群组内的用户终端的数量以及单个用户终端进行背景流量下载需要的单位流量值,将所述单位流量值与所述用户群组内的用户终端的数量的乘积作为所述用户终端进行背景流量下载需要的流量值,其中,各用户终端进行背景流量下载需要的流量值相同。
优选地,在本发明的优选实施例中,所述应用服务器确定所述用户群组进行背景流量下载所需的时间窗,具体包括:
所述获取所述用户群组进行背景流量下载所需的时间窗,具体包括:
所述应用服务器获取所述用户群组进行背景流量下载所需的时间段,将所述时间段确定为所述用户群组进行背景流量下载所需的时间窗。
或者,确定所述用户群组进行背景流量下载的起始时刻以及从所述起始时刻开始的计时信息,根据所述起始时刻以及从所述起始时刻开始的计时信息确定所述用户群组进行背景流量下载所需的时间窗。
优选地,在本发明的优选实施例中,所述用户群组的区域信息为所述用户群组对应的区域的区域信息。其中,所述用户群组对应的区域对应运营商定义的跟踪区、演进基站eNB、路由区、小区中的一个或多个。
优选地,在本发明的优选实施例中,所述应用服务器接收所述网络感知调度单元发送的指示策略生成失败的消息;
所述应用服务器接收所述网络感知调度单元发送的定时信息,并间隔所述定时信息后通过所述开放平台向所述网络感知调度单元发送所述背景流量下载请求消息。
本发明实施例提供的背景流量下载方法,应用服务器获取一个群组进行背景流量下载所需的需求信息,以便运营商网络的网络感知调度设备生成该群组进行背景流量下载的背景流量下载策略,可以避免网络感知调度设备对来自应用服务器的同样的请求作重复响应,为用户群组中的各个用户终端制定相同的背景流量下载策略。另外,应用服务器在确定网络侧满足该群组的背景流量下载请求后确定该群组中需要下载背景流量的用户终端的IP地址,以便运营商网络的策略与计费制定设备确定所述用户群组中需要进行背景流量下载的各用户终端的策略与计费控制,进而由策略与计费控制执行设备为所述用户群组中需要下载背景流量的用户终端分配承载资源,最后由应用服务器向所述用户群组中需要进行背景流 量下载的用户终端传输数据。可以在一定程度上避免由于同时向群组中的每个用户终端传输数据所造成的网络拥塞。
实施例2:
本发明实施例提供了一种背景流量下载方法,应用于背景流量管理系统,所述背景流量管理系统包括:应用服务器、开放平台(网络能力开放层exposure layer)、提供网络感知、调度功能的网络感知调度设备(例如RPSF)以及提供策略与计费制定功能的策略与计费制定设备(例如PCRF)。如图5所示,所述方法包括以下步骤:
501、应用服务器获取对用户群组进行背景流量下载所需的需求信息,生成携带所述需求信息的背景流量下载请求消息,并向网络感知调度设备发送所述背景流量下载请求消息。
其中,所述用户群组中包括至少一个用户终端。所述需求信息包括以下信息中的至少一项:所述用户群组进行背景流量下载所需的流量值、所述用户群组进行背景流量下载所需的时间窗、所述用户群组的区域信息。
关于用户群组进行背景流量下载的需求信息,作出以下说明:所述用户群组进行背景流量下载需要的流量值可以是所述用户群组中所有用户进行背景流量下载所需要的总流量值。也可以是获取所述用户群组内用户数量与单用户进行背景流量所需要的单位流量值,根据所述用户群组内用户数量与所述单位流量值确定所述用户群组进行背景流量下载需要的流量值。需要说明的是,在此假设所述用户群组内各用户进行背景流量下载需要的流量值(接收的背景流量值)相同。
本发明实施例提供的方法确定群组进行背景流量下载的需求信息,进而使得网络感知调度设备为群组生成一个背景流量下载策略。避免策略与计费制定设备对同样的请求作重复响应,多次生成同样的背景流量下载策略,进而可以节省网络开销。
示例地,若用户群组中有10个用户终端,且每个用户终端都 会向应用服务器发送背景流量下载请求,这样,策略与计费制定设备就会为这10个用户终端生成10个背景流量下载策略。而本发明实施例提供的方法,网络感知调度设备针对群组中的10个用户终端只需要生成一个背景流量下载策略,即可实现各用户终端请求的背景流量下载业务。
502、网络感知调度设备接收应用服务器发送的背景流量下载请求消息,判断网络是否能够满足所述用户群组的背景流量下载请求。
其中,所述背景流量下载请求消息携带对用户群组进行背景流量下载所需的需求信息。
当所述需求信息中包含所述用户群组进行背景流量下载所需的时间窗,所述网络感知调度设备就需要判断在所述用户群组进行背景流量下载所需的时间窗内网络是否满足所述应用服务器的背景流量下载请求。在本实施例中,假设所述需求信息中包含所述用户群组进行背景流量下载所需的时间窗。
示例地,若需求信息包括所述用户群组进行背景流量下载所需的时间窗时,网络感知调度设备则判断运营商网络在所述用户群组进行背景流量下载所需的时间窗内是否能够满足应用服务器的背景流量下载请求。需要说明的是若所述用户群组的需求信息中不包含所述用户群组进行背景流量下载所需的时间窗,网络感知调度设备可以不判断网络是否能够满足所述应用服务器的背景流量下载请求,直接进行步骤505。
若判断网络不能够满足所述应用服务器的背景流量下载请求则进行步骤503;若判断网络能够满足所述应用服务器的背景流量下载请求,则进行步骤505。
503、网络感知调度设备则生成指示策略生成失败的消息,并向应用服务器发送该指示策略生成失的败消息,并发送定时信息给所述应用服务器。
这里,由于所述用户群组进行背景流量下载的需求信息中包括 为所述用户群组进行背景流量下载所需的时间窗,且网络感知调度设备判断运营商网络在所述用户群组进行背景流量下载所需的时间窗内不能满足应用服务器发送的背景流量下载请求,则网络感知调度设备生成指示策略生成失败的消息,且指示策略生成失败的消息包含的失败原因值为网络状况不满足条件。
网络感知调度设备发送定时信息给所述应用服务器,使得应用服务器间隔定时信息后通过开放平台向所述网络感知调度设备发送所述背景流量下载请求消息。若网络感知调度设备还是判断运营商网络不能满足应用服务器的背景流量下载请求,则应用服务器可以间隔定时信息后通过开放平台再次向所述网络感知调度设备发送所述背景流量下载请求消息。
504、应用服务器接收所述网络感知调度设备发送的定时信息,并间隔所述定时信息后通过开放平台向所述网络感知调度设备发送所述背景流量下载请求消息。
505、网络感知调度设备根据所述需求信息生成所述用户群组的背景流量下载策略以及所述背景流量下载策略的标识;发送所述背景流量下载策略的标识给应用服务器。
其中,所述背景流量下载策略的标识还可以包含所述用户群组的标识信息。
需要说明的是,若所述用户群组进行背景流量下载的需求信息包括所述用户群组的区域信息,网络感知调度设备则可以判断对应的区域的网络是否满足用户群组的背景流量下载请求。参照图1,网络感知调度设备(以RPSF为例)获取所述用户群组区域(所述用户群组的区域信息对应的区域)的网络状态具体包括:RPSF通过Np接口,Nq接口由PCRF与MME得到的相应区域内网络状态信息。其中,网络状态信息包括区域内网络负载状况、拥塞状况,还可以包括对未来一段时间内网络状况的预测情况等信息。
示例地,网络感知调度设备根据所述用户群组的需求信息为所述用户群组生成背景流量下载策略有以下可能:
1)、若所述用户群组的需求信息包括所述用户群组进行背景流量下载需要的时间窗,则网络感知调度设备根据网络在所述用户群组
背景流量下载需要的时间窗内确定所述允许的下载时间窗,且所述用户群组进行背景流量下载所需的时间窗包含所述允许的下载时间窗,或所述允许的下载时间窗被包含在所述用户群组进行背景流量下载所需的时间窗内。
2)、若所述用户群组的需求信息包括所述用户群组进行背景流量下载需要的流量值,且所述用户群组进行背景流量下载需要的流量值为所有用户群组中各用户终端进行背景流量下载的总流量值,则网络感知调度设备根据所述总流量值确定所述用户群组的汇聚下载速率。若所述用户群组进行背景流量下载需要的流量值为所述用户群组内的用户终端的数量、所述用户群组中单个用户终端进行下载背景流量需要的单位流量值这两个信息,则网络感知调度设备根据所述单位流量值,确定所述单用户的最大下载速率。
通常,应用服务器可能对应多个群组,应用服务器可能会为多个群组请求背景流量下载。而网络感知调度设备可能要为多个群组制定背景流量下载的背景流量下载策略。因此,网络感知调度设备为每个群组生成背景流量下载策略之后,还会生成每个背景流量下载策略的标识。示例地,若所述用户群组为所述应用服务器对应的多个群组中的一个,网络感知调度设备在为所述用户群组生成背景流量下载策略之后还会生成该背景流量下载策略的标识,该标识还可以包含所述用户群组的标识信息。以便确定该背景流量下载策略是为所述用户群组生成的背景流量下载策略。
506、应用服务器接收网络感知调度设备发送的所述用户群组的背景流量下载策略的标识,确定所述用户群组中需要下载背景流量的各用户终端的IP地址。
这里,应用服务器接收到了网络感知调度设备发送的所述用户群组的背景流量下载策略的标识,则表明所述用户群组的背景流量 下载策略生成成功。进而,应用服务器确定所述用户群组中需要下载背景流量的各用户终端的IP地址,使得网络侧有目标性地向需要下载背景流量的用户终端传输数据,而不是在同时向群组内的每个用户终端传输数据,可以在一定程度上缓解由于同时向群组内的每个用户终端传输数据导致的网络拥塞。
507、应用服务器向策略与计费制定设备发送背景流量下载启用请求。
其中,背景流量下载启用请求中包含网络感知调度设备为所述用户群组生成的背景流量下载策略的标识以及所述用户群组中需要下载背景流量的各用户终端的IP地址,以便策略与计费制定设备根据所述背景流量下载策略、所述用户群组中需要下载背景流量的各用户终端的IP地址,为所述用户群组中需要下载背景流量的各用户终端确定专用承载建立时刻和最大下载速率。
508、策略与计费制定设备接收应用服务器发送的背景流量下载启用请求,并将该背景流量下载启用请求包含的背景流量下载策略的标识发送给网络感知调度设备。
依照步骤507所述,背景流量下载启用请求中包含网络感知调度设备为所述用户群组生成的背景流量下载策略的标识,根据该背景流量下载策略的标识,向网络感知调度设备获取所述用户群组的背景流量下载策略。
509、网络感知调度设备接收策略与计费制定设备发送的背景流量下载策略的标识,根据该标识确定所述用户群组的背景流量下载策略,将所述用户群组的背景流量下载策略发送给所述策略与计费制定设备。
这里,网络感知调度设备是在其制定的多个背景流量下载策略中根据策略与计费制定设备发送的标识确定一个背景流量下载策略,将该背景流量下载策略发送给策略与计费制定设备,以便所述策略与计费制定设备根据该背景流量下载策略确定背景流量下载的策略与计费控制。
510、策略与计费制定设备接收所述网络感知调度设备返回的所述用户群组的背景流量下载策略。
另外,由于所述背景流量下载策略的标识还可以包括所述用户群组的标识信息,策略与计费制定设备就可以根据所述背景流量下载策略的标识包含的所述用户群组的标识信息确定所述背景流量下载策略是所述网络感知调度单元为所述用户群组生成的背景流量下载策略。
511、策略与计费制定设备根据所述背景流量下载策略,确定背景流量下载的策略与计费控制;将所述策略与计费控制发送给策略与计费执行设备。
这里,策略与计费制定设备将所述策略与计费控制发送给策略与计费执行设备,以便所述策略与计费执行设备根据所述策略与计费控制为背景流量下载分配承载资源。
具体实现中,策略与计费制定设备确定所述用户群组中需要下载背景流量的用户终端的PCC(Policy and Charging Control,策略与计费控制)策略。这里所述各用户终端均为需要下载背景流量的用户终端。该PCC策略为:单用户终端的承载建立时刻,以及单用户的最大下载速率。其中,各用户终端的触发时刻相同,及均为上述承载建立时刻,各用户终端的最大下载速率也相同。
或者,该PCC策略为:各个用户终端的承载建立时刻,以及各个用户的最大下载速率。其中,各用户终端的触发时刻不同,即专用承载建立时刻各不相同,各用户终端的最大下载速率也不相同。
需要说明的是,不管各个用户终端的承载建立时刻是否相同,各个用户终端的承载建立时刻都应该是网络感知调度设备反馈的背景流量下载策略中包含的允许的时间窗内的一个时刻。
512、所述策略与计费执行设备根据所述策略与计费控制为所述用户群组中,需要进行背景流量下载的用户终端分配承载资源,以便应用服务器向所述用户群组中需要下载背景流量的各用户终 端传输数据。
若步骤511中,策略与计费制定设备为所述用户群组请求的背景流量下载业务确定的PCC策略为:单用户终端的专用承载建立时刻,以及单用户的最大下载速率。则,应用服务器同时向各需要下载背景流量的用户终端传输数据。如果步骤506中未确定所述用户群组中需要下载背景流量的各用户终端的IP地址,这里应用服务器同时向所述用户群组中的用户终端传输数据,很有可能导致网络拥塞。如果只是向所述用户群组中需要下载背景流量的各用户终端传输数据,就可以在一定程度上避免网络拥塞。
若步骤511中,策略与计费制定设备为所述用户群组请求的背景流量下载业务确定的PCC策略为:各个用户终端的专用承载建立时刻,以及各个用户的最大下载速率。则,策略与计费控制执行设备在每个需要下载背景流量的用户终端的专用承载建立时刻,分别为每个需要下载背景流量的用户终端分配承载资源,进而应用服务器会在不同的时刻向各需要下载背景流量的用户终端传输数据。
本发明实施例提供的一种背景流量下载方法,应用服务器确定用户群组进行背景流量下载的需求信息,并发送携带所述需求信息的背景流量下载请求给网络感知调度单元。网络感知调度单元接收应用服务器发送的背景流量下载请求消息,为群组生成一个背景流量下载业务。现有技术中,应用服务器会将群组中的每个用户终端的背景流量下载请求转发给网络侧,策略与计费制定设备会为群组中的每个用户终端生成背景流量下载策略。而本发明网络感知调度单元为群组生成一个背景流量下载策略,不必为群组中每个用户终端生成背景流量下载策略,即避免网络侧对来自应用服务器的同类请求做重复响应。另外,应用服务器确定群组中需要下载背景流量的用户终端的IP地址,以便应用服务器向需要下载背景流量的用户终端传输数据。避免由于同时向群组中的每个用户终端传输数据而造成的网络拥塞。
实施例3:
本发明实施例提供了一种背景流量下载方法,应用于背景流量管理系统,所述背景流量管理系统包括:应用服务器、开放平台(网络能力开放层exposure layer)、提供网络感知、调度功能的网络感知调度设备(例如RPSF)以及提供策略与计费制定功能的策略与计费制定设备(例如PCRF)。与上述实施例2唯一不同的是:
若步骤505生成的背景流量下载策略为允许的下载时间窗、所述用户群组的汇聚下载速率的最大值、所述汇聚下载速率小于等于最大值时的计费策略以及所述汇聚下载速率大于最大值时的计费策略。则在步骤512之后,还包括:
策略与计费控制执行设备(可以是在线计费单元online charging system,OCS)收集当前的汇聚下载速率,将当前的汇聚下载速率发送给所述策略与计费制定设备;所述策略与计费制定设备判断当前的汇聚下载速率是否大于所述背景流量下载策略中规定的汇聚下载速率最大值,将不同汇聚下载速率下的计费信息发送给所述策略与计费控制执行设备;所述策略与计费控制执行设备根据相应的计费信息正确计费。
若当前的汇聚下载速率小于等于所述背景流量下载策略中规定的汇聚下载速率最大值,则根据背景流量下载策略中,当前的汇聚下载速率小于等于所述背景流量下载策略中规定的汇聚下载速率最大值时的计费策略进行计费。
若当前的汇聚下载速率大于所述背景流量下载策略中规定的汇聚下载速率最大值,则根据所述背景流量下载策略中,当前的汇聚下载速率大于所述背景流量下载策略中规定的汇聚下载速率最大值时的计费策略进行计费。
实施例4:
本发明实施例提供了一种背景流量下载方法,应用于背景流量管理系统,所述背景流量管理系统包括:AS(3rd application service,应用服务器)、网络能力开放层exposure layer、RPSF以及PCRF。如图6所示,所述方法包括以下步骤:
601、AS确定背景流量下载业务。
具体地,AS确定对所述用户群组进行背景流量下载所需的需求信息,并生成携带该需求信息的背景流量下载请求消息。
602、AS通过网络能力开放层向RPSF发送背景流量下载请求消息。
这是由于,AS与RPSF可能对应不同的协议,而网络能力开放层可能有协议转化的功能。因此AS需要通过网络能力开放层向RPSF发送该背景流量下载请求消息。
603、RPSF生成背景流量下载策略。
具体实现中,若所述需求信息包括所述用户群组的区域信息,RPSF通过Np接口,Nq接口由PCRF与MME得到所述用户群组的区域信息对应的区域内的网络状态信息。
另外,RPSF还会生成该背景流量下载策略的标识,另外,该标识还可以包含所述用户群组的标识信息。
需要说明的是,当所述需求信息包括所述用户群组进行背景流量下载所需的时间窗时,RPSF需要判断网络在所述用户群组进行背景流量下载所需的时间窗内是否能够满足应用服务器发送的背景流量下载请求,若满足则为所述用户群组生成背景流量下载策略;若不满足,则发送指示策略生成失败的消息给应用服务器。
604、RPSF将该背景流量下载策略的策略标识发送给AS。
605、AS向PCRF发送背景流量下载启用请求。
其中,该背景流量下载启用请求中包含与该背景流量下载策略的标识,以及AS确定的所述用户群组中需要下载背景流量的用户终端的IP地址。
606、PCRF向RPSF获取为所述用户群组生成的背景流量下载策略。
具体地,PCRF将与该背景流量下载策略的策略标识发送给RPSF,以便RPSF在其制定的多个背景流量下载的背景流量下载策略中根据该标识确定出为所述用户群组生成的背景流量下载策略。
607、PCRF确定PCC策略。
这里的PCC策略就是本发明实施例所述的策略与计费控制。
具体地,PCRF确定单用户终端的专用承载建立时刻,以及单用户的最大下载速率。或者,确定各个用户终端的专用承载建立时刻,以及各个用户的最大下载速率。
其中,所述单用户的专用承载建立时刻、所述各个用户终端的专用承载建立时刻均为所述背景流量下载策略中包含的允许的下载时间窗内的一个时刻。
608、PCRF将上述PCC策略发送给策略与计费控制设备。
609、策略与计费控制设备分配承载资源。
策略与计费执行设备根据所述策略与计费控制为背景流量下载分配承载资源。也可以是,为所述用户群组中需要进行背景流量下载的各用户终端分配承载资源。
610、AS向所述用户群组中需要下载背景流量的各用户终端传输数据。
具体地,AS根据预先确定的所述用户群组中需要进行背景流量下载的各用户终端的IP地址向对应的用户终端传输数据。
另外,若所述背景流量下载策略包括为所述允许的下载时间窗、所述用户群组的汇聚下载速率的最大值、所述汇聚下载速率小于等于最大值时的计费策略以及所述汇聚下载速率大于最大值时的计费策略。则,在610之后,所述方法还包括:策略与计费控制执行设备获取AS当前的汇聚下载速率,并进行正确计费。
具体实现参照实施例3中描述的具体计费方法,在此不作赘述。
本发明实施例提供的一种背景流量下载方法,AS确定群组进行背景流量下载的需求信息,并发送携带群组需求信息的背景流量下载请求给RPSF,请求网络侧为群组建立背景流量下载业务。RPSF接收AS发送的背景流量下载请求消息,并为群组生成一个背景流量下载策略。现有技术中,AS会将群组中的每个用户终端 的背景流量下载请求转发给PCRF,PCRF会为群组中的每个用户终端生成一个背景流量下载策略。而本发明RPSF为群组的背景流量下载业务制定一个背景流量下载策略,不必为群组中每个用户终端生成相应的背景流量下载策略,即避免网络侧对来自应用服务器的同类请求做重复响应。另外AS确定群组中需要下载背景流量的用户终端的IP地址,以便PCRF为所述用户群组中需要下载背景流量的用户终端生成策略与计费控制,进而由策略与计费控制执行设备为所述用户群组中需要下载背景流量的用户终端分配承载资源,应用服务器向需要下载背景流量的用户终端传输数据。避免由于同时向群组中的每个用户终端传输数据而造成的网络拥塞。
实施例5:
本发明实施例还提供了一种应用服务器7,如图7所示,所述应用服务器7包括:获取单元701、发送单元702、接收单元703。
获取单元701,用于获取对用户群组进行背景流量下载所需的需求信息。
其中,所述需求信息包括以下信息中的至少一项:所述用户群组进行背景流量下载所需的流量值、所述用户群组进行背景流量下载所需的时间窗、所述用户群组的区域信息。
需要说明的是,所述用户群组为该应用服务器对应的群组中,需要进行背景流量下载的群组。所述用户群组中的多个用户或全部用户将接收来自于应用服务器的背景流量。所述背景流量可以是群组应用的系统信息,可以是群组用户统一订阅的周期性信息,也可以是其他内容相同的任何类型信息。所述用户进行背景流量下载所需的流量值为获取单元701预计的、所述用户群组进行背景流量下载需要的流量值,可以是所述用户群组中各用户终端进行背景流量下载的中流量值,也可以是所述用户群组中单个用户终端进行背景流量下载的单位流量值与所述用户群组中的用户终端的数量这两个信息。
所述用户群组的区域信息指应用服务器所选择的提供背景流 量下载服务的区域范围的区域信息,该区域范围与运营商的跟踪区,演进基站eNB,小区,路由区,服务区中的一个或多个相对应。
发送单元702,用于将所述背景流量下载请求消息向网络感知调度单元发送。所述背景流量下载请求消息携带对用户群组进行背景流量下载所需的需求信息,以便于所述网络感知调度单元根据所述需求信息生成所述用户群组进行背景流量下载的背景流量下载策略和背景流量下载策略的标识。
其中,网络感知调度设备可以是运营商网络的RPSF,用以收集、分析、预测运营商网络的网络状态信息,支持应用服务器对运营商网络的网络资源的管理调用。开放平台(网络能力开放层Exposure layer),与应用服务器、RPSF连接,实现应用服务器与运营商网络的通信。该开放平台,可能具有协议转换功能,可以将来自运营商域内接口的协议与外部服务器(例如本发明实施例中所述的应用服务器)所使用接口的协议进行转换。
接收单元703,用于接收所述网络感知调度设备发送的所述用户群组的背景流量下载策略的标识。
这里,接收单元703接收到了网络感知调度设备发送的标识,证明网络感知调度设备确定网络满足应用服务器的背景流量下载请求(即应用服务器为所述用户群组发起的背景流量下载请求),并为所述用户群组制定了背景流量下载策略。若接收单元703未接收到所述网络感知调度设备发送的策略标识,则会接收到所述网络感知调度设备发送的指示策略生成失败的消息,证明网络感知调度设备确定网络不能满足应用服务器的背景流量下载请求(应用服务器为所述用户群组发起的背景流量下载请求)。
另外,背景流量下载策略的标识还有可能携带所述用户群组的标识信息,以便根据该标识确定一个背景流量下载策略之后,就可以确定该背景流量下载策略是为所述用户群组生成的背景流量下载策略。
发送单元702还用于,向策略与计费制定设备发送背景流量下 载启用请求,所述背景流量下载启用请求中携带所述背景流量下载策略的标识,以便所述策略与计费制定设备根据所述背景流量下载启用请求获取所述用户群组的背景流量下载策略,确定背景流量下载的策略与计费控制。
其中,策略与计费制定设备可以是运营商网络的PCRF,通过Np接口与RPSF相连,实现策略与计费制定功能。
这里,发送单元702需要先向PCRF发送背景流量下载启用请求,再由PCRF向RPSF请求与发送单元702发送的背景流量下载启用请求包含的策略标识对应的背景流量下载策略(即RPSF为所述用户群组生成的背景流量下载策略),最后由PCRF为所述用户群组中用户终端制定背景流量下载的策略与计费控制,以便为所述用户群组中的各用户终端传输数据。
所述获取单元701还用于,在所述接收单元703接收所述网络感知调度设备发送的所述用户群组的背景流量下载策略的标识之后,获取所述用户群组中需要下载背景流量的各用户终端的IP地址。
则,所述背景流量下载启用请求中还包括所述用户群组中需要下载背景流量的各用户终端的IP地址,以便PCRF为所述用户群组中,需要下载背景流量的各用户终端确定背景流量下载的策略与计费控制。
所述获取单元701具体用于,获取所述用户群组内的用户终端进行背景流量下载的总流量值,将所述总流量值作为所述用户群组进行背景流量下载所需的流量值。
所述获取单元701具体用于,获取所述用户群组内的用户终端的数量以及所述用户群组中单个用户终端进行背景流量下载需要的单位流量值,根据所述单位流量值与所述用户群组内的用户终端的数量的确定所述用户群组进行背景流量下载所需的流量值,其中,各用户终端进行背景流量下载需要的流量值相同。
所述获取单元701具体用于,获取所述用户群组进行背景流量 下载需要的时间段,将所述时间段确定为所述用户群组进行背景流量下载所需的时间窗。
所述获取单元701具体用于,获取所述用户群组进行背景流量下载的起始时刻以及从所述起始时刻开始的计时信息,根据所述起始时刻以及从所述起始时刻开始的计时信息确定所述用户群组进行背景流量下载所需的时间窗。
所述接收单元703用于,接收所述网络感知调度单元发送的指示策略生成失败的消息;接收所述网络感知调度单元发送的定时信息。
所述发送单元702还用于,间隔所述定时信息后通过所述开放平台向所述网络感知调度单元发送所述背景流量下载请求消息。
本发明实施例提供的应用服务器,获取一个群组进行背景流量下载需要的时间窗、进行背景流量下载需要的流量值、该群组的区域信息中的至少一项,以便运营商网络的网络感知调度设备为该群组制定背景流量下载的背景流量下载策略,可以避免网络感知调度设备对来自应用服务器的同样的请求作重复响应,多次制定同样的背景流量下载策略。另外,在确定网络侧满足该群组的背景流量下载请求后确定该群组中需要下载背景流量的用户终端的IP地址,以便运营商网络的策略与计费制定设备向需要下载背景流量的用户终端传输数据。可以在一定程度上避免由于同时向群组中的每个用户终端传输数据所造成的网络拥塞。
本发明实施例还提供了一种网络感知调度设备8,如图8所示,所述网络感知调度设备8包括:接收单元801、生成单元802、发送单元803与确定单元804。
接收单元801,用于接收应用服务器发送的背景流量下载请求消息,所述背景流量下载请求消息携带对用户群组进行背景流量下载所需的需求信息。
生成单元802,用于根据所述需求信息生成所述用户群组的背景流量下载策略和所述背景流量下载策略的标识。
其中,所述背景流量下载策略的标识还可以包括所述用户群组的标识信息。
另外,网络感知调度设备可以是运营商网络的RPSF,可以对运营商网络的状态信息进行收集,以便确定运营商是否支持应用服务器的背景流量下载请求(应用服务器为所述用户群组发起的背景流量下载请求),或者在确定运营商支持所述用户群组的背景流量下载请求之后,为所述用户群组制定对应的背景流量下载策略。
这里,不论应用服务器发送的背景流量下载请求消息中包含所述用户群组进行背景流量下载所需的流量值、所述用户群组进行背景流量下载所需的时间窗、所述用户群组的区域信息中的哪几项,生成单元802都可以为所述用户群组生成一个背景流量下载策略。生成单元802为群组制定一个背景流量下载策略,不需要为每个用户终端生成背景流量下载策略,避免运营商的策略单元(网络感知调度设备)对来自应用服务器的同类请求做重复响应。另外,当所述用户群组请求启动背景流量业务时,网络感知调度设备8只需要根据所述用户群组背景流量下载启动请求中包含的背景流量下载策略的标识,就可以锁定之前为所述用户群组生成的背景流量下载策略。
由于应用服务器可能对应多个群组,因此生成单元802为每个群组生成相应的背景流量下载策略之后,都会为各个背景流量下载策略生成一个唯一对应的标识,以便可以根据该标识快速锁定一个背景流量下载策略。示例地,在本发明实施例中,网络感知调度设备8根据策略与计费制定单元提供的背景流量下载策略的标识,就可以唯一确定一个背景流量下载策略,进一步,由于该标识包含所述用户群组的标识信息,就可以确定该背景流量下载策是网络感知调度设备为所述用户群组生成的背景流量下载策略。
发送单元803,用于向所述应用服务器发送所述背景流量下载策略的标识。
具体地,发送单元803通过开放平台,向所述应用服务器发送 所述背景流量下载策略的标识。
所述接收单元801还用于,接收策略与计费制定设备发送的所述背景流量下载策略的标识。
确定单元804,根据所述背景流量下载策略的标识确定所述用户群组的所述背景流量下载策略。
所述发送单元803,用于将所述背景流量下载策略发送给所述策略与计费制定设备,以便所述策略与计费制定设备根据所述背景流量下载策略确定背景流量下载的策略与计费控制。
所述生成单元802具体用于,若所述需求信息包括所述用户群组进行背景流量下载所需的流量值,则,根据所述用户群组进行背景流量下载所需的流量值确定所述用户群组的汇聚下载速率的最大值;或根据所述用户群组进行背景流量下载所需的流量值对应的单个用户终端的单位流量值,确定所述单用户的最大下载速率。
若所述需求信息包括所述用户群组进行背景流量下载所需的时间窗,则,所述允许的下载时间窗被包含在所述用户群组进行背景流量下载所需的时间窗内,或,所述用户群组进行背景流量下载所需的时间窗包含所述允许的下载时间窗。
网络感知调度设备8还包括判断单元。
所述判断单元用于,在所述生成单元802根据所述需求信息生成所述用户群组的背景流量下载策略和所述背景流量下载策略的标识之前,当所述需求信息包括所述用户群组进行背景流量下载所需的时间窗时,确定网络在所述用户群组进行背景流量下载所需的时间窗内能够满足所述应用服务器的背景流量下载请求。
所述生成单元802还用于,在所述判断单元确定网络在所述用户群组进行背景流量下载所需的时间窗内不能够满足所述应用服务器的背景流量下载请求之后,生成指示策略生成失败的消息。
所述发送单元803用于,向所述应用服务器发送所述指示策略生成失败的消息。
所述发送单元803用于,在向所述应用服务器发送所述指示策 略生成失败的消息之后,发送定时信息给所述应用服务器,使得所述应用服务器间隔所述定时信息后通过所述开放平台向所述网络感知调度单元发送所述背景流量下载请求消息。
本发明实施例提供的网络感知调度设备,在接收应用服务器请求为用户群组发送的背景流量下载请求消息之后,根据背景流量下载请求消息中包含的所述用户群组进行背景流量下载的需求信息以及网络的状态,判断网络是否能够满足应用服务器的背景流量下载请求。在确定网络能够满足所述用户群组的背景流量下载请求后,由生成单元802为所述用户群组生成一个背景流量下载策略并生成与该背景流量下载策略的标识,以便根据应用服务器发送的标识锁定为一个背景流量下载策略,另外,可以根据该标识包含的所述用户群组的标识信息确定该背景流量下载策略是为所述用户群组的背景流量下载业务生成的背景流量下载策略。
本发明实施例还提供了一种策略与计费制定设备9,如图9所示,所述策略与计费制定设备9包括:接收单元901、发送单元902、生成单元903。
接收单元901,用于接收应用服务器发送的背景流量下载启用请求,所述背景流量下载启用请求携带用户群组的背景流量下载策略的标识。
发送单元902,用于将所述背景流量下载策略的标识发送至网络感知调度设备。
所述接收单元901还用于,接收所述网络感知调度设备返回的所述用户群组的背景流量下载策略。
生成单元903,用于根据所述背景流量下载策略,确定背景流量下载的策略与计费控制。
所述生成单元903具体用于,当所述背景流量下载启用请求中还包括所述用户群组中需要下载背景流量的各用户终端的IP地址时,根据所述背景流量下载策略、所述用户群组中需要下载背景流量的各用户终端的IP地址,为所述用户群组中需要下载背景流量 的各用户终端确定专用承载建立时刻和最大下载速率。
所述发送单元902用于,将所述策略与计费控制发送给策略与计费执行设备,以便所述策略与计费执行设备根据所述策略与计费控制为背景流量下载分配承载资源。最后,由应用服务器向用户群组中的用户终端传输数据。
不同于现有技术,由于接收单元901接收的所述用户群组中需要下载背景流量的各用户终端的IP地址,生成单元903为所述用户群组中需要下载背景流量的各用户终端确定专用承载建立时刻和最大下载速率,所述策略与计费执行设备为所述用户群组中需要下载背景流量的各用户终端分配承载资源。最后,应用服务器向所述用户群组中需要下载背景流量的各用户终端传输数据。避免由于同时向所有用户终端传输数据而导致的网络拥塞。
需要说明的是,所述各用户终端的承载建立时刻不完全相同,所述各用户终端的最大下载速率不完全相同。其中,各用户终端的承载建立时刻均为所述背景流量下载策略中包含的允许的下载时间窗内的一个时刻。
本发明实施提供的策略与计费制定设备,接收应用服务器发送的背景流量下载启用请求,根据该背景流量下载启用请求中包含的标识向网络感知调度设备请求对应的背景流量下载策略。根据该背景流量下载策略的标识包含的用户群组的标识信息,确定网络感知调度设备反馈的背景流量下载策略是网络感知调度设备为所述用户群组生成的背景流量下载策略。最后,根据该背景流量下载启用请求中包含所述用户群组需要下载背景流量的用户终端的IP地址,为所述用户群组中的需要下载背景流量的各用户终端生成策略与计费控制,就可以向需要下载背景流量的用户终端传输数据,避免由于同时向所述用户群组中的每个用户终端传输数据所造成的网络拥塞。
实施例6:
本发明实施例还提供一种背景流量管理系统,包括:上述应用 服务器7、网络感知调度设备8、策略与计费制定9。
应用服务器确7定群组进行背景流量下载的需求信息,并发送包括群组需求信息的背景流量下载请求给网络感知调度设备8,请求网络侧为群组建立背景流量下载业务。网络感知调度设备8接收应用服务器7发送的背景流量下载请求消息,并为群组生成一个背景流量下载策略。本发明网络感知调度设备8为群组制定背景流量下载策略,不必为群组中每个用户终端生成背景流量下载策略,即避免网络感知调度设备8对来自应用服务器7的同类请求做重复响应,不必制定多个背景流量下载策略。另外,应用服务器7确定群组中需要下载背景流量的用户终端的IP地址,以便策略与计费制定设备为所述用户群组中需要下载背景流量的用户终端生成策略与计费控制。从而可以向所述用户群组中需要下载背景流量的用户终端传输数据,避免由于网络侧同时向群组中的每个用户终端传输数据而造成的网络拥塞。
本领域技术人员能够理解,上述图7至图9的实施例中,用于发送消息的发送单元可以采用发送器实现,或者采用收发器实现;用于接收消息的接收单元可以采用接收器实现,或者采用收发器实现。在物理实现上,发送器或者收发器可以用一个物理实体实现,也可采用多个物理实体实现,发送器和收发器可以采用一个物理实体实现,也可以采用多个物理实体实现,本发明对此不做限制;其他单元,如获取单元、生成单元、确定单元可以采用一个或多个处理器实现,本发明对此不做限制。
本发明实施例还提供了一种背景流量下载装置10,如图10所示,该背景流量下载装置10包括:发射器1001、接收器1002、存储器1003以及分别与发射器1001、接收器1002和存储器1003连接的处理器1004。当然,所述应用服务器10还可以包括基带处理部件、中射频处理部件、输入输出装置等通用部件,本发明实施例在此不做任何限制。其中,存储器1003中存储一组程序代码,且处理器1004用于调用存储器1003中存储的程序代码,用于执行图 2-图4所述的背景流量下载方法的方法流程。在执行图2所述的背景流量下载方法的方法流程时,所述背景流量下载装置10可以是网络感知调度设备;在执行图3所述的背景流量下载方法的方法流程时,所述背景流量下载装置10可以是策略与计费制定设备;在执行图4所述的背景流量下载方法的方法流程时,所述背景流量下载装置10可以是应用服务器。
本领域普通技术人员可以理解:实现上述方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成,前述的程序可以存储于计算机可读取存储介质中,该程序在执行时,执行包括上述方法实施例的步骤;而前述的存储介质包括:ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,仅为本发明的具体实施方式,但本发明的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本发明揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本发明的保护范围之内。因此,本发明的保护范围应以所述权利要求的保护范围为准。

Claims (25)

  1. 一种背景流量下载方法,其特征在于,所述方法包括:
    网络感知调度设备接收应用服务器发送的背景流量下载请求消息,所述背景流量下载请求消息携带对用户群组进行背景流量下载所需的需求信息;
    所述网络感知调度设备根据所述需求信息生成所述用户群组的背景流量下载策略和所述背景流量下载策略的标识;
    所述网络感知调度设备向所述应用服务器发送所述背景流量下载策略的标识;
    所述网络感知调度设备接收策略与计费制定设备发送的所述背景流量下载策略的标识,根据所述背景流量下载策略的标识确定所述用户群组的所述背景流量下载策略,将所述背景流量下载策略发送给所述策略与计费制定设备,以便所述策略与计费制定设备根据所述背景流量下载策略确定背景流量下载的策略与计费控制。
  2. 根据权利要求1所述的方法,其特征在于,所述需求信息包括以下信息中的至少一项:所述用户群组进行背景流量下载所需的流量值、所述用户群组进行背景流量下载所需的时间窗、所述用户群组的区域信息。
  3. 根据权利要求1或2所述的方法,其特征在于,所述背景流量下载策略包括以下信息中的至少一项:
    允许的下载时间窗、单个用户终端的计费信息、单个用户终端的最大下载速率、所述用户群组的汇聚下载速率的最大值、不同汇聚下载速率下的计费策略。
  4. 根据权利要求3所述的方法,其特征在于,
    若所述需求信息包括所述用户群组进行背景流量下载所需的时间窗,则所述背景流量下载策略包括所述允许的下载时间窗;其中,所述用户群组进行背景流量下载所需的时间窗包含所述允许的下载时间窗;
    或者,若所述需求信息包括所述用户群组进行背景流量下载所 需的流量值,则所述背景流量下载策略包括所述用户群组的汇聚下载速率的最大值或所述用户群组中单个用户终端的最大下载速率;其中,所述用户群组的汇聚下载速率的最大值或所述用户群组中单个用户终端的最大下载速率由所述用户群组进行背景流量下载所需的流量值确定。
  5. 根据权利要求1或2所述的方法,其特征在于,若所述需求信息包括所述用户群组进行背景流量下载所需的时间窗,
    则,在所述网络感知调度设备根据所述需求信息生成所述用户群组的背景流量下载策略和所述背景流量下载策略的标识之前,所述方法还包括:
    所述网络感知调度设备确定在所述用户群组进行背景流量下载所需的时间窗内网络能够满足所述应用服务器的背景流量下载请求。
  6. 一种背景流量下载方法,其特征在于,所述方法包括:
    策略与计费制定设备接收应用服务器发送的背景流量下载启用请求,所述背景流量下载启用请求携带用户群组的背景流量下载策略的标识;
    所述策略与计费制定设备将所述背景流量下载策略的标识发送至网络感知调度设备;
    所述策略与计费制定设备接收所述网络感知调度设备返回的所述用户群组的背景流量下载策略;
    所述策略与计费制定设备根据所述背景流量下载策略,确定背景流量下载的策略与计费控制。
  7. 根据权利要求6所述的方法,其特征在于,若所述背景流量下载启用请求中还包括所述用户群组中需要下载背景流量的各用户终端的IP地址,则所述策略与计费制定设备根据所述背景流量下载策略,确定背景流量下载的策略与计费控制包括:
    所述策略与计费制定设备根据所述背景流量下载策略、所述用户群组中需要下载背景流量的各用户终端的IP地址,为所述用户群 组中需要下载背景流量的各用户终端确定专用承载建立时刻和最大下载速率。
  8. 根据权利要求6或7所述的方法,其特征在于,所述方法还包括:
    所述策略与计费制定设备将所述策略与计费控制发送给策略与计费执行设备,以便所述策略与计费执行设备根据所述策略与计费控制为背景流量下载分配承载资源。
  9. 一种背景流量下载方法,其特征在于,所述方法包括:
    应用服务器向网络感知调度设备发送背景流量下载请求消息,所述背景流量下载请求消息携带对用户群组进行背景流量下载所需的需求信息;
    所述应用服务器接收所述网络感知调度设备发送的所述用户群组的背景流量下载策略的标识;
    所述应用服务器向策略与计费制定设备发送背景流量下载启用请求,所述背景流量下载启用请求中携带所述背景流量下载策略的标识,以便所述策略与计费制定设备根据所述背景流量下载启用请求获取所述用户群组的背景流量下载策略,确定背景流量下载的策略与计费控制。
  10. 根据权利要求9所述的方法,其特征在于,所述需求信息包括以下信息中的至少一项:所述用户群组进行背景流量下载所需的流量值、所述用户群组进行背景流量下载所需的时间窗、所述用户群组的区域信息。
  11. 根据权利要求9或10所述的方法,其特征在于,所述应用服务器向网络感知调度设备发送背景流量下载请求消息之前,所述方法还包括:
    所述应用服务器获取所述需求信息。
  12. 根据权利要求9-11任一项所述的方法,其特征在于,所述应用服务器接收所述网络感知调度设备发送的所述背景流量下载策略的标识之后,所述方法还包括:
    所述应用服务器获取所述用户群组中需要下载背景流量的各用户终端的IP地址;
    则,所述背景流量下载启用请求还包括所述用户群组中需要下载背景流量的各用户终端的IP地址。
  13. 一种网络感知与调度设备,其特征在于,包括:
    接收单元,用于接收应用服务器发送的背景流量下载请求消息,所述背景流量下载请求消息携带对用户群组进行背景流量下载所需的需求信息;
    生成单元,用于根据所述需求信息生成所述用户群组的背景流量下载策略和所述背景流量下载策略的标识;
    发送单元,用于向所述应用服务器发送所述背景流量下载策略的标识;
    所述接收单元还用于,接收策略与计费制定设备发送的所述背景流量下载策略的标识;
    确定单元,用于根据所述背景流量下载策略的标识确定所述用户群组的所述背景流量下载策略;
    所述发送单元还用于,将所述背景流量下载策略发送给所述策略与计费制定设备,以便所述策略与计费制定设备根据所述背景流量下载策略确定背景流量下载的策略与计费控制。
  14. 根据权利要求13所述的网络感知与调度设备,其特征在于,所述需求信息包括以下信息中的至少一项:所述用户群组进行背景流量下载所需的流量值、所述用户群组进行背景流量下载所需的时间窗、所述用户群组的区域信息。
  15. 根据权利要求13或14所述的网络感知与调度设备,其特征在于,所述背景流量下载策略包括以下信息中的至少一项:
    允许的下载时间窗、单个用户终端的计费信息、单个用户终端的最大下载速率、所述用户群组的汇聚下载速率的最大值、不同汇聚下载速率下的计费策略。
  16. 根据权利要求15所述的网络感知与调度设备,其特征在于,
    若所述需求信息包括所述用户群组进行背景流量下载所需的时间窗,则所述背景流量下载策略包括所述允许的下载时间窗;其中,所述用户群组进行背景流量下载所需的时间窗包含所述允许的下载时间窗;
    或者,若所述需求信息包括所述用户群组进行背景流量下载所需的流量值,则所述背景流量下载策略包括所述用户群组的汇聚下载速率的最大值或所述用户群组中单个用户终端的最大下载速率;其中,所述用户群组的汇聚下载速率的最大值或所述用户群组中单个用户终端的最大下载速率由所述用户群组进行背景流量下载所需的流量值确定。
  17. 根据权利要求13或14所述的网络感知与调度设备,其特征在于,
    所述确定单元还用于,当所述需求信息包括所述用户群组进行背景流量下载所需的时间窗时,在所述生成单元根据所述需求信息生成所述用户群组的背景流量下载策略和所述背景流量下载策略的标识之前,确定在所述用户群组进行背景流量下载所需的时间窗内网络能够满足所述应用服务器的背景流量下载请求。
  18. 一种策略与计费制定设备,其特征在于,包括:
    接收单元,用于接收应用服务器发送的背景流量下载启用请求,所述背景流量下载启用请求携带用户群组的背景流量下载策略的标识;
    发送单元,用于将所述背景流量下载策略的标识发送至网络感知调度设备;
    所述接收单元还用于,接收所述网络感知调度设备返回的所述用户群组的背景流量下载策略;
    生成单元,用于根据所述背景流量下载策略,确定背景流量下载的策略与计费控制。
  19. 根据权利要求18所述的策略与计费制定设备,其特征在于,
    所述生成单元具体用于,当所述背景流量下载启用请求中还包 括所述用户群组中需要下载背景流量的各用户终端的IP地址时,根据所述背景流量下载策略、所述用户群组中需要下载背景流量的各用户终端的IP地址,为所述用户群组中需要下载背景流量的各用户终端确定专用承载建立时刻和最大下载速率。
  20. 根据权利要求18或19所述的策略与计费制定设备,其特征在于,
    所述发送单元还用于,将所述策略与计费控制发送给策略与计费执行设备,以便所述策略与计费执行设备根据所述策略与计费控制为背景流量下载分配承载资源。
  21. 一种应用服务器,其特征在于,包括:
    发送单元,用于向网络感知调度设备发送背景流量下载请求消息,所述背景流量下载请求消息携带对用户群组进行背景流量下载所需的需求信息;
    接收单元,用于接收所述网络感知调度设备发送的所述用户群组的背景流量下载策略的标识;
    所述发送单元还用于,向策略与计费制定设备发送背景流量下载启用请求,所述背景流量下载启用请求中携带所述背景流量下载策略的标识,以便所述策略与计费制定设备根据所述背景流量下载启用请求获取所述用户群组的背景流量下载策略,确定背景流量下载的策略与计费控制。
  22. 根据权利要求21所述的应用服务器,其特征在于,所述需求信息包括以下信息中的至少一项:所述用户群组进行背景流量下载所需的流量值、所述用户群组进行背景流量下载所需的时间窗、所述用户群组的区域信息。
  23. 根据权利要求21或22所述的应用服务器,其特征在于,还包括获取单元,
    所述获取单元用于,在所述发送单元向网络感知调度设备发送背景流量下载请求消息之前,获取所述需求信息。
  24. 根据权利要求21-23任一项所述的应用服务器,其特征在 于,
    所述获取单元还用于,在所述接收单元接收所述网络感知调度设备发送的所述背景流量下载策略的标识之后,获取所述用户群组中需要下载背景流量的各用户终端的IP地址;
    则,所述背景流量下载启用请求还包括所述用户群组中需要下载背景流量的各用户终端的IP地址。
  25. 一种系统,其特征在于,包括:网络感知调度设备、策略与计费制定设备以及应用服务器,
    所述网络感知调度设备为上述权利要求13~17任一项所述的网络感知调度设备;
    所述策略与计费制定设备为上述权利要求18~20任一项所述的策略与计费制定设备;
    所述应用服务器为上述权利要求21~24任一项所述的应用服务器。
PCT/CN2014/088156 2014-10-08 2014-10-08 一种背景流量下载方法、设备及系统 WO2016054777A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/CN2014/088156 WO2016054777A1 (zh) 2014-10-08 2014-10-08 一种背景流量下载方法、设备及系统
CN201480081842.2A CN106688256B (zh) 2014-10-08 2014-10-08 一种背景流量下载方法、设备及系统
US15/482,532 US10211995B2 (en) 2014-10-08 2017-04-07 Background traffic downloading method, device, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/088156 WO2016054777A1 (zh) 2014-10-08 2014-10-08 一种背景流量下载方法、设备及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/482,532 Continuation US10211995B2 (en) 2014-10-08 2017-04-07 Background traffic downloading method, device, and system

Publications (1)

Publication Number Publication Date
WO2016054777A1 true WO2016054777A1 (zh) 2016-04-14

Family

ID=55652466

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/088156 WO2016054777A1 (zh) 2014-10-08 2014-10-08 一种背景流量下载方法、设备及系统

Country Status (3)

Country Link
US (1) US10211995B2 (zh)
CN (1) CN106688256B (zh)
WO (1) WO2016054777A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021204299A1 (zh) * 2020-04-10 2021-10-14 华为技术有限公司 一种确定策略的方法、装置及系统

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016103053A1 (en) * 2014-12-24 2016-06-30 Orange A method and system for dynamically allocating operator specific billing rules for date exchange by an application on a user equipment
US10284999B2 (en) * 2017-05-10 2019-05-07 Qualcomm Incorporated Mobile device position determination using compatible dedicated-frequency nodes and non-dedicated-frequency nodes
CN110519795B (zh) * 2018-05-21 2021-12-10 华为技术有限公司 一种确定背景流量传输策略的方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1708434A1 (de) * 2005-03-30 2006-10-04 Vodafone Holding GmbH Verfahren und System zur Durchsetzung geeigneter Richtlinien für Datenverkehr in einem Funkkommunikationssystem
CN101119211A (zh) * 2007-09-18 2008-02-06 中兴通讯股份有限公司 一种公平用户策略的业务实现方法
CN101345633A (zh) * 2007-07-10 2009-01-14 华为技术有限公司 一种应用的策略控制方法及装置
CN101945368A (zh) * 2009-07-06 2011-01-12 华为技术有限公司 群组计费方法、计费处理装置以及通信系统
CN102014343A (zh) * 2009-09-04 2011-04-13 华为技术有限公司 群组策略与计费规则处理方法、装置以及通信系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050002375A1 (en) * 2003-05-07 2005-01-06 Gokhale Dilip Shyamsundar Advanced TDMA resource management architecture
US7607164B2 (en) * 2004-12-23 2009-10-20 Microsoft Corporation Systems and processes for managing policy change in a distributed enterprise
US20120042076A1 (en) * 2010-08-16 2012-02-16 Nokia Corporation Method and apparatus for managing application resources via policy rules
GB201020991D0 (en) * 2010-12-10 2011-01-26 Vodafone Ip Licensing Ltd Smart device based download/caching
US9148522B2 (en) * 2013-09-27 2015-09-29 Oracle International Corporation Methods, systems, and computer readable media for determining policy information associated with an emergency call

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1708434A1 (de) * 2005-03-30 2006-10-04 Vodafone Holding GmbH Verfahren und System zur Durchsetzung geeigneter Richtlinien für Datenverkehr in einem Funkkommunikationssystem
CN101345633A (zh) * 2007-07-10 2009-01-14 华为技术有限公司 一种应用的策略控制方法及装置
CN101119211A (zh) * 2007-09-18 2008-02-06 中兴通讯股份有限公司 一种公平用户策略的业务实现方法
CN101945368A (zh) * 2009-07-06 2011-01-12 华为技术有限公司 群组计费方法、计费处理装置以及通信系统
CN102014343A (zh) * 2009-09-04 2011-04-13 华为技术有限公司 群组策略与计费规则处理方法、装置以及通信系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021204299A1 (zh) * 2020-04-10 2021-10-14 华为技术有限公司 一种确定策略的方法、装置及系统

Also Published As

Publication number Publication date
CN106688256B (zh) 2019-10-25
CN106688256A (zh) 2017-05-17
US10211995B2 (en) 2019-02-19
US20170214536A1 (en) 2017-07-27

Similar Documents

Publication Publication Date Title
US11330069B2 (en) Service subscription method and system for reporting service change in communication system
US11711471B2 (en) Methods of and devices for implementing and executing policy rules on a per application basis in a telecommunications system
KR20180070710A (ko) 서비스 계층 사우스바운드 인터페이스 및 서비스 품질
US20210153020A1 (en) Service data transmission method and device
JP2016529579A5 (zh)
JP2016525819A5 (zh)
WO2013117126A1 (zh) 业务速率控制方法和系统以及设备
WO2016054777A1 (zh) 一种背景流量下载方法、设备及系统
EP3162138A1 (en) Guaranteed download time
US20180084565A1 (en) Bearer setup method and apparatus
WO2012109823A1 (zh) 一种机器类型通信设备的拥塞控制方法及系统
KR20120012162A (ko) 이동통신 시스템에서 에이지피에스 트래픽 클래스를 지원하는 장치 및 방법
WO2018095341A1 (zh) 一种执行传输策略的方法、装置和计算机可读存储介质
WO2016049866A1 (zh) 一种背景流量下载方法、设备及系统
US11923994B2 (en) Method and packet core system for common charging of network connectivity and cloud resource utilization
US10548050B2 (en) Service level agreement in radio base station
US10212722B2 (en) Volume-deadline scheduling
JP2024503095A (ja) アプリケーション関連機能のためのリソース割り当てステータスサブスクリプション
WO2015054823A1 (zh) 群组接入无线网络的控制方法及相关装置
EP4205367A1 (en) Methods and apparatuses for providing quality of service handling of user traffic transmitted by a content provider
JP2015156568A (ja) 帯域予約装置、帯域予約方法および帯域予約プログラム
JP2019134477A (ja) 情報処理装置及び情報処理方法
JP2017123617A (ja) 情報処理装置、情報処理方法、およびプログラム

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14903662

Country of ref document: EP

Kind code of ref document: A1