Data usage updating method, apparatus and system

Abstract

Embodiments of the present application provide a data usage updating method, device and system, which can improve the accuracy of data usage statistical results. The method comprises: a user plane function entity receiving a derived data packet of a first downlink data packet from an access network device, wherein the derived data packet is obtained according to the first downlink data packet, and the derived data packet comprises a first identifier; the user plane function entity determining, according to the first identifier, that the first downlink data packet is a discarded data packet; and the user plane function entity sending data usage updating information to a session management entity, wherein the data usage updating information is used to deduct the data usage of the first downlink data packet.

Description

Technical Field

[0001] This application relates to the field of communications, and in particular to methods, apparatus and systems for updating data usage. Background Technology

[0002] Existing Quality of Service (QoS) control mechanisms define aggregation-level QoS parameters, such as User Equipment (UE)-Aggregate Maximum Bit Rate (AMBR), Session AMBR, and Slice Maximum Bit Rate. UE-AMBR controls the aggregate bit rate of all non-guaranteed bit rate (non-GBR) QoS flows of the terminal equipment, and is controlled by the radio access network (RAN) equipment. Session-AMBR controls the aggregate maximum bit rate of all non-GBR QoS flows within a Protocol Data Unit (PDU) session of the terminal equipment, and is controlled by the terminal equipment and the User Plane Function (UPF). Slice Maximum Bit Rate controls the maximum bit rate of all QoS flows within a network slice of the terminal equipment, and is controlled by the terminal equipment, RAN equipment, or UPF.

[0003] In the 5G converged billing standard developed by the 3rd Generation Partnership Project (3GPP) for 5th generation (5G) data networks, RAN equipment can discard downlink data packets based on characteristics such as UE-AMBR or maximum bit rate per slice. In this scenario, existing data usage statistics are inaccurate. Summary of the Invention

[0004] This application provides a data usage update method, apparatus, and system that can improve the accuracy of data usage statistics.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0006] Firstly, a data usage update method is provided. The communication device executing this data usage update method can be a user plane function entity; it can also be a module applied in the user plane function entity, such as a chip or chip system. The following description uses a user plane function entity as the executing entity as an example. The user plane function entity receives a derived data packet from a first downlink data packet from an access network device, wherein the derived data packet is obtained based on the first downlink data packet and includes a first identifier; the user plane function entity determines that the first downlink data packet is a discarded data packet based on the first identifier; the user plane function entity sends data usage update information to a session management entity, wherein the data usage update information is used to deduct the data usage of the first downlink data packet. In this scheme, after the access network device discards the first downlink data packet, the session management entity can obtain the data usage update information, which is used to deduct the data usage information of the first downlink data packet. In other words, in this embodiment, after the access network device discards the downlink data packet, the data usage information of these downlink data packets that have already been statistically analyzed will be deducted. This ensures that the session management entity obtains more accurate data usage information. Furthermore, when the session management entity interacts with the billing function entity, the billing function entity can obtain more accurate data usage information, thereby enabling more accurate billing.

[0007] In one possible implementation, the user plane function entity sends data usage update information to the session management entity, including: the user plane function entity adding a dropped packet flag to the derived data packet; and the user plane function entity reporting the data usage update information to the session management entity according to a first usage reporting rule URR associated with a first packet detection rule (PDR), wherein the first URR is a negative URR, and the first PDR includes packet detection information (PDI) for detecting the dropped packet flag. That is, in this embodiment, the first PDR containing the PDI for detecting the dropped packet flag can be associated with a negative URR. Thus, once the user plane function entity learns that the first data packet is a dropped data packet, it can report the data usage update information to the session management entity according to the negative URR, thereby deducting the data usage information of the first downlink data packet that has already been statistically analyzed.

[0008] In one possible implementation, the user plane function entity sends data usage update information to the session management entity, including: the user plane function entity adding a discard flag to the data packet after discarding the first identifier in the derived data packet; the user plane function entity reporting the data usage update information to the session management entity according to a first URR associated with a first PDR, wherein the first URR is a negative URR, and the first PDR includes a PDI for detecting the discard flag. Thus, once the user plane function entity learns that the first data packet is a discarded data packet, it can report the data usage update information to the session management entity according to the negative URR, thereby deducting the data usage information of the first downlink data packet that has already been counted.

[0009] In one possible implementation, the data usage update method provided in this application embodiment further includes: a user plane function entity receiving a first rule from the session management entity, the first rule including the first PDR and the first URR and second URR associated with the first PDR; wherein the second URR is a positive URR. That is, the first PDR in this application embodiment may be a PDI that adds a packet drop detection flag bit to the existing PDR and is associated with a first URR opposite to the second URR.

[0010] In one possible implementation, the data usage update method provided in this application embodiment further includes: a user plane function entity receiving a second rule from the session management entity, the second rule including the first PDR and the first URR associated with the first PDR, a third PDR and a third URR associated with the third PDR, wherein the third PDR includes a PDI for detecting the first downlink data packet, and the third URR is a positive URR. That is, the first PDR and the first URR associated with the first PDR in this application embodiment are newly added. Meanwhile, the second rule in this application embodiment includes the third PDR and the third URR associated with the third PDR. Specifically, when the third PDR detects the first data packet, it uses the third URR associated with the third PDR for statistical reporting; or, when the first PDR detects a dropped packet flag, it uses the first URR associated with the first PDR for statistical reporting.

[0011] In one possible implementation, the data usage update method provided in this application embodiment further includes: a user plane function entity receiving a subscription message from a session management entity, the subscription message being used to request subscription to data usage change event information. That is, in this application embodiment, the user plane function entity may report data usage update information to the session management entity based on its subscription to the session management entity.

[0012] Secondly, a data usage update method is provided. The communication device executing this data usage update method can be an access network device; it can also be a module applied in the access network device, such as a chip or chip system. The following description uses an access network device as the executing entity as an example. The access network device determines that downlink data packet discarding information needs to be reported; the access network device sends a derived data packet of the discarded first downlink data packet to the user plane function entity, wherein the derived data packet is obtained based on the first downlink data packet, and the derived data packet includes a first identifier, which is used to indicate that the first downlink data packet is a discarded data packet. In this scheme, after discarding the first downlink data packet, the access network device sends a derived data packet of the discarded first downlink data packet to the user plane function entity, and the derived data packet includes the first identifier. Then, based on the first identifier, the user plane function entity can determine that the first downlink data packet is a discarded data packet, and sends data usage update information to the session management entity, thereby allowing the session management entity to obtain the data usage update information, which is used to deduct the data usage information of the first downlink data packet. In other words, in this embodiment of the application, after the access network device discards downlink data packets, the data usage information of these downlink data packets that have already been statistically analyzed will be deducted. This ensures that the session management entity obtains more accurate data usage information. Furthermore, when the session management entity interacts with the billing function entity, the billing function entity can obtain more accurate data usage information, thereby enabling more accurate billing.

[0013] In one possible implementation, the access network device determines that it needs to report downlink data packet drop information, including: the access network device determines that it needs to report downlink data packet drop information based on first indication information from a session management entity, the first indication information indicating that it needs to report downlink data packet drop information. Based on this scheme, the access network device can determine that it needs to report downlink data packet drop information.

[0014] In one possible implementation, the access network device determines whether downlink data packet drop information needs to be reported, including: the access network device determines whether downlink data packet drop information needs to be reported based on its local configuration. Based on this scheme, the access network device can determine whether downlink data packet drop information needs to be reported.

[0015] Thirdly, a data usage update method is provided. The communication device executing this data usage update method can be a session management entity; it can also be a module applied to the session management entity, such as a chip or chip system. The following description uses a session management entity as the executing entity as an example. The session management entity determines that downlink data packet drop information needs to be reported; the session management entity sends a first message to the access network device, the first message including second indication information indicating that downlink data packet drop information needs to be reported; the session management entity receives a second message from the access network device, the second message including information about a billing object and downlink data packet drop information corresponding to the billing object; the session management entity updates the data usage information of the billing object based on the information about the billing object and the downlink data packet drop information corresponding to the billing object, wherein the updated data usage information deducts the data usage information of the billing object for the discarded downlink data packets. Based on this scheme, it can be seen that after the access network device discards the downlink data packets of the billing object, the session management entity can obtain the updated data usage information, and the updated data usage information deducts the data usage information of the billing object for the discarded downlink data packets. In other words, in this embodiment of the application, after the access network device discards downlink data packets containing billing objects, the data usage information of these already billed downlink data packets will be deducted. This ensures that the session management entity obtains more accurate data usage information for the billing objects. Furthermore, when the session management entity interacts with the billing function entity, the billing function entity can obtain more accurate data usage information for the billing objects, thereby enabling more accurate billing for the billing objects.

[0016] In one possible implementation, the first message includes the flow identifier of the first QoS flow; the billing object is the first QoS flow, and the information of the billing object is the flow identifier of the first QoS flow. Based on this scheme, more accurate data usage information statistics at the QoS flow granularity can be achieved, thereby enabling more accurate billing at the QoS flow granularity.

[0017] In one possible implementation, the first QoS flow is a QoS flow bound to a first charging policy rule. The binding parameters of the first charging policy rule include first charging identification information, which is used to identify the corresponding charging policy. That is, in this embodiment, charging identification information can be used as the binding parameter of the first charging policy rule.

[0018] In one possible implementation, the second indication information is first billing identification information, which is used to identify the corresponding billing policy; the billing object is one or more QoS flows to which the billing policy rule containing the first billing identification information is bound in the binding parameters; and the information of the billing object is the first billing identification information. Based on this scheme, more accurate data usage information statistics at the granularity of billing identification information can be achieved, thereby achieving more accurate billing at the granularity of billing identification information.

[0019] In one possible implementation, the first message is also used to indicate that the discard information includes the value of the discarded traffic or the number of discarded packets.

[0020] In one possible implementation, the session management entity determines that downlink packet drop information needs to be reported, including: the session management entity determines that downlink packet drop information needs to be reported based on third indication information from the policy control entity, wherein the third indication information indicates that downlink packet drop information needs to be reported. Based on this scheme, the session management entity can determine that downlink packet drop information needs to be reported.

[0021] In one possible implementation, the session management entity determines whether downlink packet drop information needs to be reported, including: the session management entity determines whether downlink packet drop information needs to be reported based on its local configuration. Based on this scheme, the session management entity can determine whether downlink packet drop information needs to be reported.

[0022] Fourthly, a data usage update method is provided. The communication device executing this data usage update method can be an access network device; it can also be a module applied in the access network device, such as a chip or chip system. The following description uses an access network device as the executing entity as an example. The access network device receives a first message from a session management entity, the first message including second indication information; the second indication information indicates that downlink data packet discarding information needs to be reported; the access network device determines the downlink data packet discarding information of the billing object according to the second indication information; the access network device sends a second message to the session management entity, the second message including the information of the billing object and the downlink data packet discarding information corresponding to the billing object. Based on this scheme, it can be seen that after discarding the downlink data packet of the billing object, the access network device can send the information of the billing object and the downlink data packet discarding information corresponding to the billing object to the session management entity. Thus, the session management entity can obtain updated data usage information based on the information of the billing object and the downlink data packet discarding information corresponding to the billing object, and the updated data usage information deducts the data usage information of the billing object for the discarded downlink data packets. In other words, in this embodiment of the application, after the access network device discards downlink data packets containing billing objects, the data usage information of these already billed downlink data packets will be deducted. This ensures that the session management entity obtains more accurate data usage information for the billing objects. Furthermore, when the session management entity interacts with the billing function entity, the billing function entity can obtain more accurate data usage information for the billing objects, thereby enabling more accurate billing for the billing objects.

[0023] In one possible implementation, the first message includes a flow identifier for a first QoS flow; the billing object is the first QoS flow, and the information of the billing object is the flow identifier of the first QoS flow. Based on this scheme, more accurate data usage information statistics at the QoS flow granularity can be achieved, thereby enabling more accurate billing at the QoS flow granularity.

