WO2015039307A1

WO2015039307A1 - Charging method and device

Info

Publication number: WO2015039307A1
Application number: PCT/CN2013/083780
Authority: WO
Inventors: 陆伟; 李岩
Original assignee: 华为技术有限公司
Priority date: 2013-09-18
Filing date: 2013-09-18
Publication date: 2015-03-26
Also published as: CN104769978B; CN104769978A

Abstract

Provided are a charging method and device. The method comprises: a PCRF entity determines a first application that needs to be charged, and allocates a charging identifier for the first application; and the PCRF entity respectively sends an identifier of the first application and the charging identifier allocated to the first application to a UE, a PCEF entity and a TDF entity, so that the UE and the TDF entity add the charging identifier to a data packet of the first application, and then send same to the PCEF entity, and the PCEF entity independently charges data packets that carry the charging identifier from the UE and the TDF entity respectively on the basis of the identifier of the first application and the charging identifier allocated to the first application. The technical solution of the present invention can realize application-based charging.

Description

Billing method and equipment

The embodiments of the present invention relate to communication technologies, and in particular, to a charging method and device.

Background technique

The wireless communication network mainly includes two parts, namely an access network and a core network. The core network mainly includes mobile management network elements, gateway devices, and Policy and Charging Control (PCC) functional entities. The PCC functional entity is further divided into a Policy Control and Charging Rules Function (PCRF) entity and a Policy and Charging Enforcement Function entity. The PCRF entity mainly formulates corresponding policies according to factors such as the operator's policy, restrictions on the user's access to the network, user subscription data, and service information of the service data flow (SDF) currently being performed by the user. The PCC rule is a PCC rule. The PCEF entity performs the traffic statistics and accounting for the service data of the user equipment (User Equipment, UE for short).

Currently, charging the user's business data is performed by the PCEF entity based on the SDF granularity. Application data flow based charging is being discussed in current 3GPP organizations, but there is currently no corresponding solution. Summary of the invention

Embodiments of the present invention provide a charging method and device for implementing charging based on an application data stream.

The first aspect provides a charging method, including:

The policy control and charging rule function, the PCRF entity, determines a first application that needs to be charged, and allocates a charging identifier to the first application, where the charging identifier is used to identify that the first application needs to be separately charged;

The PCRF entity sends the identifier of the first application and the charging identifier allocated for the first application to the user equipment UE, the policy and charging execution PCEF entity, and the service detection function TDF, respectively. Entity, to enable the UE and the TDF entity to add the charging identifier to the data packet of the first application, and then send the charging identifier to the PCEF entity, so that the PCEF entity is based on the identifier of the first application. The charging identifier allocated for the first application separately charges the data packet carrying the charging identifier from the UE and the TDF entity separately.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the PCRF entity sends an identifier of the first application and a charging identifier allocated to the first application to a UE and a PCEF entity, respectively , including:

Sending, by the PCRF entity, an internet connection access network IP-CAN session establishment response message to the PCEF entity, where the IP-CAN session establishment response message includes an identifier of the first application and an allocation for the first application The fee identifier is configured to enable the PCEF entity to send the identifier of the first application and the charging identifier allocated for the first application to the UE by using a serving gateway device.

In conjunction with the first possible implementation of the first aspect, in a second possible implementation manner of the first aspect, before the sending, by the PCRF entity, the IP-CAN session establishment response message to the PCEF entity,

The PCRF entity receives an IP-CAN session establishment request message sent by the PCEF entity. With reference to the first aspect or the first possible implementation of the first aspect, or the second possible implementation of the first aspect, in a third possible implementation manner of the first aspect, the PCRF entity The identifier of the first application and the charging identifier TDF entity allocated to the first application, including: the PCRF entity sending a TDF session establishment request message to the TDF entity, where the TDF session establishment request message includes the first An identifier of the application and a charging identifier assigned to the first application.

With the third possible implementation of the first aspect, in a fourth possible implementation manner of the first aspect, after the sending, by the PCRF entity, the TDF session establishment request message to the TDF entity, the method further includes:

The PCRF entity receives a TDF session setup response message sent by the TDF entity.

With reference to the first aspect, in a fifth possible implementation manner of the foregoing aspect, the determining, by the PCRF entity, the first application that needs to be charged, includes:

Receiving, by the PCRF entity, a service flow detection event sent by the TDF entity, where the service flow detection event is sent by the TDF entity after detecting a data packet of the first application that needs to be charged, and the service flow is The detecting event includes an identifier of the first application; The PCRF entity determines the first application according to the identifier of the first application. With reference to the fifth possible implementation of the first aspect, in a sixth possible implementation manner of the first aspect, the PCRF entity, the identifier of the first application, and the accounting allocated for the first application The identifiers are sent to the UE and the PCEF entity respectively, including:

The PCRF entity sends a policy and charging rule message to the PCEF entity, where the policy and charging rule message includes an identifier of the first application and a charging identifier allocated for the first application, so that the The PCEF entity sends the identifier of the first application and the charging identifier allocated for the first application to the UE by using a serving gateway device.

In conjunction with the fifth possible implementation of the first aspect, or the sixth possible implementation of the first aspect, in a seventh possible implementation of the first aspect, the PCRF entity And the identifier and the TFP entity assigned to the first application, including:

The PCRF entity sends a modify application probe control ADC rule message to the TDF entity, where the modified ADC rule message includes an identifier of the first application and a charging identifier allocated for the first application.

The second aspect provides a charging method, including:

The policy and charging execution PCEF entity receives the policy control and charging rule function. The identifier of the first application that needs to be separately charged and the charging identifier that is allocated to the first application determined by the PCRF entity sent by the PCRF entity;

The PCEF entity sends the identifier of the first application and the charging identifier allocated to the first application to the user equipment UE through the serving gateway device, so that the UE is in the uplink data packet of the first application. Adding the charging identifier to the PCEF entity;

The PCEF entity receives an uplink data packet that is sent by the UE and carries the charging identifier, and performs independent charging on the uplink data packet that carries the charging identifier according to the charging identifier.

With reference to the second aspect, in a first possible implementation manner of the second aspect, the method further includes: receiving, by the PCEF entity, a downlink data packet that is sent by the TDF entity and carrying the charging identifier, and Performing separate charging on the downlink data packet carrying the charging identifier according to the charging identifier.

With reference to the second aspect or the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, the PCEF entity receives, by the PCRF entity, The identifier of the first application and the charging identifier assigned to the first application, the package Includes:

Receiving, by the PCEF entity, an internet connection access network IP-CAN session establishment response message sent by the PCRF entity, where the IP-CAN session establishment response message includes an identifier of the first application and an allocation for the first application Billing identifier; or

The PCEF entity receives the policy and charging rule message sent by the PCRF entity, where the policy and charging rule message includes an identifier of the first application and a charging identifier allocated for the first application.

With the second possible implementation of the second aspect, in a third possible implementation manner of the second aspect, before the PCEF entity receives the IP-CAN session establishment response message sent by the PCRF entity, the method further includes:

The PCEF entity sends an IP-CAN Session Establishment Request message to the PCRF entity.

With reference to the second aspect or the first possible implementation of the second aspect or the second possible implementation of the second aspect or the third possible implementation of the second aspect, the fourth possibility in the second aspect In the implementation manner, the PCEF entity sends the identifier of the first application and the charging identifier that is allocated to the first application to the UE by using the serving gateway device, including:

The PCEF entity sends an IP-CAN bearer setup response message to the serving gateway device, where the IP-CAN bearer setup response message includes an identifier of the first application and a charging identifier assigned to the first application, And causing the serving gateway device to send the identifier of the first application and the charging identifier allocated for the first application to the UE.

With the fourth possible implementation of the second aspect, in a fifth possible implementation manner of the second aspect, before the sending, by the PCEF entity, the IP-CAN bearer setup response message to the serving gateway device, the method further includes:

The PCEF entity receives an IP-CAN bearer setup request message sent by the serving gateway device, where the IP-CAN bearer setup request message includes an identifier of the UE.

The third aspect provides a charging method, including:

The service detection function TDF entity receives the policy control and charging rule function. The identifier of the first application that needs to be separately charged determined by the PCRF entity sent by the PCRF entity and the charging identifier allocated for the first application;

Determining, by the TDF entity, the downlink data packet of the first application according to the identifier of the first application, and adding the charging identifier to a downlink data packet of the first application; The TDF entity sends the downlink data packet that adds the charging identifier to the policy and charging execution PCEF entity, so that the PCEF entity separately counts the downlink data packet of the first application based on the charging identifier. fee.

With reference to the third aspect, in a first possible implementation manner of the third aspect, the TDF entity receives, by the PCRF entity, an identifier of the first application that is required to be separately charged by the PCRF entity, and is the first Apply the assigned billing identifier, including:

The TDF entity receives a TDF session establishment request message sent by the PCRF entity, where the TDF session establishment request message includes an identifier of the first application and a subscription identifier allocated for the first application.

With reference to the first possible implementation manner of the third aspect, in a second possible implementation manner of the third aspect, after the TDF entity receives the TDF session establishment request message sent by the PCRF entity, the method further includes:

The TDF entity sends a TDF Session Establishment Response message to the PCRF entity.

With reference to the third aspect, in a third possible implementation manner of the third aspect, the TDF entity receives, by the PCRF entity, an identifier of the first application that is required to be separately charged by the PCRF entity, and is the first Before applying the assigned billing identifier, it also includes:

The TDF entity detects a data packet of the first application that needs to be separately charged, and after detecting the data packet of the first application, sends a service flow detection event to the PCRF entity, where the service flow detection event The identifier of the first application is included, so that the PCRF entity determines that the first application needs to be separately charged according to the identifier of the first application.

With reference to the third possible implementation manner of the third aspect, in a fourth possible implementation manner of the third aspect, the TDF entity receives, by the PCRF entity, the first application that is required to be separately charged by the PCRF entity The identifier and the charging identifier assigned to the first application, including:

The TDF entity receives the modified application probe control ADC rule message sent by the PCRF entity, where the modified ADC rule message includes an identifier of the first application and a charging identifier allocated for the first application.

The fourth aspect provides a charging method, including:

Policy Control and Charging Rules Function The PCRF entity sends a Policy and Charging Control PCC Rule Identity and/or Service Data Flow SDF Template to the Traffic Detection Function TDF entity for the TDF entity to determine the impact policy and the charging execution PCEF entity is based on The first application of the SDF granularity charging result belongs to The identifier of the SDF and the traffic of the data packet of the first application;

Receiving, by the PCRF entity, the identifier of the SDF to which the first application belongs according to the PCC rule identifier and/or the SDF template, and the flow of the data packet of the first application, the PCRF entity The identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application are sent to the PCEF entity, so that the PCEF entity is based on the identifier of the SDF to which the first application belongs and the first The traffic of the applied data packet is adjusted according to the SDF granularity charging result of the uplink data packet from the user equipment UE. The data packet of the first application belongs to the uplink data packet from the UE.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the PCC rule identifier and/or the SDF template sent by the PCRF entity to the TDF entity includes:

The PCRF entity sends a TDF session establishment request message to the TDF entity, where the TDF session establishment request message includes the PCC rule identifier and/or an SDF template.

With the first possible implementation of the fourth aspect, in a second possible implementation manner of the fourth aspect, after the sending, by the PCRF entity, the TDF session establishment request message to the TDF entity, the method further includes:

With reference to the fourth aspect, or the first possible implementation manner of the fourth aspect, or the second possible implementation manner of the fourth aspect, in a third possible implementation manner of the fourth aspect, the PCRF entity The identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application are sent to the

PCEF entities, including:

The PCRF entity sends an Internet connection access network IP-CAN session modification request message to the PCEF entity, where the IP-CAN session modification request message includes an identifier of the SDF to which the first application belongs and data of the first application. The flow of the package.

The fifth aspect provides a charging method, including:

The policy and charging execution PCEF entity receives the policy control and charging rule function. The identifier sent by the PCRF entity affecting the PCEF entity based on the service data flow SDF granularity charging result, and the identifier of the SDF and the first application The traffic of the data packet, where the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application are the policy and charging control PCC rule identifier sent by the service detection function TDF entity according to the PCRF entity. / or SDF template is determined and sent to The PCRF entity;

The PCEF entity adjusts an uplink data packet from the user equipment UE based on the SDF granularity charging result according to the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application, where the The data packet of the first application belongs to an uplink data packet from the UE.

With reference to the fifth aspect, in a first possible implementation manner of the fifth aspect, the PCEF entity receives an identifier of an SDF that is sent by a PCRF entity and affects a SDF granularity-based charging result of the PCEF entity. Before the traffic of the data packet of the first application, the method further includes:

The PCEF entity performs SDF granularity based charging on uplink data packets from the UE. With reference to the fifth aspect, or the first possible implementation manner of the fifth aspect, in a second possible implementation manner of the fifth aspect, the PCEF entity receives, by the PCRF entity, an effect of the SDF granularity that affects the PCEF entity The identifier of the SDF to which the first application of the fee belongs and the traffic of the data packet of the first application, including:

Receiving, by the PCEF entity, an Internet connection access network IP-CAN session modification request message sent by the PCRF entity, where the IP-CAN session modification request message includes an identifier of the SDF to which the first application belongs and the first application The traffic of the packet.

A sixth aspect provides a charging method, including:

Service detection function TDF entity receives policy control and charging rule function The policy and charging control sent by the PCRF entity PCC rule identification and / or service data flow SDF template;

Determining, by the TDF entity, the identifier of the SDF to which the first application belongs to the SDF granularity-based charging result, and the data packet of the first application, according to the PCC rule identifier and/or the SDF template. Traffic flow

Transmitting, by the TDF entity, the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application to the PCEF entity by using the PCRF entity, so that the PCEF entity is based on the first application The identifier of the associated SDF and the traffic of the data packet of the first application are adjusted according to the SDF granularity charging result of the uplink data packet from the user equipment UE, where the data packet of the first application belongs to the UE Upstream packet.

With reference to the sixth aspect, in a first possible implementation manner of the sixth aspect, the receiving, by the TDF entity, the PCC rule identifier and/or the SDF template sent by the PCRF entity includes:

The TDF entity receives a TDF session establishment request message sent by the PCRF entity, where the TDF session establishment request message includes the PCC rule identifier and/or an SDF template. With reference to the first possible implementation manner of the sixth aspect, in a second possible implementation manner of the sixth aspect, after the TDF entity receives the TDF session establishment request message sent by the PCRF entity, the method further includes:

With reference to the sixth aspect, or the first possible implementation manner of the sixth aspect, or the second possible implementation manner of the sixth aspect, in a third possible implementation manner of the sixth aspect, And determining, by the PCC rule identifier and/or the SDF template, the identifier of the SDF that belongs to the first application that affects the SDF granularity-based charging result of the PCEF entity and the traffic of the data packet of the first application, including: the TDF entity according to the The PCC rule identifies the indicated PCC rule, determines an application to which the data packet discarded by performing the application-based flow control belongs, and determines, as the first application, the traffic of the discarded data packet as the data of the first application. The traffic of the packet, and determining the SDF to which the first application belongs; or

The TDF entity determines, according to the SDF template, that all data packets having the same IP address information in the uplink data packet from the UE are not required to be charged, from all data packets having the same IP address information. The application to which the data packet that actually needs to be charged belongs is used as the first application, and the traffic of the data packet that needs to be charged is determined as the traffic of the data packet of the first application, and the SDF to which the first application belongs is determined; Or,

When the TDF entity detects that all data packets having the same IP address information in the uplink data packet from the UE are not required to be charged, the TDF entity determines that it is unnecessary from all data packets having the same IP address information. The application to which the billed data packet belongs is used as the first application, and the traffic of the data packet that does not need to be charged is determined as the traffic of the data packet of the first application, and the SDF to which the first application belongs is determined.

A seventh aspect provides a charging method, including:

After receiving the uplink data packet sent by the PCEF entity, the service detection function TDF entity determines the reflow data, and adds a charging identifier to the reflow data, where the reflow data refers to the impact information in the uplink data packet. a data packet of a PCEF entity for charging the uplink data packet based on a service data flow SDF granularity;

The TDF entity sends the reflow data carrying the charging identifier to the PCEF entity, so that the PCEF entity performs charging based on the SDF granularity according to the reflow data carrying the charging identifier. The results are adjusted. With reference to the seventh aspect, in a first possible implementation manner of the seventh aspect, after the TDF entity receives the uplink data packet sent by the PCEF entity, determines the reflow data, and adds a charging identifier to the reflow data, Also includes:

The TDF entity receives the policy control and charging rule function, and the PCRF entity sent by the PCRF entity allocates the charging identifier for the reflow data.

With reference to the first possible implementation manner of the seventh aspect, in a second possible implementation manner of the seventh aspect, the TDF entity receives, by the PCRF entity, the PCRF entity that is allocated by the PCRF entity Fee identification, including:

The TDF entity receives a TDF session establishment request message sent by the PCRF entity, where the TDF session establishment request message includes the charging identifier.

With reference to the second possible implementation manner of the seventh aspect, in a third possible implementation manner of the seventh aspect, after the TDF entity receives the TDF session establishment request message sent by the PCRF entity, the method further includes:

The eighth aspect provides a charging method, including:

The policy and charging execution PCEF entity receives the reflow data carrying the charging identifier sent by the service detecting function TDF entity after performing the service data stream SDF granularity charging on the uplink data packet, where the reflow data is the TDF entity. Determining, in the uplink data packet, a data packet that affects the SDF granularity-based charging result of the uplink data packet by the PCEF entity;

The PCEF entity determines, according to the charging identifier, that the received data is the reflow data, determines an SDF to which the reflow data belongs, and adjusts the charging result of the determined SDF.

With reference to the eighth aspect, in a first possible implementation manner of the eighth aspect, before the PCEF entity receives the reflow data that is sent by the TDF entity and carries the charging identifier, the method includes:

The PCEF entity receives the policy control and charging rule function, and the PCRF entity sent by the PCRF entity allocates the charging identifier for the reflow data.

With reference to the first possible implementation manner of the eighth aspect, in a second possible implementation manner of the eighth aspect, the PCEF entity receives, by the PCRF entity, the PCRF entity to allocate the reflow data Fee identification, including:

The PCEF entity receives an Internet connection access network IP-CAN session establishment response message sent by the PCRF entity, where the IP-CAN session establishment response message includes the charging identifier. With the second possible implementation of the eighth aspect, in a third possible implementation manner of the eighth aspect, before the receiving, by the PCEF entity, the IP-CAN session establishment response message sent by the PCRF entity, the method further includes:

A ninth aspect provides a charging method, including:

Policy Control and Charging Rules Function The PCRF entity determines the charging identifier that needs to be assigned to the reflow packet, which refers to the service data flow in the uplink packet affecting the policy and charging execution PCEF entity to the upstream packet. a data packet of the SDF granularity charging result;

Sending, by the PCRF entity, the charging identifier to a service detecting function TDF entity and the PCEF entity, where the TDF entity determines the reflow data from the uplink data packet from the PCEF entity. Adding the charging identifier to the PCEF entity, sending the PCEF entity to determine the reflow data according to the charging identifier, and based on the reflow data, based on the SDF of the uplink data packet The granularity of the billing result is adjusted.

With reference to the ninth aspect, in a first possible implementation manner of the ninth aspect, the sending, by the PCRF entity, the charging identifier to the TDF entity includes:

The PCRF entity sends a TDF session establishment request message to the TDF entity, where the TDF session setup request message includes the charging identifier.

With reference to the first possible implementation manner of the ninth aspect, in a second possible implementation manner of the ninth aspect, after the sending, by the PCRF entity, the TDF session establishment request message to the TDF entity, the method further includes:

With reference to the ninth aspect, or the first possible implementation manner of the ninth aspect, or the second possible implementation manner of the ninth aspect, in a third possible implementation manner of the ninth aspect, the PCRF entity The billing identifier is sent to the PCEF entity, including:

The PCRF entity sends an internet connection access network IP-CAN session establishment response message to the PCEF entity, and the IP-CAN session establishment response message includes the charging identifier.

In conjunction with the third possible implementation of the ninth aspect, in a fourth possible implementation manner of the ninth aspect, before the sending, by the PCRF entity, the IP-CAN session establishment response message to the PCEF entity,

The PCRF entity receives an IP-CAN session establishment request message sent by the PCEF entity. The tenth aspect provides a policy control and charging rule function PCRF entity, including:

a determining module, configured to determine a first application that needs to be billed;

An allocating module, configured to allocate a charging identifier to the first application, where the charging identifier is used to identify that the first application needs to be separately charged;

a sending module, configured to send the identifier of the first application determined by the determining module and the charging identifier allocated by the allocating module to the first application to a user equipment UE, a policy and a charging execution PCEF entity, and The service detection function TDF entity, so that the UE and the TDF entity add the charging identifier to the data packet of the first application, and then send the charging identifier to the PCEF entity, so that the PCEF entity is based on the first The identifier of the application and the charging identifier allocated for the first application separately charge the data packet carrying the charging identifier from the UE and the TDF entity separately.

With the tenth aspect, in a first possible implementation manner of the tenth aspect, the sending module is configured to send an identifier of the first application and a charging identifier allocated to the first application to a UE and a PCEF entities, including:

The sending module is specifically configured to send an Internet connection access network IP-CAN session establishment response message to the PCEF entity, where the IP-CAN session establishment response message includes an identifier of the first application and is used by the first application. The assigned charging identifier, so that the PCEF entity sends the identifier of the first application and the charging identifier allocated for the first application to the UE by using a serving gateway device.

With reference to the tenth aspect, or the first possible implementation manner of the tenth aspect, in the second possible implementation manner of the tenth aspect, the sending module, the identifier of the first application is the first application The assigned billing identifier TDF entity, including:

The sending module is specifically configured to send a TDF session establishment request message to the TDF entity, where the TDF session establishment request message includes an identifier of the first application and a charging identifier allocated for the first application.

With reference to the tenth aspect, in a third possible implementation manner of the tenth aspect, the determining module is specifically configured to receive a service flow detection event that is sent by the TDF entity, where the service flow detection event is the TDF entity detection And sending, after the data packet of the first application that needs to be charged, the service flow detection event includes an identifier of the first application; determining the first application according to the identifier of the first application.

