WO2011003307A1 - Charging method and system for evolved packet system - Google Patents

Abstract

A charging method and system for an Evolved Packet System are provided, and the method comprises: the Evolved Packet System accepts a user's access to a service; reports the charging information of bearing layer of the accessed service to a charging system; and reports the charging information of application layer of the accessed service to the charging system, the charging information of application layer including the service quality information of data stream in the accessed service; and the charging system charges according to the charging information of bearing layer and the charging information of application layer. The correct charging for the accessed service is realized.

Description

TECHNICAL FIELD The present invention relates to the field of communications, and in particular to a charging method and system for an evolved packet system. BACKGROUND OF THE INVENTION Figure 1 shows an Evolved Packet System (EPS) structure diagram of a non-roaming state 3rd Generation Partnership Project (3GPP) network according to the related art, EPS evolution Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Mobility Management Entity (MME), and Serving Gateway (S-GW) Packet Data Network Gateway (P-GW), Home Subscriber Server (HSS), 3 GPP Authentication 4 Authorization and Accounting (AAA) It consists of a server and policy and charging rules function (PCRF) entity and other supporting nodes. 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. 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. System access to data anchors with access to non-3GPP systems. In the system architecture of EPS, 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. Figure 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) The function, abbreviated as PCEF, resides in the P-GW of the EPS system, and the PCRF exchanges information with the PCEF through the Gx interface. When the interface between the P-GW and the S-GW is based on the Proxy Mobile IPv6 (referred to as ΡΜΙΡν6) protocol, 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. At the same time, the application function (Application Function, abbreviated as AF) 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). 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. At the same time, 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. 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. 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. When the General Packet Radio Service Tunneling Protocol (GTP) is used between the S-GW and the P-GW, the P-GW/PCEF allocates an Access for each of the PDN connections of the UE. -Network-Charging-Identifier„ 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. 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. For 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. When the PMIPv6 protocol is used between the S-GW and the P-GW, 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. An Access-Network-Charging-Identifier. 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. In the charging information, an AVP (Attribute Value Pair) is provided for the data flow having the same QoS (ie, a combination of QCI and APR), and 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. In this way, for the charging system, 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. In the process of implementing the present invention, the inventors have found that 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. SUMMARY OF THE INVENTION 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. The accuracy is inconsistent, which leads to the problem of not being able to charge correctly. In an embodiment of the present invention, a charging method for an evolved packet system is provided, 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. Further, in the above charging method, the quality of service information includes a quality of service level identifier and an allocation and retention priority. Further, in the foregoing charging method, 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. Further, in the foregoing charging method, 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. a request message; 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. Further, in the foregoing charging method, 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. Further, in the foregoing charging method, 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. Sending the negotiated quality of service information after negotiation with the user, and subscribing to the update notification of the access network charging identifier; 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. Further, in the above charging method, 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. Further, in the foregoing charging method, 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, 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 identification and service quality information; the application server applies the application layer charging information to the charging system, and the application layer charging information includes the access network charging identifier and the monthly service quality information. Further, in the foregoing charging method, 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. On the other hand, in an embodiment of the present invention, a charging system for an evolved packet system is provided, 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. Further, in the above charging system, the quality of service information includes a quality of service level identifier and an allocation and retention priority. On the other hand, in an embodiment of the present invention, a charging information association method for an evolved packet system is provided, 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. Further, in the above charging information association method, the monthly quality information includes a monthly quality level identifier and an allocation and retention priority. Further, in the foregoing charging information association method, the application function entity includes the service quality information for the charging association in the charging information sent to the charging system. Further, in the foregoing charging information association method, 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. When 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. Inconsistent, resulting in problems that cannot be billed correctly. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the drawings: 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. A flowchart of a charging method for an evolved packet system according to an embodiment of the invention; 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. FIG. 3 is a flowchart showing a charging method for an evolved packet system according to an embodiment of the present invention, the method includes the following steps: 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. -Network-Charging-Identifier and QoS information, application layer accounting In addition to the Access-Network-Charging-Identifier including the data stream, the information includes the QoS information of the data stream. Finally, 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. Therefore, the charging method for the evolved packet system in the related art is used between the S-GW and the P-GW. When the PMIPv6 protocol is used, 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. It should be noted that the foregoing bearer layer charging information and application layer charging information may be reported by different entities. For example, 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. In addition, 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. Preferably, in the foregoing charging method, 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. Preferably, in the foregoing charging method, 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. In the preferred embodiment, 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. In this embodiment, 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. Preferably, in the foregoing charging method, 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, the establishment of 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. During the establishment process, Based on the subscription information of the user, 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. Preferably, in the foregoing charging method, 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. Preferably, in the foregoing charging method, 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. Preferably, in the foregoing charging method, 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, and 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. In this embodiment, 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. In this way, for the charging system, the charging information from the P-GW/PCEF can reach the data flow level of the QoS. Preferably, in the foregoing charging method, 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. Message, PCEF After the rule is installed, 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). The combination;). Because the application layer charging information of the charging system to the charging system includes the Access-Network-Charging-Identifier of the accessed service, the QoS information of the data flow in the accessed service, and the application layer meter obtained by the charging system. The fee information also reaches the data flow level of QoS, that is, the uniformity of the accuracy of the charging information with the carrier layer is realized. Preferably, in the foregoing charging method, 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. To assist in understanding the above embodiments, other preferred embodiments of the present invention are further described below. 4 is a flow chart showing a charging method according to a preferred embodiment 1 of the present invention. 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. Rules and QoS rules, and the QoS rules are sent to the BBERF entity, and the BBERF entity is installed; 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. After the completion, the user can request the service; 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. In this embodiment, 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 412: The PCRF entity sends a policy charging rule providing message to the PCEF entity, and sends the message

