WO2016169457A1 - 用量信息确定方法、发送方法、接收方法及装置 - Google Patents

用量信息确定方法、发送方法、接收方法及装置 Download PDF

Info

Publication number
WO2016169457A1
WO2016169457A1 PCT/CN2016/079585 CN2016079585W WO2016169457A1 WO 2016169457 A1 WO2016169457 A1 WO 2016169457A1 CN 2016079585 W CN2016079585 W CN 2016079585W WO 2016169457 A1 WO2016169457 A1 WO 2016169457A1
Authority
WO
WIPO (PCT)
Prior art keywords
usage information
party application
usage
pcef
pcrf
Prior art date
Application number
PCT/CN2016/079585
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 中兴通讯股份有限公司
Publication of WO2016169457A1 publication Critical patent/WO2016169457A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing

Definitions

  • the present invention relates to the field of communications, and in particular, to a usage information determining method, a transmitting method, a receiving method, and a device.
  • the Policy and Charging Control (PCC) architecture of the 3rd Generation Partnership Project (3GPP) is a functional framework that can be applied to multiple access technologies.
  • UTRAN Universal Mobile Telecommunications System
  • UMT Universal Mobile Telecommunications System
  • GSM Global System for Mobile Communication
  • EDGE Enhanced Data Rates for Global Evolution
  • I-WLAN interworking wireless local area network
  • EPS Evolved Packet System
  • FIG. 1 is a schematic diagram 1 of a related art Rel-8 PCC non-roaming architecture. The following describes the logical function entities and their interface functions in the PCC architecture with reference to FIG. 1 :
  • AF Application Function Entity
  • PCRF Policy and Charging Rules Function
  • the PCRF is the core of the PCC and is responsible for policy decision making and billing rules.
  • the PCRF provides network control rules based on service data flows, including traffic data flow monitoring, Gating Control, Quality of Service (QoS) control, and data flow based charging rules. .
  • the PCRF sends its policy and charging rules to the Policy and Charging Enforcement Function (PCEF).
  • PCEF Policy and Charging Enforcement Function
  • the PCRF also needs to ensure that these rules are consistent with the user's subscription information.
  • the basis for formulating the policy and charging rules by the PCRF includes: obtaining information related to the service from the AF; obtaining the subscription information of the user policy charging control from the Subscription Profile Repository (SPR); and acquiring the network related to the bearer from the PCEF. information.
  • the PCEF is used to perform the policy and charging rules formulated by the PCRF on the bearer plane.
  • the PCEF monitors the service data flow according to the service data flow filter in the rule sent by the PCRF, and then executes the policy and charging rules formulated by the PCRF for these service data flows.
  • the PCEF performs QoS authorization according to the rules sent by the PCRF, and performs gate control according to the execution of the AF.
  • the charging rule sent by the PCRF the PCEF performs a corresponding service data flow charging operation, and the charging can be either online charging or offline charging. If it is online charging, the PCEF needs to perform credit management together with the Online Charging System (OCS).
  • OCS Online Charging System
  • the interface between the PCEF and the PCRF is a Gx interface
  • the interface between the OCE and the OCS is a Gy interface
  • the interface between the OFCS and the OFCS is a Gz interface.
  • the PCEF is usually located in a Gateway (Gate-Way, GW for short), such as a GPRS Gateway Support Node (GGSN) in GPRS and a Packet Data Gateway (PDG) in I-WLAN.
  • GGSN GPRS Gateway Support Node
  • PGW Packet Data Gateway
  • Bearer Binding and Event Reporting Function whose functions include bearer binding, verification of uplink bearer binding, and event reporting.
  • BBERF Bearer Binding and Event Reporting Function
  • the BBERF is located at the S-GW, and when the UE accesses through the trusted non-3GPP access system, the BBERF is located in the trusted non- The 3GPP access gateway, when the UE accesses through the untrusted non-3GPP access system, the BBERF is located in the Evolved Packet Data Gateway (ePDG). At this time, the PCEF no longer performs the bearer binding function.
  • ePDG Evolved Packet Data Gateway
  • the User Contracted Database stores user policy charging control subscription information related to policy control and charging.
  • the interface between SPR and PCRF is the Sp interface.
  • the online charging system together with the PCEF, controls and manages user credits in the online charging mode.
  • the offline charging system (OFCS), together with the PCEF, performs the charging operation in the offline charging mode.
  • IP-CAN IP Connectivity Access Network
  • PDN Packet Data Network
  • the third-party data application provider can change the chargeable party of the session service during the session initiation or session, that is, the user accessing the service is charged or the third-party service provider is charged.
  • the call gap process may be poor.
  • a certain billing error For a single user single visit, this billing error will be relatively small, but considering that there will be a large number of users accessing a third-party data application, the operator will have a very large cumulative error when paying for third-party applications. Given that the rate offered by the network will be faster and faster, this error will be very alarming.
  • the existence of the PC/AAC architecture due to the emergence of new network elements, it is bound to increase the delay of message delivery. Therefore, there is a problem of charging error in the related art.
  • the invention provides a usage information determining method, a transmitting method, a receiving method and a device, so as to at least solve the problem of charging error existing in the related art.
  • a method for determining usage information is provided, which is characterized in that: the policy and charging execution function entity PCEF sends the first usage information before the change of the chargeable entity to the server of the third-party application.
  • the first usage information is usage information of the third-party application accessed by the user equipment UE before the change of the billable entity, and the first usage information is used by the server of the third-party application to determine the second usage information,
  • the second usage information is usage information used by the provider of the third-party application for the UE to access the third-party application.
  • the first usage information includes information about traffic and/or duration of the UE accessing the third-party application before the changeable billable subject;
  • the second usage information includes a provider of the third-party application.
  • the second usage information is the third usage information minus the first usage information
  • the third usage information is the third-party application.
  • the server counts the total usage of the third-party application before and after the change of the chargeable entity; if the chargeable entity before the change is the provider of the third-party application, the second The usage information is the first usage information.
  • the PCEF sends the first usage information before the changeable billable entity to the third Before the server is applied, the method further includes: the PCEF determining a usage measurement method for measuring the first usage information, wherein the PCEF and the server of the third-party application adopt the same usage measurement method; The first usage information is measured according to the determined dosage measurement method.
  • the PCEF determines that the usage measurement method for measuring the first usage information comprises: the PCEF receiving policy and the charging control PCC rule sent by the PCF receiving policy and charging rule function, wherein the PCC rule The indication information of the usage measurement method is carried in, and the PCRF determines a usage measurement method that is the same as the server of the third-party application according to the provider of the third-party application.
  • the server of the third-party application provides the PCRF with the indication information of the usage measurement method adopted by the server of the third-party application, and the PCRF is instructed according to the usage measurement method provided by the server of the third-party application.
  • the information determines the metering method used by the PCEF.
  • the PCEF determines the first usage information by using the PCEF statistics according to the determined usage measurement method;
  • the PCEF determines the first usage information by interacting with the online charging system OCS according to the determined usage measurement method; the PCEF passes the PCEF and the offline charging system according to the determined usage measurement method.
  • the manner in which the OFCS interacts determines the first usage information.
  • the server that sends the first usage information to the third-party application includes at least one of the following: the PCEF sends the first usage information to a policy and charging rule function PCRF, where The PCRF sends the first usage information to the application function AF, and the AF reports the first usage information to the server of the third-party application; the PCEF sends the first usage information to the policy and the meter The fee-based function PCRF, the PCRF sends the first usage information to the application function AF through the protocol converter PC, the application access control AAC, or the service capability development function SCEF, and the AF reports the first usage information to the The server of the third party application.
  • the PCEF sends the first usage information to a policy and charging rule function PCRF, where The PCRF sends the first usage information to the application function AF, and the AF reports the first usage information to the server of the third-party application.
  • a method for transmitting usage information including: the policy and charging execution function entity PCEF transmitting, to the application function AF, the first usage information before the change of the chargeable entity is performed, wherein the The first usage information is usage information of the user equipment UE accessing the third-party application before the changeable billable subject changes.
  • the first usage information includes time and/or traffic for accessing the third-party application.
  • the sending, by the PCEF, the first usage information to the AF includes at least one of the following: the PCEF sends the first usage information to a policy and charging rule function PCRF, where the PCRF The first usage information is sent to the AF; the PCEF sends the first usage information to a policy and charging rule function PCRF, and the PCRF passes a protocol converter PC, an application access control AAC, or a service capability development function.
  • the SCEF sends the first usage information to the AF.
  • a method for determining usage information including: a service of a third party application Receiving, by the server, the first usage information sent by the policy and the accounting execution function entity PCEF, wherein the first usage information is usage information of the third-party application accessed by the user equipment UE before the changeable billable subject; the third party The server of the application determines the second usage information according to the first usage information, where the second usage information is used by the provider of the third-party application for the UE to access the third-party application. Usage information.
  • the first usage information includes information about traffic and/or duration when the UE accesses the third-party application before the change of the billable entity; the second usage information includes the provision of the third-party application. Information for the UE to pay for the traffic and/or duration of the UE accessing the third-party application.
  • the determining, by the server of the third-party application, the second usage information according to the first usage information includes: if the applicable billable entity before the change is the UE, the server of the third-party application passes the third usage And subtracting the first usage information from the information to obtain the second usage information, where the third usage information is the server statistics of the third-party application, and the UE accesses before and after the change of the chargeable entity.
  • the total usage of the third-party application if the chargeable entity before the change is the provider of the third-party application, the server of the third-party application determines the first usage information as the second usage information.
  • the method further includes: determining, by the server of the third-party application, the usage measurement for measuring the third usage information
  • the server of the third-party application measures the third usage information according to the determined usage measurement method.
  • the server of the third-party application determines that the usage measurement method for measuring the third usage information comprises: determining, by the server of the third-party application, a contracting agreement with an operator of the third-party application
  • the usage measurement method is determined by the server of the third-party application by dynamically negotiating with the operator of the third-party application.
  • a usage information receiving method comprising: applying a first usage information before a change of a billable entity sent by a function AF receiving policy and a charging execution function entity PCEF, wherein The first usage information is usage information of the user equipment UE accessing the third-party application before the changeable billable subject changes.
  • the first usage information includes time and/or traffic for accessing the third-party application.
  • the receiving, by the AF, the first usage information sent by the PCEF includes: the AF passing policy and charging rule function PCRF receiving the first usage information sent by the PCEF.
  • a method for transmitting usage information including: a policy and charging rule function entity PCRF, after receiving a first indication sent by an application function AF for indicating change of a billable subject, to a policy And sending, by the charging execution function entity PCEF, a second indication for indicating that the PCEF reports the fourth usage information before the change of the billable entity, wherein the fourth usage information includes the changeable billable subject before The PCEF has not accessed the accumulated usage information of the third-party application to the user equipment UE reported by the PCRF; after receiving the fourth usage information, the PCRF sends the fifth usage information to the AF, where The fifth usage information includes cumulative usage information of the UE accessing the third-party application before the changeable billable subject changes.
  • the value of the fifth usage information is the value of the fourth usage information, or the value of the fifth usage information is the fourth usage information and the previously reported information of the PCEF.
  • the fourth usage information includes information about the traffic and/or duration of the UE accessing the third-party application.
  • the PCRF further includes: the PCRF indicating that the PCEF is deactivated for monitoring the fourth usage.
  • the monitoring key of the information is the Monitoring Key.
  • the PCRF instructing the PCEF to deactivate the first monitoring key for monitoring the fourth usage information includes: sending, by the PCRF, the PCEF to deactivate the first monitoring key Instructing or replacing the indication of the first Monitoring Key with a second Monitoring key.
  • a usage information determining apparatus the apparatus being applied to a policy and charging execution function entity PCEF, comprising: a first sending module, configured to change a billable subject before The first usage information is sent to the server of the third-party application, where the first usage information is the usage information of the user equipment UE accessing the third-party application before the changeable billable entity is changed, and the first usage information is used for the The server of the third-party application determines the second usage information, where the second usage information is the usage information used by the provider of the third-party application for the UE to access the third-party application.
  • the first usage information includes information about traffic and/or duration of the UE accessing the third-party application before the changeable billable subject;
  • the second usage information includes a provider of the third-party application.
  • the second usage information is the third usage information minus the first usage information
  • the third usage information is the third-party application.
  • the server counts the total usage of the third-party application before and after the change of the chargeable entity; if the chargeable entity before the change is the provider of the third-party application, the second The usage information is the first usage information.
  • the device further includes: a first determining module, configured to determine a usage measurement method for measuring the first usage information, wherein the PCEF and the server of the third-party application use the same usage measurement
  • the first metering module is configured to measure the first amount information according to the determined metering method.
  • the first determining module includes: a first receiving unit, configured to receive a policy and a charging rule function The policy and the charging control PCC rule that can be sent by the PCRF, wherein the PCC rule carries the indication information of the usage measurement method, and the PCRF determines the server with the third-party application according to the provider of the third-party application. The same amount measurement method.
  • the server of the third-party application provides the PCRF with the indication information of the usage measurement method adopted by the server of the third-party application, and the PCRF is instructed according to the usage measurement method provided by the server of the third-party application.
  • the information determines the metering method used by the PCEF.
  • the first metering module includes at least one of the following: the PCEF determines the first usage information by using the PCEF statistics according to the determined usage measurement method; and the PCEF is determined according to the determined usage measurement method. Determining, by the PCEF, the first usage information in a manner of interacting with an online charging system OCS; the PCEF determining the first manner by interacting with the offline charging system OFCS according to the determined usage measurement method Usage information.
  • the first sending module includes at least one of the following: a first sending unit, configured to send the first usage information to a policy and charging rule function PCRF, where the PCRF uses the first usage information Sending to the application function AF, the AF reports the first usage information to the server of the third-party application; the second sending unit is configured to send the first usage information to the policy and charging rule function PCRF,
  • the PCRF sends the first usage information to the application function AF through the protocol converter PC, the application access control AAC, or the service capability development function SCEF, and the AF reports the first usage information to the third-party application. Server.
  • a usage information transmitting apparatus the apparatus being applied to a policy and charging execution function entity PCEF, comprising: a second sending module, configured to change a billable entity before The first usage information is sent to the application function AF, where the first usage information is usage information of the user equipment UE accessing the third-party application before the changeable billable subject changes.
  • the first usage information includes time and/or traffic for accessing the third-party application.
  • the second sending module includes at least one of the following: a third sending unit, configured to send the first usage information to a policy and charging rule function PCRF, where the PCRF uses the first usage information Sending to the AF; the fourth sending unit is configured to send the first usage information to a policy and charging rule function PCRF, where the PCRF passes the protocol converter PC, the application access control AAC, or the service capability development function SCEF Sending the first usage information to the AF.
  • a third sending unit configured to send the first usage information to a policy and charging rule function PCRF, where the PCRF uses the first usage information Sending to the AF
  • the fourth sending unit is configured to send the first usage information to a policy and charging rule function PCRF, where the PCRF passes the protocol converter PC, the application access control AAC, or the service capability development function SCEF Sending the first usage information to the AF.
  • a usage information determining apparatus configured to apply to a server of a third-party application, comprising: a first receiving module, configured to receive a policy and a charging execution function entity PCEF a usage information, wherein the first usage information is usage information of the user equipment UE accessing the third party application before the changeable billable subject is changed; and the second determining module is configured to determine according to the first usage information The second usage information, where the second usage information is usage information used by the provider of the third-party application for the UE to access the third-party application.
  • the first usage information includes information about traffic and/or duration of the UE accessing the third-party application before the changeable billable subject;
  • the second usage information includes a provider of the third-party application.
  • the second determining module includes: if the billable entity before the change is the UE, the server of the third-party application obtains the first by subtracting the first usage information from the third usage information The second usage information, wherein the third usage information is a total usage of the third-party application before and after the change of the chargeable entity by the server of the third-party application; if the change is before the change
  • the charging entity is a provider of the third-party application, and the server of the third-party application determines the first usage information as the second usage information.
  • the device further includes: a third determining module, configured to determine a usage measurement method for measuring the third usage information; and a second measurement module configured to measure the third according to the determined usage measurement method Usage information.
  • a third determining module configured to determine a usage measurement method for measuring the third usage information
  • a second measurement module configured to measure the third according to the determined usage measurement method Usage information.
  • the third determining module includes at least one of the following: a first determining unit, configured to determine the usage metering method by means of an agreement with an operator of the third-party application; and second determining unit, setting The usage measurement method is determined in a manner of dynamic negotiation with an operator of the third-party application.
  • a usage information receiving device the device being applied to an application function AF, comprising: a second receiving module, configured to receive a billable policy and a billing execution function entity PCEF The first usage information before the main body changes, wherein the first usage information is usage information of the user equipment UE accessing the third-party application before the changeable billable subject changes.
  • the first usage information includes time and/or traffic for accessing the third-party application.
  • the second receiving module includes: a second receiving unit, configured to receive the first usage information sent by the PCEF by using a policy and charging rule function PCRF.
  • a usage information sending apparatus which is applied to a policy and charging rule function entity PCRF, and includes: a third sending module, configured to send a change in the receiving application function AF for indicating a change. And transmitting, by the policy and charging execution function entity PCEF, a second indication for instructing the PCEF to report the fourth usage information before the change of the chargeable entity, where the fourth usage is
  • the information includes the accumulated usage information of the user equipment UE that has not been reported to the PCRF by the PCEF before the change of the billable subject, and the fourth sending module is configured to: after receiving the fourth usage information, The AF sends the fifth usage information, where the fifth usage information includes the accumulated usage information of the UE accessing the third-party application before the changeable billable subject changes.
  • the value of the fifth usage information is the value of the fourth usage information, or the fifth usage information is the fourth usage information and the UE access previously reported by the PCEF.
  • the fourth usage information includes information about the traffic and/or duration of the UE accessing the third-party application.
  • the apparatus further includes an indication module, configured to be applied to the PCRF, configured to instruct the PCEF to deactivate after receiving the first indication sent by the AF to indicate that the changeable billable subject is changed A monitoring key Monitoring Key for monitoring the fourth usage information.
  • an indication module configured to be applied to the PCRF, configured to instruct the PCEF to deactivate after receiving the first indication sent by the AF to indicate that the changeable billable subject is changed A monitoring key Monitoring Key for monitoring the fourth usage information.
  • the indication module includes: an indicating unit, configured to send a deactivation to the PCEF An indication of the first Monitoring Key or an indication of replacing the first Monitoring Key with a second Monitoring key.
  • Another embodiment of the present invention provides a computer storage medium storing execution instructions for performing the method in the above embodiments.
  • the first usage information before the change of the billable entity is sent to the server of the third-party application by using the policy and charging execution function entity PCEF, wherein the first usage information is the user before the changeable billable entity
  • the device UE accesses the usage information of the third-party application, where the first usage information is used by the server of the third-party application to determine the second usage information, where the second usage information is the provider of the third-party application.
  • the usage information of the UE for accessing the third-party application by the UE solves the problem of charging error existing in the related art, thereby achieving the effect of reducing the charging error.
  • FIG. 1 is a schematic diagram 1 of a related art Rel-8 PCC non-roaming architecture
  • FIG. 2 is a schematic diagram 2 of a Rel-8 PCC non-roaming architecture in the related art
  • FIG. 3 is a flow chart of a first method for determining usage information according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of a method for transmitting usage information according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a second method for determining usage information according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of a method for receiving usage information according to an embodiment of the present invention.
  • FIG. 7 is a structural block diagram of a first usage information determining apparatus according to an embodiment of the present invention.
  • FIG. 8 is a block diagram showing a preferred structure of a first usage information determining apparatus according to an embodiment of the present invention.
  • FIG. 9 is a structural block diagram of a first determining module 82 in the first usage information determining apparatus according to an embodiment of the present invention.
  • FIG. 10 is a structural block diagram of a first transmitting module 72 in a first usage information determining apparatus according to an embodiment of the present invention.
  • FIG. 11 is a block diagram showing the structure of a usage information transmitting apparatus according to an embodiment of the present invention.
  • FIG. 12 is a structural block diagram of a second sending module 112 in a usage information transmitting apparatus according to an embodiment of the present invention.
  • FIG. 13 is a structural block diagram of a second usage information determining apparatus according to an embodiment of the present invention.
  • FIG. 14 is a block diagram showing a preferred structure of a second usage information determining apparatus according to an embodiment of the present invention.
  • FIG. 15 is a structural block diagram of a third determining module 142 in a second usage information determining apparatus according to an embodiment of the present invention.
  • Figure 16 is a block diagram showing the structure of a usage information receiving apparatus according to an embodiment of the present invention.
  • FIG. 17 is a structural block diagram of a second receiving module 162 in the usage information determining apparatus according to an embodiment of the present invention.
  • Figure 23 is a flow chart of the usage report according to the sixth embodiment of the present invention.
  • FIG. 3 is a flowchart of a method for determining usage information according to an embodiment of the present invention. As shown in FIG. 3, the process includes the following steps:
  • step S302 the policy and charging execution function entity PCEF sends the first usage information before the change of the billable entity to the server of the third-party application, where the first usage information is accessed by the user equipment UE before the changeable billable entity changes.
  • the usage information of the third-party application where the first usage information is used by the server of the third-party application to determine the second usage information, where the second usage information is used by the provider of the third-party application for the UE to access the third-party application. information.
  • the foregoing billable entity may be a user equipment UE or a provider of a third party application, and the change of the billable subject may enable switching between the two.
  • the chargeable entity when the chargeable entity is changed, the first usage information before the changeable billable entity is changed is sent to the server of the third-party application, so that the third-party server can accurately measure the provider of the third-party application.
  • the usage information paid by the user equipment UE should be used to improve the charging accuracy, thereby solving the problem of the charging error existing in the related art, thereby achieving the effect of reducing the charging error.
  • the foregoing first usage information includes information about traffic and/or duration of the UE accessing the third-party application before the changeable billing entity changes; and the second usage information includes the third-party application provider paying for the UE. Information for the UE's access to traffic and/or duration of third-party applications.
  • the second usage information is the third usage information minus the first usage information, where the third usage information is the server of the third-party application, and the UE is in the chargeable entity.
  • the total usage of the third-party application is accessed before and after the change; if the chargeable entity before the change is the provider of the third-party application, the second usage information is the first usage information.
  • the method before the PCEF sends the first usage information before the changeable billable entity to the server of the third-party application, the method further includes: determining, by the PCEF, the usage measurement method for measuring the first usage information.
  • the PCEF and the server of the third-party application adopt the same usage measurement method; the PCEF measures the first usage information according to the determined usage measurement method.
  • the method for measuring the usage of the first usage information by the PCEF includes: a policy and a charging control PCC rule sent by the PCEF receiving policy and charging rule function PCRF, wherein the PCC rule carries an indication of the usage measurement method.
  • the PCRF determines the same metering method as the server of the third party application based on the provider of the third party application.
  • the server of the third-party application provides the PCRF with the indication information of the usage measurement method used by the server of the third-party application, and the PCRF determines the usage measurement method used by the PCEF according to the indication information of the usage measurement method provided by the server of the third-party application.
  • the PCEF measures the first usage information according to the determined usage measurement method.
  • there may be multiple determination methods which may include at least one of the following: the PCEF determines the first usage information by means of PCEF statistics according to the determined usage measurement method; the PCEF passes the PCEF and the online charging system according to the determined usage measurement method.
  • the method for interacting with the OCS determines the first usage information; the PCEF determines the first usage information by interacting with the offline charging system OFCS according to the determined usage measurement method.
  • the foregoing PCEF sends the first usage information to the server of the third-party application, including at least one of the following: the PCEF sends the first usage information to the policy and charging rule function PCRF, and the PCRF
  • the usage information is sent to the AF, and the AF reports the first usage information to the server of the third-party application; the PCEF sends the first usage information to the policy and charging rule function PCRF, and the PCRF passes the protocol converter PC and the application access control.
  • the AAC or the service capability development function SCEF sends the first usage information to the AF, and the AF reports the first usage information to the server of the third-party application.
  • FIG. 4 is a flowchart of a method for transmitting usage information according to an embodiment of the present invention. As shown in FIG. 4, the method includes the following steps:
  • step S402 the policy and charging execution function entity PCEF sends the first usage information before the change of the billable entity to the application function AF, where the first usage information is the user equipment UE accessing the third party before the changeable billable subject changes. Usage usage information.
  • the PCEF sends the usage information of the UE before the change to the AF, so that the usage information of the third-party application accessed by the UE before the change of the billable entity can be clarified, thereby Billing has been paved the way to improve billing accuracy.
  • the problem of the charging error existing in the related art is solved, thereby achieving the effect of reducing the charging error.
  • the first usage information may include time and/or traffic for accessing the third party application.
  • the PCEF may send the first usage information to the AF, and may include at least one of the following: the PCEF sends the first usage information to the policy and charging rule function PCRF, and the PCRF sends the first usage information to the AF; the PCEF uses the first usage.
  • the information is sent to the policy and charging rule function PCRF, which sends the first usage information to the AF through the protocol converter PC, the application access control AAC or the service capability development function SCEF.
  • FIG. 5 is a flowchart of a second method for determining usage information according to an embodiment of the present invention. As shown in FIG. 5, the process includes the following steps:
  • Step S502 The server of the third-party application receives the first usage information sent by the policy and the charging execution function entity PCEF, where the first usage information is the usage information of the user equipment UE accessing the third-party application before the changeable billable subject changes;
  • step S504 the server of the third-party application determines the second usage information according to the first usage information, where the second usage information is the usage information used by the provider of the third-party application for the UE to access the third-party application.
  • the foregoing billable entity may be a user equipment UE or a provider of a third party application, and the change of the billable subject may enable switching between the two.
  • the chargeable entity when the chargeable entity is changed, the first usage information before the changeable billable entity is changed is sent to the server of the third-party application, so that the third-party server can accurately measure the provider of the third-party application.
  • the usage information paid by the user equipment UE should be used to improve the charging accuracy, thereby solving the problem of the charging error existing in the related art, thereby achieving the effect of reducing the charging error.
  • the foregoing first usage information includes information about traffic and/or duration of the UE accessing the third-party application before the changeable billable entity changes; and the second usage information includes the third-party application provider paying for the UE. Information for the traffic and/or duration of the UE accessing the third party application.
  • the server of the third-party application determines, according to the first usage information, the second usage information, that is, if the chargeable entity before the change is the UE, the third-party application server reduces the third usage information by Go to the first usage information to obtain the second usage information, where the third usage information is the total usage of the third-party application before and after the change of the chargeable entity by the server of the third-party application;
  • the charging entity is a provider of the third-party application, and the server of the third-party application determines the first usage information as the second usage information.
  • the method before the server of the third-party application determines the second usage information according to the first usage information, the method further includes: determining, by the server of the third-party application, a usage measurement method for measuring the third usage information; The server of the three-party application measures the third usage information according to the determined usage measurement method.
  • the method for measuring the usage of the third-party application by the server of the third-party application includes: the server of the third-party application determines the usage measurement method by means of a contract agreement with the operator of the third-party application; the server of the third-party application The usage measurement method is determined by dynamic negotiation with the operator of the third-party application.
  • FIG. 6 is a flowchart of a method for receiving usage information according to an embodiment of the present invention. As shown in FIG. 6, the process includes the following steps:
  • Step S602 the first usage information before the change of the billable entity sent by the application function AF receiving policy and the charging execution function entity PCEF, wherein the first usage information is the user equipment UE accessing the third party before the changeable billable subject changes Usage usage information.
  • the PCEF sends the usage information of the UE before the change to the AF, so that the usage information of the third-party application accessed by the UE before the change of the billable entity can be clarified, thereby Billing has been paved the way to improve billing accuracy.
  • the problem of the charging error existing in the related art is solved, thereby achieving the effect of reducing the charging error.
  • the first usage information includes time and/or traffic for accessing the third party application.
  • the first usage information sent by the AF receiving PCEF includes: the AF receiving the first usage information sent by the PCEF through the policy and charging rule function PCRF.
  • a method for sending usage information includes the following steps:
  • Step 1 After receiving the first indication sent by the application function AF to indicate that the changeable billable entity is sent, the policy and charging rule function entity PCRF sends a policy to the policy and charging execution function entity PCEF to indicate that the PCEF reports the billable a second indication of the fourth usage information before the change of the main body, where the fourth usage information includes the accumulated usage information of the user equipment UE that has not been reported by the PCEF to the PCRF before the change of the billable entity;
  • Step 2 After receiving the fourth usage information, the PCRF sends the fifth usage information to the AF, where the fifth usage information includes the accumulated usage information of the UE accessing the third-party application before the changeable billable subject changes.
  • the value of the fifth usage information is the value of the fourth usage information, or the value of the fifth usage information is the fourth usage information and the UE reported by the PCEF to access the third-party application. The sum of the cumulative usage information.
  • the fourth usage information includes information about the traffic and/or duration of the UE accessing the third-party application.
  • the PCRF further includes: the PCRF instructing the PCEF to deactivate the monitoring key Monitoring Key for monitoring the fourth usage information.
  • the PCRF indicating that the PCEF deactivates the first monitoring key for monitoring the fourth usage information includes: the PCRF sends an indication to the PCEF to deactivate the first monitoring key or The second Monitoring key replaces the indication of the first Monitoring Key.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • a storage medium such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods of various embodiments of the present invention.
  • a usage information determining device is further provided, which is used to implement the above-mentioned embodiments and preferred embodiments, and has not been described again.
  • the term “module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 7 is a structural block diagram of a first usage information determining apparatus according to an embodiment of the present invention.
  • the apparatus is applied to a policy and charging execution function entity PCEF.
  • the apparatus includes a first sending module 72, The device will be described.
  • the first sending module 72 is configured to send the first usage information before the changeable billable main body to the server of the third-party application, where the first usage information is the user equipment UE accessing the third-party application before the billable main body changes.
  • the usage information, the first usage information is used by the server of the third-party application to determine the second usage information, where the second usage information is the usage information that the third-party application provider pays for the user equipment UE for the UE to access the third-party application.
  • the first usage information includes information about traffic and/or duration of the UE accessing the third-party application before the change of the billable entity; and the second usage information includes the third-party application provider paying for the UE for the UE access. Information on the traffic and/or duration of the three-party application.
  • the second usage information is the third usage information minus the first usage information
  • the third usage information is the third-party application server statistics before the UE changes the chargeable entity and The total usage of the third-party application after the change; if the chargeable entity before the change is the provider of the third-party application, the second usage information is the first usage information.
  • FIG. 8 is a block diagram showing a preferred structure of a first usage information determining apparatus according to an embodiment of the present invention. As shown in FIG. 8, the apparatus includes a first determining module 82 and a first metering, in addition to the module shown in FIG. Module 84, the device will be described below.
  • the first determining module 82 is configured to determine a usage measurement method for measuring the first usage information, wherein the PCEF and the server of the third-party application adopt the same usage measurement method; the first measurement module 84 is connected to the first determination The module 82 and the first sending module 72 are configured to measure the first usage information according to the determined usage measurement method.
  • FIG. 9 is a structural block diagram of a first determining module 82 in the first usage information determining apparatus according to an embodiment of the present invention. As shown in FIG. 9, the first determining module 82 includes a first receiving unit 92, and the first determining module 82 is described below:
  • the first receiving unit 92 is configured to receive the policy and charging control PCC rule sent by the policy and charging rule function PCRF, where the PCC rule carries the indication information of the usage measurement method, and the PCRF determines according to the provider of the third-party application. The same usage measurement method for servers of third-party applications.
  • the server of the third-party application provides the PCRF with the indication information of the usage measurement method used by the server of the third-party application, and the PCRF determines the usage measurement method used by the PCEF according to the indication information of the usage measurement method provided by the server of the third-party application.
  • the first metering module 84 includes at least one of the following: the PCEF determines the first usage information by means of PCEF statistics according to the determined usage measurement method; and the PCEF passes the PCEF according to the determined usage measurement method.
  • the first usage information is determined in a manner of interacting with the online charging system OCS; the PCEF determines the first usage information by interacting with the offline charging system OFCS according to the determined usage measurement method.
  • FIG. 10 is a structural block diagram of a first sending module 72 in a first usage information determining apparatus according to an embodiment of the present invention.
  • the first sending module 72 includes a first sending unit 102 and/or a second sending. Unit 104, the first transmitting module 72 will be described below.
  • the first sending unit 102 is configured to send the first usage information to the policy and charging rule function PCRF, the PCRF sends the first usage information to the AF, and the AF reports the first usage information to the server of the third-party application;
  • the sending unit 104 is configured to send the first usage information to the policy and charging rule function PCRF, and the PCRF sends the first usage information to the AF through the protocol converter PC, the application access control AAC, or the service capability development function SCEF.
  • the AF reports the first usage information to the server of the third-party application.
  • FIG. 11 is a structural block diagram of a usage information sending apparatus according to an embodiment of the present invention.
  • the apparatus is applied to a policy and charging execution function entity PCEF.
  • the usage information sending apparatus includes a second sending module 112. The device will be described.
  • the second sending module 112 is configured to send the first usage information before the change of the billable entity to the application function AF, where the first usage information is the usage of the user equipment UE to access the third party application before the chargeable subject changes. information.
  • the first usage information includes time and/or traffic for accessing a third-party application.
  • FIG. 12 is a structural block diagram of a second sending module 112 in a usage information sending apparatus according to an embodiment of the present invention. As shown in FIG. 12, the second sending module 112 includes a third sending unit 122 and/or a fourth sending unit 124. The second transmitting module 112 will be described below.
  • the third sending unit 122 is configured to send the first usage information to the policy and charging rule function PCRF, the PCRF sends the first usage information to the AF, and the fourth sending unit 124 is configured to send the first usage information to the policy.
  • the charging rule function PCRF the PCRF sends the first usage information to the AF through the protocol converter PC, the application access control AAC or the service capability development function SCEF.
  • FIG. 13 is a structural block diagram of a second usage information determining apparatus according to an embodiment of the present invention.
  • the apparatus is applied to a server of a third-party application, and includes a first receiving module 132 and a second determining module 134. Description.
  • the first receiving module 132 is configured to receive the first usage information sent by the policy and charging execution function entity PCEF, where the first usage information is the usage information of the user equipment UE accessing the third-party application before the changeable billable entity changes;
  • the second determining module 134 is connected to the first receiving module 132, and is configured to determine the second usage information according to the first usage information, where the second usage information is a third-party application provider paying for the UE for the UE Access usage information for third-party apps.
  • the first usage information includes information about the traffic and/or duration of the UE accessing the third-party application before the changeable billable entity changes; the second usage information includes the third-party application provider paying for the UE for the UE access. Information on the traffic and/or duration of the three-party application.
  • the second determining module 134 includes: if the billable entity before the change is the UE, the server of the third-party application obtains the second usage information by subtracting the first usage information from the third usage information.
  • the third usage information is a total usage of the third-party application before and after the change of the chargeable entity by the server of the third-party application; if the changeable before the change is the provider of the third-party application, The server of the third-party application determines the first usage information as the second usage information.
  • FIG. 14 is a block diagram showing a preferred structure of a second usage information determining apparatus according to an embodiment of the present invention. As shown in FIG. 14, the apparatus includes a third determining module 142 and a second, in addition to all the modules shown in FIG. Metering module 144, the apparatus will be described below.
  • the third determining module 142 is configured to determine a usage measurement method for measuring the third usage information; the second measurement module 144 is connected to the third determination module 142 and the first receiving module 132, and is configured to be determined according to the determined usage measurement method. The third amount of information is measured.
  • FIG. 15 is a structural block diagram of a third determining module 142 in a second usage information determining apparatus according to an embodiment of the present invention.
  • the third determining module 142 includes a first determining unit 152 and/or a second determining. Unit 154, the third determining module 142 is described below.
  • the first determining unit 152 is configured to determine the usage measurement method by means of an agreement with the operator of the third-party application; the second determining unit 154 is configured to determine the usage measurement method by dynamically negotiating with the operator of the third-party application. .
  • Figure 16 is a block diagram showing the structure of a usage information receiving apparatus according to an embodiment of the present invention.
  • the apparatus is applied to an application function AF.
  • the apparatus includes a second receiving module 162, which will be described below.
  • the second receiving module 162 is configured to receive the first usage information before the change of the billable entity sent by the policy and charging execution function entity PCEF, where the first usage information is accessed by the user equipment UE before the changeable billable subject changes Usage information for third-party applications.
  • the foregoing first usage information includes time and/or traffic for accessing a third-party application.
  • FIG. 17 is a structural block diagram of a second receiving module 162 in the usage information determining apparatus according to an embodiment of the present invention. As shown in FIG. 17, the second receiving module 162 includes a second receiving unit 172, and the second receiving module 162 Be explained.
  • the second receiving unit 172 is configured to receive the first usage information sent by the PCEF through the policy and charging rule function PCRF.
  • a usage information sending device is further provided, which is applied to a policy and charging rule function entity PCRF, where the device includes a third sending module and a fourth sending module, and the device is performed below. Description:
  • a third sending module configured to send, after receiving the first indication sent by the application function AF to change the billable entity, to the policy and charging execution function entity PCEF, before instructing the PCEF to report the change of the billable entity a second indication of the fourth usage information, wherein the fourth usage information includes the cumulative usage information of the user equipment UE that has not been reported by the PCEF to the PCRF before the change of the billable subject, and the fourth sending module is set to After receiving the fourth usage information, the fifth usage information is sent to the AF, where the fifth usage information includes the accumulated usage information of the UE accessing the third-party application before the changeable billable subject changes.
  • the value of the fifth usage information is the value of the fourth usage information, or the fifth usage information is the fourth usage information and the accumulated UE accessing the third party application reported by the PCEF. The sum of the usage information.
  • the fourth usage information includes information about the traffic and/or duration of the UE accessing the third-party application.
  • the apparatus further includes an indication module, configured to be applied to the PCRF, configured to instruct the PCEF to deactivate after receiving the first indication sent by the AF to indicate that the changeable billable subject is changed A monitoring key Monitoring Key for monitoring the fourth usage information.
  • an indication module configured to be applied to the PCRF, configured to instruct the PCEF to deactivate after receiving the first indication sent by the AF to indicate that the changeable billable subject is changed A monitoring key Monitoring Key for monitoring the fourth usage information.
  • the indication module when the PCEF is instructed to deactivate the first monitoring key Monitoring Key for monitoring the first usage information, includes: an indicating unit, configured to send to the PCEF to deactivate the first monitoring key. Indicates or replaces the indication of the first Monitoring Key with a second Monitoring key.
  • This embodiment describes the process in which the billable entity is the user equipment UE when the service is initiated, and the billable entity becomes the provider of the third party application in the service access process.
  • FIG. 18 is a flow chart of the usage report according to the first embodiment of the present invention. As shown in FIG. 18, the process includes the following steps:
  • Step S1802 The UE attaches to the network to establish an IP-CAN session.
  • a Gx session for policy and charging control is established between the PCEF and the PCRF. If the IP-CAN session involves BBERF, a gateway control session for policy control is established between the BBERF and the PCRF.
  • Step S1804 The UE interacts with the third-party application server to initiate service access.
  • the third-party application server charges the service access of the UE, and the accounting information (also called Metering) usage information (Usage Information) accessed by the UE.
  • the usage information may be traffic and/or duration. .
  • Step S1806 A specific interaction process is performed between the third-party application server and the AF, and the service information requested by the user is provided to the application server or the AF.
  • Step S1808 The AF sends a Diameter AAR message to the PCRF to carry the service information.
  • Step S1810 The PCRF returns an acknowledgement message to the AF.
  • Step S1812 The PCRF formulates a PCC rule according to information such as service information, network policy, and user subscription. If BBERF is present, the PCRF also formulates QoS rules based on PCC rules.
  • Step S1814 The PCRF provides a QoS rule to the BBERF.
  • Step S1816 The PCRF provides a PCC rule to the PCEF.
  • the PCEF performs the PCC rule, and performs charging on the third-party service accessed by the UE according to the charging policy in the PCC rule, and statistics (also called measurement) the usage information generated by the UE accessing the service.
  • the usage information can be traffic and/or duration. This charging is for the UE to charge.
  • Step S1818 In the process of the UE accessing the third-party service, the third-party application determines to sponsor the third-party service that the UE is accessing, the application server interacts with the AF, sends an indication of the sponsored service to the AF, and the sponsor identifier, the application provider identifier.
  • Step S1820 The AF sends an AAR message to the PCRF, where the message carries the sponsored data connection information, including the sponsor identifier and the application provider identifier.
  • Step S1822 After the PCRF saves the information, a confirmation message is returned;
  • Step S1824 The PCRF performs policy decision according to information such as service information, network policy, and user subscription. Update the PCC rules that were developed before. The PCRF confirms the corresponding charging key and/or PCRF according to the sponsor identification and the application provider identifier to add the sponsor identification and the application provider identifier in the PCC rule.
  • Step S1826 The PCRF provides a PCC rule to the PCEF.
  • Step S1828 The PCEF returns an acknowledgement message to the PCRF, and carries the accumulated usage information (the usage may be the traffic and/or the duration) before the handover of the chargeable entity in the current service access of the UE.
  • the PCEF can collect statistics on the accumulated usage information since the UE initiated the service, and can also obtain the accumulated usage information since the UE initiated the service by interacting with the charging system (OCS or OFCS).
  • Step S1830 The PCRF sends a RAR message to the AF, where the message carries the accumulated usage information.
  • Step S1832 AF returns a confirmation message.
  • Step S1834 The specific message of the AF and the third-party application server, for example, the cumulative usage information is reported to the third-party application server.
  • AF and third-party application servers can be deployed independently, and AF can be integrated on third-party application servers. Regardless of the deployment, from the perspective of PCRF, the interworking of PCRF and AF can also be considered as the interworking between the PCRF and the third-party application server.
  • the chargeable subject is the user equipment UE, and in the service access process, the process becomes a third-party application provider.
  • FIG. 19 is a flow chart of the usage report according to the second embodiment of the present invention. As shown in FIG. 19, the process includes the following steps:
  • Step S1902 The UE attaches to the network to establish an IP-CAN session.
  • a Gx session for policy and charging control is established between the PCEF and the PCRF. If the IP-CAN session involves BBERF, a gateway control session for policy control is established between the BBERF and the PCRF.
  • Step S1904 The UE interacts with the third-party application server to initiate service access.
  • the third-party application server charges the service access of the UE, and collects statistics (also called measurement) usage information accessed by the UE, where the usage information may be traffic and/or duration.
  • Step S1906 A specific interaction process is performed between the third-party application server and the AF, and the third-party application server provides the AF with the service information requested by the user.
  • Step S1908 The AF sends an HTTP POST to the PC/AAC/SCEF, where the message carries the service information.
  • Step S1910 The PC/AAC/SCEF sends a Diameter AAR message to the PCRF to carry the service information.
  • Step S1912 The PCRF returns an acknowledgement message to the AF.
  • Step S1914 The PC/AAC/SCEF returns an acknowledgement message to the AF.
  • Step S1916 The PCRF formulates a PCC rule according to information such as service information, network policy, and user subscription. If BBERF is present, the PCRF also formulates QoS rules based on PCC rules.
  • Step S1918 The PCRF provides a QoS rule to the BBERF.
  • Step S1920 The PCRF provides a PCC rule to the PCEF.
  • the PCEF performs the PCC rule, and performs statistics (also called metering) on the third-party services accessed by the UE according to the charging policy in the PCC rule.
  • the usage information can be traffic and/or duration.
  • the charging is for the user to charge (the billable subject is the UE).
  • Step S1922 In the process of the UE accessing the third-party service, the third-party application determines to sponsor the third-party service that the UE is accessing, the third-party application server interacts with the AF, sends an indication of the sponsored service to the AF, and the sponsor identifier, the application provider. logo.
  • Step S1924 The AF sends an HTTP PUT message to the PC/AAC/SCEF, where the message carries the sponsored data connection information, including the sponsor identifier and the application provider identifier.
  • Step S1926 The PC/AAC/SCEF sends an AAR message to the PCRF, where the message carries the sponsored data connection information, including the sponsor identifier and the application provider identifier.
  • Step S1928 After the PCRF saves the information, it returns a confirmation message to the PC/AAC.
  • Step S1930 The PC/AAC/SCEF returns an acknowledgement message to the AF.
  • Step S1932 The PCRF performs policy decision according to information such as service information, network policy, and user subscription, and updates the previously established PCC rule.
  • the PCRF confirms the corresponding charging key and/or PCRF according to the sponsor identification and the application provider identifier to add the sponsor identification and the application provider identifier in the PCC rule.
  • Step S1934 The PCRF provides a PCC rule to the PCEF.
  • Step S1936 The PCEF returns an acknowledgement message to the PCRF, and carries the accumulated usage information (this amount may be traffic and/or duration) before the handover of the chargeable entity in the current service access of the UE.
  • the PCEF can collect statistics (also called metering) of the cumulative usage of the UE since it initiated the service, and can also obtain the cumulative usage information since the UE initiated the service by interacting with the charging system (OCS or OFCS).
  • Step S1938 The PCRF sends a RAR message to the PC/AAC, where the message carries the accumulated usage information.
  • Step S1940 The PC/AAC sends an HTTP PUT message to the AF, where the message carries the accumulated usage information.
  • Step S1942 The AF returns a confirmation message to the PC/AAC.
  • Step S1944 The PC/AAC returns an acknowledgement message to the PCRF.
  • Step S1946 The specific message of the AF and the third-party application server is reported to the application server, for example, to the accumulated usage information.
  • the third-party application provider obtains the accumulated usage information generated by the user (and the UE described above) accessing the third-party data application before the gateway performs the changeable billable entity policy. This part of the cumulative usage information is borne by the user.
  • the third-party data application itself also counts the usage information of the user accessing the third-party data. In this way, third-party data application providers can more accurately know the cumulative usage information of their truly sponsored third-party data applications.
  • the amount of the third-party application provider sponsored by the third-party data application is the amount of the user's access to the third-party data minus the billable report reported by the gateway.
  • the cumulative usage information assumed by the user before the change of the subject.
  • AF and third-party application servers can be deployed independently or AF can be integrated on third-party application servers. Regardless of the deployment, the interworking of PCRFPC/AAC/SCEF and AF can also be considered as interworking between PC/AAC/SCEF and third-party application servers from the perspective of PC/AAC/SCEF.
  • This embodiment describes the process in which the billable entity is a third-party application provider when the service is initiated, and becomes a UE during the service access process.
  • FIG. 20 is a flowchart of usage reporting according to Embodiment 3 of the present invention. As shown in FIG. 20, the process includes the following steps:
  • Step S2002 The UE attaches to the network to establish an IP-CAN session.
  • a Gx session for policy and charging control is established between the PCEF and the PCRF.
  • a gateway control session for policy control is established between the BBERF and the PCRF.
  • Step S2004 The UE interacts with the third-party application server to initiate service access.
  • the third-party application server charges the service access of the UE, and collects statistics (also called measurement) usage information accessed by the UE, where the usage information may be traffic and/or duration.
  • Step S2006 A specific interaction process is performed between the third-party application server and the AF, and the service information requested by the user is provided to the AF by the application server, where the third-party application determines the data application that the user subscribes to, and the third-party application server provides the sponsorship service to the AF. Instructions, as well as sponsor identification, application provider identification.
  • Step S2008 The AF sends a Diameter AAR message to the PCRF, carries the service information, and is sponsored data. Connection information, including sponsor logo, application provider ID.
  • Step S2010 The PCRF returns an acknowledgement message to the AF.
  • Step S2012 The PCRF formulates a PCC rule according to information such as service information, network policy, and user subscription.
  • the PCRF confirms the corresponding charging key and/or PCRF according to the sponsor identification and the application provider identifier to add the sponsor identification and the application provider identifier in the PCC rule. If BBERF is present, the PCRF also formulates QoS rules based on PCC rules.
  • Step S2014 The PCRF provides a QoS rule to the BBERF.
  • Step S2016 The PCRF provides a PCC rule to the PCEF.
  • the PCEF performs the PCC rule, and performs charging on the third-party service accessed by the UE according to the charging policy in the PCC rule, and statistics (also called measurement) the usage information generated by the UE accessing the service.
  • the usage information can be traffic and/or duration.
  • the billing is for billing by third party application providers.
  • Step S2018 In the process of the UE accessing the third-party service, the third-party application decides to cancel the third-party service that the sponsoring UE is accessing, and the third-party application server interacts with the AF to send an instruction to cancel the sponsorship to the AF.
  • Step S2020 The AF sends an AAR message to the PCRF, where the message carries the canceled sponsorship indication.
  • Step S2022 After the PCRF saves the information, a confirmation message is returned.
  • Step S2024 The PCRF performs policy decision according to information such as service information, network policy, and user subscription, and updates the previously established PCC rule, and carries the cancellation sponsorship instruction.
  • the PCRF carries other charging keys that can charge users in the PCC rules.
  • Step S2026 The PCRF provides a PCC rule to the PCEF.
  • Step S2028 The PCEF returns an acknowledgement message to the PCRF, and carries the accumulated usage information (the usage may be the traffic and/or the duration) before the handover of the chargeable entity in the current service access of the UE.
  • the PCEF can collect statistics on the accumulated usage information since the UE initiated the service, and can also obtain the accumulated usage information since the UE initiated the service by interacting with the charging system (OCS or OFCS).
  • Step S2030 The PCRF sends a RAR message to the AF, where the message carries the accumulated usage information.
  • Step S2032 The AF returns a confirmation message.
  • Step S2034 The specific message of the AF and the third-party application server is reported to the application server, for example, to the accumulated usage.
  • AF and third-party application servers can be deployed independently or AF can be integrated on third-party application servers. Regardless of the deployment, from the perspective of PCRF, the interworking between PCRF and AF can also be considered as PCRF and Interoperability of third-party application servers.
  • This embodiment describes the process in which the billable entity is a third-party application provider when the service is initiated, and becomes a UE during the service access process.
  • FIG. 21 is a flowchart of usage reporting according to Embodiment 4 of the present invention. As shown in FIG. 21, the process includes the following steps:
  • Step S2102 The UE attaches to the network to establish an IP-CAN session.
  • a Gx session for policy and charging control is established between the PCEF and the PCRF. If the IP-CAN session involves BBERF, a gateway control session for policy control is established between the BBERF and the PCRF.
  • Step S2104 The UE interacts with the third-party application server to initiate service access.
  • the third-party application server charges the service access of the UE, and statistics (also called metering) the traffic and/or duration of the UE access.
  • Step S2106 a specific interaction process is performed between the third-party application server and the AF, and the service information requested by the user is provided to the AF by the application server, where the third-party application determines the data application that the user subscribes to, and the third-party application server provides the sponsorship service to the AF. Instructions, as well as sponsor identification, application provider identification.
  • Step S2108 The AF sends an HTTP POST message to the PC/AAC/SCEF, where the message carries the service information, the sponsored data connection information, including the sponsor identifier, and the application provider identifier.
  • Step S2110 The PC/AAC/SCEF sends an AAR message to the PCRF, where the message carries the service information, the sponsored data connection information, including the sponsor identifier, and the application provider identifier.
  • Step S2112 The PCRF returns an acknowledgement message to the PC/AAC/SCEF.
  • Step S2114 The PC/AACSCEF returns an acknowledgement message to the AF.
  • Step S2116 The PCRF formulates a PCC rule according to information such as service information, network policy, and user subscription.
  • the PCRF confirms the corresponding charging key and/or PCRF according to the sponsor identification and the application provider identifier to add the sponsor identification and the application provider identifier in the PCC rule. If BBERF is present, the PCRF also formulates QoS rules based on PCC rules.
  • Step S2118 The PCRF provides a QoS rule to the BBERF.
  • Step S2120 The PCRF provides a PCC rule to the PCEF.
  • the PCEF performs the PCC rule, and performs charging on the third-party service accessed by the UE according to the charging policy in the PCC rule, and performs statistics (also called measurement) on the UE access service.
  • the usage information can be traffic and/or duration.
  • the billing is for billing by third party application providers.
  • Step S2122 In the process of the UE accessing the third-party service, the third-party application decides to cancel the third-party service that the sponsoring UE is accessing, and the third-party application server interacts with the AF to send an instruction to cancel the sponsorship to the AF.
  • Step S2124 The AF sends an HTTP PUT message to the PC/AAC/SCEF, where the message carries the canceled sponsorship indication.
  • Step S2126 The PC/AAC/SCEF sends an AAR message to the PCRF, where the message carries the canceled sponsorship indication.
  • Step S2128 After the PCRF saves the information, it returns a confirmation message to the PC/AAC.
  • Step S2130 The PC/AAC/SCEF returns an acknowledgement message to the AF.
  • Step S2132 The PCRF performs policy decision according to information such as service information, network policy, and user subscription, and updates the previously established PCC rule, and carries the cancellation sponsorship instruction.
  • the PCRF carries other charging keys that can charge users in the PCC rules.
  • Step S2134 The PCRF provides a PCC rule to the PCEF.
  • Step S2136 The PCEF returns an acknowledgement message to the PCRF, and carries the accumulated usage information before the handover of the chargeable entity in the current service access of the UE (the usage information may be traffic and/or duration).
  • the PCEF can collect statistics on the accumulated usage information since the UE initiated the service, and can also obtain the accumulated usage information since the UE initiated the service by interacting with the charging system (OCS or OFCS).
  • Step S2138 The PCRF sends a RAR message to the PC/AAC, where the message carries the accumulated usage information.
  • Step S2140 The PC/AAC sends a RAR message to the AF, where the message carries the accumulated usage information.
  • Step S2142 The AF returns a confirmation message to the PC/AAC.
  • Step S2144 The PC/AAC returns an acknowledgement message to the PCRF.
  • Step S2146 The specific message of the AF and the third-party application server, for example, is reported to the third-party application server.
  • the third-party application provider obtains the usage information sponsored by the third-party application provider before the gateway performs the changeable billable entity policy. If the billable entity is always the UE when the UE ends the service access, the billable entity reported by the usage gateway sponsored by the third-party application provider changes the accumulated usage information sponsored by the third-party application provider.
  • AF and third-party application servers can be deployed independently or AF can be integrated into third-party applications. On the server. Regardless of the deployment, the interworking of PC/AAC/SCEF and AF can also be considered as interworking between PC/AAC/SCEF and third-party application servers from the perspective of PCRFPC/AAC/SCEF.
  • This embodiment describes the process in which the billable entity is the user equipment UE when the service is initiated, and the billable entity becomes the provider of the third party application in the service access process.
  • FIG. 22 is a flowchart of usage reporting according to Embodiment 5 of the present invention. As shown in FIG. 22, the process includes the following steps:
  • Step S2202 The UE attaches to the network to establish an IP-CAN session.
  • a Gx session for policy and charging control is established between the PCEF and the PCRF. If the IP-CAN session involves BBERF, a gateway control session for policy control is established between the BBERF and the PCRF.
  • Step S2204 The UE interacts with the third-party application server to initiate service access.
  • the third-party application server charges the service access of the UE, and the accounting information (also called Metering) usage information (Usage Information) accessed by the UE.
  • the usage information may be traffic and/or duration. .
  • Step S2206 A specific interaction process is performed between the third-party application server and the AF, and the application server or the AF is provided with the service information requested by the user and the indication that the sponsored data connection is not activated (ie, the indication of not sponsoring the service).
  • Step S2208 The AF sends a Diameter AAR message to the PCRF, carrying the service information, the sponsor identity, the application provider identity, and an indication that the sponsored data connection is not activated.
  • Step S2210 The PCRF returns an acknowledgement message to the AF.
  • Step S2212 The PCRF formulates a PCC rule according to information such as service information, network policy, and user subscription. If BBERF is present, the PCRF also formulates QoS rules based on PCC rules. Since both PCRF and AF support support changing the billable subject, or the PCRF receives an indication that the sponsored data connection is not activated or according to the user subscription or operator policy, the PCRF determines the activation usage monitoring. The PCRF carries the monitoring key Monitoring key1 in the PCC rule (Monitoring Key1 is set according to the sponsor identification).
  • Step S2214 The PCRF provides a QoS rule to the BBERF.
  • Step S2216 The PCRF provides a PCC rule to the PCEF, and carries a corresponding usage threshold (the usage threshold may be traffic or duration).
  • the PCEF executes the PCC rules and monitors the usage of the corresponding service data according to the PCC rules.
  • the PCEF reports the cumulative usage to the PCRF (the cumulative usage is equal to the usage threshold), and the PCRF then issues a new usage threshold.
  • the PCRF calculates the total accumulated usage of the UE to access the third-party application according to the cumulative usage of each report.
  • Step S2218 In the process of the UE accessing the third-party service, the third-party application determines to sponsor the third-party service that the UE is accessing, and the application server interacts with the AF to send an indication of the sponsored service to the AF (ie, an instruction to activate the sponsored data connection), And sponsor logo, application provider ID, and optional sponsorship usage threshold.
  • the third-party application determines to sponsor the third-party service that the UE is accessing, and the application server interacts with the AF to send an indication of the sponsored service to the AF (ie, an instruction to activate the sponsored data connection), And sponsor logo, application provider ID, and optional sponsorship usage threshold.
  • Step S2220 The AF sends an AAR message to the PCRF, where the message carries the sponsored data connection information, including a sponsor identifier, an application provider identifier, an indication to activate the sponsored data connection, and an optional sponsorship usage threshold.
  • the sponsored data connection information including a sponsor identifier, an application provider identifier, an indication to activate the sponsored data connection, and an optional sponsorship usage threshold.
  • Step S2222 After the PCRF saves the information, it returns a confirmation message.
  • Step S2224 The PCRF performs policy decision according to information such as service information, network policy, and user subscription, and updates the previously established PCC rule.
  • the PCRF confirms the corresponding charging key and/or PCRF according to the sponsor identification and the application provider identifier to add the sponsor identification and the application provider identifier in the PCC rule.
  • the PCRF decided to deactivate the monitoring for Monitoring Key1 usage. If the AF provides a sponsorship usage threshold, the PCRF sets the monitoring key Monitoring Key2 according to the sponsor identification and carries the Monitoring Key2 in the updated PCC rule (ie, the Monitoring Key1 is replaced with the Monitoring Key2). At the same time, the PCRF provides the PCEF with the usage threshold corresponding to the Monitoring Key2 (the usage threshold is set according to the sponsored usage threshold provided by the AF.
  • Step S2226 The PCRF provides an updated PCC rule to the PCEF, and carries an indication to deactivate the monitoring of the usage of the Monitoring Key1. If the PCRF assigns Monitoring key 2, the PCRF also provides a corresponding usage threshold to the PCEF. In order to activate the usage monitoring of the monitoring key1, the PCRF can only issue an indication to activate the monitoring of the usage key of the monitoring key1, or simply replace the monitoring key2 with the monitoring key1, or simultaneously issue an indication to activate the monitoring of the usage key of the monitoring key1, and Replace Monitoring key2 with Monitoring key1.
  • Step S2228 The PCEF returns an acknowledgement message to the PCRF. Since the usage monitoring for the Monitoring Key1 is deactivated, the PCEF carries the cumulative usage of the Monitoring Key1 that has not been reported to the PCRF before the PCEF in the response message. The PCRF receives the accumulated usage reported by the PCEF and adds it to the total accumulated usage saved before, and obtains the accumulated usage information of the third-party application accessing the third-party application before the third-party application changes the charging entity. If the cumulative usage of Monitoring Key1 is not reported by the PCEF, the cumulative usage reported by the PCEF this time is the cumulative usage information of the third-party application accessing the third-party application before the third-party application changes the charging entity.
  • the PCEF may also not carry the accumulated usage amount in the acknowledgment message, but after sending the acknowledgment message, it separately sends a usage report message, and the accumulated usage amount is reported before the PCEF is reported.
  • the PCRF After receiving the cumulative usage reported by the PCEF, the PCRF adds the total accumulated usage to the previously accumulated total usage, and obtains the accumulated usage information of the third-party application before the third-party application changes the charging entity. If the cumulative usage of the Monitoring Key1 is not reported by the PCEF, the cumulative usage reported by the PCEF is the cumulative usage information of the UE accessing the third application before the third party application changes the charging entity.
  • Step S2230 The PCRF sends a RAR message to the AF, where the message carries the accumulated usage information.
  • Step S2232 The AF returns a confirmation message.
  • Step S2234 The specific message of the AF and the third-party application server, for example, reporting the cumulative usage information to the third-party application server.
  • AF and third-party application servers can be deployed independently, and AF can be integrated on third-party application servers. Regardless of the deployment, from the perspective of PCRF, the interworking of PCRF and AF can also be considered as the interworking between the PCRF and the third-party application server.
  • PC/AAC/SCEF In the scenario where PC/AAC/SCEF exists, the PC/AAC/SCEF is responsible for the conversion between the HTTP message and the Diameter message. The rest of the process is similar and will not be described again.
  • the third-party application provider obtains the accumulated usage information generated by the user (with the UE described above) accessing the third-party data application before the gateway performs the changeable billable entity policy. This part of the cumulative usage information is borne by the user.
  • the third-party data application itself also counts the usage information of the user accessing the third-party data. In this way, third-party data application providers can more accurately know the cumulative usage information of their truly sponsored third-party data applications. If the billable entity is always a third-party application when the UE ends the service access, the amount of the third-party application provider sponsored by the third-party data application is the amount of the user's access to the third-party data minus the billable report reported by the gateway. The cumulative usage information assumed by the user before the change of the subject.
  • AF and third-party application servers can be deployed independently or AF can be integrated on third-party application servers. Regardless of the deployment, the interworking of PCRFPC/AAC/SCEF and AF can also be considered as interworking between PC/AAC/SCEF and third-party application servers from the perspective of PC/AAC/SCEF.
  • This embodiment describes the process in which the billable entity is a third-party application provider when the service is initiated, and becomes a UE during the service access process.
  • FIG. 23 is a flow chart of the usage report according to Embodiment 6 of the present invention. As shown in FIG. 23, the process includes the following steps:
  • Step S2302 The UE attaches to the network to establish an IP-CAN session.
  • a Gx session for policy and charging control is established between the PCEF and the PCRF. If the IP-CAN session involves BBERF, a gateway control session for policy control is established between the BBERF and the PCRF.
  • Step S2304 The UE interacts with the third-party application server to initiate service access.
  • the third-party application server charges the service access of the UE, and collects statistics (also called measurement) usage information accessed by the UE, where the usage information may be traffic and/or duration.
  • Step S2306 A specific interaction process is performed between the third-party application server and the AF, and the service information requested by the user is provided to the AF by the application server, where the third-party application determines the data application that the user subscribes to, and the third-party application server provides the sponsorship service to the AF.
  • Step S2308 The AF sends a Diameter AAR message to the PCRF, carries the service information, and the sponsored data connection information, including the sponsor identifier, the application provider identifier, and the usage threshold value sponsored by the third party application.
  • Step S2310 The PCRF returns an acknowledgement message to the AF.
  • Step S2312 The PCRF formulates a PCC rule according to information such as service information, network policy, and user subscription.
  • the PCRF confirms the corresponding charging key and/or PCRF according to the sponsor identification and the application provider identifier to add the sponsor identification and the application provider identifier in the PCC rule. If BBERF is present, the PCRF also formulates QoS rules based on PCC rules. In addition, the PCRF sets the monitoring key Monitoring Key1 according to the sponsor identification. And carry the Monitoring Key1 in the PCC rules.
  • Step S2314 The PCRF provides a QoS rule to the BBERF.
  • Step S2316 The PCRF provides a PCC rule to the PCEF to activate the usage monitoring for the Monitoring key1.
  • the PCRF provides the PCEF with the usage threshold of the monitoring key1 (the usage threshold is set by the PCRF according to the sponsored usage threshold provided by the AF).
  • the PCEF executes the PCC rules and monitors the usage of the third-party applications accessed by the UE according to the PCC rules.
  • the PCEF reports the cumulative usage to the PCRF (the cumulative usage is equal to the usage threshold), and the PCRF then issues a new usage threshold.
  • the PCRF calculates the total accumulated usage of the UE to access the third-party application according to the cumulative usage of each report.
  • Step S2318 In the process of the UE accessing the third-party service, the third-party application decides to cancel the third-party service that the sponsoring UE is accessing, and the third-party application server interacts with the AF to send an instruction to cancel the sponsorship to the AF.
  • Step S2320 The AF sends an AAR message to the PCRF, where the message carries a sponsor identity, an application provider identifier, and an indication to deactivate the sponsored data connection.
  • Step S2322 After the PCRF saves the information, it returns a confirmation message.
  • Step S2324 The PCRF performs policy decision according to information such as service information, network policy, and user subscription, and updates the previously established PCC rule.
  • the PCRF carries other charging keys that can charge users in the PCC rules and/or does not carry the sponsor identification and the application provider identifier in the PCC rules.
  • the PCRF decided to deactivate the usage monitoring for Monitoring key1.
  • the PCRF decides to continue monitoring the usage of the data of the UE accessing the third-party application, and the PCRF sets the monitoring key according to the sponsor identifier. Key2 and is included in the PCC rules. At the same time, the corresponding usage threshold is assigned to the Monitoring key2.
  • Step S2326 The PCRF provides a PCC rule to the PCEF, and instructs the PCEF to deactivate the usage monitoring of the Monitoring key1. If the PCRF assigns Monitoring key 2, the PCRF also provides a corresponding usage threshold to the PCEF. In order to activate the usage monitoring of the monitoring key1, the PCRF can only issue an indication to activate the monitoring of the usage key of the monitoring key1, or simply replace the monitoring key2 with the monitoring key1, or simultaneously issue an indication to activate the monitoring of the usage key of the monitoring key1, and Replace Monitoring key2 with Monitoring key1.
  • Step S2328 The PCEF returns an acknowledgement message to the PCRF. Since the usage monitoring of the monitoring key1 is deactivated, the PCEF carries the cumulative usage of the Monitoring Key1 that has not been reported before the PCEF in the response message. The PCRF receives the accumulated usage reported by the PCEF and adds it to the total accumulated usage saved before, and obtains the accumulated usage information of the third-party application before the third-party application changes the charging entity (ie, the third-party application sponsors Usage information). If the cumulative usage of the Monitoring Key1 is not reported by the PCEF, the cumulative usage reported by the PCEF is the cumulative usage information of the UE accessing the third application before the third party application changes the charging entity.
  • the cumulative usage reported by the PCEF is the cumulative usage information of the UE accessing the third application before the third party application changes the charging entity.
  • the PCEF may also not carry the accumulated usage amount in the acknowledgment message, but after sending the acknowledgment message, it separately sends a usage report message, and the accumulated usage amount is reported before the PCEF is reported.
  • the PCRF receives the accumulated usage reported by the PCEF and adds it to the total accumulated usage saved before, and obtains the accumulated usage information of the third-party application accessing the third-party application before the third-party application changes the charging entity. If the cumulative usage of the Monitoring Key1 is not reported by the PCEF, the cumulative usage reported by the PCEF is the cumulative usage information of the UE accessing the third application before the third party application changes the charging entity.
  • Step S2330 The PCRF sends a RAR message to the AF, where the message carries the accumulated usage information.
  • Step S2332 The AF returns a confirmation message.
  • Step S2334 The specific message of the AF and the third-party application server is reported to the application server, for example, to the accumulated usage.
  • AF and third-party application servers can be deployed independently or AF can be integrated on third-party application servers. Regardless of the deployment, from the perspective of PCRF, the interworking of PCRF and AF can also be considered as the interworking between the PCRF and the third-party application server.
  • PC/AAC/SCEF In the scenario where PC/AAC/SCEF exists, the PC/AAC/SCEF is responsible for the conversion between the HTTP message and the Diameter message. The rest of the process is similar and will not be described again.
  • the operator and all third-party application providers use the same usage charging method (operators and all third-party application providers use time-based charging, traffic accounting, or simultaneous time and traffic).
  • the metering method may also be differentiated, and one of the following two methods may be used:
  • the operator and the third-party application provider can determine the fixed metering method (Metering Method) by signing the agreement. For example, if the carrier A and the third-party application provider A are contracted according to the measurement method of the traffic, after the UE accesses the third-party application, the third-party application server determines that the user UE accesses the service through the operator A, and the third-party application server The traffic is used as the usage information.
  • the PCRF determines the measurement method according to the third-party application provider that provides the service, and carries the measurement method as the traffic indication in the PCC rule.
  • the PCEF indicates the traffic generated by the user accessing the service according to the measurement method. Perform statistics. When the billable subject changes, the PCEF returns the usage information of the traffic to the PCRF. Optionally, the PCRF returns the usage information of the traffic to the AF.
  • the measurement method using the duration or the simultaneous duration and flow is similar and will not be described again.
  • the operator and the third-party application provider dynamically negotiate the measurement method. For example, if operator A and third-party application provider A sign up, they can use time, traffic, or simultaneous time and traffic for charging.
  • the third-party application server determines that the user UE accesses the service through the operator A, and the third-party application server may determine one of the three types as the measurement method of the service orientation, and if the third-party application server decides to adopt
  • the third-party server sends the measurement method to the PCRF together with the service information; the PCRF carries the measurement method as the traffic indication in the PCC rule according to the indication of the third-party application server.
  • the PCEF performs statistics on the traffic generated by the user accessing the service according to the measurement method.
  • the PCEF returns the usage information of the traffic to the PCRF.
  • the PCRF returns the usage information of the traffic to the AF.
  • the measurement method using the duration or the simultaneous duration and flow is similar and will not be described again.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are located in multiple In the processor.
  • Embodiments of the present invention also provide a storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • the policy and charging execution function entity PCEF sends the first usage information before the change of the billable entity to the server of the third-party application, where the first usage information is the user equipment UE access before the changeable billable entity changes.
  • the usage information of the three-party application the first usage information is used by the server of the third-party application to determine the second usage information, where the second usage information is the usage information used by the provider of the third-party application for the UE to access the third-party application. .
  • the storage medium is further arranged to store program code for performing the following steps:
  • the policy and charging execution function entity PCEF sends the first usage information before the change of the billable entity to the application function AF, where the first usage information is the user equipment UE accessing the third party application before the chargeable subject changes Usage information.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the server of the third-party application receives the first usage information sent by the policy and the charging execution function entity PCEF, where the first usage information is the usage information of the user equipment UE accessing the third-party application before the changeable billable entity changes;
  • the server of the third-party application determines the second usage information according to the first usage information, where the second usage information is usage information used by the provider of the third-party application for the UE to access the third-party application.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the first usage information before the change of the billable entity sent by the application function AF receiving policy and the charging execution function entity PCEF, wherein the first usage information is the user equipment UE accessing the third party application before the changeable billable subject changes Usage information.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the PCRF After receiving the first indication sent by the application function AF to indicate that the changeable billable entity is sent, the PCRF is sent to the policy and charging enforcement function entity PCEF to instruct the PCEF to report the billable entity.
  • a second indication of the fourth usage information before the change occurs, wherein the fourth usage information includes the accumulated usage information of the user equipment UE that has not been reported by the PCEF to the PCRF before the change of the billable subject;
  • the PCRF after receiving the fourth usage information, the PCRF sends the fifth usage information to the AF, where the fifth usage information includes the accumulated usage information of the UE accessing the third-party application before the changeable billable subject changes.
  • the foregoing storage medium may include, but is not limited to, a USB flash drive, a Read-Only Memory (ROM), and a Random Access Memory (RAM).
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the usage information determining method, the sending method, the receiving method, and the apparatus have the following beneficial effects: when the billable subject is changed, the first usage information before the changeable billable subject changes
  • the server is sent to the third-party application, so that the third-party server can accurately measure the usage information that the third-party application provider should pay for the user equipment UE, and improve the charging precision, thereby solving the charging existing in the related technology.
  • the problem of error in turn, achieves the effect of reducing the billing error.

Abstract

本发明提供了一种用量信息确定方法、发送方法、接收方法及装置，其中，该用量信息确定方法包括：策略与计费执行功能实体PCEF将可计费主体发生变化之前的第一用量信息发送给第三方应用的服务器，其中，该第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息，该第一用量信息用于第三方应用的服务器确定第二用量信息，该第二用量信息为第三方应用的提供商为UE支付的用于UE访问第三方应用的用量信息。通过本发明，解决了相关技术中存在的计费误差的问题，进而达到了减小计费误差的效果。

Description

用量信息确定方法、发送方法、接收方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及一种用量信息确定方法、发送方法、接收方法及装置。
背景技术
第三代合作伙伴计划(3rd Generation Partnership Project，简称为3GPP)的策略和计费控制(Policy and Charging Control，简称为PCC)架构是一个能够应用于多种接入技术的功能框架。例如，应用于通用移动通信系统(Universal Mobile Telecommunications System，简称为UMTS)的陆上无线接入网(UMTS Terrestrial Radio Access Network，简称为UTRAN)、全球移动通信系统(Global system for Mobile Communication，简称为GSM)/GSM数据增强演进(Enhanced Data rates for Global Evolution，简称为EDGE)无线接入网、互通无线局域网(I-WLAN)以及演进的分组系统(Evolved Packet System，简称为EPS)等。
图1为相关技术的Rel-8PCC非漫游架构的示意图一，以下参照图1对该PCC架构中的各个逻辑功能实体及其接口功能进行描述：
应用功能实体(Application Function，简称为AF)，提供业务应用的接入点，这些业务应用所使用的网络资源需要进行动态的策略控制。在业务面进行参数协商时，AF将相关业务信息传递给策略与计费规则功能实体(Policy and Charging Rules Function，简称为PCRF)，如果这些业务信息与PCRF的策略相一致，则PCRF接受该协商；否则，PCRF拒绝该协商，并在反馈中同时给出PCRF可接受的业务参数。随后，AF可将这些参数返回给用户设备(User Equipment，简称为UE)。其中，AF和PCRF之间的接口是Rx接口。
PCRF是PCC的核心，负责策略决策和计费规则的制定。PCRF提供了基于业务数据流的网络控制规则，这些网络控制包括业务数据流的监测、门控(Gating Control)、服务质量(Quality of Service，简称为QoS)控制以及基于数据流的计费规则等。PCRF将其制定的策略和计费规则发送给策略与计费执行功能实体(Policy and Charging Enforcement Function，简称为PCEF)执行，同时，PCRF还需要保证这些规则和用户的签约信息一致。PCRF制定策略和计费规则的依据包括：从AF获取与业务相关的信息；从用户签约数据库(Subscription Profile Repository，简称为SPR)获取用户策略计费控制签约信息；从PCEF获取与承载相关网络的信息。
PCEF，用于在承载面执行PCRF所制定的策略和计费规则。PCEF按照PCRF所发送的规则中的业务数据流过滤器对业务数据流进行监测，进而对这些业务数据流执行PCRF所制定的策略和计费规则。在承载建立时，PCEF按照PCRF发送的规则进行QoS授权，并根据AF的执行进行门控控制。根据PCRF发送的计费规则，PCEF执行相应的业务数据流计费操作，计费既可以是在线计费，也可以是离线计费。如果是在线计费，则PCEF需要和在线计费系统(Online Charging System，简称为OCS)一起进行信用管理。离线计费时，PCEF和离线计费系统(Offline Charging System，简称为OFCS)之间交换相关计费信息。PCEF与PCRF之间的接口是Gx接口，与OCS之间的接口是Gy接口，与OFCS之间的接口是Gz接口。PCEF通常位于网络的网关(Gate-Way，简称为GW)内，如GPRS中的GPRS网关支持节点(GGSN)以及I-WLAN中的分组数据网关(Packet Data Gateway，简称为PDG)。
承载绑定和事件报告功能实体(Bearer Binding and Event Reporting Function，简称为BBERF)，其功能包括承载绑定、上行承载绑定的验证、以及事件报告。当UE通过E-UTRAN接入，并且S-GW与P-GW之间采用PMIPv6协议时，BBERF就位于S-GW，当UE通过可信任非3GPP接入系统接入时，BBERF位于可信任非3GPP接入网关，当UE通过不可信任非3GPP接入系统接入时、BBERF位于演进的分组数据网关(Evolved Packet Data Gateway，简称为ePDG)。此时，PCEF不再执行承载绑定功能。
用户签约数据库(SPR)存储了和策略控制与计费相关的用户策略计费控制签约信息。SPR和PCRF之间的接口是Sp接口。
在线计费系统(OCS)，与PCEF一起进行在线计费方式下用户信用的控制和管理。
离线计费系统(OFCS)，与PCEF一起完成离线计费方式下的计费操作。
以上PCC架构通过各功能实体实现了对UE为访问一个分组数据网络(Packet Data Network，简称为PDN)所建立的IP连接接入网(IP Connectivity Access Network，简称为IP-CAN)会话的策略计费控制。
随着移动互联网的发展，运营商需要与第三方数据应用提供商进行互通，为第三方数据应用提供商提供的业务进行QoS保障。由于目前PCC支持的Rx接口采用的Diameter协议，而对于大多数第三方数据应用提供商来说，他们更擅长基于SOAP、REST协议的开发。目前业界研究PCC架构支持基于SOAP/REST协议的Rx接口。在PCRF和AF直接设置一个称为协议转换器(Protocol Converter，简称PC)的逻辑功能，用于将SOAP或REST协议转换成Diameter，可以如图2所示，图2是相关技术中的Rel-8PCC非漫游架构的示意图二。其中，还可以在PC上面增加一些接入控制功能， 以便能够更好的实现运营商对第三方数据应用的接入控制，此时该逻辑功能还称为应用接入控制(Application Access Control，简称AAC)功能实体或者称为业务能力开放功能(Service Capability Exposure Function)。
第三方数据应用提供商可以在会话发起或会话过程中改变会话业务的可计费的主体(chargeable party)，即访问业务的用户被计费或是第三方业务提供商被计费。
对于在会话过程中改变可计费主体的场景，由于当第三方应用提供商向PCRF发起变更请求到PCEF根据PCRF更新的策略执行计费策略有一个时间间隙，因此在这个时间间隙过程中会差生一定的计费误差。对单个用户单次访问，这个计费误差会比较小，但考虑到会有海量的用户访问一个第三方数据应用，因此运营商给第三方应用进行费用结算时，会出现非常大的累计误差。考虑到未来网络提供的速率将越来越快，因此这个误差将是非常惊人的。特别是考虑的存在PC/AAC的架构，由于新的网元的出现，势必会增加消息传递的延迟。因此，在相关技术中存在着计费误差的问题。
针对相关技术中存在的计费误差的问题，目前尚未提出有效的解决方案。
发明内容
本发明提供了一种用量信息确定方法、发送方法、接收方法及装置，以至少解决相关技术中存在的计费误差的问题。
根据本发明的一个方面，提供了一种用量信息确定方法，其特征在于，包括：策略与计费执行功能实体PCEF将可计费主体发生变化之前的第一用量信息发送给第三方应用的服务器，其中，所述第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息，所述第一用量信息用于所述第三方应用的服务器确定第二用量信息，所述第二用量信息为所述第三方应用的提供商为所述UE支付的用于所述UE访问所述第三方应用的用量信息。
可选地，所述第一用量信息包括可计费主体变化之前所述UE访问所述第三方应用的流量和/或时长的信息；所述第二用量信息包括所述第三方应用的提供商为所述UE支付的用于所述UE访问所述第三方应用的流量和/或时长的信息。
可选地，若变化之前的可计费主体是所述UE，则所述第二用量信息为第三用量信息减去所述第一用量信息，所述第三用量信息为所述第三方应用的服务器统计的所述UE在可计费主体变化之前和变化之后访问所述第三方应用的总用量；若变化之前的可计费主体是所述第三方应用的提供商，则所述第二用量信息为所述第一用量信息。
可选地，所述PCEF将可计费主体发生变化之前的第一用量信息发送给所述第三 方应用的服务器之前，还包括：所述PCEF确定用于计量所述第一用量信息的用量计量方法，其中，所述PCEF和所述第三方应用的服务器采用相同的用量计量方法；所述PCEF根据确定的用量计量方法计量所述第一用量信息。
可选地，所述PCEF确定用于计量所述第一用量信息的用量计量方法包括：所述PCEF接收策略和计费规则功能PCRF发送的策略和计费控制PCC规则，其中，所述PCC规则中携带所述用量计量方法的指示信息，所述PCRF根据所述第三方应用的提供商确定与所述第三方应用的服务器相同的用量计量方法。
可选地，所述第三方应用的服务器向所述PCRF提供所述第三方应用的服务器采用的用量计量方法的指示信息，所述PCRF根据所述第三方应用的服务器提供的用量计量方法的指示信息确定所述PCEF采用的用量计量方法。
可选地，所述PCEF根据确定的用量计量方法计量所述第一用量信息包括以下至少之一：所述PCEF根据确定的用量计量方法通过由所述PCEF统计的方式确定第一用量信息；所述PCEF根据确定的用量计量方法通过由所述PCEF与在线计费系统OCS进行交互的方式确定所述第一用量信息；所述PCEF根据确定的用量计量方法通过由所述PCEF与离线计费系统OFCS进行交互的方式确定所述第一用量信息。
可选地，所述PCEF将所述第一用量信息发送给所述第三方应用的服务器包括以下至少之一：所述PCEF将所述第一用量信息发送给策略和计费规则功能PCRF，所述PCRF将所述第一用量信息发送给应用功能AF，所述AF将所述第一用量信息上报给所述第三方应用的服务器；所述PCEF将所述第一用量信息发送给策略和计费规则功能PCRF，所述PCRF通过协议转换器PC、应用接入控制AAC或业务能力开发功能SCEF将所述第一用量信息发送给应用功能AF，所述AF将所述第一用量信息上报给所述第三方应用的服务器。
根据本发明的另一方面，提供了一种用量信息发送方法，包括：策略与计费执行功能实体PCEF将可计费主体发生变化之前的第一用量信息发送给应用功能AF，其中，所述第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息。
可选地，所述第一用量信息包括访问所述第三方应用的时间和/或流量。
可选地，所述PCEF将所述第一用量信息发送给所述AF包括以下至少之一：所述PCEF将所述第一用量信息发送给策略和计费规则功能PCRF，所述PCRF将所述第一用量信息发送给所述AF；所述PCEF将所述第一用量信息发送给策略和计费规则功能PCRF，所述PCRF通过协议转换器PC、应用接入控制AAC或业务能力开发功能SCEF将所述第一用量信息发送给所述AF。
根据本发明的另一方面，提供了一种用量信息确定方法，包括：第三方应用的服 务器接收策略与计费执行功能实体PCEF发送的第一用量信息，其中，所述第一用量信息为可计费主体变化之前用户设备UE访问所述第三方应用的用量信息；所述第三方应用的服务器根据所述第一用量信息确定第二用量信息，其中，所述第二用量信息为所述第三方应用的提供商为所述UE支付的用于所述UE访问所述第三方应用的用量信息。
可选地，所述第一用量信息包括可计费主体变化之前所述UE访问所述第三方应用时的流量和/或时长的信息；所述第二用量信息包括所述第三方应用的提供商为所述UE支付的用于所述UE访问所述第三方应用的流量和/或时长的信息。
可选地，所述第三方应用的服务器根据所述第一用量信息确定第二用量信息包括：若变化之前的可计费主体是所述UE，所述第三方应用的服务器通过将第三用量信息减去所述第一用量信息得到所述第二用量信息，其中，所述第三用量信息为所述第三方应用的服务器统计的所述UE在可计费主体变化之前和变化之后访问所述第三方应用的总用量；若变化之前的可计费主体是所述第三方应用的提供商，所述第三方应用的服务器将所述第一用量信息确定为所述第二用量信息。
可选地，所述第三方应用的服务器根据所述第一用量信息确定所述第二用量信息之前，还包括：所述第三方应用的服务器确定用于计量所述第三用量信息的用量计量方法；所述第三方应用的服务器根据确定的用量计量方法计量所述第三用量信息。
可选地，所述第三方应用的服务器确定用于计量所述第三用量信息的用量计量方法包括：所述第三方应用的服务器通过与所述第三方应用的运营商签约协议的方式确定所述用量计量方法；所述第三方应用的服务器通过与所述第三方应用的运营商进行动态协商的方式确定所述用量计量方法。
根据本发明的另一方面，提供了一种用量信息接收方法，包括：应用功能AF接收策略与计费执行功能实体PCEF发送的可计费主体发生变化之前的第一用量信息，其中，所述第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息。
可选地，所述第一用量信息包括访问所述第三方应用的时间和/或流量。
可选地，所述AF接收所述PCEF发送的所述第一用量信息包括：所述AF通过策略和计费规则功能PCRF接收所述PCEF发送的所述第一用量信息。
根据本发明的另一方面，提供了一种用量信息发送方法，包括：策略与计费规则功能实体PCRF在接收应用功能AF发送的用于指示改变可计费主体的第一指示后，向策略与计费执行功能实体PCEF发送用于指示所述PCEF上报可计费主体发生变化之前的第四用量信息的第二指示，其中，所述第四用量信息包括可计费主体变化之前 所述PCEF还未向所述PCRF上报的用户设备UE访问第三方应用的累计用量信息；所述PCRF在接收到所述第四用量信息后，向所述AF发送第五用量信息，其中，所述第五用量信息包括可计费主体变化之前所述UE访问第三方应用的累计用量信息。
可选地，所述第五用量信息的取值为所述第四用量信息的取值，或者，所述第五用量信息的取值为所述第四用量信息与所述PCEF之前上报的所述UE访问第三方应用的累计用量信息的和。
可选地，所述第四用量信息包括所述UE访问所述第三方应用的流量和/或时长的信息。
可选地，所述PCRF在接收所述AF发送的用于指示改变可计费主体的所述第一指示后，还包括：所述PCRF指示所述PCEF去激活用于监控所述第四用量信息的监控键Monitoring Key。
可选地，所述PCRF指示所述PCEF去激活用于监控所述第四用量信息的所述第一监控键Monitoring Key包括：所述PCRF向所述PCEF发送去激活所述第一Monitoring Key的指示或用第二Monitoring key替换所述第一Monitoring Key的指示。
根据本发明的另一方面，提供了一种用量信息确定装置，所述装置应用于策略与计费执行功能实体PCEF中，包括：第一发送模块，设置为将可计费主体发生变化之前的第一用量信息发送给第三方应用的服务器，其中，所述第一用量信息为可计费主体变化之前用户设备UE访问所述第三方应用的用量信息，所述第一用量信息用于所述第三方应用的服务器确定第二用量信息，所述第二用量信息为所述第三方应用的提供商为所述UE支付的用于所述UE访问所述第三方应用的用量信息。
可选地，所述第一用量信息包括可计费主体变化之前所述UE访问所述第三方应用的流量和/或时长的信息；所述第二用量信息包括所述第三方应用的提供商为所述UE支付的用于所述UE访问所述第三方应用的流量和/或时长的信息。
可选地，若变化之前的可计费主体是所述UE，则所述第二用量信息为第三用量信息减去所述第一用量信息，所述第三用量信息为所述第三方应用的服务器统计的所述UE在可计费主体变化之前和变化之后访问所述第三方应用的总用量；若变化之前的可计费主体是所述第三方应用的提供商，则所述第二用量信息为所述第一用量信息。
可选地，所述装置还包括：第一确定模块，设置为确定用于计量所述第一用量信息的用量计量方法，其中，所述PCEF和所述第三方应用的服务器采用相同的用量计量方法；第一计量模块，设置为根据确定的用量计量方法计量所述第一用量信息。
可选地，所述第一确定模块包括：第一接收单元，设置为接收策略和计费规则功 能PCRF发送的策略和计费控制PCC规则，其中，所述PCC规则中携带所述用量计量方法的指示信息，所述PCRF根据所述第三方应用的提供商确定与所述第三方应用的服务器相同的用量计量方法。
可选地，所述第三方应用的服务器向所述PCRF提供所述第三方应用的服务器采用的用量计量方法的指示信息，所述PCRF根据所述第三方应用的服务器提供的用量计量方法的指示信息确定所述PCEF采用的用量计量方法。
可选地，所述第一计量模块包括以下至少之一：所述PCEF根据确定的用量计量方法通过由所述PCEF统计的方式确定第一用量信息；所述PCEF根据确定的用量计量方法通过由所述PCEF与在线计费系统OCS进行交互的方式确定所述第一用量信息；所述PCEF根据确定的用量计量方法通过由所述PCEF与离线计费系统OFCS进行交互的方式确定所述第一用量信息。
可选地，所述第一发送模块包括以下至少之一：第一发送单元，设置为将所述第一用量信息发送给策略和计费规则功能PCRF，所述PCRF将所述第一用量信息发送给应用功能AF，所述AF将所述第一用量信息上报给所述第三方应用的服务器；第二发送单元，用于将所述第一用量信息发送给策略和计费规则功能PCRF，所述PCRF通过协议转换器PC、应用接入控制AAC或业务能力开发功能SCEF将所述第一用量信息发送给应用功能AF，所述AF将所述第一用量信息上报给所述第三方应用的服务器。
根据本发明的另一方面，提供了一种用量信息发送装置，所述装置应用于策略与计费执行功能实体PCEF中，包括：第二发送模块，设置为将可计费主体发生变化之前的第一用量信息发送给应用功能AF，其中，所述第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息。
可选地，所述第一用量信息包括访问所述第三方应用的时间和/或流量。
可选地，所述第二发送模块包括以下至少之一：第三发送单元，设置为将所述第一用量信息发送给策略和计费规则功能PCRF，所述PCRF将所述第一用量信息发送给所述AF；第四发送单元，设置为将所述第一用量信息发送给策略和计费规则功能PCRF，所述PCRF通过协议转换器PC、应用接入控制AAC或业务能力开发功能SCEF将所述第一用量信息发送给所述AF。
根据本发明的另一方面，提供了一种用量信息确定装置，所述装置应用于第三方应用的服务器中，包括：第一接收模块，设置为接收策略与计费执行功能实体PCEF发送的第一用量信息，其中，所述第一用量信息为可计费主体变化之前用户设备UE访问所述第三方应用的用量信息；第二确定模块，设置为根据所述第一用量信息确定 第二用量信息，其中，所述第二用量信息为所述第三方应用的提供商为所述UE支付的用于所述UE访问所述第三方应用的用量信息。
可选地，所述第一用量信息包括可计费主体变化之前所述UE访问所述第三方应用的流量和/或时长的信息；所述第二用量信息包括所述第三方应用的提供商为所述UE支付的用于所述UE访问所述第三方应用的流量和/或时长的信息。
可选地，所述第二确定模块包括：若变化之前的可计费主体是所述UE，所述第三方应用的服务器通过将第三用量信息减去所述第一用量信息得到所述第二用量信息，其中，所述第三用量信息为所述第三方应用的服务器统计的所述UE在可计费主体变化之前和变化之后访问所述第三方应用的总用量；若变化之前的可计费主体是所述第三方应用的提供商，所述第三方应用的服务器将所述第一用量信息确定为所述第二用量信息。
可选地，所述装置还包括：第三确定模块，设置为确定用于计量所述第三用量信息的用量计量方法；第二计量模块，设置为根据确定的用量计量方法计量所述第三用量信息。
可选地，所述第三确定模块包括以下至少之一：第一确定单元，设置为通过与所述第三方应用的运营商签约协议的方式确定所述用量计量方法；第二确定单元，设置为通过与所述第三方应用的运营商进行动态协商的方式确定所述用量计量方法。
根据本发明的另一方面，提供了一种用量信息接收装置，所述装置应用于应用功能AF中，包括：第二接收模块，设置为接收策略与计费执行功能实体PCEF发送的可计费主体发生变化之前的第一用量信息，其中，所述第一用量信息为可计费主体变化之前用户设备UE访问所述第三方应用的用量信息。
可选地，所述第一用量信息包括访问所述第三方应用的时间和/或流量。
可选地，所述第二接收模块包括：第二接收单元，设置为通过策略和计费规则功能PCRF接收所述PCEF发送的所述第一用量信息。
根据本发明的另一方面，提供了一种用量信息发送装置，应用于策略与计费规则功能实体PCRF中，包括：第三发送模块，设置为在接收应用功能AF发送的用于指示改变可计费主体的第一指示后，向策略与计费执行功能实体PCEF发送用于指示所述PCEF上报可计费主体发生变化之前的第四用量信息的第二指示，其中，所述第四用量信息包括可计费主体变化之前所述PCEF还未向所述PCRF上报的用户设备UE访问第三方应用的累计用量信息；第四发送模块，设置为在接收到所述第四用量信息后，向所述AF发送第五用量信息，其中，所述第五用量信息包括可计费主体变化之前所述UE访问第三方应用的累计用量信息。
可选地，所述第五用量信息的取值为所述第四用量信息的取值，或者，所述第五用量信息为所述第四用量信息与所述PCEF之前上报的所述UE访问第三方应用的累计用量信息的和。
可选地，所述第四用量信息包括所述UE访问所述第三方应用的流量和/或时长的信息。
可选地，所述装置还包括指示模块，应用于所述PCRF中，设置为在接收所述AF发送的用于指示改变可计费主体的所述第一指示后，指示所述PCEF去激活用于监控所述第四用量信息的监控键Monitoring Key。
可选地，在指示所述PCEF去激活用于监控所述第一用量信息的所述第一监控键Monitoring Key时，所述指示模块包括：指示单元，设置为向所述PCEF发送去激活所述第一Monitoring Key的指示或用第二Monitoring key替换所述第一Monitoring Key的指示。
本发明另一实施例提供了一种计算机存储介质，所述计算机存储介质存储有执行指令，所述执行指令用于执行上述实施例中的方法。
通过本发明，采用策略与计费执行功能实体PCEF将可计费主体发生变化之前的第一用量信息发送给第三方应用的服务器，其中，所述第一用量信息为可计费主体变化之前用户设备UE访问所述第三方应用的用量信息，所述第一用量信息用于所述第三方应用的服务器确定第二用量信息，所述第二用量信息为所述第三方应用的提供商为所述UE支付的用于所述UE访问所述第三方应用的用量信息，解决了相关技术中存在的计费误差的问题，进而达到了减小计费误差的效果。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1为相关技术的Rel-8 PCC非漫游架构的示意图一；
图2是相关技术中的Rel-8 PCC非漫游架构的示意图二；
图3是根据本发明实施例的第一种用量信息确定方法的流程图；
图4是根据本发明实施例的用量信息发送方法的流程图；
图5是根据本发明实施例的第二种用量信息确定方法的流程图；
图6是根据本发明实施例的用量信息接收方法的流程图；
图7是根据本发明实施例的第一种用量信息确定装置的结构框图；
图8是根据本发明实施例的第一种用量信息确定装置的优选结构框图；
图9是根据本发明实施例的第一种用量信息确定装置中第一确定模块82的结构框图；
图10是根据本发明实施例的第一种用量信息确定装置中第一发送模块72的结构框图；
图11是根据本发明实施例的用量信息发送装置的结构框图；
图12是根据本发明实施例的用量信息发送装置中第二发送模块112的结构框图；
图13是根据本发明实施例的第二种用量信息确定装置的结构框图；
图14是根据本发明实施例的第二种用量信息确定装置的优选结构框图；
图15是根据本发明实施例的第二种用量信息确定装置中第三确定模块142的结构框图；
图16是根据本发明实施例的用量信息接收装置的结构框图；
图17是根据本发明实施例的用量信息确定装置中第二接收模块162的结构框图；
图18是根据本发明实施例一的用量上报流程图；
图19是根据本发明实施例二的用量上报流程图；
图20是根据本发明实施例三的用量上报流程图；
图21是根据本发明实施例四的用量上报流程图；
图22是根据本发明实施例五的用量上报流程图；
图23是根据本发明实施例六的用量上报流程图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
在本实施例中提供了一种用量信息确定方法，图3是根据本发明实施例的第一种用量信息确定方法的流程图，如图3所示，该流程包括如下步骤：
步骤S302，策略与计费执行功能实体PCEF将可计费主体发生变化之前的第一用量信息发送给第三方应用的服务器，其中，该第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息，该第一用量信息用于第三方应用的服务器确定第二用量信息，该第二用量信息为第三方应用的提供商为UE支付的用于UE访问第三方应用的用量信息。
上述的可计费主体可以是用户设备UE，也可以是第三方应用的提供商，可计费主体的变化可以使在二者之间进行的切换。通过上述步骤，在变更可计费主体时，将可计费主体发生变化之前的第一用量信息发送给第三方应用的服务器，从而使得该第三方服务器能够精确的计量出第三方应用的提供商应该为用户设备UE支付的用量信息，提高计费精度，从而解决了相关技术中存在的计费误差的问题，进而达到了减小计费误差的效果。
UE访问第三方应用时，可以是以访问的时间进行计费的，也可以是以消耗的流量进行计费的，还可以综合时间和流量进行计费，如，将流量费用划分为闲时的费用和忙时的费用。在一个可选的实施例中，上述第一用量信息包括可计费主体变化之前UE访问第三方应用的流量和/或时长的信息；上述第二用量信息包括第三方应用的提供商为UE支付的用于UE访问第三方应用的流量和/或时长的信息。
其中，若变化之前的可计费主体是UE，则该第二用量信息为第三用量信息减去第一用量信息，该第三用量信息为第三方应用的服务器统计的UE在可计费主体变化之前和变化之后访问第三方应用的总用量；若变化之前的可计费主体是第三方应用的提供商，则该第二用量信息为第一用量信息。
在一个可选的实施例中，上述的PCEF将可计费主体发生变化之前的第一用量信息发送给第三方应用的服务器之前，还包括：PCEF确定用于计量第一用量信息的用量计量方法，其中，该PCEF和第三方应用的服务器采用相同的用量计量方法；PCEF根据确定的用量计量方法计量该第一用量信息。
其中，上述的PCEF确定用于计量第一用量信息的用量计量方法包括：该PCEF接收策略和计费规则功能PCRF发送的策略和计费控制PCC规则，其中，PCC规则中携带用量计量方法的指示信息，该PCRF根据第三方应用的提供商确定与第三方应用的服务器相同的用量计量方法。
第三方应用的服务器向PCRF提供第三方应用的服务器采用的用量计量方法的指示信息，该PCRF根据上述第三方应用的服务器提供的用量计量方法的指示信息确定PCEF采用的用量计量方法。
在一个可选的实施例中，上述PCEF根据确定的用量计量方法计量第一用量信息 时，可以有多种确定方法，可以包括以下至少之一：PCEF根据确定的用量计量方法通过由PCEF统计的方式确定第一用量信息；PCEF根据确定的用量计量方法通过由PCEF与在线计费系统OCS进行交互的方式确定第一用量信息；PCEF根据确定的用量计量方法通过由PCEF与离线计费系统OFCS进行交互的方式确定第一用量信息。
在一个可选的实施例中，上述的PCEF将第一用量信息发送给第三方应用的服务器包括以下至少之一：PCEF将第一用量信息发送给策略和计费规则功能PCRF，该PCRF将第一用量信息发送给AF，该AF将第一用量信息上报给第三方应用的服务器；PCEF将第一用量信息发送给策略和计费规则功能PCRF，该PCRF通过协议转换器PC、应用接入控制AAC或业务能力开发功能SCEF将第一用量信息发送给AF，AF将第一用量信息上报给第三方应用的服务器。
图4是根据本发明实施例的用量信息发送方法的流程图，如图4所示，该方法包括如下步骤：
步骤S402，策略与计费执行功能实体PCEF将可计费主体发生变化之前的第一用量信息发送给应用功能AF，其中，该第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息。
通过上述步骤，当可计费主体发生变化时，PCEF将变化前的UE的用量信息发送给AF，从而可以明确可计费主体发生变化前，UE访问第三方应用的用量信息，从而为后续的计费做好了铺垫，提高计费精度。解决了相关技术中存在的计费误差的问题，进而达到了减小计费误差的效果。
UE访问第三方应用时，可以是以访问的时间进行计费的，也可以是以消耗的流量进行计费的，还可以综合时间和流量进行计费，如，将流量费用划分为闲时的费用和忙时的费用，在一个可选的实施例中，上述第一用量信息可以包括访问第三方应用的时间和/或流量。
其中，PCEF将第一用量信息发送给AF可以包括以下至少之一：PCEF将第一用量信息发送给策略和计费规则功能PCRF，该PCRF将第一用量信息发送给AF；PCEF将第一用量信息发送给策略和计费规则功能PCRF，该PCRF通过协议转换器PC、应用接入控制AAC或业务能力开发功能SCEF将第一用量信息发送给AF。
图5是根据本发明实施例的第二种用量信息确定方法的流程图，如图5所示，该流程包括如下步骤：
步骤S502，第三方应用的服务器接收策略与计费执行功能实体PCEF发送的第一用量信息，其中，该第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息；
步骤S504，该第三方应用的服务器根据第一用量信息确定第二用量信息，其中，第二用量信息为第三方应用的提供商为上述UE支付的用于UE访问第三方应用的用量信息。
上述的可计费主体可以是用户设备UE，也可以是第三方应用的提供商，可计费主体的变化可以使在二者之间进行的切换。通过上述步骤，在变更可计费主体时，将可计费主体发生变化之前的第一用量信息发送给第三方应用的服务器，从而使得该第三方服务器能够精确的计量出第三方应用的提供商应该为用户设备UE支付的用量信息，提高计费精度，从而解决了相关技术中存在的计费误差的问题，进而达到了减小计费误差的效果。
UE访问第三方应用时，可以是以访问的时间进行计费的，也可以是以消耗的流量进行计费的，还可以综合时间和流量进行计费，如，将流量费用划分为闲时的费用和忙时的费用。在一个可选的实施例中，上述第一用量信息包括可计费主体变化之前UE访问第三方应用的流量和/或时长的信息；第二用量信息包括第三方应用的提供商为UE支付的用于该UE访问第三方应用的流量和/或时长的信息。
在一个可选的实施例中，上述第三方应用的服务器根据第一用量信息确定第二用量信息包括：若变化之前的可计费主体是UE，第三方应用的服务器通过将第三用量信息减去第一用量信息得到第二用量信息，其中，该第三用量信息为第三方应用的服务器统计的UE在可计费主体变化之前和变化之后访问第三方应用的总用量；若变化之前的可计费主体是第三方应用的提供商，该第三方应用的服务器将第一用量信息确定为第二用量信息。
在一个可选的实施例中，上述第三方应用的服务器根据第一用量信息确定第二用量信息之前，还包括：第三方应用的服务器确定用于计量第三用量信息的用量计量方法；该第三方应用的服务器根据确定的用量计量方法计量第三用量信息。
其中，第三方应用的服务器确定用于计量第三用量信息的用量计量方法包括：该第三方应用的服务器通过与第三方应用的运营商签约协议的方式确定用量计量方法；该第三方应用的服务器通过与第三方应用的运营商进行动态协商的方式确定用量计量方法。
图6是根据本发明实施例的用量信息接收方法的流程图，如图6所示，该流程包括如下步骤：
步骤S602，应用功能AF接收策略与计费执行功能实体PCEF发送的可计费主体发生变化之前的第一用量信息，其中，该第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息。
通过上述步骤，当可计费主体发生变化时，PCEF将变化前的UE的用量信息发送给AF，从而可以明确可计费主体发生变化前，UE访问第三方应用的用量信息，从而为后续的计费做好了铺垫，提高计费精度。解决了相关技术中存在的计费误差的问题，进而达到了减小计费误差的效果。
UE访问第三方应用时，可以是以访问的时间进行计费的，也可以是以消耗的流量进行计费的，还可以综合时间和流量进行计费，如，将流量费用划分为闲时的费用和忙时的费用，在一个可选的实施例中，上述第一用量信息包括访问第三方应用的时间和/或流量。
在一个可选的实施例中，上述AF接收PCEF发送的第一用量信息包括：该AF通过策略和计费规则功能PCRF接收PCEF发送的第一用量信息。
在本发明实施例中，还提供了一种用量信息发送方法，该方法包括如下步骤：
步骤1，策略与计费规则功能实体PCRF在接收应用功能AF发送的用于指示改变可计费主体的第一指示后，向策略与计费执行功能实体PCEF发送用于指示PCEF上报可计费主体发生变化之前的第四用量信息的第二指示，其中，该第四用量信息包括可计费主体变化之前PCEF还未向PCRF上报的用户设备UE访问第三方应用的累计用量信息；
步骤2，上述PCRF在接收到第四用量信息后，向AF发送第五用量信息，其中，该第五用量信息包括可计费主体变化之前UE访问第三方应用的累计用量信息。
在一个可选的实施例中，上述第五用量信息的取值为第四用量信息的取值，或者，第五用量信息的取值为第四用量信息与PCEF之前上报的UE访问第三方应用的累计用量信息的和。
在一个可选的实施例中，上述第四用量信息包括UE访问第三方应用的流量和/或时长的信息。
在一个可选的实施例中，上述PCRF在接收AF发送的用于指示改变可计费主体的第一指示后，还包括：PCRF指示PCEF去激活用于监控第四用量信息的监控键Monitoring Key。
在一个可选的实施例中，上述PCRF指示PCEF去激活用于监控所述第四用量信息的所述第一监控键Monitoring Key包括：PCRF向PCEF发送去激活第一Monitoring Key的指示或用第二Monitoring key替换第一Monitoring Key的指示。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但 很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例的方法。
在本实施例中还提供了一种用量信息确定装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图7是根据本发明实施例的第一种用量信息确定装置的结构框图，该装置应用于策略与计费执行功能实体PCEF中，如图7所示，该装置包括第一发送模块72，下面对该装置进行说明。
第一发送模块72，设置为将可计费主体发生变化之前的第一用量信息发送给第三方应用的服务器，其中，该第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息，第一用量信息用于第三方应用的服务器确定第二用量信息，该第二用量信息为第三方应用的提供商为用户设备UE支付的用于UE访问第三方应用的用量信息。
其中，上述的第一用量信息包括可计费主体变化之前UE访问第三方应用的流量和/或时长的信息；上述第二用量信息包括第三方应用的提供商为UE支付的用于UE访问第三方应用的流量和/或时长的信息。
若变化之前的可计费主体是UE，则该第二用量信息为第三用量信息减去第一用量信息，第三用量信息为第三方应用的服务器统计的UE在可计费主体变化之前和变化之后访问第三方应用的总用量；若变化之前的可计费主体是第三方应用的提供商，则该第二用量信息为第一用量信息。
图8是根据本发明实施例的第一种用量信息确定装置的优选结构框图，如图8所示，该装置除包括图7所示的模块外，还包括第一确定模块82和第一计量模块84，下面对该装置进行说明。
第一确定模块82，设置为确定用于计量第一用量信息的用量计量方法，其中，该PCEF和第三方应用的服务器采用相同的用量计量方法；第一计量模块84，连接至上述第一确定模块82和第一发送模块72，设置为根据确定的用量计量方法计量第一用量信息。
图9是根据本发明实施例的第一种用量信息确定装置中第一确定模块82的结构框 图，如图9所示，该第一确定模块82包括第一接收单元92，下面对该第一确定模块82进行说明：
第一接收单元92，设置为接收策略和计费规则功能PCRF发送的策略和计费控制PCC规则，其中，该PCC规则中携带用量计量方法的指示信息，PCRF根据第三方应用的提供商确定与第三方应用的服务器相同的用量计量方法。
其中，上述第三方应用的服务器向PCRF提供第三方应用的服务器采用的用量计量方法的指示信息，PCRF根据第三方应用的服务器提供的用量计量方法的指示信息确定PCEF采用的用量计量方法。
在一个可选的实施例中，上述第一计量模块84包括以下至少之一：PCEF根据确定的用量计量方法通过由PCEF统计的方式确定第一用量信息；PCEF根据确定的用量计量方法通过由PCEF与在线计费系统OCS进行交互的方式确定第一用量信息；PCEF根据确定的用量计量方法通过由PCEF与离线计费系统OFCS进行交互的方式确定第一用量信息。
图10是根据本发明实施例的第一种用量信息确定装置中第一发送模块72的结构框图，如图10所示，该第一发送模块72包括第一发送单元102和/或第二发送单元104，下面对该第一发送模块72进行说明。
第一发送单元102，设置为将第一用量信息发送给策略和计费规则功能PCRF，该PCRF将第一用量信息发送给AF，AF将第一用量信息上报给第三方应用的服务器；第二发送单元104，设置为将第一用量信息发送给策略和计费规则功能PCRF，该PCRF通过协议转换器PC、应用接入控制AAC或业务能力开发功能SCEF将第一用量信息发送给AF，该AF将第一用量信息上报给第三方应用的服务器。
图11是根据本发明实施例的用量信息发送装置的结构框图，该装置应用于策略与计费执行功能实体PCEF中，如图11所示，该用量信息发送装置包括第二发送模块112，下面对该装置进行说明。
第二发送模块112，设置为将可计费主体发生变化之前的第一用量信息发送给应用功能AF，其中，该第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息。
其中，上述第一用量信息包括访问第三方应用的时间和/或流量。
图12是根据本发明实施例的用量信息发送装置中第二发送模块112的结构框图，如图12所示，该第二发送模块112包括第三发送单元122和/或第四发送单元124，下面对该第二发送模块112进行说明。
第三发送单元122，设置为将第一用量信息发送给策略和计费规则功能PCRF，该PCRF将第一用量信息发送给AF；第四发送单元124，设置为将第一用量信息发送给策略和计费规则功能PCRF，该PCRF通过协议转换器PC、应用接入控制AAC或业务能力开发功能SCEF将第一用量信息发送给AF。
图13是根据本发明实施例的第二种用量信息确定装置的结构框图，该装置应用于第三方应用的服务器中，包括第一接收模块132和第二确定模块134，下面对该装置进行说明。
第一接收模块132，设置为接收策略与计费执行功能实体PCEF发送的第一用量信息，其中，该第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息；第二确定模块134，连接至上述第一接收模块132，设置为根据第一用量信息确定第二用量信息，其中，该第二用量信息为第三方应用的提供商为上述UE支付的用于该UE访问第三方应用的用量信息。
其中，上述的第一用量信息包括可计费主体变化之前UE访问第三方应用的流量和/或时长的信息；该第二用量信息包括第三方应用的提供商为UE支付的用于UE访问第三方应用的流量和/或时长的信息。
在一个可选的实施例中，第二确定模块134包括：若变化之前的可计费主体是UE，第三方应用的服务器通过将第三用量信息减去第一用量信息得到第二用量信息，其中，该第三用量信息为第三方应用的服务器统计的UE在可计费主体变化之前和变化之后访问第三方应用的总用量；若变化之前的可计费主体是第三方应用的提供商，该第三方应用的服务器将第一用量信息确定为第二用量信息。
图14是根据本发明实施例的第二种用量信息确定装置的优选结构框图，如图14所示，该装置除包括图13所示的所有模块外，还包括第三确定模块142和第二计量模块144，下面对该装置进行说明。
第三确定模块142，设置为确定用于计量第三用量信息的用量计量方法；第二计量模块144，连接至上述第三确定模块142和第一接收模块132，设置为根据确定的用量计量方法计量第三用量信息。
图15是根据本发明实施例的第二种用量信息确定装置中第三确定模块142的结构框图，如图15所示，该第三确定模块142包括第一确定单元152和/或第二确定单元154，下面对该第三确定模块142进行说明。
第一确定单元152，设置为通过与第三方应用的运营商签约协议的方式确定用量计量方法；第二确定单元154，设置为通过与第三方应用的运营商进行动态协商的方式确定用量计量方法。
图16是根据本发明实施例的用量信息接收装置的结构框图，该装置应用于应用功能AF中，如图16所示，该装置包括第二接收模块162，下面对该装置进行说明。
第二接收模块162，设置为接收策略与计费执行功能实体PCEF发送的可计费主体发生变化之前的第一用量信息，其中，该第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息。
其中，上述的第一用量信息包括访问第三方应用的时间和/或流量。
图17是根据本发明实施例的用量信息确定装置中第二接收模块162的结构框图，如图17所示，第二接收模块162包括第二接收单元172，下面对该第二接收模块162进行说明。
第二接收单元172，设置为通过策略和计费规则功能PCRF接收PCEF发送的第一用量信息。
在一个可选的实施例中，还提供了一种用量信息发送装置，应用于策略与计费规则功能实体PCRF中，该装置包括第三发送模块和第四发送模块，下面对该装置进行说明：
第三发送模块，设置为在接收应用功能AF发送的用于指示改变可计费主体的第一指示后，向策略与计费执行功能实体PCEF发送用于指示PCEF上报可计费主体发生变化之前的第四用量信息的第二指示，其中，该第四用量信息包括可计费主体变化之前PCEF还未向PCRF上报的用户设备UE访问第三方应用的累计用量信息；第四发送模块，设置为在接收到上述第四用量信息后，向AF发送第五用量信息，其中，该第五用量信息包括可计费主体变化之前UE访问第三方应用的累计用量信息。
在一个可选的实施例中，上述第五用量信息的取值为第四用量信息的取值，或者，上述第五用量信息为第四用量信息与PCEF之前上报的UE访问第三方应用的累计用量信息的和。
在一个可选的实施例中，上述第四用量信息包括UE访问第三方应用的流量和/或时长的信息。
在一个可选的实施例中，上述装置还包括指示模块，应用于PCRF中，设置为在接收所述AF发送的用于指示改变可计费主体的所述第一指示后，指示PCEF去激活用于监控第四用量信息的监控键Monitoring Key。
在一个可选的实施例中，在指示PCEF去激活用于监控第一用量信息的第一监控键Monitoring Key时，上述指示模块包括：指示单元，设置为向PCEF发送去激活第一Monitoring Key的指示或用第二Monitoring key替换第一Monitoring Key的指示。
下面结合具体实施例对本发明进行说明：
实施例一
本实施例描述在在发起业务时，可计费主体为用户设备UE，在业务访问过程中，可计费主体变为第三方应用的提供商的流程。
图18是根据本发明实施例一的用量上报流程图，如图18所示，该流程包括如下步骤：
步骤S1802：UE附着到网络，建立IP-CAN会话。在这个过程中，PCEF与PCRF之间建立用于策略和计费控制的Gx会话。若IP-CAN会话涉及BBERF，则BBERF与PCRF之间建立用于策略控制的网关控制会话。
步骤S1804：UE与第三方应用服务器交互，发起业务访问。在业务访问的过程中，第三方应用服务器会对UE的业务访问计费，统计(Accounting)(也称计量，Metering)UE访问的用量信息(Usage Information)，用量信息可以是流量和/或时长。
步骤S1806：第三方应用服务器与AF之间执行特定的交互流程，向应用服务器或AF提供用户请求的业务信息。
步骤S1808：AF向PCRF发送Diameter AAR消息，携带业务信息。
步骤S1810：PCRF向AF返回确认消息。
步骤S1812：PCRF根据业务信息、网络策略以及用户签约等信息制定PCC规则。若BBERF存在，则PCRF还根据PCC规则制定QoS规则。
步骤S1814：PCRF向BBERF提供QoS规则。
步骤S1816：PCRF向PCEF提供PCC规则。PCEF执行PCC规则，并根据PCC规则中的计费策略对UE访问的第三方业务进行计费，统计(也称计量)UE访问业务产生的用量信息。用量信息可以是流量和/或时长。该计费是针对UE进行计费的。
步骤S1818：在UE访问第三方业务的过程中，第三方应用决定赞助UE正在访问的第三方业务，应用服务器与AF交互，向AF发送赞助业务的指示，以及赞助商标识，应用提供商标识。
步骤S1820：AF向PCRF发送AAR消息，消息中携带被赞助数据连接信息，包括赞助商标识、应用提供商标识。
步骤S1822：PCRF保存信息后，返回确认消息；
步骤S1824：PCRF根据业务信息、网络策略以及用户签约等信息进行策略决策， 更新之前制定的PCC规则。PCRF根据赞助商标识和应用提供商标识确认相应的计费键(Charging key)和/或PCRF在PCC规则中增加赞助商标识和应用提供商标识。
步骤S1826：PCRF向PCEF提供PCC规则。
步骤S1828：PCEF向PCRF返回确认消息，并在消息中携带UE本次业务访问中，在可计费主体发生切换前的累计用量信息(该用量可以是流量和/或时长)。PCEF可以自己统计(也称计量)UE发起本次业务以来的累计用量信息，也可以通过与计费系统(OCS或OFCS)交互获取UE发起本次业务以来的累计用量信息。
步骤S1830：PCRF向AF发送RAR消息，消息中携带累计用量信息。
步骤S1832：AF返回确认消息。
步骤S1834：AF与第三方应用服务器的特定消息，譬如将累计用量信息上报给第三方应用服务器。
AF和第三方应用服务器从实现上可以是独立部署，AF也可以集成在第三方应用服务器上。不管哪种部署，从PCRF角度，PCRF与AF的互通也可以认为是PCRF与第三方应用服务器的互通。
实施例二
本实施例描述了在存在PC/AAC/SCEF的场景下，在发起业务时，可计费主体为用户设备UE，在业务访问过程中，变为第三方应用提供商的流程。
图19是根据本发明实施例二的用量上报流程图，如图19所示，该流程包括如下步骤：
步骤S1902：UE附着到网络，建立IP-CAN会话。在这个过程中，PCEF与PCRF之间建立用于策略和计费控制的Gx会话。若IP-CAN会话涉及BBERF，则BBERF与PCRF之间建立用于策略控制的网关控制会话。
步骤S1904：UE与第三方应用服务器交互，发起业务访问。在业务访问的过程中，第三方应用服务器会对UE的业务访问计费，统计(也称计量)UE访问的用量信息，其中用量信息可以是流量和/或时长。
步骤S1906：第三方应用服务器与AF之间执行特定的交互流程，第三方应用服务器向AF提供用户请求的业务信息。
步骤S1908：AF向PC/AAC/SCEF发送HTTP POST，消息中携带业务信息。
步骤S1910：PC/AAC/SCEF向PCRF发送Diameter AAR消息，携带业务信息。
步骤S1912：PCRF向AF返回确认消息。
步骤S1914：PC/AAC/SCEF向AF返回确认消息。
步骤S1916：PCRF根据业务信息、网络策略以及用户签约等信息制定PCC规则。若BBERF存在，则PCRF还根据PCC规则制定QoS规则。
步骤S1918：PCRF向BBERF提供QoS规则。
步骤S1920：PCRF向PCEF提供PCC规则。PCEF执行PCC规则，并根据PCC规则中的计费策略对UE访问的第三方业务进行统计(也称计量)UE访问业务产生的用量信息。用量信息可以是流量和/或时长。该计费是针对用户进行计费的(可计费主体是UE)。
步骤S1922：在UE访问第三方业务的过程中，第三方应用决定赞助UE正在访问的第三方业务，第三方应用服务器与AF交互，向AF发送赞助业务的指示，以及赞助商标识，应用提供商标识。
步骤S1924：AF向PC/AAC/SCEF发送HTTP PUT消息，消息中携带被赞助数据连接信息，包括赞助商标识、应用提供商标识。
步骤S1926：PC/AAC/SCEF向PCRF发送AAR消息，消息中携带被赞助数据连接信息，包括赞助商标识、应用提供商标识。
步骤S1928：PCRF保存信息后，向PC/AAC返回确认消息。
步骤S1930：PC/AAC/SCEF向AF返回确认消息。
步骤S1932：PCRF根据业务信息、网络策略以及用户签约等信息进行策略决策，更新之前制定的PCC规则。PCRF根据赞助商标识和应用提供商标识确认相应的计费键(Charging key)和/或PCRF在PCC规则中增加赞助商标识和应用提供商标识。
步骤S1934：PCRF向PCEF提供PCC规则。
步骤S1936：PCEF向PCRF返回确认消息，并在消息中携带UE本次业务访问中，在可计费主体发生切换前的累计用量信息(该用量可以是流量和/或时长)。PCEF可以自己统计(也称计量)UE发起本次业务以来的累计用量，也可以通过与计费系统(OCS或OFCS)交互获取UE发起本次业务以来的累计用量信息。
步骤S1938：PCRF向PC/AAC发送RAR消息，消息中携带累计用量信息。
步骤S1940：PC/AAC向AF发送HTTP PUT消息，消息中携带累计用量信息。
步骤S1942：AF向PC/AAC返回确认消息。
步骤S1944：PC/AAC向PCRF返回确认消息。
步骤S1946：AF与第三方应用服务器的特定消息，譬如向累计用量信息上报给应用服务器。
通过实施例一和实施例二的流程，第三方应用提供商获得了网关在执行变更可计费主体策略之前，用户(同上述的UE)访问第三方数据应用产生的累计用量信息。这部分累计用量信息是由用户承担的。同时第三方数据应用自身也会统计用户访问第三方数据的用量信息。这样，第三方数据应用提供商就可以比较精确的获知其真正赞助的第三方数据应用的累计用量信息了。若到UE结束业务访问时，可计费主体始终是第三方应用，那么第三方应用提供商赞助的用量为第三方数据应用自身统计的用户访问第三方数据的用量减去网关上报的可计费主体变更前用户承担的累计用量信息。
AF和第三方应用服务器从实现上可以是独立部署，也可以AF集成在第三方应用服务器上。不管哪种部署，从PC/AAC/SCEF角度，PCRFPC/AAC/SCEF与AF的互通也可以认为是PC/AAC/SCEF与第三方应用服务器的互通。
实施例三
本实施例描述在在发起业务时，可计费主体为第三方应用提供商，在业务访问过程中，变为UE的流程。
图20是根据本发明实施例三的用量上报流程图，如图20所示，该流程包括如下步骤：
步骤S2002：UE附着到网络，建立IP-CAN会话。在这个过程中，PCEF与PCRF之间建立用于策略和计费控制的Gx会话。若IP-CAN会话涉及BBERF，则BBERF与PCRF之间建立用于策略控制的网关控制会话。
步骤S2004：UE与第三方应用服务器交互，发起业务访问。在业务访问的过程中，第三方应用服务器会对UE的业务访问计费，统计(也称计量)UE访问的用量信息，其中用量信息可以是流量和/或时长。
步骤S2006：第三方应用服务器与AF之间执行特定的交互流程，向应用服务器向AF提供用户请求的业务信息，其中第三方应用决定赞助用户访问的数据应用，第三方应用服务器向AF提供赞助业务的指示，以及赞助商标识，应用提供商标识。
步骤S2008：AF向PCRF发送Diameter AAR消息，携带业务信息，被赞助数据 连接信息，包括赞助商标识，应用提供商标识。
步骤S2010：PCRF向AF返回确认消息。
步骤S2012：PCRF根据业务信息、网络策略以及用户签约等信息制定PCC规则。PCRF根据赞助商标识和应用提供商标识确认相应的计费键(Charging key)和/或PCRF在PCC规则中增加赞助商标识和应用提供商标识。若BBERF存在，则PCRF还根据PCC规则制定QoS规则。
步骤S2014：PCRF向BBERF提供QoS规则。
步骤S2016：PCRF向PCEF提供PCC规则。PCEF执行PCC规则，并根据PCC规则中的计费策略对UE访问的第三方业务进行计费，统计(也称计量)UE访问业务产生的用量信息。用量信息可以是流量和/或时长。该计费是针对第三方应用提供商进行计费的。
步骤S2018：在UE访问第三方业务的过程中，第三方应用决定取消赞助UE正在访问的第三方业务，第三方应用服务器与AF交互，向AF发送取消赞助的指示。
步骤S2020：AF向PCRF发送AAR消息，消息中携带被取消赞助指示。
步骤S2022：PCRF保存信息后，返回确认消息。
步骤S2024：PCRF根据业务信息、网络策略以及用户签约等信息进行策略决策，更新之前制定的PCC规则，携带取消赞助指示。PCRF在PCC规则携带其他可以对用户进行计费的计费键。
步骤S2026：PCRF向PCEF提供PCC规则。
步骤S2028：PCEF向PCRF返回确认消息，并在消息中携带UE本次业务访问中，在可计费主体发生切换前的累计用量信息(该用量可以是流量和/或时长)。PCEF可以自己统计(也称计量)UE发起本次业务以来的累计用量信息，也可以通过与计费系统(OCS或OFCS)交互获取UE发起本次业务以来的累计用量信息。
步骤S2030：PCRF向AF发送RAR消息，消息中携带累计用量信息。
步骤S2032：AF返回确认消息。
步骤S2034：AF与第三方应用服务器的特定消息，譬如向累计用量上报给应用服务器。
AF和第三方应用服务器从实现上可以是独立部署，也可以AF集成在第三方应用服务器上。不管哪种部署，从PCRF角度，PCRF与AF的互通也可以认为是PCRF与 第三方应用服务器的互通。
实施例四
本实施例描述在在发起业务时，可计费主体为第三方应用提供商，在业务访问过程中，变为UE的流程。
图21是根据本发明实施例四的用量上报流程图，如图21所示，该流程包括如下步骤：
步骤S2102：UE附着到网络，建立IP-CAN会话。在这个过程中，PCEF与PCRF之间建立用于策略和计费控制的Gx会话。若IP-CAN会话涉及BBERF，则BBERF与PCRF之间建立用于策略控制的网关控制会话。
步骤S2104：UE与第三方应用服务器交互，发起业务访问。在业务访问的过程中，第三方应用服务器会对UE的业务访问计费，统计(也称计量)UE访问的流量和/或时长。
步骤S2106：第三方应用服务器与AF之间执行特定的交互流程，向应用服务器向AF提供用户请求的业务信息，其中第三方应用决定赞助用户访问的数据应用，第三方应用服务器向AF提供赞助业务的指示，以及赞助商标识，应用提供商标识。
步骤S2108：AF向PC/AAC/SCEF发送HTTP POST消息，消息中携带业务信息，被赞助数据连接信息，包括赞助商标识，应用提供商标识。
步骤S2110：PC/AAC/SCEF向PCRF发送AAR消息，消息中携带业务信息，被赞助数据连接信息，包括赞助商标识，应用提供商标识。
步骤S2112：PCRF向PC/AAC/SCEF返回确认消息。
步骤S2114：PC/AACSCEF向AF返回确认消息。
步骤S2116：PCRF根据业务信息、网络策略以及用户签约等信息制定PCC规则。PCRF根据赞助商标识和应用提供商标识确认相应的计费键(Charging key)和/或PCRF在PCC规则中增加赞助商标识和应用提供商标识。若BBERF存在，则PCRF还根据PCC规则制定QoS规则。
步骤S2118：PCRF向BBERF提供QoS规则。
步骤S2120：PCRF向PCEF提供PCC规则。PCEF执行PCC规则，并根据PCC规则中的计费策略对UE访问的第三方业务进行计费，统计(也称计量)UE访问业务 产生的用量信息。用量信息可以是流量和/或时长。该计费是针对第三方应用提供商进行计费的。
步骤S2122：在UE访问第三方业务的过程中，第三方应用决定取消赞助UE正在访问的第三方业务，第三方应用服务器与AF交互，向AF发送取消赞助的指示。
步骤S2124：AF向PC/AAC/SCEF发送HTTP PUT消息，消息中携带被取消赞助指示。
步骤S2126：PC/AAC/SCEF向PCRF发送AAR消息，消息中携带被取消赞助指示。
步骤S2128：PCRF保存信息后，向PC/AAC返回确认消息。
步骤S2130：PC/AAC/SCEF向AF返回确认消息。
步骤S2132：PCRF根据业务信息、网络策略以及用户签约等信息进行策略决策，更新之前制定的PCC规则，携带取消赞助指示。PCRF在PCC规则携带其他可以对用户进行计费的计费键。
步骤S2134：PCRF向PCEF提供PCC规则。
步骤S2136：PCEF向PCRF返回确认消息，并在消息中携带UE本次业务访问中，在可计费主体发生切换前的累计用量信息(该用量信息可以是流量和/或时长)。PCEF可以自己统计(也称计量)UE发起本次业务以来的累计用量信息，也可以通过与计费系统(OCS或OFCS)交互获取UE发起本次业务以来的累计用量信息。
步骤S2138：PCRF向PC/AAC发送RAR消息，消息中携带累计用量信息。
步骤S2140：PC/AAC向AF发送RAR消息，消息中携带累计用量信息。
步骤S2142：AF向PC/AAC返回确认消息。
步骤S2144：PC/AAC向PCRF返回确认消息。
步骤S2146：AF与第三方应用服务器的特定消息，譬如向累计用量信息上报给第三方应用服务器。
通过实施例三和实施例四的流程，第三方应用提供商获得了网关在执行变更可计费主体策略之前，第三方应用提供商赞助的用量信息。若到UE结束业务访问时，可计费主体始终是UE，那么第三方应用提供商赞助的用量网关上报的可计费主体变更前第三方应用提供商赞助的累计用量信息。
AF和第三方应用服务器从实现上可以是独立部署，也可以AF集成在第三方应用 服务器上。不管哪种部署，从PCRFPC/AAC/SCEF角度，PC/AAC/SCEF与AF的互通也可以认为是PC/AAC/SCEF与第三方应用服务器的互通。
实施例五
本实施例描述在在发起业务时，可计费主体为用户设备UE，在业务访问过程中，可计费主体变为第三方应用的提供商的流程。
图22是根据本发明实施例五的用量上报流程图，如图22所示，该流程包括如下步骤：
步骤S2202：UE附着到网络，建立IP-CAN会话。在这个过程中，PCEF与PCRF之间建立用于策略和计费控制的Gx会话。若IP-CAN会话涉及BBERF，则BBERF与PCRF之间建立用于策略控制的网关控制会话。
步骤S2204：UE与第三方应用服务器交互，发起业务访问。在业务访问的过程中，第三方应用服务器会对UE的业务访问计费，统计(Accounting)(也称计量，Metering)UE访问的用量信息(Usage Information)，用量信息可以是流量和/或时长。
步骤S2206：第三方应用服务器与AF之间执行特定的交互流程，向应用服务器或AF提供用户请求的业务信息和不激活被赞助数据连接的指示(即不赞助业务的指示)。
步骤S2208：AF向PCRF发送Diameter AAR消息，携带业务信息、赞助商标识、应用提供商标识和不激活被赞助数据连接的指示。
步骤S2210：PCRF向AF返回确认消息。
步骤S2212：PCRF根据业务信息、网络策略以及用户签约等信息制定PCC规则。若BBERF存在，则PCRF还根据PCC规则制定QoS规则。由于PCRF和AF支持均支持改变可计费主体，或PCRF接收到了不激活被赞助数据连接的指示或根据用户签约或运营商策略，PCRF决定激活用量监控。PCRF在PCC规则中携带监控键Monitoring key1(Monitoring Key1根据赞助商标识设置)。
步骤S2214：PCRF向BBERF提供QoS规则。
步骤S2216：PCRF向PCEF提供PCC规则，并携带对应的用量阈值(用量阈值可以是流量或时长)。PCEF执行PCC规则，并根据PCC规则对对应的业务数据进行用量监控。当累计用量到达用量阈值时，PCEF向PCRF报告累计用量(该累计用量等于用量阈值)，PCRF再下发新的用量阈值。同时PCRF根据每一次报告的累计用量计算UE访问第三方应用的总的累计用量。
步骤S2218：在UE访问第三方业务的过程中，第三方应用决定赞助UE正在访问的第三方业务，应用服务器与AF交互，向AF发送赞助业务的指示(即激活被赞助数据连接的指示)，以及赞助商标识，应用提供商标识、以及可选的赞助用量阈值。
步骤S2220：AF向PCRF发送AAR消息，消息中携带被赞助数据连接信息，包括赞助商标识、应用提供商标识、激活被赞助数据连接的指示、可选的赞助用量阈值。
步骤S2222：PCRF保存信息后，返回确认消息。
步骤S2224：PCRF根据业务信息、网络策略以及用户签约等信息进行策略决策，更新之前制定的PCC规则。PCRF根据赞助商标识和应用提供商标识确认相应的计费键(Charging key)和/或PCRF在PCC规则中增加赞助商标识和应用提供商标识。此外，PCRF决定去激活针对Monitoring Key1用量监控。若AF提供了赞助用量阈值，则PCRF根据赞助商标识设置监控键Monitoring Key2，并在更新PCC规则中携带Monitoring Key2(即用Monitoring Key2替换Monitoring Key1)。同时PCRF向PCEF提供Monitoring Key2对应的用量阈值(该用量阈值根据AF提供的赞助用量阈值设置。
步骤S2226：PCRF向PCEF提供更新PCC规则，携带去激活针对Monitoring Key1用量监控的指示。若PCRF分配了Monitoring key2，则PCRF还向PCEF提供对应的用量阈值。为了去激活Monitoring key1的用量监控，PCRF可以只下发去激活Monitoring key1的用量监控的指示，或只将Monitoring key2替换为Monitoring key1，或同时下发去激活Monitoring key1的用量监控的指示，并将Monitoring key2替换为Monitoring key1。
步骤S2228：PCEF向PCRF返回确认消息。由于针对Monitoring Key1的用量监控被去激活，因此PCEF在应答消息中携带PCEF之前还未向PCRF上报的Monitoring Key1的累计用量。PCRF接收到本次PCEF上报的累计用量后再和之前保存的总的累计用量相加，获得第三方应用在改变计费主体前，UE访问第三方应用的累计用量信息。若之前PCEF没有上报过Monitoring Key1的累计用量，那么PCEF本次上报的累计用量即为第三方应用在改变计费主体前，UE访问第三方应用的累计用量信息。
PCEF也可以不在确认消息中携带累计用量，而是在确认消息后，在单独发送一个用量上报消息，上报PCEF之前还为上报的累计用量。PCRF接收到本次PCEF上报的累计用量后再和之前保存的总的累计用量相加，获得第三方应用在改变计费主体前，UE访问第三那方应用的累计用量信息。若之前PCEF没有上报过Monitoring Key1的累计用量，那么PCEF本次上报的累计用量即为第三方应用在改变计费主体前，UE访问第三应用的累计用量信息。
步骤S2230：PCRF向AF发送RAR消息，消息中携带累计用量信息。
步骤S2232：AF返回确认消息。
步骤S2234：AF与第三方应用服务器的特定消息，譬如将累计用量信息上报给第三方应用服务器。
AF和第三方应用服务器从实现上可以是独立部署，AF也可以集成在第三方应用服务器上。不管哪种部署，从PCRF角度，PCRF与AF的互通也可以认为是PCRF与第三方应用服务器的互通。
在存在PC/AAC/SCEF的场景下，PC/AAC/SCEF负责HTTP消息和Diameter消息之间的转换，其余的流程类似，不再赘述。
通过实施例五，第三方应用提供商获得了网关在执行变更可计费主体策略之前，用户(同上述的UE)访问第三方数据应用产生的累计用量信息。这部分累计用量信息是由用户承担的。同时第三方数据应用自身也会统计用户访问第三方数据的用量信息。这样，第三方数据应用提供商就可以比较精确的获知其真正赞助的第三方数据应用的累计用量信息了。若到UE结束业务访问时，可计费主体始终是第三方应用，那么第三方应用提供商赞助的用量为第三方数据应用自身统计的用户访问第三方数据的用量减去网关上报的可计费主体变更前用户承担的累计用量信息。
AF和第三方应用服务器从实现上可以是独立部署，也可以AF集成在第三方应用服务器上。不管哪种部署，从PC/AAC/SCEF角度，PCRFPC/AAC/SCEF与AF的互通也可以认为是PC/AAC/SCEF与第三方应用服务器的互通。
实施例六
本实施例描述在在发起业务时，可计费主体为第三方应用提供商，在业务访问过程中，变为UE的流程。
图23是根据本发明实施例六的用量上报流程图，如图23所示，该流程包括如下步骤：
步骤S2302：UE附着到网络，建立IP-CAN会话。在这个过程中，PCEF与PCRF之间建立用于策略和计费控制的Gx会话。若IP-CAN会话涉及BBERF，则BBERF与PCRF之间建立用于策略控制的网关控制会话。
步骤S2304：UE与第三方应用服务器交互，发起业务访问。在业务访问的过程中，第三方应用服务器会对UE的业务访问计费，统计(也称计量)UE访问的用量信息，其中用量信息可以是流量和/或时长。
步骤S2306：第三方应用服务器与AF之间执行特定的交互流程，向应用服务器向AF提供用户请求的业务信息，其中第三方应用决定赞助用户访问的数据应用，第三方应用服务器向AF提供赞助业务的指示，以及赞助商标识，应用提供商标识、激活被赞助数据连接的指示、第三方应用赞助的用量阈值。
步骤S2308：AF向PCRF发送Diameter AAR消息，携带业务信息，被赞助数据连接信息，包括赞助商标识，应用提供商标识、和第三方应用赞助的用量阈值。
步骤S2310：PCRF向AF返回确认消息。
步骤S2312：PCRF根据业务信息、网络策略以及用户签约等信息制定PCC规则。PCRF根据赞助商标识和应用提供商标识确认相应的计费键(Charging key)和/或PCRF在PCC规则中增加赞助商标识和应用提供商标识。若BBERF存在，则PCRF还根据PCC规则制定QoS规则。此外，PCRF根据赞助商标识设置监控键Monitoring Key1。并在PCC规则中携带Monitoring Key1。
步骤S2314：PCRF向BBERF提供QoS规则。
步骤S2316：PCRF向PCEF提供PCC规则，激活针对Monitoring key1的用量监控。同时PCRF向PCEF提供Monitoring key1的用量阈值(该用量阈值为PCRF根据AF提供的赞助用量阈值设置)。PCEF执行PCC规则，并根据PCC规则对UE访问的第三方应用进行用量监控。当累计用量到达用量阈值时，PCEF向PCRF报告累计用量(该累计用量等于用量阈值)，PCRF再下发新的用量阈值。同时PCRF根据每一次报告的累计用量计算UE访问第三方应用的总的累计用量。
步骤S2318：在UE访问第三方业务的过程中，第三方应用决定取消赞助UE正在访问的第三方业务，第三方应用服务器与AF交互，向AF发送取消赞助的指示。
步骤S2320：AF向PCRF发送AAR消息，消息中携带赞助商标识、应用提供商标识、去激活被赞助数据连接的指示。
步骤S2322：PCRF保存信息后，返回确认消息。
步骤S2324：PCRF根据业务信息、网络策略以及用户签约等信息进行策略决策，更新之前制定的PCC规则。PCRF在PCC规则携带其他可以对用户进行计费的计费键和/或在PCC规则中不携带赞助商标识、应用提供商标识。此外，PCRF决定去激活针对Monitoring key1的用量监控。可选地，由于PCRF和AF支持均支持改变可计费主体，或根据用户签约或运营商策略，PCRF决定继续对UE访问第三方应用的数据进行用量监控，PCRF根据赞助商标识设置监控键Monitoring key2，并包含在PCC规则中。同时为Monitoring key2分配对应的用量阈值。
步骤S2326：PCRF向PCEF提供PCC规则，并指示PCEF去激活Monitoring key1的用量监控。若PCRF分配了Monitoring key2，则PCRF还向PCEF提供对应的用量阈值。为了去激活Monitoring key1的用量监控，PCRF可以只下发去激活Monitoring key1的用量监控的指示，或只将Monitoring key2替换为Monitoring key1，或同时下发去激活Monitoring key1的用量监控的指示，并将Monitoring key2替换为Monitoring key1。
步骤S2328：PCEF向PCRF返回确认消息，由于Monitoring key1的用量监控被去激活，因此PCEF在应答消息中携带PCEF之前还未上报的Monitoring Key1的累计用量。PCRF接收到本次PCEF上报的累计用量后再和之前保存的总的累计用量相加，获得第三方应用在改变计费主体前，UE访问第三方应用的累计用量信息(即第三方应用赞助的用量信息)。若之前PCEF没有上报过Monitoring Key1的累计用量，那么PCEF本次上报的累计用量即为第三方应用在改变计费主体前，UE访问第三应用的累计用量信息。
PCEF也可以不在确认消息中携带累计用量，而是在确认消息后，在单独发送一个用量上报消息，上报PCEF之前还为上报的累计用量。PCRF接收到本次PCEF上报的累计用量后再和之前保存的总的累计用量相加，获得第三方应用在改变计费主体前，UE访问第三方应用的累计用量信息。若之前PCEF没有上报过Monitoring Key1的累计用量，那么PCEF本次上报的累计用量即为第三方应用在改变计费主体前，UE访问第三应用的累计用量信息。
步骤S2330：PCRF向AF发送RAR消息，消息中携带累计用量信息。
步骤S2332：AF返回确认消息。
步骤S2334：AF与第三方应用服务器的特定消息，譬如向累计用量上报给应用服务器。
AF和第三方应用服务器从实现上可以是独立部署，也可以AF集成在第三方应用服务器上。不管哪种部署，从PCRF角度，PCRF与AF的互通也可以认为是PCRF与第三方应用服务器的互通。
在存在PC/AAC/SCEF的场景下，PC/AAC/SCEF负责HTTP消息和Diameter消息之间的转换，其余的流程类似，不再赘述。
在上述所有实施例中，运营商和所有第三方应用提供商均采用相同用量计费方法(运营商与所有第三方应用提供商都采用时长计费、流量计费或是同时时长和流量计费)。在其他实施例中，也可以对计量方法进行差异化处理，可采用如下两种方式之一：
1)运营商与第三方应用提供商可以签约协议决定固定的计量方法(Metering Method)。举例，若运营商A与第三方应用提供商A签约的是按流量的计量方法统计，在UE访问第三方应用后，第三方应用服务器判断用户UE通过运营商A访问业务，在第三方应用服务器以流量作为用量信息；PCRF在策略决策时，根据提供业务的第三方应用提供商确定计量方法，并在PCC规则中携带计量方法为流量的指示，PCEF根据计量方法指示对用户访问业务产生的流量进行统计。在可计费主体发生变化时，PCEF向PCRF返回的是流量的用量信息，可选地，PCRF向AF返回的是流量的用量信息。采用时长或是同时时长和流量的计量方法类似，不再赘述。
2)运营商与第三方应用提供商动态协商计量方法。举例，若运营商A与第三方应用提供商A签约可以采用时长、流量或是同时时长和流量进行计费。在UE访问第三方应用后，第三方应用服务器判断用户UE通过运营商A访问业务，第三方应用服务器可以决定三种中的一种作为这次业务方位的计量方法，若第三方应用服务器决定采用流量的计费方法，则第三方服务器将计量方法为流量的指示同业务信息一同发送给PCRF；PCRF在策略决策时，根据第三方应用服务器的指示，在PCC规则中携带计量方法为流量的指示，PCEF根据计量方法指示对用户访问业务产生的流量进行统计。在可计费主体发生变化时，PCEF向PCRF返回的是流量的用量信息，可选地，PCRF向AF返回的是流量的用量信息。采用时长或是同时时长和流量的计量方法类似，不再赘述。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述模块分别位于多个处理器中。
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，策略与计费执行功能实体PCEF将可计费主体发生变化之前的第一用量信息发送给第三方应用的服务器，其中，该第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息，该第一用量信息用于第三方应用的服务器确定第二用量信息，该第二用量信息为第三方应用的提供商为UE支付的用于UE访问第三方应用的用量信息。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
S1，策略与计费执行功能实体PCEF将可计费主体发生变化之前的第一用量信息发送给应用功能AF，其中，该第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
S1，第三方应用的服务器接收策略与计费执行功能实体PCEF发送的第一用量信息，其中，该第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息；
S2，该第三方应用的服务器根据第一用量信息确定第二用量信息，其中，第二用量信息为第三方应用的提供商为上述UE支付的用于UE访问第三方应用的用量信息。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
S1，应用功能AF接收策略与计费执行功能实体PCEF发送的可计费主体发生变化之前的第一用量信息，其中，该第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
S1，策略与计费规则功能实体PCRF在接收应用功能AF发送的用于指示改变可计费主体的第一指示后，向策略与计费执行功能实体PCEF发送用于指示PCEF上报可计费主体发生变化之前的第四用量信息的第二指示，其中，该第四用量信息包括可计费主体变化之前PCEF还未向PCRF上报的用户设备UE访问第三方应用的累计用量信息；
S2，上述PCRF在接收到第四用量信息后，向AF发送第五用量信息，其中，该第五用量信息包括可计费主体变化之前UE访问第三方应用的累计用量信息。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，本发明实施例提供的一种用量信息确定方法、发送方法、接收方法及装置具有以下有益效果：在变更可计费主体时，将可计费主体发生变化之前的第一用量信息发送给第三方应用的服务器，从而使得该第三方服务器能够精确的计量出第三方应用的提供商应该为用户设备UE支付的用量信息，提高计费精度，从而解决了相关技术中存在的计费误差的问题，进而达到了减小计费误差的效果。

