EVENT REPORTING METHOD AND APPARATUS

Abstract

Embodiments of the present invention provide an event reporting method and an apparatus. The method includes: receiving, by a policy and charging rules function PCRF entity, a first message sent by a traffic detection function TDF entity, where the first message includes a start event, and the start event is used to notify the PCRF entity that a data stream starts to be transmitted; sending, by the PCRF entity, a second message to a PCEF entity or the TDF entity, where the second message is used by the PCEF entity or the TDF entity to send a stop event to the PCRF entity, and the stop event is used to notify the PCRF entity that the transmission of the data stream stops; and receiving, by the PCRF entity, the stop event sent by the PCEF entity or the TDF entity.

Claims

1. An event reporting method, comprising: receiving, by a policy and charging rules function (PCRF) entity, a first message from a traffic detection function (TDF) entity, wherein the first message comprises a start event, and the start event is used to notify the PCRF entity that a data stream starts to be transmitted; sending, by the PCRF entity, a second message to a policy and charging enforcement function (PCEF) entity or the TDF entity, wherein the second message is used by the PCEF entity or the TDF entity to send a stop event to the PCRF entity, and the stop event is used to notify the PCRF entity that the transmission of the data stream stops; and receiving, by the PCRF entity, the stop event from the PCEF entity or the TDF entity.

2. The method according to claim 1, wherein the first message further comprises 5-tuple information of the data stream; and the sending, by the PCRF entity, a second message to the PCEF entity or the TDF entity comprises: sending, by the PCRF entity, a reporting instruction of the stop event and the 5-tuple information of the data stream to the PCEF entity, wherein the 5-tuple information of the data stream is used by the PCEF entity to detect the data stream, and the reporting instruction of the stop event is used to instruct the PCEF entity to send the stop event to the PCRF entity when the transmission of the data stream stops.

3. The method according to claim 1, wherein the sending, by the PCRF entity, a second message to the PCEF entity or the TDF entity comprises: sending, by the PCRF entity, an identifier of the data stream and a reporting instruction of the stop event to the TDF entity, wherein the reporting instruction of the stop event is used to instruct the TDF entity to send the stop event to the PCRF entity when the transmission of the data stream stops; and the method further comprises: sending, by the PCRF entity, a notification to the TDF entity, wherein the notification is used to notify the TDF entity that the reporting instruction of the stop event is valid before the transmission of the data stream stops;.

4. The method according to claim 1, further comprising: sending, by the PCRF entity, modification information and an identifier of a downlink data stream of the data stream to the PCEF entity or the TDF entity, wherein the modification information is used by the PCEF entity or the TDF entity to send the stop event to the PCRF entity when the transmission of the downlink data stream of the data stream stops.

5. The method according to claim 1, further comprising: sending, by the PCRF entity, 5-tuple information of an uplink data stream of the data stream to the PCEF entity or the TDF entity.

6. An event reporting method, comprising: receiving, by a policy and charging enforcement function (PCEF) entity, a message from a policy and charging rules function (PCRF) entity, wherein the message is used by the PCEF entity to send a stop event to the PCRF entity, and the stop event is used to notify the PCRF entity that transmission of the data stream stops; detecting, by the PCEF entity, the data stream based on the message; and when the transmission of the data stream stops, sending, by the PCEF entity, the stop event to the PCRF entity.

7. The method according to claim 6, wherein the message comprises 5-tuple information of the data stream and a reporting instruction of the stop event, and the reporting instruction of the stop event is used to instruct the PCEF entity to send the stop event to the PCRF entity when the transmission of the data stream stops; and the detecting, by the PCEF entity, the data stream based on the message comprises: detecting, by the PCEF entity, a data stream corresponding to the 5-tuple information of the data stream.

8. The method according to claim 6, further comprising: receiving, by the PCEF entity, modification information and an identifier of a downlink data stream of the data stream that are from the PCRF entity, wherein the modification information is used by the PCEF entity to send the stop event to the PCRF entity when the transmission of the downlink data stream of the data stream stops.

9. The method according to claim 6, further comprising: receiving, by the PCEF entity, 5-tuple information of an uplink data stream of the data stream from the PCRF entity.

10. A policy and charging rules function (PCRF) entity comprising: a memory, configured to store computer executable program code; and a processor, coupled to the memory, wherein the program code comprises an instruction, and when the processor executes the instruction, the instruction enables the PCRF entity to perform the following operations: receiving a first message from a traffic detection function (TDF) entity, wherein the first message comprises a start event, and the start event is used to notify the PCRF entity that a data stream starts to be transmitted; sending a second message to a policy and charging enforcement function (PCEF) entity or the TDF entity, wherein the second message is used by the PCEF entity or the TDF entity to send a stop event to the PCRF entity, and the stop event is used to notify the PCRF entity that the transmission of the data stream stops; and receiving the stop event from the PCEF entity or the TDF entity.

