WO2012171428A1

WO2012171428A1 - Charging method and system for evolved packet core supporting non-3gpp accessing

Info

Publication number: WO2012171428A1
Application number: PCT/CN2012/075744
Authority: WO
Inventors: 郭文洁; 朱春晖
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-06-16
Filing date: 2012-05-18
Publication date: 2012-12-20
Also published as: CN102833718A; CN102833718B

Abstract

A charging method for an Evolved Packet Core supporting non-3GPP accessing is provided by the present invention, which comprises: a Charging Triggering Function (CTF) generates charging information based on the evolved packet data usage of the non 3rd Generation Partnership Project (3GPP) accessing network, and sends to an offline charging gateway or an online charging system for charging. A charging system for the Evolved Packet Core supporting the non-3GPP accessing is provided by the present invention simultaneously, which can realize the aforementioned method. The present invention realizes charging based on the data flow for users which access through the non-3GPP accessing network.

Description

Evolved packet core network charging method and system supporting non-3GPP access

The present invention relates to charging technologies, and more particularly to an evolved packet core network charging method and system supporting non-3rd Generation Partnership Project (3GPP) access. Background technique

Long Term Evolution (LTE) is expected to cater to the needs of the broadband market mainly through fixed technologies in the near future. To adapt to the speed increase of the wireless side, further evolution of the core network architecture has become a key topic of 3GPP organization research. It is also an important part of the System Architecture Evolution (SAE) project, also known as EPC (Evolved Packet Core) or EPC. Evolved Packet System (EPS) is the future direction of mobile network evolution. The main features include: Full packetization, providing true pure packet access; Supporting multiple access technologies, in addition to supporting existing 3GPP system access In addition, it supports access to non-3GPP networks (such as Code Division Multiple Access (CDMA), Wireless Local Area Network (WLAN)), and supports between 3GPP networks and non-3GPP networks. Roaming and switching; support end-to-end Quality of Service (QoS) guarantees, increase support for real-time services, reduce network connection delays by simplifying network architecture and signaling procedures; The user plane performs node compression, and the Radio Network Controller (RNC) is cancelled. The core network user plane nodes can be merged into one when non-roaming.

The EPC network implements the convergence of the core network, supports the common access of various 3GPP access modes and non-3GPP networks, and supports the seamless mobility of multi-mode terminal users. The development trend of operators' full-service operations has made operators begin to operate a variety of standard networks. Support multiple network access The EPC network realizes the integration of the core network, which makes the network structure simpler and reduces the network operation cost. At the same time, the EPC network supports the seamless mobility between various access modes, which improves the usage experience of LTE users in the initial coverage of LTE deployment.

Since the EPC system supports both 3GPP access (such as LTE), trusted non-3GPP network access (such as CDMA), and untrusted non-3GPP IP network access (such as WLAN), 3GPP also defines EPCs that support non-3GPP access. The architecture diagram, in which the packet data network (PDN) gateway (GW, Gateway) is used as the core device of the access, and the access gateways of different access networks (the LTE wireless network corresponds to the S-GW, and the CDMA wireless network corresponds to the HSGW, The WLAN wireless network corresponding to the ePDG) accesses the P-GW (PDN GW) to implement access to the heterogeneous network. The home subscriber server (HSS) is the core of the EPC network authentication. In addition to supporting the LTE network authentication, the network authentication for CDMA and WLAN is first processed by the 3GPP AAA server, and finally implemented in the HSS. Access authentication and authentication.