Claims (48)

  1. 一种用量信息确定方法，包括：
    策略与计费执行功能实体PCEF将可计费主体发生变化之前的第一用量信息发送给第三方应用的服务器，其中，所述第一用量信息为可计费主体变化之前用户设备UE访问所述第三方应用的用量信息，所述第一用量信息用于所述第三方应用的服务器确定第二用量信息，所述第二用量信息为所述第三方应用的提供商为所述UE支付的用于所述UE访问所述第三方应用的用量信息。
  2. 根据权利要求1所述的方法，其中，
    所述第一用量信息包括可计费主体变化之前所述UE访问所述第三方应用的流量和/或时长的信息；
    所述第二用量信息包括所述第三方应用的提供商为所述UE支付的用于所述UE访问所述第三方应用的流量和/或时长的信息。
  3. 根据权利要求1所述的方法，其中，
    若变化之前的可计费主体是所述UE，则所述第二用量信息为第三用量信息减去所述第一用量信息，所述第三用量信息为所述第三方应用的服务器统计的所述UE在可计费主体变化之前和变化之后访问所述第三方应用的总用量；
    若变化之前的可计费主体是所述第三方应用的提供商，则所述第二用量信息为所述第一用量信息。
  4. 根据权利要求1所述的方法，其中，所述PCEF将可计费主体发生变化之前的第一用量信息发送给所述第三方应用的服务器之前，还包括：
    所述PCEF确定用于计量所述第一用量信息的用量计量方法，其中，所述PCEF和所述第三方应用的服务器采用相同的用量计量方法；
    所述PCEF根据确定的用量计量方法计量所述第一用量信息。
  5. 根据权利要求4所述的方法，其中，所述PCEF确定用于计量所述第一用量信息的用量计量方法包括：
    所述PCEF接收策略和计费规则功能PCRF发送的策略和计费控制PCC规则，其中，所述PCC规则中携带所述用量计量方法的指示信息，所述PCRF根据所述第三方应用的提供商确定与所述第三方应用的服务器相同的用量计量方法。
  6. 根据权利要求5所述的方法，其中，所述第三方应用的服务器向所述PCRF提供所述第三方应用的服务器采用的用量计量方法的指示信息，所述PCRF根据所述 第三方应用的服务器提供的用量计量方法的指示信息确定所述PCEF采用的用量计量方法。
  7. 根据权利要求4所述的方法，其中，所述PCEF根据确定的用量计量方法计量所述第一用量信息包括以下至少之一：
    所述PCEF根据确定的用量计量方法通过由所述PCEF计量的方式确定第一用量信息；
    所述PCEF根据确定的用量计量方法通过由所述PCEF与在线计费系统OCS进行交互的方式确定所述第一用量信息；
    所述PCEF根据确定的用量计量方法通过由所述PCEF与离线计费系统OFCS进行交互的方式确定所述第一用量信息。
  8. 根据权利要求1所述的方法，其中，所述PCEF将所述第一用量信息发送给所述第三方应用的服务器包括以下至少之一：
    所述PCEF将所述第一用量信息发送给策略和计费规则功能PCRF，所述PCRF将所述第一用量信息发送给应用功能AF，所述AF将所述第一用量信息上报给所述第三方应用的服务器；
    所述PCEF将所述第一用量信息发送给策略和计费规则功能PCRF，所述PCRF通过协议转换器PC、应用接入控制AAC或业务能力开发功能SCEF将所述第一用量信息发送给应用功能AF，所述AF将所述第一用量信息上报给所述第三方应用的服务器。
  9. 一种用量信息发送方法，包括：
    策略与计费执行功能实体PCEF将可计费主体发生变化之前的第一用量信息发送给应用功能AF，其中，所述第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息。
  10. 根据权利要求9所述的方法，其中，所述第一用量信息包括访问所述第三方应用的时间和/或流量。
  11. 根据权利要求9所述的方法，其中，所述PCEF将所述第一用量信息发送给所述AF包括以下至少之一：
    所述PCEF将所述第一用量信息发送给策略和计费规则功能PCRF，所述PCRF将所述第一用量信息发送给所述AF；
    所述PCEF将所述第一用量信息发送给策略和计费规则功能PCRF，所述PCRF通过协议转换器PC、应用接入控制AAC或业务能力开发功能SCEF将所述第一用量信息发送给所述AF。
  12. 一种用量信息确定方法，包括：
    第三方应用的服务器接收策略与计费执行功能实体PCEF发送的第一用量信息，其中，所述第一用量信息为可计费主体变化之前用户设备UE访问所述第三方应用的用量信息；
    所述第三方应用的服务器根据所述第一用量信息确定第二用量信息，其中，所述第二用量信息为所述第三方应用的提供商为所述UE支付的用于所述UE访问所述第三方应用的用量信息。
  13. 根据权利要求12所述的方法，其中，
    所述第一用量信息包括可计费主体变化之前所述UE访问所述第三方应用的流量和/或时长的信息；
    所述第二用量信息包括所述第三方应用的提供商为所述UE支付的用于所述UE访问所述第三方应用的流量和/或时长的信息。
  14. 根据权利要求12所述的方法，其中，所述第三方应用的服务器根据所述第一用量信息确定第二用量信息包括：
    若变化之前的可计费主体是所述UE，所述第三方应用的服务器通过将第三用量信息减去所述第一用量信息得到所述第二用量信息，其中，所述第三用量信息为所述第三方应用的服务器统计的所述UE在可计费主体变化之前和变化之后访问所述第三方应用的总用量；
    若变化之前的可计费主体是所述第三方应用的提供商，所述第三方应用的服务器将所述第一用量信息确定为所述第二用量信息。
  15. 根据权利要求14所述的方法，其中，所述第三方应用的服务器根据所述第一用量信息确定所述第二用量信息之前，还包括：
    所述第三方应用的服务器确定用于计量所述第三用量信息的用量计量方法；
    所述第三方应用的服务器根据确定的用量计量方法计量所述第三用量信息。
  16. 根据权利要求15所述的方法，其中，所述第三方应用的服务器确定用于计量所述第三用量信息的用量计量方法包括：
    所述第三方应用的服务器通过与所述第三方应用的运营商签约协议的方式确定所述用量计量方法；
    所述第三方应用的服务器通过与所述第三方应用的运营商进行动态协商的方式确定所述用量计量方法。
  17. 一种用量信息接收方法，包括：
    应用功能AF接收策略与计费执行功能实体PCEF发送的可计费主体发生变化之前的第一用量信息，其中，所述第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息。
  18. 根据权利要求17所述的方法，其中，所述第一用量信息包括访问所述第三方应用的时间和/或流量。
  19. 根据权利要求17所述的方法，其中，所述AF接收所述PCEF发送的所述第一用量信息包括：
    所述AF通过策略和计费规则功能PCRF接收所述PCEF发送的所述第一用量信息。
  20. 一种用量信息发送方法，包括：
    策略与计费规则功能实体PCRF在接收应用功能AF发送的用于指示改变可计费主体的第一指示后，向策略与计费执行功能实体PCEF发送用于指示所述PCEF上报可计费主体发生变化之前的第四用量信息的第二指示，其中，所述第四用量信息包括可计费主体变化之前所述PCEF还未向所述PCRF上报的用户设备UE访问第三方应用的累计用量信息；
    所述PCRF在接收到所述第四用量信息后，向所述AF发送第五用量信息，其中，所述第五用量信息包括可计费主体变化之前所述UE访问第三方应用的累计用量信息。
  21. 根据权利要求20所述的方法，其中，所述第五用量信息的取值为所述第四用量信息的取值，或者，所述第五用量信息的取值为所述第四用量信息与所述PCEF之前上报的所述UE访问第三方应用的累计用量信息的和。
  22. 根据权利要求20所述的方法，其中，所述第四用量信息包括所述UE访问所述第三方应用的流量和/或时长的信息。
  23. 根据权利要求20所述的方法，其中，所述PCRF在接收所述AF发送的用于指示改变可计费主体的所述第一指示后，还包括：
    所述PCRF指示所述PCEF去激活用于监控所述第四用量信息的监控键Monitoring Key。
  24. 根据权利要求23所述的方法，其中，所述PCRF指示所述PCEF去激活用于监控所述第四用量信息的所述第一监控键Monitoring Key包括：
    所述PCRF向所述PCEF发送去激活所述第一Monitoring Key的指示或用第二Monitoring key替换所述第一Monitoring Key的指示。
  25. 一种用量信息确定装置，应用于策略与计费执行功能实体PCEF中，包括：
    第一发送模块，设置为将可计费主体发生变化之前的第一用量信息发送给第三方应用的服务器，其中，所述第一用量信息为可计费主体变化之前用户设备UE访问所述第三方应用的用量信息，所述第一用量信息用于所述第三方应用的服务器确定第二用量信息，所述第二用量信息为所述第三方应用的提供商为所述UE支付的用于所述UE访问所述第三方应用的用量信息。
  26. 根据权利要求25所述的装置，其中，
    所述第一用量信息包括可计费主体变化之前所述UE访问所述第三方应用的流量和/或时长的信息；
    所述第二用量信息包括所述第三方应用的提供商为所述UE支付的用于所述UE访问所述第三方应用的流量和/或时长的信息。
  27. 根据权利要求25所述的装置，其中，
    若变化之前的可计费主体是所述UE，则所述第二用量信息为第三用量信息减去所述第一用量信息，所述第三用量信息为所述第三方应用的服务器统计的所述UE在可计费主体变化之前和变化之后访问所述第三方应用的总用量；
    若变化之前的可计费主体是所述第三方应用的提供商，则所述第二用量信息为所述第一用量信息。
  28. 根据权利要求25所述的装置，其中，还包括：
    第一确定模块，设置为确定用于计量所述第一用量信息的用量计量方法，其中，所述PCEF和所述第三方应用的服务器采用相同的用量计量方法；
    第一计量模块，设置为根据确定的用量计量方法计量所述第一用量信息。
  29. 根据权利要求28所述的装置，其中，所述第一确定模块包括：
    第一接收单元，设置为接收策略和计费规则功能PCRF发送的策略和计费控 制PCC规则，其中，所述PCC规则中携带所述用量计量方法的指示信息，所述PCRF根据所述第三方应用的提供商确定与所述第三方应用的服务器相同的用量计量方法。
  30. 根据权利要求29所述的装置，其中，所述第三方应用的服务器向所述PCRF提供所述第三方应用的服务器采用的用量计量方法的指示信息，所述PCRF根据所述第三方应用的服务器提供的用量计量方法的指示信息确定所述PCEF采用的用量计量方法。
  31. 根据权利要求28所述的装置，其中，所述第一计量模块包括以下至少之一：
    所述PCEF根据确定的用量计量方法通过由所述PCEF统计的方式确定第一用量信息；
    所述PCEF根据确定的用量计量方法通过由所述PCEF与在线计费系统OCS进行交互的方式确定所述第一用量信息；
    所述PCEF根据确定的用量计量方法通过由所述PCEF与离线计费系统OFCS进行交互的方式确定所述第一用量信息。
  32. 根据权利要求25所述的装置，其中，所述第一发送模块包括以下至少之一：
    第一发送单元，设置为将所述第一用量信息发送给策略和计费规则功能PCRF，所述PCRF将所述第一用量信息发送给应用功能AF，所述AF将所述第一用量信息上报给所述第三方应用的服务器；
    第二发送单元，设置为将所述第一用量信息发送给策略和计费规则功能PCRF，所述PCRF通过协议转换器PC、应用接入控制AAC或业务能力开发功能SCEF将所述第一用量信息发送给应用功能AF，所述AF将所述第一用量信息上报给所述第三方应用的服务器。
  33. 一种用量信息发送装置，应用于策略与计费执行功能实体PCEF中，包括：
    第二发送模块，设置为将可计费主体发生变化之前的第一用量信息发送给应用功能AF，其中，所述第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息。
  34. 根据权利要求33所述的装置，其中，所述第一用量信息包括访问所述第三方应用的时间和/或流量。
  35. 根据权利要求33所述的装置，其中，所述第二发送模块包括以下至少之一：
    第三发送单元，设置为将所述第一用量信息发送给策略和计费规则功能PCRF，所述PCRF将所述第一用量信息发送给所述AF；
    第四发送单元，设置为将所述第一用量信息发送给策略和计费规则功能PCRF，所述PCRF通过协议转换器PC、应用接入控制AAC或业务能力开发功能SCEF将所述第一用量信息发送给所述AF。
  36. 一种用量信息确定装置，应用于第三方应用的服务器中，包括：
    第一接收模块，设置为接收策略与计费执行功能实体PCEF发送的第一用量信息，其中，所述第一用量信息为可计费主体变化之前用户设备UE访问所述第三方应用的用量信息；
    第二确定模块，设置为根据所述第一用量信息确定第二用量信息，其中，所述第二用量信息为所述第三方应用的提供商为所述UE支付的用于所述UE访问所述第三方应用的用量信息。
  37. 根据权利要求36所述的装置，其中，
    所述第一用量信息包括可计费主体变化之前所述UE访问所述第三方应用的流量和/或时长的信息；
    所述第二用量信息包括所述第三方应用的提供商为所述UE支付的用于所述UE访问所述第三方应用的流量和/或时长的信息。
  38. 根据权利要求36所述的装置，其中，所述第二确定模块包括：
    若变化之前的可计费主体是所述UE，所述第三方应用的服务器通过将第三用量信息减去所述第一用量信息得到所述第二用量信息，其中，所述第三用量信息为所述第三方应用的服务器统计的所述UE在可计费主体变化之前和变化之后访问所述第三方应用的总用量；
    若变化之前的可计费主体是所述第三方应用的提供商，所述第三方应用的服务器将所述第一用量信息确定为所述第二用量信息。
  39. 根据权利要求38所述的装置，其中，还包括：
    第三确定模块，设置为确定用于计量所述第三用量信息的用量计量方法；
    第二计量模块，设置为根据确定的用量计量方法计量所述第三用量信息。
  40. 根据权利要求39所述的装置，其中，所述第三确定模块包括以下至少之一：
    第一确定单元，设置为通过与所述第三方应用的运营商签约协议的方式确定 所述用量计量方法；
    第二确定单元，设置为通过与所述第三方应用的运营商进行动态协商的方式确定所述用量计量方法。
  41. 一种用量信息接收装置，应用于应用功能AF中，包括：
    第二接收模块，设置为接收策略与计费执行功能实体PCEF发送的可计费主体发生变化之前的第一用量信息，其中，所述第一用量信息为可计费主体变化之前用户设备UE访问第三方应用的用量信息。
  42. 根据权利要求41所述的装置，其中，所述第一用量信息包括访问所述第三方应用的时间和/或流量。
  43. 根据权利要求41所述的装置，其中，所述第二接收模块包括：
    第二接收单元，设置为通过策略和计费规则功能PCRF接收所述PCEF发送的所述第一用量信息。
  44. 一种用量信息发送装置，应用于策略与计费规则功能实体PCRF中，包括：
    第三发送模块，设置为在接收应用功能AF发送的用于指示改变可计费主体的第一指示后，向策略与计费执行功能实体PCEF发送用于指示所述PCEF上报可计费主体发生变化之前的第四用量信息的第二指示，其中，所述第四用量信息包括可计费主体变化之前所述PCEF还未向所述PCRF上报的用户设备UE访问第三方应用的累计用量信息；
    第四发送模块，设置为在接收到所述第四用量信息后，向所述AF发送第五用量信息，其中，所述第五用量信息包括可计费主体变化之前所述UE访问第三方应用的累计用量信息。
  45. 根据权利要求44所述的装置，其中，所述第五用量信息的取值为所述第四用量信息的取值，或者，所述第五用量信息为所述第四用量信息与所述PCEF之前上报的所述UE访问第三方应用的累计用量信息的和。
  46. 根据权利要求44所述的装置，其中，所述第四用量信息包括所述UE访问所述第三方应用的流量和/或时长的信息。
  47. 根据权利要求44所述的装置，其中，所述装置还包括指示模块，应用于所述PCRF中，设置为在接收所述AF发送的用于指示改变可计费主体的所述第一指示后，指示所述PCEF去激活用于监控所述第四用量信息的监控键Monitoring Key。
  48. 根据权利要求47所述的装置，其中，在指示所述PCEF去激活用于监控所述第一用量信息的所述第一监控键Monitoring Key时，所述指示模块包括：
    指示单元，设置为向所述PCEF发送去激活所述第一Monitoring Key的指示或用第二Monitoring key替换所述第一Monitoring Key的指示。