11. The PCRF entity according to claim 10, wherein the first message further comprises 5-tuple information of the data stream, the operation of sending a second message comprising: sending a reporting instruction of the stop event and the 5-tuple information of the data stream to the PCEF entity, wherein the 5-tuple information of the data stream is used by the PCEF entity to detect the data stream, and the reporting instruction of the stop event is used to instruct the PCEF entity to send the stop event to the PCRF entity when the transmission of the data stream stops.

12. The PCRF entity according to claim 10, wherein when the processor executes the instruction, the instruction further enables the PCRF entity to further perform the following operations: sending an identifier of the data stream and a reporting instruction of the stop event to the TDF entity, wherein the reporting instruction of the stop event is used to instruct the TDF entity to send the stop event to the PCRF entity when the transmission of the data stream stops; and sending a notification to the TDF entity, wherein the notification is used to notify the TDF entity that the reporting instruction of the stop event is valid before the transmission of the data stream stops.

13. The PCRF entity according to claim 10, wherein when the processor executes the instruction, the instruction further enables the PCRF entity to further perform the following operations: sending modification information and an identifier of a downlink data stream of the data stream to the PCEF entity or the TDF entity, wherein the modification information is used by the PCEF entity or the TDF entity to send the stop event to the PCRF entity when the transmission of the downlink data stream of the data stream stops.

14. The PCRF entity according to claim 13, wherein when the processor executes the instruction, the instruction further enables the PCRF entity to further perform the following operations: sending 5-tuple information of an uplink data stream of the data stream to the PCEF entity or the TDF entity.

15. A policy and charging enforcement function (PCEF) entity comprising: a memory, configured to store computer executable program code; and a processor, coupled to the memory, wherein the program code comprises an instruction, and when the processor executes the instruction, the instruction enables the PCEF entity to perform the following operations: receiving a message from a policy and charging rules function (PCRF) entity, wherein the message is used by the PCEF entity to send a stop event to the PCRF entity, and the stop event is used to notify the PCRF entity that transmission of the data stream stops; detecting the data stream based on the message; and sending the stop event to the PCRF entity when the transmission of the data stream stops.

16. The PCEF entity according to claim 15, wherein the message comprises 5-tuple information of the data stream and a reporting instruction of the stop event, the reporting instruction of the stop event is used to instruct the PCEF entity to send the stop event to the PCRF entity when the transmission of the data stream stops; wherein the operation of detecting the data stream based on the message comprising: detecting a data stream corresponding to the 5-tuple information of the data stream.

17. The PCEF entity according to claim 15, wherein when the processor executes the instruction, the instruction further enables the PCEF entity to perform the following operations: receiving modification information and an identifier of a downlink data stream of the data stream from the PCRF entity, wherein the modification information is used by the PCEF entity to send the stop event to the PCRF entity when the transmission of the downlink data stream of the data stream stops.

18. The method according to claim 15, wherein when the processor executes the instruction, the instruction further enables the PCEF entity to perform the following operations: receiving 5-tuple information that is of an uplink data stream of the data stream from the PCRF entity.

Description

BRIEF DESCRIPTION OF DRAWINGS

[0044] To describe the technical solutions in the embodiments of the present invention more clearly, the following briefly describes the accompanying drawings required for describing the embodiments. Apparently, the accompanying drawings in the following description show merely some embodiments of the present invention, and a person of ordinary skill in the art may derive other drawings from these accompanying drawings without creative efforts.

[0045] FIG. 1 is a schematic diagram of an SAE architecture in the prior art;

[0046] FIG. 2 is a schematic diagram of a PCC architecture according to an embodiment of the present invention;

[0047] FIG. 3 is a schematic diagram of another PCC architecture according to an embodiment of the present invention;

[0048] FIG. 4 is a schematic flowchart of an event reporting method according to an embodiment of the present invention;

[0049] FIG. 5 is a schematic diagram of communication of another event reporting method according to an embodiment of the present invention;

[0050] FIG. 6 is a schematic diagram of communication of still another event reporting method according to an embodiment of the present invention;

[0051] FIG. 7 is a schematic diagram of communication of still another event reporting method according to an embodiment of the present invention;

[0052] FIG. 8A is a schematic structural diagram of a PCRF entity according to an embodiment of the present invention;

[0053] FIG. 8B is a schematic structural diagram of another PCRF entity according to an embodiment of the present invention;

