Buffer status reporting

Abstract

The invention relates to buffer status reporting. The embodiment of the invention relates to BSR equipment, method and device and a computer readable storage medium. The method comprises obtaining a configuration for at least a first type of BSR MAC CE and a second type of BSR MAC CE, the configuration defining at least: any one of the BSR MAC CE types can be used to report a buffer status of an LCG, where an LCG ID refers to the LCG for which the buffer status is reported, and the LCID of the BSR MAC CE indicates the type of the BSR MAC CE for reporting the buffer status of the LCG; and transmitting at least one type of BSR MAC CE to the network device based on the configuration.

Description

[0001] This divisional application is a divisional application of Chinese patent application No. 202380081576.2, with the application date of February 24, 2023 and the invention name “Buffer Status Report”. Technical Field

[0002] Embodiments of the present disclosure generally relate to the field of telecommunications, and more particularly, to a buffer status reporting (BSR) device, method, apparatus, and computer-readable storage medium. Background Art

[0003] The 3rd Generation Partnership Project (3GPP) has initiated research on enhancements to New Radio (NR) for XR (such as augmented reality (AR) and virtual reality (VR). As XR evolves, BSR may require further enhancements to accommodate XR service characteristics such as periodicity, multi-streaming, jitter, latency, and reliability. Summary of the Invention

[0004] In general, example embodiments of the present disclosure provide a BSR solution.

[0005] In a first aspect, an apparatus is provided. The apparatus includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: obtain a configuration for at least a first type of buffer status report (BSR) media access control (MAC) control element (CE) and a second type of BSR MAC CE, the configuration at least defining that any one of the BSR MAC CE types can be used to report a buffer status of a logical channel group (LCG), wherein a logical channel group identifier (LCG ID) refers to an LCG for which a buffer status is reported, and a logical channel identifier (LCID) of the BSR MAC CE indicates a type of BSR MAC CE used to report the buffer status of the LCG; and send at least one type of BSR MAC CE to a network device based on the configuration.

[0006] In a second aspect, an apparatus is provided. The apparatus includes at least one processor; and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the apparatus to at least: obtain a configuration for at least a first type of BSR MAC CE and a second type of BSR MAC CE, the configuration at least defining that only the first type of BSR MAC CE can be used to report a buffer status of a first group of LCGs, and only the second type of BSR MAC CE can be used to report a buffer status of a second group of LCGs, and that an LCID of the BSR MAC CE indicates the type of BSR MAC CE used to report the buffer status of the LCG; and; and send at least one type of BSR MAC CE to a network device based on the configuration.

[0007] In a third aspect, an apparatus is provided. The apparatus includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: receive at least one type of BSR MAC CE from a terminal device, and determine a buffer status of the terminal device based on the at least one type of BSR MAC CE and a configuration for at least a first type of BSR MAC CE and a second type of BSR MAC CE, the configuration at least defining that any one of the BSR MAC CE types can be used to report a buffer status of an LCG, wherein an LCG ID refers to an LCG for which the buffer status is reported, and an LCID of the BSR MAC CE indicates the type of BSR MAC CE used to report the buffer status of the LCG.

[0008] In a fourth aspect, an apparatus is provided. The apparatus includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: receive at least one type of BSR MAC CE from a terminal device, and determine a buffer status of the terminal device based on the at least one type of BSR MAC CE and a configuration for at least a first type of BSR MAC CE and a second type of BSR MAC CE, the configuration defining at least that only the first type of BSR MAC CE can be used to report the buffer status of a first group of LCGs, and only the second type of BSR MAC CE can be used to report the buffer status of a second group of LCGs, and that an LCID of the BSR MAC CE indicates the type of BSR MAC CE used to report the buffer status of the LCG.

[0009] In a fifth aspect, a method is provided. The method includes: obtaining a configuration for at least a first type of BSR MAC CE and a second type of BSR MAC CE, the configuration at least defining that: any one of the BSR MAC CE types can be used to report a buffer status of an LCG, wherein an LCG ID refers to an LCG for which the buffer status is reported, and an LCID of the BSR MAC CE indicates a type of BSR MAC CE used to report the buffer status of the LCG; and sending at least one type of BSR MAC CE to a network device based on the configuration.

[0010] In a sixth aspect, a method is provided. The method includes: obtaining a configuration for at least a first type of BSR MAC CE and a second type of BSR MAC CE, the configuration at least defining that: only the first type of BSR MAC CE can be used to report a buffer status of a first group of LCGs, and only the second type of BSR MAC CE can be used to report a buffer status of a second group of LCGs, and that an LCID of the BSR MAC CE indicates the type of BSR MAC CE used to report the buffer status of the LCG; and sending at least one type of BSR MAC CE to a network device based on the configuration.

[0011] In a seventh aspect, a method is provided. The method includes: receiving at least one type of BSR MAC CE from a terminal device; and determining a buffer status of the terminal device based on the at least one type of BSR MAC CE and a configuration for at least a first type of BSR MAC CE and a second type of BSR MAC CE, the configuration at least defining that any one of the BSR MAC CE types can be used to report a buffer status of an LCG, wherein an LCG ID refers to an LCG for which the buffer status is reported, and an LCID of the BSR MAC CE indicates a type of BSR MAC CE used to report the buffer status of the LCG.

[0012] In an eighth aspect, a method is provided. The method includes: receiving at least one type of BSR MAC CE from a terminal device; and determining a buffer status of the terminal device based on the at least one type of BSR MAC CE and a configuration for at least a first type of BSR MAC CE and a second type of BSR MAC CE, the configuration at least defining that only the first type of BSR MAC CE can be used to report the buffer status of a first group of LCGs, and only the second type of BSR MAC CE can be used to report the buffer status of a second group of LCGs, and that an LCID of the BSR MAC CE indicates the type of BSR MAC CE used to report the buffer status of the LCG.

[0013] In a ninth aspect, a device is provided, comprising: a component for obtaining a configuration for at least a first type of BSR MAC CE and a second type of BSR MAC CE, the configuration at least defining that: any one of the BSR MAC CE types can be used to report the buffer status of the LCG, wherein the logical channel group identifier (LCGID) refers to the LCG for which the buffer status is reported, and the LCID of the BSR MAC CE indicates the type of BSR MAC CE used to report the buffer status of the LCG; and a component for sending at least one type of BSR MAC CE to a network device based on the configuration.

[0014] In a tenth aspect, a device is provided, comprising: a component for obtaining a configuration for at least a first type of BSR MAC CE and a second type of BSR MAC CE, the configuration defining at least that only the first type of BSR MAC CE can be used to report the buffer status of a first group of LCGs, and only the second type of BSR MAC CE can be used to report the buffer status of a second group of LCGs, and that the LCID of the BSR MAC CE indicates the type of BSRMAC CE used to report the buffer status of the LCG; and; and a component for sending at least one type of BSR MAC CE to a network device based on the configuration.

[0015] In an eleventh aspect, a device is provided, comprising: a component for receiving at least one type of BSR MAC CE from a terminal device; and a component for determining a buffer status of a terminal device based on at least one type of BSR MAC CE and a configuration for at least a first type of BSR MAC CE and a configuration for a second type of BSR MAC CE, the configuration at least defining that: any one of the BSR MAC CE types can be used to report the buffer status of an LCG, wherein the LCGID refers to the LCG for which the buffer status is reported, and the LCID of the BSR MAC CE indicates the type of BSR MAC CE used to report the buffer status of the LCG.

[0016] In a twelfth aspect, a device is provided, comprising: a component for receiving at least one type of BSR MAC CE from a terminal device; and a component for determining a buffer status of a terminal device based on the at least one type of BSR MAC CE and a configuration for at least a first type of BSR MAC CE and a second type of BSR MAC CE, the configuration defining at least that only the first type of BSR MAC CE can be used to report the buffer status of a first group of LCGs, and only the second type of BSR MAC CE can be used to report the buffer status of a second group of LCGs, and that the LCID of the BSR MAC CE indicates the type of BSR MAC CE used to report the buffer status of the LCG.

[0017] In the thirteenth aspect, a computer-readable medium is provided, on which a computer program is stored, which, when executed by at least one processor of an apparatus, causes the apparatus to perform a method according to the fifth aspect, the sixth aspect, the seventh aspect or the eighth aspect.

[0018] Other features and advantages of the embodiments of the present disclosure will also be apparent from the following description of specific embodiments when read in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The embodiments of the present disclosure are presented in the form of examples, and advantages thereof will be explained in more detail below with reference to the accompanying drawings.

[0020] Figure 1 illustrates an example environment in which example embodiments of the present disclosure may be implemented;

[0021] Figure 2 shows a signaling diagram illustrating an example of a process according to some example embodiments of the present disclosure;

[0022] Figure 3 A flowchart illustrating an example method of BSR according to some example embodiments of the present disclosure is shown;

[0023] Figure 4 A flowchart illustrating an example method of BSR according to some example embodiments of the present disclosure is shown;

[0024] Figure 5 A flowchart illustrating an example method of BSR according to some example embodiments of the present disclosure is shown;

[0025] Figure 6 A flowchart illustrating an example method of BSR according to some example embodiments of the present disclosure is shown;

[0026] Figure 7 shows a simplified block diagram of a device suitable for implementing an example embodiment of the present disclosure; and

[0027] Figure 8 A block diagram of an example computer-readable medium is shown, according to some embodiments of the present disclosure.

[0028] Throughout the drawings, the same or similar reference numbers may refer to the same or similar elements. DETAILED DESCRIPTION

[0029] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to help those skilled in the art understand and implement the present disclosure, and are not intended to imply any limitation on the scope of the present disclosure. The embodiments described herein can be implemented in various ways in addition to the ways described below.

[0030] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein may have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0031] In this disclosure, references to "one embodiment," "an embodiment," "an example embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, those skilled in the art believe that it is within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.

