Buffer status report reporting method and communication device

Abstract

The invention provides a buffer status report reporting method and a communication device. The method comprises the following steps: acquiring a scaling parameter; and reporting a BSR based on the scaling parameter, the BSR indicating a cache state corresponding to a logical channel group (LCG), the cache state corresponding to the LCG being obtained based on the scaling parameter and a first cache state, the first cache state being predefined or configured by the network device. Based on the method provided by the invention, the cache state can be flexibly scaled based on the scaling parameter to meet different service requirements, so that the reporting of the cache state is more accurate, and the waste of transmission resources is reduced.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a cache status report reporting method and a communication device. Background Art

[0002] During the uplink transmission process, when the terminal has uplink data to transmit, the terminal needs to request the base station to perform uplink resource scheduling through an uplink scheduling request (SR), and report the amount of buffered data on the logical channel group (LCG) through a buffer state report (BSR), so that the base station can allocate sufficient uplink resources to the LCG for uplink data transmission.

[0003] The specific process of the terminal reporting the amount of buffered data on the LCG with the help of the BSR can be understood as: determining the buffer state where the amount of buffered data on the LCG is located from multiple buffer states (BS), and reporting the index value corresponding to the buffer state. The base station will allocate uplink transmission resources to the terminal according to the maximum value of the buffer state corresponding to the index value.

[0004] Usually, BSR has a bit length limit, and the number of cache states that can be divided is limited. As service requirements become more flexible, the reporting of cache states is not accurate and may be greater than the amount of cached data, resulting in a waste of transmission resources. Summary of the invention

[0005] The present application provides a cache status report reporting method and a communication device, which are conducive to making the reporting of the cache status more accurate, thereby reducing the waste of transmission resources.

[0006] In a first aspect, the present application provides a method for reporting a cache status report, which can be executed by a terminal, or by a module (such as a processor, a chip, or a chip system, etc.) applied to the terminal, or by a logical node, a logical module, or software that can implement all or part of the terminal functions. In the method for reporting a cache status report, a scaling parameter is obtained; a BSR is reported based on the scaling parameter, the BSR indicates a cache status corresponding to a logical channel group LCG, and the cache status corresponding to the LCG is obtained based on the scaling parameter and a first cache status, the first cache status is predefined or the first cache status is configured by a network device.

[0007] Based on the method described in the first aspect, the cache status can be flexibly scaled based on the scaling parameters to meet different business requirements, making the reporting of the cache status more accurate, thereby reducing the waste of transmission resources.

[0008] In a possible embodiment, a specific implementation method of acquiring the scaling parameter is: receiving first configuration information from a network device, where the first configuration information is used to configure the scaling parameter.

[0009] Based on this possible embodiment, the scaling parameters can be flexibly configured by the network device.

[0010] In a possible embodiment, the first configuration information is also used to configure BSR reporting.

[0011] In a possible embodiment, indication information may also be sent to the network device, where the indication information indicates the scaling parameter.

[0012] Based on this possible embodiment, the scaling parameter may be flexibly determined by the terminal.

[0013] Optionally, a specific implementation of obtaining the scaling parameter is: determining the scaling parameter. After determining the scaling parameter, the indication information may be sent to the network device.

[0014] Optionally, the scaling parameters may be determined based on transmission parameters of the service.

[0015] Based on this optional approach, the cache state can be made to better match the actual transmission parameters of the service, and the reporting of the cache state can be made more accurate, thereby reducing the waste of transmission resources.

[0016] Optionally, the transmission parameters of the service may include one or more of the following: a transmission rate of the service, a frame rate of the service, or a size of a video frame of the service.

[0017] In a possible embodiment, the BSR and the indication information are located in the same medium access control MAC control element CE.

[0018] Based on this possible embodiment, it is helpful to save signaling overhead and obtain the scaled cache status in time.

[0019] In a possible embodiment, the BSR is located in a first media access control MAC control element CE, and the indication information is located in a second MAC CE.

[0020] Based on this possible embodiment, it is helpful to avoid the terminal sending MAC CE too frequently to report the BSR.

[0021] In a possible embodiment, second configuration information may also be received from the network device, where the second configuration information is used to configure a reporting period of the second MAC CE.

[0022] Based on this possible embodiment, the reporting period of the second MAC CE can be made more flexible.

[0023] In a second aspect, the present application provides a cache status reporting method, which can be executed by a network device, or by a module (such as a processor, chip, or chip system, etc.) applied to the network device, or by a logical node, logical module, or software that can implement all or part of the network device functions. In the cache status reporting method,

[0024] A BSR is received from a terminal, where the BSR indicates a cache state corresponding to a logical channel group LCG, where the cache state corresponding to the LCG is obtained based on a scaling parameter and a first cache state, where the first cache state is predefined or configured by a network device.

[0025] In a possible embodiment, first configuration information may also be sent to the terminal, where the first configuration information is used to configure the scaling parameter.

[0026] Optionally, a scaling parameter may be determined. After the scaling parameter is determined, first configuration information is sent to the terminal, where the first configuration information is used to configure the scaling parameter.

[0027] Optionally, the scaling parameters may be determined based on transmission parameters of the service.

[0028] Optionally, the transmission parameters of the service may include one or more of the following: a transmission rate of the service, a frame rate of the service, or a size of a video frame of the service.

[0029] In a possible embodiment, the first configuration information is also used to configure BSR reporting.

[0030] In a possible embodiment, indication information from the terminal may also be received, where the indication information indicates the scaling parameter.

[0031] In a possible embodiment, the BSR and the indication information are located in the same medium access control MAC control element CE.

[0032] In a possible embodiment, the BSR is located in a first media access control MAC control element CE, and the indication information is located in a second MAC CE.