PCT/CN2016/079585 2015-04-24 2016-04-18 用量信息确定方法、发送方法、接收方法及装置 WO2016169457A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510202033.9 2015-04-24
CN201510202033.9A CN106162596B (zh) 2015-04-24 2015-04-24 用量信息确定方法、发送方法、接收方法及装置

Publications (1)

Publication Number Publication Date
WO2016169457A1 true WO2016169457A1 (zh) 2016-10-27

Family

ID=57144469

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/079585 WO2016169457A1 (zh) 2015-04-24 2016-04-18 用量信息确定方法、发送方法、接收方法及装置

Country Status (2)

Country Link
CN (1) CN106162596B (zh)
WO (1) WO2016169457A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110266504A (zh) * 2019-04-23 2019-09-20 联通物联网有限责任公司 计费方法和装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1848895A (zh) * 2005-11-03 2006-10-18 华为技术有限公司 一种WiMAX中利用移动用户站切换计费方式的方法
CN101489207A (zh) * 2005-11-03 2009-07-22 华为技术有限公司 一种WiMAX中利用移动用户站切换计费方式的方法
CN101968907A (zh) * 2010-09-17 2011-02-09 宇龙计算机通信科技(深圳)有限公司 一种基于双卡移动终端的支付方法、系统及移动终端

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101442428B (zh) * 2007-11-19 2012-02-15 华为技术有限公司 一种端到端QoS的申请方法、系统和设备
CN101409954A (zh) * 2008-10-16 2009-04-15 中兴通讯股份有限公司 策略控制方法和系统、以及策略和计费执行功能实体
KR101470750B1 (ko) * 2013-07-30 2014-12-08 주식회사 엘지유플러스 스팬딩 리밋 제어 시의 트래픽 부하 감소를 위한 장치, 방법, 및 기록 매체

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1848895A (zh) * 2005-11-03 2006-10-18 华为技术有限公司 一种WiMAX中利用移动用户站切换计费方式的方法
CN101489207A (zh) * 2005-11-03 2009-07-22 华为技术有限公司 一种WiMAX中利用移动用户站切换计费方式的方法
CN101968907A (zh) * 2010-09-17 2011-02-09 宇龙计算机通信科技(深圳)有限公司 一种基于双卡移动终端的支付方法、系统及移动终端

