Buffer state report reporting method and communication apparatus

Abstract

The present application provides a buffer state report (BSR) reporting method and a communication apparatus. The method comprises: acquiring a scaling parameter; and reporting a BSR on the basis of the scaling parameter, the BSR indicating a buffer state corresponding to a logical channel group (LCG), the buffer state corresponding to the LCG being obtained on the basis of the scaling parameter and a first buffer state, and the first buffer state being predefined or the first buffer state being configured by a network device. On the basis of the method provided in the present application, the buffer state can be flexibly scaled on the basis of the scaling parameter, so that different service requirements are met, and the reporting of the buffer state is more accurate, thereby reducing the waste of transmission resources.

Description

Cache status reporting method and communication device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on November 16, 2023, with application number 202311532884.0, and priority to the Chinese patent application entitled “Cache Status Reporting Method and Communication Device”, all contents of which are incorporated by reference into this application. Technical Field

[0002] 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

[0003] During uplink transmission, when a terminal has uplink data to transmit, it requests the base station to perform uplink resource scheduling through an uplink scheduling request (SR) and reports 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.

[0004] The specific process by which a terminal reports the amount of buffered data on an LCG using a BSR can be understood as: determining the buffer state (BS) corresponding to the amount of buffered data on the LCG from multiple buffer states (BS) and reporting the index value corresponding to that buffer state. The base station allocates uplink transmission resources to the terminal based on the maximum value of the buffer state corresponding to that index value.

[0005] Typically, BSRs have a bit length limit, and the number of cache states that can be divided is limited. As service requirements become more flexible, cache state reporting is inaccurate and may exceed the cache data volume, resulting in a waste of transmission resources.

[0006] Summary of the Invention

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

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

[0009] 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 needs, making the reporting of the cache status more accurate, thereby reducing the waste of transmission resources.

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

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

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

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

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

[0015] 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.

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

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

[0018] 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.

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

[0020] Based on this possible embodiment, it is beneficial to save signaling overhead and obtain the scaled cache status in a timely manner.

[0021] 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.

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

[0023] 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.

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

[0025] In the 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) 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,

[0026] A BSR is received from the 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.

[0027] 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.

[0028] 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.

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

[0030] 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.

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

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

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

[0034] 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.

[0035] 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.

[0036] The beneficial effects of the second aspect can be referred to the beneficial effects of the first aspect, and will not be repeated here.

[0037] In a third aspect, the present application provides a communication device, which may be, for example, a terminal or a module applied to a terminal, such as a processor, chip, or chip system, or a logical node, logic module, or software capable of implementing all or part of the terminal's functions. The communication device includes a module / unit for executing any method of the first aspect and its possible implementations.

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

[0039] 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.

[0040] 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.

[0041] In the seventh aspect, the present application provides a computer-readable storage medium, which stores computer-executable instructions. 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.

[0042] 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.

[0043] 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

[0044] FIG1 is a possible, non-limiting schematic diagram of a system provided by the present application;

[0045] FIG2 is a schematic diagram of a short BSR format BSR provided by this application;

[0046] FIG3 is a schematic diagram of a long BSR format BSR provided by this application;

[0047] Figures 4-6 are flowcharts of a cache status report reporting method provided by this application;

[0048] FIG7 is a schematic diagram of another short BSR format BSR provided by the present application;

[0049] FIG8 is a schematic diagram of another long BSR format BSR provided by this application;

[0050] FIG9 is a schematic diagram of another long BSR format BSR provided by this application;

[0051] 10 and 11 are schematic diagrams of the structure of the communication device provided in this application. DETAILED DESCRIPTION

[0052] The specific embodiments of the present application are further described in detail below with reference to the accompanying drawings.

[0053] The terms "first" and "second" and the like in the specification, claims, and drawings of this application are used to distinguish between different objects, not to describe a particular order. Furthermore, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not limited to the listed steps or elements, but may optionally include steps or elements not listed, or may optionally include other steps or elements inherent to the process, method, product, or apparatus.

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

[0055] In this application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that there can be three relationships. 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.

[0056] In this application, "sending information" can be understood as one device sending information to another device, or as one logical module within a device sending information to another logical 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 as logical module 1 within an access network device sending information to logical module 2 within the access network device.

