Communication method and communication device

Abstract

Provided are a communication method and a communication device, the method comprising: determining a first service flow, the first service flow being used for indicating a data volume successfully transmitted by a data radio bearer in a downlink, the first service flow comprising a data volume transmitted in a time slot when data in a cache region is emptied; and determining a first service time length, the first service time length being used for indicating a time length for transmitting the first service traffic, the first service time length comprising a time length occupied when the data of the cache region is emptied, and the first service traffic and the first service time length being used for determining a downlink rate of the terminal device. According to the invention, the data volume in the time slot when all the cached data are emptied is converted and compensated, so that the downlink rate result can reflect the rate of the user with good channel quality or the user with poor channel quality in a more balanced manner, the conversion proportion is improved, the statistical distortion is avoided, and the accuracy of the UE downlink rate statistical result can be improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Technology

[0002] The transmission rate of user equipment (UE) is a key indicator for operators to evaluate and assess communication performance.

[0003] The current protocol defines the statistical principles for UE transmission rate metrics. These principles exclude data transmitted in time slots where the buffer is cleared, leading to distorted statistical results. Although current technology provides compensation schemes, significant deviations may still exist. Summary of the Invention

[0004] This application provides a communication method and communication device. Based on the assumption of a large packet continuous service model, it restores the true air interface rate capability of the UE under the large packet continuous service model by compensating for the amount of data in the time slot when all cached data is cleared. This can more fairly reflect the proportion of sample points with good and poor channel quality under NR cell.

[0005] In a first aspect, a communication method is provided, which can be executed by a first device or by a chip or circuit configured in the first device, wherein the first device can be a domain management function unit or a network element, and this application does not limit it.

[0006] The method may include: determining a first service traffic, the first service traffic indicating the amount of data successfully transmitted in a downlink by a data radio bearer, the first service traffic including the amount of data transmitted in the time slot when the data in the buffer is cleared; determining a first service duration, the first service duration indicating the duration of transmitting the first service traffic, the first service duration including the duration occupied when the data in the buffer is cleared, the first service traffic and the first service duration being used to determine the downlink rate of one or more terminal devices.

[0007] The time taken when the data in the buffer is cleared can be understood as including the time taken when the data sent in the last slot is cleared, or it can be understood as including the time taken when the data sent in the last slot is cleared, or it can be understood as including the time taken when the RLC layer sends data in the last slot burst.

[0008] Based on the above technical solution, by calculating and compensating for the amount of data in the time slot where all cached data is cleared, the downlink rate results more evenly reflect the rates of users with good channel quality or users with poor channel quality, improve the calculation ratio, avoid statistical distortion, and thus improve the accuracy of UE downlink rate statistics.

[0009] In conjunction with the first aspect, in some implementations of the first aspect, the duration occupied when the data in the buffer is cleared is determined based on the ratio of the amount of data transmitted in the time slot where the data in the buffer is cleared to the amount of data in the transmission block scheduled when the buffer reaches saturation.

[0010] For example, when the buffer reaches saturation, the data volume of the scheduled transmission block can be greater than the data volume of the maximum available RB when the data volume of the buffer is greater than the data volume of the transmission block when the wireless air interface transmission capacity is greater. It can be understood that when the buffer reaches saturation, the data volume of the scheduled transmission block is the data volume of the transmission block of the last time slot data burst when the last time slot data burst is in a full buffer.

[0011] In this technical solution, a compensation calculation is performed based on the assumption that the data in the buffer is much larger than the NR air interface transmission capacity, so that the calculated UE rate result is more consistent with the actual rate capability of the UE.

[0012] In conjunction with the first aspect, in some implementations of the first aspect, the amount of data transmitted in the time slot where the data in the buffer is cleared is statistically determined by layer 2.

[0013] For example, the amount of data transmitted in the time slot when the buffer data is cleared can be counted by the RLC layer or MAC layer.

[0014] In conjunction with the first aspect, in some implementations of the first aspect, the amount of data transmitted in the time slot where the data in the buffer is cleared is the first data amount, which is the difference between the total data amount of the transmission block corresponding to the time slot where the data in the buffer is cleared and the amount of data of the padding bits added to the transmission block corresponding to the time slot.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, the first service traffic also includes the amount of data transmitted in the time slot where the data in the buffer was successfully transmitted and not cleared.

[0016] In this technical solution, the first service traffic includes the amount of data transmitted in the time slot when all data in the buffer is cleared. This amount of data transmitted in the time slot when all data in the buffer is cleared can include the amount of data transmitted in a single transmission within the buffer, or the amount of data transmitted in the buffer that is not transmitted in a single transmission. This improves the conversion ratio, making the downlink rate result more evenly reflect the rates of users with good or poor channel quality, thus avoiding statistical distortion.

[0017] In conjunction with the first aspect, in some implementations of the first aspect, the first service duration also includes the duration occupied when the data in the buffer is successfully transmitted and not cleared.

[0018] In this technical solution, the first service duration includes the time occupied when the data in the buffer is cleared, and also includes the time occupied when the data in the buffer is successfully transmitted without being cleared. This improves the conversion ratio, making the downlink rate result more evenly reflect the rate of users with good channel quality or users with poor channel quality, and avoiding statistical distortion.

[0019] In conjunction with the first aspect, in some implementations of the first aspect, the downlink rate of the one or more terminal devices is determined based on the first service traffic and the first service duration.

[0020] In this technical solution, by calculating and compensating for the amount of data in the time slot where all cached data is cleared, the downlink rate results more evenly reflect the rates of users with good channel quality or users with poor channel quality, thus avoiding statistical distortion.

[0021] In conjunction with the first aspect, in certain implementations of the first aspect, the downlink rate of each of the one or more terminal devices satisfies:

[0022] UE Throughput in DL=(ThpVolDl+ThpVolDl_Last_Slot) / (ThpTimeDl+ThpTimeDL_LastSlot),

[0023] Wherein, UE Throughput in DL represents the downlink rate of the terminal device, ThpVolDl represents the amount of data transmitted in the time slot when the data in the buffer is successfully transmitted and not cleared, ThpVolDl_Last_Slot represents the amount of data transmitted in the time slot when the data in the buffer is cleared, ThpTimeDl represents the duration occupied when the data in the buffer is successfully transmitted and not cleared, and ThpTimeDL_LastSlot represents the duration occupied when the data in the buffer is cleared.

[0024] In conjunction with the first aspect, in some implementations of the first aspect, the downlink rate distribution statistics and / or average downlink rate statistics of multiple terminal devices are determined based on the first service traffic and the first service duration.

[0025] In conjunction with the first aspect, in some implementations of the first aspect, the first device reports the statistical results of the air interface transmission rate of the terminal device to the cross-domain management node.

[0026] For example, the statistical results of the downlink rate of the terminal device include at least one of the following: UE downlink rate (UE Throughput in DL), distribution of DL UE throughput in gNB statistics, and average DL UE throughput in gNB statistics.

[0027] Secondly, a communication device is provided, which may be a first device or a chip or circuit configured in the first device, wherein the first device may be a domain management function unit or a network element, and this application does not limit it.

[0028] The device may include: a processing unit configured to determine a first service traffic, the first service traffic indicating the amount of data successfully transmitted in a downlink by a data radio bearer, the first service traffic including the amount of data transmitted in the time slot when the data in the buffer is cleared; the processing unit further configured to determine a first service duration, the first service duration indicating the duration of transmitting the first service traffic, the first service duration including the duration occupied when the data in the buffer is cleared, the first service traffic and the first service duration being used to determine the downlink rate of one or more terminal devices.

[0029] In conjunction with the second aspect, in some implementations of the second aspect, the duration occupied when the data in the buffer is cleared is determined based on the ratio of the amount of data transmitted in the time slot where the data in the buffer is cleared to the amount of data in the transmission block scheduled when the buffer reaches saturation.

[0030] In conjunction with the second aspect, in some implementations of the second aspect, the amount of data transmitted in the time slot where the data in the buffer is cleared is statistically determined by layer 2.

[0031] In conjunction with the second aspect, in some implementations of the second aspect, the amount of data transmitted in the time slot where the data in the buffer is cleared is the first data amount, which is the difference between the total data amount of the transmission block corresponding to the time slot where the data in the buffer is cleared and the amount of data of the padding bits added to the transmission block corresponding to the time slot.