PCC Rule1 and PCC Rule2; 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, 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. In this embodiment, the information corresponding to the IP flow1 Including the access network charging identifier, QCI1 and ARP1, the information corresponding to IP flow2 includes the access network charging identifier, QCI2 and ARP2; Step 415, the AF entity returns an acknowledgement message to the PCRF entity. At this point, 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. In summary, from the perspective of the AF entity, the access network charging identifier, QCI, and ARP obtained are used for charging information association. In the first preferred embodiment, if 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. Transmitting the QoS rule after the tampering; 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. . Of course, 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. In summary, from the perspective of the AF entity, 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. Finally, 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. 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. Therefore, the charging system for the evolved packet system in the related art is used between the S-GW and the P-GW. When the PMIPv6 protocol is used, 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 accuracy of the information and application layer charging information is inconsistent, resulting in the problem of not being able to correctly charge. Preferably, in the above charging system, 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. On the other hand, in an embodiment of the present invention, a charging information association method for EPS is also provided. FIG. 7 is a flowchart of a charging information association method for an EPS according to an embodiment of the present invention, including the following steps: 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. In this embodiment, 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 charging method for the EPS in the technology, when the PM-IPv6 protocol is used between the S-GW and the P-GW, only the Access-Network-Charging-Identifier is applied to the AF entity, so the charging for the application layer can only be accurate. The problem is that the PDN connection level is not properly billed. Preferably, in the foregoing charging information association method, 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. Preferably, in the foregoing charging information association method, the AF entity includes QoS information for charging association in the charging information sent to the charging system. In the preferred embodiment, 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. . Preferably, in the foregoing charging information association method, 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. . In the preferred embodiment, 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. Obviously, those skilled in the art should understand that the above 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. Thus, 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. Various modifications and variations of the present invention are possible in the art. 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.

Claims