In conjunction with the third possible implementation of the tenth aspect, the fourth possible implementation in the tenth aspect In the current mode, the sending module is configured to send the identifier of the first application and the charging identifier that is allocated to the first application to the UE and the PCEF entity, respectively, including:

The sending module is specifically configured to send a policy and charging rule message to the PCEF entity, where the policy and charging rule message includes an identifier of the first application and a charging identifier allocated to the first application, And causing the PCEF entity to send, by the serving gateway device, the identifier of the first application and the charging identifier allocated for the first application to the UE.

With the third possible implementation of the tenth aspect, or the fourth possible implementation of the tenth aspect, in a fifth possible implementation manner of the tenth aspect, the sending module is configured to use the first The identifier of the application and the charging identifier TDF entity allocated for the first application, including:

The sending module is specifically configured to send a modified application detection control ADC rule message to the TDF entity, where the modified ADC rule message includes an identifier of the first application and a charging identifier allocated for the first application.

The eleventh aspect provides a policy and charging execution PCEF entity, including:

a receiving module, configured to receive a policy control and charging rule function, the identifier of the first application that is separately billed by the PCRF entity sent by the PCRF entity, and the charging identifier allocated for the first application;

a sending module, configured to send, by the serving gateway device, the identifier of the first application and the charging identifier that is configured by the receiving module to the user equipment, to enable the UE to be in the Adding the charging identifier to an uplink data packet of an application, and sending the charging identifier to the PCEF entity; the receiving module is further configured to receive an uplink data packet that is sent by the UE and that carries the charging identifier;

The charging module is configured to separately charge the uplink data packet that is received by the receiving module and that carries the charging identifier according to the charging identifier.

With the eleventh aspect, in a first possible implementation manner of the eleventh aspect, the receiving module is further configured to receive a downlink data packet that is sent by the TDF entity and that carries the charging identifier.

The charging module is further configured to separately charge the downlink data packet that is received by the receiving module and that carries the charging identifier according to the charging identifier.

With the first possible implementation of the eleventh aspect or the eleventh aspect, in a second possible implementation manner of the eleventh aspect, the receiving module is configured to receive, by the PCRF entity, The identifier of the first application that needs to be separately charged and the charging identifier that is allocated for the first application, which is determined by the PCRF entity, includes:

The receiving module is specifically configured to receive an Internet connection access network IP-CAN session establishment response message sent by the PCRF entity, where the IP-CAN session establishment response message includes an identifier of the first application and is the first application. Allocated billing identifier; or

The receiving module is specifically configured to receive a policy and charging rule message sent by the PCRF entity, where the policy and charging rule message includes an identifier of the first application and a charging identifier allocated for the first application.

With reference to the eleventh aspect or the first possible implementation manner of the eleventh aspect, or the second possible implementation manner of the eleventh aspect, in a third possible implementation manner of the eleventh aspect, the sending The module is configured to send the identifier of the first application and the charging identifier that is allocated to the first application to the UE by using the serving gateway device, including:

The sending module is specifically configured to send an IP-CAN bearer setup response message to the serving gateway device, where the IP-CAN bearer setup response message includes an identifier of the first application and a billing allocated for the first application. And the identifier is sent to the serving gateway device to send the identifier of the first application and the charging identifier allocated to the first application to the UE.

The twelfth aspect provides a service detection function TDF entity, including:

Determining an adding module, configured to determine, according to the identifier of the first application received by the receiving module, a downlink data packet of the first application, and adding, in a downlink data packet of the first application, a received by the receiving module Description of the charging identifier;

a sending module, configured to send a downlink data packet that adds the charging identifier to a policy and charging execution PCEF entity, so that the PCEF entity separately performs downlink data packets of the first application based on the charging identifier Billing.

With reference to the twelfth aspect, in a first possible implementation manner of the twelfth aspect, the receiving module is configured to receive, by the PCRF entity, an identifier of the first application that is separately billed by the PCRF entity and The charging identifier allocated by the first application includes:

The receiving module is specifically configured to receive a TDF session establishment request sent by the PCRF entity. The TDF session establishment request message includes an identifier of the first application and a charging identifier allocated for the first application.

In conjunction with the twelfth aspect, in a second possible implementation of the twelfth aspect, the TDF entity further includes: a detecting module, configured to detect a data packet of the first application that needs to be separately charged; The sending module is further configured to: after the detecting module detects the data packet of the first application, send a service flow detecting event to the PCRF entity, where the service flow detecting event includes an identifier of the first application, And causing the PCRF entity to determine, according to the identifier of the first application, that the first application needs to be separately charged.

With the second possible implementation of the twelfth aspect, in a third possible implementation manner of the twelfth aspect, the receiving module is configured to receive, by the PCRF entity, The identifier of the first application and the charging identifier allocated to the first application, the method includes: the receiving module is configured to receive a modified application detection control ADC rule message sent by the PCRF entity, where the modifying the ADC rule message includes An identifier of the first application and a charging identifier assigned to the first application.

The thirteenth aspect provides a policy control and charging rule function PCRF entity, including: a processor, configured to determine a first application that needs to be charged, and allocate a charging identifier to the first application, where the charging identifier is Used to identify that the first application needs to be separately charged;

a transmitter, configured to send, by the processor, an identifier of the first application and a charging identifier allocated by the processor to the first application to a user equipment UE, a policy and charging execution PCEF entity, and The service detecting function TDF entity, so that the UE and the TDF entity add the charging identifier to the data packet of the first application, and then send the charging identifier to the PCEF entity, so that the PCEF entity is based on the first The identifier of the application and the charging identifier allocated for the first application separately charge the data packet carrying the charging identifier from the UE and the TDF entity separately.

A fourteenth aspect provides a policy and charging enforcement PCEF entity, including:

a receiver, configured to receive a policy control and charging rule function, and the identifier of the first application that is separately billed by the PCRF entity and the charging identifier that is allocated for the first application determined by the PCRF entity;

a transmitter, configured to send, by the serving gateway device, an identifier of the first application and a charging identifier that is allocated by the receiver to the user equipment, to enable the UE to be in the Adding the charging identifier to an uplink data packet of an application, and sending the identifier to the PCEF entity; The receiver is further configured to receive an uplink data packet that is sent by the UE and that carries the charging identifier;

The processor is configured to separately charge the uplink data packet that is received by the receiver and that carries the charging identifier according to the charging identifier.

The fifteenth aspect provides a service detection function TDF entity, including:

a processor, configured to determine, according to the identifier of the first application received by the receiver, a downlink data packet of the first application, and add, in a downlink data packet of the first application, the received by the receiver Billing identifier

a transmitter, configured to send a downlink data packet that adds the charging identifier to a policy and charging execution

And a PCEF entity, to enable the PCEF entity to separately charge the downlink data packet of the first application based on the charging identifier.

The sixteenth aspect provides a policy control and charging rule function PCRF entity, including: a sending module, a policy and charging control PCC rule identifier and/or a service data flow SDF template sent to the service detecting function TDF entity, Determining, by the TDF entity, an identifier of the SDF to which the first application to which the impact policy and the charging execution PCEF entity performs the SDF granularity based charging result and the traffic of the data packet of the first application;

a receiving module, configured to receive, according to the PCC rule identifier, sent by the TDF entity, and/or

The identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application determined by the SDF template;

The sending module is further configured to send the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application to the PCEF entity, so that the PCEF entity is based on the first application The identifier of the SDF and the traffic of the data packet of the first application are adjusted according to the SDF granularity charging result of the uplink data packet from the user equipment UE; wherein the data packet of the first application belongs to the UE from the UE Upstream packet.

In conjunction with the sixteenth aspect, in a first possible implementation manner of the sixteenth aspect, the sending, by the sending module, the PCC rule identifier and/or the SDF template that is sent to the TDF entity includes:

The sending module is specifically configured to send a TDF session establishment request message to the TDF entity, where The TDF session establishment request message includes the PCC rule identifier and/or an SDF template. In conjunction with the sixteenth aspect or the first possible implementation manner of the sixteenth aspect, in a second possible implementation manner of the sixteenth aspect, the sending module is configured to: And sending the traffic of the data packet of the first application to the PCEF entity, including:

The sending module is specifically configured to send an internet connection access network to the PCEF entity

The IP-CAN session modification request message includes the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application.

The seventeenth aspect provides a policy and charging execution PCEF entity, including:

a receiving module, configured to receive, by the policy control and charging rule function, the identifier of the SDF that is sent by the first application that affects the PCEF entity based on the serving data flow SDF granularity, and the data packet of the first application The traffic of the SDF to which the first application belongs and the traffic of the data packet of the first application are the service detection function TDF entity according to the policy and charging control PCC rule identifier sent by the PCRF entity and/or The SDF template is determined and sent to the PCRF entity;

The charging adjustment module is configured to adjust, according to the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application, the uplink data packet from the user equipment UE, based on the SDF granularity charging result, where The data packet of the first application belongs to an uplink data packet from the UE.

In conjunction with the seventeenth aspect, in a first possible implementation of the seventeenth aspect, the PCEF entity further includes: a charging module, configured to receive, at the receiving module, an identifier and a location of an SDF to which the first application belongs Before the traffic of the data packet of the first application, the SDF granularity based charging is performed on the uplink data packet from the UE.

With reference to the seventeenth aspect, or the first possible implementation manner of the seventeenth aspect, in a second possible implementation manner of the seventeenth aspect, the receiving module is configured to receive, by the PCRF entity, the PCEF entity The identifier of the SDF to which the first application belongs to the SDF granularity-based charging result and the traffic of the data packet of the first application, including:

The receiving module is specifically configured to receive an Internet connection access network IP-CAN session modification request message sent by the PCRF entity, where the IP-CAN session modification request message includes an identifier of the SDF to which the first application belongs, and the The traffic of an application's packets.

The eighteenth aspect provides a service detection function TDF entity, including:

a receiving module, configured to receive a policy control and charging rule function, a policy and a meter sent by a PCRF entity Fee control PCC rule identification and / or service data flow SDF template;

a determining module, configured to determine, according to the PCC rule identifier and/or the SDF template received by the receiving module, an identifier and a location of the SDF to which the first application belongs to the SDF granularity-based charging result of the PCEF entity The traffic of the data packet of the first application;

a sending module, configured to send, by the PCRF entity, the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application to the PCEF entity, to make the PCEF The entity adjusts the uplink data packet from the user equipment UE based on the SDF granularity charging result based on the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application, where the first application is The data packet belongs to an upstream data packet from the UE.

In conjunction with the eighteenth aspect, in a first possible implementation of the eighteenth aspect, the receiving module is configured to receive a PCC rule identifier and/or an SDF template sent by the PCRF entity, including:

The receiving module is specifically configured to receive a TDF session establishment request message sent by the PCRF entity, where the TDF session establishment request message includes the PCC rule identifier and/or an SDF template.

In conjunction with the eighteenth aspect, or the first possible implementation manner of the eighteenth aspect, in a second possible implementation manner of the eighteenth aspect, the determining module is configured to receive the PCC according to the receiving module The rule identifier and/or the SDF template, the identifier of the SDF to which the first application that affects the charging result of the SDF granularity of the PCEF entity is determined, and the traffic of the data packet of the first application, the determining module is specifically configured to be used according to the Determining, by the receiving module, the PCC rule indicated by the PCC rule identifier, determining, by using the application that belongs to the data packet that is discarded by performing the application-based flow control, as the first application, determining the traffic of the discarded data packet As the traffic of the data packet of the first application, and determining the SDF to which the first application belongs; or

The determining module is specifically configured to: when the SDF template received by the receiving module detects that all data packets having the same IP address information in the uplink data packet from the UE are not required to be charged, the same IP is obtained. In the data packet of the address information, the application to which the data packet actually required to be charged belongs is determined as the first application, and the traffic of the data packet actually required to be charged is determined as the traffic of the data packet of the first application, and is determined. The SDF to which the first application belongs; or

The determining module is specifically configured to: when the SDF template received by the receiving module detects that all data packets having the same IP address information in the uplink data packet from the UE are not required to be charged, the same IP is obtained. All data packets of the address information, determining an application to which the data packet that does not need to be charged belongs as the first application, determining traffic of the data packet that does not need to be charged as the first The traffic of an application's data packet, and determines the SDF to which the first application belongs.

A nineteenth aspect provides a policy control and charging rule function PCRF entity, including: a transmitter, a policy and charging control PCC rule identifier and/or a service data flow SDF template sent to a service detection function TDF entity, Determining, by the TDF entity, an identifier of the SDF to which the first application to which the impact policy and the charging execution PCEF entity performs the SDF granularity based charging result and the traffic of the data packet of the first application;

a receiver, configured to receive, by the TDF entity, the identifier of the SDF to which the first application belongs according to the PCC rule identifier and/or the SDF template, and the flow of the data packet of the first application And sending, to the PCEF entity, the identifier of the SDF to which the first application belongs and the data packet of the first application, so that the PCEF entity is based on the identifier of the SDF to which the first application belongs The traffic of the data packet of the first application is adjusted according to the SDF granularity charging result of the uplink data packet from the user equipment UE; wherein the data packet of the first application belongs to an uplink data packet from the UE.

The twentieth aspect provides a policy and charging execution PCEF entity, including:

a receiver, configured to receive, by the policy control and charging rule function, the identifier of the SDF that is sent by the first application that affects the PCEF entity based on the service data flow SDF granularity charging result, and the data packet of the first application The traffic of the SDF to which the first application belongs and the traffic of the data packet of the first application are the service detection function TDF entity according to the policy and charging control PCC rule identifier sent by the PCRF entity and/or The SDF template is determined and sent to the PCRF entity;

a processor, configured to adjust an uplink data packet from the user equipment UE according to an SDF granularity charging result according to the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application, where The data packet of the first application belongs to an uplink data packet from the UE.

The twenty-first aspect provides a service detection function TDF entity, including:

Receiver for receiving policy control and charging rule functions, policy and charging control sent by the PCRF entity, PCC rule identification and/or service data flow SDF template;

a processor, configured to determine, according to the PCC rule identifier and/or the SDF template received by the receiver, an identifier and a location of an SDF to which the first application that affects the policy and charging execution PCEF entity based on the SDF granularity charging result The traffic of the data packet of the first application; a transmitter, configured to send, by the processor, an identifier of an SDF to which the first application belongs and a traffic of a data packet of the first application to the PCEF entity by using the PCRF entity, to enable the PCEF The entity adjusts the uplink data packet from the user equipment UE based on the SDF granularity charging result based on the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application, where the first application is The data packet belongs to an upstream data packet from the UE.

The twenty-second aspect provides a service detection function TDF entity, including:

a receiving module, configured to receive an uplink data packet sent by the PCEF entity by using a policy and a charging, and determining an adding module, configured to: after the receiving module receives the uplink data packet, determine reflow data, and add the reflow data a billing identifier, where the reflow data refers to a data packet in the uplink data packet that affects the charging result of the PCEF entity based on the service data stream SDF granularity of the uplink data packet;

a sending module, configured to send the reflow data carrying the charging identifier to the PCEF entity, so that the PCEF entity is based on the SDF granularity of the uplink data packet according to the reflow data carrying the charging identifier The fee results are adjusted.

With reference to the twenty-second aspect, in a first possible implementation manner of the twenty-second aspect, the receiving module is further configured to: before the determining adding module adds a charging identifier to the reflow data, receiving a policy control And the charging identifier that is sent by the PCRF entity sent by the PCRF entity to the reflow data.

With reference to the first possible implementation of the twenty-second aspect, in a second possible implementation manner of the second aspect, the receiving module is configured to receive, by the PCRF entity, the PCRF entity as the reflow The charging identifier of the data distribution includes:

The receiving module is specifically configured to receive a TDF session establishment request message sent by the PCRF entity, where the TDF session establishment request message includes the charging identifier.

The twenty-third aspect provides a policy and charging execution PCEF entity, including:

a receiving module, configured to: after performing service-based data stream SDF granularity charging on the uplink data packet, receive, by the service detecting function TDF entity, reflow data carrying the charging identifier, where the reflow data is determined by the TDF entity a data packet in the uplink data packet that affects an SDF granularity-based charging result of the uplink data packet by the PCEF entity;

a billing adjustment module, configured to determine, according to the billing identifier, that the data received by the receiving module is the reflow data, determine an SDF to which the reflow data belongs, and charge the determined SDF The results are adjusted.

In conjunction with the twenty-third aspect, in a first possible implementation manner of the twenty-third aspect, the receiving module is further configured to receive a policy before receiving the reflow data carried by the TDF entity and carrying the charging identifier The control and charging rule function sends the charging identifier assigned by the PCRF entity to the reflow data.

With reference to the first possible implementation of the twenty-third aspect, in a second possible implementation manner of the twenty-third aspect, the receiving module is configured to receive, by the PCRF entity, the PCRF entity as the reflow The charging identifier of the data distribution includes:

The receiving module is specifically configured to receive an Internet connection access network IP-CAN session establishment response message sent by the PCRF entity, where the IP-CAN session establishment response message includes the charging identifier.

The twenty-fourth aspect provides a policy control and charging rule function PCRF entity, including: a determining module, configured to determine a charging identifier that needs to be allocated to a reflow data packet, where the reflow data refers to an impact policy in the uplink data packet Charging a data packet of a service data flow SDF granularity based charging result of the uplink data packet by the PCEF entity;

a sending module, configured to send the charging identifier to the service detecting function TDF entity and the PCEF entity, where the TDF entity determines the reflow data from the uplink data packet from the PCEF entity Adding the charging identifier to the PCEF entity, and sending the PCEF entity to determine, according to the charging identifier, the reflow data, and based on the reflow data, the uplink data packet is based on The billing result of the SDF granularity is adjusted.

In conjunction with the twenty-fourth aspect, in a first possible implementation of the twenty-fourth aspect, the sending, by the sending, the sending, by the sending,

The sending module is specifically configured to send a TDF session establishment request message to the TDF entity, where the TDF session establishment request message includes the charging identifier.

With reference to the twenty-fourth aspect or the first possible implementation manner of the twenty-fourth aspect, in a second possible implementation manner of the twenty-fourth aspect, the sending module is configured to send the charging identifier To the PCEF entity, including:

The sending module is specifically configured to send an internet connection access network IP-CAN session establishment response message to the PCEF entity, where the IP-CAN session establishment response message includes the charging identifier. The twenty-fifth aspect provides a service detection function TDF entity, including:

a receiver, configured to receive an uplink data packet sent by the PCEF entity, and a processor, configured to: after the receiver receives the uplink data packet, determine reflow data, and add a meter for the reflow data a fee identifier, where the reflow data refers to a data packet in the uplink data packet that affects the charging result of the PCEF entity based on the service data flow SDF granularity of the uplink data packet;

a transmitter, configured to send the reflow data carrying the charging identifier to the PCEF entity, so that the PCEF entity is based on the reflow data carrying the charging identifier, and the uplink data packet is based on

The billing result of the SDF granularity is adjusted.

The twenty-sixth aspect provides a policy and charging execution PCEF entity, including:

a receiver, configured to receive reflow data carried by the service detection function TDF entity and carrying the charging identifier, after the serving data stream SDF granularity charging of the uplink data packet, where the reflow data is determined by the TDF entity a data packet in the uplink data packet that affects an SDF granularity-based charging result of the uplink data packet by the PCEF entity;

And a processor, configured to determine, according to the charging identifier, that the data received by the receiver is the backflow data, determine an SDF to which the reflow data belongs, and adjust a charging result of the determined SDF.

The twenty-seventh aspect provides a policy control and charging rule function PCRF entity, including: a processor, configured to determine a charging identifier that needs to be allocated to a reflow packet, where the reflow data refers to an impact policy in an uplink packet Charging a data packet of a service data flow SDF granularity based charging result of the uplink data packet by the PCEF entity;

a transmitter, configured to send the charging identifier to a service detecting function TDF entity and the PCEF entity, where the TDF entity determines the reflow data from the uplink data packet from the PCEF entity Adding the charging identifier to the PCEF entity, adding the charging identifier to the PCEF entity, causing the PCEF entity to determine the reflow data according to the charging identifier, and based on the reflow data, the uplink data packet is based on The billing result of the SDF granularity is adjusted.

The charging method and the device provided by the embodiment of the present invention allocate a charging identifier for an application that needs to be separately charged, and implement an identifier for an application that needs to be separately charged, and implement independent charging for the application based on the charging identifier. . BRIEF DESCRIPTION OF THE DRAWINGS In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief description of the drawings used in the embodiments or the prior art description will be briefly described below. The drawings are some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without any inventive labor.

FIG. 1 is a schematic diagram of three access technologies in a current wireless communication network according to an embodiment of the present invention. FIG. 2 is a data flow interface and a direction of a control plane and a user plane in control and management of a wireless communication system according to an embodiment of the present invention. Schematic diagram

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

4 is a flowchart of another charging method according to an embodiment of the present invention.

FIG. 5 is a flowchart of still another charging method according to an embodiment of the present invention;

6 is a flowchart of still another charging method according to an embodiment of the present invention.

FIG. 7 is a structural diagram of a PCRF entity according to an embodiment of the present invention.

FIG. 8 is a block diagram of another PCRF entity according to an embodiment of the present invention.

FIG. 9 is a schematic structural diagram of a PCEF entity according to an embodiment of the present invention.

FIG. 10 is a diagram of another PCEF entity according to an embodiment of the present invention.

Figure 1 1 is the present invention: ; The structure of a TDF entity provided by the example ^

Figure 12 is a view of the present invention: another TDF entity provided by the embodiment

Figure 13 is the present invention:; another embodiment of the PCRF body provided;

Figure 14 is the present invention:; another embodiment of the PCRF body provided;

Figure 15 is the present invention:; another embodiment of the PCEF body provided by the embodiment;

Figure 16 is the present invention:; another embodiment of the PCEF body provided by the embodiment;

Figure 17 is a view of the present invention: - TDF % provided by the embodiment;

Figure 18 is a view of the present invention;

Figure 19 is a view of the present invention:

Figure 20 is a view of the present invention;

Figure 21 is the present invention:; another embodiment of the PCEF body provided by the embodiment;

Figure 22 is the present invention:; another embodiment of the PCEF ^ body provided;