[0032] In conjunction with the second aspect, in some implementations of the second aspect, the first service traffic also includes the amount of data transmitted in the time slot where the data in the buffer was successfully transmitted and not cleared.

[0033] In conjunction with the second aspect, in some implementations of the second aspect, the first service duration also includes the duration occupied when the data in the buffer is successfully transmitted and not cleared.

[0034] In conjunction with the second aspect, in some implementations of the second aspect, the processing unit is further configured to determine the downlink rate of the one or more terminal devices based on the first service traffic and the first service duration.

[0035] In conjunction with the second aspect, in some implementations of the second aspect, the downlink rate of the terminal device is determined by the following formula:

[0036] UE Throughput in DL=(ThpVolDl+ThpVolDl_Last_Slot) / (ThpTimeDl+ThpTimeDL_LastSlot),

[0037] Wherein, UE Throughput in DL represents the downlink rate of the terminal device, ThpVolDl represents the amount of data transmitted in the time slot when the data in the buffer is successfully transmitted and not cleared, ThpVolDl_Last_Slot represents the amount of data transmitted in the time slot when the data in the buffer is cleared, ThpTimeDl represents the duration occupied when the data in the buffer is successfully transmitted and not cleared, and ThpTimeDL_LastSlot represents the duration occupied when the data in the buffer is cleared.

[0038] In conjunction with the second aspect, in some implementations of the second aspect, the processing unit is further configured to determine downlink rate distribution statistics and / or average downlink rate statistics of multiple terminal devices based on the first service traffic and the first service duration.

[0039] In conjunction with the second aspect, in some implementations of the second aspect, the communication device further includes a transceiver unit for transmitting at least one of the downlink rate of the terminal device, downlink user rate distribution statistics, and average downlink user rate.

[0040] In conjunction with the second aspect, in some implementations of the second aspect, the transceiver unit is also used to report the statistical results of the air interface transmission rate of the terminal device to the cross-domain management node.

[0041] For example, the statistical results of the downlink rate of the terminal device include at least one of the following: UE downlink rate (UE Throughput in DL), distribution of DL UE throughput in gNB statistics, and average DL UE throughput in gNB statistics.

[0042] Thirdly, a communication apparatus is provided for performing the method provided in the first aspect. Specifically, the apparatus may include units and / or modules for performing the method provided in any of the above implementations of the first aspect, such as processing units and / or communication units.

[0043] In one implementation, the device is a communication device (such as a terminal device or a network device). When the device is a communication device, the communication unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0044] In another implementation, the device is a chip, chip system, or circuit used in a communication device. When the device is a chip, chip system, or circuit used in a device, the communication unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit can be at least one processor, processing circuit, or logic circuit.

[0045] Fourthly, a communication device is provided, the device comprising: at least one processor for executing the method provided in any of the above implementations of the first aspect.

[0046] Optionally, the device further includes: a memory for storing a program; correspondingly, at least one processor for executing the computer program or instructions stored in the memory.

[0047] In one implementation, the device is a communication device (such as a terminal device or a network device).

[0048] In another implementation, the device is a chip, chip system, or circuit used in a communication device.

[0049] Fifthly, this application provides a processor for performing the method provided in the first aspect above.

[0050] Unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, the transmission and acquisition / reception operations involved in the processor can be understood as processor output and input operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.

[0051] In a sixth aspect, a computer-readable storage medium is provided that stores program code for execution by a device, the program code including a method for performing any of the above-described implementations of the first aspect.

[0052] In a seventh aspect, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the method provided by any of the above implementations of the first aspect.

[0053] Eighthly, a chip is provided, the chip including a processor and a communication interface, the processor reading instructions stored in a memory through the communication interface and executing the method provided by any of the above implementations of the first aspect.

[0054] Optionally, as one implementation, the chip also includes a memory storing computer programs or instructions, and a processor is used to execute the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the processor is used to execute the method provided by any of the above implementations of the first aspect. Attached Figure Description

[0055] Figure 1 This is a schematic diagram of a service-oriented management architecture 100 applicable to embodiments of this application.

[0056] Figure 2 This is a schematic diagram of a communication system 200 applicable to an embodiment of this application.

[0057] Figure 3 This is a schematic diagram of data transmission under a bursty small packet service applicable to an embodiment of this application.

[0058] Figure 4 This is a data transmission diagram for a large-package continuous download service applicable to embodiments of this application.

[0059] Figure 5 This is a schematic diagram of a UE downlink rate statistics method applicable to embodiments of this application.

[0060] Figure 6 This is a schematic diagram of a communication method 600 applicable to an embodiment of this application.

[0061] Figure 7This is a schematic diagram of a communication device 700 applicable to an embodiment of this application.

[0062] Figure 8 This is a structural block diagram of a communication device 800 applicable to embodiments of this application. Detailed Implementation

[0063] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0064] The technical solutions provided in this application can be applied to various communication systems, such as 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, and LTE time division duplex (TDD) systems. The technical solutions provided in this application can also be applied to future communication systems, such as 6th generation (6G) mobile communication systems. The technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems. The technical solutions provided in this application can also be applied to non-terrestrial network (NTN) systems such as inter-satellite communication and satellite communication.

[0065] As an example, a satellite communication system includes a satellite base station and terminal equipment. The satellite base station provides communication services to the terminal equipment. Satellite base stations can also communicate with each other. A satellite can act as a base station or as a terminal device. Here, "satellite" can refer to drones, hot air balloons, low-Earth orbit satellites, medium-Earth orbit satellites, high-Earth orbit satellites, etc. "Satellite" can also refer to non-terrestrial base stations or non-terrestrial equipment.

[0066] As an example, V2X communication can include: vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, and vehicle-to-network (V2N) communication.

[0067] In a communication system, a device can send signals to or receive signals from another device. These signals can include information, signaling, or data. The term "device" can also be replaced by an entity, network entity, communication equipment, communication device, communication module, node, communication node, etc. This disclosure uses a device as an example for description.

[0068] The terminal devices in this application include various devices with wireless communication capabilities, which can be used to connect people, objects, machines, etc. These terminal devices can be widely applied in various scenarios, such as: cellular communication, D2D, V2X, peer-to-peer (P2P), M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, etc. The terminal device can be a terminal in any of the above scenarios, such as an MTC terminal, an IoT terminal, etc. Terminal equipment can be a user equipment (UE), terminal, fixed equipment, mobile station equipment or mobile device, subscriber unit, handheld device, vehicle-mounted equipment, wearable device, cellular phone, smartphone, session initiation protocol (SIP) phone, wireless data card, personal digital assistant (PDA), computer, tablet computer, laptop computer, wireless modem, handset, laptop computer, computer with wireless transceiver capability, smart book, vehicle, satellite, global positioning system (GPS) device, target tracking device, aircraft (e.g., drone, helicopter, or airplane), boat, remote control device, smart home device, industrial equipment, or a device built into the above devices (e.g., a communication module, modem, or chip in the above devices), or other processing devices connected to a wireless modem. For ease of description, the terminal equipment will be described below using terminals or UEs as examples.

[0069] It should be understood that in certain scenarios, a UE can also be used as a base station. For example, a UE can act as a scheduling entity, providing sidelink signaling between UEs in scenarios such as V2X, D2D, or P2P.

[0070] In this embodiment, the device used to implement the functions of the terminal device, i.e., the terminal device, can be the terminal device itself, or it can be a device that supports the terminal device in implementing the functions, such as a chip system or a chip. This device can be installed in the terminal device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0071] The network device in this application embodiment can be a device for communicating with a terminal device. This network device can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitter, master station, auxiliary station, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. Base stations can also be mobile switching centers, devices that perform base station functions in D2D, V2X, and M2M communications, network-side devices in 6G networks, and devices that perform base station functions in future communication systems. Base stations can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0072] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0073] In some deployments, the network devices mentioned in the embodiments of this application may be devices including CU, or DU, or devices including CU and DU, or devices with control plane CU nodes (central unit-control plane (CU-CP)) and user plane CU nodes (central unit-user plane (CU-UP)) and DU nodes.