[0057] In this application, "receiving information" can be understood as one device receiving information from another device, or as a logical module within a device receiving information from another logical module. For example, "an access network device receiving information" can be understood as the access network device receiving information from another device (such as a terminal), or as logical module 1 within the access network device receiving information from logical module 2 within the access network device.

[0058] In this application, "sending information to... (e.g., a terminal)" or the related illustrations in the accompanying drawings can be understood as the destination end of the information being the terminal. This can include sending information to the terminal directly or indirectly. "Receiving information from... (e.g., a terminal)" or "receiving information from... (e.g., a terminal)" or "receiving information sent by (e.g., a terminal)", or the related illustrations in the accompanying drawings can be understood as the source end of the information being the terminal, which can include receiving information from the terminal directly or indirectly. 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.

[0059] To better understand the embodiments of the present application, the following first introduces the system architecture involved in the embodiments of the present application:

[0060] The embodiments of the present application can be applied to communication systems evolved after 5G, such as long term evolution (LTE) systems, fifth generation mobile communication (5G) systems, sixth generation mobile communication (6G) systems, satellite communications, 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.

[0061] Figure 1 shows a possible, non-limiting system diagram. As shown in Figure 1 , communication system 10 includes a radio access network (RAN) 100, a core network (CN) 200, and the Internet 300. RAN 100 includes at least one RAN node (e.g., 110a and 110b in Figure 1 , collectively referred to as 110) and at least one terminal (e.g., 120a-120j in Figure 1 , collectively referred to as 120). RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment (not shown in Figure 1 ). Terminal 120 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wiredly connected to core network 200. The core network equipment in core network 200 and RAN node 110 in RAN 100 may be separate physical devices, or they may be the same physical device that integrates core network logical functions and radio access network logical functions.

[0062] The RAN 100 may be a cellular system related to the Third Generation Partnership Project (3GPP), such as a 4G or 5G mobile communication system, or a future-oriented evolutionary system (such as a 6G mobile communication system). The RAN 100 may also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. The RAN 100 may also be a communication system that integrates two or more of the above systems.

[0063] 1.RAN node 110

[0064] RAN node 110, sometimes also referred to as access network equipment, RAN entity, access node, or network equipment, constitutes part of the communication system and facilitates wireless access for terminals. Multiple RAN nodes 110 in the communication system 10 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal 120 are relative. For example, network element 120i in Figure 1 can be a helicopter or drone, which can be configured as a mobile base station. For terminal 120j accessing RAN 100 via network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes referred to as communication devices. For example, network elements 110a and 110b in Figure 1 can be understood as communication devices with base station functionality, and network elements 120a-120j can be understood as communication devices with terminal functionality.

[0065] In one 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 (such as 110a in FIG. 1 ), a micro base station or an indoor station (such as 110b in FIG. 1 ), a relay node or a donor node, or a wireless controller in a CRAN scenario. In one possible embodiment, the RAN node 110 may also be a server, a wearable device, a vehicle, or an onboard device. For example, the access network device in vehicle-to-everything (V2X) technology may be a roadside unit (RSU). All or part of the functionality of the RAN node 110 in this application may also be implemented via software functions running on hardware, or via virtualized functions instantiated on a platform (such as a cloud platform). The RAN node 110 in this 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.

[0066] 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 included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0067] 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, this application uses CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0068] In the embodiments of the present application, the form of the RAN node 110 is not limited. The device used to implement the functions of the RAN node 110 can be the RAN node 110, or it can be a device that supports the RAN node 110 in implementing the functions, such as a chip system. The device can be installed in the RAN node 110 or used in conjunction with the RAN node 110.

[0069] For ease of description, the RAN node 110 will be referred to as a network device in the following description.

[0070] 2. Terminal

[0071] Terminals can also be referred to as terminal devices, user equipment (UE), mobile stations, or mobile terminals. They can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, and smart home appliances.

[0072] In the embodiments of the present application, the form of the terminal is not limited. The device for implementing the function of the terminal can be a terminal; it can also 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.

[0073] 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.

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

[0075] 1. Extended reality (XR)

[0076] XR refers to the use of computers to combine the real and virtual worlds to create a virtual environment that allows for human-computer interaction. XR includes both VR and AR. XR services typically require low packet loss and low latency transmission.

[0077] 2. Active timeout packet loss mechanism