[0032] It should be understood that although the terms "first," "second," etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element can be referred to as a second element, and similarly, a second element can be referred to as a first element, without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0033] As used herein, “at least one of: ” and “at least one of ” and similar expressions (wherein a list of two or more elements is joined by “and” or “or”) refer to at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0034] As used herein, unless explicitly stated otherwise, performing a step “in response to A” does not mean that the step is performed immediately after “A” occurs, but may include one or more intermediate steps.

[0035] The terms used herein are for the purpose of describing particular embodiments only and are not intended to limit the example embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the terms "comprises," "comprising," "has," "having," "includes," and / or "including" when used herein specify the presence of stated features, elements, and / or components, etc., but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0036] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0037] (a) a pure hardware circuit implementation (such as an implementation with only analog and / or digital circuitry), and

[0038] (b) a combination of hardware circuitry and software such as (if applicable):

[0039] (i) a combination of (one or more) analog and / or digital hardware circuits and software / firmware, and

[0040] (ii) any portion of hardware processor(s) (including digital signal processor(s)), software and memory(s) with software that work together to enable a device (such as a mobile phone or server)

[0041] perform various functions), and

[0042] (c) Hardware circuit(s) and / or processor(s), such as microprocessor(s) or portion(s) of microprocessor(s), that require software (e.g., firmware) for operation, but which may not be present when not required for operation.

[0043] This definition of circuitry applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors), or a portion of a hardware circuit or processor and its accompanying software and / or firmware. For example, if applicable to a particular claim element, the term circuitry also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0044] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), Enhanced Machine Type Communication (eMTC), etc. In addition, the communication between the terminal equipment and the network equipment in the communication network can be performed according to any suitable intergenerational communication protocol, including but not limited to first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G), sixth generation (6G) communication protocols, and / or any other protocol currently known or to be developed in the future. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communication, there will certainly be future types of communication technologies and systems that can be used to implement the present disclosure. It should not be regarded as limiting the scope of the present disclosure to the above-mentioned systems.

[0045] As used herein, the terms "network equipment", "radio network equipment" and / or "radio access network equipment" refer to nodes in a communication network via which a terminal device accesses the network and receives services from the network. A network device may refer to a base station (BS) or an access point (AP), such as a NodeB (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NRNB (also known as a gNB), a remote radio unit (RRU), a remote radio head (RRH), a relay, an integrated access and backhaul (IAB) node, a low-power node (such as a femto, a micro), a non-terrestrial network (NTN) or non-terrestrial network equipment (such as satellite network equipment), a low earth orbit (LEO) satellite and a geosynchronous orbit (GEO) satellite, an aircraft network device, etc., depending on the terminology and technology applied. In some example embodiments, a low earth orbit (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU). In some other example embodiments, a portion of the radio access network equipment or all of the radio access network equipment may be carried on an airborne or spaceborne NTN vehicle.

[0046] The term "terminal device" refers to any end device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS) or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smart phones, voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), game terminal devices, music storage and playback devices, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated process chain environments), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. The terminal device may also correspond to the mobile terminal (MT) portion of an IAB node (eg, a relay node).In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" may be used interchangeably.

[0047] As used herein, the terms "resources," "transmission resources," "resource blocks," "physical resource blocks" (PRBs), "uplink resources," or "downlink resources" may refer to any resources used to perform communication (e.g., communication between a terminal device and a network device), such as time domain resources, frequency domain resources, spatial domain resources, code domain resources, or any other resources that enable communication. Hereinafter, unless explicitly stated otherwise, resources in both the frequency domain and the time domain will be used as examples of transmission resources to describe some example embodiments of the present disclosure. It should be noted that the example embodiments of the present disclosure are equally applicable to other resources in other domains.

[0048] Figure 1 1 shows an example communication network 100 in which embodiments of the present disclosure may be implemented. Figure 1 As shown, the communication network 100 may include a terminal device 110. Hereinafter, the terminal device 110 may also be referred to as a UE.

[0049] The communication network 100 may further include a network device 120. Hereinafter, the network device 120 may also be referred to as a gNB or an eNB. The terminal device 110 may communicate with the network device 120.

[0050] It should be understood that Figure 1 The number of network devices and terminal devices shown is given for illustrative purposes and does not represent any limitation. Communication network 100 may include any suitable number of network devices and terminal devices.

[0051] In some example embodiments, the link from network device 120 to terminal device 110 may be referred to as a downlink (DL), and the link from terminal device 110 to network device 120 may be referred to as an uplink (UL). In the DL, network device 120 is a transmitting (TX) device (or transmitter), and terminal device 110 is a receiving (RX) device (or receiver). In the UL, terminal device 110 is a TX device (or transmitter), and network device 120 is an RX device (or receiver).

