CN103781041A

CN103781041A - Charging synchronization method, apparatus and system

Info

Publication number: CN103781041A
Application number: CN201210397754.6A
Authority: CN
Inventors: 卢飞; 周晓云
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2012-10-18
Filing date: 2012-10-18
Publication date: 2014-05-07
Anticipated expiration: 2032-10-18
Also published as: WO2014059911A1; CN103781041B

Abstract

The invention discloses a charging synchronization method, apparatus and system. The method comprises a PGW notifying a TDF to execute the same charging operation as the PGW. According to the invention, the PGW notifies the TDF to execute the same charging operation as the PGW so that the problem of non-synchronized PGW charging and TDF charging in related arts is solved, the errors caused by the non-synchronized PGW charging and TDF charging are reduced, and the charging processes of the PGW and the TDF are improved.

Description

Charging synchronization method, device and system

Technical Field

The present invention relates to the field of communications, and in particular, to a method, an apparatus, and a system for charging synchronization.

Background

With the advent of World Interoperability for Microwave Access (WiMax), third generation mobile communication systems must improve their network performance and reduce their network construction and operation costs to maintain their strong competitiveness in the mobile communication field. Therefore, the standardization working group of the third Generation partnership project (3 rd Generation partnership project, abbreviated as 3 GPP) is currently working on the Evolution of Packet switched Core Network (Packet Switch Core, abbreviated as PS Core) and Universal Mobile telecommunications system radio access Network (UTRAN), which is called System Architecture Evolution (SAE) and aims to enable Evolved Packet Network (Evolved Packet Core, abbreviated as EPC) to provide higher transmission rate, shorter transmission delay, optimize packets, and support mobility management between Evolved UTRAN (Evolved UTRAN, abbreviated as E-UTRAN), UTRAN, Wireless Local Area Network (WLAN), and other non-3 GPP access networks.

Fig. 1 is a schematic diagram of the architecture of a current SAE according to the related art, as shown in fig. 1, the SAE includes the following network elements:

evolved radio access network (Evolved RAN, abbreviated E-RAN): higher uplink/downlink rates, lower transmission delays, and more reliable wireless transmissions may be provided. The network element included in the E-RAN is an E-NodeB (evolved node B) for providing radio resources for access of users.

Packet Data Network (PDN): a network providing services to users.

Evolved Packet network (E-Packet Core), provides lower latency and allows more wireless access system access. It comprises the following network elements:

mobility Management Entity (MME): a control plane functional entity, a server for temporarily storing User data, and a control plane functional entity, which is responsible for managing and storing contexts (such as UE/User identifiers, mobility management states, User security parameters, and the like) of a User Equipment (User Equipment, abbreviated as UE), allocating temporary identifiers to users, and when the UE is camped in the tracking area or the network, being responsible for authenticating the users; processing all non-access stratum messages between the MME and the UE; paging at SAE is triggered. The MME is a mobility management unit of the SAE system. In the UMTS system, the mobility management unit is an SGSN (Serving GPRS Support Node).

A Serving Gateway (SGW) is a user plane entity, and is responsible for routing user plane data and terminating downlink data of a UE in an IDLE (ECM IDLE) state. And managing and storing SAE bearer (bearer) context of the UE, such as IP bearer service parameters, network internal routing information and the like. The SGW is an anchor point of a user plane in a 3GPP system, and one user only has one SGW at one time;

a packet data network Gateway (PDN Gateway, abbreviated as PGW), which is responsible for accessing a PDN by the UE, allocates a user IP address, and is a mobility anchor point of 3GPP and non-3 GPP access systems, and the function of the PGW further includes policy implementation and charging support. A user can access multiple PGWs at the same time. The PCEF (Policy and Charging implementation Function) is also located in the PGW.

A Policy and Charging Rules Function (Policy and Charging Rules Function, abbreviated as PCRF) is responsible for providing Policy control and Charging Rules to the PCEF.

A Home Subscriber Server (HSS) permanently stores Subscriber subscription data, and the content stored by the HSS includes an IMSI (International Mobile Subscriber identity) of the UE and an IP address of the PGW. The HSS is connected to a serving GPRS support node, which is connected to a Radio Network Controller (RNC).

The Traffic Detection Function (TDF) is responsible for detecting and controlling the service application of the user, and may also perform charging according to the detected service application.

Physically, the SGW and PGW may be unified. The EPC system user plane network element comprises an SGW and a PGW. When the SGW and the PGW are connected through GTP (GPRS Tunneling Protocol ), there is no interface between the SGW and the PCRF; when the SGW and the PGW are connected through pmip (proxy Mobile Internet protocol), the SGW and the PCRF are connected through a Gxc interface.

In the SAE system, the SGW has a function of buffering downlink data of the UE in an idle state. When the UE is in the idle mode, and the SGW receives Downlink Data sent from the PGW to the UE, because the SGW does not know the address of the E-NodeB (or referred to as eNodeB) where the UE is located, the SGW cannot send the Downlink Data in time, and therefore the SGW needs to buffer the received Downlink Data, and needs to send a Downlink Data Notification message (Downlink Data Notification) to the MME, and the MME triggers Paging (Paging). If the MME receives the paging response within a certain time, the Serving GW may obtain the address of the eNodeB in time, and may issue the cached data to the eNodeB, and the specific flow is shown in fig. 2. However, when the SGW has no relevant bearer information, the SGW can only discard the arriving downlink data packet, and cannot send a downlink data arrival notification message to the MME.

When the coverage Area of the UE changes, for example, the UE moves from one coverage Area of the mobility management unit to another coverage Area of the mobility management unit, the UE finds that the UE enters an unregistered Area by monitoring a broadcast channel, and needs to register under a new RAT coverage Area in order to ensure continuous service between the UE and a core network, so the UE initiates a Tracking Area Update (TAU) or Routing Area Update (RAU) procedure. Fig. 2 is a flow of TAU caused by a UE registered under an E-UTRAN coverage area moving to another MME coverage area according to the related art. As shown in fig. 2, the method includes the following steps (step S202 to step S228):