[0078] Because XR services require low-latency transmission, video frames for XR services must be transmitted from the server to the terminal (or from the terminal to the server) within a certain 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, and the waiting time of the XR service video frame in the terminal's buffer exceeds the latency budget, the terminal will discard the timed-out XR video frame, thereby saving transmission resources and ensuring the successful transmission of subsequent video frames.

[0079] 3. Cache Status Report

[0080] If a terminal has no uplink data to upload, but the network device allocates uplink transmission resources to the terminal, this will result in a waste of transmission resources. To avoid this waste of transmission resources, Long Term Evolution (LTE) and New Radio (NR) technologies provide an SR mechanism. In the SR mechanism, the terminal sends an SR to the network device, notifying the terminal that uplink transmission resources are needed to transmit uplink data. The terminal then reports a BSR to the network device, indicating the amount of uplink data to be transmitted by the terminal. Furthermore, the network device configures uplink transmission resources for the terminal based on the BSR.

[0081] In LTE and NR systems, terminals usually use LCG as the reporting granularity of BSR and report BSR to the network device. 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. The following takes the NR system as an example to schematically illustrate how the terminal reports the BSR to the network device.

[0082] 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.

[0083] 3.1、Short BSR

[0084] A short BSR is also called a truncated BSR. In a short BSR, only the cache status of one LCG is reported. A schematic diagram of the short BSR format is shown in Figure 2 , where 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 cache status (i.e., 5 bits are used to report the index value of the cache status; the short BSR format has 32 cache statuses). The correspondence between the index value of the short BSR cache status and the cache status value is shown in Table 1.

[0085] Table 1

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

[0087] 3.2 Long BSR

[0088] The schematic diagram of the long BSR format BSR can be seen in Figure 3. In Figure 3, the long BSR format BSR consists of 8 LCG ID fields (i.e., LCG0 to LCG7 in Figure 3) and m buffer size fields (i.e., buffer size in Figure 3). 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 i If the value is not 1, it indicates 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 eight LCGs to the network device. In the long BSR format, 8 bits are used to indicate the value of the cache status (i.e., 8 bits are used to report the index value of the cache status, and the long BSR format has 256 cache status values). The correspondence between the long BSR cache status index value and the cache status value is shown in Table 2.

[0089] Table 2

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

[0091] 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 that the index value of the cache state corresponding to the amount of cached data on the LCG (i.e., 40Bytes) is 6 based on Table 1. 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.

[0092] Due to the high latency requirements of XR services and the existence of a timeout and packet loss mechanism, the quantization range of the buffer status is too large. For example, if the XR service rate is 10Mbps and the frame rate is 60FPS (frame per second), the size of each video frame is 20,833 bytes. If the frame transmission delay budget is 10ms, then a frame will be discarded if it waits in the data buffer for more than 10ms. Therefore, the maximum buffered data size of the LCG corresponding to the XR service is 20,833 bytes, the size of a video frame. If Table 1 is used to report the short BSR, the maximum buffer status index used is 25 (corresponding to a buffer status value <= 28,581 bytes); indexes 26-31 are not used. When a video frame arrives, the network device schedules the terminal as if it has 28,581 bytes of data to upload. Compared to the terminal's actual 20,833 bytes, this wastes approximately 8,000 bytes of uplink transmission resources. Similarly, if Table 2 is used to report a long BSR, the maximum cache status index value used is 123 (the corresponding cache status value is <= 22885 Bytes), and index values ​​124-255 are not used, which will also waste scheduling resources.

[0093] Therefore, in order to make the reporting of cache status more accurate and reduce the waste of transmission resources, the embodiments of the present application provide a cache status reporting method and communication device. The embodiments 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.

[0094] 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 realize 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 realize all or part of the functions of the terminal.

[0095] Please refer to FIG4 , which is a flowchart of a cache status report reporting method provided in an embodiment of the present application, wherein:

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

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

[0098] 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 scaled cache state value to be a decimal.

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

[0100] Optionally, the predefined cache status or the cache status configured by the network device can 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.

[0101] For example, let's take scaling the cache status in Table 1 corresponding to the aforementioned short BSR using a scaling parameter as an example. Assuming the scaling parameter is alpha, the BSR table obtained by scaling the cache status in Table 1 corresponding to the aforementioned short BSR using the scaling parameter is shown in Table 3 below. The principle of scaling the cache status in other BSR tables using scaling parameters is similar and is not further described here.

