WO2022110152A1 - Procédé, appareil et système de mise à jour d'utilisation de données - Google Patents

Procédé, appareil et système de mise à jour d'utilisation de données 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)
Chinese (zh)
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 PCT/CN2020/132802 priority Critical patent/WO2022110152A1/fr
Priority to CN202080107431.1A priority patent/CN116615922A/zh
Publication of WO2022110152A1 publication Critical patent/WO2022110152A1/fr

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

Des modes de réalisation de la présente demande concernent un procédé, un appareil et un système de mise à jour d'utilisation de données, permettant d'améliorer la précision d'un résultat de statistiques d'utilisation de données. Le procédé comprend les étapes suivantes : une entité de fonction de plan d'utilisateur reçoit un paquet de données dérivées d'un premier paquet de données de liaison descendante à partir d'un dispositif de réseau d'accès, le paquet de données dérivées étant obtenu selon le premier paquet de données de liaison descendante, et le paquet de données dérivées comprenant un premier identifiant ; l'entité de fonction de plan d'utilisateur détermine, en fonction du premier identifiant, que le premier paquet de données de liaison descendante est un paquet de données rejeté ; et l'entité de fonction de plan d'utilisateur transmet des informations de mise à jour d'utilisation de données à une entité de gestion de session, les informations de mise à jour d'utilisation de données étant utilisées pour déduire l'utilisation de données du premier paquet de données de liaison descendante.
PCT/CN2020/132802 2020-11-30 2020-11-30 Procédé, appareil et système de mise à jour d'utilisation de données WO2022110152A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2020/132802 WO2022110152A1 (fr) 2020-11-30 2020-11-30 Procédé, appareil et système de mise à jour d'utilisation de données
CN202080107431.1A CN116615922A (zh) 2020-11-30 2020-11-30 数据用量更新方法、装置及系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/132802 WO2022110152A1 (fr) 2020-11-30 2020-11-30 Procédé, appareil et système de mise à jour d'utilisation de données

Publications (1)

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

Family

ID=81753889

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/132802 WO2022110152A1 (fr) 2020-11-30 2020-11-30 Procédé, appareil et système de mise à jour d'utilisation de données

Country Status (2)

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

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 (fr) * 2022-08-09 2024-02-15 北京小米移动软件有限公司 Procédé et appareil de traitement d'informations, dispositif de communication et support de stockage

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 (fr) * 2018-06-25 2020-01-02 Telefonaktiebolaget Lm Ericsson (Publ) Procédé de rapport de métriques de trafic par une fonction de plan utilisateur, upf, à une fonction de gestion de session, smf, dans un réseau de télécommunication, ainsi qu'une upf correspondante
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 (fr) * 2018-06-25 2020-01-02 Telefonaktiebolaget Lm Ericsson (Publ) Procédé de rapport de métriques de trafic par une fonction de plan utilisateur, upf, à une fonction de gestion de session, smf, dans un réseau de télécommunication, ainsi qu'une upf correspondante
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 (fr) * 2022-08-09 2024-02-15 北京小米移动软件有限公司 Procédé et appareil de traitement d'informations, dispositif de communication et support de stockage
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 (fr) Procédé, dispositif et système d'entraînement faisant appel à un modèle mos
WO2020063694A1 (fr) Procédé et dispositif de traitement d'informations de tranches
EP3675551B1 (fr) Procédé et système de détection d'une qualité de service de service
KR102581335B1 (ko) 서비스 품질 모니터링 방법 및 시스템, 및 디바이스
US20210345174A1 (en) Method, apparatus, and system for reporting data usage
EP2999261B1 (fr) Policy and charging rules unité, procédé de communication sans fil et système de communication sans fil
WO2022110152A1 (fr) Procédé, appareil et système de mise à jour d'utilisation de données
US20220256390A1 (en) Quality of service information notification method, device, and system
WO2023236905A1 (fr) Procédé de détermination de fiabilité de retard, dispositif de réseau d'accès et support de stockage
US11483685B2 (en) Systems and methods for distributed charging in digital telecommunications networks
WO2020169039A1 (fr) Procédé et dispositif de gestion de politique
US20220086243A1 (en) Method, device, and system
WO2021238331A1 (fr) Procédé, dispositif et système d'acquisition de ressources de réseau
US20220353731A1 (en) Data Transmission Method, Device, and System
WO2021103009A1 (fr) Procédé, appareil et système de génération de pdr en liaison montante
WO2022193127A1 (fr) Procédé et appareil de planification de service, et système
WO2021046746A1 (fr) Procédé, dispositif et système de rapport d'informations de gestion de session
WO2020192263A1 (fr) Procédé, dispositif et système d'association de règles de facturation
WO2017166031A1 (fr) Procédé et dispositif permettant de distinguer un réseau d'accès, et support de stockage lisible par ordinateur
US20230379233A1 (en) Packet Loss Rate Detection Method, Communication Apparatus, and Communication System
WO2023143255A1 (fr) Procédé et appareil de communication
WO2023185402A1 (fr) Procédé et appareil de communication

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