WO2011003307A1 - 用于演进分组***的计费方法及*** - Google Patents

用于演进分组***的计费方法及*** Download PDF

Info

Publication number
WO2011003307A1
WO2011003307A1 PCT/CN2010/073249 CN2010073249W WO2011003307A1 WO 2011003307 A1 WO2011003307 A1 WO 2011003307A1 CN 2010073249 W CN2010073249 W CN 2010073249W WO 2011003307 A1 WO2011003307 A1 WO 2011003307A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging
information
service
function entity
policy
Prior art date
Application number
PCT/CN2010/073249
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 WO2011003307A1 publication Critical patent/WO2011003307A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1485—Tariff-related aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/73—Validating charges
    • 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

  • EPS Evolved Packet System
  • 3GPP 3rd Generation Partnership Project
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • HSS Home Subscriber Server
  • AAA 3 GPP Authentication 4 Authorization and Accounting
  • the E-UTRAN is connected to the MME through the S1-MME, and the MME is connected to the HSS through the S6a;
  • the S-GW is an access gateway device connected to the E-UTRAN, and the data is forwarded between the E-UTRAN and the P-GW, and responsible for buffering the paging waiting data,
  • the S-GW is connected to the E-UTRAN through the SI-U, connected to the MME through the S11, connected to the PCRF through the Gxc, and connected to the P-GW through the S5;
  • the P-GW is the EPS and
  • the border gateway of the Packet Data Network (PDN) is responsible for accessing the PDN and forwarding data between the EPS and the PDN.
  • PDN Packet Data Network
  • the P-GW is connected to the PCRF through the Gx and is connected to the IP service provided by the operator through the SGi.
  • the PCRF is connected to the operator's Internet Protocol (IP) service network interface through the Rx interface to obtain service information, and is connected to the gateway device in the 3GPP network through the Gx/Gxa/Gxb/Gxc interface, and is responsible for initiating the IP bearer. Establishing, guaranteeing the quality of service (Quality of Service, QoS for short), and performing charging control.
  • the EPS also supports user equipment (User Equipment, UE for short) access through non-3GPP systems other than E-UTRAN, where access by non-3GPP systems is implemented through the S2a/b/c interface, and P-GW is used as 3GPP.
  • non-3GPP systems are classified into a trusted non-3GPP IP access network and an untrusted non-3GPP IP access network.
  • Trusted non-3GPP IP access network can pass S2a directly
  • the interface is connected to the P-GW; the untrusted non-3GPP IP access network needs to be connected to the P-GW by an Evolved Packet Data Gateway (ePDG), and the interface between the ePDG and the P-GW is S2b.
  • ePDG Evolved Packet Data Gateway
  • FIG. 2 shows a structure diagram supporting EPC Dynamic Policy Charging Control (PCC), where SPR is a Subscription Profile Repositor, Policy and Charging Enforcement (Policy and Charging Enforcement)
  • PCEF Policy and Charging Enforcement
  • the function resides in the P-GW of the EPS system, and the PCRF exchanges information with the PCEF through the Gx interface.
  • the S-GW also has a policy control function, which is called a bearer binding and an event 4 advertisement function (Bearer).
  • the Binding and Event Reporting Function (BBERF) is used to exchange information between the BBERF and the PCRF through the Gxc interface.
  • the application function Application Function, abbreviated as AF
  • AF Application Function for providing the UE to the UE sends the service information for formulating the PCC or the QoS policy to the PCRF through the Rx interface.
  • the EPS can provide the charging system with the charging information of the bearer layer, including offline charging and online charging.
  • the charging system includes an offline charging system (Offline Charging System, referred to as OFCS) and an online charging system (Online Charging System). , referred to as OCS).
  • OFCS Offline Charging System
  • OCS Online Charging System
  • For online charging when the UE accesses through 3GPP, the P-GW interacts with the OCS to perform credit control.
  • the P-GW provides bearer layer charging information to the charging system, and uses the Access-Network-Charging-Identifier (also referred to as a carrier-based charging identifier) for identification.
  • the application server also provides application layer charging information to the charging system, and is identified by an application function charging identifier (AF-Charging-Identifier), which is generated by the AF entity and sent to the relevant application server.
  • AF-Charging-Identifier application function charging identifier
  • the AF entity itself can also provide application layer charging information to the charging system, which is also identified by AF-Charging-Identifier.
  • the charging information generated by the AF entity or the application server is application layer charging information.
  • the related art provides a charging method for an evolved packet system, in order to enable a charging system to associate bearer layer charging information generated by a user to access a certain service with application layer charging information, ⁇ -GW
  • the /PCEF and the AF entity send the respective generated charging identifiers to the other party through the PCRF.
  • the P-GW/PCEF When the P-GW/PCEF sends the carrier layer charging information identified by the Access-Network-Charging-Identifier to the charging system, it carries the AF-Charging- Identifier, and when the AF entity or the application server sends the application-layer charging information identified by the AF-Charging-Identifier to the charging system, the charging system can carry the access-Network-Charging-Identifier.
  • the accounting information is associated with the application layer charging information, so that the user's service access is correctly charged.
  • GTP General Packet Radio Service Tunneling Protocol
  • -Network-Charging-Identifier Lan IP data streams with the same QoS in the UE access service are bound to the same payload, where QoS includes QCI (QoS Class Identifier) and allocation and hold priority (Allocation and Retention Priority (ARP for short), P-GW/PCEF uses one Access-Network-Charging-Identifier for each charging information generated by the user, and P-GW/PCEF also uses Access-Network-Charging- The Identifier notifies the AF entity, and notifies the AF entity of the association between the Access-Network-Charging-Identifier and the IP data stream on the bearer layer. Therefore, the AF entity or the application server can transmit the IP data stream with the corresponding Access-Network-Charging.
  • QoS includes QCI (QoS Class Identifier) and allocation and hold priority (Allocation and Retention Priority (ARP for short)
  • ARP Allocation and Retention Priority
  • the -Identifier is associated with the Access-Network-Charging-Identif when the AF entity or the application server sends the application layer charging information of the IP data stream to the charging system. Ier, and then the charging system implements the association between the bearer layer charging information and the application layer charging information of the IP data flow of the same QoS.
  • the charging system from the P-GW/PCEF and the application server 4 ⁇ The billing information ⁇ " degrees can reach the same QoS data stream level.
  • the P-GW/PCEF can only assign one access network charging identifier to one PDN connection of the UE due to the limitation of the PMIPv6 protocol, that is, a PDN connection is only available.
  • the P-GW/PCEF is the charging information generated by a PDN connection of the UE and is identified by the Access-Network-Charging-Identifier.
  • an AVP Attribute Value Pair
  • QoS ie, a combination of QCI and APR
  • QCI and APR combination the charging with the same QoS (QCI and APR combination) data flow is carried.
  • Information, and this QoS is identified by the QoS (QCI and ARP combination) that the data stream has.
  • the accuracy of the charging information reported from the P-GW/PCEF can still reach the data flow level with the same QoS; however, since the P-GW/PCEF only has 4 Bar Access-Network-Charging-Identifier Provided to the AF entity, the billing information reported to the billing system by the jt ⁇ AF entity or the application server can only reach the PDN connection level.
  • the charging method for the evolved packet system in the related art is used when the PMIPv6 protocol is used between the S-GW and the P-GW, and the bearer layer charging information reported to the charging system is reached.
  • the QoS data flow level, and the application layer charging information reported to the charging system only reaches the PDN connection level, that is, the accuracy of the bearer layer charging information and the application layer charging information is inconsistent, resulting in failure to correctly charge.
  • the present invention is directed to a charging method and system for an evolved packet system, which can solve the charging method for an evolved packet system in the related art when the PMIPv6 protocol is used between the S-GW and the P-GW.
  • the bearer layer charging information reported to the charging system reaches the QoS data flow level, and the application layer charging information reported to the charging system only reaches the PDN connection level, that is, the carrier layer charging information and the application layer charging information.
  • a charging method for an evolved packet system including the following steps: The evolved packet system accepts service access of a user; and charges to a bearer layer of the accessed service on the charging system.
  • Information and application layer charging information, application layer charging information includes quality of service information of the data stream in the accessed service; the charging system performs charging according to the bearer layer charging information and the application layer charging information.
  • the quality of service information includes a quality of service level identifier and an allocation and retention priority.
  • the service of the evolved packet system accepting the user access specifically includes: the policy and charging execution function entity allocates the IP connection access network session according to the received established IP connection access network session request message. Incoming network charging identifier; Establishing an IP connection access network session; The service accepts user access through an IP connection access network session.
  • the policy and charging execution function entity allocates an access network charging identifier for the IP connection access network session according to the received IP connection access network session request message, which includes: And the event reporting function entity and the policy and charging rule function entity establish a gateway control session; the policy and charging rule function entity formulates a default policy charging control rule and a default quality of service rule; the policy and charging rule function entity will default the quality of service rule
  • the bearer binding and event reporting function entity is delivered; the bearer binding and event reporting function entity installs a default quality of service rule; the bearer binding and event reporting function entity sends an IP connection access network session to the policy and charging execution function entity.
  • the policy and charging execution function entity allocates an access network charging identifier for the IP connection access network session; the policy and charging execution function entity sends an establishment IP connection access network session indication message to the policy and charging rule function entity Establishing an IP connection access network session indication message includes an access network charging identifier.
  • the establishing an IP connection access network session specifically includes: the policy and charging rule function entity performs policy decision according to the default policy charging control rule, and obtains the first Policy charging control rule; the policy and charging rule function entity sends an IP connection access network session confirmation message to the policy and charging execution function entity, and the establishment of the IP-CAN session confirmation message includes the first policy charging control rule;
  • the charging execution function entity installs the first policy charging control rule; the policy and charging execution function entity interacts with the charging system to establish a charging session; the policy and charging execution function entity sends the bearer binding and event reporting function entity An IP connection access network session confirmation message is established, and the IP connection access network session establishment is completed.
  • the service accepting the user access by using the IP connection access network session specifically includes: the user interacts with the application function entity through the IP connection access network session; and applies the functional entity to the policy and charging rule function entity.
  • the policy and charging rule function entity saves the negotiated quality of service information, and returns an acknowledgement message to the application function entity;
  • the fee rule functional entity formulates a second policy charging control rule and a second quality of service rule according to the negotiated quality of service information, and the second month quality of service rule includes a quality of service level identifier and an allocation and retention priority.
  • the carrier layer charging information of the accessed service to the charging system specifically includes: the policy and charging rule function entity sends the second policy charging control rule to the policy and The charging execution function entity sends the second quality of service rule to the bearer binding and event reporting function entity; the policy and charging execution function entity installs the second policy charging control rule, and the bearer binding and event reporting function entity is installed.
  • the second service quality rule; the policy and charging execution function entity reports the bearer layer charging information to the charging system, the bearer layer charging information includes the access network charging identifier and the service quality information, and the monthly service quality information includes the monthly service quality. Level identification and assignment and retention priorities.
  • the application layer charging information of the accessed service to the charging system specifically includes: the policy and charging rule function entity provides the access function charging identifier and the month to the application function entity.
  • the service quality information includes the monthly service quality level identifier and the allocation and retention priority; the application function entity returns an acknowledgement message to the policy and charging rule function entity; the application function entity provides the access network billing to the application server.
  • the application layer charging information of the accessed service to the charging system specifically includes: the policy and charging rule function entity provides the access function charging identifier and the month to the application function entity.
  • the service quality information includes the monthly service quality level identifier and the allocation and retention priority; the application function entity returns an acknowledgement message to the policy and charging rule function entity; the application function entity reports the application layer billing to the billing system.
  • Information, application layer charging information including access network charging standard Knowledge and quality information.
  • a charging system for an evolved packet system including: an access accepting module, configured to accept service access of a user; and a reporting module, configured to report the accessed service
  • the bearer layer charging information and the application layer charging information, the application layer charging information includes the service quality information of the data stream in the accessed service, and the charging module is configured to calculate according to the bearer layer charging information and the application layer charging information. fee.
  • the quality of service information includes a quality of service level identifier and an allocation and retention priority.
  • a charging information association method for an evolved packet system including the following steps:
  • the policy charging rule function entity reports the data flow and the data flow to the application function entity.
  • Service quality information The application function entity uses the service quality information to perform billing information association.
  • the monthly quality information includes a monthly quality level identifier and an allocation and retention priority.
  • the application function entity includes the service quality information for the charging association in the charging information sent to the charging system.
  • the application function entity sends the service quality information of the data stream and the data stream to the application server, and the application server includes the service quality information in the charging information sent to the charging system. Billing association. Because the application layer charging information of the charging system to the charging system includes the accessed service.
  • the Access-Network-Charging-Identifier also includes the QoS information of the data flow in the accessed service, so that the application layer charging information learned by the charging system also reaches the QoS data flow level, that is, the bearer layer charging information and the application layer.
  • the accuracy of the charging information is consistent, and the correct charging for the accessed service is implemented. Therefore, the charging method for the evolved packet system in the related art is overcome.
  • the PMIPv6 protocol is used between the S-GW and the P-GW, the reporting is performed.
  • the bearer layer charging information of the charging system reaches the same QoS data flow level, and the application layer charging information reported to the charging system only reaches the PDN connection level, that is, the accuracy of the bearer layer charging information and the application layer charging information.
  • FIG. 1 shows an EPS structure diagram of a non-roaming state 3GPP network according to the related art
  • FIG. 2 shows a structure diagram of a PCC supporting dynamic policy charging control PCC
  • FIG. 4 is a flow chart showing a charging method according to a preferred embodiment 1 of the present invention
  • FIG. 5 shows a preferred embodiment according to the present invention
  • FIG. 6 is a block diagram showing a structure of a charging system according to an embodiment of the present invention
  • FIG. 7 is a flowchart showing a charging information association method for EPS according to an embodiment of the present invention
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. The invention will be described in detail below with reference to the drawings in conjunction with the embodiments.
  • Step S101 the EPS accepts a service access of a user
  • Step S102 7 layered charging information and application layer charging information of the accessed service on the charging system, the application layer charging information includes QoS information of the data stream of the accessed service
  • Step S103 the charging system is based on the bearer layer Billing information and application layer billing information are charged.
  • the EPS service in this embodiment first accepts the user access, and then carries the bearer layer charging information and the application layer charging information of the accessed service to the charging system, and the bearer layer charging information includes the access of the data stream in the accessed service.
  • the information includes the QoS information of the data stream.
  • the charging system uses the Access-Network-Charging-Identifier in the bearer layer charging information and the application layer charging information. Billing with QoS information. Because the application layer charging information of the charging system includes the QoS information of the data stream in the accessed service, the application layer charging information learned by the charging system also reaches the data flow level of the QoS, that is, the bearer layer meter. The fee information is consistent with the accuracy of the application layer charging information, and the correct charging for the accessed service is realized.
  • the charging method for the evolved packet system in the related art is used between the S-GW and the P-GW.
  • the bearer layer accounting information reported to the charging system reaches the same QoS data flow level, and the application layer charging information reported to the charging system only reaches the PDN connection level, that is, the bearer layer charging information and The accuracy of the application layer charging information is inconsistent, resulting in the problem that the charging cannot be performed correctly.
  • the foregoing bearer layer charging information and application layer charging information may be reported by different entities.
  • the bearer layer charging information is reported by the P-GW/PCEF in the EPS, and the application layer charging information is 4 on the AF entity or application server.
  • the foregoing process may not limit the reporting sequence of the bearer layer charging information and the application layer charging information, that is, the charging information of the bearer layer may be reported first, and then the application layer charging information may be reported, or the application may be reported first.
  • the layer charging information is reported to the bearer layer charging information.
  • the QoS information includes a QCI and an ARP.
  • the QoS information in the preferred embodiment is a combination of QCI and ARP, where QCI is a QoS class identifier, and ARP is an allocation and hold priority. Therefore, the combination of QCI and ARP is used as QoS information, which can clearly indicate the data of the accessed service. Flow accounting information.
  • step S101 specifically includes: the PCEF entity assigns an Access-Network-Charging-Identifier to the IP-CAN session according to the received setup IP-CAN session request message; establishing an IP-CAN session; User access is accepted through an IP-CAN session.
  • the PCEF entity is first assigned to the IP-CAN session.
  • Access-Network-Charging-Identifier which can be used to indicate the carrier charging status of the accessed service, and then establish an IP-CAN session, and finally the service accepts user access through the IP-CAN session.
  • an Access-Network-Charging-Identifier is generated to inform the charging system about the charging situation of the bearer layer, and an IP-CAN session is also established, which provides a basis for the user to access the service.
  • the PCEF entity in step S101 is based on the received configuration.
  • the IP-CAN session request message allocates an Access-Network-Charging-Identifier for the IP-CAN session, which specifically includes: the BBERF entity establishes a gateway control session with the PCRF entity; the PCRF entity formulates a default PCC rule and a default QoS rule; and the BBERF entity sends the PCEF entity to the PCEF entity.
  • Establish an IP-CAN session request message the PCRF entity sends the default QoS rule to the BBERF entity; the BBERF entity installs the default QoS rule; the PCEF entity assigns the Access-Network-Charging-Identifier to the IP-CAN session; and the PCEF entity sends the establishment to the PCRF entity.
  • the IP-CAN session indication message includes an Access-Network-Charging-Identifier.
  • the BBERF in the preferred embodiment resides in the S-GW, and the PCEF resides in the P-GW. Therefore, the gateway control session needs to be established first to implement information interaction between the BBERF entity and the PCEF entity.
  • the PCRF formulates the default PCC rules and default QoS rules for the bearer, and sends the default QoS rules to the BBERF.
  • the BBERF is installed, and the gateway hosting the BBERF (such as the S-GW) is stationed with the PCEF.
  • the gateway (such as P-GW) sends an IP-CAN session request message, and the message is a proxy binding update request message, and the gateway hosting the PCEF allocates an Access-Network-Charging-Identifier for the IP-CAN session that is requested to be established.
  • the PCEF sends an IP-CAN session indication message to the PCRF, and the message carries the Access-Network-Charging-Identifier. This embodiment implements that the PCEF entity allocates an Access-Network-Charging-Identifier for the IP-CAN session.
  • the establishing an IP-CAN session in step S101 specifically includes: the PCRF entity performs policy decision according to a default PCC rule to obtain a first PCC rule; and the PCRF entity sends an IP-CAN to the PCEF entity.
  • the session confirmation message, the establishment of the IP-CAN session confirmation message includes the first PCC rule; the PCEF entity installs the first PCC rule; the PCEF entity interacts with the charging system to establish a charging session; and the PCEF entity sends an IP-CAN session to the BBERF entity.
  • Confirmation message, IP-CAN session setup is complete.
  • the preferred embodiment first makes a policy decision by the PCRF, possibly tampering with the previously established default
  • the PCF rule the PCRF entity sends an IP-CAN session confirmation message including the first PCC rule to the PCEF entity, the PCEF installs the PCC rule, and the PCEF interacts with the OCS to establish an online charging session, and the gateway that resides with the PCEF (eg, The P-GW) returns an IP-CAN session confirmation message to the gateway (e.g., S-GW) residing with the BBERF, and the message is implemented as a proxy binding update confirmation message.
  • This embodiment establishes an IP-CAN session so that the user can request a service through an IP-CAN session.
  • the accepting user access by the service in step S101 through the IP-CAN session specifically includes: the user interacts with the AF entity through the IP-CAN session; the AF entity
  • the PCRF entity sends the negotiated QoS information after negotiation with the user, and subscribes to the update notification of the Access-Network-Charging-Identifier; the PCRF entity saves the QoS information after the ten-party, and returns an acknowledgement message to the AF entity;
  • the post QoS information formulates a second PCC rule and a second QoS rule, the second QoS rule including QCI and ARP.
  • the preferred embodiment first performs service access by the user, and after performing application layer interaction with the AF entity,
  • the AF entity provides the negotiated QoS information to the PCRF after the negotiation with the user, and the AF entity subscribes to the update notification of the Access-Network-Charging-Identifier, and the PCRF saves the service information such as the negotiated QoS information, and returns an acknowledgement message, and the PCRF is based on the user's
  • the contract information, the network policy, and the service information are used to make policy decisions.
  • the PCC rules and QoS rules are established.
  • the PCRF interacts with the BBERF, and the QoS rules are sent to the BBERF and the BBERF for installation. This embodiment implements the service to accept user access through an IP-CAN session.
  • the step S102 specifically includes: the PCRF entity sends the second PCC rule to the PCEF entity, and the second QoS rule is sent to the PCEF entity and the BBERF entity; and the PCEF entity installs the second PCC
  • the BBERF entity installs the second QoS rule
  • the PCEF entity reports the bearer layer charging information to the charging system, and the bearer layer charging information includes an Access-Network-Charging-Identifier and QoS information
  • the QoS information includes the QCI and the ARP.
  • the preferred embodiment first sends the second QoS rule to the PCEF entity and the BBERF entity by the PCRF entity, the BBERF entity installs the second QoS rule, and the PCEF entity sends the charging information to the charging system, including Access-Network- Charging-Identifier and QoS information, including QoS information including QCI and ARP.
  • the PCEF entity generates an Access-Network-Charging-Identifier for a PDN connection of the UE, where an AVP is provided for the data flow with the same QoS (ie, a combination of QCI and APR), and the accounting with the same QoS data flow is carried. Information, and this AVP is identified by the QoS that the data stream has.
  • step S103 specifically includes The PCRF entity provides an Access-Network-Charging-Identifier and QoS information to the AF entity, the QoS information includes the QCI and the allocation and retention priority; the AF entity returns an acknowledgement message to the PCRF entity; and the AF entity provides Access-Network-Charging- to the application server.
  • the Identifier and the QoS information are sent by the application server to the accounting system, and the application layer charging information includes the Access-Network-Charging-Identifier and the QoS information.
  • the preferred embodiment first sends the policy charging rule to the PCEF by the PCRF.
  • the return policy charging rule provides an acknowledgment message. Since the AF entity subscribes to the update port of the Access-Network-Charging-Identifier, the PCRF provides the information to the AF entity, and the information is accurate to the corresponding IP stream provided by the AF entity.
  • the access network charging identifier and the PCRF are the QoS information (the combination of QCI and ARP) of the IP stream, and the AF entity returns an acknowledgement message to the PCRF, and the AF entity retrieves the Access-Network-Charging-Identifier message and
  • the QoS information (the combination of QCI and ARP) is provided to the application server, and finally the application server reports the application layer charging information to the charging system, and the application layer charging information includes the Access-Network-Charging-Identifier message and the QoS information (QCI and ARP).
  • step S103 specifically includes: the PCRF entity provides an Access-Network-Charging-Identifier and QoS information to the AF entity, where the QoS information includes the QCI and the allocation and retention priority; the AF entity sends the PCRF entity to the PCRF entity.
  • the acknowledgment message is returned; the AF entity reports the application layer charging information to the charging system, and the application layer charging information includes the Access-Network-Charging-Identifier and the QoS information.
  • the preferred embodiment first sends a policy charging rule providing message to the PCEF by the PCRF. After the PCEF installs the rule, the return policy charging rule provides an acknowledgement message. Since the AF entity subscribes to the update port of the Access-Network-Charging-Identifier, the PCRF The AF entity provides the information, the information is accurate to the access network charging identifier corresponding to each IP stream provided by the AF entity, and the PCRF is the QoS information (the combination of QCI and ARP) that is authorized by the IP stream, and the AF entity returns to the PCRF.
  • the acknowledgment message, the AF entity reports the Access-Network-Charging-Identifier message and the QoS information (the combination of QCI and ARP) as the application layer charging information to the charging system.
  • the application layer charging information reported to the charging system includes, in addition to the Access-Network-Charging-Identifier of the accessed service, the QoS information of the data stream in the accessed service, and then the application layer charging information learned by the charging system.
  • the data flow level of the QoS is also achieved, that is, the uniformity of the charging information with the bearer layer is achieved.
  • the method includes implementing a PDN connection established by a UE, and an AF entity provides service information, and the PCRF uses each IP data flow included in the service information.
  • the associated access network charging identifier and QoS information are reported to the AF entity,
  • the method includes the following steps: Step 401: After receiving the IP-CAN session request message, the BBERF entity interacts with the PCRF entity to establish a gateway control session. In this process, the PCRF entity formulates a default bearer PCC according to the subscription information of the user.
  • Step 402 the gateway hosting the BBERF (such as the S-GW) sends the establishment to the gateway (such as the P-GW) where the PCEF resides.
  • the IP-CAN session request message is implemented as a proxy binding update request message.
  • Step 403 The gateway residing with the PCEF allocates an access network charging identifier for the IP-CAN session requested to be established, and the PCEF entity sends the PCR entity to the PCRF entity.
  • An IP-CAN session indication message is set, and the message carries the access network charging identifier.
  • Step 404 The PCRF entity performs a policy decision, and may modify the previously-prescribed PCC rule of the default bearer.
  • Step 405 The PCRF entity returns an IP-based establishment to the PCEF entity.
  • the PC session confirmation message is sent, the PCC rule is issued, and the PCEF entity installs the PCC rule.
  • Step 406 The PCEF entity interacts with the OCS to establish an online charging session.
  • Step 407 Residing The gateway of the PCEF (such as the P-GW) returns an IP-CAN session confirmation message to the gateway (such as the S-GW) that resides in the BBERF, and the message is implemented as a proxy binding update confirmation message, and thus, the IP-CAN session is established.
  • Step 408 the user performs the service access, and after the application layer interaction with the AF entity, the AF entity provides the QoS information negotiated with the user to the PCRF entity, and the AF entity subscribes to Access-Network-Charging-
  • the Identifier information informs that, in this embodiment, the service provided by the AF entity includes two IP data streams, where IP flow 1 and IP flow 2 are used for identification, and each IP data stream has its requested QoS; Step 409, PCRF entity The service information is saved, and the confirmation message is returned.
  • Step 410 The PCRF entity performs policy decision according to the subscription information, the network policy, and the service information of the user, and formulates the PCC rule and the QoS rule.
  • the PCRF is used for the PCC rule defined by the IP flow1.
  • PCC Rulel indicates that QCI and ARP are used in QCI1 and ARP1 in the rule. It is indicated that the PCC rule defined for IP flow2 is represented by PCC Rule2, and the QCI and ARP in the rule are represented by QCI2 and ARP2.
  • Step 411 The PCRF entity interacts with the BBERF entity, and the QoS rule is sent to the BBERF entity, and the BBERF entity is installed.
  • Step 413 after the PCEF entity installs the rule, returning the policy charging rule to provide an acknowledgement message;
  • Step 414 the PCR entity provides the AF entity to the AF entity because the AF entity subscribes to the notification of the Access-Network-Charging-Identifier information.
  • the information is accurate to the access network charging identifier corresponding to each IP stream provided by the AF entity, and the QoS information (QCI and ARP) authorized by the PCRF entity for the IP data stream.
  • the information corresponding to the IP flow1 Including the access network charging identifier, QCI1 and ARP1 includes the access network charging identifier, QCI2 and ARP2;
  • Step 415 the AF entity returns an acknowledgement message to the PCRF entity.
  • the AF entity obtains the charging information corresponding to each IP flow, including the access network charging identifier, QCI, and ARP.
  • the AF entity sends the access network charging identifier, QCI, and ARP to other application servers.
  • the application layer accounting information reported by the application server to the OCS carries the Access-Network-Charging-Identifier, QCI, and ARP for OCS. Association of carrier layer billing information.
  • the AF entity can also report the accounting information to the OCS at the same time.
  • the accounting information includes Access-Network-Charging-Identifier, QCI, and ARP.
  • the access network charging identifier, QCI, and ARP obtained are used for charging information association.
  • the PCRF is the same as the QoS ACL of the IP flow1 and the IP flow2 (the QCI and the ARP)
  • the PCRF entity is on the AF entity.
  • the information corresponding to IP flow2 includes Access-Network-Charging-Identifier, QCIa, and ARPa.
  • FIG. 5 is a flowchart of a charging method according to a preferred embodiment 2 of the present invention.
  • This embodiment describes a user in the second embodiment after establishing an IP-CAN session access service, due to a network policy, or AF.
  • the process of changing the service information provided by the entity causes the PCRF entity to modify the application layer charging information, which includes the following steps: Step 501: The PCRF entity enters due to the network policy or the service information provided by the AF entity. In the present embodiment, the PCRF entity modifies the QoS of the IP flow1, and the ARP1 4 ⁇ is changed to ARP1. In step 502, the PCRF entity interacts with the BBERF entity.
  • Step 503 The PCRF entity sends a policy and charging rule providing message to the PCEF entity, where the message carries the falsified PCC rule PCC Rule1'; Step 504, PCEF entity update The rule returns a confirmation message.
  • Step 505 The PCRF entity sends a new Access-Network-Charging-Identifier information to the AF entity, including the access network charging identifier corresponding to IP flow 1 and the new QoS authorized by the PCRF entity. Information, QCI1 and ARP1,; Step 4 gathers 506, and the AF entity returns a confirmation message after saving the information.
  • the PCRF entity can only tamper with QCI or simultaneously ⁇ ⁇ ' ⁇ QCI and ARP.
  • the PCRF entity can also change the corresponding ⁇ to the AF entity.
  • the AF entity obtains the application layer charging identifier information corresponding to the IP flowl 4 tampering, including the access network charging identifier, QCI1, and ARP1.
  • the AF entity sends the information to the application server, and the application server reports the charging information to the OCS, which carries the access network charging identifier, QCI 1, ARP 1 ', so that the OCS performs association with the bearer layer charging information. .
  • the AF entity can also report the accounting information to the OCS at the same time.
  • the charging information includes Access-Network-Charging-Identifier, QCI1, and ARP1.
  • the AF entity uses the acquired access network charging identifier, QCI, and ARP for accounting information association.
  • FIG. 6 is a structural block diagram of a charging system according to an embodiment of the present invention, which can be used to implement the foregoing charging method.
  • the system includes: an access accepting module 10, configured to accept a user's service access; a reporting module 20, connected to the access accepting module 10, for reporting the bearer layer charging information and the application layer charging of the accessed service of the access accepting module 10.
  • the information, the application layer charging information includes the QoS information of the data stream, and the charging module 30 is connected to the reporting module 20 for performing charging according to the bearer layer charging information and the application layer charging information reported by the reporting module 20.
  • the charging system in this embodiment first uses the access accepting module 10 to access the services of the evolved packet system, and then the reporting module 20 reports the bearer layer charging information and the application layer charging information of the accessed service to the charging system.
  • the layer charging information includes an Access-Network-Charging-Identifier and QoS information.
  • the application layer charging information includes an Access-Network-Charging-Identifier of the data stream, and includes QoS information of the data stream.
  • the charging module 30 is used. The charging is performed according to the Access-Network-Charging-Identifier and QoS information in the bearer layer charging information and the application layer charging information.
  • the application layer charging information of the charging system includes the QoS information of the data stream in the accessed service
  • the application layer charging information learned by the charging system also reaches the data flow level of the QoS, that is, the bearer layer meter.
  • the fee information is consistent with the accuracy of the application layer charging information, and the correct charging for the accessed service is realized. Therefore, the charging system for the evolved packet system in the related art is used between the S-GW and the P-GW.
  • the bearer layer charging information reported to the charging system reaches the QoS data flow level, and the application layer charging information of the charging system only reaches the PDN connection level, that is, the carrier layer charging.
  • the QoS information includes QCI and ARP.
  • the QoS information in the preferred embodiment is a combination of QCI and ARP, where QCI is a QoS class identifier, and ARP is an allocation and hold priority. Therefore, the combination of QCI and ARP is used as QoS information, which can clearly indicate the data of the accessed service. Flow accounting information.
  • a charging information association method for EPS is also provided. FIG.
  • Step S701 A PCRF entity reports QoS information of a data stream and a data stream to an AF entity.
  • Step S702 the AF entity uses the QoS information to perform charging information association.
  • the PCRF entity first reports the QoS information of the data stream and the data stream to the AF entity, and performs charging according to the QoS information. Because the application layer charging information reported to the charging system includes the QoS information of the data flow, the application layer charging information learned by the charging system reaches the data flow level of the QoS, thereby realizing correct charging, thus overcoming the correlation.
  • the QoS information includes a QCI and an ARP.
  • the QoS information in the preferred embodiment is a combination of QCI and ARP, where QCI is a QoS class identifier, and ARP is an allocation and hold priority. Therefore, the combination of QCI and ARP is used as QoS information, which can clearly indicate the data of the accessed service. Flow accounting information.
  • the AF entity includes QoS information for charging association in the charging information sent to the charging system.
  • the AF entity directly sends application layer charging information to the charging system, which includes QoS information for charging association.
  • the application layer charging information sent to the charging system includes the QoS information, so that the application layer charging information learned by the charging system also reaches the QoS data flow level, that is, the association with the carrier layer charging information is realized.
  • the AF entity sends the QoS information of the data stream and the data stream to the application server, and the application server includes the QoS information for the charging association in the charging information sent to the charging system. .
  • the AF entity first sends the QoS information of the data stream and the data stream to the application server, and then the application server sends the application layer charging information to the charging system, where the QoS information for the charging association is included. Because the application layer charging information sent to the charging system includes the QoS information, the application layer charging information learned by the charging system also reaches the QoS data flow level, that is, the association with the bearer layer charging information is realized. From the above description, it can be seen that the foregoing embodiment of the present invention enables the application layer charging information learned by the charging system to reach the QoS data flow level, that is, the carrier layer charging information and the application layer charging information. The accuracy is consistent, and the correct charging for the accessed service is realized.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed 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, or they may be separately fabricated into individual integrated circuit modules, or they may be Multiple modules or steps are made into a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the above description is only a preferred embodiment of the present invention, and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

用于演进分组***的计费方法及*** 技术领域 本发明涉及通信领域， 具体而言， 涉及一种用于演进分组***的计费方 法及***。 背景技术 图 1 示出了根据相关技术的非漫游状态第三代合作伙伴计划 （ 3rd Generation Partnership Project, 简称为 3GPP ) 网络的演进分组*** ( Evolved Packet System , 简称为 EPS ) 结构图， EPS 由演进的通用地面无线接入网 ( Evolved Universal Terrestrial Radio Access Network, 简称为 E-UTRAN )、移 动管理单元 ( Mobility Management Entity, 简称为 MME ),月艮务网关（ Serving Gateway, 简称为 S-GW ),分组数据网络网关（ Packet Data Network Gateway, 简称为 P-GW )、 归属用户月艮务器 （Home Subscriber Server, 简称为 HSS )、 3 GPP认证 4受权计费 ( Authentication、 Authorization and Accounting, 简称为 AAA )月艮务器、 策略和计费规则功能 ( Policy and Charging Rules Function, 简称为 PCRF ) 实体及其他支撑节点组成。 其中， E-UTRAN通过 S 1-MME 与 MME相连， MME通过 S6a与 HSS相连； S-GW是与 E-UTRAN相连的 接入网关设备， 在 E-UTRAN和 P-GW之间转发数据， 并且负责对寻呼等待 数据进行緩存， S-GW通过 SI-U与 E-UTRAN相连，通过 S 11与 MME相连， 通过 Gxc与 PCRF相连， 通过 S5与 P-GW相连； P-GW则是 EPS与分组数 据网 （ Packet Data Network , 简称为 PDN ) 的边界网关， 负责 PDN的接入、 在 EPS与 PDN间转发数据等， P-GW通过 Gx与 PCRF相连， 通过 SGi与运 营商提供的 IP业务相连； PCRF通过 Rx接口与运营商互联网协议 ( Internet Protocol , 简称为 IP ) 业务网络接口连接， 获取业务信息， 并通过 Gx/Gxa/Gxb/Gxc接口与 3GPP网络中的网关设备相连， 负责发起 IP承载的 建立， 保证业务数据的服务质量 （Quality of Service, 简称为 QoS ), 并进行 计费控制。 EPS 也支持用户设备 ( User Equipment, 简称为 UE ) 通过除 E-UTRAN以外的其它非 3GPP***的接入， 其中， 非 3GPP***的接入通过 S2a/b/c接口实现， P-GW作为 3GPP***的接入与非 3GPP***的接入的数 据锚点。 在 EPS的***架构中， 非 3GPP***被分为可信任非 3GPP IP接入 网和不可信任非 3GPP IP接入网。 可信任非 3GPP IP接入网可直接通过 S2a 接口与 P-GW连接； 不可信任非 3GPP IP接入网需要经过演进的分组数据网 关（ Evolved Packet Data Gateway, , 简称为 ePDG )与 P-GW相连， ePDG与 P-GW间的接口为 S2b。 图 2示出了支持 EPC动态策略计费控制 （ Policy and Charging Control, 简称为 PCC ) 的结构图， 其中， SPR 为签约文档库 ( Subscription Profile Repositorty ),策略和计费执行功能 ( Policy and charging enforcement function, 简称为 PCEF )驻留在 EPS***的 P-GW中， PCRF与 PCEF间通过 Gx接口 交换信息。当 P-GW与 S-GW间的接口基于代理移动 IPv6( Proxy Mobile IPv6 , 简称为 ΡΜΙΡν6 )协议时， S-GW也存在策略控制的功能， 称为 载绑定和事 件 4艮告功能 ( Bearer Binding and Event Reporting Function, 简称为 BBERF ), BBERF与 PCRF之间通过 Gxc接***换信息。 同时， 为 UE提供业务的应用 功能 ( Application Function, 简称为 AF ) 实体通过 Rx接口向 PCRF发送用 于制定 PCC或 QoS策略的业务信息。
EPS可以向计费***提供承载层的计费信息，包括离线计费和在线计费， 其中计费***包括离线计费*** （ Offline Charging System, 简称为 OFCS ) 和在线计费*** （Online Charging System, 简称为 OCS )。 对于在线计费， 当 UE通过 3GPP接入时， 由 P-GW与 OCS交互， 进行信用控制。 P-GW向 计 费 系 统 提 供 承 载 层 计 费 信 息 ， 用 接 入 网 计 费 标 识 ( Access-Network-Charging-Identifier , 也称为 载层计费标识 ) 进行标识。 同时应用服务器也向计费***提供应用层计费信息， 用应用功能计费标识 ( AF-Charging-Identifier )进行标识， 该计费标识由 AF实体产生并发送给相 关的应用服务器。 AF 实体自身也可向计费***提供应用层计费信息， 同样 用 AF-Charging-Identifier进行标识。 AF实体或应用服务器产生的计费信息均 为应用层计费信息。 相关技术中提供了一种用于演进分组***的计费方法， 该方法为了使计 费***将用户访问某个业务所产生的承载层计费信息和应用层计费信息进行 关联，Ρ-GW/PCEF和 AF实体通过 PCRF将各自产生的计费标识发送给对方， 当 P-GW/PCEF向计费***发送用 Access-Network-Charging-Identifier标识的 载层计费信息时携带 AF-Charging-Identifier,而当 AF实体或应用月艮务器向 计费***发送用 AF-Charging-Identifier 标识的应用层计费信息时携带 Access-Network-Charging-Identifier, 则计费***就可以 ^" 载层计费信息和 应用层计费信息进行关联， 从而实现对用户的业务访问进行正确计费。 当 S-GW与 P-GW之间釆用通用分组无线业务隧道协议 ( General Packet Radio Service Tunneling Protocol, 简称为 GTP ) 时， P-GW/PCEF为 UE的一 个 PDN连接的每一个 载分配一个 Access-Network-Charging-Identifier„ UE 访问业务中具有相同 QoS的 IP数据流会绑定到同一个^载上， 其中 QoS包 括 QCI( QoS Class Identifier, QoS等级标识）和分配与保持优先级（ Allocation and Retention Priority , 简称为 ARP ) , P-GW/PCEF为每一个 载产生的计费 信息用一个 Access-Network-Charging-Identifier进行标识， 同时 P-GW/PCEF 还通过 PCRF将 Access-Network-Charging-Identifier通知 AF实体， 并将承载 层上 Access-Network-Charging-Identifier与 IP数据流的关联关系通知 AF实 体 。 故 AF 实 体 或 应 用 月艮务 器 可 将 IP 数据 流与 相 应 的 Access-Network-Charging-Identifier关联起来， 当 AF实体或应用月艮务器向计 费 系 统发送 IP 数据流的应用 层计 费信息时， 会携 带相应的 Access-Network-Charging-Identifier, 进而计费***实现了对相同 QoS 的 IP 数据流的承载层计费信息和应用层计费信息的关联。 对于计费***来说， 从 P-GW/PCEF和应用月艮务器上 4艮上来的计费信息^"度都可以到达相同 QoS的 数据流级别。 当 S-GW与 P-GW之间釆用 PMIPv6协议时， 由于 PMIPv6协议的局限 性导致 P-GW/PCEF只能为 UE的一个 PDN连接分配一个接入网计费标识， 即一个 PDN连接只有一个 Access-Network-Charging-Identifier。 P-GW/PCEF 为 UE 的 一 个 PDN 连 接 产 生 的 计 费 信 息 ， 并 用 Access-Network-Charging-Identifier 进行标识。 在该计费信息中为具有相同 QoS (即 QCI和 APR的组合） 的数据流提供一个 AVP ( Attribute Value Pair, 属性 -值对）， 携带具有相同 QoS ( QCI和 APR组合）数据流的计费信息， 并且用数据流所具有的 QoS ( QCI和 ARP组合） 标识这个 AVP。 这样， 对 于计费***来说， 从 P-GW/PCEF上报上来的计费信息精度仍然能够达到具 有 相 同 QoS 的 数 据 流 级 别 ； 然 而 由 于 P-GW/PCEF 只 4巴 Access-Network-Charging-Identifier提供给 AF实体， 因 jt匕 AF实体或应用月艮 务器向计费***上报的计费信息只能达到 PDN连接级别。 在实现本发明过程中， 发明人发现相关技术中用于演进分组***的计费 方法当 S-GW与 P-GW之间釆用 PMIPv6协议时， 上报到计费***的承载层 计费信息达到 QoS的数据流级别， 而上报到计费***的应用层计费信息仅达 到 PDN 连接级别， 即承载层计费信息与应用层计费信息的精度不一致， 从 而导致无法正确计费。 发明内容 本发明旨在提供一种用于演进分组***的计费方法及***， 能够解决相 关技术中用于演进分组***的计费方法当 S-GW与 P-GW之间釆用 PMIPv6 协议时， 上报到计费***的承载层计费信息达到 QoS的数据流级别， 而上报 到计费***的应用层计费信息仅达到 PDN 连接级别， 即 载层计费信息与 应用层计费信息的精度不一致， 从而导致无法正确计费的问题。 在本发明的实施例中， 提供了一种用于演进分组***的计费方法， 包括 以下步骤： 演进分组***接受用户的业务访问； 向计费***上 4艮被访问业务 的承载层计费信息和应用层计费信息， 应用层计费信息包括被访问业务中数 据流的服务质量信息； 计费***根据承载层计费信息和应用层计费信息进行 计费。 进一步地， 在上述的计费方法中， 服务质量信息包括服务质量等级标识 以及分配与保持优先级。 进一步地， 在上述的计费方法中， 演进分组***的业务接受用户访问具 体包括：策略和计费执行功能实体根据接收的建立 IP连接接入网会话请求消 息为 IP连接接入网会话分配接入网计费标识； 建立 IP连接接入网会话； 业 务通过 IP连接接入网会话接受用户访问。 进一步地， 在上述的计费方法中， 策略和计费执行功能实体根据接收的 建立 IP连接接入网会话请求消息为 IP连接接入网会话分配接入网计费标识 具体包括： 承载绑定和事件报告功能实体与策略和计费规则功能实体建立网 关控制会话； 策略和计费规则功能实体制定默认策略计费控制规则和默认服 务质量规则； 策略和计费规则功能实体将默认服务质量规则下发给承载绑定 和事件报告功能实体；承载绑定和事件报告功能实体安装默认服务质量规则； 承载绑定和事件报告功能实体向策略和计费执行功能实体发送建立 IP 连接 接入网会话请求消息；策略和计费执行功能实体为 IP连接接入网会话分配接 入网计费标识； 策略和计费执行功能实体向策略和计费规则功能实体发送建 立 IP连接接入网会话指示消息， 建立 IP连接接入网会话指示消息包括接入 网计费标识。 进一步地， 在上述的计费方法中， 建立 IP连接接入网会话具体包括： 策 略和计费规则功能实体根据默认策略计费控制规则进行策略决策， 得到第一 策略计费控制规则； 策略和计费规则功能实体向策略和计费执行功能实体发 送建立 IP连接接入网会话确认消息， 建立 IP-CAN会话确认消息包括第一策 略计费控制规则； 策略和计费执行功能实体安装第一策略计费控制规则； 策 略和计费执行功能实体与计费***进行交互， 建立计费会话； 策略和计费执 行功能实体向承载绑定和事件报告功能实体发送建立 IP 连接接入网会话确 认消息， IP连接接入网会话建立完成。 进一步地， 在上述的计费方法中， 业务通过 IP连接接入网会话接受用户 访问具体包括： 用户通过 IP连接接入网会话与应用功能实体交互； 应用功能 实体向策略和计费规则功能实体发送与用户协商后的协商后服务质量信息， 并订阅接入网计费标识的更新通知； 策略和计费规则功能实体保存协商后服 务质量信息， 并向应用功能实体返回确认消息； 策略和计费规则功能实体根 据协商后服务质量信息制定第二策略计费控制规则和第二服务质量规则， 第 二月艮务质量规则包括艮务质量等级标识以及分配与保持优先级。 进一步地， 在上述的计费方法中， 向计费***上 4艮被访问业务的 载层 计费信息具体包括： 策略和计费规则功能实体将第二策略计费控制规则下发 给策略和计费执行功能实体， 将第二服务质量规则下发给承载绑定和事件报 告功能实体； 策略和计费执行功能实体安装第二策略计费控制规则， 承载绑 定和事件报告功能实体安装第二服务质量规则； 策略和计费执行功能实体向 计费***上报承载层计费信息， 承载层计费信息包括接入网计费标识和服务 质量信息， 月艮务质量信息包括月艮务质量等级标识以及分配与保持优先级。 进一步地， 在上述的计费方法中， 向计费***上 4艮被访问业务的应用层 计费信息具体包括： 策略和计费规则功能实体向应用功能实体提供接入网计 费标识和月艮务质量信息， 艮务质量信息包括月艮务质量等级标识以及分配与保 持优先级； 应用功能实体向策略和计费规则功能实体返回确认消息； 应用功 能实体向应用服务器提供接入网计费标识和服务质量信息； 应用服务器向计 费***上 4艮应用层计费信息， 应用层计费信息包括接入网计费标识和月艮务质 量信息。 进一步地， 在上述的计费方法中， 向计费***上 4艮被访问业务的应用层 计费信息具体包括： 策略和计费规则功能实体向应用功能实体提供接入网计 费标识和月艮务质量信息， 艮务质量信息包括月艮务质量等级标识以及分配与保 持优先级； 应用功能实体向策略和计费规则功能实体返回确认消息； 应用功 能实体向计费***上报应用层计费信息， 应用层计费信息包括接入网计费标 识和艮务质量信息。 另一方面， 在本发明的实施例中， 还提供了一种用于演进分组***的计 费***， 包括： 访问接受模块， 用于接受用户的业务访问； 上报模块， 用于 上报被访问业务的承载层计费信息和应用层计费信息， 应用层计费信息包括 被访问业务中数据流的服务质量信息； 计费模块， 用于根据承载层计费信息 和应用层计费信息进行计费。 进一步地， 在上述的计费***中， 服务质量信息包括服务质量等级标识 以及分配与保持优先级。 另一方面， 在本发明的实施例中， 还提供了一种用于演进分组***的计 费信息关联方法， 包括以下步骤： 策略计费规则功能实体向应用功能实体上 报数据流和数据流的服务质量信息； 应用功能实体釆用服务质量信息进行计 费信息关联。 进一步地， 在上述的计费信息关联方法中， 月艮务质量信息包括月艮务质量 等级标识以及分配与保持优先级。 进一步地， 在上述的计费信息关联方法中， 应用功能实体在发送给计费 ***的计费信息中包含服务质量信息用于计费关联。 进一步地， 在上述的计费信息关联方法中， 应用功能实体将数据流和数 据流的服务质量信息发送给应用服务器， 应用服务器在发送给计费***的计 费信息中包含服务质量信息用于计费关联。 因为上 4艮给计费***的应用层计费信息除了 包括被访问业务的
Access-Network-Charging-Identifier,还包括被访问业务中数据流的 QoS信息， 进而使得计费***获知的应用层计费信息也达到了 QoS的数据流级别， 即承 载层计费信息与应用层计费信息的精度一致， 实现了对被访问业务的正确计 费， 所以克服了相关技术中用于演进分组***的计费方法当 S-GW与 P-GW 之间釆用 PMIPv6协议时， 上报到计费***的承载层计费信息达到相同 QoS 的数据流级别， 而上报到计费***的应用层计费信息仅达到 PDN连接级别， 即承载层计费信息与应用层计费信息的精度不一致， 从而导致无法正确计费 的问题。 附图说明 此处所说明的附图用来提供对本发明的进一步理解， 构成本申请的一部 分， 本发明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的 不当限定。 在附图中： 图 1示出了根据相关技术的非漫游状态 3GPP网络的 EPS结构图； 图 2示出了支持 EPC动态策略计费控制 PCC的结构图； 图 3 示出了才艮据本发明实施例的用于演进分组***的计费方法的流程 图； 图 4示出了 居本发明优选实施例一的计费方法的流程图； 图 5示出了才艮据本发明优选实施例二的计费方法的流程图； 图 6示出了 居本发明实施例的计费***的结构框图； 图 7 示出了根据本发明实施例的用于 EPS 的计费信息关联方法的流程 图。 具体实施方式 需要说明的是， 在不冲突的情况下， 本申请中的实施例及实施例中的特 征可以相互组合。 下面将参考附图并结合实施例来详细说明本发明。 图 3 示出了才艮据本发明实施例的用于演进分组***的计费方法的流程 图， 该方法包括以下步 4聚： 步骤 S 101 , EPS接受用户的业务访问； 步骤 S 102,向计费***上 4艮被访问业务的 7 载层计费信息和应用层计费 信息， 应用层计费信息包括被访问业务的数据流的 QoS信息； 步骤 S 103 , 计费***根据承载层计费信息和应用层计费信息进行计费。 本实施例中的 EPS业务首先接受用户访问， 然后向计费***上 4艮被访问 业务的承载层计费信息和应用层计费信息， 承载层计费信息包括被访问业务 中数据流的 Access-Network-Charging-Identifier和 QoS信息， 应用层计费信 息中除了包括数据流的 Access-Network-Charging-Identifier之外，还包括数据 流的 QoS 信息， 最后计费***根据承载层计费信息和应用层计费信息中的 Access-Network-Charging-Identifier和 QoS信息进行计费。因为上 4艮给计费系 统的应用层计费信息包括被访问业务中数据流的 QoS信息，进而使得计费系 统获知的应用层计费信息也达到了 QoS的数据流级别， 即承载层计费信息与 应用层计费信息的精度一致， 实现了对被访问业务的正确计费， 所以克月艮了 相关技术中用于演进分组***的计费方法当 S-GW 与 P-GW 之间釆用 PMIPv6协议时， 上报到计费***的承载层计费信息达到相同 QoS的数据流 级别， 而上报到计费***的应用层计费信息仅达到 PDN 连接级别， 即承载 层计费信息与应用层计费信息的精度不一致，从而导致无法正确计费的问题。 需要说明的是， 上述的承载层计费信息和应用层计费信息可以由不同的 主体上报， 例如， 承载层计费信息由 EPS中的 P-GW/PCEF上报， 而应用层 计费信息由 AF 实体或应用月艮务器上 4艮。 同时， 上述上 4艮的过程可以不限定 承载层计费信息和应用层计费信息的上报顺序， 即， 既可以先上报承载层计 费信息再上报应用层计费信息， 也可以先上报应用层计费信息再上报承载层 计费信息。 优选地， 在上述的计费方法中， QoS信息包括 QCI以及 ARP。 本优选实施例中的 QoS信息为 QCI和 ARP的组合， 其中 QCI为 QoS 等级标识， ARP为分配与保持优先级， 故以 QCI和 ARP的组合作为 QoS信 息， 可清楚地表明被访问业务的数据流的计费信息。 优选地， 在上述的计费方法中， 步骤 S 101具体包括： PCEF实体根据接 收 的 建 立 IP-CAN 会 话 请 求 消 息 为 IP-CAN 会 话 分 配 Access-Network-Charging-Identifier; 建立 IP-CAN 会话； 业务通过 IP-CAN 会话接受用户访问。 本优选 实施例 中 首先 由 PCEF 实体为 IP-CAN 会话分配
Access-Network-Charging-Identifier, 其可用来表示被访问业务的 载层计费 情况， 然后建立 IP-CAN会话， 最后业务通过 IP-CAN会话接受用户访问。 本实施例生成了 Access-Network-Charging-Identifier , 以告知计费***有关承 载层的计费情况， 还建立了 IP-CAN会话， 为用户对业务的访问提供了基础。 优选地， 在上述的计费方法中， 步骤 S 101中的 PCEF实体才艮据接收的建 立 IP-CAN 会 话 请 求 消 息 为 IP-CAN 会 话 分 配 Access-Network-Charging-Identifier具体包括： BBERF实体与 PCRF实体建立 网关控制会话； PCRF实体制定默认 PCC规则和默认 QoS规则； BBERF实 体向 PCEF实体发送建立 IP-CAN会话请求消息； PCRF实体将默认 QoS规 则下发给 BBERF实体； BBERF实体安装默认 QoS规则； PCEF实体为 IP-CAN 会话分配 Access-Network-Charging-Identifier; PCEF实体向 PCRF实体发送 建立 IP-CAN 会话指示消 息， 建立 IP-CAN 会话指示消 息包括 Access-Network-Charging-Identifier。 本优选实施例中的 BBERF驻留在 S-GW中， PCEF驻留在 P-GW中，故 需要首先建立起网关控制会话来实现 BBERF实体与 PCEF实体之间的信息 交互， 在建立过程中， PCRF根据用户的签约信息， 制定承载的默认 PCC规 则和默认 QoS规则， 并将默认 QoS规则下发给 BBERF, BBERF进行安装， 驻留有 BBERF的网关（如 S-GW ) 向驻留有 PCEF的网关 （如 P-GW )发送 建立 IP-CAN会话请求消息， 实现时该消息为代理绑定更新请求消息， 驻留 有 PCEF 的 网 关 为 请 求 建 立 的 IP-CAN 会 话 分 配 Access-Network-Charging-Identifier。 PCEF向 PCRF发送建立 IP-CAN会话指 示消息， 消息中携带该 Access-Network-Charging-Identifier。 本实施例实现了 PCEF实体为 IP-CAN会话分配 Access-Network-Charging-Identifier。 优选地， 在上述的计费方法中， 步骤 S 101中的建立 IP-CAN会话具体包 括： PCRF实体根据默认 PCC规则进行策略决策，得到第一 PCC规则； PCRF 实体向 PCEF实体发送建立 IP-CAN会话确认消息， 建立 IP-CAN会话确认 消息包括第一 PCC规则； PCEF实体安装第一 PCC规则； PCEF实体与计费 ***进行交互， 建立计费会话； PCEF实体向 BBERF实体发送建立 IP-CAN 会话确认消息， IP-CAN会话建立完成。 本优选实施例首先由 PCRF 进行策略决策， 可能^ ί'爹改之前制定的默认
PCC规则， PCRF实体向 PCEF实体下发包括有第一 PCC规则的建立 IP-CAN 会话确认消息， PCEF安装 PCC规则， PCEF与 OCS进行交互， 建立在线计 费会话，驻留有 PCEF的网关（如 P-GW )向驻留有 BBERF的网关（如 S-GW ) 返回建立 IP-CAN会话确认消息， 该消息实现时为代理绑定更新确认消息。 本实施例建立了 IP-CAN会话， 使得用户可通过 IP-CAN会话请求业务。 优选地， 在上述的计费方法中， 步骤 S 101中的业务通过 IP-CAN会话接 受用户访问具体包括： 用户通过 IP-CAN会话与 AF 实体交互； AF 实体向 PCRF 实体发送与 用 户 协商后 的 协商后 QoS 信息 ， 并订 阅 Access-Network-Charging-Identifier的更新通知； PCRF实体保存十办商后 QoS 信息， 并向 AF实体返回确认消息； PCRF实体才艮据协商后 QoS信息制定第 二 PCC规则和第二 QoS规则， 第二 QoS规则包括 QCI以及 ARP。 本优选实施例首先由用户进行业务访问，与 AF实体进行应用层交互后 ,
AF实体将与用户协商后的协商后 QoS信息提供给 PCRF, 同时 AF实体订阅 Access-Network-Charging-Identifier的更新通知， PCRF保存协商后 QoS信息 等业务信息， 并返回确认消息， PCRF 根据用户的签约信息， 网络策略以及 业务信息进行策略决策， 制定 PCC规则和 QoS规则， PCRF与 BBERF进行 交互， 将 QoS规则下发给 BBERF, BBERF进行安装。 本实施例实现了业务 通过 IP-CAN会话接受用户访问。 优选地， 在上述的计费方法中， 步骤 S 102具体包括： PCRF实体将第二 PCC规则下发给 PCEF实体， 将第二 QoS规则下发给 PCEF实体和 BBERF 实体； PCEF实体安装第二 PCC规则， BBERF实体安装第二 QoS规则； PCEF 实体向计费 系 统上报承载层计费信息， 承载层计费信息 包括 Access-Network-Charging-Identifier和 QoS信息， QoS信息包括 QCI以及 ARP。 本优选实施例首先由 PCRF 实体将第二 QoS规则下发给 PCEF 实体和 BBERF实体， BBERF实体安装第二 QoS规则， PCEF实体向计费***上 4艮 载层计费信息， 包括 Access-Network-Charging-Identifier和 QoS信息， QoS 信息包括 QCI和 ARP。 本实施例中 PCEF实体为 UE的一个 PDN连接产生 Access-Network-Charging-Identifier, 其中为具有相同 QoS (即 QCI和 APR 的组合）的数据流提供一个 AVP, 携带具有相同 QoS数据流的计费信息， 并 且用数据流所具有的 QoS 标识这个 AVP。 这样， 对于计费***来说， 从 P-GW/PCEF上 4艮上来的计费信息 ^"度可达到 QoS的数据流级别。 优选地， 在上述的计费方法中， 步骤 S 103具体包括： PCRF实体向 AF 实体提供 Access-Network-Charging-Identifier和 QoS信息， QoS信息包括 QCI 以及分配与保持优先级； AF实体向 PCRF实体返回确认消息； AF实体向应 用服务器提供 Access-Network-Charging-Identifier和 QoS信息； 应用服务器 向 计 费 系 统上报应 用 层计 费 信 息 ， 应 用 层计 费 信 息 包括 Access-Network-Charging-Identifier和 QoS信息。 本优选实施例首先由 PCRF向 PCEF发送策略计费规则提供消息， PCEF 安装规则后， 返回策略计费规则提供确认消息， 由于 AF 实体订阅了 Access-Network-Charging-Identifier的更新通 口， PCRF向 AF实体提供该信 息， 信息精确到 AF实体提供的每个 IP流对应的接入网计费标识和 PCRF为 该 IP流 ·ί受权的 QoS信息 （ QCI和 ARP的组合 ), AF实体向 PCRF返回确认 消息， AF实体再^]夺 Access-Network-Charging-Identifier消息和 QoS信息（ QCI 和 ARP的组合）提供给应用服务器， 最后由应用服务器向计费***上报应用 层计费信息，应用层计费信息包括 Access-Network-Charging-Identifier消息和 QoS信息 （ QCI和 ARP的组合；)。 因为上 4艮给计费***的应用层计费信息除 了包括被访问业务的 Access-Network-Charging-Identifier, 还包括被访问业务 中数据流的 QoS 信息， 进而使得计费***获知的应用层计费信息也达到了 QoS的数据流级别， 即实现了与^载层计费信息的精度的统一。 优选地， 在上述的计费方法中， 步骤 S 103具体包括： PCRF实体向 AF 实体提供 Access-Network-Charging-Identifier和 QoS信息， QoS信息包括 QCI 以及分配与保持优先级； AF实体向 PCRF实体返回确认消息； AF实体向计 费 系 统 上 报 应 用 层 计 费 信 息 ， 应 用 层 计 费 信 息 包 括 Access-Network-Charging-Identifier和 QoS信息。 本优选实施例首先由 PCRF向 PCEF发送策略计费规则提供消息， PCEF 安装规则后， 返回策略计费规则提供确认消息， 由于 AF 实体订阅了 Access-Network-Charging-Identifier的更新通 口， PCRF向 AF实体提供该信 息， 信息精确到 AF实体提供的每个 IP流对应的接入网计费标识和 PCRF为 该 IP流 ·ί受权的 QoS信息 （ QCI和 ARP的组合 ), AF实体向 PCRF返回确认 消息， AF实体将 Access-Network-Charging-Identifier消息和 QoS信息 （ QCI 和 ARP的组合）作为应用层计费信息向计费***上报。 因为上报给计费*** 的 应 用 层 计 费 信 息 除 了 包 括 被 访 问 业 务 的 Access-Network-Charging-Identifier,还包括被访问业务中数据流的 QoS信息， 进而使得计费***获知的应用层计费信息也达到了 QoS的数据流级别， 即实 现了与承载层计费信息的精度的统一。 为了帮助理解上述实施例， 下面进一步描述本发明的其他多个优选实施 例。 图 4示出了才艮据本发明优选实施例一的计费方法的流程图， 该方法包括 实现了 UE建立 PDN连接， AF实体提供业务信息， PCRF将业务信息中包 含的各 IP数据流与其关联的接入网计费标识和 QoS信息上报给 AF实体，具 体包括以下步 4聚: 步骤 401 , BBERF实体收到建立 IP-CAN会话请求消息后， 与 PCRF实 体交互建立网关控制会话， 在这个过程中， PCRF实体根据用户的签约信息， 制定默认承载的 PCC规则和 QoS规则， 并将 QoS规则下发给 BBERF实体， BBERF实体进行安装； 步骤 402,驻留有 BBERF的网关（如 S-GW )向驻留有 PCEF的网关（如 P-GW )发送建立 IP-CAN会话请求消息， 实现时该消息为代理绑定更新请求 消息； 步骤 403 , 驻留有 PCEF的网关为请求建立的 IP-CAN会话分配接入网 计费标识， PCEF实体向 PCRF实体发送建立 IP-CAN会话指示消息， 消息中 携带接入网计费标识； 步骤 404, PCRF 实体进行策略决策， 可能修改之前制定的默认承载的 PCC规则； 步骤 405 , PCRF实体向 PCEF实体返回建立 IP-CAN会话确认消息， 下 发 PCC规则， PCEF实体安装 PCC规则； 步骤 406, PCEF实体与 OCS进行交互， 建立在线计费会话； 步骤 407,驻留有 PCEF的网关（如 P-GW )向驻留有 BBERF的网关（如 S-GW )返回建立 IP-CAN会话确认消息， 该消息实现时为代理绑定更新确认 消息， 至此， IP-CAN会话建立完成， 用户可以请求业务了； 步骤 408, 用户进行业务访问， 与 AF实体进行应用层交互后， AF实体 将与用户协商后的 QoS 信息提供给 PCRF 实体， 同时 AF 实体订阅 Access-Network-Charging-Identifier信息通知， 在本实施例中， AF 实体提供 的业务包含两个 IP数据流， 这里用 IP flow 1和 IP flow2进行标识， 每个 IP 数据流都有其请求的 QoS; 步骤 409, PCRF实体保存业务信息， 返回确认消息； 步骤 410, PCRF实体根据用户的签约信息， 网络策略以及业务信息进行 策略决策， 制定 PCC规则和 QoS规则， 在本实施例中， PCRF为 IP flowl制 定的 PCC规则用 PCC Rulel表示， 规则中的 QCI和 ARP用 QCI1和 ARP1 表示，为 IP flow2制定的 PCC规则用 PCC Rule2表示，规则中的 QCI和 ARP 用 QCI2和 ARP2表示； 步骤 411 , PCRF实体与 BBERF实体进行交互，将 QoS规则下发给 BBERF 实体， BBERF实体进行安装； 步骤 412, PCRF 实体向 PCEF 实体发送策略计费规则提供消息， 下发
PCC Rulel和 PCC Rule2; 步骤 413 , PCEF实体安装规则后， 返回策略计费规则提供确认消息； 步骤 414, 由于 AF实体订阅了 Access-Network-Charging-Identifier信息 的通知， PCRF实体向 AF实体提供该信息， 信息精确到 AF实体提供的每个 IP 流对应的接入网计费标识和 PCRF 实体为该 IP数据流授权的 QoS信息 ( QCI和 ARP ), 在本实施例中， IP flowl对应的信息包括接入网计费标识、 QCI1和 ARP1 , IP flow2对应的信息包括接入网计费标识、 QCI2和 ARP2; 步骤 415 , AF实体向 PCRF实体返回确认消息。 至此， AF实体获取了每个 IP流对应的计费信息， 包括接入网计费标识、 QCI、 ARP。 AF实体将接入网计费标识、 QCI、 ARP发送给其他应用月艮务器， 应 用 服 务 器 向 OCS 上 报 的 应 用 层 计 费 信 息 是 携 带 Access-Network-Charging-Identifier, QCI、 ARP以便 OCS进行与 载层计费 信息的关联。 当然 AF实体也可以同时向 OCS上报计费信息， 计费信息中包 含 Access-Network-Charging-Identifier、 QCI、 ARP。 总之， 从 AF 实体角度 看， 其釆用获取的接入网计费标识、 QCI、 ARP用于计费信息关联。 本优选实施例一中， 若 PCRF对 IP flowl和 IP flow2的 QoS ·ί受权 ( QCI 和 ARP ) 是相同的 （ £设用 QCIa, ARPa表示）， 那么 PCRF 实体在向 AF 实 体 上 4艮 IP flowl 和 IP flow2 对 应 的 信 息 包 括 Access-Network-Charging-Identifier、 QCIa和 ARPa。 图 5示出了才艮据本发明优选实施例二的计费方法的流程图， 本实施例描 述的是第二实施例中的用户建立 IP-CAN会话访问业务后， 由于网络策略、 或 AF实体提供的业务信息的变化导致 PCRF实体需要修改应用层计费信息 的流程， 具体包括以下步 4聚： 步骤 501 , 由于网络策略或 AF实体提供的业务信息变化， PCRF实体进 行策略决策， 制定 PCC规则和 QoS规则， 在本实施例中， PCRF实体修改了 对 IP flowl的 QoS ·ί受权， ARP1 4爹改为 ARP1，； 步骤 502, PCRF实体与 BBERF实体进行交互，下发^ ί'爹改后的 QoS规则； 步骤 503 , PCRF实体向 PCEF实体发送策略和计费规则提供消息， 消息 中携带^ ί'爹改后的 PCC规则 PCC Rulel'； 步骤 504, PCEF实体更新规则， 并返回确认消息； 步 骤 505 , PCRF 实 体 向 AF 实 体 上 4艮 新 的 Access-Network-Charging-Identifier信息， 包含 IP flow 1对应的接入网计费标 识和 PCRF实体新 ·ί受权的 QoS信息， QCI1和 ARP1，； 步 4聚 506, AF实体保存信息后返回确认消息。
PCRF实体可仅^ ί'爹改 QCI或者同时^ ί'爹丈 QCI和 ARP。 PCRF实体也可以 将相应的爹改上 4艮给 AF实体。
AF实体获取了 IP flowl 4爹改后对应的应用层计费标识信息，包括接入网 计费标识、 QCI1、 ARP1，。 AF 实体将给信息发送给应用月艮务器， 应用月艮务 器向 OCS上报计费信息是携带接入网计费标识、 QCI 1、 ARP 1 '以便 OCS进 行与承载层计费信息的关联。当然 AF实体也可以同时向 OCS上报计费信息， 计费信息中包含 Access-Network-Charging-Identifier、 QCI1、 ARP1，。 总之， 从 AF实体角度看， AF实体釆用获取的接入网计费标识、 QCI、 ARP是用于 计费信息关联。 图 6示出了才艮据本发明实施例的计费***的结构框图， 该***可以用于 实现上述计费方法。 该***包括： 访问接受模块 10, 用于接受用户的业务访问； 上报模块 20 , 连接至访问接受模块 10 , 用于上报访问接受模块 10的被 访问业务的承载层计费信息和应用层计费信息， 应用层计费信息包括数据流 的 QoS信息； 计费模块 30 , 连接至上报模块 20, 用于根据上报模块 20上报的承载层 计费信息和应用层计费信息进行计费。 本实施例中的计费***首先釆用访问接受模块 10 对演进分组***的业 务进行访问， 然后上报模块 20 向计费***上报被访问业务的承载层计费信 息 和 应 用 层 计 费 信 息 ， 承 载 层 计 费 信 息 包 括 Access-Network-Charging-Identifier和 QoS信息，应用层计费信息中除了包括 数据流的 Access-Network-Charging-Identifier, 还包括数据流的 QoS信息， 最 后釆用计费模块 30 根据承载层计费信息和应用层计费信息中的 Access-Network-Charging-Identifier和 QoS信息进行计费。因为上 4艮给计费系 统的应用层计费信息包括被访问业务中数据流的 QoS信息，进而使得计费系 统获知的应用层计费信息也达到了 QoS的数据流级别， 即承载层计费信息与 应用层计费信息的精度一致， 实现了对被访问业务的正确计费， 所以克月艮了 相关技术中用于演进分组***的计费***当 S-GW 与 P-GW 之间釆用 PMIPv6协议时，上报到计费***的承载层计费信息达到 QoS的数据流级别， 而上 4艮到计费***的应用层计费信息仅达到 PDN 连接级别， 即^载层计费 信息与应用层计费信息的精度不一致， 从而导致无法正确计费的问题。 优选地， 在上述的计费***中， QoS信息包括 QCI以及 ARP。 本优选实施例中的 QoS信息为 QCI和 ARP的组合， 其中 QCI为 QoS 等级标识， ARP为分配与保持优先级， 故以 QCI和 ARP的组合作为 QoS信 息， 可清楚地表明被访问业务的数据流的计费信息。 另一方面， 在本发明的实施例中， 还提供了一种用于 EPS的计费信息关 联方法。 图 7示出了根据本发明实施例的用于 EPS的计费信息关联方法的流 程图， 包括以下步 4聚： 步骤 S701 , PCRF实体向 AF实体上报数据流和数据流的 QoS信息。 步骤 S702, AF实体釆用 QoS信息进行计费信息关联。 本实施例中首先由 PCRF实体向 AF实体上报数据流和数据流的 QoS信 息， 并根据 QoS信息进行计费。 因为上报给计费***的应用层计费信息包括 数据流的 QoS信息， 故使得计费***获知的应用层计费信息达到了 QoS 的 数据流级别， 进而实现了正确计费， 所以克服了相关技术中用于 EPS的计费 方法当 S-GW 与 P-GW 之间釆用 PMIPv6 协议时， 仅向 AF 实体上 4艮 Access-Network-Charging-Identifier,故对应用层的计费仅能精确到 PDN连接 级别， 从而导致无法正确计费的问题。 优选地， 在上述的计费信息关联方法中， QoS信息包括 QCI以及 ARP。 本优选实施例中的 QoS信息为 QCI和 ARP的组合， 其中 QCI为 QoS 等级标识， ARP为分配与保持优先级， 故以 QCI和 ARP的组合作为 QoS信 息， 可清楚地表明被访问业务的数据流的计费信息。 优选地， 在上述的计费信息关联方法中， AF 实体在发送给计费***的 计费信息中包含 QoS信息用于计费关联。 本优选实施例中由 AF 实体直接向计费***发送应用层计费信息， 其中 包含有用于计费关联的 QoS信息。 因为发送给计费***的应用层计费信息包 括了 QoS信息， 进而使得计费***获知的应用层计费信息也达到了 QoS 的 数据流级别， 即实现了与^载层计费信息的关联。 优选地， 在上述的计费信息关联方法中， AF 实体将数据流和数据流的 QoS信息发送给应用服务器， 应用服务器在发送给计费***的计费信息中包 含 QoS信息用于计费关联。 本优选实施例中由 AF实体先向应用服务器发送数据流和数据流的 QoS 信息， 再由应用服务器向计费***发送应用层计费信息， 其中包含有用于计 费关联的 QoS信息。 因为发送给计费***的应用层计费信息包括了 QoS信 息， 进而使得计费***获知的应用层计费信息也达到了 QoS的数据流级别， 即实现了与承载层计费信息的关联。 从以上的描述中， 可以看出， 本发明上述的实施例使得计费***获知的 应用层计费信息也达到了 QoS的数据流级别， 即^载层计费信息与应用层计 费信息的精度一致， 实现了对被访问业务的正确计费。 显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布 在多个计算装置所组成的网络上， 可选地， 它们可以用计算装置可执行的程 序代码来实现， 从而， 可以将它们存储在存储装置中由计算装置来执行， 或 者将它们分别制作成各个集成电路模块， 或者将它们中的多个模块或步骤制 作成单个集成电路模块来实现。 这样， 本发明不限制于任何特定的硬件和软 件结合。 以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本 领域的技术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和 原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护 范围之内。

Claims

权 利 要 求 书 一种用于演进分组***的计费方法， 其特征在于， 包括以下步^^
所述演进分组***接受用户的业务访问；
向计费***上报被访问业务的承载层计费信息和应用层计费信息， 所述应用层计费信息包括所述被访问业务中数据流的月艮务质量信息； 所述计费***根据所述承载层计费信息和所述应用层计费信息进行 计费。 根据权利要求 1所述的计费方法， 其特征在于， 所述服务质量信息包括 月艮务质量等级标识以及分配与保持优先级。 根据权利要求 2所述的计费方法， 其特征在于， 所述演进分组***接受 用户的业务访问具体包括： 策略和计费执行功能实体根据接收的建立 IP 连接接入网会话请求 消息为所述 IP连接接入网会话分配所述接入网计费标识；
建立所述 IP连接接入网会话；
所述业务通过所述 IP连接接入网会话接受所述用户访问。 根据权利要求 3所述的计费方法， 其特征在于， 所述策略和计费执行功 能实体根据接收的所述建立 IP连接接入网会话请求消息为所述 IP连接 接入网会话分配所述接入网计费标识具体包括：
承载绑定和事件报告功能实体与所述策略和计费规则功能实体建立 网关控制会话；
所述策略和计费规则功能实体制定默认策略计费控制规则和默认服 务质量规则；
所述策略和计费规则功能实体将所述默认服务质量规则下发给所述 承载绑定和事件报告功能实体；
所述承载绑定和事件报告功能实体安装所述默认服务质量规则； 所述承载绑定和事件报告功能实体向所述策略和计费执行功能实体 发送所述建立 IP连接接入网会话请求消息； 所述策略和计费执行功能实体为所述 IP 连接接入网会话分配所述 接入网计费标识；
所述策略和计费执行功能实体向所述策略和计费规则功能实体发送 所述建立 IP连接接入网会话指示消息， 所述建立 IP连接接入网会话指 示消息包括所述接入网计费标识。 才艮据权利要求 4所述的计费方法， 其特征在于， 建立所述 IP连接接入网 会话包括：
所述策略和计费规则功能实体进行策略决策， 得到第一策略计费控 制规则；
所述策略和计费规则功能实体向所述策略和计费执行功能实体发送 建立 IP连接接入网会话确认消息， 所述建立 IP连接接入网会话确认消 息包括所述第一策略计费控制规则；
所述策略和计费执行功能实体安装所述第一策略计费控制规则； 所述策略和计费执行功能实体与所述计费***进行交互， 建立计费 会话；
所述策略和计费执行功能实体向所述承载绑定和事件报告功能实体 发送所述建立 IP连接接入网会话确认消息， 所述 IP连接接入网会话建 立完成。 才艮据权利要求 5所述的计费方法， 其特征在于， 所述业务通过所述 IP连 接接入网会话接受所述用户访问具体包括：
所述用户通过所述 IP连接接入网会话与应用功能实体交互； 应用功能实体向所述策略和计费规则功能实体发送与所述用户协商 后的协商后月艮务质量信息， 并订阅所述接入网计费标识的更新通知； 所述策略和计费规则功能实体保存所述协商后服务质量信息， 并向 所述应用功能实体返回确认消息；
所述策略和计费规则功能实体根据所述协商后服务质量信息制定第 二策略计费控制规则和第二服务质量规则， 所述第二服务质量规则包括 所述艮务质量等级标识以及所述分配与保持优先级。
7. 根据权利要求 6所述的计费方法， 其特征在于， 向所述计费***上报所 述被访问业务的所述承载层计费信息包括：
所述策略和计费规则功能实体将所述第二策略计费控制规则下发给 所述策略和计费执行功能实体， 将所述第二服务质量规则下发给所述承 载绑定和事件 4艮告功能实体；
所述策略和计费执行功能实体安装所述第二策略计费控制规则， 所 述承载绑定和事件报告功能实体安装所述第二服务质量规则；
所述策略和计费执行功能实体向所述计费***上报所述承载层计费 信息， 所述承载层计费信息包括所述接入网计费标识和所述服务质量信 息， 所述艮务质量信息包括所述艮务质量等级标识以及所述分配与保持 优先级。
8. 根据权利要求 6所述的计费方法， 其特征在于， 向所述计费***上报所 述被访问业务的所述应用层计费信息包括：
所述策略和计费规则功能实体向所述应用功能实体提供所述接入网 计费标识和所述服务质量信息， 所述服务质量信息包括所述服务质量等 级标识以及所述分配与保持优先级；
所述应用功能实体向所述策略和计费规则功能实体返回确认消息； 所述应用功能实体向应用服务器提供所述接入网计费标识和所述服 务质量信息；
所述应用服务器向所述计费***上报所述应用层计费信息， 所述应 用层计费信息包括所述接入网计费标识和所述月艮务质量信息。
9. 根据权利要求 6所述的计费方法， 其特征在于， 向所述计费***上报所 述被访问业务的所述应用层计费信息还包括：
所述策略和计费规则功能实体向所述应用功能实体提供所述接入网 计费标识和所述服务质量信息， 所述服务质量信息包括所述服务质量等 级标识以及所述分配与保持优先级；
所述应用功能实体向所述策略和计费规则功能实体返回确认消息； 所述应用功能实体向所述计费***上 ·ί艮所述应用层计费信息， 所述 应用层计费信息包括所述接入网计费标识和所述月艮务质量信息。
10. —种用于演进分组***的计费***， 其特征在于， 包括： 访问接受模块， 用于接受用户的业务访问；
上报模块， 用于上报被访问业务的承载层计费信息和应用层计费信 息 ,所述应用层计费信息包括所述被访问业务中数据流的月艮务质量信息； 计费模块， 用于根据所述承载层计费信息和所述应用层计费信息进 行计费。
11. 居权利要求 10所述的计费***， 其特征在于， 所述月艮务质量信息包括 月艮务质量等级标识以及分配与保持优先级。
12. 一种用于演进分组***的计费信息关联方法， 其特征在于， 包括以下步 骤：
策略计费规则功能实体向应用功能实体上 4艮数据流和所述数据流的 服务质量信息；
所述应用功能实体釆用所述服务质量信息进行所述计费信息的关 联。
13. 居权利要求 12所述的方法， 其特征在于， 所述艮务质量信息包括艮务 质量等级标识以及分配与保持优先级。
14. 根据权利要求 12或 13所述的方法， 其特征在于， 所述应用功能实体在 发送给计费***的计费信息中包含所述服务质量信息用于计费关联。
15. 根据权利要求 12或 13所述的方法， 其特征在于， 所述应用功能实体将 数据流和所述数据流的月艮务质量信息发送给应用月艮务器， 所述应用月艮务 器在发送给计费***的计费信息中包含所述服务质量信息用于计费关 联。
PCT/CN2010/073249 2009-07-08 2010-05-26 用于演进分组***的计费方法及*** WO2011003307A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN 200910158938 CN101945367A (zh) 2009-07-08 2009-07-08 用于演进分组***的计费方法及装置
CN200910158938.5 2009-07-08

Publications (1)

Publication Number Publication Date
WO2011003307A1 true WO2011003307A1 (zh) 2011-01-13

Family

ID=43428768

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/073249 WO2011003307A1 (zh) 2009-07-08 2010-05-26 用于演进分组***的计费方法及***

Country Status (2)

Country Link
CN (1) CN101945367A (zh)
WO (1) WO2011003307A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102833718B (zh) * 2011-06-16 2018-12-21 中兴通讯股份有限公司 支持非3gpp接入的演进分组核心网计费方法及***
CN103634125A (zh) * 2012-08-28 2014-03-12 镇江睿泰信息科技有限公司 一种基于动态流程组合的网络服务计费方法
EP3883181A1 (en) * 2014-10-28 2021-09-22 Convida Wireless, LLC Methods and apparatuses for service layer charging correlation with underlying networks
CN107454579B (zh) * 2016-05-30 2020-02-25 普天信息技术有限公司 一种lte网络支持计费的s1接口缓存加速方法、***及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101009571A (zh) * 2006-01-25 2007-08-01 华为技术有限公司 一种计费关联的方法
CN101141821A (zh) * 2007-09-30 2008-03-12 中兴通讯股份有限公司 一种无线通信网络的策略和计费执行功能节点定位方法
CN101163022A (zh) * 2006-10-13 2008-04-16 华为技术有限公司 一种点对点通信计费方法及通讯***以及计费装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101009571A (zh) * 2006-01-25 2007-08-01 华为技术有限公司 一种计费关联的方法
CN101163022A (zh) * 2006-10-13 2008-04-16 华为技术有限公司 一种点对点通信计费方法及通讯***以及计费装置
CN101141821A (zh) * 2007-09-30 2008-03-12 中兴通讯股份有限公司 一种无线通信网络的策略和计费执行功能节点定位方法

Also Published As

Publication number Publication date
CN101945367A (zh) 2011-01-12

Similar Documents

Publication Publication Date Title
US8874715B2 (en) Charging method, system and reporting method for terminal accessing through multiple access networks
US9351325B2 (en) Policy control method and system for converged network
US8799440B2 (en) Policy and charging control method and system for multi-PDN connections of single APN
US20100281170A1 (en) Method for selecting a policy and charging rules function entity in the non-roaming scenario
WO2009135362A1 (zh) 一种隐藏拜访地网络拓扑结构的策略计费控制的方法
WO2011097911A1 (zh) 策略和计费规则功能实体的选择方法、装置及***
WO2010006491A1 (zh) 一种事件触发器的下发和安装方法
WO2012075875A1 (zh) 一种消费限制业务的签约和执行方法及***
WO2011063688A1 (zh) 策略和计费规则功能实体的选择方法及***
WO2012006909A1 (zh) 一种上报固网接入信息的方法及***
WO2010135931A1 (zh) 一种实现制定业务计费策略的方法及***
WO2016201999A1 (zh) 一种第三方应用的计费方法、装置及应用功能设备
WO2012003760A1 (zh) 信息传递方法和***
WO2011085614A1 (zh) 在全业务融合网络中控制资源的方法和***
WO2011085621A1 (zh) 业务处理方法及***
WO2013060170A1 (zh) 一种提供基于lipa承载的计费支持的方法及装置
WO2010078761A1 (zh) 基于多接入技术的策略计费控制方法、装置和***
WO2011026385A1 (zh) 一种本地疏导漫游场景在线计费的方法和***
WO2014107985A1 (zh) 漫游本地业务的在线计费方法、h-ocs及v-ocs
WO2014094488A1 (zh) 漫游本地业务的计费策略方法及装置
WO2012071956A1 (zh) 漫游场景支持被赞助数据连接的方法、***和装置
WO2011088702A1 (zh) 在全业务融合网络中控制资源的方法和***
WO2011003307A1 (zh) 用于演进分组***的计费方法及***
WO2010105465A1 (zh) 计费标识的关联方法和装置
WO2011018020A1 (zh) 控制pcrf负载均衡的方法、***及重定向dra

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

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

Country of ref document: EP

Kind code of ref document: A1