[0024] In one possible implementation, the first QoS flow is a QoS flow bound to a first charging policy rule. The binding parameters of the first charging policy rule include first charging identification information, which is used to identify the corresponding charging policy. That is, in this embodiment, charging identification information can be used as the binding parameter of the first charging policy rule.

[0025] In one possible implementation, the second indication information is the first billing identification information, which is used to identify the corresponding billing policy; the billing object is one or more QoS flows bound to different billing policy rules containing the first billing identification information in the binding parameters; and the information of the billing object is the first billing identification information. Based on this scheme, more accurate data usage information statistics at the granularity of the billing identification information can be achieved, thereby enabling more accurate billing at the granularity of the billing identification information.

[0026] In one possible implementation, the first message is also used to indicate that the discard information includes the value of the discarded traffic or the number of discarded packets.

[0027] Fifthly, a data usage update method is provided. The communication device executing this data usage update method can be a session management entity; it can also be a module applied in the session management entity, such as a chip or chip system. The following description uses a session management entity as the executing entity as an example. The session management entity receives a third message from an access network device. The third message includes first billing identification information and first downlink data packet discarding information. The first downlink data packet is a downlink data packet containing the first billing identification information. The session management entity updates the data usage information of the first downlink data packet according to the first billing identification information and the first downlink data packet discarding information. In the updated data usage information, the data usage information of the discarded first downlink data packet is deducted. Based on this scheme, after the access network device discards the first downlink data packet containing the first billing identification information, the session management entity can obtain the updated data usage information, and the data usage information of the first downlink data packet is deducted from the updated data usage information. In other words, in this embodiment, after the access network device discards the first downlink data packet containing the first billing identification information, the data usage information of these billed downlink data packets will be deducted. This ensures that the session management entity obtains more accurate data usage information at the granularity of billing identification information. Furthermore, when the session management entity interacts with the billing function entity, the billing function entity can obtain more accurate data usage information at the granularity of billing identification information, thereby enabling more accurate billing at the granularity of billing identification information.

[0028] In one possible implementation, the data usage update method provided in this application further includes: a session management entity sending a first indication message to an access network device, the first indication message indicating that downlink data packet drop information needs to be reported. Based on this scheme, the access network device can determine that downlink data packet drop information needs to be reported.

[0029] In one possible implementation, the first indication information is the first billing identification information. Based on this scheme, more accurate data usage information statistics at the granularity of billing identification information can be achieved, thereby enabling more accurate billing at the granularity of billing identification information.

[0030] In one possible implementation, the first indication information further indicates that the discard information includes the value of the discarded traffic or the number of discarded data packets.

[0031] In one possible implementation, the data usage update method provided in this application further includes: a session management entity sending a fifth indication message to a user plane entity, the fifth indication message instructing the user plane entity to add charging identification information to the downlink data packet. Based on this scheme, the user plane functional entity can add charging identification information to the downlink data packet, thereby enabling the access network device to perform data usage statistics based on the charging identification information in the downlink data packet.

[0032] Sixthly, a data usage update method is provided. The communication device executing this data usage update method can be an access network device; it can also be a module applied in the access network device, such as a chip or chip system. The following description uses the access network device as the executing entity as an example. The access network device determines that downlink data packet discarding information needs to be reported; the access network device determines the discarding information of a first downlink data packet based on the charging identification information in the received downlink data packet, where the first downlink data packet is a downlink data packet containing the first charging identification information; the access network device sends a third message to a session management entity, the third message including the first charging identification information and the discarding information of the first downlink data packet. Based on this scheme, it can be seen that after discarding the first downlink data packet containing the first charging identification information, the access network device can send the first charging identification information and the discarding information of the first downlink data packet to the session management entity. Thus, the session management entity can obtain updated data usage information based on the first charging identification information and the discarding information of the first downlink data packet, and the data usage information of the first downlink data packet is deducted from the updated data usage information. In other words, in this embodiment, after the access network device discards the first downlink data packet containing the first billing identification information, the data usage information of these already billed downlink data packets will be deducted. This ensures that the session management entity obtains more accurate data usage information at the granularity of the billing identification information. Furthermore, when the session management entity interacts with the billing function entity, the billing function entity can obtain more accurate data usage information at the granularity of the billing identification information, thereby enabling more accurate billing at the granularity of the billing identification information.

[0033] In one possible implementation, the discard information includes the value of the discarded traffic or the number of discarded packets.

[0034] In one possible implementation, the access network device determines that downlink data packet drop information needs to be reported, including: the access network device determines that downlink data packet drop information needs to be reported based on first indication information from a session management entity, wherein the first indication information indicates that downlink data packet drop information needs to be reported. Based on this scheme, the access network device can determine that downlink data packet drop information needs to be reported.

[0035] In one possible implementation, the first indication information is the first billing identification information. Based on this scheme, more accurate data usage information statistics at the granularity of billing identification information can be achieved, thereby enabling more accurate billing at the granularity of billing identification information.

[0036] In one possible implementation, the first indication information also indicates that the discard information includes the value of the discarded traffic or the number of discarded packets.

[0037] In one possible implementation, the access network device determines whether downlink data packet drop information needs to be reported, including: the access network device determines whether downlink data packet drop information needs to be reported based on its local configuration. Based on this scheme, the access network device can determine whether downlink data packet drop information needs to be reported.

[0038] In a seventh aspect, a communication device is provided for implementing the above-described method. The communication device includes modules, units, or means corresponding to the implementation of the above-described method. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above-described functions.

[0039] In one possible implementation, the communication device includes a processing module and a transceiver module. The transceiver module is used to perform message receiving and sending operations on the communication device side as described in any one of the first to sixth aspects above. The processing module is used to invoke instructions to perform message processing or control operations on the communication device side as described in any one of the first to sixth aspects above.

[0040] Eighthly, a communication device is provided, comprising: a processor; the processor being configured to be coupled to a memory, and after reading computer instructions stored in the memory, to execute the method as described in any of the preceding aspects according to the instructions.

[0041] In one possible implementation, the communication device further includes a memory for storing computer instructions.

[0042] In one possible implementation, the communication device further includes a communication interface for communicating with other devices. For example, the communication interface may be a transceiver, an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuitry.

[0043] In one possible implementation, the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or may include chips and other discrete components.

[0044] In one possible implementation, when the communication device is a chip or chip system, the aforementioned communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The aforementioned processor can also be embodied as a processing circuit or logic circuit.

[0045] Ninthly, a computer-readable storage medium is provided that stores instructions which, when executed on a computer, cause the computer to perform the methods described in any of the preceding aspects.

[0046] In a tenth aspect, a computer program product containing instructions is provided, which, when run on a computer, enables the computer to perform the methods described in any of the preceding aspects.

[0047] The technical effects of any possible implementation of aspects seven through ten can be found in the technical effects of different implementations of aspects one, two, three, four, five, or six above, and will not be repeated here.

[0048] Eleventhly, a communication system is provided, comprising a user plane function entity that executes the data usage update method described in the first aspect and an access network device that executes the data usage update method described in the second aspect; or, the communication system comprises a session management entity that executes the data usage update method described in the third aspect and an access network device that executes the data usage update method described in the fourth aspect; or, the communication system comprises a session management entity that executes the data usage update method described in the fifth aspect and an access network device that executes the data usage update method described in the sixth aspect. Attached Figure Description

[0049] Figure 1 This is a schematic diagram of an existing 5G QoS model based on QoS flow.

[0050] Figure 2a A schematic diagram of the service-oriented architecture of existing 5G networks;

[0051] Figure 2b for Figure 2a A schematic diagram of the corresponding reference-point-based 5G network architecture;

[0052] Figure 3 This is a diagram illustrating the existing billing process;

[0053] Figure 4 A flowchart illustrating the network billing process provided in this application embodiment;

[0054] Figure 5 A schematic diagram illustrating the existing relationship between PDR, PDI, and flow.

[0055] Figure 6 A schematic diagram of a communication system architecture provided in an embodiment of this application;

[0056] Figure 7 This is a schematic diagram of another communication system architecture provided in an embodiment of this application;

[0057] Figure 8 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0058] Figure 9 Flowchart of the data usage update method provided in the embodiments of this application Figure 1 ;

[0059] Figure 10a A schematic diagram of the association between PDR and URR provided in the embodiments of this application. Figure 1 ;

[0060] Figure 10b Schematic diagram 2 showing the association between PDR and URR provided for embodiments of this application;

[0061] Figure 11 A schematic flowchart of the data usage update method provided in this application embodiment is shown in Figure 2.

[0062] Figure 12 Flowchart of the data usage update method provided in the embodiments of this application Figure 3 ;

[0063] Figure 13 Interaction illustration of the data usage update method provided in the embodiments of this application Figure 1 ;

[0064] Figure 14 Data transmission illustration provided for embodiments of this application Figure 1 ;

[0065] Figure 15 Schematic diagram 2 of the data transmission provided in the embodiments of this application;

[0066] Figure 16A second interactive schematic diagram of the data usage update method provided in this application embodiment;

[0067] Figure 17 Interaction illustration of the data usage update method provided in the embodiments of this application Figure 3 ;

[0068] Figure 18 Interaction illustration of the data usage update method provided in the embodiments of this application Figure 4 ;

[0069] Figure 19 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0070] To facilitate understanding of the solutions in the embodiments of this application, a brief introduction to the relevant concepts is given below:

[0071] First, PDU session:

[0072] A PDU session is an association between a terminal device and a data network (DN) used to provide a PDU connection service.

[0073] Second, the QoS model:

[0074] In 5G systems, to ensure end-to-end service quality, a 5G QoS model based on QoS flow has been proposed, such as... Figure 1 As shown, this 5G QoS model supports both GBR QoS flows (i.e., GBR QoS flows) and non-GBR QoS flows. Packets controlled by the same QoS flow receive the same transmission processing (such as scheduling or admission thresholds).

[0075] like Figure 1As shown, a terminal device can establish one or more PDU sessions with the 5G network. Each PDU session can establish one or more QoS flows. A QoS flow is identified by a QoS flow identifier (QFI), meaning the QFI uniquely identifies a QoS flow within the session. Specifically, a PDU session corresponds one-to-one with a GPRS tunneling protocol user plane (GTP-U) tunnel between the RAN device and the UPF; a QoS flow corresponds to a radio bearer between the terminal device and the RAN device, and a radio bearer can correspond to one or more QoS flows.

[0076] Whether a QoS flow is a GBR QoS flow or a non-GBR QoS flow is determined by the corresponding QoS profile.

[0077] For GBR QoS flows, the corresponding QoS file includes the following QoS parameters: 5G QoS identifier (5QI), allocation and retention priority (ARP), guaranteed flow bit rate (GFBR), and maximum flow bit rate (MFBR), and optionally, QoS notification control (QNC). Specifically, based on whether the QoS file includes QNC, GBR QoS flows can be divided into GBR QoS flows requiring notification control and GBR QoS flows not requiring notification control. For GBR QoS flows requiring notification control, when the RAN device detects that the corresponding QoS flow resources cannot be satisfied, the RAN device notifies the session management function (SMF) of this event. The SMF can then initiate a QoS flow deletion or modification process. For Non-GBR QoS flows, the corresponding QoS file includes the following QoS parameters: 5QI and ARP; optionally, a reflective QoS attribute (RQA) can be included.

[0078] The definitions of the above QoS parameters are as follows:

[0079] 5QI is a scalar used to index corresponding 5G QoS features. 5QIs are categorized into standardized 5QIs, pre-configured 5QIs, and dynamically allocated 5QIs. Standardized 5QIs correspond one-to-one with a set of standardized 5G QoS feature values; pre-configured 5QIs have their corresponding 5G QoS feature values ​​pre-configured on the radio access network (RAN) equipment; and dynamically allocated 5QIs are sent to the RAN equipment by the core network equipment via a QoS file.

[0080] ARP includes priority levels, preemption capability, and the ability to be preempted.