Claims A billing method for an evolved packet system, comprising the following steps: ^^  The evolved packet system accepts service access by a user;  Transmitting the bearer layer charging information and the application layer charging information of the accessed service to the charging system, where the application layer charging information includes monthly service quality information of the data flow in the accessed service; The bearer layer charging information and the application layer charging information are charged. The charging method according to claim 1, wherein the quality of service information comprises a monthly quality level identifier and an allocation and retention priority. The charging method according to claim 2, wherein the evolving packet system accepting the service access of the user specifically includes: the policy and charging execution function entity according to the received setup IP connection access network session request message Assigning, by the IP connection access network session, the access network charging identifier;  Establishing the IP connection access network session;  The service accepts the user access through the IP connection access network session. The charging method according to claim 3, wherein the policy and charging execution function entity allocates the IP connection access network session to the IP connection access network session according to the received IP connection access network session request message. The access network charging identifier specifically includes:  The bearer binding and event reporting function entity establishes a gateway control session with the policy and charging rule function entity;  The policy and charging rule function entity formulates a default policy charging control rule and a default service quality rule;  The policy and charging rule function entity sends the default quality of service rule to the bearer binding and event reporting function entity; The bearer binding and event reporting function entity installs the default quality of service rule; the bearer binding and event reporting function entity sends the establish IP connection access network session request message to the policy and charging execution function entity ; The policy and charging execution function entity allocates the access network charging identifier to the IP connection access network session;  The policy and charging execution function entity sends the establishing an IP connection access network session indication message to the policy and charging rule function entity, where the establishing an IP connection access network session indication message includes the access network meter Fee identification. The charging method according to claim 4, wherein the establishing the IP connection access network session comprises:  The policy and charging rule function entity performs policy decision to obtain a 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, where the establishing an IP connection access network session confirmation message includes the first policy charging control Rule  The policy and 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;  And the policy and charging execution function entity sends the establishment of an IP connection access network session confirmation message to the bearer binding and event reporting function entity, where the IP connection access network session establishment is completed. The charging method according to claim 5, wherein the accepting the user access by the service through the IP connection access network session specifically includes:  The user interacts with the application function entity through the IP connection access network session; the application function entity sends the negotiated monthly service quality information negotiated with the user to the policy and charging rule function entity, and subscribes to the An update notification of the access network charging identifier; 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 policy and charging rule function entity formulates a second policy charging control rule and a second quality of service rule according to the negotiated quality of service information, where the second quality of service rule includes the quality of service level identifier and the Assign and maintain priority. The charging method according to claim 6, wherein the reporting of the bearer layer charging information of the accessed service to the charging system comprises:  The policy and charging rule function entity sends the second policy charging control rule to the policy and charging execution function entity, and sends the second quality of service rule to the bearer binding and event. 4 obituary functional entity;  The policy and charging execution function entity installs the second policy charging control rule, and the bearer binding and event reporting function entity installs the second quality of service rule;  The policy and charging execution function entity reports the bearer layer charging information to the charging system, where the bearer layer charging information includes the access network charging identifier and the service quality information, The quality information includes the quality of service level identifier and the allocation and retention priority. The charging method according to claim 6, wherein the reporting the application layer charging information of the accessed service to the charging system comprises:  The policy and charging rule function entity provides the access network charging identifier and the service quality information to the application function entity, where the service quality information includes the quality of service level identifier and the allocation and maintaining priority Level  The application function entity returns an acknowledgement message to the policy and charging rule function entity; the application function entity provides the access network charging identifier and the service quality information to an application server;  The application server reports the application layer charging information to the charging system, where the application layer charging information includes the access network charging identifier and the monthly service quality information. The charging method according to claim 6, wherein the reporting the application layer charging information of the accessed service to the charging system further comprises:  The policy and charging rule function entity provides the access network charging identifier and the service quality information to the application function entity, where the service quality information includes the quality of service level identifier and the allocation and maintaining priority Level The application function entity returns an acknowledgement message to the policy and charging rule function entity; the application function entity sends the application layer charging information to the charging system, and the application layer charging information includes The access network charging identifier and the monthly service quality information. 10. A charging system for an evolved packet system, comprising: an access accepting module, configured to accept a user's service access;  a reporting module, configured to report bearer layer charging information and application layer charging information of the accessed service, where the application layer charging information includes monthly service quality information of the data stream in the accessed service; Charging is performed according to the bearer layer charging information and the application layer charging information. 11. The charging system according to claim 10, wherein the monthly quality information comprises a monthly quality level identifier and an allocation and retention priority. 12. A charging information association method for an evolved packet system, comprising the steps of:  The policy charging rule function entity sends the data flow and the service quality information of the data flow to the application function entity;  The application function entity uses the quality of service information to perform association of the charging information. 13. The method of claim 12, wherein the quality of service information comprises a quality of service level identifier and an allocation and retention priority. The method according to claim 12 or 13, wherein the application function entity includes the quality of service information for charging association in charging information sent to the charging system. The method according to claim 12 or 13, wherein the application function entity sends the data stream and the monthly quality information of the data stream to the application server, and the application server The service quality information is included in the charging information sent to the charging system for charging association.