step 202, the UE moves to an E-UTRAN coverage area under another MME, sends a tracking area update request to the new MME, requests registration in a new area, and the request message carries the GUTI allocated by the old MME for the UE.

And step 204, the new MME finds the old MME according to the GUTI identification, and sends a context request signaling to perform a context acquisition process.

In step 206, the old MME sends the mobility management and bearer information of the ue to the new MME, i.e. performs context response.

In step 208, the new MME receives the corresponding information and then confirms the context, i.e., the context is confirmed.

Step 210, the new MME initiates a bearer update request to the SGW, where the request message carries a source GTP-C tunnel identifier and a destination GTP-C tunnel identifier, and the SGW updates the binding relationship of the bearer.

Step 212, the SGW sends an update bearer request to the PGW, and sends parameters such as address information, tunnel identifier information, access technology type, and the like of the SGW to the PGW.

In step 214, the PGW updates its context and returns an update bearer response message to the SGW, where the message content includes the address and tunnel identifier of the PGW.

In step 216, the SGW returns an update bearer response to the new MME, and brings the destination GTP-C tunnel identifier, the address of the SGW, the address of the PGW, the tunnel information, and the like, which are specified by the SGW, to the MME.

The new MME informs the HSS of the change of the registered location by a location update message, step 218.

In step 220, the HSS sends a location cancellation signaling to the old MME, maintaining only the registration of the new MME.

In step 222, the old MME returns a location cancellation response to the HSS.

In step 224, the HSS confirms the location update of the new MME.

Step 226, if the new MME confirms that the UE is valid in the current tracking area, sending a tracking area update accept message to the UE, where the message carries a periodic tracking area update timer, and the recommended value in the current standard protocol is 54 minutes.

In step 228, if the new MME allocates a new GUTI identifier to the UE through the TAU procedure, the UE returns a tracking area update complete message to confirm to the MME.

For the RAU procedure initiated when the UE registered under the E-UTRAN coverage area moves to the UTRAN coverage area, the procedure is similar to the above procedure, and thus the details are not repeated. In a real network, the SGW may restart due to system instability or upgrade. After the mobility management unit and the PGW detect that the SGW is restarted, the mobility management unit and the PGW in the existing operating network delete the user context associated therewith, so that the mobility management unit cannot contact the user equipment and cause the user equipment not to obtain downlink data, and the user equipment can be reconnected with the network only when uplink data is sent by the user equipment. In order to enable the user service to be recovered as soon as possible, after the mobility management unit and the PGW detect that the SGW is restarted, the mobility management unit and the PGW continue to keep the user context and the user bearer context for a period of time, but mark that these bearers are unavailable, and when the PGW receives downlink data packets on these bearers, the PGW discards the bearers, and does not perform charging. But since the TDF would charge for packets sent to the PGW, this causes an out-of-sync of charging.

An effective solution is not proposed at present for the problem of asynchronous charging of PGW and TDF in the related art.

Disclosure of Invention

Aiming at the problem of asynchronous charging of PGW and TDF in the related technology, the invention provides a charging synchronization method, a device and a system, so as to at least solve the problem.

According to an aspect of the present invention, there is provided a charging synchronization method, including: the PGW notifies the TDF to perform the same charging operation as the above PGW.

The step of the PGW notifying the TDF to perform the same charging operation as the PGW includes: the PGW notifies the TDF to perform the same charging operation as the PGW through a policy and charging rules function entity PCRF.

Before the PGW notifies the TDF to perform the same charging operation as the PGW, the method further includes: and after receiving the downlink data packet, the PGW determines to perform charging stop operation or charging recovery operation on the data packet.

The notifying, by the PGW through the PCRF, the TDF to perform the same charging operation as the PGW includes: when the PGW determines to perform a charging stop operation on the data packet, the PGW notifies the TDF to perform the charging stop operation through the PCRF and/or notifies the TDF to directly discard the data packet; and under the condition that the PGW determines to execute the charging recovery operation on the data packet, the PGW informs the TDF to execute the charging recovery operation through the PCRF.

After receiving the downlink data packet, the determining that the charging stop operation or the charging recovery operation is performed on the data packet by the PGW includes: after receiving a downlink data packet on an unavailable bearer, the PGW determines to perform a charging stop operation on the data packet; or, after receiving the downlink data packet on the bearer that is restored to normal, the PGW determines to perform a charging restoration operation on the data packet.

In a case where the PGW notifies the TDF to directly discard the packet, the method further includes: and under the condition that the bearer is recovered to be normal, the PGW informs the TDF to execute charging recovery operation.

Before the PGW receives the downlink data packet on the unavailable bearer, the method further includes: after the PGW detects that the SGW is restarted, reserving a bearing context and a user context; the PGW marks the bearer as unavailable.

Before the PGW receives the downlink data packet on the unavailable bearer, the method further includes: the PGW receives a bearer suspension notification message sent by a mobile management entity MME through an SGW; the PGW returns a bearer suspension acknowledgement message to the MME through the SGW; wherein the suspended bearer of the PGW is an unavailable bearer.

Before the PGW receives the downlink data packet on the bearer that recovers to normal, the method further includes: the PGW receives a bearer modification request message sent by the MME through the SGW; the PGW returns a bearer modification response message to the MME through the SGW; wherein, the modified bearer of the PGW is a normal bearer.

Before the PGW receives the bearer modification request message sent by the MME through the SGW, the method further includes: the MME reselects the SGW; wherein, the reselected SGW is a restarted SGW or a normally working SGW.

Before the PGW receives the bearer modification request message sent by the MME through the SGW, the method further includes: and the MME receives a non-access stratum message sent by User Equipment (UE).