[0033] In a possible embodiment, second configuration information may also be sent to the terminal, where the second configuration information is used to configure a reporting period of the second MAC CE.

[0034] The beneficial effects of the second aspect can refer to the beneficial effects of the first aspect, which will not be repeated here.

[0035] In a third aspect, the present application provides a communication device, for example, the communication device may be a terminal or a module applied to a terminal, such as a processor, a chip, or a chip system, and may also be a logical node, a logical module, or software that can implement all or part of the terminal functions. The communication device includes a module / unit for executing any method in the first aspect and its possible implementations.

[0036] In a fourth aspect, the present application provides a communication device, for example, the communication device may be a network device or a module applied to a network device, such as a processor, a chip, or a chip system, and may also be a logical node, a logical module, or software that can implement all or part of the functions of the network device. The communication device includes a module / unit for executing any method in the second aspect and its possible implementations.

[0037] In a fifth aspect, the present application provides a communication device, comprising a processor, wherein the processor is coupled to a memory, and the memory is used to store programs or instructions. When the program or instructions are executed by the processor, the device executes the method described in the first or second aspect above.

[0038] In a sixth aspect, the present application provides a chip, comprising a processor and an interface, wherein the processor and the interface are coupled; the interface is used to receive or output signals, and the processor is used to execute code instructions, so that the chip executes the method described in the first or second aspect above.

[0039] In a seventh aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are called, the method described in the first aspect is executed, or the method described in the second aspect is executed.

[0040] In an eighth aspect, the present application provides a computer program product, comprising: a computer program code, wherein when the computer program code is executed, the method described in the first aspect is executed, or the method described in the second aspect is executed.

[0041] In a ninth aspect, the present application provides a communication system, which includes a communication device (such as a terminal) for executing the method described in the first aspect and a communication device (such as a network device) for executing the method described in the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 A possible, non-limiting system schematic diagram provided for this application;

[0043] Figure 2 A schematic diagram of a short BSR format BSR provided in this application;

[0044] Figure 3 A schematic diagram of a long BSR format BSR provided for this application;

[0045] Figure 4-Figure 6 A flowchart of the cache status report reporting method provided by this application;

[0046] Figure 7 A schematic diagram of another short BSR format BSR provided for this application;

[0047] Figure 8 A schematic diagram of another long BSR format BSR provided for this application;

[0048] Fig. 9 A schematic diagram of another long BSR format BSR provided by this application;

[0049] Fig.10 and Fig.11 A schematic diagram of the structure of the communication device provided in this application. DETAILED DESCRIPTION

[0050] The specific embodiments of the present application are further described in detail below in conjunction with the accompanying drawings.

[0051] The terms "first" and "second" and the like in the specification, claims and drawings of this application are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products or devices.

[0052] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0053] In the present application, "at least one (item)" means one or more, "more than one" means two or more, "at least two (items)" means two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0054] In this application, "sending information" can be understood as one device sending information to another device, or it can also be understood as a logic module inside a device sending information to another logic module. For example, "an access network device sending information" can be understood as an access network device sending information to another device (such as a terminal), or it can be understood as logic module 1 in an access network device sending information to logic module 2 in an access network device.

[0055] In this application, "receiving information" can be understood as a device receiving information from another device, or it can also be understood as a logic module inside a device receiving information from another logic module. For example, "the access network device receives information" can be understood as the access network device receiving information from another device (such as a terminal), or it can be understood as logic module 1 in the access network device receiving information from logic module 2 in the access network device.

[0056] In this application, "sending information to... (for example, a terminal)" or the related illustrations in the accompanying drawings can be understood as the destination end of the information is the terminal. It can include sending information to the terminal directly or indirectly. "Receiving information from... (for example, a terminal)" or "receiving information from... (for example, a terminal)" or "receiving information sent by (for example, a terminal)", or the related illustrations in the accompanying drawings can be understood as the source end of the information is the terminal, which can include directly or indirectly receiving information from the terminal. The information may be processed as necessary between the source end and the destination end of the information transmission, such as format changes, etc., but the destination end can understand the valid information from the source end. Similar expressions in this application can be understood similarly and will not be repeated here.

[0057] In order to better understand the embodiments of the present application, the system architecture involved in the embodiments of the present application is first introduced below:

[0058] The embodiments of the present application can be applied to long term evolution (LTE) systems, fifth generation mobile communication (5G) systems, sixth generation mobile communication (6G) systems and other communication systems evolved after 5G, satellite communication and short-range wireless communication systems. Among them, the wireless communication systems mentioned in the embodiments of the present application include but are not limited to: three major application scenarios of 5G / 6G mobile communication systems: enhanced mobile broadband (eMBB), ultra reliable low latency communication (URLLC) and massive machine type communication (mMTC), long range Internet of Things (LoRa) systems or vehicle networking systems. The wireless communication system may include one or more access network devices, and one or more terminal devices.