1 is a schematic diagram of an EPC roaming architecture a supporting a non-3GPP access mode, FIG. 2 is a schematic diagram of an EPC roaming architecture b supporting a non-3GPP access mode, and FIG. 3 is a schematic diagram of an EPC roaming architecture c supporting a non-3GPP access mode. 1, FIG. 2 and FIG. 3 respectively represent three possible roaming architectures for supporting non-3GPP network access EPC (the roaming situation of P-GW located in Home-Routed of the home network). The difference between the three is that Figure 1 uses the P-GW as the anchor point for non-3GPP access and the S8, S2a and S2b interfaces, and the trusted non-3GPP (such as CDMA) access access authentication and authentication through the 3GPP AAA; Non-trusted non-3GPP (such as WLAN, etc., performs access authentication and authentication through 3GPP AAA, and user plane information accesses P-GW via ePDG. Figure 2 uses S-GW as anchor point for non-3GPP access and S8, S2a-PMIP and S2b interface; Figure 3 uses S8 and S2c interface between UE and P-GW. P-GW generates Charging ID to indicate the same IP-CAN bearer from the charging angle, ePDG can Directly learned through the GTP (GPRS Tunnel Protocol) tunnel or through policy control and accounting (PMC, Policy and Internet Protocol) (PCC, Policy and The Charging Control architecture indirectly knows this information. The ePDG generates a PDN link identifier to indicate the same IP-CAN session. The P-GW can also directly learn the information through the GTP tunnel or indirectly through the PCC architecture in PMIP mode.

Currently, for the enhanced architecture supporting the non-3GPP network access EPC of FIG. 1, FIG. 2 and FIG. 3 described above, it is known that the P-GW generates charging information through a specific charging interface, but for the access network and the home network. In the case of different operators, when the P-GW is located in the home network and the ePDG is located in the access network, the charging and reconciliation of different carrier networks cannot be completed by relying only on the charging of the P-GW. Summary of the invention

In view of this, the main objective of the present invention is to provide an evolved packet core network charging method and system supporting non-3GPP access, which can provide charging services for users accessing through non-3GPP access networks.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

An evolving packet core network charging method supporting non-3GPP access includes:

The CTF generates charging information based on the evolved packet data usage of the non-3rd Generation Partnership Project 3GPP access network and sends it to the offline charging gateway and/or the online charging system for charging.

Preferably, the CTF is set in the ePDG, and/or is disposed outside the ePDG. Preferably, the CTF is disposed outside the ePDG and is:

The CTF is set in 3GPP AAA or in other network elements.

Preferably, the offline charging gateway is provided with a CDF and a CGF.

Preferably, the CDF and the CGF are disposed in the ePDG;

Or the CDF is set in the ePDG, and the CGF is disposed outside the ePDG;

Or the CDF and the CGF are set in the 3GPP AAA;

Or the CDF is set in the 3GPP AAA, and the CGF is set in the 3GPP Outside AAA.

Preferably, when the CTF is set in the 3GPP AAA, the 3GPP AAA obtains the evolved packet data usage of the non-3GPP access network from the ePDG and/or the home serving gateway HSGW.

Preferably, when the CTF is set in another network element, the 3GPP AAA obtains charging related information of the non-3GPP access network from the other network element.

Preferably, the charging information includes an evolved packet data usage, a Charging ID, and a PDN Connection ID of the user accessed by the non-3GPP access network.

An evolved packet core network charging system supporting non-3GPP access, including a CTF, and an offline charging gateway and/or an online charging system;

The CTF is configured to generate charging information based on the evolved packet data usage of the non-3rd Generation Partnership Project 3GPP access network, and send the information to the offline charging gateway and/or the online charging system;

An offline charging gateway and/or an online charging system is configured to perform offline accounting data record generation and/or online charging credit control based on the charging information.

Preferably, the CTF is set in the evolved packet data gateway ePDG, and/or is disposed outside the ePDG.

Preferably, the CTF is set in 3GPP AAA or in other network elements.

Preferably, the offline charging gateway is provided with a CDF and a CGF.

Preferably, the CDF and the CGF are disposed in the ePDG;

Or the CDF is set in the ePDG, and the CGF is disposed outside the ePDG;

Or the CDF and the CGF are set in the 3GPP AAA;

Alternatively, the CDF is set in the 3GPP AAA, and the CGF is set outside the 3GPP AAA.

In the present invention, in the ePDG or in a network element other than the ePDG (such as in 3GPP AAA) After the network element other than the ePDG or the ePDG obtains the evolved packet data usage of the non-3GPP access network access network, the accounting information is generated and sent to the offline charging gateway and/or the online charging. The system is used for billing, thereby enabling data flow based charging for users accessing through non-3GPP access networks. DRAWINGS

FIG. 1 is a schematic diagram of an EPC roaming architecture a supporting a non-3GPP access mode;

2 is a schematic diagram of an EPC roaming architecture b supporting a non-3GPP access mode;

FIG. 3 is a schematic diagram of an EPC roaming architecture c supporting a non-3GPP access mode;

4 is a schematic diagram of an offline charging structure supporting a non-3GPP access mode according to the present invention; FIG. 5 is a schematic diagram of an online charging structure supporting a non-3GPP access mode according to the present invention; FIG. 6 is a plan for uniformly deploying an ePDG and a P-GW according to the present invention; Schematic diagram of fee interface;

7 is a schematic diagram of a charging interface for unified deployment of an ePDG and an S-GW according to the present invention;

8 is a flow chart of charging under the offline charging mechanism of the present invention;

9 is a flow chart of charging under the online charging mechanism of the present invention;

10 is a flow chart of charging under the offline charging mechanism of the present invention;

FIG. 11 is a flow chart of charging under the online charging mechanism of the present invention. The basic idea of the present invention is that the charging logic function entity CTF receives the evolved packet data usage of the non-3GPP access network access network sent by the network element for the non-3GPP access network access in the EPC. Thereafter, charging information is generated and sent to the offline charging gateway and/or the online charging system for charging; the charging system performs charging based on the charging information of the evolved packet data.

The above CTF is specifically set in the ePDG, and/or is disposed outside the ePDG. The CTF is set outside the ePDG, and the CTF is set in the 3GPP AAA or other network element.

CDF and CGF are set in the above offline charging gateway. The above CDF and CGF may be set in the ePDG; when the CDF and the CGF are set in the ePDG, the ePDG and the offline charging gateway are combined.

Alternatively, the CDF is set in the ePDG, and the CGF is set outside the ePDG; or, the CDF and the CGF are set in the 3GPP AAA; when the CDF and the CGF are set in the 3GPP AAA, the 3GPP AAA and the offline charging gateway are combined.

Alternatively, the CDF is set in 3GPP AAA, and the CGF is set in the 3GPP AAA.

When the CTF is set in the 3GPP AAA, the 3GPP AAA acquires the evolved packet data usage of the non-3GPP access network from the ePDG and/or the HSGW.

When the CTF is set in another network element, the 3GPP AAA obtains charging related information of the non-3GPP access network from the other network element.

The evolved packet core network charging system supporting non-3GPP access of the present invention will be further elaborated below with reference to the accompanying drawings.

Specifically, the evolved packet core network charging system supporting the non-3GPP access of the present invention includes a user equipment, a trusted and/or untrusted non-3GPP access network, an EPC core network element, an ePDG, and used to generate an evolved packet. The billing logic function entity of the data billing information, and the offline and/or online billing system; wherein the EPC core network network element includes an S-GW, a P-GW, an HSS, a policy control, and a billing PCC related network element, etc. The logical entity of the evolved packet data gateway and the charging information is connected to the offline/online charging system.

The evolved packet data charging logic function entity is one or more combinations of CTF, CDF, and CGF, and may be embedded in ePDG or 3GPPAAA, or may be deployed partially or completely independently.

4 is a schematic diagram of an offline charging structure supporting a non-3GPP access mode according to the present invention. As shown in FIG. 4, when the charging mode is offline charging, CTF, CDF, and CGF can be embedded in the ePDG. The Bsw interface sends the CDR file to the billing domain of the offline charging system. When the CGF is deployed independently of the ePDG, the CTF and the CDF are embedded in the ePDG. The ePDG sends the user's charging information to the CGF through the SWz interface. The CGF collects the charging information. Follow-up The post-encapsulation is a CDR file and is sent to the Billing Domain of the offline charging system through the Bsw interface. When the CDF is deployed independently of the ePDG, and the CTF is embedded in the ePDG, the ePDG generates a SWf interface to send a charging request message ACR to the CDF. FIG. 4 illustrates a possible deployment manner of a possible billing logic functional entity in the present invention. A deployment mode may be selected in the actual system. The manner in which logical entities of other possible accounting information are deployed is not enumerated.

It should be noted that the above-mentioned charging logic function entity may also be set in the 3GPP AAA, and the deployment mode is basically the same as that in the ePDG, and details are not described herein again. As shown in FIG. 4, the trusted and/or untrusted non-3GPP access network sends charging related information to the 3GPP AAA, and then the 3GPP AAA sends the charging data to the offline charging system. In this manner, the 3GPP AAA can receive charging related information from trusted and/or untrusted non-3GPP access networks, and in the following embodiments, HSGW and ePDG are used to represent trusted and untrusted, respectively. The non-3GPP access network accesses the 3GPP AAA gateway. In fact, the trusted and/or untrusted non-3GPP access network has multiple possible gateways, and is not limited thereto. For example: some fixed network access situations or some WLAN access is considered to be untrusted non-3GPP access, while some WLAN access is considered to be trusted non-3GPP access (such as China Mobile's WLAN access China Mobile) network of).

In fact, regardless of the deployment mode of the charging logic function entity, the way to interact with the ePDG or 3GPP AAA is basically determined, that is, for the offline charging structure, ePDG or 3GPP AAA (with CTF set) to CDF The ACR message is sent, and the ACR message carries the user's evolved packet data usage. After receiving the ACR message, the CDF sends the charging data request CDR message to the CGF. The CDR message carries the user's evolved packet data usage; The CDR file is generated by the packet data usage and sent to the offline charging system; the offline charging system performs charging based on the CDR file.

FIG. 5 is a schematic diagram of an online charging structure supporting a non-3GPP access mode according to the present invention. As shown in FIG. 5, when the charging mode is online charging, the CTF is embedded in the ePDG, and the ePDG passes the SWy interface and the online charging system (OCS). , Online Charging System ) Interactive Credit Control Request / Credit Control response messages for real-time online charging. The charging related information may also be sent to the 3GPP AAA by the trusted and/or untrusted non-3GPP access network, and then the online charging data is sent by the 3GPP AAA to the online charging system. For example: Passing the charging related information to the 3GPP AAA through the HSGW/ePDG (trusted and/or untrusted 3GPP network through the HSGW/ePDG access), by the 3GPP AAA (with the CTF set) through the SWo interface and the online charging system ( OCS, Online Charging System) Interactive credit control request/credit control response message for real-time online charging.

In the present invention, the ePDG can be uniformly deployed with the P-GW according to the characteristics of the different roaming architectures and the requirements of the deployment of the operator. In the architecture shown in Figure 1, the ePDG can be uniformly deployed with the P-GW. In the present invention, The so-called unified deployment is the ePDG and P-GW-body settings. FIG. 6 is a schematic diagram of a charging interface uniformly deployed by an ePDG and a P-GW according to the present invention. As shown in FIG. 6, the P-GW function sub-device is connected to an offline charging gateway CGF through an offline charging interface Ga/SWz, and performs online charging. The interface Gy/SWy is connected to the online charging system. On the offline charging interface and the online charging interface, the charging information generated by the original ePDG deployment is mapped to the charging information generated by the P-GW, and a unified new charging generated by the P-GW is generated. information.

In the present invention, the ePDG can be deployed in a unified manner with the S-GW according to the characteristics of the different roaming architectures and the requirements of the deployment of the operator. In the architecture shown in FIG. 2, the ePDG can be uniformly deployed with the S-GW. In the present invention, The so-called unified deployment is the ePDG and S-GW-body settings. FIG. 7 is a schematic diagram of a charging interface deployed by an ePDG and an S-GW according to the present invention. As shown in FIG. 7, the S-GW function sub-device is connected to an offline charging gateway CGF through an offline charging interface Ga/SWz; The generated charging information is to be mapped to the charging information generated by the S-GW to generate a unified new charging information generated by the S-GW. At the same time, the S-GW deployed in a unified manner is still connected to the P-GW through the S5/S8 interface.

Hereinafter, in conjunction with the evolved packet core network charging system supporting the non-3GPP access of the present invention, the method for charging the evolved packet core network supporting the non-3GPP access of the present invention will be described in detail.

FIG. 8 is a flow chart of charging under the offline charging mechanism of the present invention, as shown in FIG. The charging method under the line charging mechanism includes the following steps:

Step 801: After 3GPP AAA access authentication and authentication, an untrusted non-3GPP access network such as a WLAN is allowed to access the EPC core network;

Step 802: The ePDG sends the charging related information, such as the current data traffic, the Charging ID, and the PDN Connection ID, to the offline charging gateway. In this step, according to different deployment scenarios of the charging logic functional entity, ePDG You can send ACR (CDF independent of ePDG deployment) messages to CDF, or you can send CDR (both CDF and CTF are embedded in ePDG) messages to CGF, or you can send CDR files to Billing Domain (CTF, CDF, and CGF are all embedded in ePDG); For details, please refer to the related description above. The interface offline charging gateway collects the charging information to generate the CDR file, and the offline charging system Billing Domain generates the bill based on the CDR file.

Step 803: The offline charging gateway returns a charging data response to the ePDG in response to the charging data request. FIG. 9 is a flow chart of the charging under the online charging mechanism of the present invention. As shown in FIG. 9, the charging method in the online charging mechanism of the present example includes the following steps:

Step 901: After the 3GPP AAA access authentication and authentication, the untrusted non-3GPP access network, such as the WLAN, is allowed to access the EPC core network;

Step 902: The ePDG with the embedded CTF sends the credit control information carrying the current data traffic, the Charging ID, and the PDN Connection ID of the user to the OCS, and the OCS performs the corresponding credit according to the charging policy and the current data traffic share request and the corresponding service type. control.

Step 903: The OCS returns a credit control response to the ePDG, and the credit control response carries the guaranteed service unit GSU;

Step 904: When both online charging and offline charging are supported, the Billing Domain receives the charging data sent by the ePDG, and further generates a bill.

10 is a flow chart of charging under the offline charging mechanism of the present invention. As shown in FIG. 10, this example is shown in FIG. The charging method under the offline charging mechanism includes the following steps:

Step 1001: After 3GPP AAA access authentication and authentication, trusted non-3GPP access networks such as CDMA and/or untrusted non-3GPP access networks such as WLAN are allowed to access the EPC core network, where HSGW (hometown) The service gateway is a trusted non-3GPP access gateway. Step 1002: The trusted non-3GPP access gateway and/or the untrusted non-3GPP access gateway, such as the HSGW/ePDG, reports the current user traffic information to the 3GPP AAA. Related billing information such as Charging ID and PDN Connection ID.

Step 1003: The 3GPP AAA sends related charging information including current user traffic information, Charging ID, and PDN Connection ID to an offline charging gateway/offline charging system; wherein the charging logical function entity is deployed in 3GPP AAA There are also many possibilities as in the case of the first embodiment, and here is no longer a description.

Step 1004: The offline charging gateway returns a charging data response to the 3GPP AAA in response to the charging data request.

Figure 11 is a flow chart of the charging under the online charging mechanism of the present invention. As shown in Figure 11, the charging method in the online charging mechanism of the present example includes the following steps:

Step 1101: After 3GPP AAA access authentication and authentication, a trusted non-3GPP access network, such as CDMA and/or an untrusted non-3GPP access network, such as a WLAN, is allowed to access the EPC core network, where the HSGW is a a trusted non-3GPP access gateway;

Step 1102: The trusted non-3GPP access gateway and/or the untrusted non-3GPP access gateway, such as the HSGW/ePDG, report the current user traffic information, the Charging ID, and the PDN Connection ID to the 3GPP AAA. .

Step 1103: The 3GPP AAA that embeds the CTF sends the credit control information carrying the current data traffic of the user to the online charging system OCS, and the OCS performs corresponding credit control according to the charging policy and the current data traffic share request and the corresponding service type. Step 1104: The OCS returns a credit control response to the 3GPP AAA, where the credit control response carries the guaranteed service unit GSU;

Step 1105: When both online charging and offline charging are supported, the charging domain receives the charging data sent by the 3GPP AAA, and further generates a bill.

In the present invention, when the P-GW and the ePDG are uniformly deployed according to different roaming architectures supporting the non-3GPP access EPC and the deployment requirements of the operator, the ePDG is originally connected to the offline/online charging interface, and is currently connected by the P. The GW is connected to the offline/online charging interface. As shown in FIG. 8, the offline/online charging interface on the P-GW will map the content of the charging interface belonging to the ePDG on the interface of the P-GW.

When the S-GW and the ePDG are deployed in a unified manner according to the different roaming architectures that support the non-3GPP access to the EPC and the deployment requirements of the carrier, the ePDG is connected to the offline charging interface. Interface connection, as shown in Figure 9, at this time, the offline charging interface on the S-GW maps the content of the accounting interface belonging to the ePDG on the interface of the S-GW. The online charging information is exchanged between the P-GW and the OCS through the S5/S8 interface between the S-GW and the P-GW.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Industrial applicability

The present invention sets a CTF in an ePDG or a network element other than the ePDG, such as a 3GPP AAA or a non-3GPP access EPC access network element, and acquires a non-3GPP access network access network in a network element other than the ePDG or the ePDG. After the evolved packet data usage, billing information is generated and sent to the offline charging gateway and/or the online charging system for charging, thereby implementing a data flow based meter for users accessing through the non-3GPP access network. fee.

Claims

Claim

A method for charging an evolved packet core network supporting non-3GPP access, wherein the method includes:

The billing triggering function entity CTF generates billing information based on the progressive packet data usage of the non-3rd Generation Partnership Project 3GPP access network, and sends it to the offline charging gateway and/or the online billing system for billing.

The method according to claim 1, wherein the CTF is set in an evolved packet data gateway ePDG, and/or is disposed outside the ePDG.

3. The method according to claim 2, wherein the CTF is disposed outside the ePDG, and is:

The CTF is set in 3GPP AAA or in other network elements.

The method according to claim 2 or 3, wherein the offline charging gateway is provided with an accounting data function entity CDF and a charging gateway function entity CGF.

5. The method according to claim 4, wherein the CDF and the CGF are disposed in the ePDG;

Or the CDF is set in the ePDG, and the CGF is disposed outside the ePDG;

Or the CDF and the CGF are set in the 3GPP AAA;

The method according to claim 4, wherein when the CTF is set in the 3GPP AAA, the 3GPP AAA acquires the evolution of the non-3GPP access network from the ePDG and/or the home serving gateway HSGW Packet data usage.

The method according to claim 3, wherein when the CTF is set in another network element, the 3GPP AAA obtains a charging related information of the non-3GPP access network from the other network element. Interest.

The method according to any one of claims 1 to 7, wherein the charging information comprises an evolved packet data usage, a charging identifier Charging ID, and a packet data network of a user accessed by the non-3GPP access network. The connection identifies the PDN Connection ID.

9. An evolved packet core network charging system supporting non-3GPP access, comprising a CTF, and an offline charging gateway and/or an online charging system;

10. The system according to claim 9, wherein the CTF is set in an evolved packet data gateway ePDG, and/or is disposed outside the ePDG.

The system according to claim 10, wherein the CTF is set in a 3GPP AAA or in another network element.

The system according to claim 10 or 11, wherein the offline charging gateway is provided with a CDF and a CGF.

13. The system according to claim 12, wherein the CDF and the CGF are disposed in the ePDG;

Or the CDF is set in the ePDG, and the CGF is disposed outside the ePDG;

Or the CDF and the CGF are set in the 3GPP AAA;