The non-access stratum message is a tracking area update TAU request message.

The notifying, by the PGW through the PCRF, the TDF to perform the same charging operation as the PGW includes: the PGW sends a charging notification message to the PCRF; wherein, the charging notification message is used to notify the TDF to perform the same charging operation as the PGW; and the PCRF sends the charging notification message to the TDF.

After the PGW notifies the TDF to perform the same charging operation as the PGW through the PCRF, the method further includes: the TDF returns a charging notification response message to the PCRF; and the PGW receives the charging notification response message sent by the PCRF.

The method further comprises the following steps: after detecting that the SGW is restarted, the PGW reserves a bearer context and a user context and marks the bearer as an unavailable bearer; after the PCRF detects that the SGW is restarted, the connection with the SGW is deleted, and user information and a strategy are reserved; the PCRF sends the charging notification message to the TDF; wherein, the charging notification message is used to notify the TDF to perform charging stop operation.

The method further comprises the following steps: after detecting that the SGW recovers the work, the PCRF sends the charging notification message to the TDF; wherein, the charging notification message is used to notify the TDF to execute a charging recovery operation.

The method further comprises the following steps: after detecting that the PGW is restarted, the PCRF deletes the connection with the PGW and retains user information and strategies; the PCRF sends the charging notification message to the TDF; wherein, the charging notification message is used to notify the TDF to perform charging stop operation.

The method further comprises the following steps: after detecting that the PGW recovers, the PCRF sends the charging notification message to the TDF; wherein, the charging notification message is used to notify the TDF to execute a charging recovery operation.

According to another aspect of the present invention, there is provided a charging synchronization apparatus, including: and the charging execution module is used for informing the TDF to execute the same charging operation as the PGW.

The charging execution module comprises: and a charging execution unit, configured to notify, by a policy and charging rules function entity PCRF, the TDF to execute the same charging operation as the PGW.

The above-mentioned device still includes: and the charging determining module is used for determining to execute charging stopping operation or charging recovering operation on the data packet after receiving the downlink data packet.

The charging execution unit includes: a first performing subunit, configured to, in a case where the PGW determines to perform a charging stop operation on the data packet, notify, by the PCRF, the TDF to perform the charging stop operation, and/or notify, by the TDF, to directly discard the data packet; a second performing subunit, configured to notify, by the PCRF, the TDF to perform a charging recovery operation when the PGW determines to perform the charging recovery operation on the data packet.

The charging determining module includes: a charging stop determining unit, configured to determine to perform a charging stop operation on a downlink data packet after receiving the data packet on an unavailable bearer; or, the charging recovery determining unit is configured to determine to perform a charging recovery operation on the data packet after receiving the downlink data packet on the bearer that recovers to normal.

In a case where the PGW notifies the TDF to directly discard the packet, the apparatus further includes: and a notification module, configured to notify the TDF to perform a charging recovery operation when the bearer is recovered to be normal.

Before the PGW receives the downlink data packet on the unavailable bearer, the charging determining module further includes: a reserving unit, configured to reserve a bearer context and a user context after detecting that a serving gateway SGW is restarted; and the marking unit is used for marking the bearing as the unavailable bearing.

Before the PGW receives the downlink data packet on the unavailable bearer, the charging determining module further includes: a notification message receiving unit, configured to receive a bearer suspension notification message sent by an MME through an SGW; a confirmation message returning unit, configured to return a bearer suspension confirmation message to the MME through the SGW; wherein the suspended bearer of the PGW is an unavailable bearer.

Before the PGW receives the downlink data packet on the normal bearer, the charging determining module further includes: a request message receiving unit, configured to receive a bearer modification request message sent by the MME through the SGW; a response message returning unit, configured to return a modified bearer response message to the MME through the SGW; wherein, the modified bearer of the PGW is a normal bearer.

According to still another aspect of the present invention, there is provided a charging synchronization system, including: a PGW, a PCRF, and a TDF, wherein the PGW includes the charging synchronization apparatus, and the PGW includes: a first sending module, configured to send a charging notification message to the PCRF; wherein, the charging notification message is used to notify the TDF to perform the same charging operation as the PGW; the PCRF comprises the following steps: and a second sending module, configured to send the charging notification message to the TDF.

The TDF includes: a response module, configured to return a charging notification response message to the PCRF; the PGW further includes: and the receiving module is used for receiving the charging notification response message sent by the PCRF.

The PGW further includes: a reserving module, configured to reserve a bearer context and a user context after detecting that the SGW is restarted, and mark the bearer as an unavailable bearer; the PCRF further includes: the first deleting module is used for deleting the connection with the SGW after the SGW is detected to restart, and keeping user information and strategies; the PCRF further includes: a first message sending module, configured to send the charging notification message to the TDF; wherein, the charging notification message is used to notify the TDF to perform charging stop operation.

The PCRF further includes: a second message sending module, configured to send the charging notification message to the TDF after detecting that the SGW recovers to work; wherein, the charging notification message is used to notify the TDF to execute a charging recovery operation.

The PCRF further includes: a second deleting module, configured to delete the connection with the PGW and retain the user information and the policy after detecting that the PGW is restarted; the PCRF further includes: a third message sending module, configured to send the charging notification message to the TDF; wherein, the charging notification message is used to notify the TDF to perform charging stop operation.

The PCRF further includes: a fourth message sending module, configured to send the charging notification message to the TDF after detecting that the PGW recovers work; wherein, the charging notification message is used to notify the TDF to execute a charging recovery operation.

Through the invention, the PGW informs the TDF to execute the same charging operation as the PGW, thereby solving the problem of asynchronous charging of the PGW and the TDF in the related technology, reducing the error caused by asynchronous charging of the PGW and the TDF and perfecting the charging process of the PGW and the TDF.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:

FIG. 1 is an architecture diagram of a current SAE according to the related art;