[0074] In some deployments, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be CUs, DUs, CU-CPs, CU-UPs, or radio units (RUs). CUs and DUs can be configured separately or included in the same network element, such as a BBU. RUs can be included in radio frequency equipment or radio frequency units, such as RRUs, AAUs, or RRHs.

[0075] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, a radio access network can also be an open radio access network (O-RAN) architecture. In an ORAN system, CU can also be called an open CU (open CU, O-CU), DU can also be called an open DU (open DU, O-DU), CU-CP can also be called an open CU-CP (O-CU-CP), CU-UP can also be called an open CU-UP (O-CU-UP), and RU can also be called an open RU (open RU, O-RU). Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0076] In this embodiment, the apparatus for implementing the functions of a network device can be the network device itself, or it can be an apparatus capable of supporting the network device in implementing those functions, such as a chip system or a chip. This apparatus can be installed within the network device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete components.

[0077] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

[0078] First, combine Figure 1 The system architecture applicable to the embodiments of this application is described below.

[0079] See Figure 1 As an example, Figure 1 This is a schematic diagram of a service-oriented management architecture 100 applicable to embodiments of this application. For example... Figure 1 As shown, the service-oriented management architecture includes a business support system (BSS), a cross-domain management function (CD-MnF), a domain management function (Domain-MnF), and at least one element.

[0080] The business support system is oriented towards communication services and provides functions and management services such as billing, settlement, accounting, customer service, sales, network monitoring, communication service lifecycle management, and service intent translation. This business support system can be an operator's operating system or a vertical OT system; this application embodiment does not limit this.

[0081] The cross-domain management function unit, also known as the network management function (NMF), can be a network management system (NMS) or a network function management service consumer (NFMS_C). For example, the cross-domain management function unit can provide one or more of the following management functions or services: network lifecycle management, network deployment, network fault management, network performance management, network configuration management, network assurance, network optimization, and translation of network intents from communication service providers (Intent-CSP).

[0082] The network referred to in the aforementioned management functions or services may include one or more network elements or sub-networks, or it may be a network slice. That is to say, the network management function unit may be a network slice management function (NSMF), a management data analytical function (MDAF), a self-organization network function (SON Function), or an intent-driven management service (MnS), etc., and the embodiments of this application do not limit it.

[0083] Optionally, in certain deployment scenarios, the cross-domain management function unit can also provide sub-network lifecycle management, sub-network deployment, sub-network fault management, sub-network performance management, sub-network configuration management, sub-network assurance, sub-network optimization functions, and translation of network intents (Intent-CSP) from service producers or network intents (intent from communication service consumer, Intent-CSC) from service consumers in the sub-network. Here, a sub-network consists of multiple smaller sub-networks, which can be network slice sub-networks.

[0084] The domain management function unit can also be called a sub-network management function (NMF) or a network element management function unit. For example, the domain management function unit can be a wireless automation engine (MBBautomation engine, MAE), an element management system (EMS), a network function management service provider (NFMS_P), or other network element management entities. This application embodiment does not limit this.

[0085] For example, the domain management function unit can provide one or more of the following functions or management services: subnetwork or network element lifecycle management, subnetwork or network element deployment, subnetwork or network element fault management, subnetwork or network element performance management, subnetwork or network element assurance, subnetwork or network element optimization functions, and translation of subnetwork or network element intents from network operators (Intent-NOPs). Here, a subnetwork includes one or more network elements. A subnetwork can also include other subnetworks, meaning one or more subnetworks can form a larger subnetwork.

[0086] Optionally, the subnet here can also be a network slice subnet. The domain management system can be a network slice subnet management function (NSSMF), a management data analytical function (Domain MDAF), a self-organizing network function (SON Function), an IntentDriven MnS, etc.

[0087] The domain management functional units can be classified as follows:

[0088] Based on network type, domain management functions can be categorized into: Radio Access Network Domain Management Function (RAN-Domain-MnF), Core Network Domain Management Function (CN-Domain-MnF), and Transport Network Domain Management Function (TN-Domain-MnF). It's important to note that a domain management function unit can also be a domain network management system, capable of managing one or more of the access network, core network, or transport network.

[0089] According to administrative regions, they can be divided into: regional management functional units of a certain region, such as regional management functional unit of city A, regional management functional unit of city B, etc.

[0090] Among them, network elements are entities that provide network services, and can also be called network devices, including core network elements, access network elements, etc.

[0091] For example, core network elements may include: access and mobility management function (AMF), session management function (SMF), policy control function (PCF), network data analytical function (NWDAF), network repository function (NRF), and gateways, etc. Access network elements include: base stations (such as gNB, eNB), central unit control plane (CUCP), central unit (CU), distribution unit (DU), central unit user plane (CUUP), etc.

[0092] For example, a network element can provide one or more of the following management functions or services: network element lifecycle management, network element deployment, network element fault management, network element performance management, network element assurance, network element optimization functions, and network element intent translation, etc.

[0093] For example, the cross-domain management function unit can be nodes such as NMS, MnS producer, and MnS consumer.

[0094] For example, the domain management functional unit can be nodes such as EMS, MAE, MnS Producer, and MnS Consumer.

[0095] In one possible implementation, if the management service is a management service provided by the cross-domain management functional unit, then the cross-domain management functional unit is the management service producer, and the business support system is the management service consumer.

[0096] In another possible implementation, if the management service is a management service provided by the domain management functional unit, then the domain management functional unit is the management service producer, and the cross-domain management functional unit is the management service consumer.

[0097] In another possible implementation, if the management service is a management service provided by the network element, then the network element is the management service producer and the domain management functional unit is the management service consumer.

[0098] In this embodiment, the domain management function unit can be used for the statistics and reporting of the air interface transmission rate of the terminal device. Firstly, combined with... Figure 2The communication system applicable to the embodiments of this application is briefly described below.

[0099] Figure 2 This is a schematic diagram of a communication system 200 applicable to embodiments of this application. For example... Figure 2 As shown, the wireless communication system 200 may include at least one network device, such as Figure 2 The network devices 110a and 110b shown (collectively referred to as network device 110) may also include at least one terminal device, such as Figure 2 The terminal devices 120a-120j shown are collectively referred to as terminal devices 120. Both network devices and terminal devices can be configured with multiple antennas, and network devices and terminal devices can communicate using multi-antenna technology. Terminal devices can also communicate with each other. For example, terminal devices can communicate directly with each other. Alternatively, terminal devices can communicate with each other through other communication devices, such as network devices or other terminal devices.

[0100] When the network device and the terminal device communicate, the network device can manage one or more cells, and a cell can contain an integer number of terminal devices. Optionally, the network device 110 and the terminal device 120 form a single-cell communication system, and without loss of generality, the cell is referred to as cell #1. The network device 110 can be a network device in cell #1, or the network device 110 can serve the terminal devices (e.g., terminal device 120) in cell #1.

[0101] In one cell, for example, cell #1, network device 110 can send downlink data to terminal device 120.

[0102] It should be noted that a residential area can be understood as the area within the wireless signal coverage of network devices.

[0103] It should be noted that the network devices in the communication system 200 (e.g., network devices 110a and 110b) can be Figure 1 Network elements in management architecture 100.

[0104] It should be understood that Figure 2 This is a simplified schematic diagram for ease of understanding. The wireless communication system 200 may also include other network devices such as a core network 300 and an Internet 400, or it may include other terminal devices. Figure 2 It is not shown in the figure. The embodiments of this application can be applied to any communication scenario in which the sending end device and the receiving end device communicate.

[0105] To facilitate understanding of the embodiments of this application, the terminology involved in the embodiments of this application will be briefly explained below.

[0106] 1. Small data burst / small data: This refers to application layer service demand that is less than the air interface transmission capacity of the NR cell, and the service packets arrive intermittently. This results in a high probability that the NR cell's radio link control (RLC) buffer contains no application layer data or that the RLC buffer is cleared with only a few transmissions (e.g., 1-3). In essence, a small data burst is a service data transmission with a relatively small amount of data. Typical examples include WeChat chat, short video services, and web browsing. This application's embodiments do not limit this to specific types of services.