[0059] Figure 1 A possible, non-limiting system schematic is shown. Figure 1 As shown, the communication system 10 includes a radio access network (RAN) 100, a core network (CN) 200 and the Internet 300. The RAN 100 includes at least one RAN node (e.g. Figure 1 110a and 110b, collectively referred to as 110) and at least one terminal (such as Figure 1 RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment ( Figure 1 The terminal 120 is connected to the RAN node 110 in a wireless manner. The RAN node 110 is connected to the core network 200 in a wireless or wired manner. The core network device in the core network 200 and the RAN node 110 in the RAN 100 may be different physical devices, or may be the same physical device that integrates the core network logical function and the radio access network logical function.

[0060] RAN 100 may be a cellular system related to the third generation partnership project (3GPP), for example, a 4G, 5G mobile communication system, or a future evolution system (for example, a 6G mobile communication system). RAN 100 may also be an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (cloud radio access network, CRAN), or a wireless fidelity (wireless fidelity, WiFi) system. RAN 100 may also be a communication system that integrates two or more of the above systems.

[0061] 1. RAN node 110

[0062] The RAN node 110, which may also be sometimes referred to as an access network device, a RAN entity or an access node or a network device, etc., constitutes a part of the communication system to help the terminal achieve wireless access. The multiple RAN nodes 110 in the communication system 10 may be nodes of the same type or nodes of different types. In some scenarios, the roles of the RAN node 110 and the terminal 120 are relative, for example, Figure 1 The network element 120i may be a helicopter or a drone, which may be configured as a mobile base station. For the terminals 120j that access the RAN 100 through the network element 120i, the network element 120i is a base station; but for the base station 110a, the network element 120i is a terminal. The RAN node 110 and the terminal 120 are sometimes referred to as communication devices, for example Figure 1 The network elements 110a and 110b may be understood as communication devices having base station functions, and the network elements 120a-120j may be understood as communication devices having terminal functions.

[0063] In a possible scenario, the RAN node 110 may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), a next generation base station in a sixth generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. The RAN node 110 may be a macro base station (e.g., Figure 1 110a in), micro base stations or indoor stations (such as Figure 1110b in the present application), a relay node or a donor node, or a wireless controller in a CRAN scenario. In a possible embodiment, the RAN node 110 may also be a server, a wearable device, a vehicle or an on-board device, etc. For example, the access network device in the vehicle to everything (V2X) technology may be a road side unit (RSU). All or part of the functions of the RAN node 110 in the present application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform). The RAN node 110 in the present application may also be a logical node, a logical module or software that can implement all or part of the functions of the RAN node 110.

[0064] In another possible scenario, multiple RAN nodes 110 collaborate to assist the terminal in achieving wireless access, and different RAN nodes 110 respectively implement part of the functions of the base station. For example, the RAN node 110 can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or can also be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU) or a remote radio head (RRH).

[0065] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, CU, CU-CP, CU-UP, DU and RU are described as examples in this application. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0066] In the embodiment of the present application, the form of the RAN node 110 is not limited. The device for implementing the function of the RAN node 110 may be the RAN node 110; or it may be a device capable of supporting the RAN node 110 to implement the function, such as a chip system. The device may be installed in the RAN node 110 or used in conjunction with the RAN node 110.

[0067] For the convenience of description, the RAN node 110 will be referred to as a network device for description below.

[0068] 2. Terminal

[0069] Terminals can also be called terminal devices, user equipment (UE), mobile stations, mobile terminals, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. Terminals can be mobile phones, tablet computers, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc.

[0070] In the embodiments of the present application, the form of the terminal is not limited, and the device for implementing the function of the terminal can be a terminal; or it can be a device that can support the terminal to implement the function, such as a chip system. The device can be installed in the terminal or used in conjunction with the terminal.

[0071] In order to facilitate the understanding of the content of this solution, some of the terms involved in the embodiments of this application are explained below to facilitate understanding by those skilled in the art. This part is only for ease of understanding and cannot be regarded as a disclosure or specific limitation of the technical solution of this application.

[0072] In order to facilitate the understanding of the technical solution of this scheme, some of the terms involved in this application are explained below.

[0073] 1. Extended reality (XR)

[0074] XR refers to the combination of reality and virtuality through computers to create a virtual environment for human-computer interaction. XR includes VR and AR. XR services usually have low packet loss rate and low latency transmission requirements.

[0075] 2. Active timeout packet loss mechanism

[0076] Since XR services have low-latency transmission requirements, the video frames of XR services need to be transmitted from the server to the terminal (or from the terminal to the server) within a certain period of time (i.e., the latency budget). Taking the transmission of uplink data from the terminal to the server as an example, if congestion occurs during air interface transmission, when the waiting time of the video frames of the XR service in the terminal's buffer exceeds the latency budget, the terminal will discard the timed-out XR video frames, thereby saving transmission resources and ensuring the successful transmission of subsequent video frames.

[0077] 3. Cache status report

[0078] If the terminal has no uplink data to upload, but the network device allocates uplink transmission resources to the terminal, it will cause a waste of transmission resources. In order to avoid this waste of transmission resources, the long term evolution (LTE) technology and the new radio (NR) technology provide an SR mechanism. In the SR mechanism, the terminal sends an SR to the network device, which is used to notify the terminal that uplink transmission resources are needed to transmit uplink data; the terminal reports a BSR to the network device, which is used to indicate the amount of uplink data to be transmitted by the terminal; further, the network device configures uplink transmission resources for the terminal according to the BSR.

[0079] In LTE and NR systems, terminals usually report BSR to network devices with LCG as the reporting granularity of BSR. The division of LCG usually depends on the algorithm implementation of the network device. For example, the network device can divide logical channels with the same QoS requirements into the same LCG, or divide logical channels with the same priority into the same LCG. Since the configuration of the terminal's LCG and logical channels is controlled by the network device, the network device knows which logical channels each LCG contains and the priorities of these logical channels. Although the network device cannot know the cache status of a single logical channel, since the logical channels in the same LCG have similar QoS / priority requirements, reporting the cache status based on LCG can also enable uplink scheduling to provide appropriate scheduling results. Taking the NR system as an example, the following schematic illustration of the terminal reporting BSR to the network device is given.

[0080] In the NR system, the BSR is reported through the BSR MAC control element (CE) of the MAC layer. The reported BSR includes two formats: short BSR (also known as short BSR) format and long BSR (also known as long BSR) format.

[0081] 3.1、short BSR