fig. 2 is a flow of TAU triggered by a UE registered under an E-UTRAN coverage area moving to another MME coverage area according to the related art;

fig. 3 is a flowchart of a charging synchronization method according to an embodiment of the present invention;

fig. 4 is a flowchart of a PGW and TDF charging synchronization method according to an embodiment of the present invention;

fig. 5 is a flow diagram of notifying TDF of charging synchronization after SGW restart according to an embodiment of the present invention;

fig. 6 is a flowchart of a PGW notifying TDF of charging synchronization in a bearer "suspended" state on the PGW in SRVCC according to an embodiment of the present invention;

fig. 7 is a flowchart of notifying TDF of recovery charging after bearer recovery on PGW after MME reselects an SGW according to an embodiment of the present invention;

fig. 8 is a flowchart of notifying TDF to resume charging after returning to PGW under E-UTRAN coverage to resume normal after terminating CS session according to an embodiment of the present invention;

fig. 9 is a flow diagram of PCRF detecting SGW restart notification TDF stop charging in accordance with an embodiment of the present invention;

fig. 10 is a flowchart of PCRF detecting PGW restart notification TDF stop charging according to an embodiment of the present invention;

fig. 11 is a block diagram of a structure of a charging synchronization apparatus according to an embodiment of the present invention;

fig. 12 is a block diagram of a structure of a charging synchronization system according to an embodiment of the present invention.

Detailed Description

The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.

The embodiment of the invention provides a charging synchronization method, a device and a system, which are described in detail through specific embodiments.

This embodiment provides a charging synchronization method, fig. 3 is a flowchart of the charging synchronization method according to the embodiment of the present invention, as shown in fig. 3, the method includes the following steps:

in step S302, the PGW notifies the TDF to perform the same charging operation as the PGW.

By the method, the PGW informs the TDF to execute the same charging operation as the PGW, the problem of asynchronous charging of the PGW and the TDF in the related technology is solved, errors caused by asynchronous charging of the PGW and the TDF are reduced, and the charging flow of the PGW and the TDF is perfected.

Regardless of how the PGW informs the TDF, it is sufficient that both guarantee the same charging operation. Preferably, in order to ensure the accuracy and timeliness of the notification procedure, in practical applications, the notification procedure may be implemented by the PCRF in most cases, and therefore, the present embodiment provides a preferred embodiment, that is, the PGW notifies the TDF to perform the same charging operation as the PGW through the PCRF.

After receiving the downlink data sent by the TDF on the unavailable bearer, the PGW also notifies the TDF not to charge if the PGW does not charge. If the PGW recovers the normal charging, the PGW also notifies the TDF to recover the normal charging. Typically, the PGW notifies the TDF not to charge through the PCRF. The unavailability of the user bearer on the PGW includes detecting that the SGW is restarted and receiving a Suspend Notification (Suspend Notification) message sent by the SGW in SRVCC and CSFB procedures; after the user bearer on the PGW recovers to normal, the PGW needs to notify the TDF to recover normal charging.

Before the PGW notifies the TDF to perform the same charging operation as the PGW, the method further includes: after receiving the downlink data packet, the PGW determines to perform a charging stop operation or a charging recovery operation on the data packet. When the PGW determines to perform charging stop operation on the data packet, the PGW notifies the TDF to perform charging stop operation through the PCRF, and/or notifies the TDF to directly discard the data packet; and under the condition that the PGW determines to execute the charging recovery operation on the data packet, the PGW informs the TDF to execute the charging recovery operation through the PCRF. Through the above manner, the charging synchronization of the PGW and the TDF is realized.

Preferably, after receiving the downlink data packet, the determining to perform the charging stop operation or the charging recovery operation on the data packet by the PGW includes: after receiving a downlink data packet on an unavailable bearer, the PGW determines to perform charging stop operation on the data packet; or, after receiving the downlink data packet on the bearer that is restored to normal, the PGW determines to perform the charging restoration operation on the data packet. In a case where the PGW notifies the TDF to directly discard the data packet, the method further includes: and the PGW informs the TDF to execute the charging recovery operation under the condition that the bearing is recovered to be normal. By the mode, the synchronization of the charging stop operation and the synchronization of the charging recovery operation are respectively realized.

Preferably, before the PGW receives the downlink data packet on the unavailable bearer, the method further includes: after detecting that the SGW is restarted, the PGW reserves a bearing context and a user context; the PGW marks the bearer as unavailable. The method provides a basis for executing the charging stop operation or the charging recovery operation according to the decision of whether the bearing is available or not.

Preferably, before the PGW receives the downlink data packet on the unavailable bearer, the method further includes: a PGW receives a bearer suspension notification message sent by a mobile management entity MME through an SGW; the PGW returns a bearing suspension confirmation message to the MME through the SGW; wherein the suspended bearer of the PGW is an unavailable bearer.

Preferably, before the PGW receives the downlink data packet on the restored normal bearer, the method further includes: the PGW receives a bearer modification request message sent by the MME through the SGW; the PGW returns a response message of modifying the load to the MME through the SGW; wherein the modified bearer of the PGW is a normal restored bearer.

Before the PGW receives the bearer modification request message sent by the MME through the SGW, the method further includes: and the MME receives a non-access stratum message sent by User Equipment (UE). The non-access stratum message may be a tracking area update TAU request message.

The step of the PGW notifying the TDF to perform the same charging operation as the PGW through the PCRF includes: the PGW sends a charging notification message to the PCRF; wherein, the charging notification message is used to notify the TDF to perform the same charging operation as the PGW; and the PCRF sends the charging notification message to the TDF.

Preferably, the method further comprises: after detecting that the SGW is restarted, the PGW reserves a bearing context and a user context and marks the bearing as an unavailable bearing; after the PCRF detects that the SGW is restarted, the connection with the SGW is deleted, and user information and a strategy are reserved; the PCRF sends the charging notification message to the TDF; wherein, the charging notification message is used to notify the TDF to perform charging stop operation.