[0102] Table 3

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

[0104] Mode 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 refer to the description of the embodiment corresponding to FIG5 , which will not be repeated here.

[0105] Mode 2: The terminal determines the scaling parameter by itself. For example, the specific implementation method can be found in the description of the embodiment corresponding to FIG6 , which will not be described in detail here.

[0106] 402. The terminal reports a BSR based on the scaling parameter. The BSR indicates a cache status corresponding to the LCG. 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 configured by the network device. Accordingly, the network device may receive the BSR from the terminal.

[0107] In the embodiment of the present application, the reported BSR may be a short BSR or a long BSR, or other BSRs that report 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.

[0108] 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 by other network devices or predefined.

[0109] 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. This can be understood as the cache state corresponding to the LCG being 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 * the value of the first cache state.

[0110] For example, let's assume that the first cache state is one of the cache states in Table 1 corresponding to the short BSR. The terminal can scale the 32 cache states in Table 1 corresponding to the short BSR based on a scaling parameter. For example, assuming the scaling parameter is 0.2, the resulting BSR table after scaling is shown in Table 4. Assuming the terminal determines that the amount of cached data on the LCG is 29,000 bytes, the terminal reports a BSR to the network device. The index value of the cache state carried in the BSR is 30, indicating that the cache state corresponding to the LCG is greater than 21,534 bytes and less than or equal to 30,000 bytes. Accordingly, the network device can also scale the 32 cache states in Table 1 corresponding to the short BSR based on the scaling parameter to obtain the cache states shown in Table 4. After receiving the BSR, the network device can determine, based on the index value 30, that the cache state corresponding to the LCG is greater than 21,534 bytes and less than or equal to 30,000 bytes.

[0111] Table 4

[0112] 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.

[0113] It can be seen that based on the method described in FIG. 4 , the cache status can be flexibly scaled based on the scaling parameters to meet different service requirements, making the reporting of the cache status more accurate, thereby reducing the waste of transmission resources.

[0114] Please refer to FIG5 , which is a flowchart of another cache status report reporting method provided by an embodiment of the present application, wherein:

[0115] 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.

[0116] Optionally, the network device may determine a 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.

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

[0118] 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.

[0119] For example, if the service's transmission parameters are the service's transmission rate and frame rate, the service's average video frame size can be determined based on the service's transmission rate and frame rate, and the predefined or network device-configured cache state can be scaled based on the service's average video frame size. For another example, if the service's transmission parameter is the service's video frame size, the service's average video frame size over a period of time can be calculated based on the service's video frame size, and the predefined or network device-configured cache state can be scaled based on the service's average video frame size. For example, assume the service's average video frame size is 70,000 bytes. Taking the short BSR report as an example, the maximum cache state in Table 1 is ≤150,000 bytes. Therefore, the cache state in Table 1 can be reduced by a factor of 2, that is, by multiplying the cache state value in Table 1 by 0.5.

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

[0121] Optionally, the server adds the frame number information of the video frame to the real-time protocol (RTP). The core network device can then mark the data packets (IP packets) belonging to the same video frame as a protocol data unit (PDU) set. The network device can calculate the frame rate based on the number of PDU sets that arrive per unit time.

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

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

[0124] In a possible embodiment, the first configuration information is further 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.

[0125] 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.

[0126] 502. The terminal reports a BSR based on the scaling parameter. The BSR indicates a cache status corresponding to the LCG. 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 configured by the network device. Accordingly, the network device may receive the BSR from the terminal.

[0127] The specific implementation of step 502 can refer to the specific implementation of step 402 and will not be repeated here.

[0128] It can be seen that based on the method described in Figure 5, 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 status based on the scaling parameters to meet different business needs, make the cache status reporting more accurate, and reduce the waste of transmission resources.

[0129] Please refer to FIG6 , which is a flowchart of another cache status report reporting method provided in an embodiment of the present application, wherein:

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

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

[0132] 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 can obtain the transmission rate, frame rate, or size of the video frame of the service from the application layer.

[0133] The specific implementation manner in which the terminal determines the scaling parameter based on the transmission parameter of the service can be referred to the specific implementation manner in which the network device determines the scaling parameter based on the transmission parameter of the service in the embodiment corresponding to FIG5 , which will not be described in detail here.

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