[0052] Communications in the communication environment 100 may be implemented according to any suitable communication protocol(s), including but not limited to first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), fifth generation (5G), sixth generation (6G), etc. cellular communication protocols, wireless local area network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocols currently known or to be developed in the future. Furthermore, communications may utilize any suitable wireless communication technology, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiplexing (OFDM), discrete Fourier transform spread spectrum OFDM (DFT-s-OFDM), and / or any other technology currently known or to be developed in the future.

[0053] As mentioned above, BSR may need to be further enhanced to adapt to the characteristics of XR services, especially the low latency requirements.

[0054] The specification defines various BSR formats. For example, BSR formats include Short BSR and Short Truncated BSR MAC, Long BSR and Long Truncated BSR, and Extended Short BSR and Extended Short Truncated BSR MAC CE. Essentially, a BSR indicates the amount of buffer data associated with one or more LCGIDs. The amount of buffer data can be indicated by the buffer size associated with a specific buffer size table.

[0055] For short BSR and short truncated BSR, the BSR of only one LCG is reported (with a fixed length of 8 bits), and the BSR includes an LCG ID field with a length of 3 bits and a buffer size field with a length of 5 bits.

[0056] Long BSR / Long Truncated BSR can report the BSR of one or more LCGs. LCGID may have a 3-bit field and can report a maximum of 8 LCGs.

[0057] Regarding XR technology, there has been discussion on whether it is necessary to add one or more new BSR tables (ie, buffer size tables) with finer granularity for XR, and whether to include reporting of delay information in the BSR.

[0058] Therefore, it is unclear how the LCHs with or without the new BSR table(s) work together when there are other logical channels (LCHs) configured for the UE in addition to the XR services (e.g., Signaling Radio Bearers (SRBs) or other services). Furthermore, the representation of buffer data may also need to be defined with the newly added BSR table(s).

[0059] The solution of the present disclosure proposes a mechanism for BSR (particularly for XR). In the solution, as an option, the terminal device 110 may obtain a configuration for at least a first type of BSR MAC CE and a second type of BSR MAC CE. The configuration may be obtained in the same message or in different messages. The configuration may be pre-configured to the terminal device 110. The configuration may at least define that any one of the BSR MAC CE types can be used to report the buffer status of an LCG, where the LCG ID refers to the LCG for which the buffer status is reported. In other words, the buffer status of any given LCG among multiple LCGs may use any one of the BSR formats for reporting the buffer status on the LCG. The LCID of the BSR MAC CE may indicate the type of BSR MAC CE used to report the buffer status of the LCG. In one embodiment, the LCID may be present in the BSR MAC CE.

[0060] As another option, terminal device 110 may obtain configuration for at least a first-type BSR MAC CE and a second-type BSR MAC CE. The configuration may be obtained in the same message or in different messages. The configuration may be pre-configured for terminal device 110. The configuration may at least define that only the first-type BSR MAC CE can be used to report the buffer status of the first group of LCGs, and only the second-type BSR MAC CE can be used to report the buffer status of the second group of LCGs.

[0061] Based on the configuration, the terminal device 110 sends at least one type of BSR MAC CE to the network device 120 .

[0062] In this way, a mechanism is provided for the coexistence of LCH / LCG configured with a legacy BSR buffer size table associated with the legacy type of BSR MAC CE and a new BSR buffer size table associated with the new type of BSR MAC CE.

[0063] Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0064] Now refer to Figure 2 , which shows a signaling diagram 200 for communication according to some example embodiments of the present disclosure. Figure 2 As shown, the signaling diagram 200 involves the terminal device 110 and the network device 120. For the purpose of discussion, reference is made to Figure 1 2. Signaling diagram 200 is described below.

[0065] It is assumed that multiple types of BSR MAC CEs can be used for buffer status reporting, namely a first type of BSR MAC CE (which can be referred to as a legacy BSR MAC CE) and a second type of BSR MAC CE (which can be referred to as a new BSR MAC CE). The type of BSR MAC CE can be indicated by the LCID of the BSR MAC CE. For example, there are 64 LCIDs. LCIDs 0-31 can be used to indicate from which LCH the buffer data is reported, and LCIDs 32-64 can be used to indicate the type of BSR MAC CE. The LCID here can also be referred to as an extended logical channel ID (eLCID).

[0066] The first type of BSR MAC CE may be associated with the legacy buffer size table(s), and the second type of BSR MAC CE may be associated with the new buffer size table(s) or both the legacy buffer size table(s) and the new buffer size table(s), which may follow a similar format containing an LCGID to indicate which LCH / LCG(s) are being reported.

[0067] The terminal device 110 may obtain at least the BSR configuration for the first type of BSR MAC CE and the BSR configuration for the second type of BSR MAC CE. Figure 2 As shown, the terminal device 110 may receive (202) a BSR configuration from the network device 120, for example, via higher layer signaling (e.g., via RRC signaling). It should be understood that the configuration may be predefined in the specification, which means that the terminal device 110 may know the BSR configuration for at least the first type of BSR MAC CE and the second type of BSR MAC CE without explicit signaling from the network device 120.

[0068] Terminal device 110 may then send (204) at least one type of BSR MAC CE to network device 120 based on the configuration at least for the first type of BSR MAC CE and for the second type of BSR MAC CE.

[0069] Between steps 202 and 204, the terminal device may determine, based on the configuration, which type of BSR MAC CE or both types of BSR MAC CEs to apply to report the buffer status of a given LCG. For example, depending on the configuration, the buffer status of a particular LCG may be reported only with a particular type of BSR MAC CE. As another example, if, depending on the configuration, both BSR MAC CEs may be used to report the buffer status of a particular LCG, the configuration may provide a rule for selecting which BSR MAC CE to use, as will be described later.

[0070] At least the BSR configuration for the first type of BSR MAC CE and the second type of BSR MAC CE can define which type of BSR MAC CE can be used to report the buffer status of which LCG. The configuration of which BSR MAC CE to use can also be specific to a logical channel (LCH), where the LCH is configured for the LCG. Therefore, the terminal device 110 can determine which type of BSR MAC CE to use to report the buffer status of which LCG. Based on this configuration, the behavior of the terminal device 110 can be further discussed as follows.

[0071] In some example embodiments, the BSR configuration for at least the first type of BSR MAC CE and the second type of BSR MAC CE may at least define that any of the BSR MAC CE types can be used to report a buffer status of an LCG, where the LCG ID refers to the LCG for which the buffer status is reported. The LCID of the subheader of the BSR MAC CE may indicate the type of BSR MAC CE used to report the buffer status of the LCG.

[0072] In this case, the first LCG ID used in the first type BSR MAC CE and the second LCG ID used in the second type BSR MAC CE may be associated with the same LCG containing the same group of one or more LCHs, or may point to the same LCG containing the same group of one or more LCHs. For example, LCG ID 1 used in the first type BSR MAC CE and LCG ID 1 used in the second type BSR MAC CE point to the same LCG. That is, the first LCG ID and the second LCG ID may have the same index.