[0081] GFBR represents the bit rate expected to be provided to the GBR QoS flow.

[0082] MFBR limits the bit rate provided to the GBR QoS flow, i.e., the maximum bit rate provided to the GBR QoS flow. If this bit rate is exceeded, packets can be dropped.

[0083] RQA is used to indicate that services using the corresponding QoS flow should use inverted QoS.

[0084] QNC is used to instruct the RAN device whether to notify the network side when the GFBR cannot meet the requirements during the usage period of the QoS flow.

[0085] In addition to the QoS flow-level QoS parameters mentioned above, 5G systems also introduce aggregation-level QoS parameters, such as UE-AMBR, session-AMBR, and maximum bit rate per slice.

[0086] The UE-AMBR controls the aggregated bit rate of all non-GBR QoS flows of the terminal equipment, and this control is performed by the RAN equipment. For example, the RAN equipment controls the uplink (UL) and downlink (DL) UE-AMBR to perform traffic shaping, such as dropping packets that exceed the limit.

[0087] The session-AMBR controls the aggregated maximum bit rate of all non-GBR QoS flows within a PDU session of an end device, and is controlled by both the end device and the UPF. For example, the end device controls the UL Session-AMBR to perform traffic shaping, such as dropping packets exceeding the limit. The UPF controls both the UL and DL Session-AMBRs to perform traffic shaping, such as dropping packets exceeding the limit.

[0088] The maximum bit rate of a slice controls the maximum bit rate of all QoS flows within a network slice for an end device. This control is performed by the end device, RAN device, or UPF. For example, the RAN device controls the UL and DL slice-MBR to perform traffic shaping, such as dropping packets that exceed the limit.

[0089] Third, the functions related to 5G system architecture and 5G converged billing:

[0090] Figure 2a This diagram illustrates the service-oriented architecture of an existing 5G network. This 5G network includes RAN equipment, UPF, core access and mobility management function (AMF), SMF, authentication server function (AUSF), network slice selection function (NSSF), network exposure function (NEF), network exposure function repository function (NRF), policy control function (PCF), unified data management (UDM), unified data repository (UDR), application function (AF), or charging function (CHF), etc.

[0091] Among them, such as Figure 2aAs shown, the terminal device accesses the 5G network through the RAN device. The terminal device communicates with the AMF through the N1 interface (N1 for short); the RAN device communicates with the AMF through the N2 interface (N2 for short); the RAN device communicates with the UPF through the N3 interface (N3 for short); the SMF communicates with the UP through the N4 interface (N4 for short), and the UPF accesses the data network through the N6 interface (N6 for short). Furthermore, Figure 2a The control plane functions shown, such as AUSF, AMF, SMF, NSSF, NEF, NRF, PCF, UDM, UDR, CHF, or AF, interact using service-oriented interfaces. For example, the service-oriented interface provided by AUSF is Nausf; AMF is Namf; SMF is Nsmf; NSSF is Nnssf; NEF is Nnef; NRF is Nnrf; PCF is Npcf; UDM is Nudm; UDR is Nudr; CHF is Nchf; and AF is Naf. For relevant functional and interface descriptions, please refer to the 5G system architecture diagram in the 23501 standard; they will not be elaborated upon here.

[0092] Figure 2b for Figure 2a A schematic diagram of the corresponding reference-point-based 5G network architecture. (See diagram below.) Figure 2bAs shown, terminal devices access the 5G network through RAN equipment. Terminal devices communicate with the AMF via the N1 interface (N1); the RAN equipment communicates with the AMF via the N2 interface (N2); the RAN equipment communicates with the UPF via the N3 interface (N3); different UPFs communicate with each other via the N9 interface (N9); and the UPF accesses the data network via the N6 interface (N6). Furthermore, the SMF communicates with the UPF via the N4 interface (N4); AMF network elements communicate with the SMF via the N11 interface (N11); and the AMF communicates with the UDM via the N8 interface (N8). The AMF communicates with the AUSF via the N12 interface (N12); the AMF communicates with the PCF via the N15 interface (N15); the AMF communicates with the NSSF via the N22 interface (N22); different AMFs communicate with each other via the N14 interface (N14); the SMF communicates with the PCF via the N7 interface (N7); the SMF communicates with the UDM via the N10 interface (N10); the SMF communicates with the NEF via the N29 interface (N29); S MF communicates with NRF via the Nnrf interface (Nnrf for short); SMF communicates with CHF via the Nchf interface (Nchf for short); PCF communicates with NEF via the N5 interface (N5 for short); UDR communicates with PCF via the N36 interface (N36 for short); UDR communicates with NEF via the N37 interface (N37 for short); UDM communicates with AUSF via the N13 interface (N13 for short); UDM communicates with NRF via the N29 interface (N29 for short).

[0093] exist Figure 2a The 5G network architecture shown or Figure 2b In the 5G network architecture shown, the 5G converged billing-related functions include PCF, SMF, UPF, and CHF. A description of each billing-related function is shown in Table 1.

[0094] Table 1

[0095]

[0096] Fourth, the billing process:

[0097] Existing billing processes such as Figure 3 As shown, it includes the following steps:

[0098] When an S1 / PDU session is created, the SMF requests billing rules from the PCF. The PCF then returns the billing rules to the SMF. The billing rules include the billing granularity and the billing method.

[0099] S2 and SMF select the corresponding CHF according to priority.

[0100] S3, SMF applies for quotas from CHF, CHF returns quotas and billing events to SMF.

[0101] S4 and SMF issue N4 rules to UPF. N4 rules include quota and billing events.

[0102] S5. When a terminal device accesses a service, the UPF parses the packets and performs data usage statistics according to the matched packet detection rule (PDR). When a billing event is met, the UPF reports the data usage information (also known as quota usage information) to the SMF.

[0103] S6 and SMF report data usage information to CHF and apply for new quotas. The subsequent process repeats itself, continuously reporting data usage information and updating new quotas until the user becomes inactive or the balance is insufficient.

[0104] The following sections will explain the billing granularity, billing method, and billing event mentioned above.

[0105] In this embodiment, the billing granularity is used to characterize who is being billed. For terminal devices accessing a 5G network, a PDU session may contain many service flows. In current 5G converged billing, billing can be applied to the entire PDU session or to different service flows within the PDU session separately. For example, the relevant descriptions of different billing granularities are shown in Table 2.

[0106] Table 2

[0107]

[0108] 5G converged billing combines offline and online billing, therefore there are two billing methods: offline billing and online billing. In online billing, the SMF (Service Provider) needs to apply for service quotas and related billing parameters from the CHF (Service Controller) when a billing session is created. In offline billing, the SMF only needs to apply for relevant billing parameters from the CHF when a billing session is created, but does not need to apply for service quotas.

[0109] Billing events, also known as trigger conditions, are events that the CHF subscribes to from the SMF. These events require the SMF to request or report quotas under specified conditions. For example, when the traffic used by a service reaches a specified threshold, the SMF sends a message to the CHF to update the billing session and obtain new quotas. Billing events can be categorized by granularity into PDU session-level (session-level) and service-level (rating group, RG)-level events. PDU session-level events affect all RGs within the PDU session, applying to the entire session. Service-level events only affect the specified service flow within the PDU session, applying to the specified RG. Billing events can also be categorized by reporting method into immediate and deferred reporting. When a billing event occurs, for immediately reported events, the SMF collects the quota usage corresponding to the current billing event and immediately reports it to the CHF. When a billing event occurs, for billing events that are reported late, SMF collects the quota usage corresponding to the current billing event, caches it temporarily, and reports it together when the next billing event that is reported immediately occurs.

[0110] Currently, the SMF (Service Management Function) supports local configuration of whether billing events are enabled and the reporting method, which is used as the default value. The CHF (Service Control Function) can also send billing events to the SMF, and the priority of the sent billing events is higher than the priority of locally configured billing events. The enabling and reporting methods of some billing events are modifiable. In 2G / 3G / 4G networks, most billing events are reported immediately. However, in 5G converged billing, the reporting method of some billing events can be modified. Operators can flexibly formulate the reporting method according to their own services, which can reduce signaling impact. Table 3 describes the relevant information using two billing triggers as examples.

[0111] Table 3

[0112]

[0113] The following example illustrates the network billing process when a user accesses a service.

[0114] Assume terminal device A has opened an account with online billing. It has recharged 100 yuan and subscribed to the following package:

[0115] The basic data package contains 0.1 yuan / MB of ordinary data traffic. The operator stipulates that the corresponding rate group for the basic data package is RG1.

[0116] The targeted data package is 1GB of data for a news reading app for 10 yuan. The operator stipulates that the corresponding rate group for the app's data is RG2.

[0117] Then as Figure 4 As shown, the network billing process includes the following steps:

[0118] S11. After terminal device A is powered on, it requests the SMF to create a PDU session.

[0119] S12 and SMF interact with PCF to obtain the corresponding billing rules based on the user's contract information, including billing granularity and billing method, such as RG1 (online billing) and RG2 (online billing).

[0120] S13. The SMF requests the corresponding quota from the CHF; the CHF checks the account balance, creates the user's call detail record (CDR), and issues the corresponding quota and billing event to the SMF, as follows:

[0121] Basic traffic package: 50MB quota; "Traffic threshold reached" billing event, immediately reported, parameter is 10MB (that is, when the quota is 10MB remaining, the billing event will be triggered).

[0122] Targeted traffic package: quota 30M; "Traffic threshold reached" billing event, report immediately, parameter is 10MB.

[0123] S14, SMF sends the quotas and billing events corresponding to the basic traffic package and the targeted traffic package to UPF together.

[0124] S15. Terminal device A starts browsing news using the APP. UPF parses the business messages, starts the counter, and records the traffic of the APP that is parsed.

[0125] S16. As terminal device A is used, the cumulative message traffic continues to increase. When the targeted traffic packet uses 20MB (with 10MB remaining), the "traffic threshold reached" billing event is triggered, and the UPF reports the data usage information to the SMF.

[0126] S17. SMF reports data usage information to CHF and requests quota updates.

[0127] S18 and CHF store the billing information corresponding to data usage in the corresponding call detail record (CDR) and issue a new 30M quota to SMF, so that SMF can issue a new 30M quota to UPF. During the entire quota update process, UPF continues to charge, and 5M of traffic used during the process needs to be deducted after the new quota is issued.

[0128] The subsequent process is the same as before. As users continue to use the service, UPF and SMF will repeatedly report data usage information and apply for quotas until the user shuts down the service or the balance is insufficient.

[0129] Fifth, binding mechanism:

[0130] The binding mechanism is the process of associating a service data flow (defined in a policy and charging control (PCC) rule by means of the service data flow (SDF) template) with the QoS flow deemed to transport the service data flow. Existing binding mechanisms include the following three steps:

[0131] The first step is session binding, which involves mapping AF sessions to PDU sessions one-to-one. For details, please refer to existing implementation methods, which will not be elaborated here.

[0132] The second step, PCC rule authorization, is performed by the PCF. It authorizes the PCC rules and assigns QoS parameters to them. For details, please refer to the existing implementation methods, which will not be elaborated here.

[0133] The third step is QoS flow binding, which associates a PCC rule with a QoS flow within a PDU session. The binding is performed using the following binding parameters:

[0134] 1. 5QI: For a description of the relevant parameters, please refer to the QoS parameter section above. It will not be repeated here.

[0135] 2. ARP: For a description of ARP, please refer to the QoS parameters section above. It will not be repeated here.

[0136] Alternatively, if the PCC rule includes one or more of the following parameters, then one or more of the following parameters may also be used as binding parameters:

[0137] 3. QNC: For a description of QNC, please refer to the QoS parameters section above. It will not be repeated here.

[0138] 4. Priority: Priority indicates the priority of resource scheduling within a QoS flow. Priority is used to distinguish QoS flows from the same terminal device and also to distinguish QoS flows from different terminal devices.