Figure 23 is the present invention:; another embodiment of the PCRF ^ body provided; FIG. 24 is a schematic structural diagram of still another PCRF entity according to an embodiment of the present invention.

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. The embodiments are a part of the embodiments of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The current wireless communication network has three access technologies, one is the Global System of Mobile communication (GSM), commonly referred to as 2G; - Wozhong is the Universal Mobile Telecommunications system (Universal Mobile Telecommunications) System, Jane is UMTS), commonly referred to as 3G; and Long Term Evolved (LTE) system, commonly referred to as 4G. The system architecture under the three access technologies is shown in Figure 1.

No matter which access technology network architecture can be divided into two parts, one is the access network part, one core network part. The core network part is further divided into a mobility management network element, a gateway device, and a PCC part. The access network part is mainly responsible for radio access layer signaling and user data transmission. Specifically, in GSM, the access network part mainly refers to GERAN (English: GSM EDGE Radio Access Network) in Figure 1, including BTS and BSC; In UMTS, the access network part mainly refers to the UTRAN in FIG. 1, including the RNC and the NodeB; in the LTE system, the access network part mainly refers to the E-UTRAN in FIG. 1, including the eNodeB. The other part of the architecture shown in Figure 1 except the access network part is the core network part. The SGSN of GSM and UMTS and the 匪E of the LTE system are called mobility management network elements, which are mainly used to acquire users. Signing data, responsible for NAS signaling and NAS signaling encryption, roaming, tracking, etc., assigning user temporary identity, security functions, etc. The GGSN in GSM and UMTS and the PGW in the LTE system are gateway devices, which are mainly responsible for policy enforcement and charging and lawful interception related functions. In addition, an important component of the core network is the PCC part, which includes a PCRF entity and a PCEF entity. The PCEF entity is usually combined with a gateway device, such as a GGSN or a PGW, and is subscribed to a database (Subscription Profile Repository, SPR for short). ), Application Function (AF) entities, etc. together implement the PCC part. SPR is not shown in Figure 1.

The PCRF entity is mainly based on the operator's policy, restrictions on user access to the network, and number of user subscriptions. According to factors such as the service information of the SDF currently being performed by the user, a corresponding policy is formulated, which is called a PCC rule; the PCEF entity mainly performs a PCC rule formulated by the PCRF entity, for example, detecting and measuring the SDF according to the PCC rule, Quality of Service (QoS), user-side traffic detection, and session management for triggering control planes. Further, in order to guarantee the QoS of the service, all Internet Protocol (IP) data packets sent by the UE or all IP data packets to be received need to pass through the PCEF, and the PCEF will serve the data flow and bearer according to the QoS parameters of the SDF. Binding, for example, the QoS Class Identifier (QCI) is the same as the Address Resolution Protocol (ARP) service data flow on the same bearer, so as to facilitate other core networks. The network element performs flow control based on the bearer. In addition, the PCEF will also receive the service data stream according to the charging policy and charging method delivered by the PCRF.

Currently, charging the user's business data is performed by the PCEF entity based on the SDF granularity. Application data flow based charging is being discussed in current 3GPP organizations. The present invention provides the following two solutions for the application data flow based charging that is currently being discussed by the 3GPP organization. One is to implement an application data flow-based charging scheme on a Traffic Detection Function (TDF) entity, and the other is to implement an application data flow-based charging scheme on a PCEF entity.

The TDF entity is a functional entity of the Deep Packet Inspection (DPI) device, and can perform detection on the data packet according to the detection rule of the data packet sent by the PCRF entity, for example, detecting a certain type of application (QQ). The data packet, or the data packet of the specified Uniform Resource Locator (URL), is detected, and the packet event is reported to the PCRF entity after detecting the application data packet that satisfies the condition. In addition, the TDF entity may also perform flow control on the detected application data packets, such as the maximum bit rate limit of uplink and downlink. Figure 2 shows the data flow interface and direction of the control plane and the user plane in the control and management of the wireless communication system. As shown by the dotted line with an arrow in FIG. 2, the uplink data packet sent by the UE first passes through the PCEF entity, and then passes through the TDF entity to reach the network side, correspondingly, as shown by the solid line with an arrow in FIG. 2, the network The downlink data packet sent by the side must pass through the TDF entity before passing through the PCEF entity to reach the UE.

In the first solution, for the uplink data packet, it is possible to pass the SDF granularity-based charging of the PCEF entity, and then the TDF entity is based on the application data flow-based charging, and the repeated charging causes the charging to be inaccurate; For the downlink data stream, because the PCEF entity is to implement the SDF QoS policy Slightly, the packets that have been billed in the TDF entity may be discarded, which may result in inaccurate billing.

In the second solution, after detecting the application to which the downlink data packet belongs, the TDF entity identifies the downlink data packet, so that the PCEF entity identifies the application to which the downlink data packet belongs according to the identifier, and performs charging, thereby implementing Based on the application data flow-based charging, but for the uplink data packet, the PCEF entity cannot identify the application to which the uplink data packet belongs, and only after performing the SDF granularity-based charging, the uplink data packet is sent to the TDF entity, and the TDF entity detects The application to which the uplink data packet belongs is fed back to the PCEF entity. At this time, the PCEF entity charges the uplink data packet to implement charging based on the application data flow, which has the problem of repeated charging, and also causes charging. Inaccurate.

The following embodiments of the present invention provide a more detailed and complete solution to the problems that are currently being discussed in application-based data flow-based charging in the 3GPP organization, and the solutions provided above.

The main idea of the first charging method provided by the present invention is: determining, by the PCRF entity, the first application that needs to be charged, and assigning a charging identifier to the first application, where the charging identifier needs to be used for the first application. Separate billing; then the PCRF entity sends the identifier of the first application and the charging identifier assigned to the first application to the TDF entity, the PCEF entity, and the UE respectively; thus, before the UE sends the uplink packet of the first application to the PCEF entity, Adding the charging identifier to the uplink data packet of the first application, and then sending the uplink data packet that adds the charging identifier to the PCEF entity, where the PCEF entity can receive the received uplink carrying the charging identifier. The data packet is separately charged, and the first application is separately charged in the uplink direction, and since the uplink data packet of the first application can be identified, there is no problem of repeated charging; similarly, the TDF entity sends the data to the PCEF entity. Before the downlink data packet of the first application, adding the charging identifier to the downlink data packet of the first application, and then adding the charging identifier The uplink data packet is sent to the PCEF entity, and the PCEF entity can separately charge the received downlink data packet carrying the charging identifier to implement separate charging for the first application in the downlink direction, because the first packet can be identified. The downlink packet of the application does not have the problem of repeated charging.

Based on the main idea of the first charging method, the flow of the first charging method is described in detail from the perspective of a PCRF entity, a PCEF entity, a TDF entity, and a UE.

The method flow described from the perspective of the PCRF entity includes:

The PCRF entity determines a first application that needs to be charged, and allocates a charging identifier to the first application, where the charging identifier is used to identify that the first application needs to be separately charged. The PCRF entity sends the identifier of the first application and the charging identifier allocated for the first application to the UE, the PCEF entity, and the TDF entity, respectively, so that the UE and the TDF entity are in the data packet of the first application. Adding the charging identifier to the PCEF entity, and causing the PCEF entity to carry the bearer from the UE and the TDF entity according to the identifier of the first application and the charging identifier allocated for the first application, respectively. The data packet of the charging identifier is separately charged, thereby implementing separate charging for the first application.

In an optional implementation, the PCRF entity sends the identifier of the first application and the charging identifier allocated for the first application to the UE, including:

The PCRF entity sends an IP-CAN session establishment response message to the PCEF entity, where the IP-CAN session establishment response message includes an identifier of the first application and an assigned charging identifier for the first application, so that The PCEF entity sends the identifier of the first application and the charging identifier allocated for the first application to the UE by using a serving gateway device.

Based on the foregoing, before the PCRF entity sends the IP-CAN session establishment response message to the PCEF entity, the method further includes: the PCRF entity receiving the IP-CAN session establishment request message sent by the PCEF entity.

In an optional implementation, the PCRF entity sends the identifier of the first application and the charging identifier allocated for the first application to the TDF entity, including:

The PCRF entity sends a TDF session establishment request message to the TDF entity, where the TDF session establishment request message includes an identifier of the first application and a charging identifier allocated for the first application.

Further, after the PCRF entity sends the TDF session establishment request message to the TDF entity, the method further includes: the PCRF entity receiving the TDF session establishment response message sent by the TDF entity.

In an optional implementation, the PCRF entity determines the first application that needs to be charged, and the method includes: the PCRF entity receives a service flow detection event sent by the TDF entity, where the service flow detection event is that the TDF entity detects that the charging is required. After the data packet of the first application is sent, the service flow detection event includes an identifier of the first application, and the PCRF entity determines the first application according to the identifier of the first application.

The PCRF entity sends the identifier of the first application and the charging identifier allocated for the first application to the UE and the PCEF entity, based on the foregoing method for detecting the first application that needs to be charged by the TDF entity, including:

The PCRF entity sends a policy and charging rule message to the PCEF entity, where the policy and charging rule message includes an identifier of the first application and a charging identifier allocated to the first application, so that The PCEF entity sends the identifier of the first application and the charging identifier allocated for the first application to the UE by using a serving gateway device.