[0082] Short BSR is also called truncated BSR. In short BSR, only the cache status of one LCG is reported. The schematic diagram of the short BSR format can be found in Figure 2 As shown, in Figure 2 The short BSR format consists of an LCG ID field and a buffer size field. In the short BSR format, 5 bits are used to indicate the value of the buffer status (that is, 5 bits are used to report the index value of the buffer status, and there are 32 buffer statuses in the short BSR format). The corresponding relationship between the index value of the buffer status of the short BSR and the value of the buffer status is shown in Table 1.

[0083] Table 1

[0084] Index BS value Index BS value Index BS value Index BS value 0 0 8 ≤102 16 ≤1446 24 ≤20516 1 ≤10 9 ≤142 17 ≤2014 25 ≤28581 2 ≤14 10 ≤198 18 ≤2806 26 ≤39818 3 ≤20 11 ≤276 19 ≤3909 27 ≤55474 4 ≤28 12 ≤384 20 ≤5446 28 ≤77284 5 ≤38 13 ≤535 21 ≤7587 29 ≤107669 6 ≤53 14 ≤745 22 ≤10570 30 ≤150000 7 ≤74 15 ≤1038 23 ≤14726 31 >150000

[0085] For example, based on the corresponding relationship between the index value of the cache state and the numerical value of the cache state in Table 1, when the amount of cache data on the LCG is less than or equal to 10Bytes, Figure 2 The index value in the buffer size field is 1; when the amount of cached data on the LCG is greater than 276Bytes and less than or equal to 384Bytes, the index value in the buffer size field is 12.

[0086] 3.2, long BSR