[0139] 5. Average Window: The average window is only used for GBR QoS flow and represents the duration of calculating GFBR and MFBR.

[0140] 6. MDBV: MDBV represents the maximum amount of data that the 5G access network is required to serve within a packet delay budget (PDB). PDB defines the upper limit of the time delay that can occur when a data packet is transmitted between a terminal device and a UPF network element with an N6 interface.

[0141] Of course, the aforementioned priority, average window, or maximum data burst size can also be parameters in the QoS attributes corresponding to the 5QI mentioned above, and no specific limitations are made here.

[0142] Optionally, in this embodiment of the application, if the PCC rule includes billing identification information, then the billing identification information can be used as a binding parameter. The billing identification information in this embodiment of the application is used to identify the corresponding billing policy, and will not be repeated below.

[0143] It should be noted that in the embodiments of this application, PCC rules with different binding parameter attributes will definitely be bound to different QoS flows. This will be explained uniformly here and will not be repeated below.

[0144] Sixth, N4 interface:

[0145] like Figure 2b As shown, the N4 interface is the interface between the SMF and the UPF. The SMF sends N4 rules containing PDRs to the UPF to execute corresponding controls. Figure 5As shown, the PDR includes a PDR ID, packet detection information (PDI), forwarding action rule (FAR) ID, QoS enforcement rule (QER) ID, and / or usage reporting rule (URR) ID. The FAR ID indicates the FAR, the URR ID indicates the URR, and the QER ID indicates the QER, which are the flow actions associated with the PDR. The PDI contains one or more matching fields. When the corresponding field of the inbound data traffic matches all matching fields in the PDI, the UPF considers the match successful. Furthermore, the UPF can perform operations such as dropping, forwarding, buffering, notifying, or duplicating packets based on the FAR. The UPF can perform QoS operations on packets based on the QER. The UPF can perform usage reporting based on the URR.

[0146] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" are not necessarily different. Meanwhile, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is being used as an example, illustration, or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

[0147] Furthermore, the network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0148] like Figure 6 The diagram illustrates a communication system 60 provided in this embodiment of the application. The communication system 60 includes a user plane function entity 601 and an access network device 602. The user plane function entity 601 and the access network device 602 can communicate directly or via forwarding from other devices; this embodiment does not impose specific limitations on this.

[0149] In one possible implementation, the access network device 602, after determining that downlink data packet discarding information needs to be reported, sends a derived data packet of the discarded first downlink data packet to the user plane function entity 601. This derived data packet is obtained based on the first downlink data packet and includes a first identifier indicating that the first downlink data packet is a discarded data packet. The user plane function entity 601 receives the derived data packet of the first downlink data packet from the access network device 602, and after determining that the first downlink data packet is a discarded data packet based on the first identifier in the derived data packet, sends data usage update information to the session management entity. This data usage update information is used to deduct the data usage information of the first downlink data packet. The specific implementation of this scheme will be described in detail in subsequent method embodiments and will not be repeated here. Based on this scheme, it can be seen that after the access network device discards the first downlink data packet, the session management entity can obtain data usage update information, which is used to deduct the data usage information of the first downlink data packet. In other words, in this embodiment, after the access network device discards the downlink data packet, the data usage information of these downlink data packets that have already been statistically analyzed will be deducted. This ensures that the session management entity obtains more accurate data usage information. Furthermore, when the session management entity interacts with the billing entity, the billing entity can obtain more accurate data usage information, thereby enabling more accurate billing.

[0150] like Figure 7 The diagram illustrates a communication system 70 provided in this embodiment of the application. The communication system 70 includes a session management entity 701 and an access network device 702. The session management entity 701 and the access network device 702 can communicate directly or via forwarding from other devices; this embodiment does not impose specific limitations on this.

[0151] In one possible implementation, session management entity 701, after determining that downlink data packet drop information needs to be reported, sends a first message to access network device 702. The first message includes second indication information, indicating that downlink data packet drop information needs to be reported. Access network device 702 receives the first message from session management entity 701, and after determining the downlink data packet drop information of the billing object based on the second indication information, sends a second message to session management entity 701. The second message includes information about the billing object and the downlink data packet drop information corresponding to the billing object. Session management entity 701 receives the second message from access network device 702, and updates the data usage information of the billing object based on the information about the billing object and the downlink data packet drop information corresponding to the billing object. In the updated data usage information, the data usage information of the billing object for dropped downlink data packets is deducted. The specific implementation of this scheme will be described in detail in subsequent method embodiments and will not be repeated here. Based on this scheme, after the access network device discards downlink data packets containing a billing object, the session management entity can obtain updated data usage information, and the data usage information of the discarded downlink data packets in the billing object is deducted from the updated data usage information. In other words, in this embodiment, after the access network device discards downlink data packets containing a billing object, the data usage information of these billed downlink data packets will be deducted. This ensures that the session management entity obtains more accurate data usage information for the billing object. Furthermore, when the session management entity interacts with the billing function entity, the billing function entity can obtain more accurate data usage information for the billing object, thereby enabling more accurate billing for the billing object.

[0152] In another possible implementation, access network device 702 determines the need to report downlink data packet drop information. After determining the drop information of the first downlink data packet based on the charging identification information in the received downlink data packet, it sends a third message to session management entity 701. The first downlink data packet is a downlink data packet containing the first charging identification information; the third message includes the first charging identification information and the drop information of the first downlink data packet. Session management entity 701 receives the third message from access network device 702 and updates the data usage information of the first downlink data packet based on the first charging identification information and the drop information of the first downlink data packet. In the updated data usage information, the data usage information of the dropped first downlink data packet is deducted. The specific implementation of this scheme will be described in detail in subsequent method embodiments and will not be repeated here. Based on this scheme, after the access network device drops the first downlink data packet containing the first charging identification information, the session management entity can obtain the updated data usage information, and the data usage information of the first downlink data packet is deducted from the updated data usage information. In other words, in this embodiment, after the access network device discards the first downlink data packet containing the first billing identification information, the data usage information of these already billed downlink data packets will be deducted. This ensures that the session management entity obtains more accurate data usage information at the granularity of the billing identification information. Furthermore, when the session management entity interacts with the billing function entity, the billing function entity can obtain more accurate data usage information at the granularity of the billing identification information, thereby enabling more accurate billing at the granularity of the billing identification information.

[0153] Optionally, the access network device in this application embodiment can be any communication device with wireless transceiver capabilities used for communicating with terminal devices. This access network device includes, but is not limited to: evolved node B (eNB), baseband unit (BBU), access point (AP), wireless relay node, wireless backhaul node, transmission point (TP), or TRP in a wireless fidelity (WIFI) system. The access network device can also be a RAN device in a 5G system, which may include, for example, a gNB, TRP, or TP, or one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system. Furthermore, the RAN device can also be a network node constituting a gNB or TP, such as a BBU, or a distributed unit (DU).

[0154] In some deployments, a gNB may include a centralized unit (CU) and a dedicated unit (DU). Additionally, a gNB may include an active antenna unit (AAU). The CU implements some of the gNB's functions, and the DU implements others. For example, the CU handles non-real-time protocols and services, implementing radio resource control (RRC) and packet data convergence protocol (PDCP) layer functions. The DU handles physical layer protocols and real-time services, implementing radio link control (RLC), media access control (MAC), and physical (PHY) layer functions. The AAU implements some physical layer processing functions, radio frequency processing, and active antenna-related functions. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can also be considered as being sent by the DU, or by the DU+AAU. It is understandable that access network equipment can be one or more of the following: CU node, DU node, and AAU node.

[0155] Optional, Figure 6 The communication system 60 shown or Figure 7 The communication system 70 shown can be applied to the 5G network currently under discussion, or to other networks in the future, etc., and this application embodiment does not specifically limit it.

[0156] For example, with Figure 6 The communication system 60 shown or Figure 7 Taking the communication system 70 shown as an example, which can be applied to the currently discussed 5G network, the network element or entity corresponding to the above-mentioned access network equipment can be... Figure 2a or Figure 2b The RAN equipment in the 5G network; the network element or entity corresponding to the aforementioned user plane functional entity can be... Figure 2a or Figure 2b The UPF in the 5G network; the network element or entity corresponding to the aforementioned session management entity can be... Figure 2a or Figure 2b The SMF in the aforementioned 5G network.

[0157] Optionally, the user plane function entity, session management entity, or access network device in the embodiments of this application may also be referred to as a communication device, which may be a general-purpose device or a special-purpose device. The embodiments of this application do not specifically limit this.

[0158] Optionally, the user plane functional entity, session management entity, or related functions of the access network device in the embodiments of this application can be implemented by one device, multiple devices, or one or more functional modules within a device. This application does not specifically limit these implementations. It is understood that the aforementioned functions can be network elements in hardware devices, software functions running on dedicated hardware, a combination of hardware and software, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0159] For example, the user plane function entity, session management entity, or related functions of the access network device in the embodiments of this application can be achieved through... Figure 8 This is achieved through the communication device 800. Figure 8 The diagram shown is a structural schematic of a communication device 800 provided in an embodiment of this application. The communication device 800 includes one or more processors 801, a communication line 802, and at least one communication interface. Figure 8 (This is merely an example illustration of a communication interface 804 and a processor 801; optionally, a memory 803 may also be included.)

[0160] The processor 801 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present application.

[0161] The communication line 802 may include a path for connecting different components.

[0162] The communication interface 804 can be a transceiver module used to communicate with other devices or communication networks, such as Ethernet, RAN, wireless local area networks (WLAN), etc. For example, the transceiver module can be a transceiver or similar device. Optionally, the communication interface 804 can also be a transceiver circuit located within the processor 801, used to implement the processor's signal input and signal output.

[0163] The memory 803 can be a device with storage functionality. For example, it can be read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions; random access memory (RAM) or other types of dynamic storage devices capable of storing information and instructions; electrically erasable programmable read-only memory (EEPROM); compact disc read-only memory (CD-ROM) or other optical disc storage; optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.); magnetic disk storage media or other magnetic storage devices; or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited to these. The memory can exist independently and be connected to the processor via communication line 802. The memory can also be integrated with the processor.

[0164] The memory 803 stores computer execution instructions for implementing the scheme of this application, and its execution is controlled by the processor 801. The processor 801 executes the computer execution instructions stored in the memory 803, thereby implementing the data usage update method provided in the embodiments of this application.

[0165] Alternatively, in this embodiment, the processor 801 may execute the processing-related functions in the data usage update method provided in the following embodiments of this application, and the communication interface 804 may be responsible for communicating with other devices or communication networks. This embodiment does not specifically limit this.

[0166] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0167] In a specific implementation, as one example, the processor 801 may include one or more CPUs, for example... Figure 8 CPU0 and CPU1 in the CPU.

[0168] In a specific implementation, as one example, the communication device 800 may include multiple processors, such as... Figure 8The processors 801 and 808 are described herein. Each of these processors may be a single-core processor or a multi-core processor. The processors herein may include, but are not limited to, at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller unit (MCU), or an artificial intelligence processor, and other computing devices that run software. Each computing device may include one or more cores for executing software instructions to perform calculations or processing.

[0169] In a specific implementation, as one embodiment, the communication device 800 may further include an output device 805 and an input device 806. The output device 805 communicates with the processor 801 and can display information in various ways. For example, the output device 805 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 806 communicates with the processor 801 and can receive user input in various ways. For example, the input device 806 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0170] The aforementioned communication device 800 may sometimes be referred to as a communication device, which can be a general-purpose device or a special-purpose device. For example, the communication device 800 may be a desktop computer, a portable computer, a network server, a handheld digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, the aforementioned terminal device, the aforementioned network device, or a device with... Figure 8 Devices with similar structures. This application does not limit the type of communication device 800 to any particular embodiment.

[0171] The data usage update method provided in the embodiments of this application will now be described with reference to the accompanying drawings.

[0172] like Figure 9 As shown in the figure, a data usage update method provided in this application embodiment includes the following steps:

[0173] S901, The access network device determines that it needs to report information on the dropping of downlink data packets.

[0174] The discard information in this application embodiment includes the value of discarded traffic or the number of discarded data packets.

[0175] In one possible implementation, the access network device determines that it needs to report downlink data packet drop information, including: the access network device determines that it needs to report downlink data packet drop information based on first indication information from a session management entity, wherein the first indication information indicates that it needs to report downlink data packet drop information. For example, in this embodiment, the first indication information may be first billing identification information, which is used to identify the corresponding billing policy.

[0176] Optionally, in this embodiment, the first indication information is further used to indicate the content of the discarded information, such as the value of the discarded traffic or the number of discarded data packets. Of course, in this embodiment, the access network device may also receive a fourth indication information from the session management entity, which is used to indicate the content of the discarded information; this embodiment does not specifically limit this.

[0177] In another possible implementation, the access network device determines that downlink data packet drop information needs to be reported, including: the access network device determines that downlink data packet drop information needs to be reported based on its local configuration, for example, the access network device determines that a certain session needs to report downlink data packet drop information based on the session slicing information configured locally.

[0178] S902. The access network device sends a derived data packet of the discarded first downlink data packet to the user plane function entity. Correspondingly, the user plane function entity receives the derived data packet of the first downlink data packet from the access network device. This derived data packet is obtained based on the first downlink data packet and includes a first identifier indicating that the first downlink data packet was a discarded data packet.

[0179] In this embodiment, the derived data packet of the first downlink data packet functions to identify the first downlink data packet. For example, the derived data packet of the first downlink data packet may be a data packet including a first identifier and a copy of the first downlink data packet; or, the derived data packet of the first downlink data packet may be a data packet including a first identifier, information about the service flow that can identify the first downlink data packet, and information about the data usage of the first downlink data packet. This embodiment does not specifically limit the content of the derived data packet of the first downlink data packet.

[0180] S903. The user plane function entity determines that the first downlink data packet is a discarded data packet based on the first identifier in the derived data packet.

[0181] S904. The user plane function entity sends data usage update information to the session management entity. Correspondingly, the session management entity receives the data usage update information from the user plane function entity. The data usage update information is used to deduct the data usage of the first downlink data packet.

[0182] In one possible implementation, the user plane function entity sends data usage update information to the session management entity, including: the user plane function entity adds a packet drop flag to the derived data packet, and reports the data usage update information to the session management entity according to the first URR associated with the first PDR, wherein the first URR is a negative URR (i.e. the measured usage is negative, the same below), and the first PDR includes a PDI for detecting the packet drop flag.

[0183] In another possible implementation, the user plane function entity sends data usage update information to the session management entity, including: the user plane function entity adds a discard flag bit to the data packet after discarding the first identifier in the discarded derived data packet, and reports the data usage update information to the session management entity according to the first URR associated with the first PDR, wherein the first URR is a negative URR, and the first PDR includes a PDI for detecting the discard flag bit.

[0184] In another possible implementation, the user plane function entity sends data usage update information to the session management entity, including: the user plane function entity reports the data usage update information to the session management entity based on the negative URR associated with the PDR of the matched uplink data packet.

[0185] It should be noted that, in this embodiment, the data usage update information can be the updated data usage obtained by the user plane function entity deducting the data usage of the first downlink data packet from the data usage already statistically calculated internally; or, the data usage update information can be the data usage of the first downlink data packet, which is used to update the data usage already reported by the user plane function entity to the session management entity, and the update method is to deduct the data usage of the first downlink data packet from the data usage already reported by the user plane function entity to the session management entity. Of course, it is not limited to this; the data usage update information can simply be implemented by deducting the data usage of the first downlink data packet.

[0186] Optionally, in this embodiment of the application, the user plane functional entity can obtain the first PDR and the first URR in the following manner.

[0187] In one possible implementation, the user plane function entity receives a first rule from the session management entity. The first rule includes a first PDR and a first URR and a second URR associated with the first PDR; wherein the second URR is a positive URR. The measurement object corresponding to the second URR and the first URR is the same.

[0188] For example, such as Figure 10aAs shown, in this embodiment, the first PDR can be an existing PDR with an added PDI for detecting dropped packets, and associated with a first URR that is the opposite of the second URR. That is, in this embodiment, the first PDR also includes a PDI for detecting first downlink data packets. Specifically, when the first PDR detects a first downlink data packet, it uses the second URR associated with the first PDR for statistical reporting; or, when the first PDR detects a dropped packet flag, it uses the first URR associated with the first PDR for statistical reporting.

[0189] It should be noted that the PDI that detects the first downlink data packet in the first PDR of this application embodiment can also detect other downlink data packets besides the first data packet, and this application embodiment does not specifically limit this.

[0190] In another possible implementation, the user plane function entity receives a second rule from the session management entity. The second rule includes a first PDR and a first URR associated with the first PDR, a third PDR and a third URR associated with the third PDR, wherein the third PDR includes a PDI for detecting the first downlink data packet, and the third URR is a positive URR. The measurement objects corresponding to the first URR and the third URR are the same.

[0191] For example, such as Figure 10b As shown, the first PDR and the first URR associated with the first PDR are newly added in this embodiment. Meanwhile, the second rule in this embodiment includes a third PDR and a third URR associated with the third PDR. Specifically, when the third PDR detects a first data packet, it uses the third URR associated with the third PDR for statistical reporting; or, when the first PDR detects a dropped packet flag, it uses the first URR associated with the first PDR for statistical reporting.

[0192] It should be noted that the PDI that detects the first downlink data packet in the third PDR of this application embodiment can also detect other downlink data packets besides the first data packet, and this application embodiment does not specifically limit this.

[0193] Optionally, the data usage update method provided in this application embodiment may further include: the user plane function entity receiving a subscription message from the session management entity, the subscription message being used to request subscription to a data usage change event. That is, in this application embodiment, the user plane function entity may report data usage information to the session management entity based on the session management entity's subscription request.

[0194] Figure 9 For a detailed implementation of the embodiments shown, please refer to the following. Figure 13 The embodiments shown will not be described in detail here.

[0195] Based on this scheme, after the access network device discards the first downlink data packet, the session management entity can obtain data usage update information, which is used to deduct the data usage information of the first downlink data packet. In other words, in this embodiment, after the access network device discards the downlink data packet, the data usage information of these downlink data packets that have already been statistically recorded will be deducted. This ensures that the session management entity obtains more accurate data usage information. Furthermore, when the session management entity interacts with the billing function entity, the billing function entity can obtain more accurate data usage information, thereby achieving more accurate billing.

[0196] Among them, the actions of the user plane functional entities in steps S901 to S904 above can be performed by... Figure 8 The processor 801 in the communication device 800 shown calls the application code stored in the memory 803 to instruct the user plane function entity to execute. The actions of the access network device in steps S901 to S904 above can be performed by... Figure 8 The processor 801 in the communication device 800 shown calls the application code stored in the memory 803 to instruct the access network device to execute the operation. The actions of the session management entity in steps S901 to S904 can be performed by... Figure 8 The processor 801 in the communication device 800 shown calls the application code stored in the memory 803 to instruct the session management entity to execute, and this embodiment does not impose any restrictions on this.

[0197] like Figure 11 As shown in the figure, a data usage update method provided in this application embodiment includes the following steps:

[0198] S1101, The session management entity determines whether downlink data packet dropping information needs to be reported.

[0199] The discard information in this application embodiment includes the discarded traffic value or the number of discarded data packets, etc.

[0200] In one possible implementation, the session management entity determines that downlink data packet drop information needs to be reported, including: the session management entity determines that downlink data packet drop information needs to be reported based on third indication information from the policy control entity, wherein the third indication information indicates that downlink data packet drop information needs to be reported.

[0201] In another possible implementation, the session management entity determines that downlink packet drop information needs to be reported, including: the session management entity determines that downlink packet drop information needs to be reported based on local configuration.

[0202] S1102, The session management entity sends a first message to the access network device. Correspondingly, the access network device receives the first message from the session management entity. The first message includes second indication information, which indicates that downlink data packet drop information needs to be reported.

[0203] S1103. The access network device determines the downlink data packet discarding information of the billing object according to the second instruction information.

[0204] S1104. The access network device sends a second message to the session management entity. Correspondingly, the session management entity receives the second message from the access network device. The second message includes information about the charging object and information about the dropping of downlink data packets corresponding to the charging object.

[0205] S1105. The session management entity updates the data usage information of the billing object based on the information of the billing object and the discard information of the downlink data packets corresponding to the billing object. In the updated data usage information, the data usage information of the billing object that has discarded downlink data packets is deducted.

[0206] For steps S1102-S1105 above:

[0207] In one possible implementation, the first message includes the flow identifier of the first QoS flow; the billing object is the first QoS flow, and the information of the billing object is the flow identifier of the first QoS flow.

[0208] Optionally, in this embodiment, the first QoS flow is the QoS flow bound to the first charging policy rule (or, as can be understood, the first QoS flow is the QoS flow bound to the first charging policy rule). The binding parameters of the first charging policy rule include first charging identification information, which is used to identify the corresponding charging policy. That is, in this embodiment, the first charging identification information can be used as a binding parameter when binding a QoS flow, thereby enabling data usage statistics at the QoS flow granularity, and thus enabling QoS flow granularity charging.

[0209] In another possible implementation, the second indication information in the first message is the first billing identification information, which is used to identify the corresponding billing policy; the billing object is one or more QoS flows bound to a billing policy rule whose binding parameters include the first billing identification information (or, as can be understood, one or more QoS flows bound to a billing policy rule whose binding parameters include the first billing identification information); the information of the billing object is the first billing identification information. That is, in this embodiment, the first billing identification information can be used as a binding parameter when binding QoS flows, thereby enabling data usage statistics at the billing identification identifier granularity, and thus billing at the billing identification identifier granularity.

[0210] Optionally, in this embodiment, the first message is further used to indicate the content of the discarded information, such as the value of the discarded traffic or the number of discarded data packets. In one possible implementation, the parameter used to indicate the content of the discarded information can be, for example, the second indication information mentioned above. Of course, the session management entity can also indicate the content of the discarded information through other information in the first message, or the session management entity can also indicate the content of the discarded information in other ways; this embodiment does not specifically limit this.

[0211] Figure 11 For a detailed implementation of the embodiments shown, please refer to the following. Figure 16 or Figure 17 The embodiments shown will not be described in detail here.

[0212] Based on this scheme, after the access network device discards downlink data packets containing a billing object, the session management entity can obtain updated data usage information, and the data usage information of the discarded downlink data packets in the billing object is deducted from the updated data usage information. In other words, in this embodiment, after the access network device discards downlink data packets containing a billing object, the data usage information of these billed downlink data packets will be deducted. This ensures that the session management entity obtains more accurate data usage information for the billing object. Furthermore, when the session management entity interacts with the billing function entity, the billing function entity can obtain more accurate data usage information for the billing object, thereby enabling more accurate billing for the billing object.

[0213] The actions of the access network equipment in steps S1101 to S1105 above can be performed by... Figure 8 The processor 801 in the communication device 800 shown calls the application code stored in the memory 803 to instruct the access network device to execute the above steps S1101 to S1105, and the actions of the session management entity can be performed by... Figure 8 The processor 801 in the communication device 800 shown calls the application code stored in the memory 803 to instruct the session management entity to execute, and this embodiment does not impose any restrictions on this.

[0214] like Figure 12 As shown in the figure, a data usage update method provided in this application embodiment includes the following steps:

[0215] S1201. The access network device determines that it needs to report information on the dropping of downlink data packets.

[0216] For a detailed implementation of step S1201, please refer to [link / reference]. Figure 9 Step S901 of the embodiment shown will not be repeated here.

[0217] S1202. The access network device determines the discard information of the first downlink data packet based on the charging identification information in the received downlink data packet. The first downlink data packet is a downlink data packet containing the first charging identification information.