[0054] FIG. 9A is a schematic structural diagram of a PCEF entity according to an embodiment of the present invention;

[0055] FIG. 9B is a schematic structural diagram of another PCEF entity according to an embodiment of the present invention;

[0056] FIG. 10A is a schematic structural diagram of a TDF entity according to an embodiment of the present invention; and

[0057] FIG. 10B is a schematic structural diagram of another TDF entity according to an embodiment of the present invention.

DESCRIPTION OF EMBODIMENTS

[0058] To make the objectives, technical solutions, and advantages of the present invention clearer, the following describes the technical solutions of the embodiments of the present invention with reference to the accompanying drawings.

[0059] In an existing data transmission process, after a data stream starts to be transmitted, a PCRF entity delivers a PCC rule to a PCEF entity. Therefore, after the PCEF entity binds the data stream to a corresponding bearer, the PCRF entity retains the corresponding bearer for the data stream because the PCRF entity cannot learn whether the data stream stops or when to stop. Therefore, even after the transmission of the foregoing data stream stops, the corresponding bearer of the data stream cannot be released, thereby causing a waste of network resources.

[0060] For this purpose, embodiments of the present invention provide an event reporting method and an apparatus, so as to resolve a problem of the waste of the network resources. The method and the apparatus are based on a same inventive concept. Because problem resolving principles of the method and the apparatus are similar, mutual reference may be made to implementations of the method and the apparatus, and no repeated description is provided.

[0061] To clearly describe the solutions in the embodiments of the present invention, a service scenario and a system architecture that may be used in the embodiments of the present invention are described below with reference to FIG. 2 and FIG. 3.

[0062] FIG. 2 shows a possible system architecture according to an embodiment of the present invention. As shown in FIG. 2, a PCC architecture is a part of an SAE architecture, and an overall architecture of the SAE architecture is shown in FIG. 1. Here, for brevity, only the PCC architecture is described. As shown in FIG. 2, the PCC architecture includes a PCRF entity, a PCEF entity, and a traffic detection function (TDF) entity, and the TDF entity may perform application detection and policy execution based on an application detection and control (ADC) rule delivered by the PCRF entity. In the PCC architecture shown in FIG. 1, the PCEF entity and the TDF entity are separately deployed, in other words, the PCEF entity and the TDF entity are deployed in different physical devices. The PCEF entity and the PCRF entity may communicate with each other by using a Gx interface, and the TDF entity and the PCRF entity may communicate with each other by using an Sd interface.

[0063] FIG. 3 shows another possible system architecture according to an embodiment of the present invention. In FIG. 3, for content that is the same as or similar to that in FIG. 2, refer to a detailed description in FIG. 2, and details are not described herein again. Different from the system architecture shown in FIG. 2, in the PCC architecture shown in FIG. 3, a PCEF entity and a TDF entity are deployed in a same physical device, and for ease of description, the same physical device is subsequently referred to as an integrated device. The integrated device integrates functions of the PCEF entity and the TDF entity, and may internally include a separate module that has a PCEF entity function and a separate module that has a TDF entity function, or may not externally present the foregoing separate modules.

[0064] It should be noted that the foregoing PCC architectures shown in FIG. 2 and FIG. 3 may further include another functional entity such as an application function (AF) entity, a bearer binding and event reporting function (BBERF) entity, a subscription profile repository (SPR), an online charging system (OCS), and an offline charging system (OFCS).

[0065] It may be understood that the network architecture and the service scenario described in the embodiments of the present invention are intended to describe the technical solutions in the embodiments of the present invention more clearly, and impose no limitation on the technical solutions provided in the embodiments of the present invention. A person of ordinary skill in the art may know that, with evolution of the network architecture and emergence of a new service scenario, the technical solutions provided in the embodiments of the present invention are also applicable to a similar technical problem.

[0066] Based on foregoing common aspects included in the embodiments of the present invention, the following further describes the embodiments of the present invention in detail.