[0107] See Figure 3 As an example, Figure 3 This diagram illustrates data transmission under a bursty small packet service. Figure 3 As can be seen, in scenario one, application layer services can clear the data in the RLC buffer after 1-3 transmissions (within 1-3 time slots). In scenario two, some time slots in the RLC buffer do not contain application layer data to be transmitted.

[0108] The above Figure 3 This is merely an example of data transmission under bursty small packet services and does not impose any limitations on the embodiments of this application.

[0109] The aforementioned sudden small package service can also be referred to as small package service, sudden service, small package data, sudden small package data, etc. This application embodiment does not limit the name of this term. In this application, the sudden small package service is used as an example for explanation.

[0110] 2. Large Packet Continuous Download Service: This refers to a situation where the demand for application-layer services far exceeds the air interface transmission capacity of the NR cell, resulting in a continuous accumulation of large amounts of application-layer data in the NR cell's RLC buffer. This service can last for a considerable period of time. It can be understood that the large packet continuous download service involves transmitting large amounts of data. Typical examples include FTP file downloads and downloading large files from cloud storage. This application's embodiments do not limit this to specific types of services.

[0111] See Figure 4 As an example, Figure 4 This diagram illustrates data transmission under a large packet continuous download service. As can be seen from the diagram, a large amount of application layer data is constantly waiting to be transmitted in the RLC buffer of the NR cell, and it takes a considerable amount of time before the data in the RLC buffer can be cleared.

[0112] The above Figure 4 This is merely an example of data transmission in a large-package continuous download service and does not impose any limitations on the embodiments of this application.

[0113] The aforementioned continuous large package download service can also be referred to as large package service, continuous service, large package data, continuous large package data, etc. This application embodiment does not limit the name of this term. In this application, the continuous large package download service is used as an example for explanation.

[0114] 3. Statistical principles for UE throughput on the radio access side: Taking the statistical methods and principles for UE downlink rate on the radio access side as defined in 3GPP TS28.5546.3.6.2 and TS28.552 5.1.1.3.1 as examples. Details are as follows:

[0115] Downlink traffic (ThpVolDl): This counts the amount of RLC layer data successfully transmitted from the NR side to the UE side, excluding the data transmitted during the last slot (defined as the last slot) after clearing the buffer.

[0116] For example, ThpVolDl refers to the RLC layer data volume of a data burst, excluding data transmitted in the time slot where the buffer is cleared. For instance, ThpVolDl refers to the amount of data, measured in kbit, successfully transmitted (and acknowledged by the UE) at the RLC Service Data Unit (SDU) level by a data radio bearer (DRB) in the downlink (DL) during ThpTimeDl. (The amount of data transmitted during the last portion of the data sent when the buffer is cleared should be excluded).

[0117] Among them, a data burst refers to a series of data transmitted continuously in a short period of time, and a "buffer" is an area for temporarily storing data.

[0118] For example, the last slot can also be understood as the time slot in which the data in the buffer is cleared. For example, Figure 2 The time slot in the buffer shown is where the data was successfully transmitted and cleared.

[0119] It should be understood that in this application, the UE's transmission rate (UE throughput) refers to the UE's rate, which can also be called the UE's throughput, UE's throughput rate, UE rate, etc. The embodiments of this application do not limit this.

[0120] See Figure 5 As an example, Figure 5 A schematic diagram of a UE downlink rate statistics method is shown. From Figure 5As can be seen from this, downlink traffic includes the amount of data transmitted in the time slot where all buffered data is successfully transmitted and not cleared, but does not include the amount of data transmitted in the time slot where the buffered data is cleared.

[0121] Downlink service duration (ThpTimeDl): Duration statistics start counting from the first time data in the buffer is transmitted to the UE (denoted as time T2) until the data in the buffer is cleared, excluding the last slot transmission time (denoted as time T1). ThpTimeDl = T1 - T2. Figure 5 As can be seen, the downlink service duration does not include the time occupied by the amount of data transmitted in the time slot when the data in the buffer is cleared.

[0122] For example, ThrpTimeDI refers to the time required to transmit a data burst, excluding the time spent transmitting data while the buffer is being emptied. A sample value of ThrpTimeDI is recorded each time a DRB's DL buffer is emptied.

[0123] UE downlink rate (UE throughput in DL): UE throughput in DL = downlink traffic (ThpVolDl) / downlink duration (ThpTimeDl) (kbits / s).

[0124] For large packet transmission scenarios, the existing protocol describes that the data in the last slot will be continuously deleted and not counted, that is, the ThrpVolDl of the last slot is 0.

[0125] For bursty small packet service scenarios, the existing protocol describes that when all data in the cache is included in an initial hybrid automatic repeat request (HARQ) for transmission, that is, all data in the cache can be transmitted in one slot, the downlink service duration (ThpTimeDl) is 0 and does not contribute to the UE downlink rate statistics sample.

[0126] Commercial networks primarily handle bursty small packet services. The aforementioned method of calculating UE downlink rates results in statistical distortion. For instance, UEs with good radio channel quality are likely to be excluded from NR cell-level UE rate statistics as the last slot when transmitting bursty small packet services (ThpTimeDl is recorded as 0). Conversely, UEs with poor radio channel quality are retained in the statistics when transmitting bursty small packet services (ThpTimeDl is not recorded as 0). This leads to NR cell-level UE rate statistics results being more biased towards reflecting the rate experience of users with poor radio channel quality.

[0127] However, for continuous large packet service scenarios, because a large amount of data is continuously cached in the base station RLC buffer, the amount of cached data in the buffer is always greater than the NR air interface transmission rate, making the probability of the last slot appearing extremely low. In the end, a large number of rate samples of users with good channel quality who have successfully transmitted and whose buffers are not empty are counted in the NR cell-level UE rate statistics.

[0128] For example, when a UE in a cell is performing continuous large packet services, the last slot traffic accounts for less than 1%, and the average downlink UE rate counted by the NR side reaches as high as 1.8Gbps. When a UE in a cell is not performing continuous large packet services, that is, when there are only bursty small packet services, the last slot traffic accounts for more than 85% to 90%, and the downlink user experience rate drops to about 200Mbps.

[0129] In summary, the current protocol's downlink UE rate statistics method suffers from statistical distortion in the context of sudden small packet traffic, and cannot truly reflect the downlink user experience.

[0130] 4. Last slot padding calculation method: 3GPP 28552 5.1.1.3.2 provides another optional calculation method. A duration less than 1 slot is obtained by using (TBVol - PaddingVol) / TBVol * slot, where TBVol refers to the total data volume of the transport block corresponding to the time slot where the buffer data is cleared; PaddingVol refers to the amount of padding data added to the transport block corresponding to the time slot where the buffer data is cleared.

[0131] The above statistical method can compensate for the samples that were originally removed, thus increasing the number of statistical samples.

[0132] The above statistical method has the following problems:

[0133] Question 1: The ThrpTimeDL calculated using this method can only compensate for the last slot sample where the data in the buffer is transmitted in one go. For the last slot sample where the data in the buffer is not transmitted in one go, this calculation method has an error. That is, when all the data in the buffer is not included in an initial HARQ for transmission, that is, when all the data in the buffer is not transmitted in one slot, the downlink service duration (ThpTimeDL) of the last slot is counted as 0, which makes the final UE downlink rate statistics have a large error.

[0134] Question 2: Due to the small number of RBs scheduled in the last slot, even the rate calculated based on padding is low, far lower than the rate under continuous large packet service, and still cannot reflect the UE downlink rate when the data in the buffer is large enough.

[0135] For example, for a UE, the data in the buffer is cleared in two slots. During the first clearing, the amount of data in the buffer is greater than the amount of data to be transmitted over the air interface.

[0136] The first scheduling is 273PDSCH RB, MCS18, Rank=2, corresponding to a scheduled traffic of 24597 bytes, a duration of 1 slot, and a corresponding rate of 24597*8 / 0.5ms=393Mbps.

[0137] The second scheduling (last slot) is 48PDSCH RB MCS18, Rank=2, corresponding TBVol=4352 bytes, Padding data=541 bytes, ThrpTimeDl=(4352-541)*8 / 4352*0.5ms=0.44ms, corresponding rate=(4352-541)*8 / 0.44ms=69.63Mbps.