[0218] S1203, the access network device sends a third message to the session management entity. Correspondingly, the session management entity receives the third message from the access network device. The third message includes first charging identification information and information on the discarding of the first downlink data packet.

[0219] S1204. The session management entity updates the data usage information of the first downlink data packet based on the first billing identification information and the first downlink data packet discarding information. Specifically, the data usage information of the discarded first downlink data packet is deducted from the updated data usage information.

[0220] Optionally, the data usage update method provided in this application embodiment may further include: the session management entity sending a fifth indication message to the user plane entity, the fifth indication message instructing the user plane entity to add billing identification information to the downlink data packet.

[0221] Figure 12 For a detailed implementation of the embodiments shown, please refer to the following. Figure 17 The embodiments shown will not be described in detail here.

[0222] Based on this scheme, after the access network device discards the first downlink data packet containing the first charging identification information, the session management entity can obtain updated data usage information, and the data usage information of the first downlink data packet is deducted from the updated data usage information. In other words, in this embodiment, after the access network device discards the first downlink data packet containing the first charging identification information, the data usage information of these downlink data packets that have already been charged will be deducted. This ensures that the session management entity obtains more accurate data usage information with a higher granularity of the charging identification information. Furthermore, when the session management entity interacts with the charging function entity, the charging function entity can obtain more accurate data usage information with a higher granularity of the charging identification information, thereby achieving more accurate charging with a higher granularity of the charging identification information.

[0223] The actions of the access network equipment in steps S1201 to S1204 above can be performed by... Figure 8 The processor 801 in the communication device 800 shown calls the application code stored in the memory 803 to instruct the access network device to execute the above steps S1201 to S1204, and the actions of the session management entity can be performed by... Figure 8 The processor 801 in the communication device 800 shown calls the application code stored in the memory 803 to instruct the session management entity to execute, and this embodiment does not impose any restrictions on this.

[0224] The following will be based on Figure 6 or Figure 7 The communication system described is applied to, for example Figure 2a or Figure 2b Taking the 5G network shown as an example, for Figures 9 to 12 The data usage update method described herein is illustrated by example.

[0225] It should be noted that the message names between network elements or the names of parameters in the messages in the following embodiments of this application are just examples. Other names may be used in the specific implementation. This application does not limit them in this respect.

[0226] Combination Figure 9 The data usage update method described herein, in order to Figure 6 The communication system described is applied to, for example Figure 2a or Figure 2b Taking the 5G network shown as an example, such as Figure 13 As shown in the figure, a data usage update method provided in this application embodiment includes the following steps:

[0227] S1301, Optionally, after determining that the RAN device needs to report downlink data packet drop information, the SMF sends a first indication message to the RAN device. Correspondingly, the RAN device receives the first indication message from the SMF, which indicates that the RAN device needs to report downlink data packet drop information.

[0228] In one possible implementation, assuming the SMF is locally configured with information about services, sessions, or slices that need to report downlink packet drop information, the SMF can send a first indication message to the RAN device according to the local configuration. The first indication message indicates that the RAN device needs to report downlink packet drop information for a specific service, session, or slice.

[0229] In another possible implementation, the SMF can receive indication information from the PCF, which instructs the RAN device to report downlink packet drop information for a specific service, session, or slice. Furthermore, the SMF can send a first indication message to the RAN device based on this indication message, which instructs the RAN device to report downlink packet drop information for a specific service, session, or slice.

[0230] Optionally, in this embodiment, the first indication information may also indicate the content of the discard information, such as the value of the discarded traffic or the number of discarded data packets. This embodiment does not specifically limit this. Of course, the SMF may also indicate the content of the discard information to be reported to the RAN device in other ways, and this embodiment does not specifically limit this.

[0231] S1302, The RAN device determines that it needs to report information on the dropping of downlink data packets.

[0232] In one possible implementation, if step S1301 is executed, the RAN device can determine the downlink data packet drop information that needs to be reported based on the first indication information.

[0233] In another possible implementation, the RAN device can determine the downlink packet drop information that needs to be reported based on its local configuration. For example, assuming the RAN device is locally configured with information about services, sessions, or slices that require reporting downlink packet drop information, the RAN device can determine, based on its local configuration, whether to report downlink packet drop information for a specific service, session, or slice.

[0234] S1303, the RAN device discards the first downlink data packet.

[0235] For example, the RAN device may discard the first downlink data packet due to factors such as traffic shaping or congestion, and this application embodiment does not specifically limit this.

[0236] S1304. The RAN device sends a derived data packet of the discarded first downlink data packet to the UPF. Correspondingly, the UPF receives the derived data packet of the first downlink data packet from the RAN device. For a description of the derived data packet of the first downlink data packet, please refer to... Figure 9 The embodiments shown will not be described in detail here.

[0237] For example, such as Figure 14 As shown, assuming downlink data packet 0 is successfully transmitted, and data packets 1, 2, and 3 are all discarded, the RAN device sends derived data packets of data packet 1 (denoted as data packet 11), data packet 2 (denoted as data packet 21), and data packet 3 (denoted as data packet 31) to the UPF. Figure 14 In the example, data packet 11 includes the content of downlink transmitted data packet 1, data packet 21 includes the content of downlink transmitted data packet 2, and data packet 31 includes the content of downlink transmitted data packet 3. Furthermore, data packets 11, 21, and 31 also include a first identifier. Optionally, the first identifier can be carried in the data packet header, such as by using reserved bits in the data packet header. Taking the GTP protocol as an example, the first identifier can be added to the GTP-U uplink header. Here, the destination tunnel identifier in the GTP-U uplink header is the UPF tunnel identifier.

[0238] It should be noted that, Figure 13 The example shown is only one possible form of derived data packet, such as Figure 9 As described in the embodiments, the derived data packets may also exist in other forms, and this application does not specifically limit them.

[0239] S1305, UPF determines the first downlink data packet as a discarded data packet based on the first identifier in the derived data packet.

[0240] S1306, the UPF sends data usage update information to the SMF. Correspondingly, the SMF receives the data usage update information from the UPF. This data usage update information is used to deduct the data usage of the first downlink data packet.

[0241] In this embodiment, the specific implementation of the UPF sending data usage update information to the SMF can be found in [reference]. Figure 9 The embodiments shown will not be described in detail here.

[0242] For example, such as Figure 15 As shown, assuming data packet A is a normal uplink data packet and does not contain the first identifier; data packets 11, 21, and 31 all contain the first identifier. After receiving data packet A, the UPF processes it normally. For data packets 11, 21, and 31, after the UPF performs packet matching based on the PDI in the PDR used for detecting uplink data packets and the match is successful, the UPF can determine that the first downlink data packet is a discarded data packet based on the first identifier. Therefore, the UPF can discard the first identifier in data packets 11, 21, and 31 and add a discard flag (e.g., ...). Figure 15 After the negative flag bit in the PDR, matching continues through the PDI in the PDR used to detect downlink packets (because the content of the PDU session layer remains unchanged (taking the IP layer as an example, the destination IP address here is still the IP address of the terminal device), so packets 11, 21, and 31 can still be regarded as downlink packets). When packets 11, 21, and 31 match the PDI of the dropped packet flag bit in the first PDR, the UPF reports the data usage update information to the SMF according to the first URR associated with the first PDR. For example, assuming the data usage of packets 1, 2, and 3 is 3M, the data usage update information is used to deduct the 3M data usage.

[0243] It should be noted that the above example uses the discarding of the first identifier in the derived data packet as an example. For example... Figure 9As shown in the embodiment, the UPF may not discard the first identifier, but instead directly add a discard flag to the derived data packet and continue matching using the PDI in the PDR used to detect downlink data packets. When data packets 11, 21, and 31 match the PDI in the first PDR that detects the discard flag, the UPF reports the data usage update information to the SMF based on the first URR associated with the first PDR. Alternatively, for data packets 11, 21, and 31, after the UPF performs data packet matching based on the PDI in the PDR used to detect uplink data packets and the match is successful, the UPF can determine that the first downlink data packet is a discarded data packet based on the first identifier. Furthermore, the UPF can report the data usage update information to the SMF based on the negative URR associated with the matched PDR used to detect uplink data packets (i.e., in this embodiment, the PDR used to detect uplink data packets can be associated with a negative URR that is the opposite of the positive URR). This embodiment does not specifically limit this.

[0244] like Figure 9 As shown in the embodiments, in this application embodiment, the data usage update information can be the updated data usage obtained by UPF after deducting the data usage of the first downlink data packet based on the data usage already counted internally; or, the data usage update information can be the data usage of the first downlink data packet, and this application embodiment does not specifically limit this.

[0245] For example, suppose the SMF issues a quota of 30MB to the UPF, and the billing event is reported immediately after the "traffic threshold is reached," with a parameter of 10MB (meaning the billing event is triggered when the quota has 10MB remaining). When the UPF collects data usage data, after detecting packets 11, 21, and 31, it will deduct 3MB from the already collected data usage to obtain the updated data usage (e.g., if the already collected data traffic is 15MB, after detecting packets 11, 21, and 31, the collected data traffic is updated to 12MB). Furthermore, when 20MB of data usage has been used (with 10MB remaining), the "traffic threshold reached" billing event is triggered, and the UPF reports the data usage information to the SMF. Of course, after detecting data packets 11, 21, and 31, the UPF can directly send the data usage (3M) of data packets 11, 21, and 31 to the SMF, so that the SMF can update the data usage already reported by the UPF. This embodiment of the application does not specifically limit this. The relevant descriptions of quotas and billing events can be found in the description of the "Billing Process" in the preamble of the specific implementation method, and will not be repeated here.

[0246] Optionally, in the data usage update method provided in this application embodiment, before the UPF sends the data usage update information to the SMF, it may further include: the SMF sending a subscription message to the UPF. Correspondingly, the UPF receives the subscription message from the SMF. This subscription message is used to request subscription to a data usage change event (or a billing update event). The data usage change event may, for example, be a change in data usage information.

[0247] Figure 13 The technical effects of the embodiments described above can be referred to the above. Figure 9 The technical effects of the embodiments described herein will not be elaborated further here.

[0248] Among them, the actions of UPF in steps S1301 to S1306 above can be performed by Figure 8 The processor 801 in the communication device 800 shown calls the application code stored in the memory 803 to execute it with the instruction UPF. The actions of the RAN device in the above steps S1301 to S1306 can be performed by... Figure 8 The processor 801 in the communication device 800 shown calls the application code stored in the memory 803 to instruct the RAN device to execute. The actions of the SMF in steps S1301 to S1306 above can be performed by... Figure 8 The processor 801 in the communication device 800 shown calls the application code stored in the memory 803 to execute the instruction SMF. This embodiment does not impose any restrictions on this.

[0249] Combination Figure 11 The data usage update method described herein, in order to Figure 7 The communication system described is applied to, for example Figure 2a or Figure 2b Taking the 5G network shown as an example, such as Figure 16 As shown in the figure, a data usage update method provided in this application embodiment includes the following steps:

[0250] S1601, Optionally, after determining that the RAN device needs to report downlink data packet drop information, the PCF sends a third indication message to the SMF. Correspondingly, the RAN device receives the third indication message from the SMF, which instructs the RAN device to report downlink data packet drop information.

[0251] In one possible implementation, the third indication information can be carried in the PCC rule sent by the PCF to the SMF. Optionally, in this embodiment, the third indication information can also indicate the content of the discard information, such as the value of the discarded traffic or the number of discarded packets; this embodiment does not specifically limit this. Of course, the PCF can also indicate the content of the discard information to be reported to the SMF in other ways; this embodiment does not specifically limit this.

[0252] S1602, SMF determines that the RAN device needs to report downlink data packet drop information.

[0253] In one possible implementation, if step S1602 is performed, the SMF can determine the downlink data packet drop information that the RAN device needs to report based on the third indication information.