[0087] For a diagram of the long BSR format BSR, see Figure 3 As shown, in Figure 3 The long BSR format consists of 8 LCG ID fields (i.e. Figure 3 LCG0~LCG7) and m cache sizes (i.e. Figure 3 The buffer size field in LCG. i For any of the 8 LCG ID fields, when LCG i When it is 1, it means that the cache status of the i-th LCG is reported; otherwise (when LCG iis not 1), it means that the cache status of the i-th LCG has not been reported. Therefore, the long BSR format can report the buffer sizes of up to 8 LCGs to the network device together. In the long BSR format, 8 bits are used to indicate the value in the cache status (that is, 8 bits are used to report the index value of the cache status, and there are 256 cache states in the long BSR format). The corresponding relationship between the index value of the cache status of the long BSR and the value of the cache status is shown in Table 2.

[0088] Table 2

[0089]

[0090]

[0091] 4. Network equipment allocates transmission resources to terminals based on BSR

[0092] When there is cached data on the LCG, the terminal determines the index value of the cache state corresponding to the amount of cached data on the LCG; the terminal reports the index value to the network device. Further, the network device will determine the cache state corresponding to the LCG based on the index value, and allocate uplink transmission resources to the terminal based on the maximum value of the cache state. For example, the BSR table in Table 1 includes a cache state, and the value range of the cache state is: greater than 38 bytes (Bytes) and less than or equal to 53Bytes. The index value of the cache state is 6. Assuming that the amount of cached data on LCG1 is 40Bytes, the terminal determines based on Table 1 that the index value of the cache state corresponding to the amount of cached data on the LCG (i.e., 40Bytes) is 6. The terminal sends a BSR to the network device, and the BSR indicates that the index value of the cache state corresponding to the amount of cached data on LCG1 is 6. The network device determines that the value of the cache state corresponding to the index value 6 is: greater than 38Bytes, and less than or equal to 53Bytes. The network device allocates uplink transmission resources to the terminal according to the maximum value 53 Bytes in the buffer state, that is, allocates uplink transmission resources capable of transmitting 53 Bytes.

[0093] Due to the high latency requirements of XR services and the existence of a timeout packet loss mechanism, the quantization interval of the cache state is too large. For example, if the rate of the XR service is 10Mbps and the frame rate is 60FPS (FPS: frame per second), the size of each video frame is 20833Bytes. If the frame transmission delay budget is 10ms, then a frame will be discarded after the waiting time in the data buffer exceeds 10ms. Therefore, the maximum amount of cache data of the LCG corresponding to the XR service is the size of a video frame, 20833Bytes. If Table 1 is used to report short BSR, the maximum index value of the cache state used is 25 (the corresponding cache state value is <= 28581Bytes), and index values ​​26-31 are not used. When a video frame arrives, the network device will schedule the terminal according to the fact that the terminal has 28581Bytes of data to upload, which wastes about 8000Bytes of uplink transmission resources compared to the actual 20833Bytes of the terminal. Similarly, if Table 2 is used to report a long BSR, the maximum index value of the cache state used is 123 (the corresponding cache state value is <= 22885Bytes), and index values ​​124-255 are not used, which will also waste scheduling resources.

[0094] Therefore, in order to make the reporting of cache status more accurate and reduce the waste of transmission resources, the embodiment of the present application provides a cache status report reporting method and communication device. The embodiment of the present application can flexibly scale the cache status through scaling parameters to make the reporting of cache status more accurate, thereby reducing the waste of transmission resources.

[0095] The following is a further introduction to the cache status report reporting method and communication device in conjunction with the accompanying drawings. It can be understood that the present application uses the network device and the terminal as an example to illustrate the execution subject of the interaction diagram, but the present application does not limit the execution subject of the interaction diagram. For example, the method executed by the network device in the present application can also be executed by a module (such as a chip, a chip system, or a processor) applied to the network device, and can also be implemented by a logical node, a logical module or software that can implement all or part of the functions of the network device; the method executed by the terminal in the present application can also be executed by a module (such as a chip, a chip system, or a processor) applied to the terminal, and can also be implemented by a logical node, a logical module or software that can implement all or part of the terminal functions.

[0096] See also Figure 4 , Figure 4 A schematic diagram of a cache status report reporting method provided in an embodiment of the present application, wherein:

[0097] 401. The terminal obtains a scaling parameter.

[0098] In the embodiment of the present application, the scaling parameter may be a parameter greater than 0. The scaling parameter is used to scale the predefined cache state or the cache state configured by the network device, that is, the scaling parameter is used to scale the value of the predefined cache state or the cache state configured by the network device.

[0099] The scaling parameter scales the predefined cache state, which can be understood as scaling parameter*predefined cache state value, or predefined cache state value / scaling parameter; optionally, a rounding operation can be added on this basis to avoid causing the value of the scaled cache state to be a decimal.

[0100] The scaling parameter scales the cache state configured by the network device, which can be understood as scaling parameter*value of the cache state configured by the network device, or value of the cache state configured by the network device / scaling parameter; optionally, a rounding operation can be added on this basis.

[0101] Optionally, the predefined cache status or the cache status configured by the network device may be the cache status in Table 1 corresponding to the above-mentioned short BSR, the cache status in Table 2 corresponding to the above-mentioned long BSR, or the cache status in other network device configurations or predefined BSR tables, which is not limited in the embodiments of the present application.

[0102] For example, take scaling the cache status in Table 1 corresponding to the above short BSR by using a scaling parameter as an example. Assuming that the scaling parameter is alpha, the BSR table obtained by scaling the cache status in Table 1 corresponding to the above short BSR by using the scaling parameter is shown in Table 3 below. The principle of scaling the cache status in other BSR tables by using the scaling parameter is the same and will not be repeated here.

[0103] Table 3

[0104] Index BS value … … 28 ≤77284*alpha 29 ≤107669*alpha 30 ≤150000*alpha 31 >150000*alpha

[0105] In the embodiment of the present application, the terminal can obtain the scaling parameter through the following two possible implementations:

[0106] Method 1: The network device determines the scaling parameter, and then the network device configures the scaling parameter to the terminal. For example, the specific implementation method can be found in Figure 5 The description in the corresponding embodiment is not repeated here.

[0107] Method 2: The terminal determines the scaling parameters by itself. For example, the specific implementation method can be found in Figure 6 The description in the corresponding embodiment is not repeated here.

[0108] 402. The terminal reports a BSR based on the scaling parameter, where the BSR indicates a cache state corresponding to the LCG, where the cache state corresponding to the LCG is obtained based on the scaling parameter and a first cache state, where the first cache state is predefined or configured by the network device. Accordingly, the network device may receive the BSR from the terminal.

[0109] In the embodiment of the present application, the reported BSR may be a short BSR or a long BSR, or other BSRs for reporting the cache status. The BSR may indicate the cache status corresponding to the LCG by carrying an index value of the cache status corresponding to the LCG.

[0110] In an embodiment of the present application, the first cache state may be a cache state in Table 1 corresponding to the above-mentioned short BSR, or the first cache state may be a cache state in Table 2 corresponding to the above-mentioned long BSR, or the first cache state may be a cache state in a BSR table configured or predefined by other network devices.

[0111] In the embodiment of the present application, the cache state corresponding to the LCG is obtained based on the scaling parameter and the first cache state. It can be understood that the cache state corresponding to the LCG is the cache state obtained by scaling the first cache state by the scaling parameter, that is, the value of the cache state corresponding to the LCG is obtained by scaling the value of the first cache state by the scaling parameter. For example, the value of the cache state corresponding to the LCG = scaling parameter * value of the first cache state.

[0112] For example, the first cache state is a cache state in Table 1 corresponding to the above short BSR. The terminal can scale the 32 cache states in Table 1 corresponding to the above short BSR based on the scaling parameter. For example, assuming that the scaling parameter is 0.2, the BSR table obtained after scaling is shown in Table 4. Assuming that the terminal determines that the amount of cache data on the LCG is 29000Bytes, the terminal reports a BSR to the network device, and the index value of the cache state carried by the BSR is 30, indicating that the cache state corresponding to the LCG is greater than 21534Bytes and less than or equal to 30000Bytes. Correspondingly, the network device can also scale the 32 cache states in Table 1 corresponding to the above short BSR based on the scaling parameter to obtain the cache state shown in Table 4. After receiving the BSR, the network device can determine that the cache state corresponding to the LCG is greater than 21534Bytes and less than or equal to 30000Bytes based on the index value 30.

[0113] Table 4

[0114]

[0115] In an embodiment of the present application, if the reported BSR is a long BSR. The cache state corresponding to the LCG is obtained based on the first cache state and the scaling parameter corresponding to the LCG. Different LCGs may correspond to the same or different scaling parameters. For example, take different LCGs corresponding to different scaling parameters as an example. The BSR indicates the cache state corresponding to LCG1 and the cache state corresponding to LCG2. The cache state corresponding to LCG1 is obtained based on scaling parameter 1 and cache state 1 corresponding to LCG1, and the cache state 1 is predefined or the cache state 1 is configured by the network device. The cache state corresponding to LCG2 is obtained based on scaling parameter 2 and cache state 2 corresponding to LCG2, and the cache state 2 is predefined or the cache state 2 is configured by the network device.

[0116] It can be seen that based on Figure 4 The described method can flexibly scale the cache state based on the scaling parameter to meet different business requirements, making the reporting of the cache state more accurate, thereby reducing the waste of transmission resources.

[0117] See also Figure 5 , Figure 5 A flowchart of another cache status report reporting method provided in an embodiment of the present application, wherein:

[0118] 501. A network device sends first configuration information to a terminal, where the first configuration information is used to configure a scaling parameter. Accordingly, the terminal may receive the first configuration information from the network device.

[0119] Optionally, the network device may determine the scaling parameter. After determining the scaling parameter, the network device sends first configuration information to the terminal, where the first configuration information is used to configure the scaling parameter.

[0120] Optionally, the network device may determine the scaling parameter based on the transmission parameter of the service. Based on this optional approach, the cache state can be made to better match the actual transmission parameter of the service, and the reporting of the cache state can be made more accurate, thereby reducing the waste of transmission resources.

[0121] Optionally, the transmission parameters of the service may include one or more of the following: a transmission rate of the service, a frame rate of the service, or a size of a video frame of the service.

[0122] For example, if the transmission parameters of the service are the transmission rate of the service and the frame rate of the service, the average video frame size of the service can be determined according to the transmission rate and frame rate of the service, and then the predefined or network device configured cache state can be scaled based on the average video frame size of the service. For another example, if the transmission parameter of the service is the size of the video frame of the service, the average video frame size of the service over a period of time can be calculated based on the size of the video frame of the service, and then the predefined or network device configured cache state can be scaled based on the average video frame size of the service. For example, assume that the average video frame size of the service is 70000Bytes. Taking the short BSR reported as an example, the maximum cache state in Table 1 is ≤150000Bytes. Therefore, the cache state in Table 1 can be reduced by 2 times, that is, the value of the cache state in Table 1*0.5.

[0123] Optionally, the network device may obtain information about IP data packets included in the video frames of the service from the core network, thereby determining the size of the video frames of the service based on the information about IP data packets included in the video frames of the service.

[0124] Optionally, the server adds the frame number information of the video frame in the real time protocol (RTP), and the core network device can mark the data packets (IP packets) belonging to the same video frame as a protocol data unit (PDU) set. The network device can obtain the frame rate based on the number of PDU sets arriving per unit time.

[0125] Optionally, the network device can determine the transmission rate of the service based on the size of the video frame and the frame rate of the service. Alternatively, the network device can negotiate the service rate with the core network and obtain the transmission rate of the service according to the negotiation result.

[0126] In a possible embodiment, the first configuration information is located in radio resource control (RRC) signaling.

[0127] In a possible embodiment, the first configuration information is also used to configure BSR reporting. For example, the first configuration information may configure a BSR reporting period, a BSR retransmission time, or configure which LCGs need to report according to which BSR tables.

[0128] That is, the first configuration information may be carried in the BSR-config field of the RRC signaling. In future communication systems, the BSR-config field may also be called other names, which are not limited in the embodiments of the present application.

[0129] 502. The terminal reports a BSR based on the scaling parameter, where the BSR indicates a cache state corresponding to the LCG, where the cache state corresponding to the LCG is obtained based on the scaling parameter and a first cache state, where the first cache state is predefined or configured by the network device. Accordingly, the network device may receive the BSR from the terminal.

[0130] The specific implementation of step 502 can refer to the specific implementation of step 402, which will not be repeated here.

[0131] It can be seen that based on Figure 5 With the described method, the network device can determine the scaling parameters and configure the scaling parameters to the terminal, so that the terminal can flexibly scale the cache state based on the scaling parameters to meet different business requirements, making the reporting of the cache state more accurate and reducing the waste of transmission resources.

[0132] See also Figure 6 , Figure 6 A flowchart of another cache status report reporting method provided in an embodiment of the present application, wherein:

[0133] 601. The terminal determines a scaling parameter.

[0134] Optionally, the terminal may determine the scaling parameter based on the transmission parameter of the service. Based on this optional approach, the cache state can be made to better match the actual transmission parameter of the service, and the reporting of the cache state can be made more accurate, thereby reducing the waste of transmission resources.

[0135] Optionally, the transmission parameters of the service may include one or more of the following: the transmission rate of the service, the frame rate of the service, or the size of the video frame of the service. Since the terminal has an application-related protocol layer, the terminal may obtain the transmission rate of the service, the frame rate of the service, or the size of the video frame of the service from the application layer.

[0136] For a specific implementation method of determining the scaling parameters based on the transmission parameters of the service, see Figure 5 The specific implementation manner in which the network device determines the scaling parameter based on the transmission parameter of the service in the corresponding embodiment is not described here.

[0137] 602. The terminal sends indication information to the network device, where the indication information indicates a scaling parameter. Accordingly, the network device may receive the indication information from the terminal.

[0138] In the embodiment of the present application, after determining the scaling parameter, the terminal may send indication information to the network device, where the indication information indicates the scaling parameter.

[0139] 603. The terminal reports a BSR based on the scaling parameter, where the BSR indicates a cache state corresponding to the LCG, where the cache state corresponding to the LCG is obtained based on the scaling parameter and a first cache state, where the first cache state is predefined or configured by the network device. Accordingly, the network device may receive the BSR from the terminal.

[0140] The specific implementation of step 603 can refer to the specific implementation of step 402, which will not be repeated here.

[0141] In a possible embodiment, the BSR and the indication information are located in the same medium access control (MAC) control element (CE). Based on this possible embodiment, it is beneficial to save signaling overhead and obtain the scaled buffer status in time.

[0142] For example, Figure 7 Take the above short BSR report as an example. Figure 7 As shown, the MAC CE where the BSR is located can also indicate the scaling parameter through 8 bits. Figure 8 Take the above long BSR report as an example. Figure 8 As shown, the MAC CE where the BSR is located can also indicate the scaling parameter through 8 bits. Fig. 9 Take the above long BSR report as an example. Fig. 9 As shown, a scaling parameter can be indicated for each Buffer Size in the MAC CE where the BSR is located. Of course, the scaling parameter can also be indicated by fewer or more bits. Figure 7 , Figure 8 and Fig. 9 Just an example.

[0143] In another possible embodiment, the BSR is located in the first MAC CE, and the indication information is located in the second MAC CE. That is, the BSR and the indication information are located in two different MAC CEs, which helps to avoid the terminal sending MAC CEs too frequently to report the BSR.

[0144] In a possible embodiment, the network device sends second configuration information to the terminal, and the second configuration information is used to configure the reporting period of the second MAC CE. Accordingly, the terminal can receive the second configuration information from the network device. After receiving the second configuration information, the terminal can report the second MAC CE based on the configured reporting period. Based on this possible embodiment, the reporting period of the second MAC CE can be made more flexible.

[0145] It can be seen that based on Figure 6With the described method, the terminal can determine the scaling parameter and indicate the scaling parameter to the network device, so that the terminal can flexibly scale the cache state based on the scaling parameter to meet different business requirements, make the reporting of the cache state more accurate, and reduce the waste of transmission resources.

[0146] The present application provides a communication device that can be used to implement the functions of the above-mentioned terminal or network device. The communication device can be a terminal or a network device. The communication device includes a module or unit corresponding to the method / operation / step / action performed by the terminal or network device in the above-mentioned method embodiment. The unit can be a hardware circuit, or software, or a combination of a hardware circuit and software. Fig.10 , Fig.10 A schematic diagram of the structure of a communication device 1000 according to an embodiment of the present application is shown. The communication device 1000 may include an interface unit 1001 and a processing unit 1002. The processing unit 1002 is used to process signaling and / or data, the signaling and / or data may be data received by the interface unit 1001, and the processed signaling and / or data may also be sent by the interface unit 1001;

[0147] In one implementation, when the communication device 1000 is a terminal, wherein:

[0148] The processing unit 1002 is used to obtain a scaling parameter;

[0149] Processing unit 1002 is used to control the device to report a BSR based on the scaling parameter, where the BSR indicates the cache status corresponding to the logical channel group LCG, where the cache status corresponding to the LCG is obtained based on the scaling parameter and the first cache status, where the first cache status is predefined or configured by the network device.

[0150] In a possible embodiment, the communication device further includes an interface unit 1001;

[0151] The interface unit 1001 is used to receive first configuration information from a network device, where the first configuration information is used to configure a scaling parameter.

[0152] In a possible embodiment, the first configuration information is also used to configure BSR reporting.

[0153] In a possible embodiment, the communication device further includes an interface unit 1001;

[0154] The interface unit 1001 is used to send indication information to the network device, where the indication information indicates a scaling parameter.

[0155] In a possible embodiment, the BSR and the indication information are located in the same medium access control MAC control element CE.

[0156] In a possible embodiment, the BSR is located in a first media access control MAC control element CE, and the indication information is located in a second MAC CE.

[0157] In a possible embodiment, the interface unit 1001 is further configured to receive second configuration information from the network device, where the second configuration information is used to configure a reporting period of the second MAC CE.

[0158] In one implementation, when the communication device 1000 is a network device, wherein:

[0159] Interface unit 1001 is used to receive a BSR from a terminal, where the BSR indicates a cache status corresponding to a logical channel group LCG, where the cache status corresponding to the LCG is obtained based on a scaling parameter and a first cache status, where the first cache status is predefined or configured by a network device.

[0160] In a possible embodiment, the interface unit 1001 is further configured to send first configuration information to the terminal, where the first configuration information is used to configure the scaling parameters.

[0161] In a possible embodiment, the first configuration information is also used to configure BSR reporting.

[0162] In a possible embodiment, the interface unit 1001 is further configured to receive indication information from a terminal, where the indication information indicates a scaling parameter.

[0163] In a possible embodiment, the BSR and the indication information are located in the same medium access control MAC control element CE.

[0164] In a possible embodiment, the BSR is located in a first media access control MAC control element CE, and the indication information is located in a second MAC CE.

[0165] In a possible embodiment, the interface unit 1001 is further configured to send second configuration information to the terminal, where the second configuration information is used to configure a reporting period of the second MAC CE.

[0166] like Fig.11 The present invention provides a communication device 1100, which is used to implement the functions of the above-mentioned terminal or network device. The device may be a communication device or a device used in a communication device. The communication device may be a terminal or a network device. The device used in the communication device may be a chip system or a chip in the communication device. The chip system may be composed of a chip, or may include a chip and other discrete devices.

[0167] The communication device 1100 includes at least one processor 1110, which is used to implement the processing function of the device (such as a network device or a terminal) in the method provided in the embodiment of the present application.

[0168] Optionally, the communication device 1100 may further include a communication interface 1120 for implementing the transceiver operation of the device (e.g., a network device or a terminal) in the method provided in the embodiment of the present application. In the embodiment of the present application, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface, which is used to communicate with other devices through a transmission medium. For example, the communication interface 1120 is used for the device in the communication device 1100 to communicate with other devices. The processor 1110 uses the communication interface 1120 to send and receive data, and is used to implement the method described in the above method embodiment. Fig.11 As shown, the communication interface 1120 may be located inside the communication device 1100 or outside the communication device 1100 , which is not limited in the embodiment of the present application.

[0169] Optionally, the communication device 1100 may also include at least one memory 1130 for storing program instructions and / or data. The memory 1130 is coupled to the processor 1110. The coupling in the embodiment of the present application is an indirect coupling or communication connection between devices, units or modules, which may be electrical, mechanical or other forms, and is used for information interaction between devices, units or modules. The processor 1110 may operate in conjunction with the memory 1130. The processor 1110 may execute program instructions stored in the memory 1130. At least one of the at least one memory may be included in the processor 1110. Alternatively, the at least one memory may be located within the communication device 1100 and outside the processor 1110. Alternatively, the at least one memory may be located outside the communication device 1100, which is not limited in the embodiment of the present application.

[0170] The specific connection medium between the communication interface 1120, the processor 1110 and the memory 1130 is not limited in the embodiment of the present application. Fig.11 The memory 1130, the processor 1110 and the communication interface 1120 are connected via a bus. Fig.11 The connections between the other components are shown in bold lines, which are only for illustration and are not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.11 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0171] When the communication device 1100 is specifically a device for a device (such as a network device or a terminal), for example, when the communication device 1100 is specifically a chip or a chip system, the communication interface 1120 may output or receive a baseband signal. When the communication device 1100 is specifically a device (such as a network device or a terminal), the communication interface 1120 may output or receive a radio frequency signal. In an embodiment of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0172] It should be noted that the above-mentioned communication interface 1120 can be used to execute the function of the above-mentioned interface unit 1001, and the above-mentioned processor 1110 can be used to execute the function of the above-mentioned processing unit 1002, which will not be repeated here.