[0073] The LCID of the BSR MAC CE may indicate which type of BSR MAC CE is used, and the reported LCG does not necessarily need other indications to indicate which buffer size table is used. This allows the buffer size of the same LCG to be reported via a first type BSR MAC CE and / or a second type BSR MAC CE, where the LCID of the BSR MAC CE tells which buffer size table is used.

[0074] Furthermore, a first type of BSR MAC CE may be associated with a first set of one or more buffer size tables, and a second type of BSR MAC CE may be associated with a second set of one or more buffer size tables.

[0075] In some examples, the buffer sizes reported for different LCGs in one type of BSR MAC CE may be associated with different buffer size tables. Which buffer size table(s) apply to which LCG or LCH can be configured by the network.

[0076] As an option, the first set of one or more buffer size tables and the second set of one or more buffer size tables may not overlap. As another option, the first set of one or more buffer size tables may have a full range of buffer sizes, and thus the first set of one or more buffer size tables and the second set of one or more buffer size tables may at least partially overlap. The second set of one or more buffer size tables may provide finer granularity for a particular range of buffer sizes than the granularity of the first set of one or more buffer size tables.

[0077] In this case, the buffer size table(s) associated with each BSR MAC CE sent is indicated by one of the LCIDs in a first set of one or more LCIDs associated with a first type of BSR MAC CE, or by one of the LCIDs in a second set of one or more LCIDs associated with a second type of BSR MAC CE.

[0078] Terminal device 110 may decide which buffer size table to use based on the following rules: The rules may be included in the configuration.

[0079] As an option, the buffer size table selected for an LCH or LCG is, for example, a table that provides the minimum difference between the amount of buffer data and the buffer size value indicated by the buffer size index in the case of a certain type of BSR MAC CE, because this difference may vary due to quantization. That is, due to different quantization of different types of BSR MAC CEs (or buffer size tables associated with different types of BSR MAC CEs), the difference in actual buffer data for different types of BSR MAC CEs may vary. For example, assume that a first type of BSR MAC CE can be used to indicate a buffer status of x, while the reported actual buffer status at the LCG / LCH is y. Further assume that a second type of BSR MAC CE can be used to indicate a buffer status of z, where z is closer to y than x. In this case, the second type of BSR MAC CE can be used to report the buffer status of the LCG / LCG.

[0080] As another option, if the buffer size of the LCH(s) / LCG(s) to be reported falls outside the range of the buffer size table associated with the second type of BSR MAC CE, the terminal device 110 may fall back to the buffer size table associated with the first type of BSR MAC CE, and vice versa. That is, the terminal device 110 may determine that the buffer size table associated with the first type of BSR MAC CE is to be used rather than the buffer size table associated with the second type of BSR MAC CE.

[0081] As described above, conventionally, a long BSR / long truncated BSR can report the BSR of one or more LCGs. The LCG ID may have a 3-bit field and can report up to 8 LCGs. For a long BSR, when all reported LCHs / LCGs use the same buffer size table, the BSR MAC CE corresponding to that buffer size table is used. Similarly, for a new type of BSR MAC CE, the LCG ID may be used to indicate which LCGs are reported, and the buffer status for each LCG may be reported based on (one or more) new buffer size tables (e.g., one or more legacy BSR buffer size tables associated with a legacy type BSR MAC CE and / or one or more new BSR buffer size tables associated with a new type BSR MAC CE).

[0082] If not all reported LCHs / LCGs use the same buffer size table, then as many BSR MAC CEs as required buffer size tables are reported for LCHs / LCGs with buffer data (i.e., non-zero), and each LCH / LCG is reported in the BSR whose LCID matches the required buffer size table.

[0083] Alternatively, a single BSR MAC CE may be used to report different LCHs / LCGs to which different buffer size tables apply. Which buffer size table applies to which LCH / LCG may be configured by network device 120. Based on this configuration, network device 120 knows which buffer size table to use for which LCH / LCG in the BSR MAC CE.

[0084] In other words, a non-zero buffer size for an LCH / LCG with buffer data can only be reported once. If a zero buffer size is indicated or no buffer size for the LCGID is present in all BSR MAC CEs (via the LCGID bitmap), network device 120 may know that no data is buffered for the LCH / LCG.

[0085] Due to the described table selection rule(s), more accurate buffer sizes of LCH(s) / LCG(s) can be reported with minimal quantization error.

[0086] In some other example embodiments, the BSR configuration for at least a first type of BSR MAC CE and a second type of BSR MAC CE may at least define that only the first type of BSR MAC CE can be used to report the buffer status of a first group of LCGs, and only the second type of BSR MAC CE can be used to report the buffer status of a second group of LCGs. The LCG groups may not overlap. The LCID of the BSR MAC CE subheader may indicate the BSR MAC CE type used to report the buffer status of the LCG.

[0087] In this case, the LCGID used in the first type of BSR MAC CE (e.g., the legacy BSR MAC CE) and the LCGID used in the second type of BSR MAC CE (e.g., the new BSR MAC CE) are separately configured so that separate LCGIDs are used for the LCH / LCG to which the legacy buffer size table associated with the first type of BSR MAC CE is applied and the LCH / LCG to which the new buffer size table associated with the second type of BSR MAC CE is applied.

[0088] Therefore, LCH / LCG configured to apply the new buffer size table only uses the new BSR MAC CE format with the new LCID. The new BSR MAC CE may only support the new buffer size table, which may also cover the legacy buffer size range, or may support both the legacy buffer size table and the new buffer size table, or may only support the new buffer size table that is different from the legacy buffer size table.

[0089] In some example embodiments, the buffer size table associated with each BSR MAC CE may be indicated by one of a first set of one or more LCIDs associated with a first type of BSR MAC CE, or by one of a second set of one or more LCIDs associated with a second type of BSR MAC CE.

[0090] Compared to the case where any of the BSR MAC CE types can be used to report the buffer status of the same LCG, in this option of a separate LCG ID pool, the number of different LCGs that can be used with the first type of BSR MAC CE and the second type of BSR MAC CE can be greater. This can provide, for example, a separate LCG for each LCH.

[0091] In this case, the terminal device 110 may determine the type of BSR MAC CE to be used to report the buffer status of the LCG, for example, based on the LCG for which the buffer status is to be reported. The network may know which LCGs are associated with which type of BSR MAC CE based on the configuration.

[0092] When the same LCH is configured as part of two LCG IDs, the BSR may be reported twice, for example, using both the legacy BSR MAC CE format and the new BSR MAC CE format. Alternatively, the terminal device 110 may be left to select which buffer size table presents the smaller quantization error and select the corresponding type of BSR MAC CE accordingly.

[0093] Alternatively or optionally, for example, the configuration may further define that the terminal device 110 may use the legacy BSR MAC CE (i.e., the first type) for the LCH / LCG only when delay information reporting is not configured for the LCH / LCG. Alternatively, the network device 120 may configure the terminal device 110 to use the legacy BSR MAC CE for the LCH / LCG only when delay information reporting is not configured for the LCH / LCG. Otherwise, the new BSR MAC CE is used.

[0094] In one embodiment, the delay information defines the delay or latency requirement for data buffered in the LCG / LCH.In one embodiment, the delay information is included in the transmitted BSR MAC CE.