Also Published As

Publication number Publication date
CN106162596B (zh) 2020-11-20
CN106162596A (zh) 2016-11-23

Similar Documents

Publication Publication Date Title
JP6077664B2 (ja) 無線アクセス・ネットワーク（ｒａｎ）のための輻輳制御
US9374737B2 (en) Policy and/or charging control
CN101861713B (zh) 一种会话修改方法及系统
US9647848B2 (en) Application charging method, device, and system
CN101431423B (zh) 一种用户业务流计费核减方法和装置
WO2009012686A1 (fr) Procédé, équipement et système de mise en œuvre du contrôle des conditions d'utilisation et de facturation
CN102065402B (zh) 基于时段的策略和计费控制方法及系统
CN102625272A (zh) 一种支持流检测功能的用量监控方法及系统
WO2011060698A1 (zh) 一种实现用量监测控制的方法及系统
WO2011063722A1 (zh) 一种实现用量监测控制的方法及系统
WO2009124441A1 (zh) 会话终结触发方法、实现方法及系统
CN106304195B (zh) 第三方应用的策略控制方法、scef和pcrf
WO2015143851A1 (zh) 用量监控方法、装置和系统
WO2011082644A1 (zh) 在线计费方法及装置
CN101583152A (zh) 一种信息传递方法、装置和系统
WO2016169457A1 (zh) 用量信息确定方法、发送方法、接收方法及装置
CN102711086A (zh) 被赞助数据连接的处理方法及策略与计费规则功能实体
WO2017092442A1 (zh) 策略和计费控制快速调整方法、装置及系统
KR101470750B1 (ko) 스팬딩 리밋 제어 시의 트래픽 부하 감소를 위한 장치, 방법, 및 기록 매체
CN101998339B (zh) 基于业务使用次数的策略与计费控制方法与装置
WO2009070947A1 (fr) Système de comptabilité de contenu prépayé et son procédé
WO2013113263A1 (zh) 一种应用检测控制功能模式的识别方法及系统
WO2012041149A1 (zh) 一种用量监测方法及系统
WO2011082639A1 (zh) 在线计费方法及装置
Sou et al. Signaling overhead of Policy and online Charging Control for bearer sessions in LTE network

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

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

Country of ref document: EP

Kind code of ref document: A1