[0173] When the above-mentioned communication device is a chip applied to a terminal, the terminal chip implements the function of the terminal in the above-mentioned method embodiment, and the terminal chip receives information from other network elements; or, the terminal chip sends information to other network elements.

[0174] When the communication device is a chip applied to a network device, the network device chip implements the function of the network device in the above method embodiment. The network device chip receives information from other network elements; or the network device chip sends information to other network elements.

[0175] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0176] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, mobile hard disks, CD-ROMs or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a network device or a terminal. Of course, the processor and the storage medium can also be present in a terminal or a network device as discrete components.

[0177] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is executed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program or instruction may be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a tape; it may also be an optical medium, such as a DVD; it may also be a semiconductor medium, such as a solid state disk (SSD).

[0178] In the various embodiments of the present application, unless otherwise specified or provided for in any logical conflict, the terms and / or descriptions between the different embodiments are consistent and may be referenced to each other, and the technical features in the different embodiments may be combined to form new embodiments according to their inherent logical relationships.

[0179] It is understood that the various numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic.

[0180] An embodiment of the present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed, the method executed by the terminal or network device in the above method embodiment is implemented.

[0181] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed, the method executed by the terminal or network device in the above method embodiment is implemented.

[0182] The embodiment of the present application also provides a communication system, which includes a terminal or a network device. The terminal is used to execute the method executed by the terminal in the above method embodiment. The network device is used to execute the method executed by the network device in the above method embodiment.