The method further comprises the following steps: after the PCRF detects that the PGW is restarted, the connection with the PGW is deleted, and user information and a strategy are reserved; the PCRF sends the charging notification message to the TDF; wherein, the charging notification message is used to notify the TDF to perform charging stop operation. The method further comprises the following steps: after detecting that the PGW recovers, the PCRF sends the charging notification message to the TDF; wherein, the charging notification message is used to notify the TDF to execute a charging recovery operation.

Fig. 4 is a flowchart of a PGW and TDF charging synchronization method according to an embodiment of the present invention, as shown in fig. 4, including the following steps (step S402-step S406):

step S402, the PGW receives downlink data on an unavailable bearer, and the PGW does not charge and discards the data packet.

Step S404, the PGW informs the TDF of temporary unavailability of the bearer and temporary charging through the PCRF; and if the PCRF directly detects that the SGW is restarted or the PGW is restarted, the PCRF directly informs the TDF that the bearer is unavailable, and charging is suspended.

In step S406, the bearer of the PGW is recovered to normal, and the PGW needs to notify the TDF that the bearer has been recovered through the PCRF and recover charging.

Fig. 5 is a flowchart of notifying TDF of charging synchronization after SGW restart according to an embodiment of the present invention, as shown in fig. 5, including the following steps (step S502-step S514):

step S502, after the MME detects that the SGW is restarted, the MME still keeps the bearing context and the user context for a period of time.

In step S504, after the PGW detects that the SGW is restarted, the PGW still retains the bearer context and the user context for a period of time, but marks that the affected bearer is temporarily unavailable.

In step S506, when the PGW receives the downlink data on the reserved bearers, the PGW does not perform charging and directly discards the received data packets.

Step S508, the PGW sends a TDF stop charging request message to the PCRF to notify the PCRF: the bearer is temporarily unavailable and requires the TDF to stop charging.

Step S510, the PCRF sends a TDF stop charging request message to the TDF to notify the TDF: the bearer is temporarily unavailable and requires the TDF to stop charging.

In step S512, the TDF returns a TDF stop charging response message to the PCRF.

In step S514, the PCRF returns a TDF stop charging response message to the PGW.

In this embodiment, the UE is illustrated in the MME coverage area, and the processing method is similar for the UE in the SGSN coverage area, so detailed description is not repeated.

Fig. 6 is a flowchart illustrating a PGW notifying TDF of charging synchronization in a bearer "suspended" state on the PGW in SRVCC according to an embodiment of the present invention, and as shown in fig. 6, the method includes the following steps (step S602-step S642):

step S602, the UE sends a measurement report to the eNodeB.

Step S604, according to the measurement report of UE, eNodeB decides to initiate SRVCC handover to GERAN, and eNodeB sends handover request message to MME.

Step S606, the MME classifies according to the QCI of the load, switches the voice load to the circuit domain, and the MME sends a switching request message from PS to CS to the MSC.

Step S608, the MSC sends a handover request message to the BSS, and the BSS returns a handover confirmation message to the MSC.

Step S610, the MSC returns a PS to CS handover response message to the MME.

Step S612, the source MME sends a handover command to the source eNodeB.

Step S614, the source eNodeB sends a handover command to the UE.

Step S616, the UE is switched to GERAN, and the UE sends a bearer suspension process to the BSS.

At step S618, the target BSS forwards the bearer suspend message to the target SGSN.

Step S620, the target SGSN initiates a suspend notification message to the source MME, and the source MME returns a corresponding acknowledgement message.

In step S622, the target BSS sends a handover complete message to the target SGSN.

Step S624, MSC sends PS to CS switch complete message to MME; the MME returns a PS to CS handover confirm message to the MSC.

In step S626, the source MME sends a suspend notification message to the SGW.

In step S628, the SGW forwards the suspend notification message to the PGW.

In step S630, the PGW returns a suspend acknowledgement message to the SGW.

In step S632, the SGW returns a suspend acknowledgement message to the MME.

In step S634, when the PGW receives the downlink data on the suspended bearers, the PGW does not perform charging and directly discards the received data packets.

Step S636, the PGW sends a TDF stop charging request message to the PCRF to notify the PCRF: the bearer is temporarily suspended and requires the TDF to stop accounting.

Step S638, the PCRF sends a TDF stop charging request message to the TDF to notify the TDF: the bearer is temporarily suspended and requires the TDF to stop accounting.

In step S640, the TDF returns a TDF stop charging response message to the PCRF.

Step S642, the PCRF returns the TDF stop charging response message to the PGW.

In this embodiment, UE originally in the MME coverage area is taken as an example for explanation; the processing method is similar to the UE originally located in the coverage area of the SGSN, and thus, the detailed description is omitted. In this embodiment, SRVCC is taken as an example for explanation, and a processing method for performing CSFB for the UE is similar to that in the SRVCC example, so detailed description is not repeated.

Fig. 7 is a flowchart of notifying TDF of recovering charging after bearer recovery on PGW after MME reselects an SGW according to an embodiment of the present invention, as shown in fig. 7, including the following steps (step S702-step S718):

in step S702, the MME reselects an SGW, which may be a restarted SGW or another SGW operating normally.

Step S704, MME sends a request message for establishing session to new SGW, where the message carries parameters such as IMSI, user IP address, and bearer QoS.

Step S706, the new SGW sends a modify bearer request message to the PGW.

In step S708, the PGW returns a modify bearer response message to the SGW.

Step S710, the SGW returns a session establishment response message to the MME.

In step S712, after the bearer on the PGW recovers to normal, the PGW sends a TDF charging recovery notification message to the PCRF to notify that the bearer recovers to normal and needs the TDF to recover charging.

In step S714, the PCRF sends a TDF recovery charging notification message to the TDF for notifying the bearer to recover normal and requiring the TDF to recover charging.