[0254] In another possible implementation, the SMF can determine the downlink packet drop information that the RAN device needs to report based on its local configuration. For example, assuming the SMF is locally configured with information about the services, sessions, or slices that need to report downlink packet drop information, the SMF can determine, based on its local configuration, that the RAN device needs to report downlink packet drop information for a specific service, session, or slice.

[0255] S1603 and SMF use charging identification information as a binding parameter to bind QoS flows with different charging identification information to different PCC rules.

[0256] For example, the charging identification information in this application embodiment may include a charging key or a monitoring key. By using the charging identification information as a binding parameter, data packets in the same QoS flow can have the same data usage statistics or charging method.

[0257] It should be noted that the binding parameters in the embodiments of this application may also include other parameters. For details, please refer to the relevant description of the "binding mechanism" in the preamble of the specific implementation method, which will not be repeated here.

[0258] It should be noted that the first PCC rule in this embodiment is Figure 11 The illustrated embodiment shows one specific form of the first billing strategy rule. Of course, the first billing strategy rule can have other forms, and this embodiment does not specifically limit these forms.

[0259] S1604, the SMF sends N2 message 1 to the RAN device. Correspondingly, the RAN device receives N2 message 1 from the SMF. N2 message 1 includes the QFI of the first QoS flow and second indication information. The second indication information indicates that downlink data packet drop information needs to be reported. The first QoS flow is a QoS flow bound to a first PCC rule. The binding parameters of the first PCC rule include first charging identification information, which is used to identify the corresponding charging policy.

[0260] Optionally, in this embodiment, N2 message 1 may also indicate the content of the discarded information, such as the value of the discarded traffic or the number of discarded data packets. This embodiment does not specifically limit this. In one possible implementation, the parameter used to indicate the content of the discarded information may, for example, be the second indication information mentioned above. Of course, the SMF may also indicate the content of the discarded information through other information in N2 message 1, or the SMF may also indicate the content of the discarded information in other ways. This embodiment does not specifically limit this.

[0261] It should be noted that this embodiment illustrates the example of sending the QFI of the first QoS stream and the second indication information in the same message. Of course, the QFI of the first QoS stream and the second indication information can also be included in different messages, and this embodiment does not specifically limit this.

[0262] It should be noted that the N2 message 1 in the embodiments of this application is only... Figure 11 This is one example of the first message. The first message can also be other messages, and the embodiments of this application do not specifically limit them.

[0263] S1605. The RAN device determines the downlink data packet dropping information of the billing object based on the second instruction information.

[0264] For example, RAN devices may discard downlink data packets due to factors such as traffic shaping or congestion, and this application embodiment does not specifically limit this.

[0265] This application uses the first QoS flow as an example to illustrate the embodiment of the billing object.

[0266] S1606, RAN sends N2 message 2 to SMF. Correspondingly, SMF receives N2 message 2 from the RAN device. This N2 message 2 includes the QFI of the first QoS flow and downlink packet drop information for the first QoS flow.

[0267] S1607, SMF updates the data usage information of the first QoS stream based on the QFI of the first QoS stream and the discard information of the downlink data packets of the first QoS stream. In the updated data usage information, the data usage information of the discarded downlink data packets of the first QoS stream is deducted.

[0268] It should be noted that the N2 message 2 in the embodiments of this application is only... Figure 11 This is one example of the second message. The second message can also be other types, and the embodiments of this application do not specifically limit it.

[0269] Figure 16 The embodiments described herein are based on Figure 11The embodiment described above uses the first QoS flow as an example for billing purposes. This allows for more accurate data usage statistics at the QoS flow granularity, thereby enabling more accurate billing at the QoS flow granularity. Related technical effect analysis can be found above. Figure 11 The technical effects of the embodiments described herein will not be elaborated further here.

[0270] The operation of the RAN equipment in steps S1601 to S1607 can be performed by... Figure 8 The processor 801 in the communication device 800 shown calls the application code stored in the memory 803 to instruct the RAN device to execute. The actions of the SMF in steps S1601 to S1607 above can be performed by... Figure 8 The processor 801 in the communication device 800 shown calls the application code stored in the memory 803 to execute the instruction SMF. This embodiment does not impose any limitations on this.

[0271] Combination Figure 11 The data usage update method described herein, in order to Figure 7 The communication system described is applied to, for example Figure 2a or Figure 2b Taking the 5G network shown as an example, such as Figure 17 As shown in the figure, a data usage update method provided in this application embodiment includes the following steps:

[0272] S1701-S1703, same Figure 16 The description of steps S1601-S1603 in the illustrated embodiment can be found in the following reference. Figure 16 The embodiments shown will not be described in detail here.

[0273] S1704, the SMF sends N2 message 3 to the RAN device. Correspondingly, the RAN device receives N2 message 3 from the SMF. N2 message 3 includes first charging identification information, which indicates whether downlink data packet drop information needs to be reported.

[0274] Optionally, in this embodiment, N2 message 3 may also indicate the content of the discarded information, such as the value of the discarded traffic or the number of discarded data packets. This embodiment does not specifically limit this. In one possible implementation, the parameter used to indicate the content of the discarded information may, for example, be the first billing identification information mentioned above. Of course, the SMF may also indicate the content of the discarded information through other information in N2 message 3, or the SMF may also indicate the content of the discarded information in other ways. This embodiment does not specifically limit this.

[0275] It should be noted that the N2 message 3 in the embodiments of this application is only... Figure 11This is one example of the first message. The first message can also be other messages, and the embodiments of this application do not specifically limit them.

[0276] S1705. RAN equipment determines the dropping information of downlink data packets for billing objects.

[0277] For example, RAN devices may discard downlink data packets due to factors such as traffic shaping or congestion, and this application embodiment does not specifically limit this.

[0278] This application embodiment uses one or more QoS flows bound to a PCC rule whose binding parameter includes the first billing identification information as an example for illustration.

[0279] S1706, RAN sends N2 message 4 to SMF. Correspondingly, SMF receives N2 message 4 from the RAN device. This N2 message 4 includes first charging identification information and downlink packet drop information for one or more QoS flows to which the PCC rule, whose binding parameters contain the first charging identification information, is bound.

[0280] It should be noted that the N2 message 4 in the embodiments of this application is only... Figure 11 This is one example of the second message. The second message can also be other types, and the embodiments of this application do not specifically limit it.

[0281] S1707, SMF updates the data usage information of one or more QoS flows based on the first charging identification information and the discard information of downlink data packets of one or more QoS flows bound to the PCC rule containing the first charging identification information in the binding parameters. In the updated data usage information, the data usage information of the discarded downlink data packets of one or more QoS flows bound to the PCC rule containing the first charging identification information in the binding parameters is deducted.

[0282] Figure 17 The embodiments described herein are based on Figure 11 The embodiment described above uses one or more QoS flows bound to a billing policy rule whose binding parameters include the first billing identification information as an example. This allows for more accurate data usage statistics at the granularity of the billing identification information, thereby enabling more accurate billing. Related technical effect analysis can be found above. Figure 11 The technical effects of the embodiments described herein will not be elaborated further here.

[0283] The operation of the RAN equipment in steps S1701 to S1707 can be performed by... Figure 8The processor 801 in the communication device 800 shown calls the application code stored in the memory 803 to instruct the RAN device to execute. The actions of the SMF in steps S1701 to S1707 above can be performed by... Figure 8 The processor 801 in the communication device 800 shown calls the application code stored in the memory 803 to execute the instruction SMF. This embodiment does not impose any limitations on this.

[0284] Combination Figure 12 The data usage update method described herein, in order to Figure 7 The communication system described is applied to, for example Figure 2a or Figure 2b Taking the 5G network shown as an example, such as Figure 18 As shown in the figure, a data usage update method provided in this application embodiment includes the following steps:

[0285] S1801-S1802, same Figure 13 The steps S1301-S1302 of the embodiment shown are described in detail below. Figure 13 The embodiments shown will not be described in detail here.

[0286] S1803, Optionally, after determining that the RAN device needs to report downlink data packet drop information, the SMF sends a fifth indication message to the UPF. Correspondingly, the UPF receives the fifth indication message from the SMF, which instructs the UPF to add charging identification information to the downlink data packet.

[0287] S1804, the UPF sends a downlink data packet to the RAN device. Correspondingly, the RAN device receives the downlink data packet from the UPF. This downlink data packet includes the corresponding billing identification information.

[0288] S1805. The RAN device determines the discard information of the first downlink data packet based on the charging identification information in the received downlink data packet. The first downlink data packet is a downlink data packet containing the first charging identification information.

[0289] For example, RAN devices may discard downlink data packets due to factors such as traffic shaping or congestion, and this application embodiment does not specifically limit this.

[0290] S1806, the RAN device sends N2 message 5 to the SMF. Correspondingly, the SMF receives N2 message 5 from the RAN device. N2 message 5 includes first charging identification information and information on the discarding of the first downlink data packet.

[0291] It should be noted that the N2 message 5 in the embodiments of this application is only... Figure 12 This is one example of a third message. The third message can also be other types, and the embodiments of this application do not specifically limit it.

[0292] S1807, SMF updates the data usage information of the first downlink data packet based on the first billing identification information and the first downlink data packet discarding information. Specifically, the data usage information of the discarded first downlink data packet is deducted from the updated data usage information.

[0293] Figure 18 The technical effects of the embodiments described above can be referred to the above. Figure 12 The technical effects of the embodiments described herein will not be elaborated further here.

[0294] The operation of the RAN equipment in steps S1801 to S1807 can be performed by... Figure 8 The processor 801 in the communication device 800 shown calls the application code stored in the memory 803 to instruct the RAN device to execute. The actions of the SMF in steps S1801 to S1807 can be performed by... Figure 8 The processor 801 in the communication device 800 shown calls the application code stored in the memory 803 to execute the instruction SMF. This embodiment does not impose any limitations on this.

[0295] It is understood that, in the above embodiments, the methods and / or steps implemented by the access network device can also be implemented by components (e.g., chips or circuits) that can be used in the access network device; the methods and / or steps implemented by the session management entity can also be implemented by components (e.g., chips or circuits) that can be used in the session management entity; and the methods and / or steps implemented by the user plane function entity can also be implemented by components (e.g., chips or circuits) that can be used in the user plane function entity.

[0296] The above mainly describes the solutions provided by the embodiments of this application from the perspective of interaction between various network elements. Correspondingly, the embodiments of this application also provide a communication device for implementing the various methods described above. This communication device can be an access network device in the above method embodiments, or a device containing the above access network device, or a component usable in an access network device; or, this communication device can be a session management entity in the above method embodiments, or a device containing the above session management entity, or a component usable in a session management entity; or, this communication device can be a user plane function entity in the above method embodiments, or a device containing the above user plane function entity, or a component usable in a user plane function entity. It is understood that, in order to implement the above functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled professionals may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0297] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0298] Figure 19 A schematic diagram of a communication device 190 is shown. The communication device 190 includes a transceiver module 1901 and a processing module 1902. The transceiver module 1901, also known as a transceiver unit, is used to implement transceiver functions, and may be, for example, a transceiver circuit, a transceiver, a transceiver device, or a communication interface.

[0299] In this embodiment, the communication device 190 is taken as an example of the user plane functional entity in the above method embodiment:

[0300] Transceiver module 1901 is configured to receive a derived data packet from a first downlink data packet from an access network device, wherein the derived data packet is obtained based on the first downlink data packet and includes a first identifier. Processing module 1902 is configured to determine, based on the first identifier, that the first downlink data packet is a discarded data packet. Transceiver module 1901 is further configured to send data usage update information to a session management entity, wherein the data usage update information is used to deduct the data usage of the first downlink data packet.

[0301] Optionally, the transceiver module 1901 is used to send data usage update information to the session management entity, including: adding a packet drop flag to the derived data packet; and reporting the data usage update information to the session management entity according to the first URR associated with the first PDR, wherein the first URR is a negative URR and the first PDR includes a PDI for detecting the packet drop flag.