[0183] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

[0184] The descriptions of the various embodiments provided in this application can refer to each other, and the descriptions of the various embodiments have their own emphasis. For parts that are not described in detail in a certain embodiment, refer to the relevant descriptions of other embodiments. For the convenience and simplicity of description, for example, the functions of the various devices and equipment provided in the embodiments of this application and the steps of execution can refer to the relevant descriptions of the method embodiments of this application, and the various method embodiments and the various device embodiments can also refer to, combine or quote each other.

[0185] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for reporting a buffer status report (BSR), characterized in that: The method comprises: Get the scaling parameters; A BSR is reported based on the scaling parameter, wherein the BSR indicates a cache status corresponding to a logical channel group LCG, wherein the cache status corresponding to the LCG is obtained based on the scaling parameter and a first cache status, wherein the first cache status is predefined or configured by a network device.

2. The method according to claim 1, characterized in that The obtaining of the scaling parameters comprises: First configuration information is received from a network device, where the first configuration information is used to configure the scaling parameter.

3. The method according to claim 2, characterized in that The first configuration information is also used to configure reporting of the BSR.

4. The method according to claim 1, characterized in that: The method further comprises: Send indication information to a network device, where the indication information indicates the scaling parameter.

5. The method according to claim 4, characterized in that The BSR and the indication information are located in the same media access control MAC control element CE.