[0067] An embodiment of the present invention provides an event reporting method, an apparatus based on the method, such as a PCRF entity, a PCEF entity, and a TDF entity, and a system based on the method. As shown in FIG. 4, the method may include steps 401 to 403, and step 402 may be performed after step 401, or may be performed before step 401. In step 401, a PCRF entity receives a first message sent by a TDF entity, where the first message includes a start event, and the start event is used to notify the PCRF entity that a data stream starts to be transmitted. In step 402, the PCRF entity sends a second message to a PCEF entity or a TDF entity, where the second message is used by the PCEF entity or the TDF entity to send a stop event to the PCRF entity, and the stop event is used to notify the PCRF entity that the transmission of the data stream stops. For example, when the first message further includes 5-tuple information of the data stream, the second message may include a reporting instruction of the stop event and the 5-tuple information, and the PCRF entity may deliver, to the PCEF entity, a rule that includes the reporting instruction of the stop event and the 5-tuple information, so that the PCEF entity may detect the data stream based on the 5-tuple information in the rule. For example, the rule may be a PCC rule. When the transmission of the data stream stops, the PCEF entity may send the stop event to the PCRF entity. For another example, the second message may include the reporting instruction of the stop event. Before receiving the message sent by the TDF entity, the PCRF entity may deliver another rule such as an ADC rule to the TDF entity, and the another rule may include a reporting instruction of the start event, an identifier used to identify the data stream, and the reporting instruction of the stop event. When sending the another rule, the PCRF entity may further notify the TDF entity that the reporting instruction of the stop event is valid before the transmission of the data stream stops, for example, may notify the TDF entity by using the another rule, or may notify the TDF entity in another manner, so that the TDF entity may continue to detect the data stream based on the identifier after sending the start event to the PCRF entity, and send the stop event to the PCRF entity when the transmission of the data stream stops. Correspondingly, after receiving the second message, the PCEF entity or the TDF entity detects the data stream based on the second message. When the transmission of the data stream stops, the PCEF entity or the TDF entity sends the stop event to the PCRF entity. In step 403, the PCRF entity receives the stop event sent by the PCEF entity or the TDF entity. Before the transmission of the data stream stops, the PCRF entity may further enable, in any manner, the PCEF entity or the TDF entity to send the stop event to the PCRF entity when transmission of a downlink data stream of the data stream stops. Further, after receiving the stop event, the PCRF entity may further unbind the data stream from a corresponding bearer.

[0068] Compared with the prior art, in the solutions provided in the embodiments of the present invention, the PCRF entity sends the second message to the PCEF entity or the TDF entity, where the second message is used by the PCEF entity or the TDF entity to send the stop event to the PCRF entity, so that the PCRF entity can receive, after receiving the start event and learning that the data stream starts to be transmitted, the stop event to learn that the transmission of the data stream stops. Therefore, after the transmission of the data stream stops, the PCRF entity may unbind the data stream from the corresponding bearer to release the bearer, reducing a waste of network resources.

[0069] The following further describes the solutions provided in the embodiments of the present invention with reference to FIG. 5 to FIG. 7.

[0070] FIG. 5 is a schematic diagram of communication of another event reporting method according to an embodiment of the present invention. As shown in FIG. 5, the event reporting method may include steps 501 to 506.

[0071] In step 501, a PCRF entity delivers a first rule to a TDF entity.

[0072] The first rule includes an identifier and a reporting instruction of the start event. The start event is used to notify the PCRF entity that a data stream starts to be transmitted, and the identifier is used to identify the data stream. For example, the identifier may be an application identifier. The first rule may be an ADC rule.

[0073] For example, the first rule may further include a reporting instruction of a stop event, and the stop event is used to notify the PCRF entity that the transmission of the data stream stops. The first rule that includes the identifier and the reporting instruction of the start event is delivered to the TDF entity, so that the TDF entity may detect, in a timely manner, whether the data stream corresponding to the identifier starts to be transmitted, and report the start event to the PCRF when detecting that the data stream corresponding to the identifier starts to be transmitted. Therefore, the PCRF entity may learn, in a timely manner, that the data stream starts to be transmitted.

[0074] In step 502, the TDF detects a data stream corresponding to the identifier.

[0075] After receiving the first rule, the TDF entity detects, based on the reporting instruction of the start event, the data stream identified by the identifier, and performs step 503 when detecting that the data stream identified by the identifier starts to be transmitted.

[0076] In step 503, the TDF entity sends a first message to the PCRF entity, where the first message includes a start event.

[0077] For example, the first message further includes 5-tuple information of the data stream. The 5-tuple information includes five pieces of information: a source IP address, a source port, a destination IP address, a destination port, and a transport layer protocol. For example, a 5-tuple includes 192.168.1.1, 10000, TCP, 121.14.88.76, and 80.

[0078] In step 504, the PCRF entity delivers a second rule to a PCEF entity.

[0079] After receiving the start event, the PCRF entity learns that the data stream starts to be transmitted, and generates the second rule. For example, the second rule may be a PCC rule. The second rule includes the reporting instruction of the stop event and the 5-tuple information.

[0080] For example, the second rule may further include a quality of service policy or a charging policy of the data stream, or the like. Then correspondingly, after receiving the second rule, the PCEF may bind, based on the quality of service policy in the second rule, the data stream corresponding to the 5-tuple information to a corresponding bearer, or perform, based on the charging policy in the second rule, charging on the data stream corresponding to the 5-tuple information.