[0135] In an 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.

[0136] 603. The terminal reports a BSR based on the scaling parameter. The BSR indicates a cache status corresponding to the LCG. 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 configured by the network device. Accordingly, the network device may receive the BSR from the terminal.

[0137] The specific implementation of step 603 can refer to the specific implementation of step 402 and will not be repeated here.

[0138] 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 a timely manner.

[0139] For example, Figure 7 uses a short BSR as an example. As shown in Figure 7 , the MAC CE containing the BSR can also indicate a scaling parameter using 8 bits. For another example, Figure 8 uses a long BSR as an example. As shown in Figure 8 , the MAC CE containing the BSR can also indicate a scaling parameter using 8 bits. For another example, Figure 9 uses a long BSR as an example. As shown in Figure 9 , the MAC CE containing the BSR can indicate a scaling parameter for each buffer size. Of course, the scaling parameter can also be indicated using fewer or more bits. Figures 7, 8, and 9 are merely examples.

[0140] 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.

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

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

[0143] 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 that corresponds one-to-one 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. Please refer to Figure 10, which shows a structural diagram of a communication device 1000 in an embodiment of the present application. 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, and 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;

[0144] In one embodiment, when the communication device 1000 is a terminal, wherein:

[0145] The processing unit 1002 is configured to obtain a scaling parameter;

[0146] The processing unit 1002 is configured to control the device to report a BSR based on the scaling parameter, where the BSR indicates a 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 a first cache status, where the first cache status is predefined or configured by the network device.

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

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

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

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

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

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

[0153] 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.

[0154] 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.

[0155] In one embodiment, when the communication device 1000 is a network device, wherein:

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

[0157] 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 scaling parameters.

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

[0159] 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.

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

[0161] 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.

[0162] 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.

[0163] FIG11 shows a communication device 1100 provided in an embodiment of the present application, configured to implement the functions of the aforementioned 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 chip within the communication device. The chip system may consist of a chip alone or may include a chip and other discrete components.

[0164] 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 terminal) in the method provided in the embodiment of the present application.

[0165] Optionally, the communication device 1100 may further include a communication interface 1120 for implementing the transceiver operation of the device (such as a network device or 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, a circuit, a bus, a module or other type of communication interface for communicating with other devices via a transmission medium. For example, the device in the communication device 1100 used by the communication interface 1120 can 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. As shown in Figure 11, the communication interface 1120 may be located in the communication device 1100, or outside the communication device 1100, and the embodiment of the present application is not limited thereto.

[0166] Optionally, the communication device 1100 may further 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 exchange 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.

[0167] The specific connection medium between the communication interface 1120, processor 1110, and memory 1130 is not limited in the embodiments of the present application. In Figure 11, the embodiment of the present application shows that the memory 1130, processor 1110, and communication interface 1120 are connected via a bus. The bus is represented by a bold line in Figure 11. The connection method between other components is only for schematic illustration and is not limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one bold line is used in Figure 11, but this does not mean that there is only one bus or one type of bus.

[0168] 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.

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

[0170] When the above-mentioned communication device is a chip applied to a terminal, the terminal chip implements the functions 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.

[0171] When the communication device is a chip used in a network device, the network device chip implements the functions 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.

[0172] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be 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.

[0173] 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 read-only memory (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 an integral part of the processor. The processor and 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 storage medium can also exist as discrete components in a terminal or a network device.

[0174] 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 via 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).

[0175] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0176] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.

[0177] An embodiment of the present application further 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.

[0178] 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.

[0179] The present application also provides a communication system including a terminal or a network device, wherein the terminal is configured to execute the method executed by the terminal in the above method embodiment, and the network device is configured to execute the method executed by the network device in the above method embodiment.

[0180] 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 this application is not limited by the order of the actions described, because according to this 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 this application.

[0181] The descriptions of the various embodiments provided in this application can refer to each other. The descriptions of each embodiment have their own focus. For parts not described in detail in a particular embodiment, please refer to the relevant descriptions of other embodiments. For the convenience and brevity of description, for example, the functions and execution steps of the various devices and equipment provided in the embodiments of this application can refer to the relevant descriptions of the method embodiments of this application. The various method embodiments and the various device embodiments can also refer to, be combined with, or quote each other.

[0182] 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 them. 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 make equivalent replacements for some or all of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions 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, used 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