[0138] As illustrated in the example above, the calculation rate of the Last slot padding method is not high, and there is a significant gap compared to the scheduling rate of the first slot based on a sufficiently large amount of data in the buffer.

[0139] In view of this, the embodiments of this application provide a communication method that, based on the assumption of continuous large packet download service, compensates for the amount of data in the time slot where all cached data is cleared, thereby restoring the true air interface rate capability of the UE under continuous large packet download service, and can more fairly reflect the proportion of sample points with good and poor channel quality under NR cell.

[0140] It should be noted that, in this application, "instruction" can include direct instruction and indirect instruction. When describing a certain instruction information for the purpose of instructing A, it can be understood that the instruction information carries A, directly instructs A, or indirectly instructs A.

[0141] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.

[0142] Furthermore, in this application, the expression " / " is used to indicate that the objects before and after it are in an "or" relationship; for example, A / B can mean: A or B. The expression "and / or" is used to indicate that the objects before and after it can be in a "and" relationship or an "or" relationship; for example, A and / or B can mean the following: A exists alone, B exists alone, A and B exist simultaneously, where A and B can be single or multiple. "At least one of the following" or similar expressions are used to indicate any combination of the listed items; for example, at least one of A, B and / or C can mean the following: A exists alone, B exists alone, C exists alone, A and B exist simultaneously, B and C exist simultaneously, A and C exist simultaneously, A, B and C exist simultaneously, where A, B, and C can be single or multiple.

[0143] The methods provided by the embodiments of this application will be described in detail below with reference to the accompanying drawings. The embodiments provided by this application can be applied to the scenarios shown in the above figures, and are not limited thereto.

[0144] The following details the scheme of this application.