6. The method according to claim 4, characterized in that The BSR is located in a first media access control MAC control element CE, and the indication information is located in a second MAC CE.

7. The method according to claim 6, characterized in that The method further comprises: Receive second configuration information from a network device, where the second configuration information is used to configure a reporting period of the second MAC CE.

8. A communication device, characterized in that: The communication device comprises: A processing unit, for obtaining a scaling parameter; The processing unit is used to control the device to report a BSR based on the scaling parameter, wherein the BSR indicates a cache status corresponding to a logical channel group LCG, wherein the cache status corresponding to the LCG is obtained based on the scaling parameter and a first cache status, wherein the first cache status is predefined or configured by a network device.

9. The device according to claim 8, characterized in that The communication device also includes an interface unit; The interface unit is used to receive first configuration information from a network device, where the first configuration information is used to configure the scaling parameter.

10. The device according to claim 9, characterized in that The first configuration information is also used to configure reporting of the BSR.

11. The device according to claim 8, characterized in that The communication device also includes an interface unit; The interface unit is used to send indication information to the network device, where the indication information indicates the scaling parameter.

12. The device according to claim 11, characterized in that The BSR and the indication information are located in the same media access control MAC control element CE.

13. The device according to claim 11, characterized in that The BSR is located in a first media access control MAC control element CE, and the indication information is located in a second MAC CE.

14. The device according to claim 13, characterized in that The interface unit is further used to receive second configuration information from the network device, where the second configuration information is used to configure a reporting period of the second MAC CE.

15. A communication device, characterized in that: The device comprises a processor, the processor is coupled to a memory, the memory is used to store programs or instructions, and when the programs or instructions are executed by the processor, the device executes the method according to any one of claims 1 to 7.

16. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are called, the method described in any one of claims 1 to 7 is executed.

17. A computer program product, characterized in that The computer program product comprises: a computer program code, and when the computer program code is executed, the method according to any one of claims 1 to 7 is executed.

Images