In step S716, the TDF returns a TDF charging recovery confirm message to the PCRF.

In step S718, the PCRF returns a TDF charging restoration confirmation message to the PGW.

Fig. 8 is a flowchart of notifying TDF to resume charging after the CS session is ended and the PGW returns to normal under coverage of E-UTRAN according to an embodiment of the present invention, and the flowchart of fig. 8 may be added to the flowchart of fig. 6, as shown in fig. 8, including the following steps (steps S802-S820):

step S802, after the UE finishes the CS communication, the UE returns to the coverage area of the eNodeB, and the UE sends a TAU request message to the MME.

Step S804, the MME sends a modify bearer request message to the SGW.

In step S806, the SGW sends a modify bearer request message to the PGW.

Step S808, the PGW returns a modify bearer response message to the SGW.

Step S810, the SGW returns a session establishment response message to the MME.

In step S812, the MME returns a TAU accept message to the UE.

In step S814, after the bearer on the PGW recovers to normal, the PGW sends a TDF charging recovery notification message to the PCRF to notify that the bearer recovers to normal and needs the TDF to recover charging.

In step S816, the PCRF sends a TDF recovery charging notification message to the TDF for notifying the bearer to recover normal and requiring the TDF to recover charging.

In step S818, the TDF returns a TDF recovery charging acknowledgement message to the PCRF.

In step S820, the PCRF returns a TDF charging restoration confirmation message to the PGW.

In this embodiment, a TAU message is taken as an example for description, and for other non-access stratum messages, the specific flow is similar and is not specifically described.

Fig. 9 is a flowchart of PCRF detecting SGW restart notification TDF stop charging according to an embodiment of the present invention, as shown in fig. 9, including the following steps (step S902-step S910):

step S902, after the MME detects that the SGW is restarted, the MME still keeps the bearing context and the user context for a period of time;

step S904, after the PGW detects that the SGW is restarted, the PGW still retains the bearer context and the user context for a period of time, but marks that the affected bearer is temporarily unavailable;

step S906, after the PCRF detects that the SGW is restarted, the PCRF locally deletes the connection with the SGW, but still retains other information and strategies of the user;

step S908, the PCRF sends a TDF stop charging request message to the TDF to notify the TDF: the bearer is temporarily unavailable and charging needs to be stopped;

step S910, the TDF returns a TDF stop charging response message to the PCRF;

in the application scenario of this embodiment, the charging recovery procedure may still adopt a manner similar to that provided in fig. 7, that is, after the PCRF detects that the SGW is restarted, the subsequent charging recovery procedure is executed, which is not described herein again.

Fig. 10 is a flowchart illustrating a PCRF detecting that a PGW restarts to notify a TDF to stop charging according to an embodiment of the present invention, as shown in fig. 10, including the following steps (step S1002-step S1008):

in step S1002, the PGW restarts.

In step S1004, after the PCRF detects that the PGW is restarted, the PCRF locally deletes the connection with the PGW, but still retains other information and policies of the user.

Step S1006, the PCRF sends a TDF stop charging request message to the TDF to notify the TDF: the bearer is temporarily unavailable and charging needs to be stopped.

In step S1008, the TDF returns a TDF stop charging response message to the PCRF.

In the application scenario of this embodiment, the charging recovery procedure may still adopt a manner similar to that provided in fig. 7, and after the PCRF detects that the PGW is restarted, the subsequent charging recovery procedure is executed, which is not described herein again.

Corresponding to the charging synchronization method introduced in the foregoing embodiment, this embodiment provides a charging synchronization apparatus, which may be disposed on a PGW, to implement the foregoing embodiment. Fig. 11 is a block diagram of a structure of a charging synchronization apparatus according to an embodiment of the present invention, as shown in fig. 11, the apparatus includes: a charging executing module 12, configured to notify the TDF to execute the same charging operation as that of the PGW.

Through the device, the charging execution module of the PGW informs the TDF to execute the charging operation which is the same as that of the PGW, so that the problem of asynchronous charging of the PGW and the TDF in the related technology is solved, the error caused by asynchronous charging of the PGW and the TDF is reduced, and the charging process of the PGW and the TDF is perfected.

Preferably, the charging execution module includes: and a charging execution unit, configured to notify, by a PCRF, the TDF to execute the same charging operation as the PGW. The above-mentioned device still includes: and the charging determining module is used for determining to execute charging stopping operation or charging recovering operation on the data packet after receiving the downlink data packet. Therefore, the accuracy and timeliness of the notification process are guaranteed.

The charging execution unit includes: a first performing subunit, configured to, in a case where the PGW determines to perform a charging stop operation on the data packet, notify, by the PCRF, the TDF to perform the charging stop operation, and/or notify, by the TDF, to directly discard the data packet; a second performing subunit, configured to notify, by the PCRF, the TDF to perform a charging recovery operation when the PGW determines to perform the charging recovery operation on the data packet. Through the device, the charging synchronization of the PGW and the TDF is realized.

The charging determining module includes: a charging stop determining unit, configured to determine to perform a charging stop operation on a downlink data packet after receiving the data packet on an unavailable bearer; or, the charging recovery determining unit is configured to determine to perform a charging recovery operation on the data packet after receiving the downlink data packet on the bearer that recovers to normal. In a case where the PGW notifies the TDF to directly discard the packet, the apparatus further includes: and a notification module, configured to notify the TDF to perform a charging recovery operation when the bearer is recovered to be normal. By the device, the synchronization of the charging stop operation and the synchronization of the charging recovery operation are respectively realized.

Before the PGW receives the downlink data packet on the unavailable bearer, the charging determining module further includes: a reserving unit, configured to reserve a bearer context and a user context after detecting that a serving gateway SGW is restarted; and the marking unit is used for marking the bearing as the unavailable bearing. The structure provides a foundation for executing the charging stop operation or the charging recovery operation according to the decision of whether the bearing is available or not.