[0302] Optionally, the transceiver module 1901 is used to send data usage update information to the session management entity, including: adding a discard flag bit to the data packet after the first identifier in the discarded derived data packet; and reporting the data usage update information to the session management entity according to the first URR associated with the first PDR, wherein the first URR is a negative URR and the first PDR includes a PDI for detecting the discard flag bit.

[0303] Optionally, the transceiver module 1901 is further configured to receive a first rule from the session management entity, the first rule including a first PDR and a first URR and a second URR associated with the first PDR; wherein the second URR is a positive URR.

[0304] Optionally, the transceiver module 1901 is further configured to receive a second rule from the session management entity. The second rule includes a first PDR and a first URR associated with the first PDR, a third PDR and a third URR associated with the third PDR, wherein the third PDR includes a PDI for detecting the first downlink data packet, and the third URR is a positive URR.

[0305] Optionally, the transceiver module 1901 is also used to receive subscription messages from the session management entity, which are used to request subscription data usage change event information.

[0306] In this example, the communication device 190 is used as the session management entity in the above method embodiment:

[0307] Processing module 1902 is used to determine whether downlink data packet drop information needs to be reported. Transceiver module 1901 is used to send a first message to the access network device, the first message including second indication information indicating that downlink data packet drop information needs to be reported. Transceiver module 1901 is also used to receive a second message from the access network device, the second message including information about the billing object and the downlink data packet drop information corresponding to the billing object. Processing module 1902 is also used to update the data usage information of the billing object based on the information about the billing object and the downlink data packet drop information corresponding to the billing object, wherein the updated data usage information deducts the data usage information of the billing object for dropped downlink data packets.

[0308] In this example, the communication device 190 is the access network device in the above method embodiment:

[0309] In one possible implementation, processing module 1902 is used to determine the need to report downlink data packet discard information. Transceiver module 1901 is used to send a derived data packet of the discarded first downlink data packet to the user plane function entity, wherein the derived data packet is obtained based on the first downlink data packet and includes a first identifier, the first identifier being used to indicate that the first downlink data packet is a discarded data packet.

[0310] Optionally, the processing module 1902 is specifically used to: determine, based on the first indication information from the session management entity, the information indicating that the downlink data packet drop information needs to be reported.

[0311] Optionally, the processing module 1902 is specifically used to: determine, based on the local configuration, the information on the dropping of downlink data packets that needs to be reported.

[0312] Optionally, the processing module 1902 is used to determine the downlink data packet drop information that needs to be reported, including: determining the downlink data packet drop information that needs to be reported based on third indication information from the policy control entity, wherein the third indication information indicates that the downlink data packet drop information needs to be reported.

[0313] Optionally, the processing module 1902 is used to determine the discard information of downlink data packets that need to be reported, including: determining the discard information of downlink data packets that need to be reported based on local configuration.

[0314] In another possible implementation, transceiver module 1901 is used to receive a first message from the session management entity, the first message including second indication information; the second indication information indicates that downlink data packet drop information needs to be reported. Processing module 1902 is used to determine the downlink data packet drop information of the billing object based on the second indication information. Transceiver module 1901 is also used to send a second message to the session management entity, the second message including information about the billing object and the downlink data packet drop information corresponding to the billing object.

[0315] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0316] In this embodiment, the communication device 190 is presented in an integrated manner, divided into various functional modules. Here, "module" can refer to a specific ASIC, circuitry, a processor and memory executing one or more software or firmware programs, integrated logic circuitry, and / or other devices that can provide the aforementioned functions. In a simplified embodiment, those skilled in the art will recognize that the communication device 190 can employ... Figure 8 The communication device shown is in the form of 800.

[0317] for example, Figure 8 The processor 801 in the communication device 800 shown can execute the data usage update method in the above method embodiment by calling computer execution instructions stored in the memory 803.

[0318] Specifically, Figure 19 The functions / implementation process of the transceiver module 1901 and the processing module 1902 can be obtained through Figure 8 The processor 801 in the communication device 800 shown calls computer execution instructions stored in memory 803 to implement the function. Alternatively, Figure 19 The function / implementation process of the processing module 1902 can be obtained through Figure 8 The processor 801 in the communication device 800 shown calls computer execution instructions stored in the memory 803 to implement the communication. Figure 19 The function / implementation process of the transceiver module 1901 can be obtained through Figure 8 This is achieved through the communication interface 804 in the communication device 800 shown.

[0319] Since the communication device 190 provided in this embodiment can execute the above-described data usage update method, the technical effects it can achieve can be referred to the above-described method embodiment, and will not be repeated here.

[0320] It should be noted that one or more of the above modules or units can be implemented by software, hardware, or a combination of both. When any of the above modules or units are implemented by software, the software exists as computer program instructions and is stored in memory. The processor can be used to execute the program instructions and implement the above method flow. The processor can be built into a SoC (System-on-a-Chip) or ASIC, or it can be a separate semiconductor chip. In addition to the core that executes software instructions for computation or processing, the processor may further include necessary hardware accelerators, such as field-programmable gate arrays (FPGAs), PLDs (Programmable Logic Devices), or logic circuits that implement dedicated logic operations.

[0321] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a CPU, microprocessor, digital signal processing (DSP) chip, microcontroller unit (MCU), artificial intelligence processor, ASIC, SoC, FPGA, PLD, application-specific digital circuit, hardware accelerator, or non-integrated discrete device, which can run the necessary software or perform the above method flow independently of software.

[0322] Optionally, embodiments of this application also provide a chip system, including: at least one processor and an interface, wherein the at least one processor is coupled to a memory via the interface, and when the at least one processor executes a computer program or instructions in the memory, the method in any of the above method embodiments is executed. In one possible implementation, the communication device further includes a memory. Optionally, the chip system may be composed of chips, or may include chips and other discrete devices; embodiments of this application do not specifically limit this.

[0323] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0324] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0325] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A method for updating data usage, characterized in that, The method includes: The user plane function entity receives a derived data packet from a first downlink data packet from an access network device, wherein the derived data packet is obtained based on the first downlink data packet and includes a first identifier. The user plane function entity determines the first downlink data packet as a discarded data packet based on the first identifier; The user plane function entity sends data usage update information to the session management entity, wherein the data usage update information is used to deduct the data usage of the first downlink data packet.

2. The method according to claim 1, characterized in that, The user plane function entity sends data usage update information to the session management entity, including: The user plane function entity adds a packet drop flag to the derived data packet; The user plane function entity reports the data usage update information to the session management entity according to the first usage reporting rule URR associated with the first packet detection rule PDR, wherein the first URR is a negative URR, and the first PDR includes packet detection information PDI for detecting the dropped packet flag.

3. The method according to claim 1, characterized in that, The user plane function entity sends data usage update information to the session management entity, including: The user plane function entity adds a packet drop flag to the data packet after discarding the first identifier in the derived data packet; The user plane function entity reports the data usage update information to the session management entity based on the first URR associated with the first PDR, wherein the first URR is a negative URR, and the first PDR includes a PDI for detecting the dropped packet flag.

4. The method according to claim 2 or 3, characterized in that, The method further includes: The user plane function entity receives a first rule from the session management entity, the first rule including the first PDR and the first URR and second URR associated with the first PDR; wherein the second URR is a positive URR.

5. The method according to claim 2 or 3, characterized in that, The method further includes: The user plane function entity receives a second rule from the session management entity. The second rule includes a first PDR and a first URR associated with the first PDR, a third PDR and a third URR associated with the third PDR, wherein the third PDR includes a PDI for detecting the first downlink data packet, and the third URR is a positive URR.

6. The method according to any one of claims 1-3, characterized in that, The method further includes: The user plane function entity receives a subscription message from the session management entity, the subscription message being used to request subscription data usage change event information.

7. A method for updating data usage, characterized in that, The method includes: Access network devices determine that they need to report downlink data packet drop information; The access network device sends a derived data packet of the first downlink data packet that has been discarded to the user plane function entity. The derived data packet is obtained based on the first downlink data packet. The derived data packet includes a first identifier, which is used to indicate that the first downlink data packet is a discarded data packet. The first identifier is used by the user plane function entity to trigger the session management entity to deduct the data usage of the first downlink data packet.

8. The method according to claim 7, characterized in that, The access network device determines that it needs to report downlink data packet drop information, including: The access network device determines that it needs to report downlink data packet drop information based on the first indication information from the session management entity, wherein the first indication information indicates that it needs to report downlink data packet drop information.

9. The method according to claim 7, characterized in that, The access network device determines that it needs to report downlink data packet drop information, including: The access network device determines, based on its local configuration, the information on dropped downlink data packets that needs to be reported.

10. A user-plane functional entity, characterized in that, The user plane functional entities include: a processing module and a transceiver module; The transceiver module is configured to receive a derived data packet of a first downlink data packet from an access network device, wherein the derived data packet is obtained based on the first downlink data packet and includes a first identifier. The processing module is configured to determine, based on the first identifier, that the first downlink data packet is a discarded data packet; The transceiver module is further configured to send data usage update information to the session management entity, wherein the data usage update information is used to deduct the data usage of the first downlink data packet.

11. The user plane functional entity according to claim 10, characterized in that, The transceiver module is used to send data usage update information to the session management entity, including: Used to add a dropped packet flag to the derived data packet; and to report the data usage update information to the session management entity according to the first usage reporting rule URR associated with the first message detection rule PDR, wherein the first URR is a negative URR, and the first PDR includes packet detection information PDI for detecting the dropped packet flag.

12. The user plane functional entity according to claim 10, characterized in that, The transceiver module is used to send data usage update information to the session management entity, including: Used to add a discard flag to the data packet after discarding the first identifier in the derived data packet; and to report the data usage update information to the session management entity according to the first URR associated with the first PDR, wherein the first URR is a negative URR and the first PDR includes a PDI for detecting the discard flag.

13. An access network device, characterized in that, The access network equipment includes: a processing module and a transceiver module; The processing module is used to determine the discard information of downlink data packets that need to be reported. The transceiver module is used to send a derived data packet of a discarded first downlink data packet to a user plane function entity. The derived data packet is obtained based on the first downlink data packet. The derived data packet includes a first identifier, which is used to indicate that the first downlink data packet is a discarded data packet. The first identifier is used by the user plane function entity to trigger the session management entity to deduct the data usage of the first downlink data packet.

14. The access network device according to claim 13, characterized in that, The processing module is specifically used for: The system determines that downlink packet drop information needs to be reported based on first indication information from the session management entity, wherein the first indication information indicates that downlink packet drop information needs to be reported.

15. The access network device according to claim 13, characterized in that, The processing module is specifically used for: Determine the information on dropped downlink data packets that need to be reported based on the local configuration.

16. A communication device, characterized in that, The communication device includes: a processor and a memory; The memory is used to store computer execution instructions, which, when executed by the processor, cause the communication device to perform the method as described in any one of claims 1-6 or 7-9.

17. A chip system, characterized in that, include: Processor and interface circuitry; The interface circuit is used to receive computer execution instructions and transmit them to the processor; The processor is configured to execute the computer execution instructions to cause the communication device to perform the method as described in any one of claims 1-6 or 7-9.

18. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by a computer, causes the computer to perform the method of any one of claims 1-6 or 7-9.

19. A computer program product, characterized in that, include: Instructions, when executed on a computer, cause the computer to perform the method of any one of claims 1-6 or 7-9.

20. A communication system, characterized in that, The communication system includes user plane functional entities and access network equipment; The access network device is configured to, after determining that downlink data packet discarding information needs to be reported, send a derived data packet of the discarded first downlink data packet to the user plane function entity, wherein the derived data packet is obtained based on the first downlink data packet, and the derived data packet includes a first identifier, the first identifier being used to indicate that the first downlink data packet is a discarded data packet; The user plane function entity is used to receive a derived data packet from the first downlink data packet from the access network device, and after determining that the first downlink data packet is a discarded data packet according to the first identifier, send data usage update information to the session management entity, wherein the data usage update information is used to deduct the data usage of the first downlink data packet.

Images