[0145] See Figure 6 As an example, Figure 6 This is a schematic diagram of a communication method 600 provided in an embodiment of this application. This method can be applied to the downlink rate statistics function of the UE in a radio cell on the NR side. For ease of description, the following example uses a first device as the executing entity of method 600. Exemplarily, the first device can be a domain management node (e.g., Figure 1 The domain management functional unit in the architecture 100 can also be a network node (e.g., Figure 1The network element in the architecture 100), the execution entity of method 600 can also be a component of the first device, such as a chip, chip system, or circuit, without limitation. The steps described below as being executed by a single execution entity can also be divided into being executed by multiple execution entities, which can be logically and / or physically separated. Figure 6 The method 600 shown may include the following steps.

[0146] Method 600 includes steps 610 and 620, and optionally, method 600 includes step 630.

[0147] S610, determine the primary service traffic.

[0148] In step S610, the first device determines the first service traffic.

[0149] As an example, the first device is a domain management node (e.g., Figure 1 Domain management functional units in architecture 100) or network nodes (e.g., Figure 1 (Network elements in the 100-level architecture).

[0150] In one possible implementation, a network node (e.g., a base station) can determine the original measurement and report it to a domain management node, which then determines the first service traffic based on the original measurement.

[0151] For example, the original measurement is the first service traffic of a single UE. The domain management node calculates the average value of the first service traffic of UEs within the cell, or the distribution of the first service traffic of UEs within the cell, or calculates the throughput of UEs, the average throughput of UEs within the cell, or the distribution of the throughput of UEs within the cell based on the first service traffic. This application does not limit this.

[0152] As an example, determining the raw measurement quantity can be performed by the base station, specifically, such as by the base station's layer 2 (L2) module, which, for example, includes the RLC and / or media access control (MAC) layer.

[0153] In another possible implementation, network nodes (e.g., base stations) can determine the raw measurement and determine the first service traffic based on the raw measurement.

[0154] For example, the original measurement is the first service traffic of a single UE. The base station calculates the average value of the first service traffic of UEs within the cell, or the distribution of the first service traffic of UEs within the cell, or calculates the throughput of UEs, the average throughput of UEs within the cell, or the distribution of the throughput of UEs within the cell based on the first service traffic. This application does not limit this.

[0155] Optionally, the network node sends the first service traffic to the domain management node.

[0156] The term "first service traffic" can also be referred to as "first service transmission volume," "first service data volume," or "first data traffic," etc. This application does not limit the name of this term in its embodiments.

[0157] The first service traffic is used to indicate the amount of data successfully transmitted in the downlink by a data radio bearer.

[0158] As an example, the amount of data successfully transmitted above is the amount of data counted on the RLC Service Data Unit (SDU) level and acknowledged by the UE.

[0159] One possible implementation is that the first service traffic includes the amount of data transmitted in the time slot where the buffer data is cleared (ThpVolDl_Last_Slot).

[0160] One possible implementation is that the first service traffic also includes the amount of data transmitted in the time slot where the data in the buffer was successfully transmitted without being cleared (ThpVolDl).

[0161] One possible implementation is that the data in the buffer is cleared, which can be understood as the data to be transmitted in the buffer being completely sent out within this time slot.

[0162] One possible implementation is that the data in the buffer is successfully transmitted but not cleared. This can be understood as sending out a portion of the data to be transmitted in the buffer within that time slot, while there is still data to be transmitted that has not been sent.

[0163] One possible implementation is that the first service traffic includes the data volume of the RLC layer in a single data burst, and also includes the data volume transmitted in the time slot where the buffer is cleared. It can also be understood as including the data volume of the RLC layer in the last slot data burst.

[0164] One possible implementation is that the first service traffic includes all data successfully transmitted in the downlink, or in other words, the first service traffic includes the amount of data transmitted within all time slots where data transmission occurred. This can be understood as including time slots where data in the buffer was successfully transmitted and not yet cleared, and time slots where data in the buffer was successfully transmitted and cleared.

[0165] For example, in Figure 5 In the first service traffic, the amount of data transmitted in the time slot where the data in the buffer was successfully transmitted but not cleared, and the amount of data transmitted in the time slot where the data in the buffer was successfully transmitted and cleared.

[0166] In this technical solution, the first service traffic is used to calculate the downlink rate of the UE. This first service traffic includes the amount of data transmitted in the time slot when all data in the buffer is cleared. This amount of data transmitted in the time slot when all data in the buffer is cleared can include the amount of data in the buffer that is transmitted in one go, or it can include the amount of data in the buffer that is not transmitted in one go. This improves the conversion ratio, making the downlink rate result more evenly reflect the rate of users with good channel quality or users with poor channel quality, and avoiding statistical distortion.

[0167] The following describes the statistical method for the amount of data transmitted in the time slot (ThpVolDl_Last_Slot) when the data in the buffer is cleared (hereinafter referred to as the first data volume for ease of description).

[0168] In one possible implementation, the first data volume is statistically represented as the amount of data transmitted in the last time slot when the buffer is cleared. It can be understood that the first data volume is the amount of data transmitted in the last time slot when the buffer is cleared. Alternatively, it can be understood that the first data volume is the amount of data transmitted in the time slot when the data in the buffer is cleared, as statistically represented by the RLC layer. The first data volume can also be understood as the amount of data transmitted in the last time slot, or as the amount of data in the RLC layer that bursts with the data in the last time slot.

[0169] In one possible implementation, the first data volume is the difference between the data volume (TBVol) of the transport block corresponding to the time slot where the data in the buffer is cleared (hereinafter referred to as the second data volume for ease of description) and the data volume (PaddingVol) of the padding bits added to the transport block corresponding to the time slot (hereinafter referred to as the third data volume for ease of description).

[0170] One possible implementation is that the second data volume can be understood as the data volume of the transport block associated with the data burst within that time slot. This can be understood as the data volume of the transport block in the last time slot, or it can be understood as the data volume of the transport block in the last time slot when the MAC layer statistical buffer is cleared, or it can be understood as the data volume of the transport block associated with the data burst in the last time slot, or it can be understood as the size or capacity of the transport block associated with data transmission within a specific time slot.

[0171] In one possible implementation, the third data quantity can be understood as the amount of padding bits added to the transport block associated with the data burst within that time slot. The third data quantity can also be understood as the amount of padding bits added to the last slot, or the amount of padding bits added to the transport block associated with the MAC layer of the last slot's data burst. The second data quantity can also be described as the number of padding bits added to the relevant transport block within a specific time slot to meet transmission requirements. Padding bits refer to the extra bits added during data transmission to meet specific format requirements or ensure the integrity of the data block.

[0172] It can be understood that the second data volume is the actual data volume transmitted in the transmission block within the time slot. The transmission block within the time slot includes padding bits. Therefore, by removing the data volume occupied by the padding bits, the actual data volume transmitted in the transmission block within the time slot can be obtained.

[0173] S620, determine the first service duration.

[0174] In step S620, the first device determines the first service duration. The first device may be a network node (e.g., a base station) or a domain management function node; this application does not limit this.

[0175] In one possible implementation, a network node (e.g., a base station) can determine the original measurement and report it to a domain management node, which then determines the first service duration based on the original measurement.

[0176] For example, the original measurement is the first service duration of a single UE. The domain management node calculates the average first service duration of UEs within the cell, or the distribution of the first service duration of UEs within the cell, or calculates the throughput of UEs, the average throughput of UEs within the cell, or the distribution of the throughput of UEs within the cell based on the first service duration. This application does not limit this.

[0177] As an example, determining the raw measurement quantity can be performed by the base station, specifically, such as by the base station's Layer 2 (L2) module, which, for example, includes RLC and / or MAC.

[0178] In another possible implementation, network nodes (e.g., base stations) can determine the raw measurement and determine the first service duration based on the raw measurement.

[0179] For example, the original measurement is the first service duration of a single UE. The base station calculates the average value of the first service duration of UEs within the cell, or the distribution of the first service duration of UEs within the cell, or calculates the throughput of UEs, the average throughput of UEs within the cell, or the distribution of the throughput of UEs within the cell based on the first service duration. This application does not limit this.

[0180] Optionally, the network node sends the first service duration to the domain management node.

[0181] The term "first service duration" can also be referred to as "first service transmission duration" or "first service traffic duration," etc. This application embodiment does not limit the name of this term.

[0182] The first service duration is used to indicate the duration of transmitting the first service traffic.

[0183] As an example, the duration of the first service traffic mentioned above is the duration occupied by the transmission of data counted on the RLC Service Data Unit (SDU) level and acknowledged by the UE.

[0184] One possible implementation is that the first service duration includes the duration occupied when the data in the buffer is cleared (ThpTimeDl_LastSlot), which can also be understood as the duration occupied when the data sent in the last slot is cleared, or the duration occupied when the data sent in the last slot is sent, or the duration occupied when the data burst in the last slot is sent by the RLC layer.

[0185] One possible implementation is that the first service duration also includes the duration occupied when the data in the buffer is successfully transmitted and not cleared.

[0186] One possible implementation is that the first service duration includes the time required to transmit a data burst in the time slot where the buffer is emptied.

[0187] In one possible implementation, the first service duration includes the time occupied by the transmission of all successfully transmitted data in the downlink; or, in other words, the first service duration includes all time slots in which data transmission occurs during a data burst; or, in other words, the first service duration includes the time occupied by the RLC layer data transmission process of the last slot data burst. It can be understood that time slots in which data transmission occurs include time slots where data in the buffer was successfully transmitted but not yet cleared, and time slots where data in the buffer was successfully transmitted and then cleared.

[0188] For example, in Figure 5 In this context, the first service duration includes the time slot length occupied by the successful transmission of data in the buffer without it being cleared, and the time slot length occupied by the successful transmission of data in the buffer and its clearing.

[0189] The following describes the statistical method for the duration (ThpTimeDl_LastSlot) occupied when the data in the buffer is cleared (for ease of description, it will be referred to as the first duration).

[0190] One possible implementation is that the first duration is determined based on the ratio of the amount of data transmitted in the time slot where the data in the buffer is cleared (ThpVolDl_Last_Slot) (the first data amount) to the amount of data in the transport block scheduled when the buffer reaches saturation (TBVol_FullBuffer) (hereinafter referred to as the fourth data amount for ease of description).

[0191] In one possible implementation, the first duration is calculated as the duration of data transmission in the last time slot when the buffer is cleared. This can be understood as the duration of data transmission in the last time slot after the buffer is cleared, or it can be understood as the duration of data transmission in the time slot when the buffer is cleared, as calculated by the RLC layer. It can also be understood as the duration of data transmission in the last time slot, or it can be understood as the duration of data transmission in the RLC layer that bursts with the data in the last time slot.

[0192] In one possible implementation, the first duration is determined based on the ratio of the first data volume to the fourth data volume counted by the RLC layer or MAC layer.

[0193] In one possible implementation, the first duration is determined based on the ratio of the first data volume to the fourth data volume, wherein the first data volume is the difference between the total data volume (TBVol) of the transport block corresponding to the time slot where the data in the buffer is cleared (the second data volume) and the data volume of the padding bits added to the transport block corresponding to the time slot (the third data volume).

[0194] The specific descriptions of the second and third data volumes can be found in S610 and will not be repeated here.

[0195] The fourth data volume will be introduced below.

[0196] For example, a cache saturation state can be caused by the cache's data capacity reaching its limit, or by a cache overflow, a cache full of data, or a cache that is already full.

[0197] In one possible implementation, the buffer reaching saturation can be understood as the data in the buffer exceeding the wireless air interface transmission capacity. That is to say, the data in the buffer cannot be completely transmitted within the time slot, or the data in the buffer cannot be cleared within the time slot.

[0198] In one possible implementation, the fourth data quantity can be the data quantity of the transmission block that can be scheduled by the largest available RB when the data in the buffer is greater than the wireless air interface transmission capacity. It can be understood that the fourth data quantity is the data quantity of the transmission block of the last time slot data burst when the last time slot data burst is in a full buffer.

[0199] As an example, the amount of data in the transport block that can be scheduled by the maximum available RB when the data in the buffer is greater than the radio air interface transmission capacity refers to the TBS result of the NR radio cell L2 module according to the maximum available PDSCH RB, assuming that the data in the current slot's buffer is large enough, that is, the data in the buffer is greater than the NR air interface transmission capacity; or, within this buffer, the TBS is scheduled according to the maximum available PDSCH RB of the NR radio cell L2 module under the large packet continuous download service.

[0200] For example, if the current maximum number of RBs in the BWP bandwidth is 273, of which 16 RBs have already been scheduled and used, then the current maximum number of RBs available for scheduling is 257.

[0201] As an example, the number of TBs to be scheduled can be determined based on the maximum number of RBs currently available in the current schedule, as defined in the current protocol 38214.(5.1.3.2).

[0202] It is understandable that when the data in the buffer exceeds the NR air interface transmission capacity, the estimated number of TBs scheduled by the NR cell L2 module is much greater than the number of TBs scheduled under small packet services, which can relatively accurately reflect the user's downlink transmission situation.

[0203] For example, for a UE, the data in the buffer is cleared in two slots. During the first clearing, the amount of data in the buffer is greater than the amount of data to be transmitted over the air interface.

[0204] The first scheduling is 273PDSCH RB, MCS18, Rank=2, corresponding to a scheduled traffic of 24597 bytes, a duration of 1 slot, and a corresponding rate of 24597*8 / 0.5ms=393Mbps.

[0205] The second scheduling (last slot) uses 48 PDSCH RBs, MCS18, Rank=2, with a corresponding TBVol=4352 bytes and PaddingVol=541 bytes. Assuming the data in the buffer is infinitely large, the NR radio cell L2 module recalculates the TBS result based on the maximum available PDSCH RB in the current slot (273 RBs), resulting in TBsize=24597, or TBVol_fullbuffer=24597.

[0206] ThpTimeDl_LastSlot=(4352bytes-541bytes) / 24597bytes*1slot=0.077ms

[0207] The corresponding rate is (4352 bytes - 541 bytes) * 8 / 0.077 ms = 396 Mbps.

[0208] As can be seen from the above examples, the rate corresponding to the second scheduling is close to the rate corresponding to the first scheduling, so the downlink rate on the UE side can be predicted more accurately.

[0209] In this technical solution, a compensation calculation is performed based on the assumption that the data in the buffer is much larger than the NR air interface transmission capacity, so that the calculated UE rate result is more consistent with the actual rate capacity of the UE.

[0210] S630, determine the statistical results of the air interface transmission rate of the terminal device based on the first service traffic and the first service duration.

[0211] For example, the statistical results of the air interface transmission rate of the terminal device include at least one of the following: downlink rate of one or more terminal devices (UE Throughput in DL), distribution of downlink user rate of multiple terminal devices (Distribution of DLUE throughput in gNB), and average downlink user rate of multiple terminal devices (Average DL UE throughput in gNB).

[0212] In one possible implementation, the first device determines the downlink rate (UE Throughput in DL) of one or more terminal devices based on the first service traffic and the first service duration.

[0213] In one possible implementation, the first device determines the downlink rate of one or more terminal devices based on the ratio of the first service traffic to the first service duration.

[0214] In one possible implementation, the downlink rate of the terminal device is related to the amount of data transmitted in the time slot when the data in the buffer is successfully transmitted and not cleared, the amount of data transmitted in the time slot when the data in the buffer is cleared, the duration occupied when the data in the buffer is successfully transmitted and not cleared, and the duration occupied when the data in the buffer is cleared.

[0215] For example, the downlink rate of each terminal device satisfies:

[0216] UE Throughput in DL=(ThpVolDl+ThpVolDl_Last_Slot) / (ThpTimeDl+ThpTimeDl_LastSlot),

[0217] Wherein, UE Throughput in DL represents the downlink rate of the aforementioned terminal device, ThpVolDl represents the amount of data transmitted in the time slot when the data in the buffer was successfully transmitted and not cleared, ThpVolDl_Last_Slot represents the amount of data transmitted in the time slot when the data in the buffer was cleared, ThpTimeDl represents the duration occupied when the data in the buffer was successfully transmitted and not cleared, and ThpTimeDl_LastSlot represents the duration occupied when the data in the buffer was cleared.

[0218] For example, the downlink rate of the aforementioned terminal device = (ThpVolDl + ThpVolDl_Last_Slot) / (ThpTimeDl + ThpTimeDl_LastSlot) = (24597 bytes + 4352 bytes - 541 bytes) * 8 / (0.5 ms + 0.077 ms) = 394 Mbps.

[0219] In another possible implementation, the first device determines the downlink rate distribution (downlink user rate distribution) and / or the average downlink rate (average downlink user rate) of multiple terminal devices based on the first service traffic and the first service duration.

[0220] As an example, a network node (e.g., a base station) determines the downlink user rate distribution and / or average downlink user rate based on a first service traffic and a first service duration.

[0221] As an example, the domain management node determines the downlink user rate distribution and / or average downlink user rate based on the first service traffic and the first service duration.

[0222] For example, the downlink user rate distribution or average downlink user rate statistics can be determined by the following formula:

[0223]

[0224] If∑UEs∑ThpTimeDl+ThpTimeDL_LastSlot>0;

[0225] Distribution of DL UE throughput in gNB / Average DL UE throughput ingNB=0[kbit / s],

[0226] If∑UEs∑ThpTimeDl+ThpTimeDL_LastSlot=0.

[0227] Wherein, ∑UEs∑ThpVolDl+ThpVolDL_LastSlot represents the sum of the amount of data transmitted in the time slot when the data in the buffers of all terminal devices in the cell was successfully transmitted and not cleared, and the amount of data transmitted in the time slot when the data in the buffers was cleared. ∑UEs∑ThpTimeDl+ThpTimeDL_LastSlot represents the sum of the duration occupied when the data in the buffers of all terminal devices in the cell was successfully transmitted and not cleared, and the duration occupied when the data in the buffers was cleared.

[0228] Optionally, the method further includes step S640, whereby the first device reports the statistical results of the air interface transmission rate of the terminal device.

[0229] S640, the first device reports the statistical results of the air interface transmission rate of the terminal equipment to the cross-domain management node.

[0230] For example, the statistical results of the downlink rate of the terminal device include at least one of the following: downlink rate of one or more terminal devices (UE Throughput in DL), distribution of downlink user rate of multiple terminal devices (Distribution of DL UEthroughput in gNB), and average downlink user rate of multiple terminal devices (Average DL UEthroughput in gNB).

[0231] For example, a network node can report the statistical results of the air interface transmission rate of the terminal device to the cross-domain management node through the domain management node.

[0232] For example, a domain management node reports the statistical results of the air interface transmission rate of the terminal device to a cross-domain management node.

[0233] For example, a cross-domain management node is a cross-domain management functional unit.

[0234] Optionally, the cross-domain management node can manage and control network elements based on the statistical results of the air interface transmission rate of the terminal devices, so as to allocate and schedule resources, achieve more efficient resource utilization and allocation, and improve service quality.

[0235] Based on the above technical solution, by compensating for the amount of data in the time slot where all cached data is cleared, the downlink rate results more evenly reflect the rates of users with good or poor channel quality, avoiding statistical distortion. Furthermore, the compensation is performed based on the assumption that the data in the buffer is much larger than the NR air interface transmission capacity, making the compensated UE rate results more consistent with the actual rate capability of the UE. Additionally, compensating for the amount of data in the time slot where all cached data is cleared increases the compensation ratio, thereby improving the accuracy of the UE downlink rate statistics.

[0236] It should be noted that the English terms defined in this application are merely examples. For instance, ThpVolDl_Last_Slot represents the amount of data transmitted in the time slot when the data in the buffer is cleared, and ThpTimeDl_LastSlot represents the duration occupied when the data in the buffer is cleared. These English terms do not impose any limitations on the embodiments of this application.

[0237] It is understood that some optional features in the various embodiments of this application may not depend on other features in some scenarios, or may be combined with other features in some scenarios, without limitation.

[0238] It is also understood that the solutions in the various embodiments of this application can be used in reasonable combinations, and the explanations or descriptions of the various terms appearing in the embodiments can be referenced or explained to each other in the various embodiments, without limitation.

[0239] It is also understood that, in the above-described method embodiments, the methods and operations implemented by the terminal device can also be implemented by the components of the terminal device (e.g., chips or circuits); in addition, the methods and operations implemented by the network device can also be implemented by the components of the network device (e.g., chips or circuits), without limitation.

[0240] The above, combined with Figure 6 The methods provided in the embodiments of this application are described in detail below. Figures 7 to 8 The apparatus provided in the embodiments of this application is described in detail. It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments. Therefore, for content not described in detail, please refer to the method embodiments above. For the sake of brevity, it will not be repeated here.

[0241] See Figure 7 As an example, Figure 7 This is a schematic diagram of a communication device 700 provided in an embodiment of this application.

[0242] The device 700 includes a transceiver unit 710 and a processing unit 720. The transceiver unit 710 can be used to implement corresponding communication functions, and the processing unit 720 can be used to perform data processing.

[0243] Optionally, the transceiver unit 710 may also be referred to as a communication interface or communication unit, including a transmitting unit and / or a receiving unit. The transceiver unit 710 may be a transceiver (including a transmitter and / or receiver), an input / output interface (including input and / or output interfaces), pins, or circuitry, etc. The transceiver unit 710 can be used to perform the transmitting and / or receiving steps in the above method embodiments.

[0244] Optionally, the processing unit 720 may be a processor (which may include one or more), a processing circuit with processor functions, etc., and may be used to perform other steps in the above method embodiments besides sending and receiving.

[0245] Optionally, the device 700 further includes a storage unit, which may be a memory, an internal storage unit (e.g., a register, a cache, etc.), or an external storage unit (e.g., a read-only memory, a random access memory, etc.). The storage unit is used to store instructions, and the processing unit 720 executes the instructions stored in the storage unit to cause the communication device to perform the aforementioned method.

[0246] In a first possible design, the device 700 can be used to perform the actions performed by the first device in the above method embodiment, such as the device 1000 being used to perform the actions performed by the first device in the above method 600. In this case, the device 700 can be a component of the first device, with the transceiver unit 710 performing transceiver-related operations on the first device side of the above method embodiment, and the processing unit 720 performing processing-related operations of the first device in the above method embodiment.

[0247] In one possible implementation, processing unit 720 is configured to determine a first service traffic, which indicates the amount of data successfully transmitted in the downlink by a data radio bearer, and the first service traffic includes the amount of data transmitted in the time slot when the data in the buffer is cleared; processing unit 720 is further configured to determine a first service duration, which indicates the duration of transmitting the first service traffic, and the first service duration includes the duration occupied when the data in the buffer is cleared; the first service traffic and the first service duration are used to determine the downlink rate of the terminal device.

[0248] In one possible implementation, the processing unit 720 is further configured to determine the downlink rate of the terminal device based on the first service traffic and the first service duration.

[0249] In one possible implementation, the processing unit 720 is further configured to determine downlink user rate distribution statistics and / or average downlink user rate statistics based on the first service traffic and the first service duration.

[0250] One possible implementation is that the transceiver unit 710 is used to transmit at least one of the downlink rate of the terminal device, downlink user rate distribution statistics, and average downlink user rate.

[0251] It should be understood that the transceiver unit 710 and the processing unit 720 can also perform other operations performed by the first device in the above method 600, which will not be described in detail here.

[0252] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0253] It should also be understood that the device 700 here is embodied in the form of a functional unit. The term "unit" here can refer to an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, integrated logic circuitry, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that the device 700 can specifically be the communication device in the above embodiments, and can be used to execute the various processes and / or steps corresponding to the communication device in the above method embodiments; to avoid repetition, these will not be described again here.

[0254] The apparatus 700 of each of the above-described schemes has the function of implementing the corresponding steps performed by the communication device (such as a transmitting device or a receiving device) in the above-described methods. The function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (e.g., the transmitting unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as processing units, can be replaced by processors, each executing the transceiver operations and related processing operations in the respective method embodiments.

[0255] In addition, the transceiver unit 710 described above can also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit can be a processing circuit.

[0256] It should be pointed out that, Figure 7 The device mentioned can be the communication equipment (such as a terminal device or a network device) in the foregoing embodiments, or it can be a chip or a chip system, such as a system on a chip (SoC). The transceiver unit can be an input / output circuit or a communication interface; the processing unit is a processor, microprocessor, or integrated circuit integrated on the chip. No limitations are imposed here.

[0257] See Figure 8 As an example, Figure 8 This is a schematic diagram of a communication device 800 provided in an embodiment of this application. Figure 8 The communication device 800 shown includes a processor 810 and a transceiver 820. Optionally, the processor 810 and the transceiver 820 can be interconnected via a bus 830. The communication device 800 can be a terminal device or a network device.

[0258] Optionally, the communication device 800 may also include a memory 840. The memory 840 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), which is used to store related instructions and data.

[0259] The processor 810 is coupled to the memory 840 and is used to execute instructions stored in the memory 840 to control the transceiver 820 to send and / or receive signals.

[0260] It should be understood that the processor 810 and memory 840 can be combined into a single processing device, with the processor 810 executing the program code stored in the memory 840 to achieve the aforementioned functions. In specific implementations, the memory 840 can be integrated into the processor 810 or independent of it. It should also be understood that the processor 810 can correspond to the various processing units in the aforementioned communication device, and the transceiver 820 can correspond to the various receiving and transmitting units in the aforementioned communication device.

[0261] It should also be understood that transceiver 820 may include a receiver (or receiver unit) and a transmitter (or transmitter unit). The transceiver may further include antennas, and the number of antennas may be one or more. The transceiver may also be a communication interface or interface circuitry.

[0262] Specifically, the communication device 800 may correspond to the first device in the method 600 according to the embodiments of this application. The communication device 800 may include units of the method executed by the first device in method 600. It should be understood that the specific processes by which each unit performs the corresponding steps described above have been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0263] When the communication device 800 is a chip, the chip includes an interface unit and a processing unit. The interface unit can be an input / output circuit or a communication interface; the processing unit can be a processor, microprocessor, or integrated circuit integrated on the chip.

