WO2022110152A1 - 数据用量更新方法、装置及*** - Google Patents

数据用量更新方法、装置及*** Download PDF

Info

Publication number
WO2022110152A1
WO2022110152A1 PCT/CN2020/132802 CN2020132802W WO2022110152A1 WO 2022110152 A1 WO2022110152 A1 WO 2022110152A1 CN 2020132802 W CN2020132802 W CN 2020132802W WO 2022110152 A1 WO2022110152 A1 WO 2022110152A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
data packet
downlink data
charging
session management
Prior art date
Application number
PCT/CN2020/132802
Other languages
English (en)
French (fr)
Inventor
孙海洋
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN202080107431.1A priority Critical patent/CN116615922A/zh
Priority to PCT/CN2020/132802 priority patent/WO2022110152A1/zh
Publication of WO2022110152A1 publication Critical patent/WO2022110152A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing

Definitions

  • the present application relates to the field of communications, and in particular, to a method, device and system for updating data usage.
  • aggregation-level QoS parameters are defined, such as user equipment (user equipment, UE) - aggregate maximum bit rate (AMBR), session AMBR ( session-AMBR) and slice maximum bitrate, etc.
  • UE-AMBR is used to control the aggregated bit rate of all non-guaranteed bit rate (non-GBR) QoS flow (ie non-GBR QoS flow) of terminal equipment, which is controlled by wireless receiver.
  • a radio access network (RAN) device performs control.
  • session-AMBR is used to control the aggregate maximum bit rate of all non-GBR QoS flows in a protocol data unit (PDU) session of the end device, performed by the end device and user plane function (UPF) control.
  • PDU protocol data unit
  • UPF user plane function
  • the maximum bit rate of the slice is used to control the maximum bit rate of all QoS flows of the terminal device in a network slice (slice), and the control is performed by the terminal device, the RAN device or the UPF.
  • RAN equipment can be based on UE-AMBR or slice maximum bit rate, etc. Feature drops downstream packets. In this scenario, the existing data usage statistics are inaccurate.
  • Embodiments of the present application provide a data usage update method, device, and system, which can improve the accuracy of data usage statistics.
  • a method for updating data usage may be a user plane functional entity or a module applied in the user plane functional entity, such as a chip or a chip system.
  • the following description takes the execution subject as the user plane function entity as an example for description.
  • the user plane functional entity receives a derivative data packet of the first downlink data packet from the access network device, wherein the derivative data packet is obtained according to the first downlink data packet, and the derivative data packet includes a first identifier;
  • the user plane functional entity determines that the first downlink data packet is a discarded data packet according to the first identifier; the user plane functional entity sends data usage update information to the session management entity, wherein the data usage update information is used for the first downlink data packet. Data usage deduction for downstream packets.
  • the session management entity can obtain the data usage update information, and the data usage update information is used to deduct the data usage information of the first downlink data packet.
  • the access network device discards the downlink data packets
  • the data usage information of the downlink data packets that have been counted will be deducted. This ensures that the session management entity obtains more accurate data usage information. Further, when the session management entity interacts with the charging function entity, the charging function entity can obtain more accurate data consumption information, thereby realizing more accurate charging.
  • the user plane function entity sends the data usage update information to the session management entity, including: the user plane function entity adds a discarded packet flag in the derived data packet;
  • the first usage reporting rule URR associated with the text detection rule PDR reports the data usage update information to the session management entity, where the first URR is a negative URR, and the first PDR includes a packet for detecting the discarded packet flag bit Detection information PDI. That is, in this embodiment of the present application, the first PDR including the PDI of the discarded packet detection flag bit may be associated with the negative value URR.
  • the user plane functional 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, so that the statistics of the first downlink data packet have been Data usage information is deducted.
  • the user plane functional entity sends the data usage update information to the session management entity, including: the user plane functional entity adds a discarded packet flag to the data packet after discarding the first identifier in the derived data packet bit; the user plane function entity 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 detecting the discarded packet PDI of flag bits.
  • the user plane functional 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, so that the statistics of the first downlink data packet have been Data usage information is deducted.
  • the method for updating data usage further includes: the user plane function entity receives a first rule from the session management entity, where the first rule includes the first PDR and the The first URR and the second URR associated with a PDR; wherein, the second URR is a positive URR.
  • the first PDR in this embodiment of the present application may be a PDI that detects a discarded packet flag bit added to the current PDR, and associates the first URR opposite to the second URR.
  • the method for updating data usage further includes: the user plane function entity receives a second rule from the session management entity, where the second rule includes the first PDR and the The first URR, the third PDR associated with a PDR, and the 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 value URR. That is, the first PDR and the first URR associated with the first PDR in this embodiment of the present application are newly added.
  • the second rule in this embodiment of the present application includes a third PDR and a third URR associated with the third PDR. Wherein, when the third PDR detects the first data packet, the third URR associated with the third PDR is used for statistical reporting; or, when the first PDR detects the discarded packet flag, the first URR associated with the first PDR is used. Statistical reporting.
  • the data usage update method provided by the embodiment of the present application further includes: the user plane functional entity receives a subscription message from the session management entity, where the subscription message is used to request subscription data usage change event information. That is, in the embodiment of the present application, the user plane functional entity may report data usage update information to the session management entity based on the subscription of the session management entity.
  • a method for updating data usage is provided, and the communication device for executing the method for updating data usage may be an access network device; it may also be a module applied in the access network device, such as a chip or a chip system.
  • the following description takes the execution subject as an access network device as an example.
  • the access network device determines that the discarding information of the downlink data packet needs to be reported; the access network device sends a derivative data packet of the discarded first downlink data packet to the user plane functional entity, wherein the derivative data packet is based on the first downlink data packet.
  • the derived data packet includes a first identifier, where the first identifier is used to indicate that the first downlink data packet is a discarded data packet.
  • the access network device after discarding the first downlink data packet, sends a derivative data packet of the discarded first downlink data packet to the user plane functional entity, where the derivative data packet includes the first identifier. Further, according to the first identifier, the user plane function entity can determine that the first downlink data packet is a discarded data packet, and send the data usage update information to the session management entity, so that the session management entity can obtain the data usage update information.
  • the data usage update information is used to deduct the data usage information of the first downlink data packet.
  • the access network device after the access network device discards the downlink data packets, the data usage information of the downlink data packets that have been counted will be deducted. This ensures that the session management entity obtains more accurate data usage information. Further, when the session management entity interacts with the charging function entity, the charging function entity can obtain more accurate data consumption information, thereby realizing more accurate charging.
  • determining that the access network device needs to report the discard information of the downlink data packet includes: the access network device determines that the discard information of the downlink data packet needs to be reported according to the first indication information from the session management entity, the The first indication information indicates that the discarding information of the downlink data packet needs to be reported. Based on this solution, the access network device can determine that the discarding information of the downlink data packet needs to be reported.
  • determining that the access network device needs to report the discard information of the downlink data packet includes: the access network device determines that the discard information of the downlink data packet needs to be reported according to a local configuration. Based on this solution, the access network device can determine that the discarding information of the downlink data packet needs to be reported.
  • a method for updating data usage is provided, and a communication device executing the method for updating data usage may be a session management entity, or a module applied in the session management entity, such as a chip or a system-on-chip.
  • the following description takes the execution subject as the session management entity as an example for description.
  • the session management entity determines that the discarding information of the downlink data packet needs to be reported; the session management entity sends a first message to the access network device, where the first message includes second indication information indicating that the discarding information of the downlink data packet needs to be reported ; the session management entity receives the second message from the access network device, the second message includes the information of the charging object and the discarding information of the downlink data packet corresponding to the charging object; the session management entity according to the information of the charging object The discarding information of the downlink data packets corresponding to the charging object, and the data consumption information of the charging object is updated, wherein the data consumption information of the discarded downlink data packets in the charging object in the updated data consumption information is deducted .
  • the session management entity can obtain the updated data usage information, and the downlink data packets in the charging object have been discarded in the updated data usage information. data usage information is deducted.
  • the data consumption information of these downlink data packets that have been charged will be deducted. In this way, it can be ensured that the session management entity obtains more accurate data usage information for the charging object. Further, when the session management entity interacts with the charging function entity, the charging function entity can obtain more accurate data consumption information for the charging object, thereby realizing more accurate charging for the charging object.
  • the first message includes a flow identifier of the first QoS flow; the charging object is the first QoS flow, and the information of the charging object is the flow identifier of the first QoS flow.
  • the first QoS flow is a QoS flow to which the first charging policy rule is bound, and the binding parameter of the first charging policy rule includes first charging identification information, and the first charging policy rule includes first charging identification information.
  • the charging identification information is used to identify the corresponding charging policy. That is, in this embodiment of the present application, the charging identification information may be used as a binding parameter of the first charging policy rule.
  • the second indication information is first charging identification information, and the first charging identification information is used to identify a corresponding charging policy; the charging object is a binding parameter including the first charging One or more QoS flows to which the charging policy rule of the charging identification information is bound; the information of the charging object is the first charging identification information.
  • the first message is further used to indicate that the discarding information includes the discarded traffic value or the number of discarded data packets.
  • the session management entity determines that the discarding information of the downlink data packet needs to be reported, including: the session management entity determines the discarding information of the downlink data packet that needs to be reported according to the third indication information from the policy control entity, wherein the The third indication information indicates that the discarding information of the downlink data packet needs to be reported. Based on this solution, the session management entity can determine that the discarding information of the downlink data packet needs to be reported.
  • determining that the session management entity needs to report the discarding information of the downlink data packet includes: the session management entity determines that the discarding information of the downlink data packet needs to be reported according to the local configuration. Based on this solution, the session management entity can determine that the discarding information of the downlink data packet needs to be reported.
  • a method for updating data usage is provided, and the communication device for executing the method for updating data usage may be an access network device; it may also be a module applied in the access network device, such as a chip or a chip system.
  • the following description takes the execution subject as an access network device as an example.
  • the access network device receives the first message from the session management entity, where the first message includes second indication information; the second indication information indicates that the discarding information of the downlink data packet needs to be reported; the access network device, according to the second indication information, Determine the discarding information of the downlink data packets of the charging object; the access network device sends a second message to the session management entity, where the second message includes the information of the charging object and the discarding information of the downlink data packets corresponding to the charging object . Based on the solution, after discarding the downlink data packets of the charging object, the access network device can send the information of the charging object and the discarding information of the downlink data packets corresponding to the charging object to the session management entity.
  • the session management entity can obtain the updated data usage information according to the information of the charging object and the discarding information of the downlink data packets corresponding to the charging object, and the downlink discarded in the charging object in the updated data usage information
  • the data usage information of the packet is deducted.
  • the access network device discards the downlink data packets containing the charging object
  • the data consumption information of these downlink data packets that have been charged will be deducted.
  • the charging function entity can obtain more accurate data consumption information for the charging object, thereby realizing more accurate charging for the charging object.
  • the first message includes a flow identifier of the first QoS flow; the charging object is the first QoS flow, and the information of the charging object is the flow identifier of the first QoS flow.
  • the first QoS flow is a QoS flow bound by a first charging policy rule
  • the binding parameter of the first charging policy rule includes first charging identification information
  • the first charging policy rule The fee identification information is used to identify the corresponding charging policy. That is, in this embodiment of the present application, the charging identification information may be used as a binding parameter of the first charging policy rule.
  • the second indication information is the first charging identification information
  • the first charging identification information is used to identify a corresponding charging policy
  • the charging object is that the binding parameter includes the first charging identification information.
  • One or more QoS flows to which different charging policy rules of the charging identification information are bound; the information of the charging object is the first charging identification information.
  • the first message is further used to indicate that the discarding information includes the discarded traffic value or the number of discarded data packets.
  • a method for updating data usage is provided, and a communication device executing the method for updating data usage can be a session management entity, or a module applied in the session management entity, such as a chip or a chip system.
  • the following description takes the execution subject as the session management entity as an example for description.
  • the session management entity receives a third message from the access network device, where the third message includes the first charging identification information and the discarding information of the first downlink data packet, where the first downlink data packet contains the first charging identification information
  • the session management entity updates the data consumption information of the first downlink data packet according to the first charging identification information and the discarding information of the first downlink data packet.
  • the data consumption information of the discarded first downlink data packet in the updated data consumption information is deducted.
  • the session management entity can obtain the updated data consumption information, and the first downlink data in the updated data consumption information Data usage information for row packets is deducted.
  • the data usage information of these downlink data packets that have been charged will be deducted.
  • the charging function entity can obtain more accurate data consumption information of the granularity of the charging identification information, thereby realizing more accurate charging of the granularity of the charging identification information.
  • the data usage update method provided by the embodiment of the present application further includes: the session management entity sends first indication information to the access network device, where the first indication information indicates that the discarding information of the downlink data packet needs to be reported . Based on this solution, the access network device can determine that the discarding information of the downlink data packet needs to be reported.
  • the first indication information is the first charging identification information. Based on this solution, more accurate data usage information statistics of the granularity of charging identification information can be realized, thereby realizing more accurate charging of the granularity of charging identification information.
  • the first indication information further indicates that the discarding information includes the discarded traffic value or the number of discarded data packets.
  • the data usage update method provided by the embodiment of the present application further includes: the session management entity sends fifth indication information to the user plane entity, where the fifth indication information instructs the user plane entity to increase the count in the downlink data packet Fee identification information.
  • the user plane functional entity can add charging identification information in the downlink data packet, so that the access network device can perform data usage statistics according to the charging identification information in the downlink data packet.
  • a method for updating data usage is provided, and the communication device executing the method for updating data usage may be an access network device; it may also be a module applied in the access network device, such as a chip or a chip system.
  • the following description takes the execution subject as an access network device as an example.
  • the access network device determines that the discarding information of the downlink data packet needs to be reported; the access network device determines the discarding information of the first downlink data packet according to the charging identification information in the received downlink data packet, and 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 the session management entity, where the third message includes the first charging identification information and the discarding information of the first downlink data packet.
  • 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.
  • the session management entity can obtain the updated data usage information according to 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 in the updated data usage information is deduction.
  • the access network device discards the first downlink data packets containing the first charging identification information, the data usage information of these downlink data packets that have been charged will be deducted.
  • the session management entity obtains more accurate data usage information of the granularity of the charging identification information.
  • the charging function entity can obtain more accurate data consumption information of the granularity of the charging identification information, thereby realizing more accurate charging of the granularity of the charging identification information.
  • the discarding information includes the discarded traffic value or the number of discarded data packets.
  • determining that the access network device needs to report the discarding information of the downlink data packet includes: the access network device determines that the discarding information of the downlink data packet needs to be reported according to the first indication information from the session management entity, wherein , the first indication information indicates that the discarding information of the downlink data packet needs to be reported. Based on this solution, the access network device can determine that the discarding information of the downlink data packet needs to be reported.
  • the first indication information is the first charging identification information. Based on this solution, more accurate data usage information statistics of the granularity of charging identification information can be realized, thereby realizing more accurate charging of the granularity of charging identification information.
  • the first indication information further indicates that the discarding information includes the discarded traffic value or the number of discarded data packets.
  • determining that the access network device needs to report the discard information of the downlink data packet includes: the access network device determines that the discard information of the downlink data packet needs to be reported according to a local configuration. Based on this solution, the access network device can determine that the discarding information of the downlink data packet needs to be reported.
  • a communication device for implementing the above method.
  • the communication device includes corresponding modules, units, or means (means) for implementing the above method, and the modules, units, or means may be implemented by hardware, software, or hardware executing corresponding software.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device includes a processing module and a transceiver module, and the transceiver module is configured to perform the method described in any one of the first aspect to the sixth aspect, and receive a message on the side of the communication device. and sending operation; the processing module is used to invoke an instruction to execute the message processing or control operation performed on the communication device side in the method according to any one of the first aspect to the sixth aspect.
  • a communication device comprising: a processor; the processor is configured to be coupled to a memory, and after reading computer instructions stored in the memory, execute the method according to any one of the preceding aspects according to the instructions.
  • the communication device further includes a memory; the memory is used to store computer instructions.
  • the communication apparatus further includes a communication interface; the communication interface is used for the communication apparatus to communicate with other devices.
  • the communication interface may be a transceiver, an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, and the like.
  • the communication device may be a chip or a chip system.
  • the communication device when the communication device is a chip system, the communication device may be constituted by a chip, or may include a chip and other discrete devices.
  • the above-mentioned communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip or a chip system Wait.
  • the processor described above may also be embodied as a processing circuit or a logic circuit.
  • a computer-readable storage medium is provided, and instructions are stored in the computer-readable storage medium, when the computer-readable storage medium runs on a computer, the computer can execute the method described in any one of the above aspects.
  • a computer program product comprising instructions which, when run on a computer, enable the computer to perform the method of any of the preceding aspects.
  • a communication system in an eleventh aspect, includes a user plane functional 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.
  • the communication system includes 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 above;
  • Figure 1 is a schematic diagram of an existing 5G QoS model based on QoS flow
  • Figure 2a is a schematic diagram of a service-oriented architecture of an existing 5G network
  • Fig. 2b is a schematic diagram of a reference point-based 5G network architecture corresponding to Fig. 2a;
  • FIG. 3 is a schematic diagram of an existing charging process
  • FIG. 4 is an example flow chart of network charging provided by an embodiment of the present application.
  • Fig. 5 is a schematic diagram of the relationship between existing PDR, PDI and flow action
  • FIG. 6 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of another communication system architecture provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 9 is a schematic flowchart 1 of a method for updating data usage provided by an embodiment of the present application.
  • FIG. 10a is a schematic diagram 1 of the association between the PDR and the URR provided by the embodiment of the present application.
  • FIG. 10b is a schematic diagram 2 of the association between the PDR and the URR provided by the embodiment of the present application.
  • FIG. 11 is a second schematic flowchart of a method for updating data usage provided by an embodiment of the present application.
  • FIG. 12 is a schematic flowchart three of a method for updating data usage provided by an embodiment of the present application.
  • FIG. 13 is an interactive schematic diagram 1 of a method for updating data usage provided by an embodiment of the present application.
  • FIG. 14 is a schematic diagram 1 of data transmission provided by an embodiment of the present application.
  • FIG. 15 is a second schematic diagram of data transmission provided by an embodiment of the present application.
  • FIG. 16 is a second interactive schematic diagram of a method for updating data usage provided by an embodiment of the present application.
  • FIG. 17 is an interactive schematic diagram three of the data usage update method provided by the embodiment of the present application.
  • FIG. 18 is a fourth schematic diagram of interaction of the method for updating data usage provided by the embodiment of the present application.
  • FIG. 19 is a schematic structural diagram of another communication apparatus provided by an embodiment of the present application.
  • a PDU session is an association between a terminal device and a data network (DN) for providing a PDU connection service.
  • DN data network
  • a 5G QoS model based on QoS flow is proposed, as shown in Figure 1.
  • the 5G QoS model supports GBR QoS flow (ie GBR QoS flow) and non-GBR QoS flow. Packets controlled by the same QoS flow receive the same transport processing (such as scheduling, or admission thresholds, etc.).
  • one or more PDU sessions can be established with the 5G network.
  • One or more QoS flows can be established in each PDU session.
  • a QoS flow is identified by a QoS flow identifier (QFI), that is, a QFI uniquely identifies a QoS flow in a session.
  • QFI QoS flow identifier
  • a PDU session corresponds to a general packet radio service (GPRS) tunneling protocol user plane (GPRS tunneling protocol user plane, GTP-U) tunnel between the RAN device and the UPF one-to-one;
  • GPRS general packet radio service
  • GTP-U general packet radio service tunneling protocol user plane
  • one QoS flow corresponds to A radio bearer between a terminal device and a RAN device, and a radio bearer can correspond to one or more QoS flows.
  • a QoS flow is a GBR QoS flow or a non-GBR QoS flow is determined by the corresponding QoS profile (QoS profile).
  • the corresponding QoS file contains the following QoS parameters: 5G QoS identifier (5G QoS identifier, 5QI), allocation and retention priority (ARP), guaranteed flow bit rate (guaranteed flow bit rate, GFBR) and maximum flow bit rate (MFBR), optionally including QoS notification control (QNC).
  • 5G QoS identifier 5G QoS identifier, 5QI
  • ARP allocation and retention priority
  • guaranteed flow bit rate guaranteed flow bit rate
  • GFBR guaranteed flow bit rate
  • MFBR maximum flow bit rate
  • QNC QoS notification control
  • the GBR QoS flow can be divided into GRB QoS flow that requires notification control and GBR QoS flow that does not require notification control.
  • the RAN device detects that the corresponding QoS flow resources cannot be satisfied, the RAN device notifies the session management function (SMF) of the event. Further SMF can initiate QoS flow deletion or modification flow.
  • the corresponding QoS file contains the following QoS
  • 5QI is a scalar used to index to the corresponding 5G QoS feature.
  • 5QI is divided into standardized 5QI, pre-configured 5QI and dynamically allocated 5QI.
  • standardized 5QI there is a one-to-one correspondence with a set of standardized 5G QoS characteristic values; for the pre-configured 5QI, the corresponding 5G QoS characteristic values are pre-configured on the radio access network (RAN) equipment; for dynamic
  • the assigned 5QI and the corresponding 5G QoS features are sent by the core network device to the RAN device through the QoS file.
  • ARP includes priority, preemption capability and preemption capability.
  • GFBR stands for the bit rate expected to be provided to the GBR QoS flow.
  • 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.
  • RQA is used to indicate that the service transmitted using the corresponding QoS flow uses reverse QoS.
  • the QNC is used to instruct the RAN device whether to notify the network side when the GFBR cannot be satisfied within the usage period of the QoS flow.
  • the 5G system also introduces QoS parameters at the aggregation level, such as UE-AMBR, session-AMBR, and slice maximum bit rate.
  • UE-AMBR is used to control the aggregate bit rate of all non-GBR QoS flows of terminal equipment, and the control is performed by RAN equipment.
  • the RAN device controls the uplink (uplink, UL) and downlink (downlink, DL) UE-AMBR, and performs traffic shaping, such as discarding data packets exceeding the quota.
  • session-AMBR is used to control the aggregated maximum bit rate of all non-GBR QoS flows in one PDU session of the end device, and the control is performed by the end device and the UPF.
  • the end device controls UL Session-AMBR to perform traffic shaping, such as discarding packets that exceed the quota.
  • UPF controls UL and DL Session-AMBR, and performs traffic shaping, such as dropping packets that exceed the quota.
  • the maximum bit rate of the slice is used to control the maximum bit rate of all QoS flows of the terminal device in a network slice (slice), and the control is performed by the terminal device, the RAN device or the UPF.
  • RAN equipment controls UL and DL slice-MBR, performs traffic shaping, such as dropping packets that exceed the quota.
  • 5G system architecture (5G system architecture) and 5G converged billing related functions:
  • FIG. 2a is a schematic diagram of a service-oriented architecture of an existing 5G network.
  • the 5G network includes RAN equipment, UPF, core access and mobility management function (AMF), SMF, authentication server function (AUSF), network slice selection function (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 (application function, AF) or charging function (charging function, CHF), etc.
  • 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 AMF through the N3 interface ( N3 for short) communicates with the UPF; 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).
  • the control plane functions such as AUSF, AMF, SMF, NSSF, NEF, NRF, PCF, UDM, UDR, CHF or AF shown in FIG.
  • the service interface provided by AUSF is Nausf
  • the service interface provided by AMF is Namf
  • the service interface provided by SMF is Nsmf
  • the service interface provided by NSSF is Nnssf
  • the service interface provided by NEF is Nnef
  • the service interface provided by NRF is Nnrf
  • the service interface provided by PCF is Npcf
  • the service interface provided by UDM is Nudm
  • the service interface provided by UDR is Nudr
  • the service interface provided by CHF is Nchf
  • the service interface provided by AF externally Naf.
  • FIG. 2b is a schematic diagram of a reference point-based 5G network architecture corresponding to FIG. 2a.
  • 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 AMF through the N3 interface (N3 for short) ) communicates with the UPF; different UPFs communicate through the N9 interface (N9 for short); the UPF accesses the data network through the N6 interface (N6 for short).
  • SMF communicates with UPF through N4 interface (N4 for short); AMF network element communicates with SMF through N11 interface (N11 for short); AMF communicates with UDM through N8 interface (N8 for short); AMF communicates with AUSF through N12 interface (N12 for short) Communication; AMF communicates with PCF through N15 interface (N15 for short); AMF communicates with NSSF through N22 interface (N22 for short); different AMFs communicate through N14 interface (N14 for short); SMF communicates with PCF through N7 interface (N7 for short) ; SMF communicates with UDM through N10 interface (N10 for short); SMF communicates with NEF through N29 interface (N29 for short); SMF communicates with NRF through Nnrf interface (Nnrf for short); SMF communicates with CHF through Nchf interface (Nchf for short); PCF It communicates with NEF through N5 interface (N5 for short); UDR communicates with PCF through N36 interface (N36 for short); U
  • the functions related to 5G converged charging include PCF, SMF, UPF, and CHF.
  • the description of each charging-related function is shown in Table 1.
  • the SMF applies to the PCF for charging rules. Further, the PCF returns the charging rules to the SMF.
  • the charging rules include charging granularity and charging method.
  • S2 selects the corresponding CHF according to the priority.
  • SMF applies for quota to CHF, and CHF returns quota and charging events to SMF.
  • SMF issues N4 rules to UPF. Quota and billing events are included in N4 rules.
  • the terminal device accesses the service, the UPF parses the packet, and performs data usage statistics according to the matched packet detection rule (packet detection rule, PDR).
  • PDR packet detection rule
  • the UPF reports data usage information (also referred to as quota usage information) to the SMF.
  • the SMF reports the data usage information to the CHF, and applies for a new quota.
  • the follow-up process repeats itself, continuously reporting data usage information and updating new quotas until the user is deactivated or the balance is insufficient.
  • the charging granularity is used to characterize who is to be charged.
  • a PDU session may contain many service flows.
  • the entire PDU session can be charged, or different service flows in the PDU session can be charged separately.
  • related descriptions of different charging granularities may be as shown in Table 2.
  • 5G converged billing combines offline billing and online billing. Therefore, there are two billing methods for 5G converged billing, including offline billing and online billing. Among them, for online charging, when a charging session is created, the SMF needs to apply to the CHF for service quotas and related charging parameters. For offline charging, when a charging session is created, the SMF only needs to apply for the relevant charging parameters from the CHF, but does not need to apply for service quotas.
  • Billing events i.e. trigger conditions.
  • Billing events are actually some events subscribed by CHF to SMF, that is, SMF needs to apply for quota or report quota under specified conditions. For example, when the traffic used by the service reaches a specified threshold, the SMF sends a message to the CHF to update the charging session and obtain a new quota.
  • charging events can be divided into PDU session level (referred to as session level) and service level (referred to as rating group (RG) level).
  • the charging event at the PDU session level is effective for all RGs in the PDU session, and is applicable to the entire PDU session.
  • the service-level charging event takes effect only for the specified service flow in the PDU session and applies to the specified RG.
  • billing events can be classified into immediate reporting (Immediate) and delayed reporting (Deferred).
  • immediate reporting Immediate
  • delayed reporting Delivered
  • the SMF collects the quota consumption corresponding to the current charging event, and immediately reports it to the CHF.
  • the SMF collects the quota consumption corresponding to the current charging event, temporarily caches it, and reports it together when the next immediately reported charging event occurs.
  • SMF locally supports the configuration of whether accounting events are enabled, and the reporting method, which is used as the default value.
  • the CHF can also deliver charging events to the SMF, and the delivered charging event priority is higher than the locally configured charging event priority. Whether or not some charging events are enabled and how they are reported can be modified.
  • 2nd generation (2G)/3rd generation (3G)/4th generation (4th generation, 4G) networks charging events are mostly reported immediately, while in 5G converged charging, some
  • the reporting method of charging events can be modified, and the operator can flexibly formulate the reporting method according to its own business, which can reduce the impact of signaling.
  • Table 3 describes the related information by taking two charging triggers as an example.
  • the charging attribute is online charging. Recharged 100 yuan and ordered the following package:
  • Basic traffic package ordinary service traffic of 0.1 yuan/MB, the operator specifies that the rate group corresponding to the basic traffic package is RG1.
  • Directed traffic package 10 yuan 1GB of a certain news reading APP traffic, the operator stipulates that the rate group corresponding to the APP traffic is RG2.
  • the process of network charging includes the following steps:
  • the SMF interacts with the PCF, and obtains corresponding charging rules according to the subscription information of the user, including charging granularity and charging method, such as RG1 (online charging) and RG2 (online charging).
  • SMF applies to CHF for the corresponding quota; CHF checks account balance, creates user bills, and sends corresponding quota and charging events to SMF, as follows:
  • Directed traffic package quota 30M; "traffic threshold reached” billing event, reported immediately, the parameter is 10MB.
  • the SMF delivers to the UPF the quotas corresponding to the basic traffic packets and the directional traffic packets and the charging event together.
  • the terminal device A starts to use the APP to browse news, the UPF parses the service packet, starts the counter, and records the parsed traffic of the APP.
  • the terminal device A With the use of the terminal device A, the accumulated packet traffic continues to increase. When the directional traffic packet uses 20MB (10MB remaining), the "traffic threshold reached" charging event is triggered, and the UPF will report the data usage information to the SMF. .
  • the SMF reports the data usage information to the CHF, and requests to update the quota.
  • the CHF stores the charging information corresponding to the data usage in the corresponding bill, and issues a new 30M quota to the SMF, so that the SMF can issue a new 30M quota to the UPF.
  • UPF still continues to bill, and the 5M traffic used in the process needs to be reduced after the new quota is issued.
  • the binding mechanism is to associate the service data flow (defined by the service data flow (SDF) template in the policy and charging control (PCC) rules) with the QoS flow that transmits the service data flow Process (English:
  • SDF service data flow
  • PCC policy and charging control
  • the binding mechanism is the procedure that associates a service data flow (defined in a PCC rule by means of the SDF template), to the QoS Flow deemed to transport the service data flow).
  • the existing binding mechanism includes the following three steps:
  • the first step is session binding, that is, a one-to-one correspondence between AF sessions and PDU sessions.
  • session binding that is, a one-to-one correspondence between AF sessions and PDU sessions.
  • PCC rule authorization is performed by the PCF, authorizes the PCC rule, and assigns QoS parameters to the PCC rule.
  • PCC rule authorization is performed by the PCF, authorizes the PCC rule, and assigns QoS parameters to the PCC rule.
  • the third step associates the PCC rule with the QoS flow in the PDU session.
  • the binding is performed using the following binding parameters (English: QoS flow binding is the association of a PCC rule to a QoS Flow within a PDU Session.
  • the binding is performed using the following binding parameters:
  • the PCC rule includes one or more of the following parameters, one or more of the following parameters can also be used as binding parameters:
  • QNC the related description can refer to the above-mentioned QoS parameter part, which will not be repeated here.
  • Priority indicates the priority of scheduling resources in the QoS flow. Priority should be used to differentiate QoS flows from the same end device, and also to differentiate QoS flows from different end devices.
  • Average window the average window is only used for GBR QoS flow, which represents the duration of calculating GFBR and MFBR.
  • MDBV indicates the maximum amount of data that the 5G access network is required to serve within a packet delay budget (PDB). Among them, the PDB defines the upper limit of the time that a data packet can be delayed in transmission between the terminal device and the UPF network element with the N6 interface.
  • PDB packet delay budget
  • the above-mentioned priority, average window or maximum data burst volume may also be parameters in the QoS attribute corresponding to the above-mentioned 5QI, which is not specifically limited here.
  • the charging identification information may be used as a binding parameter.
  • the charging identification information in the embodiment of the present application is used to identify the corresponding charging policy, which is uniformly described here, and will not be repeated below.
  • the N4 interface is the interface between the SMF and the UPF.
  • the SMF delivers the N4 rule including the PDR to the UPF to execute the corresponding control.
  • the PDR includes PDR ID, packet detection information (PDI), and forwarding action rule (FAR) ID, QoS enforcement rule (QoS enforcement rule, QER) ID and/or Statistics reporting rule (usage reporting rule, URR) ID, etc.
  • the FAR indicated by the FAR ID, the URR indicated by the URR ID, and the QER indicated by the QER ID are flow actions associated with the PDR.
  • the PDI contains one or more matching fields.
  • the UPF When the corresponding fields of the ingress data flow and all the matching fields in the PDI are successfully matched, the UPF considers that the matching is passed. Further, the UPF may perform drop, forward, buffer, report to the control plane (notify) or duplicate (duplicate) operations on the packet according to the FAR. UPF can perform QoS operations on packets based on QER. UPF can report statistics on packets based on URR.
  • At least one item(s) below or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s).
  • at least one (a) of a, b, or c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c may be single or multiple .
  • words such as "first” and "second” are used to distinguish the same or similar items with basically the same function and effect.
  • words “first”, “second” and the like do not limit the quantity and execution order, and the words “first”, “second” and the like are not necessarily different.
  • words such as “exemplary” or “for example” are used to represent examples, illustrations or illustrations. Any embodiments or designs described in the embodiments of the present application as “exemplary” or “such as” should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as “exemplary” or “such as” is intended to present the related concepts in a specific manner to facilitate understanding.
  • the network architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute limitations on the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • a communication system 60 is provided in an embodiment of the present application.
  • the communication system 60 includes a user plane functional entity 601 and an access network device 602 .
  • the user plane functional entity 601 and the access network device 602 may communicate directly or communicate through forwarding by other devices, which is not specifically limited in this embodiment of the present application.
  • the access network device 602 is configured to send a derived data packet of the discarded first downlink data packet to the user plane functional entity 601 after determining that the discarding information of the downlink data packet needs to be reported.
  • the derived data packet is obtained according to the first downlink data packet, and the derived data packet includes a first identifier, and the first identifier is used to indicate that the first downlink data packet is a discarded data packet.
  • the user plane functional entity 601 is configured to receive a derivative data packet of the first downlink data packet from the access network device 602, and determine that the first downlink data packet is a discarded data packet according to the first identifier in the derivative data packet Afterwards, the data usage update information is sent to the session management entity, wherein the data usage update information is used to deduct the data usage information of 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.
  • the access network device discards the downlink data packets
  • the data usage information of the downlink data packets that have been counted will be deducted. This ensures that the session management entity obtains more accurate data usage information. Further, when the session management entity interacts with the charging function entity, the charging function entity can obtain more accurate data consumption information, thereby realizing more accurate charging.
  • a communication system 70 is provided in an embodiment of the present 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 may communicate directly or communicate through forwarding by other devices, which is not specifically limited in this embodiment of the present application.
  • the session management entity 701 is configured to send the first message to the access network device 702 after determining that the discarding information of the downlink data packet needs to be reported.
  • the first message includes second indication information, and the second indication information indicates that the discarding information of the downlink data packet needs to be reported.
  • the access network device 702 is configured to receive the first message from the session management entity 701, and after determining the discarding information of the downlink data packets of the charging object according to the second indication information, send the second message to the session management entity 701, the first The second message includes the information of the charging object and the discarding information of the downlink data packet corresponding to the charging object.
  • the session management entity 701 is configured to receive the second message from the access network device 702, and update the data consumption information of the charging object according to the information of the charging object and the discarding information of the downlink data packet corresponding to the charging object, wherein, In the updated data usage information, the data usage information of the discarded downlink data packets in the charging object is deducted.
  • the session management entity can obtain the updated data usage information, and the downlink data packets in the charging object have been discarded in the updated data usage information. data usage information is deducted.
  • the access network device discards the downlink data packets containing the charging object
  • the data consumption information of these downlink data packets that have been charged will be deducted.
  • the session management entity obtains more accurate data usage information for the charging object.
  • the charging function entity can obtain more accurate data consumption information for the charging object, thereby realizing more accurate charging for the charging object.
  • the access network device 702 is configured to determine the discarding information of the downlink data packet that needs to be reported, and determine the first downlink data packet according to the charging identification information in the received downlink data packet. After discarding the information, a third message is sent to the session management entity 701, wherein 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 first downlink data Packet discard information.
  • the session management entity 701 is configured to receive the third message from the access network device 702, and update the data consumption information of the first downlink data packet according to the first charging identification information and the discard information of the first downlink data packet, The data consumption information of the discarded first downlink data packet in the updated data consumption information is deducted.
  • the session management entity can obtain the updated data consumption information, and the first downlink data in the updated data consumption information Data usage information for row packets is deducted.
  • the data usage information of these downlink data packets that have been charged will be deducted.
  • the charging function entity can obtain more accurate data consumption information of the granularity of the charging identification information, thereby realizing more accurate charging of the granularity of the charging identification information.
  • the access network device in this embodiment of the present application may be any communication device with a wireless transceiver function that is used to communicate with a terminal device.
  • the access network equipment includes but is not limited to: evolved node B (evolved node B, eNB), baseband unit (baseband unit, BBU), access point (access point, wireless fidelity, WIFI) system AP), wireless relay node, wireless backhaul node, transmission point (TP) or TRP, etc.
  • the access network device may also be a RAN device in a 5G system, for example, the RAN device includes a gNB or TRP or TP, or one or a group (including multiple antenna panels) antenna panels of a base station in the 5G system.
  • the RAN device may also be a network node that constitutes a gNB or TP, such as a BBU, or a distributed unit (distributed unit, DU).
  • a gNB may include a centralized unit (CU) and a DU.
  • the gNB may also include an active antenna unit (active antenna unit, AAU).
  • the CU implements some functions of the gNB, and the DU implements some functions of the gNB.
  • the CU is responsible for processing non-real-time protocols and services, and implementing functions of radio resource control (RRC) and packet data convergence protocol (PDCP) layers.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • the DU is responsible for processing physical layer protocols and real-time services, implementing the functions of the radio link control (RLC) layer, media access control (MAC) layer and physical (physical, PHY) layer.
  • RLC radio link control
  • MAC media access control
  • PHY physical layer
  • the access network device may be a device including one or more of a CU node, a DU node, and an AAU node.
  • the communication system 60 shown in FIG. 6 or the communication system 70 shown in FIG. 7 may be applicable to the 5G network currently under discussion, and may also be applicable to other future networks, etc., which is not specifically described in this embodiment of the present application. limited.
  • the network element or entity corresponding to the above access network device may be as shown in FIG. 2a or the RAN device in the 5G network described in Figure 2b; the network element or entity corresponding to the above-mentioned user plane functional entity may be the UPF in the 5G network described in Figure 2a or Figure 2b; the network element or entity corresponding to the above-mentioned session management entity.
  • the element or entity may be the SMF in the 5G network described in Figure 2a or Figure 2b.
  • the user plane function entity, session management entity, or access network device in this embodiment of the present application may also be referred to as a communication device, which may be a general-purpose device or a dedicated device, which is not made in this embodiment of the present application. Specific restrictions.
  • the user plane function entity, the session management entity, or the related functions of the access network device in the embodiment of the present application may be implemented by one device, may be implemented jointly by multiple devices, or may be implemented by one device in one device. or multiple functional modules, which is not specifically limited in this embodiment of the present application. It is to be understood that the above-mentioned functions can be either network elements in hardware devices, or software functions running on dedicated hardware, or a combination of hardware and software, or instantiated on a platform (eg, a cloud platform). Virtualization capabilities.
  • FIG. 8 is a schematic structural diagram of a communication apparatus 800 according to an embodiment of the present application.
  • the communication device 800 includes one or more processors 801, a communication line 802, and at least one communication interface (in FIG. 8, the communication interface 804 and one processor 801 are used as an example for illustration only), optional
  • the memory 803 may also be included.
  • the processor 801 may be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more processors for controlling the execution of the programs of the present application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication line 802 may include a path for connecting the various components.
  • the communication interface 804 can be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, wireless local area networks (wireless local area networks, WLAN) and the like.
  • the transceiver module may be a device such as a transceiver or a transceiver.
  • the communication interface 804 may also be a transceiver circuit located in the processor 801 to implement signal input and signal output of the processor.
  • the memory 803 may be a device having a storage function. For example, it may be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or other types of storage devices that can store information and instructions
  • the dynamic storage device can also be electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact discs, laser discs, compact discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or capable of carrying or storing desired program code in the form of instructions or data structures and capable of being stored by a computer any other medium taken, but not limited to this.
  • the memory may exist independently and be connected to the processor through communication line 802 .
  • the memory can also be integrated with the processor.
  • the memory 803 is used for storing computer-executed instructions for executing the solution of the present application, and the execution is controlled by the processor 801 .
  • the processor 801 is configured to execute the computer-executed instructions stored in the memory 803, thereby implementing the data usage update method provided in the embodiment of the present application.
  • the processor 801 may also perform processing-related functions in the data usage update method provided by the following embodiments of the present application, and the communication interface 804 is responsible for communicating with other devices or communication networks, This embodiment of the present application does not specifically limit this.
  • the computer-executed instructions in the embodiment of the present application may also be referred to as application code, which is not specifically limited in the embodiment of the present application.
  • the processor 801 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 8 .
  • the communication apparatus 800 may include multiple processors, for example, the processor 801 and the processor 808 in FIG. 8 .
  • Each of these processors can be a single-core processor or a multi-core processor.
  • the processor here may include, but is not limited to, at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller (MCU), or artificial intelligence Processors and other types of computing devices that run software, each computing device may include one or more cores for executing software instructions to perform operations or processing.
  • the communication apparatus 800 may further include an output device 805 and an input device 806 .
  • the output device 805 is in communication with the processor 801 and can display information in a variety of ways.
  • 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 (projector) Wait.
  • Input device 806 is in communication with processor 801 and can receive user input in a variety of ways.
  • the input device 806 may be a mouse, a keyboard, a touch screen device or a sensing device, or the like.
  • the above-mentioned communication apparatus 800 may also be sometimes referred to as a communication apparatus, which may be a general-purpose device or a dedicated device.
  • the communication device 800 may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, the above-mentioned terminal device, the above-mentioned network device, or a 8 devices of similar structure.
  • PDA personal digital assistant
  • This embodiment of the present application does not limit the type of the communication apparatus 800 .
  • a method for updating data usage includes the following steps:
  • the access network device determines that the discarding information of the downlink data packet needs to be reported.
  • the discarding information in this embodiment of the present application includes the discarded traffic value or the number of discarded data packets.
  • the access network device determining that the discard information of the downlink data packet needs to be reported includes: the access network device determines that the discard information of the downlink data packet needs to be reported according to the first indication information from the session management entity, and the first The indication information indicates that the discarding information of the downlink data packet needs to be reported.
  • the first indication information may be first charging identification information, and the first charging identification information is used to identify a corresponding charging policy.
  • the above-mentioned first indication information is further used to indicate the content of the discarding information, such as the discarded traffic value or the number of discarded data packets.
  • the access network device may also receive fourth indication information from the session management entity, and the fourth indication information is used to indicate the content of the discard information, which is not specifically limited in the embodiment of the present application.
  • determining that the access network device needs to report the discarding information of the downlink data packet includes: the access network device determines that the discarding information of the downlink data packet needs to be reported according to the local configuration, for example, the access network device needs to report the discarding information of the downlink data packet according to the local configuration.
  • the slice information of the session is determined to determine that a certain session needs to report the discarding information of downlink data packets.
  • the access network device sends a derived data packet of the discarded first downlink data packet to the user plane functional entity.
  • the user plane functional entity receives the derivative data packet of the first downlink data packet from the access network device.
  • the derived data packet is obtained according to the first downlink data packet, and the derived data packet includes a first identifier, and the first identifier is used to indicate that the first downlink data packet is a discarded data packet.
  • the function of the derived data packet of the first downlink data packet can be used to identify the first downlink data packet.
  • the derivative data packet of the first downlink data packet may be, for example, a data packet including the first identifier and the duplicated data of the first downlink data packet; or, the derivative data packet of the first downlink data packet may be, for example, A data packet that includes a first identifier and information that can identify the service flow of the first downlink data packet and information about the data consumption of the first downlink data packet.
  • the content is not specifically limited.
  • the user plane functional entity determines, according to the first identifier in the derived data packet, that the first downlink data packet is a discarded data packet.
  • the user plane function entity sends the data usage update information to the session management entity.
  • 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.
  • the user plane functional entity sends the data usage update information to the session management entity, including: the user plane functional entity adds a discarded packet flag in the derived data packet, and according to the first URR associated with the first PDR
  • the data usage update information is reported to the session management entity, wherein the first URR is a negative URR (ie, the measured usage is a negative value, the same below), and the first PDR includes a PDI for detecting discarded packet flags.
  • the user plane functional entity sends the data usage update information to the session management entity, including: the user plane functional entity adds a discarded packet flag to the data packet after discarding the first identifier in the derived data packet, And the data usage update information is reported to the session management entity according to the first URR associated with the first PDR, where the first URR is a negative URR, and the first PDR includes a PDI for detecting a discarded packet flag.
  • the user plane functional entity sends the data usage update information to the session management entity, including: the user plane functional entity updates the data usage update information according to the negative URR associated with the matched PDR of the detected uplink data packet. Report to the session management entity.
  • the data usage update information may be the updated data usage obtained by the user plane functional entity after deducting the data usage of the first downlink data packet according to the internally counted data usage;
  • the data usage update information may be the data usage of the first downlink data packet, and the data usage of the first downlink data packet is used to update the data usage that the user plane functional entity has reported to the session management entity.
  • the data usage of the first downlink data packet is deducted from the data usage that the functional entity has reported to the session management entity.
  • the data usage update information may deduct the data usage of the first downlink data packet.
  • the user plane functional entity may obtain the first PDR and the first URR in the following manner.
  • the user plane function entity receives the first rule from the session management entity, and the first rule includes the first PDR and the first URR and the second URR associated with the first PDR; wherein, the second URR is Positive URR.
  • the measurement object corresponding to the second URR and the first URR is the same.
  • the first PDR in this embodiment of the present application may be a PDI that detects a discarded packet flag bit added to the current PDR, and associates the first URR opposite to the second URR. That is, in the embodiment of the present application, the first PDR further includes a PDI for detecting the first downlink data packet. Wherein, when the first PDR detects the first downlink data packet, the second URR associated with the first PDR is used for statistical reporting; or, when the first PDR detects the discarded packet flag bit, the first PDR associated with the first PDR is used. A URR for statistical reporting.
  • the PDI that detects the first downlink data packet in the first PDR in the embodiment of the present application may also detect other downlink data packets other than the first data packet, which is not specifically limited in the embodiment of the present application.
  • the user plane function entity receives the second rule from the session management entity, where the second rule includes the first PDR and the first URR associated with the first PDR, the third PDR and the third PDR associated with the third PDR
  • the third URR wherein the third PDR includes the 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.
  • the first PDR and the first URR associated with the first PDR in this embodiment of the present application are newly added.
  • the second rule in this embodiment of the present application includes a third PDR and a third URR associated with the third PDR.
  • the third PDR detects the first data packet
  • the third URR associated with the third PDR is used for statistical reporting; or, when the first PDR detects the discarded packet flag, the first URR associated with the first PDR is used.
  • Statistical reporting when the third PDR detects the first data packet, the third URR associated with the third PDR is used for statistical reporting; or, when the first PDR detects the discarded packet flag, the first URR associated with the first PDR is used.
  • the PDI that detects the first downlink data packet in the third PDR in the embodiment of the present application may also detect other downlink data packets other than the first data packet, which is not specifically limited in the embodiment of the present application.
  • the data usage update method provided by the embodiment of the present application may further include: the user plane function entity receives a subscription message from the session management entity, where the subscription message is used to request subscription to a data usage change event. That is, in the embodiment of the present application, the user plane functional entity may report the data usage information to the session management entity based on the subscription request of the session management entity.
  • 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.
  • the data usage information of the downlink data packets that have been counted will be deducted. This ensures that the session management entity obtains more accurate data usage information.
  • the charging function entity can obtain more accurate data consumption information, thereby realizing more accurate charging.
  • the actions of the user plane functional entity in the above steps S901 to S904 may be executed by the processor 801 in the communication device 800 shown in FIG. 8 by calling the application code stored in the memory 803 to instruct the user plane functional entity to execute.
  • the action of the access network device in S904 may be performed by the processor 801 in the communication apparatus 800 shown in FIG. 8 calling the application program code stored in the memory 803 to instruct the access network device to execute.
  • the action may be executed by the processor 801 in the communication apparatus 800 shown in FIG. 8 by calling the application code stored in the memory 803 to instruct the session management entity to execute, which is not limited in this embodiment.
  • a method for updating data usage includes the following steps:
  • the session management entity determines that the discarding information of the downlink data packet needs to be reported.
  • the discarding information in this embodiment of the present application includes the discarded traffic value or the number of discarded data packets, and the like.
  • the session management entity determines that the discarding information of the downlink data packet needs to be reported, including: the session management entity determines the discarding information of the downlink data packet that needs to be reported according to the third indication information from the policy control entity, wherein the said The third indication information indicates that the discarding information of the downlink data packet needs to be reported.
  • determining that the session management entity needs to report the discarding information of the downlink data packet includes: the session management entity determines that the discarding information of the downlink data packet needs to be reported according to the local configuration.
  • the session management entity sends a first message to the access network device.
  • the access network device receives the first message from the session management entity.
  • the first message includes second indication information, and the second indication information indicates that the discarding information of the downlink data packet needs to be reported.
  • the access network device determines discarding information of downlink data packets of the charging object according to the second indication information.
  • the access network device sends a second message to the session management entity.
  • the session management entity receives the second message from the access network device.
  • the second message includes the information of the charging object and the discarding information of the downlink data packet corresponding to the charging object.
  • the session management entity updates the data consumption information of the charging object according to the information of the charging object and the discarding information of the downlink data packets corresponding to the charging object, wherein the downlink data has been discarded in the charging object in the updated data consumption information Packet data usage information is deducted.
  • the first message includes a flow identifier of the first QoS flow; the charging object is the first QoS flow, and the information of the charging object is the flow identifier of the first QoS flow
  • the first QoS flow is a QoS flow bound to the first charging policy rule (it may also be understood that the first QoS flow is a QoS flow bound to the first charging policy rule)
  • the binding parameter of the first charging policy rule includes the first charging identification information
  • the first charging identification information is used to identify the corresponding charging policy. That is, in the embodiment of the present application, the first charging identification information may be used as a binding parameter when QoS flows are bound, so that data usage statistics at the QoS flow granularity can be implemented, and further charging at the QoS flow granularity can be implemented.
  • the second indication information in the first message is the first charging identification information, and the first charging identification information is used to identify the corresponding charging policy; the charging object is that the binding parameter includes the first charging identification information.
  • One or more QoS flows to which the charging policy rule of the charging identification information is bound it can also be understood that the charging object is one or more QoS flows bound to the charging policy rule whose binding parameter contains the first charging identification information multiple QoS flows); the information of the charging object is the first charging identification information.
  • the first charging identification information can be used as a binding parameter when QoS flows are bound, so that data usage statistics at the granularity of the charging identification identification can be implemented, and further charging at the granularity of the charging identification identification can be implemented.
  • the first message is further used to indicate the content of the discard information, such as the discarded traffic value or the number of discarded data packets.
  • the parameter used to indicate the content of the discard information may be, for example, the above-mentioned second indication information.
  • the session management entity may also indicate the content of the discard information through other information in the first message, or the session management entity may also indicate the content of the discard information through other methods, which is not specifically limited in this embodiment of the present application.
  • FIG. 11 For the specific implementation of the embodiment shown in FIG. 11 , reference may be made to the embodiment shown in the subsequent FIG. 16 or FIG. 17 , which will not be repeated here.
  • the session management entity can obtain the updated data usage information, and the downlink data packets in the charging object have been discarded in the updated data usage information. data usage information is deducted.
  • the data consumption information of these downlink data packets that have been charged will be deducted. In this way, it can be ensured that the session management entity obtains more accurate data usage information for the charging object. Further, when the session management entity interacts with the charging function entity, the charging function entity can obtain more accurate data consumption information for the charging object, thereby realizing more accurate charging for the charging object.
  • the actions of the access network equipment in the above steps S1101 to S1105 can be performed by the processor 801 in the communication apparatus 800 shown in FIG. 8 calling the application program code stored in the memory 803 to instruct the access network equipment to execute.
  • the action of the session management entity in S1105 may be executed by the processor 801 in the communication apparatus 800 shown in FIG. 8 by calling the application code stored in the memory 803 to instruct the session management entity to execute, which is not limited in this embodiment.
  • a method for updating data usage includes the following steps:
  • the access network device determines that the discarding information of the downlink data packet needs to be reported.
  • step S1201 For the specific implementation of step S1201, reference may be made to step S901 in the embodiment shown in FIG. 9 , which will not be repeated here.
  • the access network device determines discarding information of the first downlink data packet according to the charging identification information in the received downlink data packet.
  • the first downlink data packet is a downlink data packet including the first charging identification information.
  • the access network device sends a third message to the session management entity.
  • the session management entity receives the third message from the access network device.
  • the third message includes the first charging identification information and the discarding information of the first downlink data packet.
  • the session management entity updates the data usage information of the first downlink data packet according to the first charging identification information and the discard information of the first downlink data packet.
  • the data consumption information of the discarded first downlink data packet in the updated data consumption information is deducted.
  • the method for updating data usage may further include: the session management entity sends fifth indication information to the user plane entity, where the fifth indication information instructs the user plane entity to add charging identification information to the downlink data packet.
  • the session management entity can obtain the updated data consumption information, and the first downlink data in the updated data consumption information Data usage information for row packets is deducted.
  • the data usage information of these downlink data packets that have been charged will be deducted.
  • the charging function entity can obtain more accurate data consumption information of the granularity of the charging identification information, thereby realizing more accurate charging of the granularity of the charging identification information.
  • the actions of the access network equipment in the above steps S1201 to S1204 can be executed by the processor 801 in the communication apparatus 800 shown in FIG.
  • the action of the session management entity in S1204 may be instructed by the processor 801 in the communication apparatus 800 shown in FIG. 8 to call the application code stored in the memory 803 to instruct the session management entity to execute, which is not limited in this embodiment.
  • the data usage update method includes the following steps:
  • the SMF sends the first indication information to the RAN device.
  • the RAN device receives the first indication information from the SMF, and the first indication information indicates that the RAN device needs to report the discarding information of the downlink data packets.
  • the SMF can send the first indication information to the RAN device according to the local configuration, the first indication information Indicates that the RAN device needs to report the discarding information of downlink data packets for a specific service, a specific session or a specific slice.
  • the SMF may receive indication information from the PCF, where the indication information indicates that the RAN device needs to report the discarding information of downlink data packets for a specific service or a specific session or a specific slice. Further, the SMF may send first indication information to the RAN device according to the indication information, where the first indication information indicates that the RAN device needs to report the discarding information of downlink data packets for a specific service, a specific session or a specific slice.
  • the first indication information may further indicate the content of the discard information, such as the discarded traffic value or the number of discarded data packets, which is not specifically limited in this embodiment of the present application.
  • the SMF may also indicate to the RAN device the content of the discard information that needs to be reported in other ways, which is not specifically limited in this embodiment of the present application.
  • the RAN device determines that the discarding information of the downlink data packet needs to be reported.
  • the RAN device may determine, according to the foregoing first indication information, that the discarding information of the downlink data packet needs to be reported.
  • the RAN device may determine, according to the local configuration, that it needs to report the discarding information of the downlink data packets. For example, assuming that the RAN device is locally configured with information about services, sessions or slices that need to report discarding information of downlink packets, the RAN device can determine, according to the local configuration, that the discarding of downlink packets needs to be reported for a specific service, a specific session, or a specific slice. information.
  • the RAN device discards the first downlink data packet.
  • the RAN device may discard the first downlink data packet due to factors such as traffic shaping or congestion, which is not specifically limited in this embodiment of the present application.
  • the RAN device sends a derived data packet of the discarded first downlink data packet to the UPF.
  • the UPF receives the derivative data packet of the first downlink data packet from the RAN device.
  • the derived data packet of the first downlink data packet reference may be made to the embodiment shown in FIG. 9 , which will not be repeated here.
  • the RAN device sends the derived data packet of data packet 1 (denoted as data) to the UPF. packet 11), a derived packet of packet 2 (denoted as packet 21), and a derived packet of packet 3 (denoted as packet 31).
  • the data packet 11 includes the content of the data packet 1 transmitted downstream
  • the data packet 21 includes the content of the data packet 2 transmitted downstream
  • the data packet 31 includes the content of the data packet 3 transmitted downstream.
  • the data packet 11, the data packet 21 and the data packet 31 further include the first identifier.
  • the first identifier may be carried in the data packet header, such as being represented by a reserved bit of the data packet header.
  • the first identifier may be added to the GTP-U upstream packet header.
  • the destination tunnel identifier in the GTP-U uplink packet header is the tunnel identifier of the UPF.
  • the example shown in FIG. 13 is only a possible form of the derived data packet. As described in the embodiment shown in FIG. 9 , the derived data packet may also exist in other forms, which are not implemented in this embodiment of the present application. Specific restrictions.
  • the UPF determines, according to the first identifier in the derived data packet, that the first downlink data packet is a discarded data packet.
  • the UPF sends the data usage update information to the SMF. Accordingly, the SMF receives the data usage update information from the UPF. The data usage update information is used to deduct the data usage of the first downlink data packet.
  • the data packet A is a normal uplink data packet and does not contain the first identifier; the data packet 11 , the data packet 21 , and the data packet 31 all contain the first identifier.
  • the UPF processes the data packet A normally.
  • data packet 21 and data packet 31 after the UPF performs data packet matching according to the PDI in the PDR used to detect the upstream data packet and the matching is passed, the UPF can determine, according to the first identifier, that the first downstream data packet is Packet dropped.
  • the UPF can discard the first identifier in the data packet 11, the data packet 21 and the data packet 31, and after adding the discarded packet flag (the negative value flag in Figure 15), the PDR for detecting the downlink data packet is passed
  • the PDI in the PDU continues to be matched (because the content of the PDU session layer remains unchanged (take the IP layer as an example, the destination IP address here is still the IP address of the terminal device), so data packets 11, 21 and 31 can still be viewed as for downstream data packets).
  • the UPF reports the data usage update information to the SMF according to the first URR associated with the first PDR. For example, it is assumed that the data usage of the data package 1, the data package 2 and the data package 3 is 3M, then the data usage update information at this time is used to deduct the data usage of the 3M.
  • the UPF may not discard the first identifier, but directly add the discarded packet flag in the derived data packet, and then continue to match through the PDI in the PDR used to detect the downlink data packet. . After the data packet 11, the data packet 21, and the data packet 31 match the PDI in the first PDR that detects the discarded packet flag, the UPF reports the data usage update information to the SMF according to the first URR associated with the first PDR.
  • the UPF can determine the first downlink data according to the first identifier
  • the packet is a dropped packet.
  • the UPF may calculate the data usage according to the matched negative URR associated with the PDR for detecting the uplink data packet (that is, in this embodiment of the present application, the PDR for detecting the uplink data packet may be associated with a negative URR that is opposite to the positive URR).
  • the update information is reported to the SMF, which is not specifically limited in this embodiment of the present application.
  • the data usage update information may be the updated information obtained by the UPF after deducting the data usage of the first downlink data packet according to the data usage already counted in the UPF.
  • Data usage; or, the data usage update information may be the data usage of the first downlink data packet, which is not specifically limited in this embodiment of the present application.
  • the charging event is reported immediately after "traffic threshold is reached", and the parameter is 10MB (that is, when there is 10MB remaining in the quota, a charging event will be triggered).
  • UPF will deduct 3M from the already counted data usage after detecting data packet 11, data packet 21 and data packet 31 when the data usage is counted, so as to obtain the updated data usage (for example, the already counted data flow is: 15M, after detecting the data packet 11, the data packet 21 and the data packet 31, the data traffic that has been counted is updated to 12M).
  • the "traffic threshold reached" charging event is triggered, and the UPF will report the data usage information to the SMF.
  • the UPF can directly send the data usage (3M) of the data packets 11, 21 and 31 to the SMF, so that the SMF updates the UPF and has been reported to the SMF.
  • the data usage of the SMF is not specifically limited in this embodiment of the present application.
  • the quota and charging events reference may be made to the description of the "charging process" in the preamble of the specific implementation manner, which will not be repeated here.
  • the method may further include: the SMF sends a subscription message to the UPF. Accordingly, the UPF receives the subscription message from the SMF.
  • the subscription message is used to request subscription data usage change event (or billing update event).
  • the data usage change event may be, for example, that the data usage information is changed.
  • the actions of the UPF in the above steps S1301 to S1306 can be executed by the processor 801 in the communication apparatus 800 shown in FIG. 8 calling the application code stored in the memory 803 to instruct the UPF to execute, and the actions of the RAN device in the above steps S1301 to S1306
  • the application code stored in the memory 803 may be called by the processor 801 in the communication apparatus 800 shown in FIG. 8 to instruct the RAN device to execute, and the actions of the SMF in the above steps S1301 to S1306 may be executed by the communication apparatus 800 shown in FIG. 8 .
  • the processor 801 calls the application code stored in the memory 803 to instruct the SMF to execute, which is not limited in this embodiment.
  • the data usage update method includes the following steps:
  • the PCF sends third indication information to the SMF.
  • the RAN device receives the third indication information from the SMF, and the third indication information indicates that the RAN device needs to report the discarding information of the downlink data packet.
  • the third indication information may be carried in the PCC rule sent by the PCF to the SMF.
  • the third indication information may further indicate the content of the discard information, such as the discarded traffic value or the number of discarded data packets, which is not specifically limited in the embodiment of the present application.
  • the PCF may also indicate to the SMF the content of the discard information to be reported in other ways, which is not specifically limited in this embodiment of the present application.
  • the SMF determines that the RAN device needs to report the discarding information of the downlink data packet.
  • the SMF may determine, according to the foregoing third indication information, that the RAN device needs to report the discarding information of the downlink data packets.
  • the SMF may determine, according to the local configuration, that the RAN device needs to report the discarding information of the downlink data packets. For example, assuming that the SMF is locally configured with information about services, sessions or slices that need to report the discarding information of downlink packets, the SMF can determine, according to the local configuration, that the RAN device needs to report the discarding of downlink packets for a specific service, a specific session, or a specific slice. information.
  • the SMF uses the charging identification information as a binding parameter, and binds QoS flows with different charging identification information to different PCC rules.
  • the charging identification information in this embodiment of the present application may include, for example, a charging key or a monitoring key.
  • the charging identification information as a binding parameter, the data packets in the same QoS flow can have the same data usage statistics or charging methods.
  • binding parameters in this embodiment of the present application may also include other parameters, and for details, reference may be made to the relevant description of the "binding mechanism" in the preamble of the specific implementation manner, which will not be repeated here.
  • the first PCC rule in the embodiment of the present application is a specific form of the first charging policy rule in the embodiment shown in FIG. 11 .
  • the first charging policy rule may also have other forms, which are not specifically limited in this embodiment of the present application.
  • the SMF sends an N2 message 1 to the RAN device.
  • the RAN device receives the N2 message 1 from the SMF.
  • the N2 message 1 includes the QFI of the first QoS flow and the second indication information, and the second indication information indicates that the discarding information of the downlink data packet needs to be reported.
  • the first QoS flow is a QoS flow bound to the first PCC rule, and the binding parameter of the first PCC rule includes first charging identification information, and the first charging identification information is used to identify a corresponding charging policy.
  • the N2 message 1 may further indicate the content of the discard information, such as the discarded traffic value or the number of discarded data packets, which is not specifically limited in the embodiment of the present application.
  • the parameter used to indicate the content of the discard information may be, for example, the above-mentioned second indication information.
  • the SMF may also indicate the content of the discarding information through other information in the N2 message 1, or the SMF may also indicate the content of the discarding information in other ways, which is not specifically limited in this embodiment of the present application.
  • the QFI of the first QoS flow and the second indication information of the first QoS flow are included in the same message and sent as an example for illustration.
  • the QFI and the second indication information of the first QoS flow may also be included in different messages, which are not specifically limited in this embodiment of the present application.
  • N2 message 1 in the embodiment of the present application is only an example of the first message in FIG. 11 , and the first message may also be other, which is not specifically limited in the embodiment of the present application.
  • the RAN device determines, according to the second indication information, the discarding information of the downlink data packets of the charging object.
  • the RAN device may discard downlink data packets due to factors such as traffic shaping or congestion, which is not specifically limited in this embodiment of the present application.
  • the RAN sends an N2 message 2 to the SMF.
  • the SMF receives the N2 message 2 from the RAN device.
  • the N2 message 2 includes the QFI of the first QoS flow and the discarding information of the downlink data packets of the first QoS flow.
  • the SMF updates the data consumption information of the first QoS flow according to the QFI of the first QoS flow and the discarding information of the downlink data packets of the first QoS flow, wherein the discarded downlink data of the first QoS flow in the updated data consumption information
  • the data usage information of the packet is deducted.
  • N2 message 2 in the embodiment of the present application is only an example of the second message in FIG. 11 , and the second message may also be other, which is not specifically limited in the embodiment of the present application.
  • the embodiment shown in FIG. 16 is described by taking the charging object in the embodiment shown in FIG. 11 as the first QoS flow as an example, which can realize more accurate data usage information statistics of QoS flow granularity, so as to realize the QoS flow Granular and more accurate billing.
  • the technical effect analysis reference may be made to the technical effect analysis of the embodiment described in FIG. 11 , which will not be repeated here.
  • the actions of the RAN device in the above steps S1601 to S1607 can be executed by the processor 801 in the communication apparatus 800 shown in FIG. 8 by calling the application code stored in the memory 803 to instruct the RAN device to execute.
  • the action may be executed by the processor 801 in the communication apparatus 800 shown in FIG. 8 calling the application code stored in the memory 803 to instruct the SMF to execute, which is not limited in this embodiment.
  • the data usage update method includes the following steps:
  • S1701-S1703 are the same as the descriptions of steps S1601-S1603 in the embodiment shown in FIG. 16 .
  • steps S1601-S1603 are the same as the descriptions of steps S1601-S1603 in the embodiment shown in FIG. 16 .
  • the SMF sends an N2 message 3 to the RAN device.
  • the RAN device receives the N2 message 3 from the SMF.
  • the N2 message 3 includes the first charging identification information, and the first charging identification information is used to indicate that the discarding information of the downlink data packet needs to be reported.
  • the N2 message 3 may further indicate the content of the discard information, such as the discarded traffic value or the number of discarded data packets, which is not specifically limited in the embodiment of the present application.
  • the parameter used to indicate the content of the discard information may be, for example, the above-mentioned first charging identification information.
  • the SMF may also indicate the content of the discarding information through other information in the N2 message 3, or the SMF may also indicate the content of the discarding information in other ways, which is not specifically limited in this embodiment of the present application.
  • N2 message 3 in the embodiment of the present application is only an example of the first message in FIG. 11 , and the first message may also be other, which is not specifically limited in the embodiment of the present application.
  • the RAN device determines the discarding information of the downlink data packets of the charging object.
  • the RAN device may discard downlink data packets due to factors such as traffic shaping or congestion, which is not specifically limited in this embodiment of the present application.
  • the embodiment of the present application is described by taking the charging object as one or more QoS flows bound to the PCC rule whose binding parameter includes the first charging identification information as an example.
  • the RAN sends an N2 message 4 to the SMF. Accordingly, the SMF receives the N2 message 4 from the RAN device.
  • the N2 message 4 includes the first charging identification information and the discarding information of the downlink data packets of one or more QoS flows to which the PCC rule whose binding parameter includes the first charging identification information is bound.
  • N2 message 4 in the embodiment of the present application is only an example of the second message in FIG. 11 , and the second message may also be other, which is not specifically limited in the embodiment of the present application.
  • the SMF updates the downlink data packets of one or more QoS flows according to the first charging identification information and the discarding information of the downlink data packets of one or more QoS flows bound to the PCC rules whose binding parameters include the first charging identification information.
  • the data usage information wherein the data usage information of the discarded downlink data packets of one or more QoS flows bound to the PCC rule whose binding parameter includes the first charging identification information in the updated data usage information is deducted.
  • the embodiment shown in FIG. 17 is described by taking as an example that the charging object in the embodiment shown in FIG. 11 is one or more QoS flows bound to a charging policy rule whose binding parameter includes the first charging identification information , more accurate data usage information statistics of the granularity of the charging identification information can be realized, so that more accurate charging of the granularity of the charging identification information can be realized.
  • the charging object in the embodiment shown in FIG. 11 is one or more QoS flows bound to a charging policy rule whose binding parameter includes the first charging identification information , more accurate data usage information statistics of the granularity of the charging identification information can be realized, so that more accurate charging of the granularity of the charging identification information can be realized.
  • the technical effect analysis reference may be made to the technical effect analysis of the embodiment described in FIG. 11 , which will not be repeated here.
  • the actions of the RAN device in the above steps S1701 to S1707 can be executed by the processor 801 in the communication apparatus 800 shown in FIG. 8 by calling the application code stored in the memory 803 to instruct the RAN device to execute.
  • the action may be executed by the processor 801 in the communication apparatus 800 shown in FIG. 8 calling the application code stored in the memory 803 to instruct the SMF to execute, which is not limited in this embodiment.
  • the data usage update method includes the following steps:
  • S1801-S1802 are the same as steps S1301-S1302 in the embodiment shown in FIG. 13 , and the related description can refer to the embodiment shown in FIG. 13 , which will not be repeated here.
  • the SMF sends fifth indication information to the UPF.
  • the UPF receives the fifth indication information from the SMF, and the fifth indication information instructs the UPF to add charging identification information in the downlink data packet.
  • the UPF sends a downlink data packet to the RAN device.
  • the RAN device receives the downlink data packets from the UPF.
  • the downlink data packet includes corresponding charging identification information.
  • the RAN device determines discarding information of the first downlink data packet according to the charging identification information in the received downlink data packet.
  • the first downlink data packet is a downlink data packet including the first charging identification information.
  • the RAN device may discard downlink data packets due to factors such as traffic shaping or congestion, which is not specifically limited in this embodiment of the present application.
  • the RAN device sends an N2 message 5 to the SMF. Accordingly, the SMF receives the N2 message 5 from the RAN device.
  • the N2 message 5 includes the first charging identification information and the discarding information of the first downlink data packet.
  • N2 message 5 in the embodiment of the present application is only an example of the third message in FIG. 12 , and the third message may also be other, which is not specifically limited in the embodiment of the present application.
  • the SMF updates the data consumption information of the first downlink data packet according to the first charging identification information and the discard information of the first downlink data packet.
  • the data consumption information of the discarded first downlink data packet in the updated data consumption information is deducted.
  • the actions of the RAN device in the above steps S1801 to S1807 can be executed by the processor 801 in the communication apparatus 800 shown in FIG. 8 by calling the application code stored in the memory 803 to instruct the RAN device to execute.
  • the action may be executed by the processor 801 in the communication apparatus 800 shown in FIG. 8 calling the application code stored in the memory 803 to instruct the SMF to execute, which is not limited in this embodiment.
  • the methods and/or steps implemented by access network equipment may also be implemented by components (such as chips or circuits) that can be used for access network equipment; methods implemented by session management entities and/or steps can also be implemented by components (such as chips or circuits) available for session management entities; methods and/or steps implemented by user plane functional entities can also be implemented by components available for user plane functional entities (such as chips). or circuit) implementation.
  • an embodiment of the present application further provides a communication device, where the communication device is used to implement the above-mentioned various methods.
  • the communication device may be an access network device in the foregoing method embodiments, or a device including the foregoing access network device, or a component usable for access network devices; or, the communication device may be an access network device in the foregoing method embodiments A session management entity, or a device including the above session management entity, or a component that can be used for the session management entity; or, the communication device may be the user plane functional entity in the above method embodiment, or a device including the above user plane functional entity , or a component that can be used for a user plane functional entity. It can be understood that, in order to realize the above-mentioned functions, the communication apparatus includes corresponding hardware structures and/or software modules for executing each function.
  • the communication device may be divided into functional modules according to the above method embodiments.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. It should be noted that, the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation.
  • FIG. 19 shows a schematic structural diagram of a communication device 190 .
  • the communication device 190 includes a transceiver module 1901 and a processing module 1902 .
  • the transceiver module 1901 may also be called a transceiver unit to implement a transceiver function, for example, a transceiver circuit, a transceiver, a transceiver or a communication interface.
  • Transceiver module 1901 configured to receive a derivative data packet of a first downlink data packet from an access network device, wherein the derivative data packet is obtained according to the first downlink data packet, and the derivative data packet includes a first identifier .
  • the processing module 1902 is configured to determine, according to the first identifier, that the first downlink data packet is a discarded data packet.
  • the transceiver module 1901 is further configured to send data usage update information to the session management entity, where the data usage update information is used to deduct the data usage of the first downlink data packet.
  • the transceiver module 1901 is configured to send the data usage update information to the session management entity, including: adding a discarded packet flag in the derived data packet; updating the data usage update information according to the first URR associated with the first PDR. It is reported to the session management entity, wherein the first URR is a negative value URR, and the first PDR includes a PDI for detecting the discarded packet flag.
  • the transceiver module 1901 is configured to send data usage update information to the session management entity, including: adding a discarded packet flag to the packet after discarding the first identifier in the derived packet;
  • the associated first URR reports the data usage update information to the session management entity, where the first URR is a negative URR, and the first PDR includes a PDI for detecting the discarded packet flag.
  • the transceiver module 1901 is further configured to receive a first rule from a session management entity, where 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 positive Value URR.
  • the transceiver module 1901 is further configured to receive a second rule from the session management entity, where the second rule includes the first PDR, the first URR associated with the first PDR, the third PDR, and the third PDR associated with the third PDR.
  • the second rule includes the first PDR, the first URR associated with the first PDR, the third PDR, and the third PDR associated with the third PDR.
  • the transceiver module 1901 is further configured to receive a subscription message from the session management entity, where the subscription message is used to request subscription data usage change event information.
  • the processing module 1902 is configured to determine that the discarding information of the downlink data packet needs to be reported.
  • the transceiver module 1901 is configured to send a first message to the access network device, where the first message includes second indication information, and the second indication information indicates that the discarding information of the downlink data packet needs to be reported.
  • the transceiver module 1901 is further configured to receive a second message from the access network device, where the second message includes the information of the charging object and the discarding information of the downlink data packet corresponding to the charging object.
  • the processing module 1902 is further configured to update the data consumption information of the charging object according to the information of the charging object and the discarding information of the downlink data packet corresponding to the charging object, wherein, in the updated data consumption information, the charging object has been discarded
  • the data usage information of downlink packets is deducted.
  • the processing module 1902 is configured to determine that the discarding information of the downlink data packet needs to be reported.
  • the transceiver module 1901 is configured to send a derivative data packet of the discarded first downlink data packet to the user plane functional entity, wherein the derivative data packet is obtained according to the first downlink data packet, and the derivative data packet includes the first downlink data packet.
  • An identifier where the first identifier is used to indicate that the first downlink data packet is a discarded data packet.
  • the processing module 1902 is specifically configured to: determine the discarding information of the downlink data packet that needs to be reported according to the first indication information from the session management entity, where the first indication information indicates that the discarding information of the downlink data packet needs to be reported.
  • the processing module 1902 is specifically configured to: determine the discarding information of the downlink data packet that needs to be reported according to the local configuration.
  • the processing module 1902 is configured to determine that the discarding information of the downlink data packet needs to be reported, including: determining the discarding information of the downlink data packet that needs to be reported according to the third indication information from the policy control entity, wherein the third indication information indicates The discarding information of downlink packets needs to be reported.
  • the processing module 1902 is configured to determine that the discarding information of the downlink data packet needs to be reported, including: determining the discarding information of the downlink data packet that needs to be reported according to the local configuration.
  • the transceiver module 1901 is configured to receive a first message from a session management entity, where the first message includes second indication information; the second indication information indicates that the downlink data packet discard information needs to be reported.
  • the processing module 1902 is configured to determine discarding information of downlink data packets of the charging object according to the second indication information.
  • the transceiver module 1901 is further configured to send a second message to the session management entity, where the second message includes the information of the charging object and the discarding information of the downlink data packet corresponding to the charging object.
  • the communication device 190 is presented in the form of dividing each functional module in an integrated manner.
  • Module herein may refer to a specific ASIC, circuit, processor and memory executing one or more software or firmware programs, integrated logic circuit, and/or other device that may provide the functions described above.
  • the communication device 190 may take the form of the communication device 800 shown in FIG. 8 .
  • the processor 801 in the communication apparatus 800 shown in FIG. 8 may call the computer execution instructions stored in the memory 803 to make the communication apparatus 800 execute the data usage update method in the above method embodiment.
  • the function/implementation process of the transceiver module 1901 and the processing module 1902 in FIG. 19 can be implemented by the processor 801 in the communication apparatus 800 shown in FIG. 8 calling the computer execution instructions stored in the memory 803 .
  • the function/implementation process of the processing module 1902 in FIG. 19 can be implemented by the processor 801 in the communication device 800 shown in FIG. 8 calling the computer-executed instructions stored in the memory 803, and the function of the transceiver module 1901 in FIG. 19 can be implemented.
  • the implementation process can be implemented through the communication interface 804 in the communication device 800 shown in FIG. 8 .
  • the communication device 190 provided in this embodiment can execute the above-mentioned data usage update method, the technical effects that can be obtained can be referred to the above-mentioned method embodiments, and details are not repeated here.
  • one or more of the above modules or units may be implemented by software, hardware or a combination of both.
  • the software exists in the form of computer program instructions and is stored in the memory, and 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 chip) or an ASIC, or it can be an independent semiconductor chip.
  • SoC system on chip
  • ASIC application specific integrated circuit
  • the internal processing of the processor may further include necessary hardware accelerators, such as field programmable gate array (FPGA), PLD (Programmable Logic Device) , or a logic circuit that implements dedicated logic operations.
  • FPGA field programmable gate array
  • PLD Programmable Logic Device
  • the hardware can be CPU, microprocessor, digital signal processing (DSP) chip, microcontroller unit (MCU), artificial intelligence processor, ASIC, Any or any combination of SoCs, FPGAs, PLDs, dedicated digital circuits, hardware accelerators, or non-integrated discrete devices that may or may not run the necessary software to perform the above method flows.
  • DSP digital signal processing
  • MCU microcontroller unit
  • ASIC any or any combination of SoCs, FPGAs, PLDs, dedicated digital circuits, hardware accelerators, or non-integrated discrete devices that may or may not run the necessary software to perform the above method flows.
  • an embodiment of the present application further provides a chip system, including: at least one processor and an interface, the at least one processor is coupled to the memory through the interface, and when the at least one processor executes the computer program or instruction in the memory , the method in any of the above method embodiments is executed.
  • the communication device further includes a memory.
  • the chip system may be composed of chips, or may include chips and other discrete devices, which are not specifically limited in this embodiment of the present application.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • a software program it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line, DSL) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or data storage devices including one or more servers, data centers, etc. that can be integrated with the medium.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Meter Arrangements (AREA)