[0095] After receiving at least one type of BSR MAC CE, such as Figure 2As shown, the network device 120 may determine (206) a buffer status of the relevant LCG / LCH at the terminal device 110 based on the configuration of at least the BSR for the first type of BSR MAC CE and the BSR for the second type of BSR MAC CE.

[0096] For example, network device 120 may determine a buffer size table associated with the received BSR MAC CE in at least one type of BSR MAC CE based on the LCID of the received BSR MAC CE. Network device 120 may then determine a buffer status of a related LCG / LCH at terminal device 110 based on the buffer size indicated in the received BSR MAC CE and the determined buffer size table.

[0097] In some example embodiments, an example of a buffer size table associated with a second type of BSR MAC CE (eg, a new BSR MAC CE) may be listed below. It should be understood that the buffer size table associated with the second type of BSR MAC CE may not be limited to the examples listed below.

[0098]

[0099]

[0100] In addition, the BSR MAC CE format of the second type of BSR MAC CE (e.g., the new BSR MAC CE) can be configured with an LCID and LCGID bitmap in the subheader so that the buffer size index for (one or more) LCGs can be reported (its bit is set to 1 in the bitmap). Optionally, the BSR MAC CE format of the second type of BSR MAC CE may also have a field for the remaining time information of the reported (one or more) LCGs, which is configured to report the remaining time information. The buffer size index can be mapped to different buffer size tables.

[0101] As described above, the solution of the present disclosure proposes a mechanism for the coexistence of LCH / LCGs configured with one or more legacy buffer size tables and one or more new buffer size tables. Simultaneously, a mechanism is also implemented for falling back to one or more legacy buffer size tables for LCH / LCGs configured with one or more new buffer size tables.

[0102] In the case where a separate LCGID pool can support more LCGIDs, i.e., only the first type of BSR MAC CE can be used to report the buffer status of the first set of LCGs, and only the second type of BSR MAC CE can be used to report the buffer status of the second set of LCGs. Finer granularity buffer size reporting can be supported, for example, for a separate LCG per LCH.

[0103] In case a common LCGID pool is supported, i.e. any of the BSR MAC CE types can be used to report the buffer status of the LCG, the terminal device 110 may be allowed to use one or more legacy buffer size tables, where the LCID in the sub-header of the BSR MAC CE indicates the use of the new BSR MAC CE without any other additional signalling.

[0104] Figure 3 1 shows a flow chart of an example method 300 for BSR according to some example embodiments of the present disclosure. The method 300 may be implemented in a manner such as Figure 1 For the purpose of discussion, reference will be made to the terminal device 110. Figure 1 Method 300 is described.

[0105] At 310, the terminal device 110 obtains a configuration for at least a first type of BSR MAC CE and a second type of BSR MAC CE, the configuration at least defining that any one of the BSR MAC CE types can be used to report the buffer status of the LCG, where the LCG ID refers to the LCG for which the buffer status is reported, and the LCID of the BSR MACCE indicates the type of BSR MAC CE used to report the buffer status of the LCG.

[0106] At 320 , the terminal device 110 sends at least one type of BSR MAC CE to the network device based on the configuration.

[0107] In some example embodiments, a first type of BSR MAC CE is associated with a first set of one or more buffer size tables, and a second type of BSR MAC CE is associated with a second set of one or more buffer size tables.

[0108] In some example embodiments, the first set of one or more buffer size tables and the second set of one or more buffer size tables do not overlap.

[0109] In some example embodiments, the buffer size table associated with each BSR MAC CE sent is indicated by one of a first set of one or more LCIDs associated with a first type of BSR MAC CE, or by one of a second set of one or more LCIDs associated with a second type of BSR MAC CE.

[0110] In some example embodiments, terminal device 110 may determine the type of BSR MAC CE to be used to report the buffer status of the LCG, the determination being based on the difference between the amount of buffer data on the LCG and the buffer size value indicated by the buffer size index in the case of a given type of BSR MAC CE.

[0111] In some example embodiments, the BSR MAC CE providing the minimum difference between the buffer data amount and the buffer size value indicated by the buffer size index is determined to be used for reporting the buffer status.

[0112] In some example embodiments, terminal device 110 may determine that the amount of buffer data on the LCG falls outside the range of one or more buffer size tables that can be used with the second type of BSR MAC CE; and determine to report the buffer status of the LCG by using the first type of BSR MAC CE.

[0113] In some example embodiments, terminal device 110 may determine that a first buffer size table is applicable to reporting buffer status of multiple LCGs; and report the buffer status of multiple LCGs using a BSR MAC CE type associated with a buffer size table corresponding to the first buffer size table.

[0114] In some example embodiments, terminal device 110 may determine that different buffer size tables associated with different BSR MAC CE formats are required for reporting buffer status of multiple LCGs having non-zero buffer sizes; and utilize multiple BSR MAC CEs to report buffer status of the multiple LCGs.

[0115] In some example embodiments, the number of the plurality of BSR MAC CEs corresponds to the number of different buffer size tables required to report the buffer status of one or more LCGs having a non-zero buffer size, and wherein each BSR MAC CE includes an LCID corresponding to the required buffer size table of the reported LCG.

[0116] In some example embodiments, multiple BSR MAC CEs are sent using different buffer size tables for reporting buffer status of one or more LCGs.

[0117] In some example embodiments, when delay information reporting is configured for an LCG or for a logical channel within an LCG, the terminal device 110 may avoid using a first type of BSR MAC CE to report the buffer status of the LCG.

[0118] Figure 4 4 shows a flow chart of an example method 400 for BSR according to some example embodiments of the present disclosure. The method 400 may be used in Figure 1 For the purpose of discussion, reference will be made to the terminal device 110. Figure 1 Method 400 is described.

[0119] At 410, the terminal device 110 obtains a configuration for at least a first type of BSR MAC CE and a second type of BSR MAC CE, which configuration at least defines that: only the first type of BSR MAC CE can be used to report the buffer status of the first group of LCGs, and only the second type of BSR MAC CE can be used to report the buffer status of the second group of LCGs, and the LCID of the BSR MAC CE indicates the type of BSR MAC CE used to report the buffer status of the LCG.

[0120] At 420 , the terminal device 110 sends at least one type of BSR MAC CE to the network device based on the configuration.

[0121] In some example embodiments, a first type of BSR MAC CE is associated with a first set of one or more buffer size tables, and a second type of BSR MAC CE is associated with a second set of one or more buffer size tables.

[0122] In some example embodiments, the second set of one or more buffer size tables includes at least one buffer size table of the first set of one or more buffer size tables.

[0123] In some example embodiments, the buffer size table associated with each BSR MAC CE sent is indicated by one of a first set of one or more LCIDs associated with a first type of BSR MAC CE, or by one of a second set of one or more LCIDs associated with a second type of BSR MAC CE.

[0124] In some example embodiments, the number of different LCGs that can be used for a first type of BSR MAC CE and a second type of BSR MAC CE is greater than the number that would occur if either of the BSR MAC CE types could be used to report the buffer status of the same LCG, where each LCID of the BSR MAC CE indicates a different buffer size table used in the BSR MAC CE.