[0264] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0265] It should be noted that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by the integrated logic circuitry in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above methods.

[0266] This application also provides a computer-readable medium having a computer program stored thereon, which, when executed by a computer, implements the functions of any of the above method embodiments.

[0267] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

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

[0269] In the embodiments of this application, the words "exemplary," "for example," etc., are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design that is described as "exemplary" in this application should not be construed as being more preferred or advantageous than other embodiments or design options. Specifically, the use of the term "exemplary" is intended to present the concept in a concrete manner.

[0270] It should be understood that the term "embodiment" used throughout this specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout this specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.

[0271] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. All node and message names in this application are merely names set for the convenience of description, and the names in the actual network may be different. It should not be understood that this application limits the names of various nodes and messages. On the contrary, any name with the same or similar function as the node or message used in this application is regarded as the method or equivalent substitution of this application and is within the protection scope of this application.

[0272] It should also be understood that in this application, “when…”, “if” and “if” all refer to the UE or base station taking corresponding actions under certain objective circumstances, and are not time-limited, nor do they require the UE or base station to perform a judgment action, nor do they imply any other limitations.

[0273] Furthermore, the terms "system" and "network" are often used interchangeably in this paper. The term "and / or" in this paper is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A exists alone, A and B exist simultaneously, and B exists alone.