[0081] In step 505, the PCEF entity detects a data stream corresponding to the 5-tuple information.

[0082] After receiving the reporting instruction of the stop event, the PCEF entity detects the corresponding data stream based on the 5-tuple information, and performs step 506 when detecting that the transmission of the data stream identified by the 5-tuple information stops.

[0083] In step 506, the PCEF entity sends a stop event to the PCRF entity.

[0084] By performing steps 504 to 506, the PCRF entity may learn, based on the stop event reported by the PCEF entity, that the transmission of the data stream stops. Therefore, even if the first rule does not include the reporting instruction of the stop event, the PCRF entity can also learn, in a timely manner, that the transmission of the data stream stops.

[0085] In an existing procedure, after the first rule (such as the ADC rule) is delivered, if the PCRF entity sends the second rule (such as the PCC rule) to the PCEF entity, the first rule is no longer executed. To be specific, the TDF entity does not detect whether the data stream stops, and does not report the stop event to the PCRF entity. However, in the solution shown in FIG. 5, by performing steps 504 to 506, the reporting instruction of the stop event is added to the second rule sent by the PCRF entity to the PCEF entity, so that after receiving the second rule, the PCEF entity may detect whether the data stream stops, and report the stop event to the PCRF entity when the data stream stops. Therefore, the PCRF entity may learn, in a timely manner, that the transmission of the data stream has stopped, and perform a subsequent operation related to unbinding the bearer.

[0086] FIG. 6 is a schematic diagram of communication of still another event reporting method according to an embodiment of the present invention. In the method shown in FIG. 6, for content that is the same as or similar to that of the method shown in FIG. 3 or FIG. 5, refer to a detailed description in FIG. 3 or FIG. 5, and details are not described herein again. As shown in FIG. 6, the event reporting method may include steps 601 to 604.

[0087] In step 601, a PCRF entity delivers a third rule to a TDF entity.

[0088] The third rule includes an identifier, a reporting instruction of a start event, and a reporting instruction of a stop event, and the identifier is used to identify a data stream. For example, the identifier may be an application identifier. The third rule may be an ADC rule.

[0089] In step 602, the TDF entity detects a data stream corresponding to the identifier.

[0090] After receiving the third rule, the TDF entity detects the data stream identified by the identifier. When it is detected that the data stream identified by the identifier starts to be transmitted, step 603 is performed. When it is detected that the transmission of the data stream identified by the identifier stops, step 604 is performed.

[0091] For example, the third rule further includes a notification, and the notification is used to notify the TDF entity that the reporting instruction of the stop event is valid before the transmission of the data stream stops. For example, after receiving the third rule, the TDF entity may configure the reporting instruction of the stop event to take effect after the TDF entity sends the start event to the PCRF entity, and remain valid until the transmission of the data stream stops; or after the third rule is delivered, the reporting instruction of the stop event is always valid until the transmission of the data stream stops.

[0092] For another example, the PCRF entity may not add the notification to the third rule, but sends the notification to the TDF entity in another manner after the third rule is delivered. A specific implementation is not limited.

[0093] For another example, the TDF entity configures a rule in which the reporting instruction of the stop event is valid before the transmission of the data stream stops. To be specific, after the TDF entity receives the third rule, the reporting instruction of the stop event in the third rule starts to take effect after the TDF entity sends the start event to the PCRF entity, and is valid until the transmission of the data stream stops.

[0094] In step 603, the TDF entity sends a first message to the PCRF entity, where the first message includes a start event.

[0095] For example, after receiving the first message sent by the TDF entity, the PCRF entity may formulate a PCC rule, and deliver the PCC rule to a PCEF entity. The PCC rule may further include 5-tuple information of the data stream, a quality of service policy or a charging policy, and the like. Correspondingly, after receiving the PCC rule, the PCEF entity may bind, based on the quality of service policy in the PCC rule, the data stream corresponding to the 5-tuple information to a corresponding bearer, or perform, based on the charging policy in the PCC rule, charging on the data stream corresponding to the 5-tuple information.

[0096] In step 604, the TDF entity sends a stop event to the PCRF entity.