[0125] In some example embodiments, terminal device 110 may determine the type of BSRMAC CE to be used to report the buffer status of an LCG, the determination being based on the LCG for which the buffer status is to be reported.

[0126] In some example embodiments, the terminal device 110 may determine that a logical channel LCH for which the buffer status is to be reported is associated with an LCG requiring a first type of BSR MAC CE and with an LCG requiring a second type of BSR MAC CE; and send two types of BSR MAC CEs to the network device to report the buffer status of the LCH.

[0127] Figure 5 1 shows a flow chart of an example method 500 for BSR according to some example embodiments of the present disclosure. The method 500 may be performed in a manner such as Figure 1 For the purpose of discussion, reference will be made to the network device 120. Figure 1 Method 500 is described.

[0128] At 510 , the network device 120 receives at least one type of BSR MAC CE from the terminal device 110 .

[0129] At 520, the network device 120 determines the buffer status of the terminal device based on at least one type of BSR MAC CE and a configuration for at least the first type of BSR MAC CE and for the second type of BSR MAC CE, the configuration defining at least that any one of the BSR MAC CE types can be used to report the buffer status of the LCG, where the LCG ID refers to the LCG for which the buffer status is reported, and the LCID of the BSR MAC CE indicates the type of BSR MAC CE used to report the buffer status of the LCG.

[0130] In some example embodiments, a first type of BSR MAC CE is associated with a first set of one or more buffer size tables, and a second type of BSR MAC CE is associated with a second set of one or more buffer size tables.

[0131] In some example embodiments, the first set of one or more buffer size tables and the second set of one or more buffer size tables do not overlap.

[0132] In some example embodiments, network device 120 may determine a buffer size table associated with the received BSR MAC CE of at least one type of BSR MAC CE based on the LCID of the received BSR MAC CE; and determine the buffer status based at least on the buffer size table.

[0133] In some example embodiments, based on determining receipt of buffer status for multiple LCGs utilizing multiple BSR MAC CEs, network device 120 may determine different buffer size tables associated with different BSR MAC CE formats required to report buffer status for multiple LCGs having non-zero buffer sizes.

[0134] Figure 6 6. A flow chart of an example method 600 for BSR according to some example embodiments of the present disclosure is shown. The method 600 may be performed in a manner such as Figure 1 For the purpose of discussion, reference will be made to the network device 120. Figure 1 Method 600 is described.

[0135] At 610 , the network device 120 receives at least one type of BSR MAC CE from the terminal device 110 .

[0136] At 620, the network device 120 determines the buffer status of the terminal device based on at least one type of BSR MAC CE and a configuration for at least the first type of BSR MAC CE and for the second type of BSR MAC CE, the configuration defining at least that only the first type of BSR MAC CE can be used to report the buffer status of the first group of LCGs, and only the second type of BSR MAC CE can be used to report the buffer status of the second group of LCGs, and that the LCID of the BSR MAC CE indicates the type of BSR MAC CE used to report the buffer status of the LCG.

[0137] In some example embodiments, a first type of BSR MAC CE is associated with a first set of one or more buffer size tables, and a second type of BSR MAC CE is associated with a second set of one or more buffer size tables, wherein the second set of one or more buffer size tables includes at least one buffer size table of the first set of one or more buffer size tables.

[0138] In some example embodiments, network device 120 may determine a buffer size table associated with the received BSR MAC CE of at least one type of BSR MAC CE based on the LCID of the received BSR MAC CE; and determine the buffer status based at least on the buffer size table.

[0139] In some example embodiments, network device 120 may utilize two types of BSR MAC CEs to receive buffer status for logical channels LCH associated with LCGs requiring a first type of BSR MAC CE and LCGs requiring a second type of BSR MAC CE.

[0140] In some example embodiments, an apparatus capable of performing method 300 (e.g., implemented at terminal device 110) may include components for performing the corresponding steps of method 300. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0141] In some example embodiments, the apparatus includes a component for obtaining a configuration for at least a first type of BSR MAC CE and a second type of BSR MAC CE, the configuration defining at least that any one of the BSR MAC CE types can be used to report a buffer status of an LCG, wherein an LCG ID refers to an LCG for which the buffer status is reported, and an LCID of the BSR MAC CE indicates a type of BSR MAC CE used to report the buffer status of the LCG; and a component for sending at least one type of BSR MAC CE to a network device based on the configuration.

[0142] In some example embodiments, a first type of BSR MAC CE is associated with a first set of one or more buffer size tables, and a second type of BSR MAC CE is associated with a second set of one or more buffer size tables.

[0143] In some example embodiments, the first set of one or more buffer size tables and the second set of one or more buffer size tables do not overlap.

[0144] In some example embodiments, the buffer size table associated with each BSR MAC CE sent is indicated by one of a first set of one or more LCIDs associated with a first type of BSR MAC CE, or by one of a second set of one or more LCIDs associated with a second type of BSR MAC CE.

[0145] In some example embodiments, the apparatus may further include means for determining a type of BSR MAC CE to be used to report the buffer status of the LCG, the determination being based on a difference between an amount of buffer data on the LCG and an amount of data that could be reported given a given type of BSR MAC CE.

[0146] In some example embodiments, the BSR MAC CE that provides the minimum difference between the amount of buffer data and the amount of data that can be reported is determined to be used for reporting the buffer status.

[0147] In some example embodiments, the apparatus may further include means for determining that an amount of buffer data on the LCG falls outside a range of one or more buffer size tables available for a second type of BSR MAC CE; and means for determining to report a buffer status of the LCG using a first type of BSR MAC CE.

[0148] In some example embodiments, the apparatus may further include means for determining that a first buffer size table is applicable to reporting buffer status of a plurality of LCGs; and means for reporting the buffer status of the plurality of LCGs using a BSR MAC CE type associated with a buffer size table corresponding to the first buffer size table.

[0149] In some example embodiments, the apparatus may further include means for determining that different buffer size tables associated with different BSR MAC CE formats are required for reporting buffer status of multiple LCGs having non-zero buffer sizes; and means for utilizing multiple BSR MAC CEs to report the buffer status of the multiple LCGs.

[0150] In some example embodiments, the number of the plurality of BSR MAC CEs corresponds to the number of different buffer size tables required to report the buffer status of one or more LCGs having a non-zero buffer size, and wherein each BSR MAC CE includes an LCID corresponding to the required buffer size table of the reported LCG.

[0151] In some example embodiments, multiple BSR MAC CEs are sent using different buffer size tables for reporting buffer status of one or more LCGs.

[0152] In some example embodiments, the apparatus may further include means for avoiding using a first type of BSR MAC CE to report a buffer status of the LCG when delay information reporting is configured for the LCG or for a logical channel within the LCG.

[0153] In some example embodiments, an apparatus capable of performing method 400 (e.g., implemented at terminal device 110) may include components for performing the corresponding steps of method 400. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0154] In some example embodiments, the apparatus includes means for obtaining a configuration for at least a first type of BSR MAC CE and for a second type of BSR MAC CE, the configuration defining at least that only the first type of BSR MAC CE can be used to report the buffer status of a first group of LCGs, and only the second type of BSR MAC CE can be used to report the buffer status of a second group of LCGs, and that the LCID of the BSR MAC CE indicates the type of BSR MAC CE used to report the buffer status of the LCG; and; and means for sending at least one type of BSR MAC CE to a network device based on the configuration.