[0274] In this document, the terms "at least one of..." or "at least one of..." refer to all or any combination of the listed items. For example, "at least one of A, B, and C" can represent six possibilities: A exists alone, B exists alone, C exists alone, A and B exist simultaneously, B and C exist simultaneously, and A, B, and C exist simultaneously. "At least one" in this document means one or more. "More than one" means two or more.

[0275] It should be understood that in the embodiments of this application, the terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0276] It should be understood that in the various embodiments of this application, the terms "first," "second," and various numerical designations are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. For example, they can be used to distinguish different information.

[0277] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0278] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0279] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0280] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0281] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0282] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0283] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: Determine the first service traffic, which is used to indicate the amount of data successfully transmitted in the downlink of a data radio bearer, and the first service traffic includes the amount of data transmitted in the time slot when the data in the buffer is cleared; A first service duration is determined, which is used to indicate the duration of transmitting the first service traffic. The first service duration includes the duration occupied when the data in the buffer is cleared. The first service traffic and the first service duration are used to determine the downlink rate of one or more terminal devices.

2. The method according to claim 1, characterized in that, The duration occupied when the data in the buffer is cleared is determined by the ratio of the amount of data transmitted in the time slot when the data in the buffer is cleared to the amount of data in the transmission block scheduled when the buffer reaches saturation.

3. The method according to claim 1 or 2, characterized in that, The amount of data transmitted in the time slot when the data in the cache area is cleared is counted by layer 2.

4. The method according to claim 1 or 2, characterized in that, The amount of data transmitted in the time slot where the data in the buffer is cleared is the first data amount. The first data amount is the difference between the total data amount of the transmission block corresponding to the time slot where the data in the buffer is cleared and the amount of data added to the padding bits in the transmission block corresponding to the time slot.

5. The method according to any one of claims 1-4, characterized in that, The first service traffic also includes the amount of data transmitted in the time slot when the data in the buffer is successfully transmitted and has not been cleared.

6. The method according to any one of claims 1-4, characterized in that, The first service duration also includes the time occupied when the data in the buffer is successfully transmitted and not cleared.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: The downlink rate of the one or more terminal devices is determined based on the first service traffic and the first service duration.

8. The method according to claim 7, characterized in that, The downlink rate of each of the one or more terminal devices satisfies: UE Throughput in DL=(ThpVolDl+ThpVolDl_Last_Slot) / (ThpTimeDl+ThpTimeDL_LastSlot), Wherein, UE Throughput in DL represents the downlink rate of the terminal device, ThpVolDl represents the amount of data transmitted in the time slot when the data in the buffer is successfully transmitted and not cleared, ThpVolDl_Last_Slot represents the amount of data transmitted in the time slot when the data in the buffer is cleared, ThpTimeDl represents the duration occupied when the data in the buffer is successfully transmitted and not cleared, and ThpTimeDL_LastSlot represents the duration occupied when the data in the buffer is cleared.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: Based on the first service traffic and the first service duration, determine the downlink rate distribution statistics and / or average downlink rate statistics of the multiple terminal devices.

10. A communication device, characterized in that, Includes modules or units for performing the method according to any one of claims 1 to 9.

11. A communication device, characterized in that, Includes a processor for performing the method of any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed on a communication device, cause the communication device to perform the method as described in any one of claims 1 to 9.

13. A computer program product, characterized in that, The computer program product includes a computer program or instructions for performing the method as described in any one of claims 1 to 9.

Images