The PCRF entity sends the identifier of the first application and the charging identifier allocated for the first application to the TDF entity, including: the PCRF entity to the TDF, based on the solution that the TDF entity detects the first application that needs to be charged. Entity sends modify application probe control (Appl ication

The detection control (referred to as ADC) rule message, the modified ADC rule message includes an identifier of the first application and a charging identifier allocated for the first application.

The method flow described from the perspective of the PCEF entity includes:

The PCEF entity receives an identifier of the first application that is separately billed by the PCRF entity and a charging identifier that is allocated for the first application, which is sent by the PCRF entity;

The PCEF entity sends the identifier of the first application and the charging identifier allocated to the first application to the UE by using the serving gateway device, so that the UE adds the meter to the uplink data packet of the first application. After the fee is identified, it is sent to the PCEF entity;

The PCEF entity receives the uplink data packet that is sent by the UE and carries the charging identifier, and performs independent charging on the uplink data packet carrying the charging identifier according to the charging identifier.

In an optional implementation, the method further includes:

The PCEF entity receives the downlink data packet that is sent by the TDF entity and carries the charging identifier, and performs independent charging on the downlink data packet carrying the charging identifier according to the charging identifier.

In an optional implementation, the PCEF entity receives the identifier of the first application that is determined by the PCRF entity and needs to be separately charged, and the charging identifier that is allocated to the first application, and includes:

The PCEF entity receives the IP-CAN session establishment response message sent by the PCRF entity, where the IP-CAN session establishment response message includes an identifier of the first application and an allocated charging identifier for the first application.

Based on the foregoing, before receiving the IP-CAN session establishment response message sent by the PCRF entity, the PCEF entity further includes: the PCEF entity sending an IP-CAN session establishment request message to the PCRF entity.

In an optional implementation, the CEF entity receives the identifier of the first application that is determined by the PCRF entity and needs to be separately charged, and the charging identifier that is allocated to the first application, and includes:

Receiving, by the PCEF entity, a policy and charging rule message sent by the PCRF entity, where the policy and The charging rule message includes an identifier of the first application and a charging identifier allocated for the first application. In an optional implementation, the PCEF entity sends the identifier of the first application and the charging identifier that is allocated to the first application to the UE by using the serving gateway device, including:

The PCEF entity sends an IP-CAN bearer setup response message to the serving gateway device, where the IP-CAN bearer setup response message includes an identifier of the first application and a charging identifier assigned to the first application, so that The serving gateway device sends the identifier of the first application and the charging identifier allocated for the first application to the UE.

Before the PCEF entity sends the IP-CAN bearer setup response message to the serving gateway device, the method further includes: the PCEF entity receiving the IP-CAN bearer setup request message sent by the serving gateway device, the IP-CAN bearer setup request The message includes an identification of the UE.

The method flow described from the perspective of the TDF entity includes:

The TDF entity receives the identifier of the first application that needs to be separately charged and the charging identifier that is allocated for the first application, which is determined by the PCRF entity sent by the PCRF entity;

Determining, by the TDF entity, the downlink data packet of the first application according to the identifier of the first application, and adding the charging identifier to the downlink data packet of the first application;

The TDF entity sends the downlink data packet that adds the charging identifier to the PCEF entity, so that the PCEF entity separately charges the downlink data packet of the first application based on the charging identifier.

In an optional implementation, the TDF entity receives the identifier of the first application that is determined by the PCRF entity and needs to be separately charged, and the charging identifier that is allocated to the first application, and includes:

The TDF entity receives the TDF session establishment request message sent by the PCRF entity, where the TDF session establishment request message includes the identifier of the first application and the charging identifier allocated for the first application.

Further, after the TDF entity receives the TDF session establishment request message sent by the PCRF entity, the method further includes: the TDF entity sending a TDF session establishment response message to the PCRF entity.

In an optional implementation, the TDF entity receives the identifier of the first application that is determined by the PCRF entity and needs to be separately charged, and the charging identifier that is allocated to the first application, and further includes

The TDF entity detects a data packet of the first application that needs to be separately charged, and after detecting the data packet of the first application, sends a service flow detection event to the PCRF entity, where the service flow probe The event includes an identifier of the first application, so that the PCRF entity determines that the first application needs to be charged according to the identifier of the first application.

Based on the foregoing, the TDF entity receives the identifier of the first application that is determined by the PCRF entity and needs to be separately charged, and the charging identifier that is allocated to the first application, including:

The TDF entity receives the modified ADC rule message sent by the PCRF entity, and the modified ADC rule message includes an identifier of the first application and a charging identifier allocated for the first application.

The method flow described from the perspective of the UE includes:

Receiving, by the UE, the identifier of the first application that is sent by the serving gateway device, and the charging identifier that is allocated to the first application, where the charging identifier is used to identify that the first application needs to be separately charged; The identifier of the first application determines an uplink data packet of the first application, and adds the charging identifier to an uplink data packet of the first application;

The UE sends the uplink data packet that adds the charging identifier to the PCEF entity, so that the PCEF entity separately charges the uplink data packet of the first application based on the charging identifier.

The flow of the first charging method provided by the present invention is further described in detail from the perspective of multi-network element interaction.

FIG. 3 is a flowchart of a charging method according to an embodiment of the present invention. As shown in FIG. 3, the method includes:

11. The PCEF entity receives an IP-Connectivity Access Network (IP-CAN) bearer setup request message sent by the serving gateway device.

Specifically, the PCEF entity receives the service gateway device, for example, an IP-CAN bearer setup request message sent by the SGW, where the IP-CAN bearer setup request message includes information such as the identifier of the UE, and is used to establish a bearer.

12. The PCEF entity sends an IP-CAN session establishment request message to the PCRF entity.

13. The PCRF entity determines the first application that needs to be charged, and allocates a charging identifier to the first application that needs to be charged, to identify that the first application needs to be separately charged.

Herein, the first application here may be any application that needs to be charged. For the convenience of description, it is referred to as "first", but there is no limit to the number.

For example, the PCRF may allocate a corresponding differentiated service code point (DSCP) value to the first application, so that the DSCP bit in the IP header of the data packet is identified by the corresponding value to be used for the first application. Billing. 14. The PCRF entity sends a TDF session establishment request message to the TDF entity, where the TDF session establishment request message includes an identifier of the first application (APPLICATION ID) and a charging identifier, such as a DSCP value.

15. The TDF entity sends a TDF session setup response message to the PCRF entity.

Optionally, the method provided in this embodiment may further include: after receiving the identifier of the first application and the charging identifier allocated to the first application, the TDF entity adds the charging identifier to the downlink data packet of the first application, And sending the downlink data packet of the first application that adds the charging identifier to the PCEF entity; when receiving the downlink data packet that is sent by the TDF entity and carrying the charging identifier, the PCEF entity performs charging for the data packet.

After the PCRF entity allocates the charging identifier to the first application, the TDF entity initiates a TDF session establishing process to provide the identifier of the first application and the charging identifier allocated for the first application to the TDF entity, so that the TDF is in the downlink direction. The first application is identified by the charging identifier (for example, the DSCP value), so that the PCEF entity can recognize that the downlink data packet belongs to the first application that needs to be charged, and then in the downlink direction, after receiving the downlink data packet sent by the TDF. A separate billing for the first application is implemented, and there is no problem of repeated billing.

The PCRF entity sends an IP-CAN session establishment response message to the PCEF entity, where the IP-CAN session establishment response message includes an identifier of the first application and a charging identifier assigned to the first application, for example, a DSCP value.

The identifier of the first application is the identifier of the application to be charged (Char ged-app 1 i cat i on identifier).

After assigning the charging identifier to the first application, the PCRF entity provides the identifier of the first application and the charging identifier allocated for the first application to the TDF entity, and the identifier of the first application is also required to be An application-assigned charging identifier is provided to the PCEF entity, so that the PCEF entity charges the uplink and downlink data packets of the first application based on the two information.

17. The PCEF entity sends an IP-CAN bearer setup response message to the serving gateway device, where the IP-CAN bearer setup response message includes an identifier of the first application and a charging identifier assigned to the first application.

Optionally, the PCEF entity may add the identifier of the first application and the charging identifier allocated for the first application to a Protocol Configuration Option (PC0) in the IP-CAN bearer setup response message, and provide the Service gateway device.

In addition, this embodiment does not limit the implementation of the identifier of the first application. For example, if needed To charge the application data package of the Sina (Sina) webpage, it is possible to include the stomach. sina.com as the identifier of the first application in the PC0, but is not limited thereto.

After the service gateway device receives the IP-CAN bearer setup response message, the mobility management network element transparently transmits the identifier of the first application and the charging identifier allocated to the first application to the UE, for example, the IP may be transparently transmitted to the UE. The CAN bearers the PC0 in the response message.

After receiving the identifier of the first application and the charging identifier allocated for the first application, the UE adds the charging identifier to the uplink data packet of the first application, and adds the uplink data of the first application of the charging identifier. The package is sent to the PCEF entity.

20. When receiving the uplink data packet carrying the charging identifier sent by the UE, the PCEF entity performs separate charging on the received data packet.

After receiving the uplink data packet sent by the UE, the PCEF entity can learn, by using the charging identifier carried by the PCEF, that the uplink data packet belongs to the first application that needs to be charged, thereby implementing the uplink application in the uplink direction. Separate billing for an application. In addition, after receiving the downlink data packet sent by the TDF entity, the PCEF entity can learn that the downlink data packet belongs to the first application that needs to be charged by using the charging identifier carried by the PCEF entity, thereby implementing a separate application for the first application in the downlink direction. fee. In addition, the charging method provided in this embodiment is implemented on the PCEF entity, and the SDF-based charging in the prior art is performed on the same device. Therefore, there is no problem of charging inaccuracy caused by repeated charging.

FIG. 4 is a flowchart of another charging method according to an embodiment of the present invention. As shown in Figure 4, the method includes:

When the TDF entity detects the data packet of the first application to be charged, the TSF entity reports the service flow detection event to the PCRF entity, where the service flow detection event includes information such as the identifier of the first application.

Specifically, the TDF entity may detect the received data packet according to the detection rule of the data packet sent by the PCRF entity. Based on this, the TDF entity can detect which application packets need to be billed separately. Which applications need to be billed separately can be determined according to the requirements of the operator. The first application may be any application that requires charging. When the first application that needs to be charged is detected, the TDF entity reports the service flow detection event to the PCRF entity, so that the PCRF entity allocates a charging identifier to the first application and determines to modify the ADC rule.

After receiving the service flow detection event, the PCRF entity determines the first application according to the identifier of the first application, and allocates a charging identifier to the first application. For example, the allocated charging identifier may be a DSCP value.

The charging identifier is mainly used to identify that the data packet of the first application needs to be charged, for example, For the UE, the charging identifier needs to be added to the uplink data packet of the first application. For the PCEF entity, the first application that needs to be charged and the uplink data packet of the first application are determined based on the charging identifier. For the TDF entity, the charging identifier needs to be added to the downlink data packet of the first application. For the PCEF entity, the first application that needs to be charged and the first application are determined based on the charging identifier. Downstream packet.

43. The PCRF entity sends a modified ADC rule message to the TDF entity, where the message includes an identifier of the first application (APPLICATION ID) and a charging identifier assigned to the first application, such as a DSCP value.

After assigning the charging identifier to the first application, the PCRF entity provides the TDF entity with the identifier of the first application and the charging identifier allocated for the first application, so that the TDF entity can identify the first application and the charging allocated to the first application. Corresponding relationship between the identifiers, so that the TDF can identify the first application according to the charging identifier (for example, a DSCP value) in the downlink direction, so that the PCEF entity can identify the downlink data packet after receiving the downlink data packet sent by the TDF. It belongs to the first application that needs to perform charging, so that separate charging for the first application is implemented in the downlink direction, and there is no problem of repeated charging.

44. The PCRF entity sends a policy and charging rule message to the PCEF entity, where the message includes an identifier of the first application and a charging identifier allocated for the first application.

The identifier of the first application is the identifier of the application to be charged (Char ged-app 1 i cat i on identifier ).

The PCEF entity sends an IP-CAN bearer setup request message to the serving gateway device, where the IP-CAN bearer setup request message includes an identifier of the first application and a charging identifier assigned to the first application.

Optionally, the PCEF entity may add the identifier of the first application and the charging identifier allocated for the first application to the PC0 in the IP-CAN bearer setup request message, and provide the information to the serving gateway device. In addition, this embodiment does not limit the implementation of the identifier of the first application. For example, if it is necessary to charge the application data packet of the Sina (Sina) webpage, it is possible to include the stomach. sina.com as the identifier of the first application in the PC0, but is not limited thereto.

After the service gateway device receives the IP-CAN bearer setup request message, the mobility management network element transparently transmits the identifier of the first application and the charging identifier allocated for the first application to the UE, for example,

The UE transparently transmits PC0 in the IP-CAN bearer setup request message.

48. When receiving the uplink data packet carrying the charging identifier sent by the UE, the PCEF entity performs separate charging on the received data packet.

After receiving the uplink data packet sent by the UE, the PCEF entity can learn, by using the charging identifier carried by the PCEF, that the uplink data packet belongs to the first application that needs to be charged, thereby implementing the uplink application in the uplink direction. Separate billing for an application. In addition, after receiving the downlink data packet sent by the TDF entity, the PCEF entity can learn that the downlink data packet belongs to the first application that needs to be charged by using the charging identifier carried by the PCEF entity, thereby implementing a separate application for the first application in the downlink direction. fee. In addition, the charging method provided in this embodiment is implemented on the PCEF entity, and is performed on the same device as the SDF-based charging in the prior art. Therefore, there is no problem of inaccurate charging caused by repeated charging.

The second charging method provided by the present invention is mainly for performing SDF granularity-based charging in a PCEF entity. When a data packet arrives at a TDF entity, the TDF entity may perform flow control on some applications, causing data packets of some applications. The problem that the accounting is inaccurate is discarded, or the same identifier is used for the data packets with the same uplink and downlink IP address for charging. However, the actual charging requirement may be only the partial data packet of the IP address causing the excessive charging. The question was raised.

The main idea of the second charging method is: After the PCEF entity performs SDF granularity-based charging on the data packet, when the data packet arrives at the TDF entity, the TDF entity determines the influence according to the PCC rule identifier and/or the SDF template provided by the PCRF entity. The PCEF entity sends the traffic of the SDF to which the first application belongs and the traffic of the data packet of the first application to the PCEF by the PCRF entity, and then sends the traffic of the data packet of the first application to the PCEF by the PCRF entity. An entity, so that the PCEF entity adjusts the SDF granularity based charging result according to the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application. Based on the main idea of the second charging method, the flow of the second charging method is described in detail from the perspective of the PCRF entity, the PCEF entity, and the TDF entity.

The method flow described from the perspective of the PCRF entity includes:

a PCC rule identifier and/or an SDF template sent by the PCRF entity to the TDF entity, for the TDF entity to determine the identifier of the SDF to which the first application that affects the PCDF entity based on the SDF granularity charging result and the traffic of the data packet of the first application;

The PCRF entity receives, according to the PCC rule identifier and/or the SDF template, the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application sent by the TDF entity;

The PCRF entity sends the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application to the PCEF entity, so that the PCEF entity is based on the identifier of the SDF to which the first application belongs and the The traffic of the data packet of an application adjusts the SDF granularity-based charging result of the uplink data packet from the UE; wherein the data packet of the first application belongs to the uplink data packet from the UE.

In an optional implementation, the PCC rule identifier and/or the SDF template sent by the PCRF entity to the TDF entity includes:

The PCRF entity sends a TDF Session Establishment Request message to the TDF entity, the TDF Session Setup Request message including the PCC Rule Identity and/or SDF Template.

Based on the foregoing, after the PCRF entity sends the TDF session establishment request message to the TDF entity, the method further includes: the PCRF entity receiving the TDF session establishment response message sent by the TDF entity.

In an optional implementation, the PCRF entity sends the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application to the PCEF entity, including:

The PCRF entity sends an IP-CAN session modification request message to the PCEF entity, where the IP-CAN session modification request message includes the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application.

The method flow described from the perspective of the PCEF entity includes:

The PCEF entity receives the identifier of the SDF to which the first application to which the PCEF entity sends the SDF granularity-based charging result, and the traffic of the data packet of the first application, where the PCEF entity receives the identifier of the SDF to which the first application belongs. And the traffic of the data packet of the first application is determined by the TDF entity according to the PCC rule identifier and/or the SDF template sent by the PCRF entity, and sent to the PCRF entity; The PCEF entity adjusts the SDF granularity-based charging result according to the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application; where the data packet of the first application belongs to the uplink from the UE data pack.

In an optional implementation, before receiving, by the PCF entity, the identifier of the SDF that belongs to the first application that affects the SDF granularity-based charging result of the PCEF entity and the traffic of the data packet of the first application, the PCEF entity further includes:

The PCEF entity performs SDF granularity based charging on all packets arriving.

In an optional implementation manner, the PCEF entity receives, by the PCRF entity, the identifier of the SDF that belongs to the first application that affects the charging result of the PCEF entity based on the SDF granularity, and the traffic of the data packet of the first application, including:

The PCEF entity receives the IP-CAN session modification request message sent by the PCRF entity, where the IP-CAN session modification request message includes the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application.

The method flow described from the perspective of the TDF entity includes:

The TDF entity receives the PCC rule identifier and/or the SDF template sent by the PCRF entity;

The TDF entity determines, according to the PCC rule identifier and/or the SDF template, the identifier of the SDF to which the first application that affects the charging result of the PCEF entity based on the SDF granularity and the traffic of the data packet of the first application;

Transmitting, by the TDF entity, the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application to the PCEF entity by using the PCRF entity, so that the PCEF entity is based on the The identifier of the SDF and the traffic of the data packet of the first application are adjusted according to the SDF granularity charging result of the uplink data packet from the UE, where the data packet of the first application belongs to the uplink data packet from the UE .

In an optional implementation, the TDF entity receives the PCC rule identifier and/or the SDF template sent by the PCRF entity, including:

The TDF entity receives a TDF session establishment request message sent by the PCRF entity, where the TDF session establishment request message includes the PCC rule identifier and/or the SDF template.

Based on the foregoing, optionally, after receiving the TDF session establishment request message sent by the PCRF entity, the TDF entity further includes: the TDF entity sending a TDF session establishment response message to the PCRF entity.

In an optional implementation, the TDF entity identifies and/or the SDF template according to the PCC rule. Determining the identifier of the SDF to which the first application that affects the charging result of the SDF granularity of the PCEF entity belongs and the traffic of the data packet of the first application, including:

Determining, by the TDF entity, the application to which the data packet discarded by performing the application-based flow control belongs as the first application according to the PCC rule indicated by the PCC rule identifier, determining the traffic of the discarded data packet as the The traffic of the data packet of the first application, and determining the SDF to which the first application belongs; or

The TDF entity determines, according to the SDF template, that it is not required to charge all data packets having the same IP address information in the uplink data packet from the UE, and determines actual needs from all data packets having the same IP address information. The application to which the billing data packet belongs is used as the first application, and the traffic of the data packet that needs to be charged is determined as the traffic of the data packet of the first application, and the SDF to which the first application belongs is determined; or

The flow of the second charging method provided by the present invention is further described in detail from the perspective of multi-network element interaction.

FIG. 5 is a flowchart of still another charging method according to an embodiment of the present invention. As shown in Figure 5, the method includes:

51. The PCRF entity sends a TDF session establishment request message to the TDF entity, where the TDF session establishment request message includes a PCC rule id and/or an SDF template.

The PCC rule identifier is used to indicate a PCC rule, and the PCC rule includes a lot of information, which is used to perform service flow control and charging rules. In this embodiment, the charging rule indicates which application or applications are billed. The SDF template is a set of quintuple information used to indicate the bearer of the application flow. In general, it indicates which bearer the application flow should go in.

52. The TDF entity sends a TDF session setup response message to the PCRF entity.

When the data packet arrives at the TDF entity, the TDF entity determines, according to the PCC rule identifier and/or the SDF template, the traffic of the SDF to which the first application belongs and the data packet of the first application, so that the PCEF entity belongs according to the first application. SDF and traffic flow adjustment for the first application based on SDF granularity Billing result.

In this embodiment, the TDF entity can identify the SDF to which the first application that needs to be charged belongs according to the PCC rule and/or the SDF template indicated by the PCC rule. The first application is an application that affects the SDF granularity-based charging result of the PCEF entity, and may be, for example, an application to which the TDF entity discards the data packet discarded by the flow control, or an application determined by the TDF entity that needs to be separately charged. It can be an application determined by the TDF entity that does not require separate billing.

Specifically, if the TDF entity determines that the application-based flow control is to be performed according to the PCC rule indicated by the PCC rule, for example, discarding part of the data packet of the application, the TDF entity may determine the discarded data packet according to the information such as the IP address of the application. The SDF to which it belongs; At this time, the application to which the dropped packet belongs is the first application.

If the TDF entity detects from the SDF template that it is not required to charge all data packets having the same IP address information, the data packets of the application that actually need to be charged are determined from all the data packets having the same IP address information, and The SDF to which the application that needs to be charged belongs is determined. At this time, the application that actually needs to be charged is the first application. Alternatively, the TDF entity may also determine, from all the data packets having the same IP address information, the data packets that are not in the application that need to be charged, and determine the SDF to which the data packets that do not need to be charged belong; The application to which the data packet that does not need to be charged belongs is the first application.

54. The TDF entity sends the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application to the PCRF entity.

55. The PCRF entity sends an IP-CAN session modification request message to the PCEF entity, where the IP-CAN session modification request message includes the identifier of the SDF to which the first application belongs and the flow of the data packet of the first application.

The PCEF entity adjusts the charging result of the SDF to which the first application belongs according to the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application, so as to achieve accurate charging.

In this embodiment, after the PCEF entity performs the SDF granularity-based charging, the TDF entity performs detection on the data flow, and the traffic of the SDF that belongs to the data packet that is discarded by performing the flow control and the traffic of the discarded data packet are passed through the PCRF. The entity notifies the PCEF entity, so that the PCEF entity adjusts the charging result based on the SDF, or the data that has the same IP address information, the SDF and the traffic to which the application that actually needs to be charged belongs, or the application that does not need to be charged The SDF and traffic are sent to the PCEF entity through the PCRF entity, so that the PCEF entity adjusts the SDF granularity based charging result. In order to achieve accurate billing, the problem of inaccurate billing is solved.

The third charging method provided by the present invention is mainly for performing SDF granularity-based charging in a PCEF entity. When a data packet arrives at a TDF entity, the TDF entity may perform flow control on some applications, causing data packets of some applications. The problem that the accounting is inaccurate is discarded, or the same identifier is used for the data packets with the same uplink and downlink IP address for charging. However, the actual charging requirement may be only the partial data packet of the IP address causing the excessive charging. The question was raised.

The main idea of the third charging method is: First, the PCRF entity, the PCEF entity, and the TDF entity determine a charging identifier assigned to the reflow data, and the charging identifier is used to identify the reflow data. After the PCEF entity performs SDF granularity-based charging on the data packet, when the data packet arrives at the TDF entity, the TDF entity determines the reflow data, and re-sends the reflow data to the PCEF entity, so that the PCEF entity is based on the The fee identifier determines the reflow data, and adjusts the SDF granularity based charging result according to the reflow data to achieve accurate charging. The reflow data refers to data that affects the charging result of the PCEF entity based on the SDF granularity.

Based on the main idea of the third charging method, the following describes the flow of the second charging method from the perspective of the TDF entity, the PCEF entity, and the PCRF entity.

The method flow described from the perspective of the TDF entity includes:

After receiving the uplink data packet sent by the PCEF entity, the TDF entity determines the reflow data, and adds a charging identifier to the reflow data, where the reflow data refers to affecting the uplink data by the PCEF entity in the uplink data packet. a packet based on the SDF granularity of the charging result;

The TDF entity sends the reflow data carrying the charging identifier to the PCEF entity to enable the

The PCEF entity adjusts the charging result of the uplink data packet based on the SDF granularity according to the reflow data carrying the charging identifier.

In an optional implementation, after the TDF entity receives the uplink data packet, determines the reflow data, and adds the charging identifier to the reflow data, the method further includes:

The TDF entity receives the charging identifier allocated by the PCRF entity sent by the PCRF entity for the reflow data.

Further, optionally, the TDF entity receives the charging identifier that is sent by the PCRF entity to the loopback data, and includes:

The TDF entity receives a TDF session establishment request message sent by the PCRF entity, where the TDF session establishment request message includes the charging identifier. After the TDF entity receives the TDF session establishment request message sent by the PCRF entity, the method further includes:

The TDF entity sends a TDF Session Setup Response message to the PCRF entity.

The method flow described from the perspective of the PCEF entity includes:

After performing the SDF granularity-based charging on the uplink data packet, the PCEF entity receives the reflow data carried by the TDF entity and carries the charging identifier, where the reflow data is in the uplink data packet determined by the TDF entity. a data packet of the SDF granularity based charging result of the uplink data packet by the PCEF entity;

The PCEF entity determines, according to the charging identifier, that the received data is reflow data, determines an SDF to which the reflow data belongs, and adjusts the charging result of the determined SDF.

In an optional implementation, before receiving the reflow data carried by the TDF entity and carrying the charging identifier, the PCEF entity further includes:

The PCEF entity receives the charging identifier allocated by the PCRF entity sent by the PCRF entity for the reflow data.

Further, optionally, the PCEF entity receives the charging identifier that is sent by the PCRF entity and is sent by the PCRF entity to the backflow data, and includes:

The PCEF entity receives an IP-CAN session setup response message sent by the PCRF entity, and the IP-CAN session setup response message includes the charging identifier.

Based on the foregoing, before the PCEF entity receives the IP-CAN session establishment response message sent by the PCRF entity, the method further includes:

The PCEF entity sends an IP-CAN Session Setup Request message to the PCRF entity.

The method flow described from the perspective of the PCRF entity includes:

The PCRF entity determines a charging identifier that needs to be allocated to the reflow packet, and the reflow data refers to a packet in the uplink packet that affects the SDF granularity-based charging result of the PCEF entity to the uplink packet;

Sending, by the PCRF entity, the charging identifier to the TDF entity and the PCEF entity, where the TDF entity adds the reflow data to the reflow data after determining the reflow data from the uplink data packet from the PCEF entity After the charging identifier is sent to the PCEF entity, the PCEF entity determines the reflow data according to the charging identifier, and adjusts the SDF granularity-based charging result of the uplink data packet based on the reflow data. . In an optional implementation manner, the PCRF entity sends the charging identifier to the TDF entity, including: the PCRF entity sends a TDF session establishment request message to the TDF entity, where the TDF session establishment request message includes the charging identifier.

After the PCRF entity sends the TDF session establishment request message to the TDF entity, the method further includes: the PCRF entity receiving the TDF session establishment response message sent by the TDF entity.

In an optional implementation, the PCRF entity sends the charging identifier to the PCEF entity, including:

The PCRF entity sends an IP-CAN session setup response message to the PCEF entity, and the IP-CAN session setup response message includes the charging identifier.

The flow of the third charging method provided by the present invention is further described in detail from the perspective of multi-network element interaction.

FIG. 6 is a flowchart of still another charging method according to an embodiment of the present invention. As shown in Figure 6, the method includes:

61. The PCEF entity receives an IP-CAN bearer setup request message sent by the serving gateway device.

62. The PCEF entity sends an IP-CAN session establishment request message to the PCRF entity.

63. The PCRF entity determines a charging identifier that needs to be assigned to the reflow data.

It is noted that the reflow data in this embodiment refers to the data that affects the charging accuracy, and is used by the PCEF entity to adjust the SDF granularity-based charging result, which is returned by the TDF entity to the PCEF entity, for example, The TDF entity performs charging based on the application data stream, or data that is discarded by the TDF entity to perform flow control.

The PCRF entity allocates a charging identifier for the reflow data, and the purpose is to enable the TDF entity to identify the reflow data, and the second is to enable the PCEF entity to identify the reflow data from the received downlink data based on the charging identifier. The charging identifier assigned by the PCRF entity to the reflow data may be a DSCP value so that the DSCP bit in the IP header of the packet identifies the reflow data with a corresponding value.

64. The PCRF entity sends a TDF session establishment request message to the TDF entity, where the TDF session establishment request message includes a charging identifier assigned to the reflow data, such as a DSCP value.

65. The TDF entity sends a TDF session setup response message to the PCRF entity.

66. The PCRF entity sends an IP-CAN session establishment response message to the PCEF entity, the IP-CAN The session setup response message includes a charging identifier assigned to the reflow data, such as a DSCP value. At this point, the PCRF entity cooperates with the TDF entity and the PCEF entity to allocate a charging identifier for the reflow data, and provides the TDF entity and the PCEF entity respectively, so that the subsequent TDF entity and the PCEF entity are based on the charging identifier of the reflow data. Perform more accurate billing operations.

67. After receiving the uplink data packet, the TDF entity determines the reflow data. For example, the TDF entity may perform a flow control policy, determine the uplink data packet to be discarded as the reflow data, or the uplink data of the application that the TDF entity will charge based on the application data flow. The package acts as reflux data.

68. The TDF entity forwards the determined reflow data to the PCEF entity, and includes a charging identifier, such as a DSCP value, allocated to the reflow data in the reflow data, so that the PCEF entity can recognize the received data when receiving the reflow data. The reflow data is the uplink data packet discarded by the TDF entity or the uplink data packet that the TDF entity performs charging based on the application data flow.

Specifically, the TDF entity may reverse information such as the IP address of the outer IP header of the reflow data, and then forward the information to the PCEF entity.

69. After receiving the reflow data, the PCEF entity determines, according to the charging identifier in the reflow data, that the reflow data is received, determining the SDF to which the reflow data belongs according to the IP information of the inner layer of the reflow packet, such as an IP address. And adjust the billing result for the SDF to facilitate accurate billing.

Specifically, the PPCEF entity can count the traffic of the reflow data, and deduct the fee generated by the traffic of the reflow data from the charging result of the SDF to which the reflow data belongs, so as to achieve accurate charging.

In this embodiment, the charging identifier corresponding to the reflow data is pre-negotiated, and the charging identifier is used to indicate that the PCEF entity adjusts the SDF granularity-based charging result, after the PCEF entity completes the SDF granularity charging, The data packet arrives at the TDF entity. After the TDF entity performs application-based flow control or application data flow-based charging, the data packet of the operation is determined as the reflow data and carries the charging identifier therein, and then forwarded to the PCEF entity, so as to facilitate The PCEF entity determines the reflow data based on the charging identifier in the reflow data, and then adjusts the charging result of the SDF according to the SDF to which the reflow data belongs, so as to achieve accurate charging.

Here, in the embodiment shown in Fig. 6, the above data packet is described as an example, and the downlink data packet can be processed in a manner similar to the embodiment shown in Fig. 6.

FIG. 7 is a schematic structural diagram of a PCRF entity according to an embodiment of the present invention. As shown in FIG. 7, the PCRF entity includes: a determining module 71, an allocating module 72, and a sending module 73.

The determining module 71 is configured to determine a first application that needs to be charged. The allocating module 72 is connected to the determining module 71, and configured to allocate a charging identifier to the first application determined by the determining module 71, where the charging identifier is used to identify that the first application needs to be separately charged.

The sending module 73 is connected to the determining module 71 and the assigning module 72, and is configured to send the identifier of the first application determined by the determining module 71 and the charging identifier allocated by the allocating module 72 to the first application to the UE and the PCEF respectively. An entity and a TDF entity, so that the UE and the TDF entity add the charging identifier to a data packet of the first application, and then send the charging identifier to the PCEF entity, so that the PCEF entity is based on the first application. The identifier and the charging identifier allocated for the first application separately charge the data packet carrying the charging identifier from the UE and the TDF entity separately.

In an optional implementation, the sending module 73 is configured to send the identifier of the first application and the charging identifier allocated to the first application to the UE and the PCEF entity, respectively, including:

The sending module 73 is specifically configured to send an IP-CAN session establishment response message to the PCEF entity, where the IP-CAN session establishment response message includes an identifier of the first application and an allocated charging identifier for the first application. And sending, by the serving gateway device, the identifier of the first application and the charging identifier allocated for the first application to the UE by using a serving gateway device.

In an optional implementation, the sending module 73 adds the identifier of the first application and the charging identifier TDF entity allocated for the first application, including:

The sending module 73 is specifically configured to send a TDF session establishment request message to the TDF entity, where the TDF session establishment request message includes an identifier of the first application and a subscription identifier allocated for the first application.

In an optional implementation, the determining module 71 is specifically configured to receive a service flow detection event sent by the TDF entity, where the service flow detection event is that the TDF entity detects data of the first application that needs to be charged. After the packet is sent, the service flow detection event includes an identifier of the first application; and the first application is determined according to the identifier of the first application.

On the basis of the service flow detection event, the sending module 73 is configured to send the identifier of the first application and the charging identifier allocated to the first application to the UE and the PCEF entity, respectively. Sending a policy and charging rule message to the PCEF entity, where the policy and charging rule message includes an identifier of the first application and a charging identifier allocated to the first application, so that the PCEF entity passes The serving gateway device sends the identifier of the first application and the charging identifier allocated for the first application to the UE. On the basis of the service flow detection event, the sending module 73 is configured to: use the identifier of the first application and the charging identifier TDF entity allocated to the first application, including:

The sending module 73 is specifically configured to send a modified ADC rule message to the TDF entity, where the modified ADC rule message includes an identifier of the first application and a charging identifier allocated for the first application.

Further optionally, the PCEF entity may further include: a receiving module. The receiving module can be configured to receive the IP-CAN session establishment request message by the PCEF entity before the sending module 73 sends an IP-CAN session establishment response message to the PCEF entity. Alternatively, the receiving module is further configured to: after the sending module 73 sends a TDF session establishment request message to the TDF entity, receive a TDF session establishment response message sent by the TDF entity.

The functional modules of the PCRF entity provided in this embodiment may be used to perform the process of the first charging method in the foregoing method embodiments. The specific working principle is not described here. For details, refer to the description of the method embodiments.

The PCRF entity provided in this embodiment determines a first application that needs to be charged, and allocates a charging identifier to the first application, where the charging identifier needs to separately charge the first application, and then the first application is And the charging identifier assigned to the first application is sent to the TDF entity, the PCEF entity, and the UE, respectively, so that the UE and the TDF entity add the charging identifier to the data packet of the first application sent to the PCEF entity, and the PCEF entity The received data packet carrying the charging identifier can be separately charged to implement separate charging for the first application in the uplink direction. In addition, the PCRF entity provided in this embodiment does not have the problem of repeated charging by assigning a charging identifier to the first application because the data packet of the first application can be identified.

FIG. 8 is a schematic structural diagram of another PCRF entity according to an embodiment of the present invention. As shown in FIG. 8, the PCRF entity includes: a processor 81, a transmitter 82, and a memory 83.

Memory 83 can include read only memory and random access memory and provides instructions and data to processor 81. A portion of the memory 83 may also include non-volatile random access memory (NVRAM)

Memory 83 stores the following elements, executable modules or data structures, or a subset thereof, or their extended set:

Operation instructions: Includes various operation instructions for implementing various operations.

Operating System: Includes a variety of system programs for implementing basic services and handling hardware-based tasks.

In the embodiment of the present invention, the processor 81 calls the operation instruction stored in the memory 83 (the The operation instructions can be stored in the operating system), and the following operations are performed:

Determining a first application that needs to be charged, and assigning a charging identifier to the first application, where the charging identifier is used to identify that the first application needs to be separately charged.

The transmitter 82 is configured to send the identifier of the first application determined by the processor 81 and the charging identifier allocated by the processor 81 to the first application to the UE, the PCEF entity, and the TDF entity, respectively, to enable the UE And the TDF entity adds the charging identifier to the data packet of the first application, and sends the charging identifier to the PCEF entity, so that the PCEF entity allocates the first application according to the identifier of the first application. The charging identifier separately charges the data packet carrying the charging identifier from the UE and the TDF entity.

Further, as shown in FIG. 8, the PCRF entity may further include: a receiver 84.

The processor 81 controls the operation of the PCRF entity, and the processor 81 may also be referred to as a Central Processing Unit (CPU). Memory 83 can include read only memory and random access memory and provides instructions and data to processor 81. A portion of the memory 83 may also include non-volatile random access memory (NVRAM). In a specific application, the components of the PCRF entity are coupled together by a bus system 85. The bus system 85 may include a power bus, a control bus, and a status signal bus in addition to the data bus. However, for the sake of clarity, various buses are labeled as bus system 85 in the figure.

The method disclosed in the foregoing embodiments of the present invention may be applied to the processor 81 or implemented by the processor 81. Processor 81 may be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps of the above method may be completed by an integrated logic circuit of hardware in the processor 81 or an instruction in the form of software. The processor 81 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware. Component. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software modules can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 83, and the processor 81 reads the information in the memory 83 and combines the hardware to perform the steps of the above method.

In an optional implementation, the transmitter 82 is configured to identify the identifier of the first application as the first The charging identifiers allocated by the application are respectively sent to the UE and the PCEF entity, including:

The transmitter 82 is specifically configured to send an IP-CAN session establishment response message to the PCEF entity, where the IP-CAN session establishment response message includes an identifier of the first application and an allocated charging identifier for the first application. And sending, by the serving gateway device, the identifier of the first application and the charging identifier allocated for the first application to the UE by using a serving gateway device.

In an optional implementation, the transmitter 82 identifies the identifier of the first application and the charging identifier TDF entity allocated for the first application, including:

The transmitter 82 is specifically configured to send a TDF session establishment request message to the TDF entity, where

The TDF session establishment request message includes an identifier of the first application and a subscription identifier assigned to the first application.

In an optional implementation, the processor 81 is specifically configured to receive, by the receiver 84, a service flow detection event sent by the TDF entity, where the service flow detection event is that the TDF entity detects that the charging is required. And transmitting, after the data packet of the application, the service flow detection event includes an identifier of the first application; and determining the first application according to the identifier of the first application received by the receiver 84.

On the basis of the service flow detection event, the transmitter 82 is configured to send the identifier of the first application and the charging identifier allocated to the first application to the UE and the PCEF entity, respectively, including:

The transmitter 82 is specifically configured to send a policy and charging rule message to the PCEF entity, where the policy and charging rule message includes an identifier of the first application and a charging identifier allocated to the first application, so that The PCEF entity sends the identifier of the first application and the charging identifier allocated for the first application to the UE by using a serving gateway device.

Based on the foregoing service flow detection event, the transmitter 82 is configured to: use the identifier of the first application and the charging identifier TDF entity allocated for the first application, including:

The transmitter 82 is specifically configured to send a modified ADC rule message to the TDF entity, where the modified ADC rule message includes an identifier of the first application and a charging identifier allocated for the first application.

Further optionally, the receiver 84 is configured to receive the IP-CAN session establishment request message by the PCEF entity before the transmitter 82 sends the IP-CAN session establishment response message to the PCEF entity. Alternatively, the receiver 84 is further configured to: after the transmitter 82 sends a TDF session establishment request message to the TDF entity, receive a TDF session establishment response message sent by the TDF entity.

The PCRF entity provided in this embodiment may be used to perform the first charging party in the foregoing method embodiment. The specific working principle of the method of the method will not be described again. For details, refer to the description of the method embodiment.

FIG. 9 is a schematic structural diagram of a PCEF entity according to an embodiment of the present invention. As shown in FIG. 9, the PCEF entity includes: a receiving module 91, a sending module 92, and a billing module 93.

The receiving module 91 is configured to receive, by the PCRF entity, an identifier of the first application that needs to be separately charged, and a charging identifier that is allocated to the first application.

The sending module 92 is connected to the receiving module 91, and configured to send, by the serving gateway device, the identifier of the first application received by the receiving module 91 and the charging identifier allocated to the first application to the UE, so that the UE And adding the charging identifier to the uplink data packet of the first application, and sending the identifier to the PCEF entity.

The receiving module 91 is further configured to receive an uplink data packet that is sent by the UE and that carries the charging identifier.

The charging module 93 is connected to the receiving module 91, and is configured to separately charge the uplink data packet that is received by the receiving module 91 and that carries the charging identifier according to the charging identifier received by the receiving module 91.

In an optional implementation, the receiving module 91 is further configured to receive a downlink data packet that is sent by the TDF entity and that carries the charging identifier.

Correspondingly, the charging module 93 is further configured to separately charge the downlink data packet that is received by the receiving module 91 and that carries the charging identifier according to the charging identifier received by the receiving module 91.

In an optional implementation, the receiving module 91 is configured to receive, by the PCRF entity, an identifier of the first application that is determined by the PCRF entity and that needs to be separately charged, and an accounting identifier that is allocated to the first application, where:

The receiving module 91 is specifically configured to receive an IP-CAN session establishment response sent by the PCRF entity. The IP-CAN session establishment response message includes an identifier of the first application and an allocated charging identifier for the first application; or

The receiving module 91 is specifically configured to receive the policy and charging rule message sent by the PCRF entity, where the policy and charging rule message includes an identifier of the first application and a charging identifier allocated for the first application.

Optionally, the sending module 92 is further configured to send an IP-CAN session establishment request message to the PCRF entity before the receiving module 91 receives the IP-CAN session setup response message sent by the PCRF entity.

In an optional implementation, the sending module 92 is configured to send the identifier of the first application and the charging identifier that is allocated to the first application to the UE by using the serving gateway device, including:

The sending module 92 is specifically configured to send an IP-CAN bearer setup response message to the serving gateway device, where the IP-CAN bearer setup response message includes an identifier of the first application and a charging identifier allocated to the first application. So that the serving gateway device sends the identifier of the first application and the charging identifier allocated for the first application to the UE.

Optionally, the receiving module 91 is further configured to send, at the sending module 92, the serving gateway device.

Before the IP-CAN bearer setup response message, the IP-CAN bearer setup request message sent by the serving gateway device is received.

The function modules of the PCEF entity provided in this embodiment may be used to perform the process of the first charging method in the foregoing method embodiments. The specific working principle is not described here. For details, refer to the description of the method embodiments.

The PCEF entity provided in this embodiment receives the identifier of the first application that is determined by the PCRF entity and needs to be separately charged, and the charging identifier that is allocated to the first application, according to the identifier of the first application and the accounting allocated for the first application. Identifying, separately charging, for the data packet of the first application that carries the charging identifier from the UE or the TDF entity, and because the data packet of the first application can be identified by using the charging identifier, there is no repetition Billing issue.

FIG. 10 is a schematic structural diagram of another PCEF entity according to an embodiment of the present invention. As shown in FIG. 10, the PCEF entity includes: a receiver 1001, a transmitter 1002, a processor 1003, and a memory 1004.

The receiver 1001 is configured to receive, by the PCRF entity, an identifier of the first application that needs to be separately charged, and a charging identifier that is allocated to the first application.

a transmitter 1002, configured to use the identifier of the first application received by the receiver 1001 as The charging identifier of the first application is sent to the UE by the serving gateway device, so that the UE sends the charging identifier to the PCEF entity after adding the charging identifier to the uplink data packet of the first application.

The receiver 1001 is further configured to receive an uplink data packet that is sent by the UE and that carries the charging identifier.

Memory 1004 can include read only memory and random access memory and provides instructions and data to processor 1003. A portion of memory 1004 may also include non-volatile random access memory (NVRAM) o

Memory 1004 stores the following elements, executable modules or data structures, or subsets thereof, or their extended sets:

In the embodiment of the present invention, the processor 1003 performs the following operations by calling an operation instruction stored in the memory 1004 (the operation instruction can be stored in the operating system):

The uplink data packet that is received by the receiver 1001 and carries the charging identifier is separately charged according to the charging identifier received by the receiver 1001.

The processor 1003 controls the operation of the PCEF entity, which may also be referred to as a CPU. The memory 1004 can include read only memory and random access memory and provides instructions and data to the processor 1003. A portion of the memory 1004 may also include non-volatile random access memory (NVRAM). In a specific application, the components of the PCEF entity are coupled together by a bus system 1005. The bus system 1005 may include a power bus, a control bus, a status signal bus, and the like in addition to the data bus. However, for clarity of description, various buses are labeled as a bus system in the figure. The method disclosed in the above embodiments of the present invention may be applied to the processor 1003 or implemented by the processor 1003. The processor 1003 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 1003 or an instruction in a form of software. The processor 1003 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware. Component. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. Combined with this The steps of the method disclosed in the embodiments of the present invention may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software modules can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 1004. The processor 1003 reads the information in the memory 1004 and completes the steps of the above method in combination with the hardware.

In an optional implementation, the receiver 1001 is further configured to receive a downlink data packet that is sent by the TDF entity and that carries the charging identifier.

Correspondingly, the processor 1003 is further configured to separately charge the downlink data packet that is received by the receiver 1001 and that carries the charging identifier according to the charging identifier received by the receiver 1001.

In an optional implementation, the receiver 1001 is configured to receive, by the PCRF entity, an identifier of the first application that is determined by the PCRF entity and needs to be separately charged, and an accounting identifier that is allocated to the first application, where:

The receiver 1001 is specifically configured to receive an IP-CAN session establishment response message sent by the PCRF entity, where the IP-CAN session establishment response message includes an identifier of the first application and an allocated charging for the first application. Identification; or

The receiver 1001 is specifically configured to receive a policy and charging rule message sent by the PCRF entity, where the policy and charging rule message includes an identifier of the first application and a charging identifier allocated for the first application.

Optionally, the transmitter 1002 is further configured to send an IP-CAN session establishment request message to the PCRF entity before the receiver 1001 receives the IP-CAN session establishment response message sent by the PCRF entity.

In an optional implementation, the transmitter 1002 is configured to send the identifier of the first application and the charging identifier that is allocated to the first application to the UE by using the serving gateway device, including:

The transmitter 1002 is specifically configured to send an IP-CAN bearer setup response message to the serving gateway device, where the IP-CAN bearer setup response message includes an identifier of the first application and a charging identifier assigned to the first application. So that the serving gateway device sends the identifier of the first application and the charging identifier allocated for the first application to the UE.

Optionally, the receiver 1001 is further configured to receive an IP-CAN bearer setup request message sent by the serving gateway device before the transmitter 1002 sends an IP-CAN bearer setup response message to the serving gateway device. The PCEF entity provided in this embodiment may be used to perform the process of the first charging method in the foregoing method embodiment. The specific working principle is not described here. For details, refer to the description of the method embodiment.

FIG. 1 is a schematic structural diagram of a TDF entity according to an embodiment of the present invention. As shown in FIG. 11, the TDF entity includes: a receiving module 1101, a determining adding module 1102, and a sending module 1103.

The receiving module 1101 is configured to receive, by the PCRF entity, an identifier of the first application that is determined by the PCRF entity and that needs to be separately charged, and a charging identifier that is allocated to the first application.

The determining module 1102 is configured to be connected to the receiving module 1101, configured to determine, according to the identifier of the first application received by the receiving module 1101, the downlink data packet of the first application, and add and receive the downlink data packet of the first application. The charging identifier received by the module 1101.

The sending module 1103 is connected to the determining adding module 1102, and configured to send the downlink data packet that adds the charging identifier to the PCEF entity, so that the PCEF entity downlinks the first application based on the charging identifier. Packets are billed separately.

In an optional implementation, the receiving module 1101 is configured to receive, by the PCRF entity, an identifier of the first application that is determined by the PCRF entity and that needs to be separately charged, and an accounting identifier that is allocated to the first application, where:

The receiving module 1101 is specifically configured to receive a TDF session establishment request message sent by the PCRF entity, where the TDF session establishment request message includes an identifier of the first application and a charging identifier allocated for the first application.

Optionally, the sending module 1103 is further configured to send a TDF session establishment response message to the PCRF entity after the receiving module 1101 receives the TDF session establishment request message sent by the PCRF entity.

In an optional implementation manner, the PCEF entity further includes: a detecting module, configured to detect a data packet of the first application that needs to be separately charged.

The sending module 1103 is further configured to: after the detecting module detects the data packet of the first application, send a service flow detecting event to the PCRF entity, where the service flow detecting event includes the first application The identifier, so that the PCRF entity is determined according to the identifier of the first application. It is necessary to separately charge the first application.

Based on the foregoing detection module, in an optional implementation, the receiving module 1101 is configured to receive, by the PCRF entity, an identifier of the first application that is determined by the PCRF entity and needs to be separately charged, and a charging that is allocated to the first application. Identification, including:

The receiving module 1101 is specifically configured to receive a modified ADC rule message sent by the PCRF entity, where the modified ADC rule message includes an identifier of the first application and a charging identifier allocated for the first application.

The function modules of the TDF entity provided in this embodiment may be used to perform the process of the first charging method in the foregoing method embodiment. The specific working principle is not described here. For details, refer to the description of the method embodiment.

The TDF entity provided in this embodiment receives the identifier of the first application that is determined by the PCRF entity and needs to be separately charged, and the charging identifier that is allocated for the first application, according to the identifier of the first application and the accounting allocated for the first application. The identifier is sent to the PCEF entity in the downlink data packet of the first application, and is sent to the PCEF entity, so that the PCEF entity can be based on the identifier of the first application sent by the PCRF entity and the charging identifier allocated for the first application. The downlink data packet carrying the charging identifier of the TDF entity is separately charged, and the individual charging for the first application is implemented, and the problem of repeated charging does not occur.

FIG. 12 is a schematic structural diagram of another TDF entity according to an embodiment of the present invention. As shown in FIG. 12, the TDF entity includes: a receiver 1201, a processor 1202, a transmitter 1203, and a memory 1204.

The receiver 1201 is configured to receive, by the PCRF entity, an identifier of the first application that needs to be separately charged, and a charging identifier that is allocated to the first application.

Memory 1204 can include read only memory and random access memory and provides instructions and data to processor 1202. A portion of memory 1204 may also include non-volatile random access memory (NVRAM)

Memory 1204 stores the following elements, executable modules or data structures, or subsets thereof, or their extended sets:

In the embodiment of the present invention, the processor 1202 calls the operation instruction stored in the memory 1204. (The operation instruction can be stored in the operating system), do the following:

Determining a downlink data packet of the first application according to the identifier of the first application received by the receiver 1201, and adding the charging identifier received by the receiver to a downlink data packet of the first application.

The transmitter 1203 is configured to send the downlink data packet that adds the charging identifier to the PCEF entity, so that the PCEF entity separately charges the downlink data packet of the first application based on the charging identifier.

The processor 1202 controls the operation of the TDF entity, and the processor 1202 may also be referred to as a CPU. Memory 1204 can include read only memory and random access memory and provides instructions and data to processor 1202. A portion of memory 1204 may also include non-volatile random access memory (NVRAM). In a specific application, the various components of the TDF entity are coupled together by a bus system 1205, wherein the bus system 1205 can include, in addition to the data bus, a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are labeled as bus system 1205 in the figure.

The method disclosed in the foregoing embodiments of the present invention may be applied to the processor 1202 or implemented by the processor 1202. Processor 1202 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1202 or an instruction in the form of software. The processor 1202 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware. Component. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software modules can be located in conventional memory, such as random memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 1204, and the processor 1202 reads the information in the memory 1204 and combines the hardware to perform the steps of the above method.

In an optional implementation, the receiver 1201 is configured to receive, by the PCRF entity, an identifier of the first application that is determined by the PCRF entity and that needs to be separately charged, and an accounting identifier that is allocated to the first application, where:

The receiver 1201 is specifically configured to receive a TDF session establishment request message sent by the PCRF entity, where the TDF session establishment request message includes an identifier of the first application and is allocated for the first application. Billing ID.

Optionally, the transmitter 1203 is further configured to send a TDF session establishment response message to the PCRF entity after the receiver 1201 receives the TDF session establishment request message sent by the PCRF entity.

In an optional implementation, the processor 1202 is further configured to detect a data packet of the first application that needs to be separately charged.

Based on the above, the transmitter 1203 is further configured to: after the processor 1202 detects the data packet of the first application, send a service flow detection event to the PCRF entity, where the service flow detection event includes the first application And determining, by the PCRF entity, determining, according to the identifier of the first application, that the first application needs to be separately charged.

Based on the foregoing, in an optional implementation, the receiver 1201 is configured to receive, by the PCRF entity, an identifier of a first application that is separately billed by the PCRF entity and a charging identifier that is allocated to the first application, where Includes:

The receiver 1201 is specifically configured to receive a modified ADC rule message sent by the PCRF entity, where the modified ADC rule message includes an identifier of the first application and a charging identifier allocated for the first application.

The TDF entity provided in this embodiment may be used to perform the process of the first charging method in the foregoing method embodiment. The specific working principle is not described here. For details, refer to the description of the method embodiment.

FIG. 13 is a schematic structural diagram of still another PCRF entity according to an embodiment of the present invention. As shown in FIG. 13, the PCRF entity includes: a sending module 1301 and a receiving module 1302.

The sending module 1301 is configured to send the PCC rule identifier and/or the SDF template to the TDF entity, where the TDF entity determines the identifier and the first application of the SDF to which the first application that affects the PCDF entity based on the SDF granularity charging result belongs The traffic of the packet.

The receiving module 1302 is configured to receive, according to the PCC rule identifier, sent by the TDF entity, And the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application determined by the SDF template.

The sending module 1301 is connected to the receiving module 1302, and is further configured to send, by the receiving module 1302, the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application to the PCEF entity, so that The PCEF entity adjusts the uplink data packet from the UE based on the SDF granularity charging result based on the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application, where the first application is The data packet belongs to an upstream data packet from the UE.

In an optional implementation, the sending module 1301 is configured to send the PCC rule identifier and/or the SDF template to the TDF entity, including:

The sending module 1301 is specifically configured to send a TDF session establishment request message to the TDF entity, where the TDF session establishment request message includes the PCC rule identifier and/or an SDF template.

Optionally, the receiving module 1302 is further configured to: after the sending module 1301 sends a TDF session establishment request message to the TDF entity, receive a TDF session establishment response message sent by the TDF entity.

In an optional implementation, the sending module 1301 is configured to send the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application to the PCEF entity, including:

The sending module 1301 is specifically configured to send an IP-CAN session modification request message to the PCEF entity, where the IP-CAN session modification request message includes an identifier of the SDF to which the first application belongs and a data packet of the first application. flow.

The function modules of the PCRF entity provided in this embodiment may be used to perform the process of the second charging method in the foregoing method embodiments. The specific working principle is not described here. For details, refer to the description of the method embodiments.

The PCRF entity provided in this embodiment sends a PCC rule identifier and/or an SDF template to the TDF entity, so that the TDF entity determines the identifier of the first application that needs to be separately charged and the traffic of the data packet of the first application, and returns the data to the embodiment. The PCRF entity, the PCRF entity of the embodiment sends the identifier of the first application and the traffic of the data packet of the first application to the PCEF entity, so that the PCEF entity re-pairs according to the identifier of the first application and the traffic of the data packet of the first application. The billing result based on the SDF granularity is adjusted to achieve accurate billing.

FIG. 14 is a schematic structural diagram of still another PCRF entity according to an embodiment of the present invention. As shown in FIG. 14, the PCRF entity includes: a transmitter 1401, a receiver 1402, a processor 1403, and a memory 1404.

a transmitter 1401, configured to send a PCC rule identifier and/or an SDF template to the TDF entity, And determining, by the TDF entity, an identifier of the SDF to which the first application that affects the PCDF entity based on the SDF granularity charging result and a traffic of the data packet of the first application.

The receiver 1402 is configured to receive, by the TDF entity, the identifier of the SDF to which the first application belongs according to the PCC rule identifier and/or the SDF template, and the traffic of the data packet of the first application.

The transmitter 1401 is further configured to send the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application to the PCEF entity, so that the PCEF entity is based on the first application belongs to The identifier of the SDF and the traffic of the data packet of the first application are adjusted according to the SDF granularity charging result of the uplink data packet from the UE, where the data packet of the first application belongs to the uplink data packet from the UE .

In the present embodiment, the memory 1404 can include read only memory and random access memory, and provides instructions and data to the processor 1403. A portion of memory 1404 may also include non-volatile random access memory (NVRAM).

Memory 1404 stores the following elements, executable modules or data structures, or subsets thereof, or their extended sets:

In the embodiment of the present invention, the processor 1403 performs a corresponding operation by calling an operation instruction stored in the memory 1404 (which can be stored in the operating system), thereby controlling the operation of the PCRF entity.

The processor 1403 controls the operation of the PCRF entity, and the processor 1403 may also be referred to as a CPU. Memory 1404 can include read only memory and random access memory and provides instructions and data to processor 1403. A portion of memory 1404 may also include non-volatile random access memory (NVRAM). In a specific application, the components of the PCRF entity are coupled together by a bus system 1405. The bus system 1405 may include a power bus, a control bus, and a status signal bus in addition to the data bus. However, for the sake of clarity, various buses are labeled as bus system 1405 in the figure.

The method disclosed in the foregoing embodiment of the present invention may be applied to the processor 1403 or implemented by the processor 1403. The processor 1403 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 1403 or an instruction in a form of software. The processor 1403 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware. Component. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software modules can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 1404. The processor 1403 reads the information in the memory 1404 and completes the steps of the above method in combination with hardware.

In an alternative embodiment, the transmitter 1401 is configured to send the PCC rule identifier and/or the SDF template to the TDF entity, including:

The transmitter 1401 is specifically configured to send a TDF session establishment request message to the TDF entity, where the TDF session establishment request message includes the PCC rule identifier and/or an SDF template.

Optionally, the receiver 1402 is further configured to: after the transmitter 1401 sends a TDF session setup request message to the TDF entity, receive a TDF session setup response message sent by the TDF entity.

In an optional implementation, the transmitter 1401 is configured to send the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application to the PCEF entity, including:

The transmitter 1401 is specifically configured to send an IP-CAN session modification request message to the PCEF entity, where the IP-CAN session modification request message includes an identifier of the SDF to which the first application belongs and a data packet of the first application. flow.

The PCRF entity provided in this embodiment can be used to perform the process of the second charging method in the foregoing method embodiment. The specific working principle is not described here. For details, refer to the description of the method embodiment.

FIG. 15 is a schematic structural diagram of still another PCEF entity according to an embodiment of the present invention. As shown in Figure 15 The PCEF entity includes: a receiving module 1501 and a charging adjustment module 1502.

The receiving module 1501 is configured to receive, by the PCRF entity, an identifier of the SDF that is affected by the first application that affects the SDF granularity-based charging result of the PCEF entity, and a traffic of the data packet of the first application, where the first The identifier of the SDF to which the application belongs and the traffic of the data packet of the first application are determined by the TDF entity according to the PCC rule identifier and/or the SDF template sent by the PCRF entity, and sent to the PCRF entity.

The charging adjustment module 1502 is configured to be connected to the receiving module 1501, configured to determine, according to the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application received by the receiving module 1501, the uplink data packet from the UE is based on The charging result of the SDF granularity is adjusted, wherein the data packet of the first application belongs to an uplink data packet from the UE.

In an optional implementation, the PCEF entity further includes: a charging module, configured to: before the receiving module 1501 receives the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application, The uplink data packet of the UE performs charging based on SDF granularity.

In an optional implementation, the receiving module 1501 is configured to receive, by the PCRF entity, an identifier of the SDF that belongs to the first application that affects the SDF granularity-based charging result of the PCEF entity, and a traffic of the data packet of the first application. , including:

The receiving module 1501 is specifically configured to receive an IP-CAN session modification request message sent by the PCRF entity, where the IP-CAN session modification request message includes an identifier of the SDF to which the first application belongs and a data packet of the first application. Traffic.

Optionally, the PCEF entity in this embodiment may further include: a sending module, configured to receive the module

After receiving the IP-CAN session modification request message sent by the PCRF entity, the 1501 sends an IP-CAN session modification response message to the PCRF entity.

The function modules of the PCEF entity provided in this embodiment may be used to perform the process of the second charging method in the foregoing method embodiment. The specific working principle is not described here. For details, refer to the description of the method embodiment.

The PCEF entity provided in this embodiment receives the identifier of the first application that needs to be separately charged and the data packet of the first application that is determined by the TDF entity and is sent by the PCRF entity, according to the identifier of the first application and the first application. The traffic of the data packet is re-adjusted based on the SDF granularity charging result to achieve accurate charging.

FIG. 16 is a schematic structural diagram of still another PCEF entity according to an embodiment of the present invention. As shown in FIG. 16, the PCEF entity includes: a receiver 1601, a processor 1602, and a memory 1603. The receiver 1601 is configured to receive, by the PCRF entity, an identifier of the SDF that belongs to the first application that affects the SDF granularity-based charging result of the PCEF entity, and a traffic of the data packet of the first application, where the first The identifier of the SDF to which the application belongs and the traffic of the data packet of the first application are determined by the TDF entity according to the PCC rule identifier and/or the SDF template sent by the PCRF entity, and sent to the PCRF entity.

Memory 1603 can include read only memory and random access memory and provides instructions and data to processor 1602. A portion of memory 1603 may also include non-volatile random access memory (NVRAM) o

Memory 1603 stores the following elements, executable modules or data structures, or subsets thereof, or their extended sets:

In the embodiment of the present invention, the processor 1602 performs the following operations by calling an operation instruction stored in the memory 1603 (the operation instruction can be stored in the operating system):

Adjusting the uplink data packet from the UE based on the SDF granularity charging result according to the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application received by the receiver 1601, where the An application's data packet belongs to an upstream data packet from the UE.

Further optionally, the PCEF entity may further include: a transmitter 1604.

The processor 1602 controls the operation of the PCEF entity, which may also be referred to as a CPU. Memory 1603 can include read only memory and random access memory and provides instructions and data to processor 1602. A portion of memory 1603 may also include non-volatile random access memory (NVRAM). In a specific application, the components of the PCEF entity are coupled together by a bus system 1605. The bus system 1605 may include a power bus, a control bus, and a status signal bus in addition to the data bus. However, for the sake of clarity, various buses are labeled as bus system 1605 in the figure.

The method disclosed in the foregoing embodiments of the present invention may be applied to the processor 1602 or implemented by the processor 1602. The processor 1602 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1602 or an instruction in a form of software. The processor 1602 described above may be a general purpose processor, a digital Signal processor (DSP), application specific integrated circuit (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software modules can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 1603, and the processor 1602 reads the information in the memory 1603, and completes the steps of the above method in combination with the hardware thereof.

In an optional implementation, the processor 1602 is further configured to: after receiving, by the receiver 1601, the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application, the uplink data packet from the UE Perform SDF granularity based charging.

In an optional implementation manner, the receiver 1601 is configured to receive, by the PCRF entity, an identifier of the SDF that belongs to the first application that affects the SDF granularity-based charging result of the PCEF entity, and a traffic of the data packet of the first application. , including:

The receiver 1601 is specifically configured to receive an IP-CAN session modification request message sent by the PCRF entity, where the IP-CAN session modification request message includes an identifier of the SDF to which the first application belongs and a data packet of the first application. Traffic.

Optionally, the transmitter 1604 is configured to send an IP-CAN session modification response message to the PCRF entity after the receiver 1601 receives the IP-CAN session modification request message sent by the PCRF entity.

The PCEF entity provided in this embodiment may be used to perform the process of the second charging method in the foregoing method embodiment. The specific working principle is not described here. For details, refer to the description of the method embodiment.

FIG. 17 is a schematic structural diagram of still another TDF entity according to an embodiment of the present invention. As shown in FIG. 17, the TDF entity includes: a receiving module 1701, a determining module 1702, and a sending module 1703.

The receiving module 1701 is configured to receive a PCC rule identifier and/or an SDF template sent by the PCRF entity. The determining module 1702 is connected to the receiving module 1701 for receiving according to the receiving module 1701. The PCC rule identifier and/or the SDF template determines an identifier of the SDF to which the first application that affects the PCEF entity based on the SDF granularity charging result and a traffic of the data packet of the first application.

The sending module 1703 is connected to the determining module 1702, and configured to send, by the PCRF entity, the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application determined by the determining module 1702 to the PCEF entity. And adjusting, by the PCEF entity, the SDL granularity-based charging result of the uplink data packet from the UE, based on the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application; The data packet of the first application belongs to an uplink data packet from the UE.

In an optional implementation, the receiving module 1701 is configured to receive a PCC rule identifier and/or an SDF template sent by the PCRF entity, including:

The receiving module 1701 is specifically configured to receive a TDF session establishment request message sent by the PCRF entity, where the TDF session establishment request message includes the PCC rule identifier and/or an SDF template.

Optionally, the sending module 1703 is further configured to send a TDF session establishment response message to the PCRF entity after the receiving module 1701 receives the TDF session establishment request message sent by the PCRF entity.

In an optional implementation, the determining module 1702 is configured to determine, according to the PCC rule identifier and/or the SDF template received by the receiving module 1701, an identifier of the SDF to which the first application that affects the PCDF entity based on the SDF granularity charging result belongs. And the traffic of the data packet of the first application, where: the determining module 1702 is specifically configured to determine, according to the PCC rule indicated by the PCC rule identifier received by the receiving module 1701, a data packet that is discarded due to performing application-based flow control. As the first application, the associated application determines the traffic of the discarded data packet as the traffic of the data packet of the first application, and determines the SDF to which the first application belongs; or

The determining module 1702 is specifically configured to: when the SDF template received by the receiving module 1701 detects that all data packets having the same IP address information in the uplink data packet from the UE are not required to be charged, the same IP address information is obtained. In all the data packets, the application to which the data packet actually required to be charged belongs is determined as the first application, and the traffic of the data packet actually required to be charged is determined as the traffic of the data packet of the first application, and the The SDF to which the first application belongs; or the determining module 1702 is specifically configured to detect, according to the SDF template received by the receiving module 1701, that all data packets having the same IP address information in the uplink data packet from the UE are not required to be counted. Time-consuming, determining, from all the data packets having the same IP address information, an application to which the data packet that does not need to be charged belongs is used as the first application, and determining the traffic of the data packet that does not need to be charged as the The traffic of the first application's data packet, and determining the SDF to which the first application belongs.

The function modules of the TDF entity provided in this embodiment can be used to perform the process of the second charging method in the foregoing method embodiment. The specific working principle is not described here. For details, refer to the description of the method embodiment.

The TDF entity provided in this embodiment receives the PCC rule identifier and/or the SDF template sent by the PCRF entity, and determines the identifier of the first application that needs to be separately charged and the traffic of the data packet of the first application, and then passes the PCRF. The entity sends the entity to the PCEF entity, so that the PCEF entity can re-adjust the charging result based on the SDF granularity according to the identifier of the first application and the traffic of the data packet of the first application, so as to implement accurate charging.

FIG. 18 is a schematic structural diagram of still another TDF entity according to an embodiment of the present invention. As shown in FIG. 18, the TDF entity includes: a receiver 1801, a processor 1802, a transmitter 1803, and a memory 1804.

The receiver 1801 is configured to receive a PCC rule identifier and/or an SDF template sent by the PCRF entity. Memory 1804 can include read only memory and random access memory and provides instructions and data to processor 602. A portion of memory 1804 may also include non-volatile random access memory (NVRAM).

Memory 1804 stores the following elements, executable modules or data structures, or subsets thereof, or their extended sets:

In the embodiment of the present invention, the processor 1802 performs the following operations by calling an operation instruction stored in the memory 1804 (which can be stored in the operating system):

And determining, according to the PCC rule identifier and/or the SDF template received by the receiver 1801, an identifier of the SDF to which the first application that affects the PCDF entity based on the SDF granularity charging result and a traffic of the data packet of the first application.

a transmitter 1803, configured to send, by the processor 1802, an identifier of an SDF to which the first application belongs and a traffic of a data packet of the first application to the PCEF entity by using the PCRF entity, to enable the PCEF The entity adjusts the uplink data packet from the UE based on the SDF granularity charging result based on the identifier of the SDF to which the first application belongs and the traffic of the data packet of the first application; where the data packet of the first application is It belongs to the uplink data packet from the UE. The processor 1802 controls the operation of the TDF entity, and the processor 1802 may also be referred to as a CPU. Memory 1804 can include read only memory and random access memory and provides instructions and data to processor 1802. A portion of the memory 1804 may also include non-volatile random access memory (NVRAM). In a specific application, the components of the TDF entity are coupled together by a bus system 1805. The bus system 1805 may include a power bus, a control bus, and a status signal bus in addition to the data bus. However, for clarity of description, various buses are labeled as bus system 1805 in the figure.

The method disclosed in the foregoing embodiments of the present invention may be applied to the processor 1802 or implemented by the processor 1802. Processor 1802 may be an integrated circuit chip with signal processing capabilities. In an implementation process, the steps of the above method may be performed by an integrated logic circuit of hardware in the processor 1802 or an instruction in the form of software. The processor 1802 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware. Component. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software modules can be located in conventional memory, such as random memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in memory 1804, and processor 1802 reads the information in memory 1804 and, in conjunction with its hardware, performs the steps of the above method.

In an optional implementation, the receiver 1801 is configured to receive a PCC rule identifier and/or an SDF template sent by the PCRF entity, including:

The receiver 1801 is specifically configured to receive a TDF session establishment request message sent by the PCRF entity, where the TDF session establishment request message includes the PCC rule identifier and/or an SDF template.

Optionally, the transmitter 1803 is further configured to send a TDF session establishment response message to the PCRF entity after the receiver 1801 receives the TDF session establishment request message sent by the PCRF entity.

In an optional implementation, the processor 1802 is configured to determine, according to the PCC rule identifier and/or the SDF template received by the receiver 1801, an identifier of the SDF to which the first application that affects the PCDF entity based on the SDF granularity charging result belongs. And the traffic of the data packet of the first application, including:

The processor 1802 is specifically configured to determine, according to the PCC rule indicated by the PCC rule identifier received by the receiver 1801, an application to which the data packet discarded by performing application-based flow control belongs Determining, by the first application, the traffic of the discarded data packet as the traffic of the data packet of the first application, and determining the SDF to which the first application belongs; or

The processor 1802 is specifically configured to: when the SDF template received by the receiver 1801 detects that all data packets having the same IP address information in the uplink data packet from the UE are not required to be charged, the slave device has the same IP address information. In all the data packets, the application to which the data packet actually required to be charged belongs is determined as the first application, and the traffic of the data packet actually required to be charged is determined as the traffic of the data packet of the first application, and the The SDF to which the first application belongs; or,

The processor 1802 is specifically configured to: when the SDF template received by the receiver 1801 detects that all data packets having the same IP address information in the uplink data packet from the UE are not required to be charged, the slave device has the same IP address information. Determining, by the application, the application to which the data packet that does not need to be charged belongs, as the first application, determining the traffic of the data packet that does not need to be charged as the traffic of the data packet of the first application, and determining the The SDF to which the first application belongs.

The TDF entity provided in this embodiment can be used to perform the process of the second charging method in the foregoing method embodiment. The specific working principle is not described here. For details, refer to the description of the method embodiment.

FIG. 19 is a schematic structural diagram of still another TDF entity according to an embodiment of the present invention. As shown in FIG. 19, the TDF entity includes: a receiving module 1901, a determining adding module 1902, and a sending module 1903.

The receiving module 1901 is configured to receive an uplink data packet sent by the PCEF entity.

The determining module 1902 is connected to the receiving module 1901, and configured to: after the receiving module 1901 receives the uplink data packet, determine reflow data, and add a charging identifier to the reflow data, where the reflow data refers to the uplink A data packet in the data packet that affects the charging result of the SDF granularity of the uplink data packet by the PCEF entity.

The sending module 1903 is connected to the determining adding module 1902, and configured to send, by the determining the adding module 1902, the reflow data carrying the charging identifier to the PCEF entity, so that the PCEF entity is configured to carry the charging identifier. The data is reflowed, and the uplink data packet is adjusted based on the SDF granularity charging result. In an optional implementation, the receiving module 1901 is further configured to: before determining that the adding module 1902 adds a charging identifier to the reflow data, receiving, by the PCRF entity, the charging that is allocated by the PCRF entity for the reflow data. Logo. Optionally, the receiving module 1901 is further connected to the determining adding module 1902, and configured to provide the charging identifier to the determining adding module 1902.

In an optional implementation, the receiving module 1901 is configured to receive, by the PCRF entity, the charging identifier that is allocated by the PCRF entity for the reflow data, and includes:

The receiving module 1901 is specifically configured to receive a TDF session establishment request message sent by the PCRF entity, where the TDF session establishment request message includes the charging identifier.

Optionally, the sending module 1903 is further configured to send a TDF session establishment response message to the PCRF entity after the receiving module 1901 receives the TDF session establishment request message sent by the PCRF entity.

The functional modules of the TDF entity provided in this embodiment may be used to perform the process of the third charging method in the foregoing method embodiments. The specific working principle is not described here. For details, refer to the description of the method embodiments.

The TDF entity provided in this embodiment determines the reflow data in the uplink data packet from the PCEF entity, and adds the recurring data to the PCEF entity after adding the charging identifier, so that the PCEF entity can determine, according to the charging identifier, that the TDF entity sends the The data is reflowed, and the SDF granularity based charging result is readjusted based on the flow of the reflow data to achieve accurate charging.

FIG. 20 is a schematic structural diagram of still another TDF entity according to an embodiment of the present invention. As shown in FIG. 20, the TDF entity includes: a receiver 2001, a processor 2002, a transmitter 2003, and a memory. The receiver 2001 is configured to receive an uplink data packet sent by a PCEF entity.

Memory 2004 can include read only memory and random access memory and provides instructions and data to processor 2002. A portion of the memory 2004 may also include non-volatile random access memory (NVRAM) o

Memory 2004 stores the following elements, executable modules or data structures, or a subset of them, or their extended set:

In the embodiment of the present invention, the processor 2002 performs the following operations by calling an operation instruction stored in the memory 2004 (the operation instruction can be stored in the operating system): After receiving the uplink data packet, the receiver 2001 determines the reflow data, and adds a charging identifier to the reflow data, where the reflow data refers to the uplink data packet affecting the PCEF entity to the uplink data. A packet based on the SDF granularity of the charging result.

The transmitter 2003 is configured to send the reflow data carrying the charging identifier to the PCEF entity, so that the PCEF entity performs the SDF granularity on the uplink data packet according to the reflow data carrying the charging identifier. The billing result is adjusted.

The processor 2002 controls the operation of the TDF entity, and the processor 2002 may also be referred to as a CPU. Memory 2004 can include read only memory and random access memory and provides instructions and data to processor 2002. A portion of the memory 2004 may also include non-volatile random access memory (NVRAM). In a specific application, the components of the TDF entity are coupled together by a bus system 2005, which may include a power bus, a control bus, and a status signal bus in addition to the data bus. However, for clarity of description, various buses are labeled as bus system 2005 in the figure.

The method disclosed in the foregoing embodiments of the present invention may be applied to the processor 2002 or implemented by the processor 2002. The processor 2002 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 2002 or an instruction in the form of software. The processor 2002 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware. Component. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software modules can be located in conventional memory, such as random memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 2004, and the processor 2002 reads the information in the memory 2004 and combines the hardware to perform the steps of the above method.

In an optional implementation, the receiver 2001 is further configured to: before the processor 2002 adds the charging identifier to the reflow data, receive, by the PCRF entity, the charging identifier that is sent by the PCRF entity to the reflow data. And providing the charging identifier to the processor 2002.

In an optional implementation, the receiver 2001 is configured to receive, by the PCRF entity, the charging identifier that is allocated by the PCRF entity for the reflow data, and includes: The receiver 2001 is specifically configured to receive a TDF session establishment request message sent by the PCRF entity, where the TDF session establishment request message includes the charging identifier.

Optionally, the transmitter 2003 is further configured to send a TDF session establishment response message to the PCRF entity after the receiver 2001 receives the TDF session establishment request message sent by the PCRF entity.

The TDF entity provided in this embodiment may be used to perform the process of the third charging method in the foregoing method embodiment. The specific working principle is not described here. For details, refer to the description of the method embodiment.

FIG. 21 is a schematic structural diagram of still another PCEF entity according to an embodiment of the present invention. As shown in FIG. 21, the PCEF entity includes: a receiving module 2101 and a charging adjustment module 2102.

The receiving module 2101 is configured to: after performing the SDF granularity-based charging on the uplink data packet, receive the reflow data that is sent by the TDF entity and that carries the charging identifier, where the reflow data is the uplink data packet that is determined by the TDF entity. a data packet affecting the SDF granularity based charging result of the uplink data packet by the PCEF entity.

The billing adjustment module 2102 is connected to the receiving module 2101, and configured to determine, according to the billing identifier, that the data received by the receiving module 2101 is the reflow data, determine an SDF to which the reflow data belongs, and determine the SDF of the reflow data. The billing result is adjusted.

In an optional implementation, the receiving module 2101 is further configured to: before receiving the reflow data carrying the charging identifier sent by the TDF entity, receiving, by the PCRF entity, the PCRF entity to allocate the reflow data Billing ID.

In an optional implementation, the receiving module 2101 is configured to receive, by the PCRF entity, the charging identifier that is allocated by the PCRF entity for the reflow data, and includes:

The receiving module 2101 is specifically configured to receive an IP-CAN session establishment response message sent by the PCRF entity, where the IP-CAN session establishment response message includes the charging identifier.

2101: Before receiving the IP-CAN session establishment response message sent by the PCRF entity, send an IP-CAN session establishment request message to the PCEF entity.

The functional modules of the PCEF entity provided in this embodiment may be used to execute the foregoing method embodiment. For the flow of the third charging method, the specific working principle is not described again. For details, refer to the description of the method embodiment. The PCEF entity provided in this embodiment receives the reflow data carried by the TDF entity and carries the charging identifier. After determining that the received data is reflow data according to the charging identifier, determining the SDF to which the reflow data belongs, and then determining the SDF. The SDF billing result is adjusted to achieve accurate billing.

FIG. 22 is a schematic structural diagram of still another PCEF entity according to an embodiment of the present invention. As shown in FIG. 22, the PCEF entity includes: a receiver 2201, a processor 2202, and a memory 2203.

The receiver 2201 is configured to receive, after the SDF granularity-based charging of the uplink data packet, the reflow data that is sent by the TDF entity and that carries the charging identifier, where the reflow data is the uplink data packet that is determined by the TDF entity. And a data packet affecting the SDF granularity-based charging result of the uplink data packet by the PCEF entity.

Memory 2203 can include read only memory and random access memory and provides instructions and data to processor 2202. A portion of memory 2203 may also include non-volatile random access memory (NVRAM) o

The memory 2203 stores the following elements, executable modules or data structures, or a subset thereof, or their extended set:

In the embodiment of the present invention, the processor 2202 performs the following operations by calling an operation instruction stored in the memory 2203 (which can be stored in the operating system):

Determining, according to the charging identifier, that the data received by the receiver 2201 is the reflow data, determining an SDF to which the reflow data belongs, and adjusting the charging result of the determined SDF.

Optionally, the PCEF entity in this embodiment further includes: a transmitter 2204.

The processor 2202 controls the operation of the PCEF entity, which may also be referred to as a CPU. Memory 2203 can include read only memory and random access memory and provides instructions and data to processor 2202. A portion of the memory 2203 may also include non-volatile random access memory (NVRAM). In a specific application, the components of the PCEF entity are coupled together by a bus system 2205. The bus system 2205 may include a power bus, a control bus, a status signal bus, and the like in addition to the data bus. However, for clarity of description, various buses are labeled as bus system 2205 in the figure. The method disclosed in the foregoing embodiment of the present invention may be applied to the processor 2202 or implemented by the processor 2202. Processor 2202 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 2202 or an instruction in a form of software. The processor 2202 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware. Component. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software modules can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 2203. The processor 2202 reads the information in the memory 2203 and completes the steps of the above method in combination with the hardware.

In an optional implementation, the receiver 2201 is further configured to: before receiving the reflow data carrying the charging identifier sent by the TDF entity, receiving, by the PCRF entity, the PCRF entity to allocate the reflow data Billing ID.

In an optional implementation, the receiver 2201 is configured to receive, by the PCRF entity, the charging identifier that is allocated by the PCRF entity for the reflow data, and includes:

The receiver 2201 is specifically configured to receive an IP-CAN session establishment response message sent by the PCRF entity, where the IP-CAN session establishment response message includes the charging identifier.

Optionally, the transmitter 2204 is configured to receive, by the receiver 2201, the sent by the PCRF entity.

An IP-CAN Session Establishment Request message is sent to the PCEF entity prior to the IP-CAN Session Setup Response message.

The PCEF entity provided in this embodiment can be used to perform the process of the third charging method in the foregoing method embodiment. The specific working principle is not described here. For details, refer to the description of the method embodiment.

The PCEF entity provided in this embodiment receives the reflow data carried by the TDF entity and carries the charging identifier. After determining that the received data is reflow data according to the charging identifier, determining the SDF to which the reflow data belongs, and then determining the SDF. The SDF billing result is adjusted to achieve accurate billing.

FIG. 23 is a schematic structural diagram of still another PCRF entity according to an embodiment of the present invention. As shown in FIG. 23, the PCRF entity includes: a determining module 2301 and a sending module 2302.

a determining module 2301, configured to determine a charging identifier that needs to be allocated to a reflow packet, the reflow The data refers to a data packet in the uplink data packet that affects the SDF granularity-based charging result of the uplink data packet by the PCEF entity.

The sending module 2302 is connected to the determining module 2301, and configured to send the charging identifier determined by the determining module 2301 to the TDF entity and the PCEF entity, where the TDF entity sends the uplink data from the PCEF entity. After the reflow data is determined in the packet, the charging identifier is added to the reflow data, and then sent to the PCEF entity, so that the PCEF entity determines the reflow data according to the charging identifier and is based on the reflow. The data adjusts the SDF granularity based charging result of the uplink data packet.

In an optional implementation, the sending module 2302 is configured to send the charging identifier to the TDF entity, including:

The sending module 2302 is specifically configured to send a TDF session establishment request message to the TDF entity, where the TDF session establishment request message includes the charging identifier.

Optionally, the PCRF entity may further include: a receiving module, configured to: after the sending module 2302 sends a TDF session establishment request message to the TDF entity, receive the TDF entity to send a TDF session establishment response message.

In an optional implementation, the sending module 2302 is configured to send the charging identifier to the PCEF entity, including:

The sending module 2302 is specifically configured to send an IP-CAN session establishment response message to the PCEF entity, where the IP-CAN session establishment response message includes the charging identifier.

The receiving module is further configured to receive an IP-CAN session establishment request message sent by the PCEF entity before the sending module 2302 sends an IP-CAN session establishment response message to the PCEF entity.

The function modules of the PCRF entity provided in this embodiment may be used to perform the process of the third charging method in the foregoing method embodiments. The specific working principle is not described here. For details, refer to the description of the method embodiments.

The PCRF entity provided in this embodiment determines the charging identifiers that are allocated to the reflow data, and sends them to the TDF entity and the PCEF entity, respectively, so that the TDF entity adds the charging identifier to the determined reflow data and sends the charging identifier to the PCEF entity. The PCEF entity determines that the data from the TDF entity is the reflow data based on the charging identifier, and then determines the SDF to which the reflow data belongs, and adjusts the determined SDF charging result to implement accurate charging.

FIG. 24 is a schematic structural diagram of still another PCRF entity according to an embodiment of the present invention. As shown in FIG. 24, the PCRF entity includes: a processor 2401, a transmitter 2402, and a memory 2403. Memory 2403 can include read only memory and random access memory and provides instructions and data to processor 2401. A portion of the memory 2403 may also include non-volatile random access memory (NVRAM) o

Memory 2403 stores the following elements, executable modules or data structures, or subsets thereof, or their extended sets:

In the embodiment of the present invention, the processor 2401 performs the following operations by calling an operation instruction stored in the memory 2403 (the operation instruction can be stored in the operating system):

A charging identifier that needs to be allocated to the reflow packet is determined, and the reflow data refers to a packet in the uplink packet that affects the SDF granularity-based charging result of the uplink packet by the PCEF entity.

a transmitter 2402, configured to send the charging identifier to a TDF entity and the PCEF entity, where the TDF entity determines the reflow data from the uplink data packet from the PCEF entity Adding the charging identifier to the PCEF entity, and then sending, by the PCEF entity, the reflow data according to the charging identifier, and based on the reflow data, based on the SDF granularity of the uplink data packet. The billing results are adjusted.

Optionally, as shown in FIG. 24, the PCRF entity may further include: a receiver 2404.

The processor 2401 controls the operation of the PCRF entity, which may also be referred to as a CPU. The memory 2403 can include read only memory and random access memory and provides instructions and data to the processor 2401. A portion of the memory 2403 may also include non-volatile random access memory (NVRAM). In a specific application, the components of the PCRF entity are coupled together by a bus system 2405. The bus system 2405 may include a power bus, a control bus, and a status signal bus in addition to the data bus. However, for the sake of clarity, various buses are labeled as bus system 2405 in the figure.

The method disclosed in the foregoing embodiments of the present invention may be applied to the processor 2401 or implemented by the processor 2401. The processor 2401 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 2401 or an instruction in a form of software. The processor 2401 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or Other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software modules can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 2403, and the processor 2401 reads the information in the memory 2403 and completes the steps of the above method in combination with the hardware thereof.

In an optional implementation, the transmitter 2402 is configured to send the charging identifier to the TDF entity, including:

The transmitter 2402 is specifically configured to send a TDF session establishment request message to the TDF entity, where

The TDF session establishment request message includes the charging identifier.

Optionally, the receiver 2404 is configured to: after the transmitter 2402 sends a TDF session setup request message to the TDF entity, receive the TDF entity to send a TDF session setup response message.

In an optional implementation, the transmitter 2402 is configured to send the charging identifier to the PCEF entity, including:

The transmitter 2402 is specifically configured to send an IP-CAN session establishment response message to the PCEF entity, where the IP-CAN session establishment response message includes the charging identifier.

The receiver 2404 is further configured to receive an IP-CAN session establishment request message sent by the PCEF entity before the transmitter 2402 sends an IP-CAN session establishment response message to the PCEF entity.

The PCRF entity provided in this embodiment may be used to perform the process of the third charging method in the foregoing method embodiment. The specific working principle is not described here. For details, refer to the description of the method embodiment.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed. The steps of the foregoing method embodiments are included; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk. Finally, it should be noted that the above embodiments are only for explaining the technical solutions of the present invention, and are not intended to be limiting thereof; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that The technical solutions described in the foregoing embodiments may be modified, or some or all of the technical features may be equivalently replaced; and the modifications or substitutions do not deviate from the technical solutions of the embodiments of the present invention. range.

Claims

claims

1. A billing method, characterized by including:

The policy control and charging rule function PCRF entity determines the first application that requires charging, and allocates a charging identifier to the first application, where the charging identifier is used to identify that separate charging is required for the first application;

The PCRF entity sends the identity of the first application and the charging identity assigned to the first application to the user equipment UE, the policy and charging execution PCEF entity and the service detection function TDF entity respectively, so that the UE and the TDF entity adds the charging identifier to the data packet of the first application and sends it to the PCEF entity, so that the PCEF entity allocates the information to the first application based on the identifier of the first application and The charging identifier separately charges the data packets carrying the charging identifier from the UE and the TDF entity.

2. The method according to claim 1, wherein the PCRF entity sends the identity of the first application and the charging identity assigned to the first application to the UE and the PCEF entity respectively, including:

The PCRF entity sends an Internet connection access network IP-CAN session establishment response message to the PCEF entity. The IP-CAN session establishment response message includes the identification of the first application and the allocated calculation for the first application. The PCEF entity sends the identity of the first application and the charging identity assigned to the first application to the UE through the service gateway device.

3. The method according to claim 2, characterized in that before the PCRF entity sends the IP-CAN session establishment response message to the PCEF entity, it further includes:

The PCRF entity receives the IP-CAN session establishment request message sent by the PCEF entity.

4. The method according to any one of claims 1 to 3, characterized in that, the PCRF entity combines the identity of the first application and the charging identity TDF entity allocated for the first application, including: The PCRF entity sends a TDF session establishment request message to the TDF entity, where the TDF session establishment request message includes the identity of the first application and the charging identity assigned to the first application.

5. The method according to claim 4, characterized in that, after the PCRF entity sends a TDF session establishment request message to the TDF entity, it further includes:

The PCRF entity receives the TDF session establishment response message sent by the TDF entity.

6. The method according to claim 1, characterized in that the PCRF entity determines the need The first application for billing, including:

The PCRF entity receives a business flow detection event sent by the TDF entity. The business flow detection event is sent after the TDF entity detects the data packet of the first application that needs to be charged, and the business flow detection event The detection event includes the identification of the first application;

The PCRF entity determines the first application according to the identification of the first application.

7. The method according to claim 6, wherein the PCRF entity sends the identity of the first application and the charging identity assigned to the first application to the UE and the PCEF entity respectively, including:

The PCRF entity sends a policy and charging rule message to the PCEF entity, where the policy and charging rule message includes the identity of the first application and the charging identity assigned to the first application, so that the The PCEF entity sends the identity of the first application and the charging identity assigned to the first application to the UE through the service gateway device.

8. The method according to claim 6 or 7, characterized in that the PCRF entity combines the identity of the first application and the charging identity assigned to the first application to the TDF entity, including:

The PCRF entity sends a modified application detection control ADC rule message to the TDF entity, where the modified ADC rule message includes the identifier of the first application and the charging identifier assigned to the first application.

9. A billing method, characterized by including:

Policy and charging execution The PCEF entity receives the identity of the first application that requires separate charging determined by the PCRF entity and the charging identity assigned to the first application sent by the policy control and charging rule function PCRF entity;

The PCEF entity sends the identity of the first application and the charging identity assigned to the first application to the user equipment UE through the serving gateway device, so that the UE can be included in the uplink data packet of the first application. Add the charging identifier and send it to the PCEF entity;

The PCEF entity receives the uplink data packet carrying the charging identification sent by the UE, and performs separate charging on the uplink data packet carrying the charging identification according to the charging identification.

10. The method according to claim 9, further comprising:

The PCEF entity receives the downlink data packet carrying the charging identification sent by the service detection function TDF entity, and performs separate charging on the downlink data packet carrying the charging identification according to the charging identification.

11. The method according to claim 9 or 10, characterized in that, the PCEF entity receives the identifier of the first application that requires separate charging and is determined by the PCRF entity and is sent by the PCRF entity and allocates the information to the first application. The billing identifier includes:

The PCEF entity receives the Internet connection access network IP-CAN session establishment response message sent by the PCRF entity. The IP-CAN session establishment response message includes the identification of the first application and the allocation of the first application. Billing ID; or

The PCEF entity receives the policy and charging rule message sent by the PCRF entity, and the policy and charging rule message includes the identifier of the first application and the charging identifier assigned to the first application.

12. The method according to claim 11, wherein before the PCEF entity receives the IP-CAN session establishment response message sent by the PCRF entity, it further includes:

13. The method according to any one of claims 9 to 12, characterized in that, the PCEF entity sends the identity of the first application and the charging identity assigned to the first application through the service gateway device. UE, including:

The PCEF entity sends an IP-CAN bearer establishment response message to the serving gateway device, where the IP-CAN bearer establishment response message includes the identification of the first application and the charging identification assigned to the first application, so as to The serving gateway device is caused to send the identity of the first application and the charging identity assigned to the first application to the UE.

14. The method according to claim 13, wherein before the PCEF entity sends the IP-CAN bearer establishment response message to the serving gateway device, it further includes:

The PCEF entity receives the IP-CAN bearer establishment request message sent by the serving gateway device, and the IP-CAN bearer establishment request message includes the identity of the UE.

15. A billing method, characterized by including:

The service detection function TDF entity receives the policy control and charging rule function The identification of the first application that requires separate charging and the charging identification assigned to the first application determined by the PCRF entity and sent by the PCRF entity;

The TDF entity determines the downlink data packet of the first application based on the identifier of the first application, and adds the charging identifier to the downlink data packet of the first application;

The TDF entity sends the downlink data packet with the charging identifier added to the policy and charging execution PCEF entity, so that the PCEF entity separately charges the downlink data packet of the first application based on the charging identifier.

16. The method according to claim 15, characterized in that, the TDF entity receives, sent by the PCRF entity, the identification of the first application that requires separate charging determined by the PCRF entity and the accounting information allocated for the first application. Fee identification, including:

The TDF entity receives the TDF session establishment request message sent by the PCRF entity, and the TDF session establishment request message includes the identification of the first application and the charging identification assigned to the first application.

17. The method according to claim 16, characterized in that, after the TDF entity receives the TDF session establishment request message sent by the PCRF entity, it further includes:

18. The method according to claim 15, characterized in that, the TDF entity receives, sent by the PCRF entity, the identification of the first application that requires separate charging determined by the PCRF entity and the accounting information allocated for the first application. Before the fee logo, also include:

The TDF entity detects the data packet of the first application that requires separate charging, and after detecting the data packet of the first application, sends a business flow detection event to the PCRF entity, the business flow detection event The identifier of the first application is included, so that the PCRF entity determines that the first application needs to be charged separately according to the identifier of the first application.

19. The method according to claim 18, characterized in that, the TDF entity receives, sent by the PCRF entity, the identification of the first application that requires separate charging determined by the PCRF entity and the accounting information allocated for the first application. Fee identification, including:

The TDF entity receives the modified application detection control ADC rule message sent by the PCRF entity, and the modified ADC rule message includes the identifier of the first application and the charging identifier assigned to the first application.

20. A billing method, characterized by including:

The policy control and charging rule function PCRF entity sends the policy and charging control PCC rule identification and/or service data flow SDF template to the service detection function TDF entity, so that the TDF entity determines the impact policy and charging execution based on the PCEF entity The SDF granular charging result includes the identification of the SDF to which the first application belongs and the traffic volume of the data packet of the first application;

The PCRF entity receives the identity and/or SDF sent by the TDF entity according to the PCC rule. The template determines the identity of the SDF to which the first application belongs and the flow of data packets of the first application. The PCRF entity determines the identity of the SDF to which the first application belongs and the flow of data packets of the first application. Sent to the PCEF entity, so that the PCEF entity charges the uplink data packets from the user equipment UE based on the SDF granularity based on the identity of the SDF to which the first application belongs and the traffic of the data packets of the first application. The result is adjusted; wherein, the data packet of the first application belongs to the uplink data packet from the UE.

21. The method according to claim 20, characterized in that the PCC rule identification and/or SDF template sent by the PCRF entity to the TDF entity includes:

The PCRF entity sends a TDF session establishment request message to the TDF entity, and the TDF session establishment request message includes the PCC rule identification and/or SDF template.

22. The method according to claim 21, characterized in that, after the PCRF entity sends the TDF session establishment request message to the TDF entity, it further includes:

23. The method according to any one of claims 20 to 22, characterized in that, the PCRF entity sends the identification of the SDF to which the first application belongs and the traffic of the data packet of the first application to the PCEF entities, including:

The PCRF entity sends an Internet connection access network IP-CAN session modification request message to the PCEF entity. The IP-CAN session modification request message includes the identification of the SDF to which the first application belongs and the data of the first application. Packet traffic.

24. A billing method, characterized by including:

The policy and charging execution PCEF entity receives the identity of the SDF to which the first application belongs and the SDF of the first application that affects the charging result of the PCEF entity based on the service data flow SDF granularity sent by the policy control and charging rule function PCRF entity. The traffic of the data packet; wherein, the identity of the SDF to which the first application belongs and the traffic of the data packet of the first application are the identity of the policy and charging control PCC rules sent by the service detection function TDF entity according to the PCRF entity and /or the SDF template is determined and sent to the PCRF entity;

The PCEF entity adjusts the SDF granularity-based charging result of the uplink data packet from the user equipment UE according to the identity of the SDF to which the first application belongs and the traffic of the data packet of the first application, wherein, The data packet of the first application belongs to the uplink data packet from the UE.

25. The method according to claim 24, characterized in that the PCEF entity receives the identifier of the SDF to which the first application that affects the PCEF entity's charging result based on SDF granularity and the first application is sent by the PCRF entity. Before applying the packet traffic, also include:

The PCEF entity performs SDF granularity-based charging on uplink data packets from the UE.

26. The method according to claim 24 or 25, characterized in that, the PCEF entity receives the identification of the SDF to which the first application that affects the PCEF entity's charging result based on SDF granularity and the said The traffic of the first application packet, including:

The PCEF entity receives the Internet connection access network IP-CAN session modification request message sent by the PCRF entity. The IP-CAN session modification request message includes the identification of the SDF to which the first application belongs and the ID of the first application. Packet traffic.

27. A billing method, characterized by including:

Business detection function TDF entity receives policy control and charging rule function Policy and charging control sent by PCRF entity PCC rule identification and/or service data flow SDF template;

The TDF entity determines, according to the PCC rule identifier and/or SDF template, the identity of the SDF to which the first application belongs and the data packet of the first application that affects the policy and charging execution based on the SDF granularity charging result of the PCEF entity. flow;

The TDF entity sends the identity of the SDF to which the first application belongs and the traffic of the data packet of the first application to the PCEF entity through the PCRF entity, so that the PCEF entity is based on the first application. The identification of the SDF to which it belongs and the traffic volume of the data packet of the first application adjust the charging result of the uplink data packet from the user equipment UE based on the SDF granularity; wherein, the data packet of the first application belongs to the UE. of upstream data packets.

28. The method according to claim 27, characterized in that the TDF entity receives the PCC rule identification and/or SDF template sent by the PCRF entity, including:

The TDF entity receives the TDF session establishment request message sent by the PCRF entity, and the TDF session establishment request message includes the PCC rule identification and/or SDF template.

29. The method according to claim 28, wherein after the TDF entity receives the TDF session establishment request message sent by the PCRF entity, it further includes:

30. The method according to any one of claims 27 to 29, characterized in that, the TDF entity determines the influencing PCEF entity based on the PCC rule identifier and/or SDF template based on SDF granularity The identification of the SDF to which the first application belongs and the traffic volume of the data packet of the first application include:

The TDF entity determines, according to the PCC rule indicated by the PCC rule identifier, the application to which the discarded data packet belongs due to execution of application-based flow control as the first application, and determines the flow of the discarded data packet as The traffic of data packets of the first application, and determine the SDF to which the first application belongs; or

When the TDF entity detects that it is not necessary to charge all data packets with the same IP address information in the uplink data packets from the UE according to the SDF template, determine from all data packets with the same IP address information The application to which the data packets that actually need to be charged belongs is used as the first application, the traffic of the data packets that actually need to be charged is determined as the traffic of the data packets of the first application, and the SDF to which the first application belongs is determined; or,

When the TDF entity detects that it is not necessary to charge all data packets with the same IP address information in the uplink data packets from the UE according to the SDF template, it determines from all data packets with the same IP address information that it is not necessary. The application to which the charged data packets belong is used as the first application, the traffic of the data packets that do not need to be charged is determined as the traffic of the data packets of the first application, and the SDF to which the first application belongs is determined.

31. A billing method, characterized by including:

After the service detection function TDF entity receives the uplink data packet sent by the policy and charging execution PCEF entity, it determines the backflow data and adds a charging identifier to the backflow data. The backflow data refers to the affected data in the uplink data packet. The PCEF entity charges the uplink data packet based on the service data flow SDF granularity of the data packet;

The TDF entity sends the backflow data carrying the charging identifier to the PCEF entity, so that the PCEF entity charges the uplink data packet based on SDF granularity based on the backflow data carrying the charging identifier. The results are adjusted.

32. The method according to claim 31, characterized in that the TDF entity receives

After the PCEF entity sends the uplink data packet, it determines the return data, and before adding the charging identifier to the return data, it also includes:

The TDF entity receives the charging identifier sent by the policy control and charging rule function PCRF entity and allocated by the PCRF entity for the reflow data.

33. The method according to claim 32, characterized in that, the TDF entity receives PCRF The charging identifier sent by the PCRF entity for the backflow data includes: the TDF entity receives the TDF session establishment request message sent by the PCRF entity, and the TDF session establishment request message includes the accounting fee logo.

34. The method according to claim 33, characterized in that, after the TDF entity receives the TDF session establishment request message sent by the PCRF entity, it further includes:

35. A billing method, characterized by including:

After the policy and charging execution PCEF entity performs charging on the uplink data packet based on the service data flow SDF granularity, it receives the return data carrying the charging identifier sent by the service detection function TDF entity, and the return data is the TDF entity The determined data packets in the uplink data packets affect the SDF granularity-based charging result of the PCEF entity for the uplink data packets;

The PCEF entity determines that the received data is the reflow data according to the charging identifier, determines the SDF to which the reflow data belongs, and adjusts the charging result of the determined SDF.

36. The method according to claim 35, characterized in that, before the PCEF entity receives the reflow data carrying the charging identifier sent by the TDF entity, it includes:

The PCEF entity receives the charging identifier sent by the policy control and charging rule function PCRF entity and allocated by the PCRF entity for the reflow data.

37. The method according to claim 36, wherein the PCEF entity receives the charging identifier sent by the PCRF entity and allocated by the PCRF entity for the reflow data, including:

The PCEF entity receives the Internet connection access network IP-CAN session establishment response message sent by the PCRF entity, and the IP-CAN session establishment response message includes the charging identifier.

38. The method according to claim 37, wherein before the PCEF entity receives the IP-CAN session establishment response message sent by the PCRF entity, it further includes:

39. A billing method, characterized by including:

The policy control and charging rules function PCRF entity determines the charging identifier that needs to be allocated to the backflow data packet. The backflow data refers to the service data flow in the uplink data packet that affects the policy and charging execution PCEF entity on the uplink data packet. Data packets of accounting results at SDF granularity;

The PCRF entity sends the charging identification to the service detection function TDF entity and the PCEF entity, so that the TDF entity determines the uplink data packet from the PCEF entity. After the backflow data is added to the backflow data, the charging identifier is sent to the PCEF entity, so that the PCEF entity determines the backflow data based on the charging identifier and performs the uplink processing based on the backflow data. The accounting results of data packets based on SDF granularity are adjusted.

40. The method according to claim 39, characterized in that the PCRF entity sends the charging identification to the TDF entity, including:

The PCRF entity sends a TDF session establishment request message to the TDF entity, and the TDF session establishment request message includes the charging identifier.

41. The method according to claim 40, characterized in that, after the PCRF entity sends the TDF session establishment request message to the TDF entity, it further includes:

42. The method according to any one of claims 39-41, characterized in that the PCRF entity sends the charging identifier to the PCEF entity, including:

43. The method according to claim 42, characterized in that the PCRF entity sends a message to the

Before the PCEF entity sends the IP-CAN session establishment response message, it also includes:

44. A policy control and charging rule function PCRF entity, characterized in that it includes: a determination module, used to determine the first application that requires charging;

An allocation module, configured to allocate a charging identifier to the first application, where the charging identifier is used to identify the need for separate charging of the first application;

A sending module, configured to send the identification of the first application determined by the determination module and the charging identification allocated by the allocation module to the user equipment UE, the policy and charging execution PCEF entity and The service detection function TDF entity is configured to enable the UE and the TDF entity to add the charging identifier to the data packet of the first application and then send it to the PCEF entity, so that the PCEF entity can The application identifier and the charging identifier assigned to the first application perform separate charging on the data packets carrying the charging identifier from the UE and the TDF entity.

45. The PCRF entity according to claim 44, wherein the sending module is configured to send the identity of the first application and the charging identity assigned to the first application to the UE and the PCEF entity respectively, include: The sending module is specifically configured to send an Internet connection access network IP-CAN session establishment response message to the PCEF entity. The IP-CAN session establishment response message includes the identification of the first application and the ID of the first application. The assigned charging identity is so that the PCEF entity sends the identity of the first application and the charging identity assigned to the first application to the UE through the serving gateway device.

46. The PCRF entity according to claim 44 or 45, characterized in that the sending module combines the identity of the first application and the charging identity TDF entity allocated for the first application, including: the sending The module is specifically configured to send a TDF session establishment request message to the TDF entity, where the TDF session establishment request message includes the identity of the first application and the charging identity assigned to the first application.

47. The PCRF entity according to claim 44, wherein the determining module is specifically configured to receive a service flow detection event sent by the TDF entity, and the service flow detection event is when the TDF entity detects a need to calculate The first application is sent after paying the data packet of the first application, and the business flow detection event includes the identifier of the first application; and the first application is determined according to the identifier of the first application.

48. The PCRF entity according to claim 47, wherein the sending module is configured to send the identity of the first application and the charging identity assigned to the first application to the UE and the PCEF entity respectively, include:

The sending module is specifically configured to send a policy and charging rule message to the PCEF entity, where the policy and charging rule message includes the identity of the first application and the charging identity assigned to the first application, to The PCEF entity is caused to send the identity of the first application and the charging identity assigned to the first application to the UE through the serving gateway device.

49. The PCRF entity according to claim 47 or 48, characterized in that the sending module is configured to combine the identity of the first application and the charging identity allocated for the first application to the TDF entity, including:

The sending module is specifically configured to send a modified application detection control ADC rule message to the TDF entity, where the modified ADC rule message includes the identifier of the first application and the charging identifier assigned to the first application.

50. A policy and charging execution PCEF entity, characterized by including:

A receiving module, configured to receive the PCRF sent by the policy control and charging rule function PCRF entity The identity of the first application that requires separate charging determined by the entity and the charging identity assigned to the first application;

A sending module, configured to send the identification of the first application and the charging identification assigned to the first application received by the receiving module to the user equipment UE through the service gateway device, so that the UE can be used in the first application. Add the charging identifier to the uplink data packet of an application and send it to the PCEF entity; The receiving module is also used to receive the uplink data packet sent by the UE and carrying the charging identifier;

A charging module, configured to separately charge the uplink data packets carrying the charging identifier received by the receiving module according to the charging identifier.

51. The PCEF entity according to claim 50, wherein the receiving module is further configured to receive a downlink data packet carrying the charging identifier sent by the service detection function TDF entity; the charging module is further It is used for separately charging the downlink data packet carrying the charging identifier received by the receiving module according to the charging identifier.

52. The PCEF entity according to claim 50 or 51, wherein the receiving module is configured to receive the identifier of the first application that the PCRF entity determines needs to be separately charged and the identification number for the first application sent by the PCRF entity. An application-assigned billing identifier, including:

The receiving module is specifically configured to receive an Internet connection access network IP-CAN session establishment response message sent by the PCRF entity. The IP-CAN session establishment response message includes the identification of the first application and the identifier for the first application. assigned billing ID; or

The receiving module is specifically configured to receive a policy and charging rule message sent by the PCRF entity, where the policy and charging rule message includes the identifier of the first application and the charging identifier assigned to the first application.

53. The PCEF entity according to any one of claims 50 to 52, characterized in that the sending module is configured to send the identity of the first application and the charging identity allocated to the first application through the service gateway. The device sends to the UE, including:

The sending module is specifically configured to send an IP-CAN bearer establishment response message to the service gateway device. The IP-CAN bearer establishment response message includes the identification of the first application and the charging allocated for the first application. Identity, so that the service gateway device sends the identification of the first application and the charging identification assigned to the first application to the UE.

54. A service detection function TDF entity, which is characterized by including: A receiving module, configured to receive the identification of the first application that requires separate charging determined by the PCRF entity and the charging identification assigned to the first application sent by the policy control and charging rule function PCRF entity;

Determine and add a module, configured to determine the downlink data packet of the first application according to the identification of the first application received by the receiving module, and add all the downlink data packets received by the receiving module to the downlink data packet of the first application. The above billing identification;

A sending module, configured to send the downlink data packet with the charging identifier added to the policy and charging execution PCEF entity, so that the PCEF entity performs separate processing on the downlink data packet of the first application based on the charging identifier. Billing.

55. The TDF entity according to claim 54, characterized in that, the receiving module is configured to receive the identifier of the first application that the PCRF entity determines needs to be separately charged and the identification number for the first application sent by the PCRF entity. Assigned billing IDs, including:

The receiving module is specifically configured to receive a TDF session establishment request message sent by the PCRF entity. The TDF session establishment request message includes the identification of the first application and the charging identification assigned to the first application.

56. The TDF entity according to claim 54, further comprising:

A detection module, configured to detect data packets of the first application that require separate charging;

The sending module is also configured to send a business flow detection event to the PCRF entity after the detection module detects the data packet of the first application, where the business flow detection event includes the identification of the first application. , so that the PCRF entity determines that the first application needs to be charged separately according to the identification of the first application.

57. The TDF entity according to claim 56, characterized in that, the receiving module is configured to receive the identifier of the first application that requires separate charging and is determined by the PCRF entity and is sent by the PCRF entity. Assigned billing IDs, including:

The receiving module is specifically configured to receive a modified application detection control ADC rule message sent by the PCRF entity, where the modified ADC rule message includes the identifier of the first application and the charging identifier assigned to the first application.

58. A policy control and charging rule function PCRF entity, characterized in that it includes: a processor, configured to determine the first application that requires charging, and allocate a charging identifier to the first application, and the charging The identifier is used to identify that the first application needs to be charged separately; A transmitter, configured to send the identity of the first application determined by the processor and the charging identity assigned by the processor to the user equipment UE, the policy and charging execution PCEF entity and The service detection function TDF entity is configured to enable the UE and the TDF entity to add the charging identifier to the data packet of the first application and then send it to the PCEF entity, so that the PCEF entity performs the operation based on the first application. The application identifier and the charging identifier assigned to the first application perform separate charging on the data packets carrying the charging identifier from the UE and the TDF entity.

59. A policy and charging execution PCEF entity, characterized by including:

Receiver, configured to receive the identification of the first application that requires separate charging determined by the PCRF entity and the charging identification assigned to the first application sent by the policy control and charging rule function PCRF entity;

A transmitter, configured to send the identity of the first application received by the receiver and the charging identity assigned to the first application to the user equipment UE through the serving gateway device, so that the UE can Add the charging identifier to the uplink data packet of an application and send it to the PCEF entity;

The receiver is also configured to receive an uplink data packet carrying the charging identifier sent by the UE;

A processor, configured to separately charge the uplink data packet carrying the charging identifier received by the receiver according to the charging identifier.

60. A business detection function TDF entity, which is characterized by including:

A processor, configured to determine the downlink data packet of the first application according to the identification of the first application received by the receiver, and add the downlink data packet received by the receiver to the downlink data packet of the first application. billing identification;

Transmitter, used to send the downlink data packet with the charging identifier added to the policy and charging execution

PCEF entity, so that the PCEF entity separately charges the downlink data packet of the first application based on the charging identifier.

61. A policy control and charging rule function PCRF entity, characterized in that it includes: a sending module, used to send the policy and charging control PCC rule identification and/or service data flow SDF template to the service detection function TDF entity, for the TDF entity to determine the impact policy and billing implementation The PCEF entity determines the identity of the SDF to which the first application belongs and the traffic volume of the data packet of the first application based on the SDF granular charging result;

A receiving module, configured to receive the identity of the SDF to which the first application belongs and the traffic of the data packet of the first application sent by the TDF entity and determined according to the PCC rule identity and/or the SDF template;

The sending module is also configured to send the identity of the SDF to which the first application belongs and the traffic of the data packet of the first application to the PCEF entity, so that the PCEF entity can The SDF identifier and the traffic of the data packet of the first application are used to adjust the charging result of the uplink data packet from the user equipment UE based on the SDF granularity; wherein, the data packet of the first application belongs to the SDF granularity. Upstream data packet.

62. The PCRF entity according to claim 61, characterized in that the PCC rule identifier and/or SDF template sent by the sending module to the TDF entity includes:

The sending module is specifically configured to send a TDF session establishment request message to the TDF entity, where the TDF session establishment request message includes the PCC rule identification and/or SDF template.

63. The PCRF entity according to claim 61 or 62, characterized in that the sending module is configured to send the identification of the SDF to which the first application belongs and the traffic of the data packet of the first application to the PCEF entities, including:

The sending module is specifically configured to send an Internet connection access network IP-CAN session modification request message to the PCEF entity. The IP-CAN session modification request message includes the identification of the SDF to which the first application belongs and the first The traffic of application packets.

64. A policy and charging execution PCEF entity, characterized by including:

A receiving module, configured to receive the identification of the SDF to which the first application belongs and the data packet of the first application sent by the policy control and charging rule function PCRF entity that affects the charging result of the PCEF entity based on the service data flow SDF granularity. The traffic; wherein, the identity of the SDF to which the first application belongs and the traffic of the data packet of the first application are the policy and charging control PCC rule identification and/or sent by the service detection function TDF entity according to the PCRF entity The SDF template is determined and sent to the PCRF entity;

A charging adjustment module, configured to adjust the SDF granularity-based charging result of the uplink data packet from the user equipment UE according to the identity of the SDF to which the first application belongs and the traffic of the data packet of the first application, where , the data packet of the first application belongs to the uplink data packet from the UE.

65. The PCEF entity according to claim 64, further comprising: a charging module, configured to receive, in the receiving module, the identity of the SDF to which the first application belongs and the traffic volume of the data packet of the first application. Previously, uplink data packets from the UE were charged based on SDF granularity.

66. The PCEF entity according to claim 64 or 65, wherein the receiving module is configured to receive the identification of the SDF to which the first application that affects the charging result of the PCEF entity based on SDF granularity is sent by the PCRF entity. and the traffic of data packets of the first application, including:

The receiving module is specifically configured to receive an Internet connection access network IP-CAN session modification request message sent by the PCRF entity. The IP-CAN session modification request message includes the identification of the SDF to which the first application belongs and the first application. The flow of packets for an application.

67. A business detection function TDF entity, which is characterized by including:

The receiving module is used to receive the policy control and charging rule function, policy and charging control PCC rule identification and/or service data flow SDF template sent by the PCRF entity;

Determining module, configured to determine, according to the PCC rule identification and/or SDF template received by the receiving module, the identification and identification of the SDF to which the first application that affects the policy and charging execution PCEF entity's charging results based on SDF granularity belongs. The traffic of data packets of the first application;

A sending module, configured to send the identity of the SDF to which the first application belongs and the traffic of the data packet of the first application determined by the determination module to the PCEF entity through the PCRF entity, so that the PCEF The entity adjusts the charging result of the uplink data packet from the user equipment UE based on the SDF granularity based on the identity of the SDF to which the first application belongs and the traffic of the data packet of the first application; wherein, the first application's The data packet belongs to the uplink data packet from the UE.

68. The TDF entity according to claim 67, wherein the receiving module is configured to receive the PCC rule identification and/or SDF template sent by the PCRF entity, including:

The receiving module is specifically configured to receive a TDF session establishment request message sent by the PCRF entity, where the TDF session establishment request message includes the PCC rule identification and/or SDF template.

69. The TDF entity according to claim 67 or 68, wherein the determining module is configured to determine, based on the PCC rule identifier and/or SDF template received by the receiving module, the factors affecting the PCEF entity based on the SDF granularity. The identification of the SDF to which the first application of the charging result belongs and the traffic volume of the data packet of the first application include:

The determining module is specifically configured to identify the PCC rule according to the indication received by the receiving module. PCC rules, determine the application to which the discarded data packets belong due to execution of application-based flow control as the first application, determine the flow of the discarded data packets as the flow of the data packets of the first application, and determine the SDF to which the first application belongs; or

The determining module is specifically configured to detect, based on the SDF template received by the receiving module, that it is not necessary to charge all data packets with the same IP address information in the uplink data packets from the UE, from the Among all the data packets of the address information, determine the application to which the data packets that actually need to be charged belong as the first application, determine the traffic of the data packets that actually need to be charged as the traffic of the data packets of the first application, and determine The SDF to which the first application belongs; or,

The determining module is specifically configured to detect, based on the SDF template received by the receiving module, that it is not necessary to charge all data packets with the same IP address information in the uplink data packets from the UE, from the All data packets of the address information, determine the application to which the data packets that do not need to be charged belong as the first application, determine the traffic of the data packets that do not need to be charged as the traffic of the data packets of the first application, and determine The SDF to which the first application belongs.

70. A policy control and charging rule function PCRF entity, characterized in that it includes: a transmitter, used to send the policy and charging control PCC rule identification and/or service data flow SDF template to the service detection function TDF entity, For the TDF entity to determine the identity of the SDF to which the first application belongs and the traffic of the data packet of the first application based on the charging result of the SDF granularity that affects the policy and charging execution of the PCEF entity;

Receiver, configured to receive the identifier of the SDF to which the first application belongs and the stream of data packets of the first application sent by the TDF entity and determined according to the PCC rule identifier and/or the SDF template; the transmitter , and is also used to send the identity of the SDF to which the first application belongs and the traffic of the data packet of the first application to the PCEF entity, so that the PCEF entity is based on the identity of the SDF to which the first application belongs. The charging result of the uplink data packet from the user equipment UE is adjusted based on the SDF granularity based on the traffic of the data packet of the first application; wherein, the data packet of the first application belongs to the uplink data packet from the UE.

71. A policy and charging execution PCEF entity, characterized by including:

Receiver, configured to receive the identification of the SDF to which the first application belongs and the data packet of the first application that affects the charging result of the PCEF entity based on the service data flow SDF granularity sent by the policy control and charging rule function PCRF entity. traffic; wherein, the identity of the SDF to which the first application belongs and The traffic of the data packet of the first application is determined by the service detection function TDF entity according to the policy and charging control PCC rule identification and/or SDF template sent by the PCRF entity and sent to the PCRF entity;

The processor is configured to adjust the SDF granularity-based charging result of the uplink data packet from the user equipment UE according to the identification of the SDF to which the first application belongs and the traffic of the data packet of the first application, wherein, The data packet of the first application belongs to the uplink data packet from the UE.

72. A business detection function TDF entity, which is characterized by including:

Receiver, used to receive the policy control and charging rule function PCRF entity sent policy and charging control PCC rule identification and/or service data flow SDF template;

A processor configured to determine, according to the PCC rule identification and/or SDF template received by the receiver, the identification and identity of the SDF to which the first application that affects the policy and charging execution PCEF entity's charging results based on SDF granularity belongs. The traffic of data packets of the first application;

A transmitter, configured to send the identity of the SDF to which the first application determines and the traffic of the data packet of the first application determined by the processor to the PCEF entity through the PCRF entity, so that the PCEF The entity adjusts the charging result of the uplink data packet from the user equipment UE based on the SDF granularity based on the identity of the SDF to which the first application belongs and the traffic of the data packet of the first application; wherein, the first application's The data packet belongs to the uplink data packet from the UE.

73. A business detection function TDF entity, which is characterized by including:

A receiving module, configured to receive the uplink data packet sent by the policy and charging execution PCEF entity; and a determining and adding module, configured to determine the return data after the receiving module receives the uplink data packet, and add the return data to the return data packet. Charging identifier, the backflow data refers to the data packet in the uplink data packet that affects the charging result of the PCEF entity for the uplink data packet based on the service data flow SDF granularity;

A sending module, configured to send the backflow data carrying the charging identifier to the PCEF entity, so that the PCEF entity calculates the uplink data packet based on SDF granularity according to the backflow data carrying the charging identifier. Fee results are adjusted.

74. The TDF entity according to claim 73, wherein the receiving module is further configured to receive a policy control and charging rule function PCRF entity before the determining and adding module adds a charging identifier to the reflow data. The sending PCRF entity assigns the charging identifier for the reflow data.

75. The TDF entity according to claim 74, wherein the receiving module is configured to receive the charging identifier sent by the PCRF entity and allocated by the PCRF entity for the reflow data, including:

76. A policy and charging execution PCEF entity, characterized by including:

The receiving module is configured to receive the return data carrying the charging identifier sent by the service detection function TDF entity after charging the uplink data packet based on the service data flow SDF granularity. The return data is determined by the TDF entity. Data packets in the uplink data packet that affect the SDF granularity-based charging result of the PCEF entity for the uplink data packet;

A charging adjustment module, configured to determine that the data received by the receiving module is the reflow data according to the charging identification, determine the SDF to which the reflow data belongs, and adjust the charging results of the determined SDF.

77. The PCEF entity according to claim 76, wherein the receiving module is further configured to receive the policy control and charging rule function PCRF before receiving the backflow data carrying the charging identifier sent by the TDF entity. The charging identifier assigned by the PCRF entity to the backflow data is sent by the entity.

78. The PCEF entity according to claim 77, wherein the receiving module is configured to receive the charging identifier sent by the PCRF entity and allocated by the PCRF entity for the reflow data, including:

The receiving module is specifically configured to receive an Internet connection access network IP-CAN session establishment response message sent by the PCRF entity, where the IP-CAN session establishment response message includes the charging identification.

79. A policy control and charging rule function PCRF entity, characterized in that it includes: a determination module, used to determine the charging identifier that needs to be allocated to the backflow data packet, and the backflow data refers to the impact policy and in the uplink data packet The charging execution PCEF entity performs the charging result of the uplink data packet based on the service data flow SDF granularity for the data packet;

A sending module, configured to send the charging identifier to the service detection function TDF entity and the PCEF entity, so that the TDF entity determines the return data from the uplink data packet from the PCEF entity. After adding the charging identifier to the reflow data, the PCEF implements The PCEF entity determines the backflow data according to the charging identifier and adjusts the SDF granularity-based charging result of the uplink data packet based on the backflow data.

80. The PCRF entity according to claim 79, characterized in that the sending module is used to send the charging identification to the TDF entity, including:

81. The PCRF entity according to claim 79 or 80, characterized in that the sending module is used to send the charging identification to the PCEF entity, including:

The sending module is specifically configured to send an Internet connection access network IP-CAN session establishment response message to the PCEF entity, where the IP-CAN session establishment response message includes the charging identification.

82. A business detection function TDF entity, which is characterized by including:

A receiver, configured to receive the uplink data packet sent by the policy and charging execution PCEF entity; a processor, configured to determine the backflow data after the receiver receives the uplink data packet, and add calculations to the backflow data Charge identifier, the backflow data refers to the data packet in the uplink data packet that affects the charging result of the PCEF entity for the uplink data packet based on the service data flow SDF granularity;

A transmitter configured to send the backflow data carrying the charging identifier to the PCEF entity, so that the PCEF entity calculates the uplink data packet based on SDF granularity based on the backflow data carrying the charging identifier. Fee results are adjusted.

83. A policy and charging execution PCEF entity, characterized by including:

A receiver configured to receive backflow data carrying a charging identifier sent by the service detection function TDF entity after charging uplink data packets based on the service data flow SDF granularity. The backflow data is determined by the TDF entity. Data packets in the uplink data packet that affect the SDF granularity-based charging result of the PCEF entity for the uplink data packet;

A processor, configured to determine that the data received by the receiver is the reflow data according to the charging identification, determine the SDF to which the reflow data belongs, and adjust the charging result of the determined SDF.

84. A policy control and charging rule function PCRF entity, characterized in that it includes: a processor, configured to determine the charging identifier that needs to be allocated to the return data packet, and the return data is Refers to the data packets in the uplink data packet that affect the policy and charging execution PCEF entity’s charging results based on the service data flow SDF granularity of the uplink data packet;

Transmitter, configured to send the charging identifier to the service detection function TDF entity and the PCEF entity, so that the TDF entity determines the return data from the uplink data packet from the PCEF entity. The charging identifier is added to the return data and then sent to the PCEF entity, so that the PCEF entity determines the return data according to the charging identifier and performs the calculation of the uplink data packet based on the return data. The accounting results of SDF granularity are adjusted.