[0097] In an existing procedure, when the ADC rule includes the reporting instruction of the stop event, if the PCRF entity sends the PCC rule to the PCEF entity, the reporting instruction of the stop event in the ADC rule is invalid. To be specific, the TDF entity does not detect whether the data stream stops, and does not report the stop event to the PCRF entity. However, in the solution shown in FIG. 6, the PCRF entity notifies the TDF entity that the reporting instruction of the stop event is valid before the transmission of the data stream stops, so that before the transmission of the data stream stops, the TDF entity keeps detecting whether the data stream stops, and sends the stop event to the PCRF when detecting that the data stream stops. Therefore, the PCRF entity may learn, in a timely manner, that the transmission of the data stream has stopped, and perform a subsequent operation related to unbinding the bearer. In addition, by using the solution shown in FIG. 6, the PCRF entity does not need to additionally send the reporting instruction of the stop event, so that a network transmission resource is saved and a change to the existing procedure is relatively slight.

[0098] FIG. 7 is a schematic diagram of communication of still another event reporting method according to an embodiment of the present invention. As shown in FIG. 7, the event reporting method may include steps 701 to 706.

[0099] In step 701, a PCRF entity delivers a third rule to a TDF entity.

[0100] Step 701 is similar to step 601 in FIG. 6. For details, refer to a description of step 601 in FIG. 6. Details are not described herein again.

[0101] In step 702, the TDF entity detects a data stream corresponding to an identifier.

[0102] Step 702 is similar to step 602 in FIG. 6. For details, refer to a description of step 602 in FIG. 6. Details are not described herein again.

[0103] After receiving the third rule, the TDF entity detects the data stream identified by the identifier. When it is detected that the data stream identified by the identifier starts to be transmitted, step 703 is performed.

[0104] In step 703, the TDF entity sends a first message to the PCRF entity, where the message includes a start event.

[0105] Step 703 is similar to step 603 in FIG. 6. For details, refer to a description of step 603 in FIG. 6. Details are not described herein again.

[0106] For example, the first message further includes 5-tuple information of an uplink data stream of the data stream.

[0107] In step 704, the PCRF entity sends a fourth rule to a PCEF entity.

[0108] The fourth rule includes at least one of the 5-tuple information of the uplink data stream of the data stream and a quality of service policy of the uplink data stream of the data stream. The fourth rule may be a PCC rule.

[0109] For example, after receiving the fourth rule, the PCEF entity may bind, based on the quality of service policy in the fourth rule, the uplink data stream corresponding to the 5-tuple information to a corresponding bearer, for example, generate a traffic flow template (TFT), and notify a terminal device, and the terminal device binds the bearer of the uplink data stream.

[0110] In step 705, the PCRF entity sends modification information to the TDF entity.

[0111] The modification information is used by the TDF entity to send the stop event to the PCRF entity when transmission of a downlink data stream of the data stream stops. It may be understood that a manner of sending the modification information herein is merely used as an example, and the PCRF entity may also enable, by sending other information or in any another manner, the TDF entity to send the stop event to the PCRF entity when the transmission of the downlink data stream of the data stream stops.

[0112] In step 706, the TDF entity sends a stop event to the PCRF entity.

[0113] When detecting that the transmission of the downlink data stream of the data stream stops, the TDF entity sends the stop event to the PCRF entity.

[0114] For example, the TDF entity detects a data stream corresponding to a particular application, and the data stream corresponding to the application includes only a downlink data stream or the application has a small amount of data transmitted in an uplink direction. When detecting that the transmission of the downlink data stream corresponding to the application stops, the TDF entity may consider that data transmission corresponding to the application has ended and therefore send the stop event to the PCRF entity.

[0115] In the solution shown in FIG. 7, there is no limitation on an execution sequence of step 704 and step 705. Step 704 may be performed before step 705, or step 705 may be performed before step 704, or step 704 and step 705 may be performed at the same time. In an actual application, in some cases, in a process of using the application by a user, there is only the downlink data stream, for example, watching a video and browsing news. Therefore, when it is detected that the downlink data stream stops, it may be considered that both an uplink data stream and the downlink data stream have stopped. By performing steps 705 and 706, the PCRF entity may enable the TDF entity to only detect whether the transmission of the downlink data stream stops, and does not need to detect whether the transmission of the uplink data stream stops. When detecting that the transmission of the downlink data stream stops, the TDF entity reports the stop event to the PCRF entity, so that the PCRF entity can more quickly learn whether the transmission of the data stream stops, saving a CPU resource of the TDF entity.

[0116] It should be noted that in the solution shown in FIG. 7, when receiving the start event, the PCRF entity may separately process uplink and downlink data streams of the data stream. To be specific, a related operation of the uplink data stream is performed by the PCEF entity by performing step 704, and a related operation of the downlink data stream is performed by the TDF entity by performing step 705. In this manner of separately processing the uplink and downlink data streams, CPU resources of the TDF entity and the PCEF entity can be saved, a change to an existing procedure is relatively slight, and an existing device does not need to be changed.