[0155] In some example embodiments, a first type of BSR MAC CE is associated with a first set of one or more buffer size tables, and a second type of BSR MAC CE is associated with a second set of one or more buffer size tables.

[0156] In some example embodiments, the second set of one or more buffer size tables includes at least one buffer size table of the first set of one or more buffer size tables.

[0157] In some example embodiments, the buffer size table associated with each BSR MAC CE sent is indicated by one of a first set of one or more LCIDs associated with a first type of BSR MAC CE, or by one of a second set of one or more LCIDs associated with a second type of BSR MAC CE.

[0158] In some example embodiments, the number of different LCGs that can be used for a first type of BSR MAC CE and a second type of BSR MAC CE is greater than the number that can be used if either of the BSR MAC CE types can be used to report the buffer status of the same LCG, where each LCID of the BSR MAC CE indicates a different buffer size table used in the BSR MAC CE.

[0159] In some example embodiments, the apparatus may further comprise means for determining a type of BSR MAC CE to be used to report the buffer status of the LCG, the determination being based on the LCG for which the buffer status is to be reported.

[0160] In some example embodiments, the apparatus may further include a component for determining that a logical channel LCH, for which the buffer status is to be reported, is associated with an LCG requiring a first type of BSR MAC CE and an LCG requiring a second type of BSR MAC CE; and a component for sending two types of BSR MAC CEs to a network device for reporting the buffer status of the LCH.

[0161] In some example embodiments, an apparatus capable of performing method 500 (e.g., implemented at network device 120) may include components for performing the corresponding steps of method 500. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0162] In some example embodiments, the apparatus includes a component for receiving at least one type of BSR MAC CE from a terminal device; and a component for determining a buffer status of the terminal device based on the at least one type of BSR MAC CE and a configuration for at least a first type of BSR MAC CE and a configuration for a second type of BSR MAC CE, the configuration defining at least that any one of the BSR MAC CE types can be used to report the buffer status of an LCG, wherein the LCG ID refers to the LCG for which the buffer status is reported, and the LCID of the BSR MAC CE indicates the type of BSR MAC CE used to report the buffer status of the LCG.

[0163] In some example embodiments, a first type of BSR MAC CE is associated with a first set of one or more buffer size tables, and a second type of BSR MAC CE is associated with a second set of one or more buffer size tables.

[0164] In some example embodiments, the first set of one or more buffer size tables and the second set of one or more buffer size tables do not overlap.

[0165] In some example embodiments, the apparatus may further include means for determining a buffer size table associated with a received BSR MAC CE of at least one type of BSR MAC CE based on an LCID of the received BSR MAC CE; and means for determining a buffer status based at least on the buffer size table.

[0166] In some example embodiments, the apparatus may further include means for determining, based on a determination of receipt of buffer status for multiple LCGs utilizing multiple BSR MAC CEs, different buffer size tables associated with different BSR MAC CE formats required to report buffer status for multiple LCGs having non-zero buffer sizes.

[0167] In some example embodiments, an apparatus capable of performing method 600 (e.g., implemented at network device 120) may include components for performing the corresponding steps of method 600. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0168] In some example embodiments, the apparatus includes a component for receiving at least one type of BSR MAC CE from a terminal device; and a component for determining a buffer status of the terminal device based on the at least one type of BSR MAC CE and a configuration for at least a first type of BSR MAC CE and a second type of BSR MAC CE, the configuration defining at least that only the first type of BSR MAC CE can be used to report the buffer status of a first group of LCGs, and only the second type of BSR MAC CE can be used to report the buffer status of a second group of LCGs, and that the LCID of the BSR MAC CE indicates the type of BSR MAC CE used to report the buffer status of the LCG.

[0169] In some example embodiments, a first type of BSR MAC CE is associated with a first set of one or more buffer size tables, and a second type of BSR MAC CE is associated with a second set of one or more buffer size tables, wherein the second set of one or more buffer size tables includes at least one buffer size table of the first set of one or more buffer size tables.

[0170] In some example embodiments, the apparatus may further include means for determining a buffer size table associated with a received BSR MAC CE of at least one type of BSR MAC CE based on an LCID of the received BSR MAC CE; and means for determining a buffer status based at least on the buffer size table.

[0171] In some example embodiments, the apparatus may further include means for receiving, using two types of BSR MAC CEs, buffer status of logical channels LCH associated with LCGs requiring a first type of BSR MAC CE and LCGs requiring a second type of BSR MAC CE.

[0172] Figure 7is a simplified block diagram of a device 700 suitable for implementing an example embodiment of the present disclosure. The device 700 may be provided to implement a communication device, such as Figure 1 The first terminal device 110 or the second terminal device 120 is shown. As shown in the figure, the device 700 includes one or more processors 710, one or more memories 720 coupled to the processor 710, and one or more communication modules 740 coupled to the processor 710.

[0173] The communication module 740 is configured for bidirectional communication. The communication module 740 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface may represent any interface required for communication with other network elements. In some example embodiments, the communication module 740 may include at least one antenna.

[0174] Processor 710 can be of any type suitable for the local technology network and, as non-limiting examples, can include one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 700 can have multiple processors, such as application-specific integrated circuit chips that are time-slave to a clock synchronized with a main processor.

[0175] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), optical disks, laser disks, and other magnetic and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that do not persist during power outages.

[0176] The computer program 730 includes computer-executable instructions executed by the associated processor 710. The instructions of the program 730 may include instructions for performing the operations / actions of some example embodiments of the present disclosure. The program 730 may be stored in a memory (e.g., ROM 724). The processor 710 may perform any suitable actions and processes by loading the program 730 into the RAM 722.

[0177] The exemplary embodiments of the present disclosure may be implemented by the program 730 so that the device 700 can execute the reference Figures 2 to 6 Any process of the present disclosure discussed. The exemplary embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0178] In some example embodiments, the program 730 may be tangibly embodied in a computer-readable medium that may be included in the device 700 (such as in the memory 720) or in another storage device accessible to the device 700. The device 700 may load the program 730 from the computer-readable medium to the RAM 722 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. The term "non-transitory" as used herein is a limitation on the medium itself (i.e., tangible, not a signal), not a limitation on the persistence of data storage (e.g., RAM vs. ROM).

[0179] Figure 8 An example of a computer readable medium 800 is shown which may be in the form of a CD, DVD, or other optical storage disc.The computer readable medium 800 has the program 730 stored thereon.

[0180] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or a controller or other computing device, or some combination thereof.

[0181] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer-readable medium (such as a non-transitory computer-readable medium). The computer program product includes computer-executable instructions, such as instructions included in a program module, that are executed in a device on a target physical or virtual processor to perform any of the above methods. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functions of the program modules can be combined or split between program modules as needed. The machine-executable instructions for the program modules can be executed in local or distributed devices. In distributed devices, the program modules can be located in both local and remote storage media.