Abstract

本申请实施例提供数据用量更新方法、装置及***，能够提升数据用量统计结果的准确性。方法包括：用户面功能实体接收来自接入网设备的第一下行数据包的派生数据包，其中，该派生数据包是根据该第一下行数据包得到的，该派生数据包中包括第一标识；用户面功能实体根据该第一标识，确定该第一下行数据包为已丢弃数据包；用户面功能实体向会话管理实体发送数据用量更新信息，其中，该数据用量更新信息用于将该第一下行数据包的数据用量扣减。

Description

数据用量更新方法、装置及*** 技术领域
本申请涉及通信领域，尤其涉及数据用量更新方法、装置及***。
背景技术
现有的服务质量(quality of service，QoS)控制机制中，定义了聚合级别的QoS参数，如用户设备(user equipment，UE)-聚合最大比特率(aggregate maximum bit rate，AMBR)、会话AMBR(session-AMBR)以及切片最大比特率(slice maximum bitrate)等。其中，UE-AMBR用于控制终端设备的所有非保证比特率(non-guaranteed bit rate，non-GBR)的QoS流(QoS flow)(即non-GBR QoS flow)的聚合比特率，由无线接入网(radio access network，RAN)设备执行控制。session-AMBR用于控制终端设备的一个协议数据单元(protocol data unit，PDU)会话中的所有non-GBR QoS flow的聚合最大比特率，由终端设备和用户面功能(user plane function，UPF)执行控制。切片最大比特率用于控制终端设备在一个网络切片(slice)内所有QoS flow的最大比特率，由终端设备、RAN设备或UPF执行控制。
在第三代合作伙伴计划(3rd generation partnership project，3GPP)组织针对第五代(5th generation，5G)数据网络制定的5G融合计费标准中，RAN设备可以根据UE-AMBR或者切片最大比特率等特性丢弃下行数据包。该场景下，现有的数据用量统计结果不准确。
发明内容
本申请实施例提供数据用量更新方法、装置及***，能够提升数据用量统计结果的准确性。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，提供了一种数据用量更新方法，执行该数据用量更新方法的通信装置可以为用户面功能实体；也可以为应用于用户面功能实体中的模块，例如芯片或芯片***。下面以执行主体为用户面功能实体为例进行描述。用户面功能实体接收来自接入网设备的第一下行数据包的派生数据包，其中，该派生数据包是根据该第一下行数据包得到的，该派生数据包中包括第一标识；用户面功能实体根据该第一标识，确定该第一下行数据包为已丢弃数据包；用户面功能实体向会话管理实体发送数据用量更新信息，其中，该数据用量更新信息用于将该第一下行数据包的数据用量扣减。该方案中，接入网设备在丢弃第一下行数据包之后，会话管理实体可以获得数据用量更新信息，该数据用量更新信息用于将第一下行数据包的数据用量信息扣减。换言之，本申请实施例中，在接入网设备丢弃下行数据包之后，已经被统计的这些下行数据包的数据用量信息将被扣减。这样可以保证会话管理实体获得更为准确的数据用量信息。进一步的，当会话管理实体与计费功能实体交互时，计费功能实体可以获得更加准确的数据用量信息，从而可以实现更加准确的计费。
在一种可能的实现方式中，用户面功能实体向会话管理实体发送数据用量更新信 息，包括：用户面功能实体在该派生数据包中增加丢弃包标志位；用户面功能实体根据与第一报文检测规则PDR关联的第一用量上报规则URR将该数据用量更新信息上报给该会话管理实体，其中，该第一URR为负值URR，该第一PDR中包括检测该丢弃包标志位的分组检测信息PDI。即，本申请实施例中，可以将包含检测丢弃包标志位的PDI的第一PDR与负值URR进行关联。这样，一旦用户面功能实体获知第一数据包为丢弃数据包之后，即可根据该负值URR将数据用量更新信息上报给该会话管理实体，从而使得已经被统计的第一下行数据包的数据用量信息被扣减。
在一种可能的实现方式中，用户面功能实体向会话管理实体发送数据用量更新信息，包括：用户面功能实体在丢弃该派生数据包中的该第一标识后的数据包中增加丢弃包标志位；用户面功能实体根据与第一PDR关联的第一URR将该数据用量更新信息上报给该会话管理实体，其中，该第一URR为负值URR，该第一PDR中包括检测该丢弃包标志位的PDI。这样，一旦用户面功能实体获知第一数据包为丢弃数据包之后，即可根据该负值URR将数据用量更新信息上报给该会话管理实体，从而使得已经被统计的第一下行数据包的数据用量信息被扣减。
在一种可能的实现方式中，本申请实施例提供的数据用量更新方法还包括：用户面功能实体接收来自该会话管理实体的第一规则，该第一规则包括该第一PDR以及与该第一PDR关联的该第一URR和第二URR；其中，该第二URR为正值URR。即，本申请实施例中的第一PDR可以是在现在的PDR中增加检测丢弃包标志位的PDI，，并关联与第二URR相反的第一URR。
在一种可能的实现方式中，本申请实施例提供的数据用量更新方法还包括：用户面功能实体接收来自该会话管理实体的第二规则，该第二规则包括该第一PDR以及与该第一PDR关联的该第一URR、第三PDR以及与该第三PDR关联的第三URR，其中，该第三PDR中包括检测该第一下行数据包的PDI，该第三URR为正值URR。即，本申请实施例中的第一PDR以及第一PDR关联的第一URR是新增的。同时，本申请实施例中的第二规则中包括第三PDR，以及与第三PDR关联的第三URR。其中，当第三PDR检测到第一数据包时，使用第三PDR关联的第三URR进行统计上报；或者，当第一PDR检测到丢弃包标志位时，使用第一PDR关联的第一URR进行统计上报。
在一种可能的实现方式中，本申请实施例提供的数据用量更新方法还包括：用户面功能实体接收来自会话管理实体的订阅消息，该订阅消息用于请求订阅数据用量变更事件信息。即，本申请实施例中，用户面功能实体可能基于会话管理实体的订阅向会话管理实体上报数据用量更新信息。
第二方面，提供了一种数据用量更新方法，执行该数据用量更新方法的通信装置可以为接入网设备；也可以为应用于接入网设备中的模块，例如芯片或芯片***。下面以执行主体为接入网设备为例进行描述。接入网设备确定需要上报下行数据包的丢弃信息；接入网设备向用户面功能实体发送已丢弃的第一下行数据包的派生数据包，其中，该派生数据包是根据该第一下行数据包得到的，该派生数据包中包括第一标识，该第一标识用于指示该第一下行数据包为已丢弃数据包。该方案中，接入网设备在丢弃第一下行数据包之后，向用户面功能实体发送已丢弃的第一下行数据包的派生数据包，该派生数据包中包括第一标识。进而，用户面功能实体根据该第一标识，可以确 定该第一下行数据包为已丢弃数据包，并向会话管理实体发送数据用量更新信息，从而会话管理实体可以获得数据用量更新信息，该数据用量更新信息用于将第一下行数据包的数据用量信息扣减。换言之，本申请实施例中，在接入网设备丢弃下行数据包之后，已经被统计的这些下行数据包的数据用量信息将被扣减。这样可以保证会话管理实体获得更为准确的数据用量信息。进一步的，当会话管理实体与计费功能实体交互时，计费功能实体可以获得更加准确的数据用量信息，从而可以实现更加准确的计费。
在一种可能的实现方式中，接入网设备确定需要上报下行数据包的丢弃信息，包括：接入网设备根据来自会话管理实体的第一指示信息确定需要上报下行数据包的丢弃信息，该第一指示信息指示需要上报下行数据包的丢弃信息。基于该方案，接入网设备可以确定需要上报下行数据包的丢弃信息。
在一种可能的实现方式中，接入网设备确定需要上报下行数据包的丢弃信息，包括：接入网设备根据本地配置确定需要上报下行数据包的丢弃信息。基于该方案，接入网设备可以确定需要上报下行数据包的丢弃信息。
第三方面，提供了一种数据用量更新方法，执行该数据用量更新方法的通信装置可以为会话管理实体；也可以为应用于会话管理实体中的模块，例如芯片或芯片***。下面以执行主体为会话管理实体为例进行描述。会话管理实体确定需要上报下行数据包的丢弃信息；会话管理实体向接入网设备发送第一消息，该第一消息包括第二指示信息，该第二指示信息指示需要上报下行数据包的丢弃信息；会话管理实体接收来自该接入网设备的第二消息，该第二消息包括计费对象的信息和该计费对象对应的下行数据包的丢弃信息；会话管理实体根据该计费对象的信息和该计费对象对应的下行数据包的丢弃信息，更新该计费对象的数据用量信息，其中，更新后的数据用量信息中该计费对象中已丢弃下行数据包的数据用量信息被扣减。基于该方案可知，接入网设备在丢弃计费对象的下行数据包之后，会话管理实体可以获得更新后的数据用量信息，并且更新后的数据用量信息中该计费对象中已丢弃下行数据包的数据用量信息被扣减。换言之，本申请实施例中，在接入网设备丢弃包含计费对象的下行数据包之后，已经被计费的这些下行数据包的数据用量信息将被扣减。这样可以保证会话管理实体获得针对计费对象的更为准确的数据用量信息。进一步的，当会话管理实体与计费功能实体交互时，计费功能实体可以获得针对计费对象的更加准确的数据用量信息，从而可以实现针对计费对象的更加准确的计费。
在一种可能的实现方式中，第一消息包括第一QoS流的流标识；计费对象为该第一QoS流，计费对象的信息为该第一QoS流的流标识。基于该方案，可以实现QoS流粒度的更为准确的数据用量信息统计，从而实现QoS流粒度的更加准确的计费。
在一种可能的实现方式中，该第一QoS流为第一计费策略规则绑定到的QoS流，该第一计费策略规则的绑定参数包含第一计费识别信息，该第一计费识别信息用于识别对应的计费策略。即，本申请实施例可以将计费识别信息作为第一计费策略规则的绑定参数。
在一种可能的实现方式中，该第二指示信息为第一计费识别信息，该第一计费识别信息用于识别对应的计费策略；该计费对象为绑定参数包含该第一计费识别信息的 计费策略规则绑定到的一个或多个QoS流；该计费对象的信息为该第一计费识别信息。基于该方案，可以实现计费识别信息粒度的更为准确的数据用量信息统计，从而实现计费识别信息粒度的更加准确的计费。
在一种可能的实现方式中，该第一消息还用于指示该丢弃信息包括丢弃的流量值或者丢弃的数据包的个数。
在一种可能的实现方式中，会话管理实体确定需要上报下行数据包的丢弃信息，包括：会话管理实体根据来自策略控制实体的第三指示信息确定需要上报下行数据包的丢弃信息，其中，该第三指示信息指示需要上报下行数据包的丢弃信息。基于该方案，会话管理实体可以确定需要上报下行数据包的丢弃信息。
在一种可能的实现方式中，会话管理实体确定需要上报下行数据包的丢弃信息，包括：会话管理实体根据本地配置确定需要上报下行数据包的丢弃信息。基于该方案，会话管理实体可以确定需要上报下行数据包的丢弃信息。
第四方面，提供了一种数据用量更新方法，执行该数据用量更新方法的通信装置可以为接入网设备；也可以为应用于接入网设备中的模块，例如芯片或芯片***。下面以执行主体为接入网设备为例进行描述。接入网设备接收来自会话管理实体的第一消息，该第一消息包括第二指示信息；该第二指示信息指示需要上报下行数据包的丢弃信息；接入网设备根据该第二指示信息，确定计费对象的下行数据包的丢弃信息；接入网设备向该会话管理实体发送第二消息，该第二消息包括该计费对象的信息和该计费对象对应的下行数据包的丢弃信息。基于该方案可知，接入网设备在丢弃计费对象的下行数据包之后，可以向会话管理实体发送计费对象的信息和该计费对象对应的下行数据包的丢弃信息。这样，会话管理实体根据该计费对象的信息和该计费对象对应的下行数据包的丢弃信息可以获得更新后的数据用量信息，并且更新后的数据用量信息中该计费对象中已丢弃下行数据包的数据用量信息被扣减。换言之，本申请实施例中，在接入网设备丢弃包含计费对象的下行数据包之后，已经被计费的这些下行数据包的数据用量信息将被扣减。这样可以保证会话管理实体获得针对计费对象的更为准确的数据用量信息。进一步的，当会话管理实体与计费功能实体交互时，计费功能实体可以获得针对计费对象的更加准确的数据用量信息，从而可以实现针对计费对象的更加准确的计费。
在一种可能的实现方式中，该第一消息包括第一QoS流的流标识；该计费对象为该第一QoS流，该计费对象的信息为该第一QoS流的流标识。基于该方案，可以实现QoS流粒度的更为准确的数据用量信息统计，从而实现QoS流粒度的更加准确的计费。
在一种可能的实现方式中，该第一QoS流为第一计费策略规则绑定的QoS流，该第一计费策略规则的绑定参数包含第一计费识别信息，该第一计费识别信息用于识别对应的计费策略。即，本申请实施例可以将计费识别信息作为第一计费策略规则的绑定参数。
在一种可能的实现方式中，该第二指示信息为该第一计费识别信息，该第一计费识别信息用于识别对应的计费策略；该计费对象为绑定参数包含该第一计费识别信息的不同计费策略规则绑定到的一个或多个QoS流；该计费对象的信息为该第一计费识别信息。基于该方案，可以实现计费识别信息粒度的更为准确的数据用量信息统计， 从而实现计费识别信息粒度的更加准确的计费。
在一种可能的实现方式中，该第一消息还用于指示该丢弃信息包括丢弃的流量值或者丢弃的数据包的个数。
第五方面，提供了一种数据用量更新方法，执行该数据用量更新方法的通信装置可以为会话管理实体；也可以为应用于会话管理实体中的模块，例如芯片或芯片***。下面以执行主体为会话管理实体为例进行描述。会话管理实体接收来自接入网设备的第三消息，第三消息包括第一计费识别信息以及第一下行数据包的丢弃信息，该第一下行数据包为包含第一计费识别信息的下行数据包；会话管理实体根据第一计费识别信息以及第一下行数据包的丢弃信息，更新第一下行数据包的数据用量信息。其中，更新后的数据用量信息中已丢弃的第一下行数据包的数据用量信息被扣减。基于该方案可知，接入网设备在丢弃包含第一计费识别信息的第一下行数据包之后，会话管理实体可以获得更新后的数据用量信息，并且更新后的数据用量信息中第一下行数据包的数据用量信息被扣减。换言之，本申请实施例中，在接入网设备丢弃包含第一计费识别信息的第一下行数据包之后，已经被计费的这些下行数据包的数据用量信息将被扣减。这样可以保证会话管理实体获得计费识别信息粒度的更为准确的数据用量信息。进一步的，当会话管理实体与计费功能实体交互时，计费功能实体可以获得计费识别信息粒度的更加准确的数据用量信息，从而可以实现计费识别信息粒度的更加准确的计费。
在一种可能的实现方式中，本申请实施例提供的数据用量更新方法还包括：会话管理实体向接入网设备发送第一指示信息，该第一指示信息指示需要上报下行数据包的丢弃信息。基于该方案，接入网设备可以确定需要上报下行数据包的丢弃信息。
在一种可能的实现方式中，第一指示信息为第一计费识别信息。基于该方案，可以实现计费识别信息粒度的更为准确的数据用量信息统计，从而实现计费识别信息粒度的更加准确的计费。
在一种可能的实现方式中，第一指示信息还指示所述丢弃信息包括丢弃的流量值或者丢弃的数据包的个数。
在一种可能的实现方式中，本申请实施例提供的数据用量更新方法还包括：会话管理实体向用户面实体发送第五指示信息，第五指示信息指示用户面实体在下行数据包中增加计费识别信息。基于该方案，用户面功能实体可以在下行数据包中增加计费识别信息，从而使得接入网设备可以根据下行数据包中的计费识别信息进行数据用量统计。
第六方面，提供了一种数据用量更新方法，执行该数据用量更新方法的通信装置可以为接入网设备；也可以为应用于接入网设备中的模块，例如芯片或芯片***。下面以执行主体为接入网设备为例进行描述。接入网设备确定需要上报下行数据包的丢弃信息；接入网设备根据接收到的下行数据包中的计费识别信息，确定第一下行数据包的丢弃信息，第一下行数据包为包含第一计费识别信息的下行数据包；接入网设备向会话管理实体发送第三消息，第三消息包括第一计费识别信息以及第一下行数据包的丢弃信息。基于该方案可知，接入网设备在丢弃包含第一计费识别信息的第一下行数据包之后，可以向会话管理实体发送第一计费识别信息以及第一下行数据包的丢弃 信息。这样，会话管理实体根据第一计费识别信息以及第一下行数据包的丢弃信息可以获得更新后的数据用量信息，并且更新后的数据用量信息中第一下行数据包的数据用量信息被扣减。换言之，本申请实施例中，在接入网设备丢弃包含第一计费识别信息的第一下行数据包之后，已经被计费的这些下行数据包的数据用量信息将被扣减。这样可以保证会话管理实体获得计费识别信息粒度的更为准确的数据用量信息。进一步的，当会话管理实体与计费功能实体交互时，计费功能实体可以获得计费识别信息粒度的更加准确的数据用量信息，从而可以实现计费识别信息粒度的更加准确的计费。
在一种可能的实现方式中，丢弃信息包括丢弃的流量值或者丢弃的数据包的个数。
在一种可能的实现方式中，接入网设备确定需要上报下行数据包的丢弃信息，包括：接入网设备根据来自会话管理实体的第一指示信息确定需要上报下行数据包的丢弃信息，其中，第一指示信息指示需要上报下行数据包的丢弃信息。基于该方案，接入网设备可以确定需要上报下行数据包的丢弃信息。
在一种可能的实现方式中，第一指示信息为第一计费识别信息。基于该方案，可以实现计费识别信息粒度的更为准确的数据用量信息统计，从而实现计费识别信息粒度的更加准确的计费。
在一种可能的实现方式中，第一指示信息还指示丢弃信息包括丢弃的流量值或者丢弃的数据包的个数。
在一种可能的实现方式中，接入网设备确定需要上报下行数据包的丢弃信息，包括：接入网设备根据本地配置确定需要上报下行数据包的丢弃信息。基于该方案，接入网设备可以确定需要上报下行数据包的丢弃信息。
第七方面，提供了一种通信装置用于实现上述方法。该通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
一种可能的实现方式中，该通信装置包括处理模块和收发模块，该收发模块用于执行上述第一方面至第六方面任一方面所述的方法中，在所述通信装置侧进行消息接收和发送的操作；该处理模块用于调用指令，执行上述第一方面至第六方面任一方面所述的方法中，在所述通信装置侧进行的消息处理或控制操作。
第八方面，提供了一种通信装置，包括：处理器；该处理器用于与存储器耦合，并读取存储器中存储的计算机指令之后，根据该指令执行如上述任一方面所述的方法。
在一种可能的实现方式中，通信装置还包括存储器；该存储器用于存储计算机指令。
在一种可能的实现方式中，通信装置还包括通信接口；该通信接口用于该通信装置与其它设备进行通信。示例性的，该通信接口可以为收发器、输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。
在一种可能的实现方式中，该通信装置可以是芯片或芯片***。其中，当该通信装置是芯片***时，该通信装置可以由芯片构成，也可以包含芯片和其他分立器件。
在一种可能的实现方式中，当通信装置为芯片或芯片***时，上述通信接口可以是该芯片或芯片***上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相 关电路等。上述处理器也可以体现为处理电路或逻辑电路。
第九方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述任一方面所述的方法。
第十方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述任一方面所述的方法。
其中，第七方面至第十方面中任一种可能的实现方式所带来的技术效果可参见上述第一方面或第二方面或第三方面或第四方面或第五方面或第六方面中不同实现方式所带来的技术效果，此处不再赘述。
第十一方面，提供一种通信***，该通信***包括执行上述第一方面所述的数据用量更新方法的用户面功能实体和执行上述第二方面所述的数据用量更新方法的接入网设备；或者，该通信***包括执行上述第三方面所述的数据用量更新方法的会话管理实体和执行上述第四方面所述的数据用量更新方法的接入网设备；或者，该通信***包括执行上述第五方面所述的数据用量更新方法的会话管理实体和执行上述第六方面所述的数据用量更新方法的接入网设备。
附图说明
图1为现有的基于QoS flow的5G QoS模型示意图；
图2a为现有的5G网络的服务化架构示意图；
图2b为图2a对应的基于参考点的5G网络架构示意图；
图3为现有的计费流程示意图；
图4为本申请实施例提供的网络计费的流程示例图；
图5为现有的PDR、PDI与流动作关系示意图；
图6为本申请实施例提供的一种通信***架构示意图；
图7为本申请实施例提供的另一种通信***架构示意图；
图8为本申请实施例提供的一种通信装置的结构示意图；
图9为本申请实施例提供的数据用量更新方法的流程示意图一；
图10a为本申请实施例提供的PDR与URR的关联示意图一；
图10b为本申请实施例提供的PDR与URR的关联示意图二；
图11为本申请实施例提供的数据用量更新方法的流程示意图二；
图12为本申请实施例提供的数据用量更新方法的流程示意图三；
图13为本申请实施例提供的数据用量更新方法的交互示意图一；
图14为本申请实施例提供的数据传输示意图一；
图15为本申请实施例提供的数据传输示意图二；
图16为本申请实施例提供的数据用量更新方法的交互示意图二；
图17为本申请实施例提供的数据用量更新方法的交互示意图三；
图18为本申请实施例提供的数据用量更新方法的交互示意图四；
图19为本申请实施例提供的另一种通信装置的结构示意图。
具体实施方式
为方便理解本申请实施例的方案，首先给出相关概念的简要介绍如下：
第一，PDU会话：
PDU会话为终端设备与数据网络(data network，DN)之间的一个关联，用于提供一个PDU连接服务。
第二，QoS模型：
在5G***中，为了保证业务端到端的服务质量，提出了基于QoS flow的5G QoS模型，如图1所示。该5G QoS模型支持GBR的QoS flow(即GBR QoS flow)和non-GBR QoS flow。使用同一个QoS flow控制的数据包接收相同的传输处理(如调度、或准入门限等)。
如图1所示，对于一个终端设备，可以与5G网络建立一个或者多个PDU会话。每个PDU会话中可以建立一个或者多个QoS flow。一个QoS flow由一个QoS流标识(QoS flow identifier，QFI)识别，即QFI在会话中唯一标识一个QoS flow。其中，一个PDU会话与RAN设备和UPF之间的一个通用分组无线服务(general packet radio service，GPRS)隧道协议用户面(GPRS tunneling protocol user plane，GTP-U)隧道一一对应；一个QoS flow对应终端设备和RAN设备之间的一个无线承载，而一个无线承载可以对应一个或多个QoS flow。
其中，一个QoS flow为GBR QoS flow还是non-GBR QoS flow，由对应的QoS文件(QoS profile)确定。
对于GBR QoS flow，对应的QoS文件包含以下QoS参数：5G QoS标识(5G QoS identifier，5QI)、分配和预留优先级(allocation and retention priority，ARP)、保证流比特率(guaranteed flow bit rate，GFBR)和最大流比特率(maximum flow bit rate，MFBR)，可选的包含QoS通知控制(QoS notification control，QNC)。具体地，根据QoS文件是否包含QNC可以将GBR QoS flow分为需要notification control的GRB QoS flow和不需要notification control的GBR QoS flow。对于需要notification control的GBR QoS flow，当RAN设备检测到对应的QoS flow资源不能被满足时，RAN设备通知会话管理功能(session management function，SMF)该事件。进一步的SMF可以发起QoS flow删除或者修改流程。对于Non-GBR QoS flow，对应的QoS文件包含以下QoS参数：5QI和ARP；可选的包含反转QoS属性(reflective QoS attribute，RQA)。
上述QoS参数的定义如下：
5QI是一个标量，用于索引到对应的5G QoS特征。5QI分为标准化的5QI、预配置的5QI和动态分配的5QI。对于标准化的5QI，与一组标准化的5G QoS特征值一一对应；对于预配置的5QI，对应的5G QoS特征值预配置在无线接入网设备(radio access network，RAN)设备上；对于动态分配的5QI，对应的5G QoS特征由核心网设备通过QoS文件发送给RAN设备。
ARP包含优先等级、抢占能力和被抢占能力。
GFBR代表期望提供给GBR QoS flow(流)的比特率。
MFBR限制提供给GBR QoS flow的比特率，即提供给GBR QoS flow的最大比特率。如超过该比特率时，数据包可以被丢弃。
RQA用于指示使用对应QoS flow传输的业务使用反转QoS。
QNC用于指示RAN设备在QoS flow的使用期内当GFBR不能满足时是否通知网络侧。
除去上述QoS flow级别的QoS参数，5G***中还引入了聚合级别的QoS参数，如UE-AMBR、session-AMBR以及切片最大比特率等。
其中，UE-AMBR用于控制终端设备的所有non-GBR QoS flow的聚合比特率，由RAN设备执行控制。例如，RAN设备控制上行(uplink，UL)和下行(downlink，DL)UE-AMBR，进行流量整形，如丢弃超过限额的数据包。
session-AMBR用于控制终端设备的一个PDU会话中的所有non-GBR QoS flow的聚合最大比特率，由终端设备和UPF执行控制。例如，终端设备控制UL Session-AMBR，进行流量整形，如丢弃超过限额的数据包。UPF控制UL和DL Session-AMBR，进行流量整形，如丢弃超过限额的数据包。
切片最大比特率用于控制终端设备在一个网络切片(slice)内所有QoS flow的最大比特率，由终端设备、RAN设备或UPF执行控制。例如，RAN设备控制UL和DL slice-MBR，进行流量整形，如丢弃超过限额的数据包。
第三，5G***架构(5G system architecture)与5G融合计费相关的功能：
图2a为现有的5G网络的服务化架构示意图。该5G网络包括RAN设备、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)或者计费功能(charging function，CHF)等。
其中，如图2a所示，终端设备通过RAN设备接入5G网络，终端设备通过N1接口(简称N1)与AMF通信；RAN设备通过N2接口(简称N2)与AMF通信；RAN设备通过N3接口(简称N3)与UPF通信；SMF通过N4接口(简称N4)与UP通信，UPF通过N6接口(简称N6)接入数据网络。此外，图2a所示的AUSF、AMF、SMF、NSSF、NEF、NRF、PCF、UDM、UDR、CHF或者AF等控制面功能采用服务化接口进行交互。比如，AUSF对外提供的服务化接口为Nausf；AMF对外提供的服务化接口为Namf；SMF对外提供的服务化接口为Nsmf；NSSF对外提供的服务化接口为Nnssf；NEF对外提供的服务化接口为Nnef；NRF对外提供的服务化接口为Nnrf；PCF对外提供的服务化接口为Npcf；UDM对外提供的服务化接口为Nudm；UDR对外提供的服务化接口为Nudr；CHF对外提供的服务化接口为Nchf；AF对外提供的服务化接口为Naf。相关功能描述以及接口描述可以参考23501标准中的5G***架构(5G system architecture)图，在此不予赘述。
图2b为图2a对应的基于参考点的5G网络架构示意图。如图2b所示，终端设备通过RAN设备接入5G网络，终端设备通过N1接口(简称N1)与AMF通信；RAN设备通过N2接口(简称N2)与AMF通信；RAN设备通过N3接口(简称N3)与UPF通信；不同UPF之间通过N9接口(简称N9)通信；UPF通过N6接口(简称N6)接入数据网络。此外，SMF通过N4接口(简称N4)与UPF通信；AMF网元通过N11接口(简称N11)与SMF通信；AMF通过N8接口(简称N8)与UDM通信； AMF通过N12接口(简称N12)与AUSF通信；AMF通过N15接口(简称N15)与PCF通信；AMF通过N22接口(简称N22)与NSSF通信；不同AMF之间通过N14接口(简称N14)通信；SMF通过N7接口(简称N7)与PCF通信；SMF通过N10接口(简称N10)与UDM通信；SMF通过N29接口(简称N29)与NEF通信；SMF通过Nnrf接口(简称Nnrf)与NRF通信；SMF通过Nchf接口(简称Nchf)与CHF通信；PCF通过N5接口(简称N5)与NEF通信；UDR通过N36接口(简称N36)与PCF通信；UDR通过N37接口(简称N37)与NEF通信；UDM通过N13接口(简称N13)与AUSF通信；UDM通过N29接口(简称N29)与NRF通信。
在图2a所示的5G网络架构或图2b所示的5G网络架构中，5G融合计费相关的功能包括PCF、SMF、UPF和CHF。各个计费相关的功能的说明如表一所示。
表一
Figure PCTCN2020132802-appb-000001
第四，计费流程：
现有的计费流程如图3所示，包括如下步骤：
S1、PDU会话创建时，SMF向PCF申请计费规则。进而，PCF向SMF返回计费规则。计费规则包括计费粒度及计费方式。
S2、SMF按优先级选择对应的CHF。
S3、SMF向CHF申请配额，CHF向SMF返回配额及计费事件。
S4、SMF向UPF下发N4规则。N4规则中包括配额及计费事件。
S5、终端设备访问业务，UPF解析报文，按匹配到的数据包检测规则(packet detection rule，PDR)进行数据用量统计。当满足计费事件时，UPF向SMF上报数据用量信息(也可以称之为配额用量信息)。
S6、SMF上报数据用量信息到CHF，并申请新的配额。后续流程周而复始，不断的上报数据用量信息并更新新的配额，直至用户去活或余额不足。
下面分别对于上述计费粒度、计费方式和计费事件进行说明。
在本申请实施例中，计费粒度用于表征对谁进行计费。对于接入5G网络的终端 设备来讲，一个PDU会话中可能包含很多业务流。目前的5G融合计费中，既可以对整个PDU会话进行计费，也可以对PDU会话中的不同业务流分别计费。示例性的，不同计费粒度的相关说明可以如表二所示。
表二
Figure PCTCN2020132802-appb-000002
5G融合计费是将离线计费和在线计费融合到了一起，因此5G融合计费的计费方式有两种，包括离线计费和在线计费。其中，在线计费，在计费会话创建时，SMF需要到CHF申请业务的配额和相关计费参数。离线计费，在计费会话创建时，SMF只需要到CHF申请相关计费参数，但无需申请业务的配额。
计费事件，即触发条件(trigger condition)。计费事件实际上是CHF向SMF订阅的一些事件，也就是SMF在规定的条件下需要申请配额或上报配额。例如，当业务使用的流量到达指定门限时，SMF向CHF发送消息，以更新计费会话以及获取新的配额。按粒度区分，计费事件可以分为PDU会话级(简称session级)和业务级(简称费率组(rating group，RG)级)。其中，PDU会话级的计费事件对PDU会话内所有RG生效，适用于整个PDU会话。业务级的计费事件仅对PDU会话内指定的业务流生效，适用于指定RG。按上报方式区分，计费事件可以分为立即上报(Immediate)和延时上报(Deferred)。其中，当计费事件发生时，对于立即上报的计费事件，SMF收集当前计费事件对应的配额用量，立即向CHF上报。当计费事件发生时，对于延时上报的计费事件，SMF收集当前计费事件对应的配额用量，暂时缓存，并在下次立即上报的计费事件发生时一起上报。
目前，SMF本地支持配置计费事件是否使能，以及上报的方式，作为缺省值使用。CHF也可以向SMF下发计费事件，下发的计费事件优先级高于本地配置的计费事件优先级。部分计费事件是否使能，以及上报的方式是可修改的。在第二代(2nd generation，2G)/第三代(3rd generation，3G)/第4代(4th generation，4G)网络中，计费事件大多是立即上报，而在5G融合计费中，一些计费事件的上报方式是可以修改的，运营商可以根据自己的业务灵活制定上报方式，这样可以减少信令冲击。表三以2个计费触发为例，描述了相关信息。
表三
Figure PCTCN2020132802-appb-000003
下面通过一个示例给出用户访问业务时，网络的计费流程。
假设终端设备A开户，计费属性是在线计费。充值了100元，并订购了如下套餐：
基础流量包，0.1元/MB的普通业务流量，运营商规定基础流量包对应的费率组为RG1。
定向流量包，10元1GB的某款新闻阅读APP流量，运营商规定APP流量对应的费率组为RG2。
则如图4所示，网络计费的流程包括如下步骤：
S11、终端设备A开机后，向SMF申请创建PDU会话。
S12、SMF与PCF交互，根据用户的签约信息，获取对应的计费规则，包括计费粒度和计费方式，如RG1(在线计费)、RG2(在线计费)。
S13、SMF向CHF申请对应的配额；CHF检查账户余额，创建用户话单，并向SMF下发对应的配额及计费事件，如下：
基础流量包：配额50M；“流量阈值到达”计费事件，立即上报，参数为10MB(即配额还剩10MB时，会触发计费事件)。
定向流量包：配额30M；“流量阈值到达”计费事件，立即上报，参数为10MB。
S14、SMF将基础流量包和定向流量包对应的配额以及计费事件一起下发到UPF。
S15、终端设备A开始使用APP浏览新闻，UPF对业务报文进行解析，开启计数器，将解析到的该APP的流量进行记录。
S16、随着终端设备A的使用，累计的报文流量不断增加，当定向流量包使用了20MB时(剩余10MB)，触发了“流量阈值到达”计费事件，UPF会上报数据用量信息到SMF。
S17、SMF上报数据用量信息到CHF，请求更新配额。
S18、CHF将数据用量对应的计费信息存入对应的话单中，并下发新的30M配额到SMF，以使得SMF可以下发新的30M配额到UPF。在整个配额更新过程中，UPF仍旧继续计费，过程中使用了5M流量在新配额下发后需核减。
后续流程与之前一致，随着用户不断使用业务，UPF和SMF周而复始的上报数据用量信息，申请配额，直至用户关机或余额不足。
第五，绑定机制：
绑定机制是将服务数据流(在策略和计费控制(policy and charging control，PCC)规则中通过业务数据流(service data flow，SDF)模板定义)与传输服务数据流的QoS flow相关联的过程(英文：The binding mechanism is the procedure that associates a service data flow(defined in a PCC rule by means of the SDF template),to the QoS Flow deemed to transport the service data flow)。现有的绑定机制包括下述三个步骤：
第一步，会话绑定(session binding)，即将AF会话(session)和PDU会话做一一对应，具体可参考现有的实现方式，在此不再赘述。
第二步，PCC规则授权(PCC rule authorization)，由PCF来执行，对PCC规则做授权，为PCC规则分配QoS参数，具体可参考现有的实现方式，在此不再赘述。
第三步，QoS流绑定(QoS flow binding)，即将PCC规则与PDU会话内的QoS flow进行关联。使用以下绑定参数执行绑定(英文：QoS flow binding is the association of a  PCC rule to a QoS Flow within a PDU Session.The binding is performed using the following binding parameters)：
1、5QI，相关描述可参考上述QoS参数部分，在此不再赘述。
2、ARP，相关描述可参考上述QoS参数部分，在此不再赘述。
或者，可选的，若PCC规则中包括以下参数中的一个或多个，则以下参数中的一个或多个也可以作为绑定参数：
3、QNC，相关描述可参考上述QoS参数部分，在此不再赘述。
4、优先级，优先级指示在QoS流中调度资源的优先级。优先级应用于区分同一终端设备的QoS流，并且还应用于区分来自不同终端设备的QoS流。
5、平均窗口，平均窗口只用于GBR QoS flow，代表计算GFBR和MFBR的持续时间。
6、MDBV，MDBV表示要求5G接入网在一个包延时估算(packet delay budget，PDB)之内要服务的最大数据量。其中，PDB定义了一个数据包在终端设备和有N6接口的UPF网元之间传递所能被延迟的时间上限。
当然，上述的优先级、平均窗口或最大数据突发量也可以是上述5QI对应的QoS属性中的参数，在此不作具体限定。
可选的，本申请实施例中，若PCC规则中包括计费识别信息，则该计费识别信息可以作为绑定参数。其中，本申请实施例中的计费识别信息用于识别对应的计费策略，在此统一说明，以下不再赘述。
需要说明的是，本申请实施例中，具有上述不同绑定参数属性的PCC规则一定会被绑定到不同的QoS flow，在此统一说明，以下不再赘述。
第六，N4接口：
如图2b所示，N4接口为SMF与UPF之间的接口。其中，SMF向UPF下发包含PDR的N4规则以执行相应控制。如图5所示，PDR中包括PDR ID、分组检测信息(packet detection information，PDI)、以及转发动作规则(forwarding action rule，FAR)ID、QoS执行规则(QoS enforcement rule，QER)ID和/或统计信息上报规则(usage reporting rule，URR)ID等。其中，FAR ID指示的FAR、URR ID指示的URR以及QER ID指示的QER为PDR关联的流动作。PDI包含1个或者多个匹配域，当入口数据流量的对应字段与PDI中的所有匹配域都匹配成功，则UPF视为匹配通过。进而，UPF可以根据FAR对报文执行丢弃(drop)、转发(forward)、缓存(buffer)、上报控制面(notify)或者复制(duplicate)操作等。UPF可以根据QER对报文执行QoS操作。UPF可以根据URR对报文执行统计信息上报。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A,B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b， 或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。同时，在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
此外，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
如图6所示，为本申请实施例提供的一种通信***60，该通信***60包括用户面功能实体601和接入网设备602。其中，用户面功能实体601和接入网设备602之间可以直接通信，也可以通过其他设备的转发进行通信，本申请实施例对此不做具体限定。
一种可能的实现方式中，接入网设备602，用于确定需要上报下行数据包的丢弃信息之后，向用户面功能实体601发送已丢弃的第一下行数据包的派生数据包。其中，该派生数据包是根据第一下行数据包得到的，该派生数据包中包括第一标识，第一标识用于指示第一下行数据包为已丢弃数据包。用户面功能实体601，用于接收来自接入网设备602的第一下行数据包的派生数据包，并根据派生数据包中的第一标识，确定第一下行数据包为已丢弃数据包之后，向会话管理实体发送数据用量更新信息，其中，数据用量更新信息用于将第一下行数据包的数据用量信息扣减。该方案的具体实现将在后续方法实施例中详细阐述，在此不再赘述。基于该方案可知，接入网设备在丢弃第一下行数据包之后，会话管理实体可以获得数据用量更新信息，该数据用量更新信息用于将第一下行数据包的数据用量信息扣减。换言之，本申请实施例中，在接入网设备丢弃下行数据包之后，已经被统计的这些下行数据包的数据用量信息将被扣减。这样可以保证会话管理实体获得更为准确的数据用量信息。进一步的，当会话管理实体与计费功能实体交互时，计费功能实体可以获得更加准确的数据用量信息，从而可以实现更加准确的计费。
如图7所示，为本申请实施例提供的一种通信***70，该通信***70包括会话管理实体701和接入网设备702。其中，会话管理实体701和接入网设备702之间可以直接通信，也可以通过其他设备的转发进行通信，本申请实施例对此不做具体限定。
一种可能的实现方式中，会话管理实体701，用于确定需要上报下行数据包的丢弃信息之后，向接入网设备702发送第一消息。第一消息包括第二指示信息，第二指示信息指示需要上报下行数据包的丢弃信息。接入网设备702，用于接收来自会话管理实体701的第一消息，并根据第二指示信息，确定计费对象的下行数据包的丢弃信息之后，向会话管理实体701发送第二消息，第二消息包括计费对象的信息和计费对 象对应的下行数据包的丢弃信息。会话管理实体701，用于接收来自接入网设备702的第二消息，并根据计费对象的信息和计费对象对应的下行数据包的丢弃信息，更新计费对象的数据用量信息，其中，更新后的数据用量信息中计费对象中已丢弃下行数据包的数据用量信息被扣减。该方案的具体实现将在后续方法实施例中详细阐述，在此不再赘述。基于该方案可知，接入网设备在丢弃计费对象的下行数据包之后，会话管理实体可以获得更新后的数据用量信息，并且更新后的数据用量信息中该计费对象中已丢弃下行数据包的数据用量信息被扣减。换言之，本申请实施例中，在接入网设备丢弃包含计费对象的下行数据包之后，已经被计费的这些下行数据包的数据用量信息将被扣减。这样可以保证会话管理实体获得针对计费对象的更为准确的数据用量信息。进一步的，当会话管理实体与计费功能实体交互时，计费功能实体可以获得针对计费对象的更加准确的数据用量信息，从而可以实现针对计费对象的更加准确的计费。
另一种可能的实现方式中，接入网设备702，用于确定需要上报下行数据包的丢弃信息，并根据接收到的下行数据包中的计费识别信息，确定第一下行数据包的丢弃信息之后，向会话管理实体701发送第三消息，其中，第一下行数据包为包含第一计费识别信息的下行数据包；第三消息包括第一计费识别信息以及第一下行数据包的丢弃信息。会话管理实体701，用于接收来自接入网设备702的第三消息，并根据第一计费识别信息以及第一下行数据包的丢弃信息，更新第一下行数据包的数据用量信息，其中，更新后的数据用量信息中已丢弃的第一下行数据包的数据用量信息被扣减。该方案的具体实现将在后续方法实施例中详细阐述，在此不再赘述。基于该方案可知，接入网设备在丢弃包含第一计费识别信息的第一下行数据包之后，会话管理实体可以获得更新后的数据用量信息，并且更新后的数据用量信息中第一下行数据包的数据用量信息被扣减。换言之，本申请实施例中，在接入网设备丢弃包含第一计费识别信息的第一下行数据包之后，已经被计费的这些下行数据包的数据用量信息将被扣减。这样可以保证会话管理实体获得计费识别信息粒度的更为准确的数据用量信息。进一步的，当会话管理实体与计费功能实体交互时，计费功能实体可以获得计费识别信息粒度的更加准确的数据用量信息，从而可以实现计费识别信息粒度的更加准确的计费。
可选的，本申请实施例中的接入网设备可以是用于与终端设备通信的任意一种具有无线收发功能的通信设备。该接入网设备包括但不限于：演进型节点B(evolved node B，eNB)，基带单元(baseband unit，BBU)，无线保真(wireless fidelity，WIFI)***中的接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者TRP等。该接入网设备还可以为5G***中的RAN设备，该RAN设备例如包括gNB或TRP或TP，或者5G***中的基站的一个或一组(包括多个天线面板)天线面板。此外，该RAN设备还可以为构成gNB或TP的网络节点，如BBU，或分布式单元(distributed unit，DU)等。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU。此外，gNB还可以包括有源天线单元(active antenna unit，AAU)。CU实现gNB的部分功能，DU实现gNB的部分功能。比如，CU负责处理非实时协议和服务，实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能。DU负责处理物理层协议和实时服务，实现无线链路控制 (radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理(physical，PHY)层的功能。AAU实现部分物理层处理功能、射频处理及有源天线的相关功能。由于RRC层的信息最终会变成PHY层的信息，或者，由PHY层的信息转变而来，因而，在这种架构下，高层信令，如RRC层信令，也可以认为是由DU发送的，或者，由DU+AAU发送的。可以理解的是，接入网设备可以为包括CU节点、DU节点、AAU节点中一项或多项的设备。
可选的，图6所示的通信***60或图7所示的通信***70可以适用于目前正在讨论的5G网络，也可以适用于未来的其他网络等，本申请实施例对此不做具体限定。
示例性的，以图6所示的通信***60或图7所示的通信***70可以适用于目前正在讨论的5G网络为例，则上述接入网设备所对应的网元或者实体可以为图2a或图2b所述的5G网络中的RAN设备；上述用户面功能实体所对应的网元或者实体可以为图2a或图2b所述的5G网络中的UPF；上述会话管理实体所对应的网元或者实体可以为图2a或图2b所述的5G网络中的SMF。
可选的，本申请实施例中的用户面功能实体、会话管理实体或接入网设备也可以称之为通信装置，其可以是一个通用设备或者是一个专用设备，本申请实施例对此不作具体限定。
可选的，本申请实施例中的用户面功能实体、会话管理实体或接入网设备的相关功能可以由一个设备实现，也可以由多个设备共同实现，还可以是由一个设备内的一个或多个功能模块实现，本申请实施例对此不作具体限定。可以理解的是，上述功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是硬件与软件的结合，或者是平台(例如，云平台)上实例化的虚拟化功能。
例如，本申请实施例中的用户面功能实体、会话管理实体或接入网设备的相关功能可以通过图8中的通信装置800来实现。图8所示为本申请实施例提供的通信装置800的结构示意图。该通信装置800包括一个或多个处理器801，通信线路802，以及至少一个通信接口(图8中仅是示例性的以包括通信接口804，以及一个处理器801为例进行说明)，可选的还可以包括存储器803。
处理器801可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路802可包括一通路，用于连接不同组件之间。
通信接口804，可以是收发模块用于与其他设备或通信网络通信，如以太网，RAN，无线局域网(wireless local area networks，WLAN)等。例如，所述收发模块可以是收发器、收发机一类的装置。可选的，所述通信接口804也可以是位于处理器801内的收发电路，用以实现处理器的信号输入和信号输出。
存储器803可以是具有存储功能的装置。例如可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他 光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路802与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器803用于存储执行本申请方案的计算机执行指令，并由处理器801来控制执行。处理器801用于执行存储器803中存储的计算机执行指令，从而实现本申请实施例中提供的数据用量更新方法。
或者，可选的，本申请实施例中，也可以是处理器801执行本申请下述实施例提供的数据用量更新方法中的处理相关的功能，通信接口804负责与其他设备或通信网络通信，本申请实施例对此不作具体限定。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器801可以包括一个或多个CPU，例如图8中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信装置800可以包括多个处理器，例如图8中的处理器801和处理器808。这些处理器中的每一个可以是一个单核(single-core)处理器，也可以是一个多核(multi-core)处理器。这里的处理器可以包括但不限于以下至少一种：中央处理单元(central processing unit，CPU)、微处理器、数字信号处理器(DSP)、微控制器(microcontroller unit，MCU)、或人工智能处理器等各类运行软件的计算设备，每种计算设备可包括一个或多个用于执行软件指令以进行运算或处理的核。
在具体实现中，作为一种实施例，通信装置800还可以包括输出设备805和输入设备806。输出设备805和处理器801通信，可以以多种方式来显示信息。例如，输出设备805可以是液晶显示器(liquid crystal display，LCD)，发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备806和处理器801通信，可以以多种方式接收用户的输入。例如，输入设备806可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的通信装置800有时也可以称为通信装置，其可以是一个通用设备或者是一个专用设备。例如通信装置800可以是台式机、便携式电脑、网络服务器、掌上电脑(personal digital assistant，PDA)、移动手机、平板电脑、无线终端设备、嵌入式设备、上述终端设备、上述网络设备、或具有图8中类似结构的设备。本申请实施例不限定通信装置800的类型。
下面将结合附图，对本申请实施例提供的数据用量更新方法进行说明。
如图9所示，为本申请实施例提供的一种数据用量更新方法，包括如下步骤：
S901、接入网设备确定需要上报下行数据包的丢弃信息。
本申请实施例中的丢弃信息包括丢弃的流量值或者丢弃的数据包的个数。
一种可能的实现方式中，接入网设备确定需要上报下行数据包的丢弃信息，包括：接入网设备根据来自会话管理实体的第一指示信息确定需要上报下行数据包的丢弃信息，第一指示信息指示需要上报下行数据包的丢弃信息。示例性的，本申请实施例中， 第一指示信息可以为第一计费识别信息，第一计费识别信息用于识别对应的计费策略。
可选的，本申请实施例中，上述第一指示信息还用于指示丢弃信息的内容，如丢弃的流量值或者丢弃的数据包的个数。当然，本申请实施例中，还可以是接入网设备接收来自会话管理实体的第四指示信息，第四指示信息用于指示丢弃信息的内容，本申请实施例对此不做具体限定。
另一种可能的实现方式中，接入网设备确定需要上报下行数据包的丢弃信息，包括：接入网设备根据本地配置确定需要上报下行数据包的丢弃信息，例如接入网设备根据本地配置的会话的切片信息，确定某一会话需要上报下行数据包的丢弃信息。
S902、接入网设备向用户面功能实体发送已丢弃的第一下行数据包的派生数据包。相应的，用户面功能实体接收来自接入网设备的第一下行数据包的派生数据包。其中，该派生数据包是根据第一下行数据包得到的，该派生数据包中包括第一标识，第一标识用于指示第一下行数据包为已丢弃数据包。
本申请实施例中，第一下行数据包的派生数据包的功能是能够用于识别第一下行数据包。示例性的，第一下行数据包的派生数据包例如可以为包括第一标识和第一下行数据包的复制数据的数据包；或者，第一下行数据包的派生数据包例如可以为包括第一标识以及能够识别第一下行数据包的业务流的信息和第一下行数据包的数据用量的信息的数据包，本申请实施例对第一下行数据包的派生数据包的内容不做具体限定。
S903、用户面功能实体根据派生数据包中的第一标识，确定第一下行数据包为已丢弃数据包。
S904、用户面功能实体向会话管理实体发送数据用量更新信息。相应的，会话管理实体接收来自用户面功能实体的数据用量更新信息。其中，数据用量更新信息用于将第一下行数据包的数据用量扣减。
一种可能的实现方式中，用户面功能实体向会话管理实体发送数据用量更新信息，包括：用户面功能实体在派生数据包中增加丢弃包标志位，并根据与第一PDR关联的第一URR将数据用量更新信息上报给会话管理实体，其中，第一URR为负值URR(即测量的用量为负值，下同)，第一PDR中包括检测丢弃包标志位的PDI。
另一种可能的实现方式中，用户面功能实体向会话管理实体发送数据用量更新信息，包括：用户面功能实体在丢弃派生数据包中的第一标识后的数据包中增加丢弃包标志位，并根据与第一PDR关联的第一URR将数据用量更新信息上报给会话管理实体，其中，第一URR为负值URR，第一PDR中包括检测丢弃包标志位的PDI。
又一种可能的实现方式中，用户面功能实体向会话管理实体发送数据用量更新信息，包括：用户面功能实体根据匹配到的检测上行数据包的PDR所关联的负值URR将数据用量更新信息上报给会话管理实体。
需要说明的是，本申请实施例中，数据用量更新信息可以是用户面功能实体根据内部已经统计的数据用量，将第一下行数据包的数据用量扣减后获得的更新后的数据用量；或者，数据用量更新信息可以是第一下行数据包的数据用量，第一下行数据包的数据用量用于更新用户面功能实体已经上报给会话管理实体的数据用量，更新方式为从用户面功能实体已经上报给会话管理实体的数据用量中扣减第一下行数据包的数据用量。当然也不限于此，数据用量更新信息可以实现扣减第一下行数据包的数据用 量即可。
可选的，本申请实施例中，用户面功能实体可以通过如下方式获得第一PDR和第一URR。
一种可能的实现方式中，用户面功能实体接收来自会话管理实体的第一规则，第一规则包括第一PDR以及与第一PDR关联的第一URR和第二URR；其中，第二URR为正值URR。第二URR与第一URR对应的测量对象是同一个。
示例性的，如图10a所示，本申请实施例中的第一PDR可以是在现在的PDR中增加检测丢弃包标志位的PDI，并关联与第二URR相反的第一URR。即本申请实施例中，第一PDR中还包括检测第一下行数据包的PDI。其中，当第一PDR检测到第一下行数据包时，使用第一PDR关联的第二URR进行统计上报；或者，当第一PDR检测到丢弃包标志位时，使用第一PDR关联的第一URR进行统计上报。
需要说明的是，本申请实施例第一PDR中检测第一下行数据包的PDI还可以检测第一数据包之外的其他下行数据包，本申请实施例对此不做具体限定。
另一种可能的实现方式中，用户面功能实体接收来自会话管理实体的第二规则，第二规则包括第一PDR以及与第一PDR关联的第一URR、第三PDR以及与第三PDR关联的第三URR，其中，第三PDR中包括检测第一下行数据包的PDI，第三URR为正值URR。第一URR与第三URR对应的测量对象是同一个。
示例性的，如图10b所示，本申请实施例中的第一PDR以及第一PDR关联的第一URR是新增的。同时，本申请实施例中的第二规则中包括第三PDR，以及与第三PDR关联的第三URR。其中，当第三PDR检测到第一数据包时，使用第三PDR关联的第三URR进行统计上报；或者，当第一PDR检测到丢弃包标志位时，使用第一PDR关联的第一URR进行统计上报。
需要说明的是，本申请实施例第三PDR中检测第一下行数据包的PDI还可以检测第一数据包之外的其他下行数据包，本申请实施例对此不做具体限定。
可选的，本申请实施例提供的数据用量更新方法还可以包括：用户面功能实体接收来自会话管理实体的订阅消息，该订阅消息用于请求订阅数据用量变更事件。即，本申请实施例中，用户面功能实体可能是基于会话管理实体的订阅请求向会话管理实体上报数据用量信息。
图9所示的实施例的具体实现可参考后续图13所示的实施例，在此不再赘述。
基于该方案可知，接入网设备在丢弃第一下行数据包之后，会话管理实体可以获得数据用量更新信息，该数据用量更新信息用于将第一下行数据包的数据用量信息扣减。换言之，本申请实施例中，在接入网设备丢弃下行数据包之后，已经被统计的这些下行数据包的数据用量信息将被扣减。这样可以保证会话管理实体获得更为准确的数据用量信息。进一步的，当会话管理实体与计费功能实体交互时，计费功能实体可以获得更加准确的数据用量信息，从而可以实现更加准确的计费。
其中，上述步骤S901至S904中用户面功能实体的动作可以由图8所示的通信装置800中的处理器801调用存储器803中存储的应用程序代码以指令用户面功能实体执行，上述步骤S901至S904中接入网设备的动作可以由图8所示的通信装置800中的处理器801调用存储器803中存储的应用程序代码以指令接入网设备执行，上述步 骤S901至S904中会话管理实体的动作可以由图8所示的通信装置800中的处理器801调用存储器803中存储的应用程序代码以指令会话管理实体执行，本实施例对此不作任何限制。
如图11所示，为本申请实施例提供的一种数据用量更新方法，包括如下步骤：
S1101、会话管理实体确定需要上报下行数据包的丢弃信息。
本申请实施例中的丢弃信息包括丢弃的流量值或者丢弃的数据包的个数等。
一种可能的实现方式中，会话管理实体确定需要上报下行数据包的丢弃信息，包括：会话管理实体根据来自策略控制实体的第三指示信息确定需要上报下行数据包的丢弃信息，其中，所述第三指示信息指示需要上报下行数据包的丢弃信息。
另一种可能的实现方式中，会话管理实体确定需要上报下行数据包的丢弃信息，包括：会话管理实体根据本地配置确定需要上报下行数据包的丢弃信息。
S1102、会话管理实体向接入网设备发送第一消息。相应的，接入网设备接收来自会话管理实体的第一消息。第一消息包括第二指示信息，第二指示信息指示需要上报下行数据包的丢弃信息。
S1103、接入网设备根据第二指示信息，确定计费对象的下行数据包的丢弃信息。
S1104、接入网设备向会话管理实体发送第二消息。相应的，会话管理实体接收来自接入网设备的第二消息。第二消息包括计费对象的信息和计费对象对应的下行数据包的丢弃信息。
S1105、会话管理实体根据计费对象的信息和计费对象对应的下行数据包的丢弃信息，更新计费对象的数据用量信息，其中，更新后的数据用量信息中计费对象中已丢弃下行数据包的数据用量信息被扣减。
对于上述步骤S1102-S1105：
一种可能的实现方式中，第一消息包括第一QoS流的流标识；计费对象为第一QoS流，计费对象的信息为第一QoS流的流标识
可选的，本申请实施例中，第一QoS流为第一计费策略规则绑定到的QoS流(也可以理解为第一QoS流为与第一计费策略规则绑定的QoS流)，第一计费策略规则的绑定参数包含第一计费识别信息，第一计费识别信息用于识别对应的计费策略。即，本申请实施例中，第一计费识别信息可以作为QoS流绑定时的绑定参数，从而可以实现QoS流粒度的数据用量统计，进而实现QoS流粒度的计费。
另一种可能的实现方式中，第一消息中的第二指示信息为第一计费识别信息，第一计费识别信息用于识别对应的计费策略；计费对象为绑定参数包含第一计费识别信息的计费策略规则绑定到的一个或多个QoS流(也可以理解为计费对象为与绑定参数包含第一计费识别信息的计费策略规则绑定的一个或多个QoS流)；计费对象的信息为第一计费识别信息。即，本申请实施例中，第一计费识别信息可以作为QoS流绑定时的绑定参数，从而可以实现计费识别标识粒度的数据用量统计，进而实现计费识别标识粒度的计费。
可选的，本申请实施例中，第一消息还用于指示丢弃信息的内容，如丢弃的流量值或者丢弃的数据包的个数。一种可能的实现方式中，用于指示丢弃信息的内容的参数例如可以为上述的第二指示信息。当然，会话管理实体还可以通过第一消息中的其 他信息指示丢弃信息的内容，或者，会话管理实体也可以通过其他方式指示丢弃信息的内容，本申请实施例对此不做具体限定。
图11所示的实施例的具体实现可参考后续图16或图17所示的实施例，在此不再赘述。
基于该方案可知，接入网设备在丢弃计费对象的下行数据包之后，会话管理实体可以获得更新后的数据用量信息，并且更新后的数据用量信息中该计费对象中已丢弃下行数据包的数据用量信息被扣减。换言之，本申请实施例中，在接入网设备丢弃包含计费对象的下行数据包之后，已经被计费的这些下行数据包的数据用量信息将被扣减。这样可以保证会话管理实体获得针对计费对象的更为准确的数据用量信息。进一步的，当会话管理实体与计费功能实体交互时，计费功能实体可以获得针对计费对象的更加准确的数据用量信息，从而可以实现针对计费对象的更加准确的计费。
其中，上述步骤S1101至S1105中接入网设备的动作可以由图8所示的通信装置800中的处理器801调用存储器803中存储的应用程序代码以指令接入网设备执行，上述步骤S1101至S1105中会话管理实体的动作可以由图8所示的通信装置800中的处理器801调用存储器803中存储的应用程序代码以指令会话管理实体执行，本实施例对此不作任何限制。
如图12所示，为本申请实施例提供的一种数据用量更新方法，包括如下步骤：
S1201、接入网设备确定需要上报下行数据包的丢弃信息。
步骤S1201的具体实现可参考图9所示的实施例步骤S901，在此不再赘述。
S1202、接入网设备根据接收到的下行数据包中的计费识别信息，确定第一下行数据包的丢弃信息。其中，第一下行数据包为包含第一计费识别信息的下行数据包。
S1203、接入网设备向会话管理实体发送第三消息。相应的，会话管理实体接收来自接入网设备的第三消息。第三消息包括第一计费识别信息以及第一下行数据包的丢弃信息。
S1204、会话管理实体根据第一计费识别信息以及第一下行数据包的丢弃信息，更新第一下行数据包的数据用量信息。其中，更新后的数据用量信息中已丢弃的第一下行数据包的数据用量信息被扣减。
可选的，本申请实施例提供的数据用量更新方法还可以包括：会话管理实体向用户面实体发送第五指示信息，第五指示信息指示用户面实体在下行数据包中增加计费识别信息。
图12所示的实施例的具体实现可参考后续图17所示的实施例，在此不再赘述。
基于该方案可知，接入网设备在丢弃包含第一计费识别信息的第一下行数据包之后，会话管理实体可以获得更新后的数据用量信息，并且更新后的数据用量信息中第一下行数据包的数据用量信息被扣减。换言之，本申请实施例中，在接入网设备丢弃包含第一计费识别信息的第一下行数据包之后，已经被计费的这些下行数据包的数据用量信息将被扣减。这样可以保证会话管理实体获得计费识别信息粒度的更为准确的数据用量信息。进一步的，当会话管理实体与计费功能实体交互时，计费功能实体可以获得计费识别信息粒度的更加准确的数据用量信息，从而可以实现计费识别信息粒度的更加准确的计费。
其中，上述步骤S1201至S1204中接入网设备的动作可以由图8所示的通信装置800中的处理器801调用存储器803中存储的应用程序代码以指令接入网设备执行，上述步骤S1201至S1204中会话管理实体的动作可以由图8所示的通信装置800中的处理器801调用存储器803中存储的应用程序代码以指令会话管理实体执行，本实施例对此不作任何限制。
下面将以图6或图7所述的通信***应用于如图2a或图2b所示的5G网络为例，对图9至图12所述的数据用量更新方法进行示例性说明。
需要说明的是，本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字等只是一个示例，具体实现中也可以是其他的名字，本申请实施例对此不作具体限定。
结合图9所述的数据用量更新方法，以图6所述的通信***应用于如图2a或图2b所示的5G网络为例，如图13所示，为本申请实施例提供的一种数据用量更新方法，包括如下步骤：
S1301、可选的，SMF确定RAN设备需要上报下行数据包的丢弃信息之后，向RAN设备发送第一指示信息。相应的，RAN设备接收来自SMF的第一指示信息，第一指示信息指示RAN设备需要上报下行数据包的丢弃信息。
一种可能的实现方式中，假设SMF本地配置了需要上报下行数据包的丢弃信息的业务、会话或者切片的信息，则SMF可以根据本地配置，向RAN设备发送第一指示信息，第一指示信息指示RAN设备需要针对特定业务或者特定会话或者特定切片上报下行数据包的丢弃信息。
另一种可能的实现方式中，SMF可以接收来自PCF的指示信息，该指示信息指示RAN设备需要针对特定业务或者特定会话或者特定切片上报下行数据包的丢弃信息。进而，SMF可以根据该指示信息，向RAN设备发送第一指示信息，第一指示信息指示RAN设备需要针对特定业务或者特定会话或者特定切片上报下行数据包的丢弃信息。
可选的，本申请实施例中，第一指示信息还可以指示丢弃信息的内容，如丢弃的流量值或者丢弃的数据包的个数，本申请实施例对此不做具体限定。当然，SMF也可以通过其他方式向RAN设备指示需要上报的丢弃信息的内容，本申请实施例对此不做具体限定。
S1302、RAN设备确定需要上报下行数据包的丢弃信息。
一种可能的实现方式中，若执行上述步骤S1301，则RAN设备可以根据上述第一指示信息确定需要上报下行数据包的丢弃信息。
另一种可能的实现方式中，RAN设备可以根据本地配置确定需要上报下行数据包的丢弃信息。比如，假设RAN设备本地配置了需要上报下行数据包的丢弃信息的业务、会话或者切片的信息，则RAN设备可以根据本地配置，确定需要针对特定业务或者特定会话或者特定切片上报下行数据包的丢弃信息。
S1303、RAN设备丢弃第一下行数据包。
示例性的，RAN设备可以因为流量整形或者拥塞等因素丢弃第一下行数据包，本申请实施例对此不做具体限定。
S1304、RAN设备向UPF发送已丢弃的第一下行数据包的派生数据包。相应的，UPF接收来自RAN设备的第一下行数据包的派生数据包。第一下行数据包的派生数据包的相关描述可参考图9所示的实施例，在此不再赘述。
示例性的，如图14所示，假设下行数据包0成功传输，数据包1、数据包2和数据包3均被丢弃，则RAN设备向UPF发送数据包1的派生数据包(记作数据包11)、数据包2的派生数据包(记作数据包21)以及数据包3的派生数据包(记作数据包31)。其中，图14的示例中，数据包11中包括下行传输的数据包1的内容，数据包21中包括下行传输的数据包2的内容，数据包31中包括下行传输的数据包3的内容。此外，数据包11、数据包21以及数据包31中还包括第一标识。可选的，第一标识可以携带在数据包头中，如通过数据包头的保留位进行表征。以GTP协议为例，可以在GTP-U上行报文头中增加第一标识。其中，GTP-U上行报文头中的目的隧道标识为UPF的隧道标识。
需要说明的是，图13所示的示例仅是派生数据包的一种可能形式，如图9所述的实施例所述，派生数据包还可能存在其他形式，本申请实施例对此不做具体限定。
S1305、UPF根据派生数据包中的第一标识，确定第一下行数据包为已丢弃数据包。
S1306、UPF向SMF发送数据用量更新信息。相应的，SMF接收来自UPF的数据用量更新信息。其中，数据用量更新信息用于将第一下行数据包的数据用量扣减。
本申请实施例中，UPF向SMF发送数据用量更新信息的具体实现可参考图9所示的实施例，在此不再赘述。
示例性的，如图15所示，假设数据包A为正常上行数据包，不包含第一标识；数据包11、数据包21以及数据包31中均包含第一标识。则UPF收到数据包A之后，正常处理数据包A。对于数据包11、数据包21以及数据包31，在UPF根据用于检测上行数据包的PDR中的PDI执行数据包匹配并且匹配通过之后，UPF根据第一标识可以确定第一下行数据包为已丢弃数据包。进而，UPF可以丢弃数据包11、数据包21以及数据包31中的第一标识，并增加丢弃包标志位(如图15中的负值标志位)之后，通过用于检测下行数据包的PDR中的PDI继续进行匹配(因为PDU会话层的内容不变(以IP层为例，这里的目的IP地址还是终端设备的IP地址)，因此数据包11、数据包21以及数据包31依然可以视为下行数据包)。当数据包11、数据包21以及数据包31与第一PDR中检测丢弃包标志位的PDI匹配通过后，UPF根据与第一PDR关联的第一URR将数据用量更新信息上报给SMF。比如，假设数据包1、数据包2和数据包3的数据用量为3M，则此时数据用量更新信息用于将3M的数据用量扣减。
需要说明的是，上述示例以丢弃派生数据包中的第一标识为例进行说明。如图9所示的实施例所述，UPF也可以不丢弃第一标识，而是直接在派生数据包中增加丢弃包标志位之后，通过用于检测下行数据包的PDR中的PDI继续进行匹配。当数据包11、数据包21以及数据包31与第一PDR中检测丢弃包标志位的PDI匹配通过后，UPF根据与第一PDR关联的第一URR将数据用量更新信息上报给SMF。或者，对于数据包11、数据包21以及数据包31，在UPF根据用于检测上行数据包的PDR中的PDI执行数据包匹配并且匹配通过之后，UPF根据第一标识可以确定第一下行数据包为已丢弃数据包。进而，UPF可以根据匹配到的用于检测上行数据包的PDR所关联的 负值URR(即本申请实施例可以为检测上行数据包的PDR关联与正值URR相反的负值URR)将数据用量更新信息上报给SMF，本申请实施例对此不做具体限定。
如图9所示的实施例所述，本申请实施例中，数据用量更新信息可以是UPF根据内部已经统计的数据用量，将第一下行数据包的数据用量扣减后获得的更新后的数据用量；或者，数据用量更新信息可以是第一下行数据包的数据用量，本申请实施例对此不做具体限定。
示例性的，假设SMF向UPF下发的配额为30M，计费事件为“流量阈值到达”后立即上报，参数为10MB(即配额还剩10MB时，会触发计费事件)。则UPF在统计数据用量时，检测到数据包11、数据包21以及数据包31之后，将从已经统计的数据用量中扣减3M，从而获得更新后的数据用量(如已经统计的数据流量为15M，检测到数据包11、数据包21以及数据包31之后，已经统计的数据流量更新为12M)。进一步的，当数据用量使用了20MB时(剩余10MB)，触发了“流量阈值到达”计费事件，UPF会上报数据用量信息到SMF。当然，UPF在检测到数据包11、数据包21以及数据包31之后，可以直接向SMF发送数据包11、数据包21以及数据包31的数据用量(3M)，以使得SMF更新UPF已经上报给SMF的数据用量，本申请实施例对此不做具体限定。其中，配额以及计费事件的相关描述可参考具体实施方式前序部分“计费流程”的描述，在此不再赘述。
可选的，本申请实施例提供的数据用量更新方法中，在UPF向SMF发送数据用量更新信息之前，还可以包括：SMF向UPF发送订阅消息。相应的，UPF接收来自SMF的订阅消息。该订阅消息用于请求订阅数据用量变更事件(或者计费更新事件)。该数据用量变更事件例如可以为数据用量信息发生变更等。
图13所述的实施例的技术效果可参考上述图9所述的实施例的技术效果，在此不再赘述。
其中，上述步骤S1301至S1306中UPF的动作可以由图8所示的通信装置800中的处理器801调用存储器803中存储的应用程序代码以指令UPF执行，上述步骤S1301至S1306中RAN设备的动作可以由图8所示的通信装置800中的处理器801调用存储器803中存储的应用程序代码以指令RAN设备执行，上述步骤S1301至S1306中SMF的动作可以由图8所示的通信装置800中的处理器801调用存储器803中存储的应用程序代码以指令SMF执行，本实施例对此不作任何限制。
结合图11所述的数据用量更新方法，以图7所述的通信***应用于如图2a或图2b所示的5G网络为例，如图16所示，为本申请实施例提供的一种数据用量更新方法，包括如下步骤：
S1601、可选的，PCF确定RAN设备需要上报下行数据包的丢弃信息之后，向SMF发送第三指示信息。相应的，RAN设备接收来自SMF的第三指示信息，第三指示信息指示RAN设备需要上报下行数据包的丢弃信息。
一种可能的实现方式中，第三指示信息可以携带在PCF发送给SMF的PCC规则中。可选的，本申请实施例中，第三指示信息还可以指示丢弃信息的内容，如丢弃的流量值或者丢弃的数据包的个数，本申请实施例对此不做具体限定。当然，PCF也可以通过其他方式向SMF指示需要上报的丢弃信息的内容，本申请实施例对此不做具体 限定。
S1602、SMF确定RAN设备需要上报下行数据包的丢弃信息。
一种可能的实现方式中，若执行上述步骤S1602，则SMF可以根据上述第三指示信息确定RAN设备需要上报下行数据包的丢弃信息。
另一种可能的实现方式中，SMF可以根据本地配置确定RAN设备需要上报下行数据包的丢弃信息。比如，假设SMF本地配置了需要上报下行数据包的丢弃信息的业务、会话或者切片的信息，则SMF可以根据本地配置，确定RAN设备需要针对特定业务或者特定会话或者特定切片上报下行数据包的丢弃信息。
S1603、SMF将计费识别信息作为绑定参数，将具有不同计费识别信息的QoS流绑定到不同的PCC规则。
示例性的，本申请实施例中的计费识别信息例如可以包括charging key或monitoring key。通过将计费识别信息作为绑定参数，可以使得同一QoS流中的数据包，其数据用量统计方式或计费方式一致。
需要说明的是，本申请实施例中的绑定参数还可以包括其他参数，具体可参考具体实施方式前序部分“绑定机制”的相关描述，在此不再赘述。
需要说明的是，本申请实施例中的第一PCC规则为图11所示的实施例中第一计费策略规则的一种具体形式。当然，第一计费策略规则还可以有其他形式，本申请实施例对此不做具体限定。
S1604、SMF向RAN设备发送N2消息1。相应的，RAN设备接收来自SMF的N2消息1。N2消息1中包括第一QoS流的QFI和第二指示信息，第二指示信息指示需要上报下行数据包的丢弃信息。其中，第一QoS流为与第一PCC规则绑定的QoS流，第一PCC规则的绑定参数包括第一计费识别信息，第一计费识别信息用于识别对应的计费策略。
可选的，本申请实施例中，N2消息1还可以指示丢弃信息的内容，如丢弃的流量值或者丢弃的数据包的个数，本申请实施例对此不做具体限定。一种可能的实现方式中，用于指示丢弃信息的内容的参数例如可以为上述的第二指示信息。当然，SMF还可以通过N2消息1中的其他信息指示丢弃信息的内容，或者，SMF也可以通过其他方式指示丢弃信息的内容，本申请实施例对此不做具体限定。
需要说明的是，本申请实施例以第一QoS流的QFI和第二指示信息包含在同一个消息中发送为例进行示意。当然，第一QoS流的QFI和第二指示信息也可以包含在不同的消息中，本申请实施例对此不做具体限定。
需要说明的是，本申请实施例中的N2消息1仅是图11中第一消息的一种示例，第一消息还可以为其他，本申请实施例对此不做具体限定。
S1605、RAN设备根据第二指示信息，确定计费对象的下行数据包的丢弃信息。
示例性的，RAN设备可以因为流量整形或者拥塞等因素丢弃下行数据包，本申请实施例对此不做具体限定。
本申请实施例以计费对象为第一QoS流为例进行说明。
S1606、RAN向SMF发送N2消息2。相应的，SMF接收来自RAN设备的N2消息2。该N2消息2包括第一QoS流的QFI和第一QoS流的下行数据包的丢弃信息。
S1607、SMF根据第一QoS流的QFI和第一QoS流的下行数据包的丢弃信息，更新第一QoS流的数据用量信息，其中，更新后的数据用量信息中第一QoS流的已丢弃下行数据包的数据用量信息被扣减。
需要说明的是，本申请实施例中的N2消息2仅是图11中第二消息的一种示例，第二消息还可以为其他，本申请实施例对此不做具体限定。
图16所述的实施例以图11所述的实施例中的计费对象为第一QoS流为例进行说明，可以实现QoS流粒度的更为准确的数据用量信息统计，从而可以实现QoS流粒度的更加准确的计费。相关技术效果分析可参考上述图11所述的实施例的技术效果分析，在此不再赘述。
其中，上述步骤S1601至S1607中RAN设备的动作可以由图8所示的通信装置800中的处理器801调用存储器803中存储的应用程序代码以指令RAN设备执行，上述步骤S1601至S1607中SMF的动作可以由图8所示的通信装置800中的处理器801调用存储器803中存储的应用程序代码以指令SMF执行，本实施例对此不作任何限制。
结合图11所述的数据用量更新方法，以图7所述的通信***应用于如图2a或图2b所示的5G网络为例，如图17所示，为本申请实施例提供的一种数据用量更新方法，包括如下步骤：
S1701-S1703、同图16所示的实施例步骤S1601-S1603的描述，具体可参考图16所示的实施例，在此不再赘述。
S1704、SMF向RAN设备发送N2消息3。相应的，RAN设备接收来自SMF的N2消息3。N2消息3中包括第一计费识别信息，第一计费识别信息用于指示需要上报下行数据包的丢弃信息。
可选的，本申请实施例中，N2消息3还可以指示丢弃信息的内容，如丢弃的流量值或者丢弃的数据包的个数，本申请实施例对此不做具体限定。一种可能的实现方式中，用于指示丢弃信息的内容的参数例如可以为上述的第一计费识别信息。当然，SMF还可以通过N2消息3中的其他信息指示丢弃信息的内容，或者，SMF也可以通过其他方式指示丢弃信息的内容，本申请实施例对此不做具体限定。
需要说明的是，本申请实施例中的N2消息3仅是图11中第一消息的一种示例，第一消息还可以为其他，本申请实施例对此不做具体限定。
S1705、RAN设备确定计费对象的下行数据包的丢弃信息。
示例性的，RAN设备可以因为流量整形或者拥塞等因素丢弃下行数据包，本申请实施例对此不做具体限定。
本申请实施例以计费对象为绑定参数包含第一计费识别信息的PCC规则绑定到的一个或多个QoS流为例进行说明。
S1706、RAN向SMF发送N2消息4。相应的，SMF接收来自RAN设备的N2消息4。该N2消息4包括第一计费识别信息以及绑定参数包含第一计费识别信息的PCC规则绑定到的一个或多个QoS流的下行数据包的丢弃信息。
需要说明的是，本申请实施例中的N2消息4仅是图11中第二消息的一种示例，第二消息还可以为其他，本申请实施例对此不做具体限定。
S1707、SMF根据第一计费识别信息以及绑定参数包含第一计费识别信息的PCC 规则绑定到的一个或多个QoS流的下行数据包的丢弃信息，更新一个或多个QoS流的数据用量信息，其中，更新后的数据用量信息中绑定参数包含第一计费识别信息的PCC规则绑定到的一个或多个QoS流的已丢弃下行数据包的数据用量信息被扣减。
图17所述的实施例以图11所述的实施例中的计费对象为绑定参数包含第一计费识别信息的计费策略规则绑定到的一个或多个QoS流为例进行说明，可以实现计费识别信息粒度的更为准确的数据用量信息统计，从而可以实现计费识别信息粒度的更加准确的计费。相关技术效果分析可参考上述图11所述的实施例的技术效果分析，在此不再赘述。
其中，上述步骤S1701至S1707中RAN设备的动作可以由图8所示的通信装置800中的处理器801调用存储器803中存储的应用程序代码以指令RAN设备执行，上述步骤S1701至S1707中SMF的动作可以由图8所示的通信装置800中的处理器801调用存储器803中存储的应用程序代码以指令SMF执行，本实施例对此不作任何限制。
结合图12所述的数据用量更新方法，以图7所述的通信***应用于如图2a或图2b所示的5G网络为例，如图18所示，为本申请实施例提供的一种数据用量更新方法，包括如下步骤：
S1801-S1802、同图13所示的实施例步骤S1301-S1302，相关描述可参考图13所示的实施例，在此不再赘述。
S1803、可选的，SMF确定RAN设备需要上报下行数据包的丢弃信息之后，向UPF发送第五指示信息。相应的，UPF接收来自SMF的第五指示信息，第五指示信息指示UPF在下行数据包中增加计费识别信息。
S1804、UPF向RAN设备发送下行数据包。相应的，RAN设备接收来自UPF的下行数据包。该下行数据包中包括对应的计费识别信息。
S1805、RAN设备根据接收到的下行数据包中的计费识别信息，确定第一下行数据包的丢弃信息。其中，第一下行数据包为包含第一计费识别信息的下行数据包。
示例性的，RAN设备可以因为流量整形或者拥塞等因素丢弃下行数据包，本申请实施例对此不做具体限定。
S1806、RAN设备向SMF发送N2消息5。相应的，SMF接收来自RAN设备的N2消息5。N2消息5包括第一计费识别信息以及第一下行数据包的丢弃信息。
需要说明的是，本申请实施例中的N2消息5仅是图12中第三消息的一种示例，第三消息还可以为其他，本申请实施例对此不做具体限定。
S1807、SMF根据第一计费识别信息以及第一下行数据包的丢弃信息，更新第一下行数据包的数据用量信息。其中，更新后的数据用量信息中已丢弃的第一下行数据包的数据用量信息被扣减。
图18所述的实施例的技术效果可参考上述图12所述的实施例的技术效果，在此不再赘述。
其中，上述步骤S1801至S1807中RAN设备的动作可以由图8所示的通信装置800中的处理器801调用存储器803中存储的应用程序代码以指令RAN设备执行，上述步骤S1801至S1807中SMF的动作可以由图8所示的通信装置800中的处理器801调用存储器803中存储的应用程序代码以指令SMF执行，本实施例对此不作任何限制。
可以理解的是，以上各个实施例中，由接入网设备实现的方法和/或步骤，也可以由可用于接入网设备的部件(例如芯片或者电路)实现；由会话管理实体实现的方法和/或步骤，也可以由可用于会话管理实体的部件(例如芯片或者电路)实现；由用户面功能实体实现的方法和/或步骤，也可以由可用于用户面功能实体的部件(例如芯片或者电路)实现。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。相应的，本申请实施例还提供了通信装置，该通信装置用于实现上述各种方法。该通信装置可以为上述方法实施例中的接入网设备，或者包含上述接入网设备的装置，或者为可用于接入网设备的部件；或者，该通信装置可以为上述方法实施例中的会话管理实体，或者包含上述会话管理实体的装置，或者为可用于会话管理实体的部件；或者，该通信装置可以为上述方法实施例中的用户面功能实体，或者包含上述用户面功能实体的装置，或者为可用于用户面功能实体的部件。可以理解的是，该通信装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法实施例中对通信装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
图19示出了一种通信装置190的结构示意图。该通信装置190包括收发模块1901和处理模块1902。所述收发模块1901，也可以称为收发单元用以实现收发功能，例如可以是收发电路，收发机，收发器或者通信接口。
其中，以通信装置190为上述方法实施例中的用户面功能实体为例：
收发模块1901，用于接收来自接入网设备的第一下行数据包的派生数据包，其中，该派生数据包是根据第一下行数据包得到的，该派生数据包中包括第一标识。处理模块1902，用于根据第一标识，确定第一下行数据包为已丢弃数据包。收发模块1901，还用于向会话管理实体发送数据用量更新信息，其中，数据用量更新信息用于将第一下行数据包的数据用量扣减。
可选的，收发模块1901，用于向会话管理实体发送数据用量更新信息，包括：用于在派生数据包中增加丢弃包标志位；根据与第一PDR关联的第一URR将数据用量更新信息上报给会话管理实体，其中，第一URR为负值URR，第一PDR中包括检测丢弃包标志位的PDI。
可选的，收发模块1901，用于向会话管理实体发送数据用量更新信息，包括：用于在丢弃派生数据包中的第一标识后的数据包中增加丢弃包标志位；根据与第一PDR关联的第一URR将数据用量更新信息上报给会话管理实体，其中，第一URR为负值 URR，第一PDR中包括检测丢弃包标志位的PDI。
可选的，收发模块1901，还用于接收来自会话管理实体的第一规则，第一规则包括第一PDR以及与第一PDR关联的第一URR和第二URR；其中，第二URR为正值URR。
可选的，收发模块1901，还用于接收来自会话管理实体的第二规则，第二规则包括第一PDR以及与第一PDR关联的第一URR、第三PDR以及与第三PDR关联的第三URR，其中，第三PDR中包括检测第一下行数据包的PDI，第三URR为正值URR。
可选的，收发模块1901，还用于接收来自会话管理实体的订阅消息，订阅消息用于请求订阅数据用量变更事件信息。
其中，以通信装置190为上述方法实施例中的会话管理实体为例：
处理模块1902，用于确定需要上报下行数据包的丢弃信息。收发模块1901，用于向接入网设备发送第一消息，第一消息包括第二指示信息，第二指示信息指示需要上报下行数据包的丢弃信息。收发模块1901，还用于接收来自接入网设备的第二消息，第二消息包括计费对象的信息和计费对象对应的下行数据包的丢弃信息。处理模块1902，还用于根据计费对象的信息和计费对象对应的下行数据包的丢弃信息，更新计费对象的数据用量信息，其中，更新后的数据用量信息中计费对象中已丢弃下行数据包的数据用量信息被扣减。
其中，以通信装置190为上述方法实施例中的接入网设备为例：
一种可能的实现方式中，处理模块1902，用于确定需要上报下行数据包的丢弃信息。收发模块1901，用于向用户面功能实体发送已丢弃的第一下行数据包的派生数据包，其中，该派生数据包是根据第一下行数据包得到的，该派生数据包中包括第一标识，第一标识用于指示第一下行数据包为已丢弃数据包。
可选的，处理模块1902具体用于：根据来自会话管理实体的第一指示信息确定需要上报下行数据包的丢弃信息，第一指示信息指示需要上报下行数据包的丢弃信息。
可选的，处理模块1902具体用于：根据本地配置确定需要上报下行数据包的丢弃信息。
可选的，处理模块1902用于确定需要上报下行数据包的丢弃信息，包括：用于根据来自策略控制实体的第三指示信息确定需要上报下行数据包的丢弃信息，其中，第三指示信息指示需要上报下行数据包的丢弃信息。
可选的，处理模块1902用于确定需要上报下行数据包的丢弃信息，包括：用于根据本地配置确定需要上报下行数据包的丢弃信息。
另一种可能的实现方式中，收发模块1901，用于接收来自会话管理实体的第一消息，第一消息包括第二指示信息；第二指示信息指示需要上报下行数据包的丢弃信息。处理模块1902，用于根据第二指示信息，确定计费对象的下行数据包的丢弃信息。收发模块1901，还用于向会话管理实体发送第二消息，第二消息包括计费对象的信息和计费对象对应的下行数据包的丢弃信息。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该通信装置190以采用集成的方式划分各个功能模块的形式来呈 现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该通信装置190可以采用图8所示的通信装置800的形式。
比如，图8所示的通信装置800中的处理器801可以通过调用存储器803中存储的计算机执行指令，使得通信装置800执行上述方法实施例中的数据用量更新方法。
具体的，图19中的收发模块1901和处理模块1902的功能/实现过程可以通过图8所示的通信装置800中的处理器801调用存储器803中存储的计算机执行指令来实现。或者，图19中的处理模块1902的功能/实现过程可以通过图8所示的通信装置800中的处理器801调用存储器803中存储的计算机执行指令来实现，图19中的收发模块1901的功能/实现过程可以通过图8中所示的通信装置800中的通信接口804来实现。
由于本实施例提供的通信装置190可执行上述数据用量更新方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
需要说明的是，以上模块或单元的一个或多个可以软件、硬件或二者结合来实现。当以上任一模块或单元以软件实现的时候，所述软件以计算机程序指令的方式存在，并被存储在存储器中，处理器可以用于执行所述程序指令并实现以上方法流程。该处理器可以内置于SoC(片上***)或ASIC，也可是一个独立的半导体芯片。该处理器内处理用于执行软件指令以进行运算或处理的核外，还可进一步包括必要的硬件加速器，如现场可编程门阵列(field programmable gate array，FPGA)、PLD(可编程逻辑器件)、或者实现专用逻辑运算的逻辑电路。
当以上模块或单元以硬件实现的时候，该硬件可以是CPU、微处理器、数字信号处理(digital signal processing，DSP)芯片、微控制单元(microcontroller unit，MCU)、人工智能处理器、ASIC、SoC、FPGA、PLD、专用数字电路、硬件加速器或非集成的分立器件中的任一个或任一组合，其可以运行必要的软件或不依赖于软件以执行以上方法流程。
可选的，本申请实施例还提供了一种芯片***，包括：至少一个处理器和接口，该至少一个处理器通过接口与存储器耦合，当该至少一个处理器执行存储器中的计算机程序或指令时，使得上述任一方法实施例中的方法被执行。在一种可能的实现方式中，该通信装置还包括存储器。可选的，该芯片***可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中 心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (37)

  1. 一种数据用量更新方法，其特征在于，所述方法包括：
    用户面功能实体接收来自接入网设备的第一下行数据包的派生数据包，其中，所述派生数据包是根据所述第一下行数据包得到的，所述派生数据包中包括第一标识；
    所述用户面功能实体根据所述第一标识，确定所述第一下行数据包为已丢弃数据包；
    所述用户面功能实体向会话管理实体发送数据用量更新信息，其中，所述数据用量更新信息用于将所述第一下行数据包的数据用量扣减。
  2. 根据权利要求1所述的方法，其特征在于，所述用户面功能实体向会话管理实体发送数据用量更新信息，包括：
    所述用户面功能实体在所述派生数据包中增加丢弃包标志位；
    所述用户面功能实体根据与第一报文检测规则PDR关联的第一用量上报规则URR将所述数据用量更新信息上报给所述会话管理实体，其中，所述第一URR为负值URR，所述第一PDR中包括检测所述丢弃包标志位的分组检测信息PDI。
  3. 根据权利要求1所述的方法，其特征在于，所述用户面功能实体向会话管理实体发送数据用量更新信息，包括：
    所述用户面功能实体在丢弃所述派生数据包中的所述第一标识后的数据包中增加丢弃包标志位；
    所述用户面功能实体根据与第一PDR关联的第一URR将所述数据用量更新信息上报给所述会话管理实体，其中，所述第一URR为负值URR，所述第一PDR中包括检测所述丢弃包标志位的PDI。
  4. 根据权利要求2或3所述的方法，其特征在于，所述方法还包括：
    所述用户面功能实体接收来自所述会话管理实体的第一规则，所述第一规则包括所述第一PDR以及与所述第一PDR关联的所述第一URR和第二URR；其中，所述第二URR为正值URR。
  5. 根据权利要求2或3所述的方法，其特征在于，所述方法还包括：
    所述用户面功能实体接收来自所述会话管理实体的第二规则，所述第二规则包括所述第一PDR以及与所述第一PDR关联的所述第一URR、第三PDR以及与所述第三PDR关联的第三URR，其中，所述第三PDR中包括检测所述第一下行数据包的PDI，所述第三URR为正值URR。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述方法还包括：
    所述用户面功能实体接收来自所述会话管理实体的订阅消息，所述订阅消息用于请求订阅数据用量变更事件信息。
  7. 一种数据用量更新方法，其特征在于，所述方法包括：
    接入网设备确定需要上报下行数据包的丢弃信息；
    所述接入网设备向用户面功能实体发送已丢弃的第一下行数据包的派生数据包，其中，所述派生数据包是根据所述第一下行数据包得到的，所述派生数据包中包括第一标识，所述第一标识用于指示所述第一下行数据包为已丢弃数据包。
  8. 根据权利要求7所述的方法，其特征在于，所述接入网设备确定需要上报下行 数据包的丢弃信息，包括：
    所述接入网设备根据来自会话管理实体的第一指示信息确定需要上报下行数据包的丢弃信息，所述第一指示信息指示需要上报下行数据包的丢弃信息。
  9. 根据权利要求7所述的方法，其特征在于，所述接入网设备确定需要上报下行数据包的丢弃信息，包括：
    所述接入网设备根据本地配置确定需要上报下行数据包的丢弃信息。
  10. 一种数据用量更新方法，其特征在于，所述方法包括：
    会话管理实体确定需要上报下行数据包的丢弃信息；
    所述会话管理实体向接入网设备发送第一消息，所述第一消息包括第二指示信息，所述第二指示信息指示需要上报下行数据包的丢弃信息；
    所述会话管理实体接收来自所述接入网设备的第二消息，所述第二消息包括计费对象的信息和所述计费对象对应的下行数据包的丢弃信息；
    所述会话管理实体根据所述计费对象的信息和所述计费对象对应的下行数据包的丢弃信息，更新所述计费对象的数据用量信息，其中，更新后的数据用量信息中所述计费对象中已丢弃下行数据包的数据用量信息被扣减。
  11. 根据权利要求10所述的方法，其特征在于，所述第一消息包括第一QoS流的流标识；所述计费对象为所述第一QoS流，所述计费对象的信息为所述第一QoS流的流标识。
  12. 根据权利要求11所述的方法，其特征在于，所述第一QoS流为第一计费策略规则绑定到的QoS流，所述第一计费策略规则的绑定参数包含第一计费识别信息，所述第一计费识别信息用于识别对应的计费策略。
  13. 根据权利要求10所述的方法，其特征在于，所述第二指示信息为第一计费识别信息，所述第一计费识别信息用于识别对应的计费策略；所述计费对象为绑定参数包含所述第一计费识别信息的计费策略规则绑定到的一个或多个QoS流；所述计费对象的信息为所述第一计费识别信息。
  14. 根据权利要求10-13任一项所述的方法，其特征在于，所述第一消息还用于指示所述丢弃信息包括丢弃的流量值或者丢弃的数据包的个数。
  15. 根据权利要求10-14任一项所述的方法，其特征在于，所述会话管理实体确定需要上报下行数据包的丢弃信息，包括：
    所述会话管理实体根据来自策略控制实体的第三指示信息确定需要上报下行数据包的丢弃信息，其中，所述第三指示信息指示需要上报下行数据包的丢弃信息。
  16. 根据权利要求10-14任一项所述的方法，其特征在于，所述会话管理实体确定需要上报下行数据包的丢弃信息，包括：
    所述会话管理实体根据本地配置确定需要上报下行数据包的丢弃信息。
  17. 一种数据用量更新方法，其特征在于，所述方法包括：
    接入网设备接收来自会话管理实体的第一消息，所述第一消息包括第二指示信息；所述第二指示信息指示需要上报下行数据包的丢弃信息；
    所述接入网设备根据所述第二指示信息，确定计费对象的下行数据包的丢弃信息；
    所述接入网设备向所述会话管理实体发送第二消息，所述第二消息包括所述计费 对象的信息和所述计费对象对应的下行数据包的丢弃信息。
  18. 根据权利要求17所述的方法，其特征在于，所述第一消息包括第一QoS流的流标识；所述计费对象为所述第一QoS流，所述计费对象的信息为所述第一QoS流的流标识。
  19. 根据权利要求18所述的方法，其特征在于，所述第一QoS流为第一计费策略规则绑定的QoS流，所述第一计费策略规则的绑定参数包含第一计费识别信息，所述第一计费识别信息用于识别对应的计费策略。
  20. 根据权利要求17所述的方法，其特征在于，所述第二指示信息为所述第一计费识别信息，所述第一计费识别信息用于识别对应的计费策略；所述计费对象为绑定参数包含所述第一计费识别信息的不同计费策略规则绑定到的一个或多个QoS流；所述计费对象的信息为所述第一计费识别信息。
  21. 根据权利要求17-20任一项所述的方法，其特征在于，所述第一消息还用于指示所述丢弃信息包括丢弃的流量值或者丢弃的数据包的个数。
  22. 一种用户面功能实体，其特征在于，所述用户面功能实体包括：处理模块和收发模块；
    所述收发模块，用于接收来自接入网设备的第一下行数据包的派生数据包，其中，所述派生数据包是根据所述第一下行数据包得到的，所述派生数据包中包括第一标识；
    所述处理模块，用于根据所述第一标识，确定所述第一下行数据包为已丢弃数据包；
    所述收发模块，还用于向会话管理实体发送数据用量更新信息，其中，所述数据用量更新信息用于将所述第一下行数据包的数据用量扣减。
  23. 根据权利要求22所述的用户面功能实体，其特征在于，所述收发模块，用于向会话管理实体发送数据用量更新信息，包括：
    用于在所述派生数据包中增加丢弃包标志位；根据与第一报文检测规则PDR关联的第一用量上报规则URR将所述数据用量更新信息上报给所述会话管理实体，其中，所述第一URR为负值URR，所述第一PDR中包括检测所述丢弃包标志位的分组检测信息PDI。
  24. 根据权利要求22所述的用户面功能实体，其特征在于，所述收发模块，用于向会话管理实体发送数据用量更新信息，包括：
    用于在丢弃所述派生数据包中的所述第一标识后的数据包中增加丢弃包标志位；根据与第一PDR关联的第一URR将所述数据用量更新信息上报给所述会话管理实体，其中，所述第一URR为负值URR，所述第一PDR中包括检测所述丢弃包标志位的PDI。
  25. 一种接入网设备，其特征在于，所述接入网设备包括：处理模块和收发模块；
    所述处理模块，用于确定需要上报下行数据包的丢弃信息；
    所述收发模块，用于向用户面功能实体发送已丢弃的第一下行数据包的派生数据包，其中，所述派生数据包是根据所述第一下行数据包得到的，所述派生数据包中包括第一标识，所述第一标识用于指示所述第一下行数据包为已丢弃数据包。
  26. 根据权利要求25所述的接入网设备，其特征在于，所述处理模块具体用于：
    根据来自会话管理实体的第一指示信息确定需要上报下行数据包的丢弃信息，所 述第一指示信息指示需要上报下行数据包的丢弃信息。
  27. 根据权利要求25所述的接入网设备，其特征在于，所述处理模块具体用于：
    根据本地配置确定需要上报下行数据包的丢弃信息。
  28. 一种会话管理实体，其特征在于，所述会话管理实体包括：处理模块和收发模块；
    所述处理模块，用于确定需要上报下行数据包的丢弃信息；
    所述收发模块，用于向接入网设备发送第一消息，所述第一消息包括第二指示信息，所述第二指示信息指示需要上报下行数据包的丢弃信息；
    所述收发模块，还用于接收来自所述接入网设备的第二消息，所述第二消息包括计费对象的信息和所述计费对象对应的下行数据包的丢弃信息；
    所述处理模块，还用于根据所述计费对象的信息和所述计费对象对应的下行数据包的丢弃信息，更新所述计费对象的数据用量信息，其中，更新后的数据用量信息中所述计费对象中已丢弃下行数据包的数据用量信息被扣减。
  29. 根据权利要求28所述的会话管理实体，其特征在于，所述处理模块用于确定需要上报下行数据包的丢弃信息，包括：
    用于根据来自策略控制实体的第三指示信息确定需要上报下行数据包的丢弃信息，其中，所述第三指示信息指示需要上报下行数据包的丢弃信息。
  30. 根据权利要求28所述的会话管理实体，其特征在于，所述处理模块用于确定需要上报下行数据包的丢弃信息，包括：
    用于根据本地配置确定需要上报下行数据包的丢弃信息。
  31. 一种接入网设备，其特征在于，所述接入网设备包括：处理模块和收发模块；
    所述收发模块，用于接收来自会话管理实体的第一消息，所述第一消息包括第二指示信息；所述第二指示信息指示需要上报下行数据包的丢弃信息；
    所述处理模块，用于根据所述第二指示信息，确定计费对象的下行数据包的丢弃信息；
    所述收发模块，还用于向所述会话管理实体发送第二消息，所述第二消息包括所述计费对象的信息和所述计费对象对应的下行数据包的丢弃信息。
  32. 一种通信装置，其特征在于，所述通信装置包括：处理器和存储器；
    所述存储器用于存储计算机执行指令，当所述处理器执行所述计算机执行指令时，以使所述通信装置执行如权利要求1-6或7-9或10-16或17-21中任一项所述的方法。
  33. 一种芯片***，其特征在于，包括：处理器和接口电路；
    所述接口电路，用于接收计算机执行指令并传输至所述处理器；
    所述处理器用于执行所述计算机执行指令，以使所述通信装置执行如权利要求1-6或7-9或10-16或17-21中任一项所述的方法。
  34. 一种计算机可读存储介质，其特征在于，其上存储有计算机程序，当所述计算机程序被计算机执行时使得所述计算机执行权利要求1-6或7-9或10-16或17-21中任一项所述的方法。
  35. 一种计算机程序产品，其特征在于，包括：指令，当所述计算机程序产品在计算机上运行时，使得计算机执行权利要求1-6或7-9或10-16或17-21中任一项所述 的方法。
  36. 一种通信***，其特征在于，所述通信***包括用户面功能实体和接入网设备；
    所述接入网设备，用于确定需要上报下行数据包的丢弃信息之后，向所述用户面功能实体发送已丢弃的第一下行数据包的派生数据包，其中，所述派生数据包是根据所述第一下行数据包得到的，所述派生数据包中包括第一标识，所述第一标识用于指示所述第一下行数据包为已丢弃数据包；
    所述用户面功能实体，用于接收来自所述接入网设备的所述第一下行数据包的派生数据包，并根据所述第一标识，确定所述第一下行数据包为已丢弃数据包之后，向会话管理实体发送数据用量更新信息，其中，所述数据用量更新信息用于将所述第一下行数据包的数据用量扣减。
  37. 一种通信***，其特征在于，所述通信***包括会话管理实体和接入网设备；
    所述会话管理实体，用于确定需要上报下行数据包的丢弃信息之后，向所述接入网设备发送第一消息，所述第一消息包括第二指示信息，所述第二指示信息指示需要上报下行数据包的丢弃信息；
    所述接入网设备，用于接收来自会话管理实体的所述第一消息，并根据所述第二指示信息，确定计费对象的下行数据包的丢弃信息之后，向所述会话管理实体发送第二消息，所述第二消息包括所述计费对象的信息和所述计费对象对应的下行数据包的丢弃信息；
    所述会话管理实体，用于接收来自所述接入网设备的所述第二消息，并根据所述计费对象的信息和所述计费对象对应的下行数据包的丢弃信息，更新所述计费对象的数据用量信息，其中，更新后的数据用量信息中所述计费对象中已丢弃下行数据包的数据用量信息被扣减。
PCT/CN2020/132802 2020-11-30 2020-11-30 数据用量更新方法、装置及*** WO2022110152A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202080107431.1A CN116615922A (zh) 2020-11-30 2020-11-30 数据用量更新方法、装置及***
PCT/CN2020/132802 WO2022110152A1 (zh) 2020-11-30 2020-11-30 数据用量更新方法、装置及***

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/132802 WO2022110152A1 (zh) 2020-11-30 2020-11-30 数据用量更新方法、装置及***

Publications (1)

Publication Number Publication Date
WO2022110152A1 true WO2022110152A1 (zh) 2022-06-02

Family

ID=81753889

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/132802 WO2022110152A1 (zh) 2020-11-30 2020-11-30 数据用量更新方法、装置及***

Country Status (2)

Country Link
CN (1) CN116615922A (zh)
WO (1) WO2022110152A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115915044A (zh) * 2022-11-03 2023-04-04 广州爱浦路网络技术有限公司 一种用量信息传输方法、装置及网元
WO2024031403A1 (zh) * 2022-08-09 2024-02-15 北京小米移动软件有限公司 信息处理方法及装置、通信设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101431423A (zh) * 2008-12-24 2009-05-13 华为技术有限公司 一种用户业务流计费核减方法和装置
CN103718579A (zh) * 2013-06-20 2014-04-09 华为技术有限公司 计费处理方法、装置及***
CN109462488A (zh) * 2017-09-06 2019-03-12 中兴通讯股份有限公司 获取用户设备数据流量的方法、会话管理功能及存储介质
US10412625B1 (en) * 2018-04-24 2019-09-10 Verizon Patent And Licensing Inc. Systems and methods for tracking and calculating network usage in a network with multiple user plane functions
WO2020001795A1 (en) * 2018-06-25 2020-01-02 Telefonaktiebolaget Lm Ericsson (Publ) A method of reporting traffic metrics by a user plane function, upf, to a session management function, smf, in a telecommunication network, as well as a corresponding upf
CN111436030A (zh) * 2019-01-15 2020-07-21 华为技术有限公司 数据用量上报的方法、装置及***

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101431423A (zh) * 2008-12-24 2009-05-13 华为技术有限公司 一种用户业务流计费核减方法和装置
CN103718579A (zh) * 2013-06-20 2014-04-09 华为技术有限公司 计费处理方法、装置及***
CN109462488A (zh) * 2017-09-06 2019-03-12 中兴通讯股份有限公司 获取用户设备数据流量的方法、会话管理功能及存储介质
US10412625B1 (en) * 2018-04-24 2019-09-10 Verizon Patent And Licensing Inc. Systems and methods for tracking and calculating network usage in a network with multiple user plane functions
WO2020001795A1 (en) * 2018-06-25 2020-01-02 Telefonaktiebolaget Lm Ericsson (Publ) A method of reporting traffic metrics by a user plane function, upf, to a session management function, smf, in a telecommunication network, as well as a corresponding upf
CN111436030A (zh) * 2019-01-15 2020-07-21 华为技术有限公司 数据用量上报的方法、装置及***

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024031403A1 (zh) * 2022-08-09 2024-02-15 北京小米移动软件有限公司 信息处理方法及装置、通信设备及存储介质
CN115915044A (zh) * 2022-11-03 2023-04-04 广州爱浦路网络技术有限公司 一种用量信息传输方法、装置及网元
CN115915044B (zh) * 2022-11-03 2023-10-24 广州爱浦路网络技术有限公司 一种用量信息传输方法、装置及网元

Also Published As

Publication number Publication date
CN116615922A (zh) 2023-08-18

Similar Documents

Publication Publication Date Title
US10999758B2 (en) Systems and method for quality of service monitoring, policy enforcement, and charging in a communications network
US20210014157A1 (en) Quality-of-Service Monitoring Method and Apparatus
CN111432440B (zh) 实现业务连续性的方法、装置及***
WO2021012697A1 (zh) 应用mos模型的训练方法、设备及***
WO2020063694A1 (zh) 一种切片信息处理方法及装置
KR102581335B1 (ko) 서비스 품질 모니터링 방법 및 시스템, 및 디바이스
EP3675551B1 (en) Method and system for detecting quality of service of service
US20210345174A1 (en) Method, apparatus, and system for reporting data usage
EP2999261B1 (en) Policy and charging rules entity, wireless communications method and wireless communications system
WO2022110152A1 (zh) 数据用量更新方法、装置及***
US20220256390A1 (en) Quality of service information notification method, device, and system
WO2021146926A1 (zh) 一种数据传输方法、设备及***
US11483685B2 (en) Systems and methods for distributed charging in digital telecommunications networks
WO2020169039A1 (zh) 一种策略管理的方法及装置
US20220086243A1 (en) Method, device, and system
WO2021238331A1 (zh) 获取网络资源的方法、设备及***
WO2021103009A1 (zh) 上行pdr的生成方法、装置及***
WO2022193127A1 (zh) 业务调度方法、装置及***
WO2021046746A1 (zh) 上报会话管理信息的方法、设备及***
WO2020192263A1 (zh) 计费规则绑定的方法、设备及***
WO2017166031A1 (zh) 区分接入网的方法、装置及计算机可读存储介质
US20230379233A1 (en) Packet Loss Rate Detection Method, Communication Apparatus, and Communication System
WO2023143255A1 (zh) 一种通信方法及装置
WO2023236905A1 (zh) 时延可靠性确定方法、接入网设备及存储介质
WO2023185402A1 (zh) 通信方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20963040

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202080107431.1

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20963040

Country of ref document: EP

Kind code of ref document: A1