[0117] It should be noted that the methods described in FIG. 4 to FIG. 7 may be applicable to the architecture shown in FIG. 2 or FIG. 3. When the methods described in FIG. 4 to FIG. 7 are applicable to the architecture shown in FIG. 2, the PCRF entity, the TDF entity, and the PCEF entity in FIG. 2 may correspondingly perform respective functions. When the methods described in FIG. 4 to FIG. 7 are applicable to the architecture shown in FIG. 3, the PCRF entity in FIG. 3 may correspondingly perform a respective function, and functions corresponding to the TDF entity and the PCEF entity in the method example may be implemented by an integrated device.

[0118] The foregoing mainly describes the solutions provided in the embodiments of the present invention from a perspective of interaction between network elements. It may be understood that, to implement the foregoing functions, each network element, such as the PCRF entity, the PCEF entity, and the TDF entity, includes a corresponding hardware structure and/or software module for performing each function. A person skilled in the art should be easily aware that, with reference to units and algorithm steps in the examples described in the embodiments provided in this specification, the present invention can be implemented in a form of hardware or a combination of hardware and computer software. Whether a function is performed by hardware or hardware driven by computer software depends on particular applications and design constraints of the technical solutions. A person skilled in the art may use different methods to perform the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of the present invention.

[0119] In the embodiments of the present invention, division of functional units may be performed on the PCRF entity, the PCEF entity, and the TDF entity based on the foregoing method examples. For example, each functional unit may be obtained through division based on a corresponding function, or two or more functions may be integrated into one processing unit. The integrated unit may be implemented in a form of hardware, or may be implemented in a form of a software functional unit. It should be noted that the unit division in the embodiments of the present invention is an example, and is only logical function division. There may be another division manner in an actual implementation.

[0120] When an integrated unit is used, FIG. 8A shows a possible schematic structural diagram of a PCRF entity in the foregoing embodiments. A PCRF entity 800 includes a processing unit 802 and a communications unit 803. The processing unit 802 is configured to control and manage an action of the PCRF entity. For example, the processing unit 802 is configured to support the PCRF entity in performing steps 401, 402, and 403 in FIG. 4, steps 501 and 504 in FIG. 5, a step 601 in FIG. 6, steps 701, 704, and 705 in FIG. 7, and/or another procedure used for the technology described in this specification. The communications unit 803 is configured to support the PCRF entity in communicating with another network entity, for example, communicating with the functional module or the network entity shown in FIG. 1, FIG. 2, or FIG. 3. The PCRF entity may further include a storage unit 801, configured to store program code and data of the PCRF entity.

[0121] The processing unit 802 may be a processor or a controller, for example, may be a central processing unit (CPU), a general purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The processing unit 802 may implement or execute various example logical blocks, modules, and circuits described with reference to content provided in the present invention. The processor may also be a combination of processors performing a computing function, for example, one microprocessor or a combination of more than one microprocessor, or a combination of the DSP and a microprocessor. The communications unit 803 may be a transceiver, a transceiver circuit, a communications interface, or the like. The storage unit 801 may be a memory.

[0122] When the processing unit 802 is the processor, the communications unit 803 is the transceiver, and the storage unit 801 is the memory, the PCRF entity provided in this embodiment of the present invention may be a PCRF entity shown in FIG. 8B.

[0123] Referring to FIG. 8B, a PCRF entity 810 includes a processor 812, a transceiver 813, a memory 811, and a bus 814. The transceiver 813, the processor 812, and the memory 811 are interconnected by using the bus 814. The bus 814 may be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, or the like. The bus 814 may be classified into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used in FIG. 8B for representation, but it does not indicate that there is only one bus or one type of bus.

[0124] When an integrated unit is used, FIG. 9A shows a possible schematic structural diagram of a PCEF entity in the foregoing embodiments. A PCEF entity 900 includes a processing unit 902 and a communications unit 903. The processing unit 902 is configured to control and manage an action of the PCEF entity. For example, the processing unit 902 is configured to support the PCEF entity in performing steps 505 and 506 in FIG. 5, and/or another procedure used for the technology described in this specification. The communications unit 903 is configured to support the PCEF entity in communicating with another network entity, for example, communicating with the functional module or the network entity shown in FIG. 1, FIG. 2, or FIG. 3. The PCEF entity may further include a storage unit 901, configured to store program code and data of the PCEF entity.

[0125] The processing unit 902 may be a processor or a controller, for example, may be a central processing unit (CPU), a general purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The processing unit 902 may implement or execute various example logical blocks, modules, and circuits described with reference to content provided in the present invention. The processor may also be a combination of processors performing a computing function, for example, one microprocessor or a combination of more than one microprocessor, or a combination of the DSP and a microprocessor. The communications unit 903 may be a transceiver, a transceiver circuit, a communications interface, or the like. The storage unit 901 may be a memory.