[0182] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. The program code can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code, when executed by the processor or controller, enables the function / operation specified in the flow chart and / or block diagram to be realized. The program code can be executed entirely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0183] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0184] Computer readable media can be computer readable signal media or computer readable storage media.Computer readable media can include but are not limited to electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing.More specific examples of computer readable storage media will include an electrical connection with one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0185] In addition, although operations are described in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in a sequential order, or that all of the operations shown be performed in order to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of this disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Unless expressly stated otherwise, certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, unless expressly stated otherwise, various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0186] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features or acts described above are disclosed as example forms of implementing the claims.

Claims

1. A device comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: Obtaining configurations for at least a legacy type of buffer status report (BSR) medium access control (MAC) control element (CE) and a new type of BSR MAC CE, wherein the legacy type of BSR MAC CE is associated with a first buffer size table, and the new type of BSR MAC CE is associated with the first buffer size table and a second buffer size table, wherein the configurations define at least: Any one of the conventional type of BSR MAC CE and the new type of BSR MAC CE can be used to report a buffer status of a logical channel group LCG, wherein a logical channel group identifier LCG ID refers to the LCG for which the buffer status is reported, and wherein a logical channel identifier LCID of the BSR MAC CE indicates the type of the BSR MAC CE used to report the buffer status of the LCG; determining that the buffer size of the LCG falls outside a range of the second buffer size table; as well as The legacy type BSR MAC CE is sent to a network device based on the determination. 2 . The apparatus of claim 1 , wherein a range of the first buffer size table and the range of the second buffer size table overlap. 3 . The apparatus of claim 2 , wherein the second buffer size table covers only a sub-range of the first buffer size table. 4 . The apparatus of claim 2 , wherein the second buffer size table provides a finer granularity than the first buffer size table.

5. An apparatus according to any one of claims 1 to 4, wherein the buffer size table associated with each BSR MAC CE sent is indicated by one LCID in a first group of one or more LCIDs associated with the traditional type of BSR MAC CE, or by one LCID in a second group of one or more LCIDs associated with the new type of BSR MAC CE.

6. The device according to any one of claims 1 to 5, wherein the device is further configured to: determining that the first buffer size table is applicable to reporting the buffer status of a plurality of LCGs; and The buffer status of the plurality of LCGs is reported using the conventional BSR MAC CE.

7. The device according to any one of claims 1 to 6, wherein the device is configured to: determining that different buffer size tables are required for reporting the buffer status of a plurality of LCGs having non-zero buffer sizes; and The buffer status of the plurality of LCGs is reported using the new type of BSR MAC CE.

8. The device according to any one of claims 1 to 7, wherein the device is further configured to: When delay information reporting is configured for an LCG or for a logical channel within the LCG, use of the legacy type of BSR MAC CE to report the buffer status of the LCG is avoided.

9. A method comprising: Obtaining configurations for at least a legacy type BSR MAC CE and a new type BSR MAC CE, wherein the legacy type BSR MAC CE is associated with a first buffer size table, and the new type BSR MAC CE is associated with the first buffer size table and the second buffer size table, the configurations defining at least: Any one of the legacy type BSR MAC CE and the new type BSR MAC CE can be used to report a buffer status of an LCG, wherein an LCGID refers to the LCG for which the buffer status is reported, and wherein an LCID of the BSR MAC CE indicates the type of the BSR MAC CE used to report the buffer status of the LCG; determining that the buffer size of the LCG falls outside a range of the second buffer size table; as well as The legacy type BSR MAC CE is sent to a network device based on the determination. 10 . The method of claim 9 , wherein a range of the first buffer size table and the range of the second buffer size table overlap. The method of claim 10 , wherein the second buffer size table covers only a sub-range of the first buffer size table.

12. The method of any one of claims 10 to 11, wherein the second buffer size table provides a finer granularity than the first buffer size table.

13. A method according to any one of claims 9 to 12, wherein the buffer size table associated with each BSR MAC CE sent is indicated by one LCID in a first group of one or more LCIDs associated with the traditional type of BSR MAC CE, or by one LCID in a second group of one or more LCIDs associated with the new type of BSR MAC CE.

14. The method according to any one of claims 9 to 13, further comprising: determining that the first buffer size table is applicable to reporting the buffer status of a plurality of LCGs; as well as The buffer status of the plurality of LCGs is reported using the conventional BSR MAC CE.

15. The method according to any one of claims 9 to 14, further comprising: determining that different buffer size tables are required for reporting the buffer status of a plurality of LCGs having non-zero buffer sizes; as well as The buffer status of the plurality of LCGs is reported using the new type of BSR MAC CE.

16. The method according to any one of claims 9 to 15, further comprising: When delay information reporting is configured for an LCG or for a logical channel within the LCG, use of the legacy type of BSR MAC CE to report the buffer status of the LCG is avoided.

17. A non-transitory computer-readable medium comprising instructions stored thereon, the instructions, when executed by at least one processor of a device, causing the device to perform at least the following: Obtaining configurations for at least a legacy type of buffer status report (BSR) medium access control (MAC) control element (CE) and a new type of BSR MAC CE, wherein the legacy type of BSR MAC CE is associated with a first buffer size table, and the new type of BSR MAC CE is associated with the first buffer size table and a second buffer size table, wherein the configurations define at least: Any one of the conventional type of BSR MAC CE and the new type of BSR MAC CE can be used to report a buffer status of a logical channel group LCG, wherein a logical channel group identifier LCG ID refers to the LCG for which the buffer status is reported, and wherein a logical channel identifier LCID of the BSR MAC CE indicates the type of the BSR MAC CE used to report the buffer status of the LCG; determining that the buffer size of the LCG falls outside a range of the second buffer size table; as well as The legacy type BSR MAC CE is sent to a network device based on the determination. 18 . The non-transitory computer-readable medium of claim 17 , wherein a range of the first buffer size table and the range of the second buffer size table overlap.

19. The non-transitory computer-readable medium of claim 18, wherein the second buffer size table covers only a sub-range of the first buffer size table.

20. The non-transitory computer-readable medium of any one of claims 18 to 19, wherein the second buffer size table provides a finer granularity than the first buffer size table.

21. A non-transitory computer-readable medium according to any one of claims 17 to 20, wherein the buffer size table associated with each BSR MAC CE sent is indicated by one of the first group of one or more LCIDs associated with the traditional type of BSR MAC CE, or by one of the second group of one or more LCIDs associated with the new type of BSR MAC CE.

22. The non-transitory computer-readable medium of any one of claims 17 to 21, further comprising instructions stored thereon that, when executed by the at least one processor, cause the apparatus to: determining that the first buffer size table is applicable to reporting the buffer status of a plurality of LCGs; and The buffer status of the plurality of LCGs is reported using the conventional BSR MAC CE.

23. The non-transitory computer-readable medium of any one of claims 17 to 22, further comprising instructions stored thereon that, when executed by the at least one processor, cause the apparatus to: determining that different buffer size tables are required for reporting the buffer status of a plurality of LCGs having non-zero buffer sizes; and The buffer status of the plurality of LCGs is reported using the new type of BSR MAC CE.

24. The non-transitory computer-readable medium of any one of claims 17 to 23, further comprising instructions stored thereon that, when executed by the at least one processor, cause the apparatus to: When delay information reporting is configured for an LCG or for a logical channel within the LCG, use of the legacy type of BSR MAC CE to report the buffer status of the LCG is avoided.

Images