Corresponding to the charging synchronization method introduced in the foregoing embodiments, this embodiment provides a charging synchronization system, which is used to implement the foregoing embodiments. Fig. 12 is a block diagram of a structure of a charging synchronization system according to an embodiment of the present invention, and as shown in fig. 12, the system includes: a PGW, a PCRF, and a TDF, where the PGW includes the charging synchronization apparatus described in the foregoing embodiment, and the PGW includes: a first sending module 14, configured to send a charging notification message to the PCRF; wherein, the charging notification message is used to notify the TDF to perform the same charging operation as the PGW; the PCRF includes: a second sending module 16, configured to send the charging notification message to the TDF.

The TDF includes: a response module, configured to return a charging notification response message to the PCRF; the PGW further includes: and the receiving module is used for receiving the charging notification response message sent by the PCRF. Through the structure, the PGW can acquire the notification of the PGW responded by the TDF, and the accuracy and the efficiency of charging synchronization are improved.

The PGW further includes: a reserving module, configured to reserve a bearer context and a user context after detecting that the SGW is restarted, and mark the bearer as an unavailable bearer; the PCRF further includes: the first deleting module is used for deleting the connection with the SGW after the SGW is detected to restart, and keeping user information and strategies; the PCRF further includes: a first message sending module, configured to send the charging notification message to the TDF; wherein, the charging notification message is used to notify the TDF to perform charging stop operation. Through the structure, the PCRF can trigger the charging stop operation or the charging recovery operation by detecting the restarting of the SGW, thereby expanding the application range of the charging synchronization.

The PCRF further includes: a second message sending module, configured to send the charging notification message to the TDF after detecting that the SGW recovers to work; wherein, the charging notification message is used to notify the TDF to execute a charging recovery operation. The PCRF further includes: a second deleting module, configured to delete the connection with the PGW and retain the user information and the policy after detecting that the PGW is restarted; the PCRF further includes: a third message sending module, configured to send the charging notification message to the TDF; wherein, the charging notification message is used to notify the TDF to perform charging stop operation.

The PCRF further includes: a fourth message sending module, configured to send the charging notification message to the TDF after detecting that the PGW recovers work; wherein, the charging notification message is used to notify the TDF to execute a charging recovery operation. Through the structure, the PCRF can trigger the charging stop operation or the charging recovery operation by detecting the restart of the PGW, so that the application range of charging synchronization is expanded.

As can be seen from the above description, in the present invention, the PGW notifies the TDF to perform the same charging operation as the PGW, so that the charging synchronization of the PGW and the TDF is realized, the error caused by the asynchronous charging of the PGW and the TDF is reduced, and the charging flow of the PGW and the TDF is perfected.

It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present 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, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for synchronizing charging, comprising:

the packet data network gateway PGW informs a service detection function entity TDF to perform the same charging operation as the PGW.

2. The method of claim 1, wherein the PGW notifying the TDF of performing the same charging operation as the PGW comprises:

and the PGW informs the TDF to execute the same charging operation as the PGW through a Policy and Charging Rules Function (PCRF).

3. The method of claim 2, wherein before the PGW notifies the TDF to perform the same charging operation as the PGW, the method further comprises:

and after receiving the downlink data packet, the PGW determines to execute a charging stop operation or a charging recovery operation on the data packet.

4. The method of claim 3, wherein the PGW notifying the TDF through the PCRF to perform the same charging operation as the PGW comprises:

in a case that the PGW determines to perform a charging stop operation on the data packet, the PGW notifies the TDF to perform the charging stop operation through the PCRF and/or notifies the TDF to directly discard the data packet;

and under the condition that the PGW determines to execute the charging recovery operation on the data packet, the PGW informs the TDF to execute the charging recovery operation through the PCRF.

5. The method of claim 3, wherein after receiving the downlink data packet, the determining that the charging stop operation or the charging recovery operation is performed on the data packet by the PGW includes:

after receiving a downlink data packet on an unavailable bearer, the PGW determines to perform charging stop operation on the data packet; or,

and after receiving the downlink data packet on the load which is recovered to be normal, the PGW determines to execute charging recovery operation on the data packet.

6. The method of claim 4, wherein in case the PGW notifies the TDF to directly discard the data packet, the method further comprises:

and under the condition that the load is recovered to be normal, the PGW informs the TDF to execute charging recovery operation.

7. The method of claim 5, wherein before the PGW receives a downlink packet on an unavailable bearer, the method further comprises:

after the PGW detects that the SGW is restarted, reserving a bearing context and a user context;

the PGW marks the bearer as an unavailable bearer.

8. The method of claim 5, wherein before the PGW receives a downlink packet on an unavailable bearer, the method further comprises:

the PGW receives a bearer suspension notification message sent by a mobile management entity MME through an SGW;

the PGW returns a bearer suspension confirmation message to the MME through the SGW; wherein the suspended bearer of the PGW is an unavailable bearer.

9. The method of claim 5, wherein before the PGW receives the downlink data packet on the restored normal bearer, the method further comprises:

the PGW receives a bearer modification request message sent by the MME through the SGW;

the PGW returns a bearer modification response message to the MME through the SGW; wherein the modified bearer of the PGW is a normal restoration bearer.

10. The method of claim 9, wherein before the PGW receives the modify bearer request message sent by the MME through the SGW, the method further comprises:

the MME reselects an SGW; wherein, the reselected SGW is a restarted SGW or a normally working SGW.

11. The method of claim 9, wherein before the PGW receives the modify bearer request message sent by the MME through the SGW, the method further comprises:

and the MME receives a non-access stratum message sent by User Equipment (UE).

12. The method of claim 11, wherein the non-access stratum message is a Tracking Area Update (TAU) request message.