[0126] When the processing unit 902 is the processor, the communications unit 903 is the transceiver, and the storage unit 901 is the memory, the PCEF entity provided in this embodiment of the present invention may be a PCEF entity shown in FIG. 9B.

[0127] Referring to FIG. 9B, a PCEF entity 910 includes a processor 912, a transceiver 913, a memory 911, and a bus 914. The transceiver 913, the processor 912, and the memory 911 are interconnected by using the bus 914. The bus 914 may be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, or the like. The bus 914 may be classified into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used in FIG. 9B for representation, but it does not indicate that there is only one bus or one type of bus.

[0128] When an integrated unit is used, FIG. 10A shows a possible schematic structural diagram of a TDF entity in the foregoing embodiments. A TDF entity 1000 includes a processing unit 1002 and a communications unit 1003. The processing unit 1002 is configured to control and manage an action of the TDF entity. For example, the processing unit 1002 is configured to support the TDF entity in performing steps 502 and 503 in FIG. 5, steps 602, 603, and 604 in FIG. 6, steps 702, 703, and 706 in FIG. 7, and/or another procedure used for the technology described in this specification. The communications unit 1003 is configured to support the TDF entity in communicating with another network entity, for example, communicating with the functional module or the network entity shown in FIG. 1, FIG. 2, or FIG. 3. The TDF entity may further include a storage unit 1001, configured to store program code and data of the TDF entity.

[0129] The processing unit 1002 may be a processor or a controller, for example, may be a central processing unit (CPU), a general purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The processing unit 1002 may implement or execute various example logical blocks, modules, and circuits described with reference to content provided in the present invention. The processor may also be a combination of processors performing a computing function, for example, one microprocessor or a combination of more than one microprocessor, or a combination of the DSP and a microprocessor. The communications unit 1003 may be a transceiver, a transceiver circuit, a communications interface, or the like. The storage unit 1001 may be a memory.

[0130] When the processing unit 1002 is the processor, the communications unit 1003 is the transceiver, and the storage unit 1001 is the memory, the TDF entity provided in this embodiment of the present invention may be a TDF entity shown in FIG. 10B.

[0131] Referring to FIG. 10B, a TDF entity 1010 includes a processor 1012, a transceiver 1013, a memory 1011, and a bus 1014. The transceiver 1013, the processor 1012, and the memory 1011 are interconnected by using the bus 1014. The bus 1014 may be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, or the like. The bus 1014 may be classified into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used to represent the bus in FIG. 10B, but this does not indicate that there is only one bus or only one type of bus.

[0132] It should be noted that when functions of the TDF entity and the PCEF entity are integrated into an integrated device, a structure of the integrated device may be shown in FIG. 9A, FIG. 9B, FIG. 10A, or FIG. 10B. For a detailed description of the structure of the integrated device, refer to the foregoing detailed description related to the TDF entity or the PCEF entity. Details are not described herein again. For example, when the structure of the integrated device is shown in FIG. 9A, the processing unit included in the integrated device may implement all functions performed by the TDF entity and the PCEF entity.

[0133] Method or algorithm steps described in combination with the content provided in the present invention may be implemented by hardware, or may be implemented by a processor by executing a software instruction. The software instruction may include a corresponding software module. The software module may be stored in a random access memory (RAM), a flash memory, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a register, a hard disk, a mobile hard disk, a compact disc read-only memory (CD-ROM), or any other form of storage medium well-known in the art. For example, a storage medium is coupled to a processor, so that the processor can read information from the storage medium or write information into the storage medium. Certainly, the storage medium may be a component of the processor. The processor and the storage medium may be located in the ASIC. In addition, the ASIC may be located in a core network interface device. Certainly, the processor and the storage medium may exist in the core network interface device as discrete components.

[0134] A person skilled in the art should be aware that in the foregoing one or more examples, functions described in the present invention may be implemented by hardware, software, firmware, or any combination thereof When the present invention is implemented by software, the foregoing functions may be stored in a computer-readable medium or transmitted as one or more instructions or code in the computer-readable medium. The computer-readable medium includes a computer storage medium and a communications medium, where the communications medium includes any medium that enables a computer program to be transmitted from one place to another. The storage medium may be any available medium accessible to a general-purpose or dedicated computer.

[0135] The objectives, technical solutions, and benefits of the present invention are further described in detail in the foregoing specific embodiments. It should be understood that the foregoing descriptions are merely specific embodiments of the present invention, but are not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.