13. The method of claim 2, wherein the PGW notifying the TDF through the PCRF to perform the same charging operation as the PGW comprises:

the PGW sends a charging notification message to the PCRF; wherein the charging notification message is used to notify the TDF to perform the same charging operation as the PGW;

the PCRF sends the charging notification message to the TDF.

14. The method of claim 13, wherein after the PGW notifies the TDF through the PCRF to perform the same charging operation as the PGW, the method further comprises:

the TDF returns a charging notification response message to the PCRF;

and the PGW receives the charging notification response message sent by the PCRF.

15. The method of claim 2, further comprising:

after the PGW detects that the SGW is restarted, reserving a bearer context and a user context, and marking the bearer as an unavailable bearer;

after the PCRF detects that the SGW is restarted, the connection with the SGW is deleted, and user information and a strategy are reserved;

the PCRF sends the charging notification message to the TDF; wherein the accounting notification message is used to notify the TDF to perform an accounting stop operation.

16. The method of claim 2, further comprising:

after detecting that the SGW recovers the work, the PCRF sends the charging notification message to the TDF; wherein the charging notification message is used to notify the TDF to perform a charging recovery operation.

17. The method of claim 2, further comprising:

after detecting that the PGW is restarted, the PCRF deletes the connection with the PGW and retains user information and policies;

18. The method of claim 2, further comprising:

after detecting that the PGW recovers, the PCRF sends the charging notification message to the TDF; wherein the charging notification message is used to notify the TDF to perform a charging recovery operation.

19. A charging synchronization apparatus, comprising:

and the charging execution module is used for informing the service detection function entity TDF to execute the same charging operation as the PGW.

20. The apparatus of claim 19, wherein the billing execution module comprises:

and a charging execution unit, configured to notify, by a policy and charging rules function entity PCRF, the TDF to execute the same charging operation as the PGW.

21. The apparatus of claim 20, further comprising:

and the charging determining module is used for determining to execute charging stopping operation or charging recovering operation on the data packet after receiving the downlink data packet.

22. The apparatus of claim 21, wherein the charging performing unit comprises:

a first performing subunit, configured to, in a case where the PGW determines to perform a charging stop operation on the data packet, notify, by the PCRF, the TDF to perform the charging stop operation, and/or notify the TDF to directly discard the data packet;

a second performing subunit, configured to notify, by the PCRF, the TDF to perform a charging recovery operation if the PGW determines to perform the charging recovery operation on the data packet.

23. The apparatus of claim 21, wherein the billing determination module comprises:

a charging stop determining unit, configured to determine to perform a charging stop operation on a downlink data packet after receiving the data packet on an unavailable bearer; or,

and the charging recovery determining unit is used for determining to execute charging recovery operation on the data packet after receiving the downlink data packet on the load which is recovered to be normal.

24. The apparatus of claim 22, wherein in case the PGW notifies the TDF to directly discard the data packet, the apparatus further comprises:

and the notification module is used for notifying the TDF to execute the charging recovery operation under the condition that the load is recovered to be normal.

25. The apparatus of claim 23, wherein before the PGW receives the downlink packet on the unavailable bearer, the charging determining module further includes:

a reserving unit, configured to reserve a bearer context and a user context after detecting that a serving gateway SGW is restarted;

a marking unit for marking the bearer as unavailable.

26. The apparatus of claim 23, wherein before the PGW receives the downlink packet on the unavailable bearer, the charging determining module further includes:

a notification message receiving unit, configured to receive a bearer suspension notification message sent by an MME through an SGW;

a confirmation message returning unit, configured to return a bearer suspension confirmation message to the MME through the SGW; wherein the suspended bearer of the PGW is an unavailable bearer.

27. The apparatus of claim 23, wherein before the PGW receives the downlink data packet on the recovered normal bearer, the charging determining module further includes:

a request message receiving unit, configured to receive a bearer modification request message sent by the MME through an SGW;

a response message returning unit, configured to return a modified bearer response message to the MME through the SGW; wherein the modified bearer of the PGW is a normal restoration bearer.

28. A billing synchronization system, comprising: a packet data network gateway, PGW, a policy and charging rules function, PCRF, and a traffic detection function, TDF, wherein the PGW comprises the charging synchronization apparatus of any of claims 19 to 27,

the PGW includes: a first sending module, configured to send a charging notification message to the PCRF; wherein the charging notification message is used to notify the TDF to perform the same charging operation as the PGW;

the PCRF includes: a second sending module, configured to send the charging notification message to the TDF.

29. The system of claim 28,

the TDF includes: a response module, configured to return a charging notification response message to the PCRF;

the PGW further includes: and the receiving module is used for receiving the charging notification response message sent by the PCRF.

30. The system of claim 28,

the PGW further includes: a reserving module, configured to reserve a bearer context and a user context after detecting that the SGW is restarted, and mark the bearer as an unavailable bearer;

the PCRF further includes: the first deleting module is used for deleting the connection with the SGW after the SGW is detected to restart, and keeping user information and strategies;

the PCRF further includes: a first message sending module, configured to send the charging notification message to the TDF; wherein the accounting notification message is used to notify the TDF to perform an accounting stop operation.

31. The system of claim 28,

the PCRF further includes: a second message sending module, configured to send the charging notification message to the TDF after detecting that the SGW resumes operation; wherein the charging notification message is used to notify the TDF to perform a charging recovery operation.

32. The system of claim 28,

the PCRF further includes: a second deleting module, configured to delete the connection with the PGW and retain user information and a policy after detecting that the PGW is restarted;

the PCRF further includes: a third message sending module, configured to send the charging notification message to the TDF; wherein the accounting notification message is used to notify the TDF to perform an accounting stop operation.

33. The system of claim 28,

the PCRF further includes: a fourth message sending module, configured to send the charging notification message to the TDF after detecting that the PGW resumes operation; wherein the charging notification message is used to notify the TDF to perform a charging recovery operation.