Methods and systems for enhanced delay status reporting

Abstract

Embodiments herein disclose methods and systems for enhanced Delay Status Reporting (DSR) for extended reality (XR) in wireless communication networks, wherein a multi-entry DSR Medium Access Control (MAC) Control Element (CE) is used. Embodiments herein disclose methods and systems for configuring a UE for multi-entry DSR. Embodiments herein disclose methods and systems for enabling the UE to determine, compose, and send the multi-entry DSR. Embodiments herein disclose methods and systems for providing an enhanced DSR MAC CE composing and reporting for multiple thresholds for multi-modal services, configuring for multiple thresholds for enhanced DSR reporting, for signaling UE capability for enhanced DSR reporting (i.e., multi-entry DSR MAC CE), for providing multi-entry DSR MAC CE format including the extension field and multiple delay and buffer fields and identification LCID, and for including non-delay critical data in the enhanced DSR MAC CE.

Description

METHODS AND SYSTEMS FOR ENHANCED DELAY STATUS REPORTING

[0001] Embodiments disclosed herein relate to wireless communication networks, and more specifically related to method for enhanced (multi-entry) Delay Status Reporting (DSR) for extended reality (XR) in wireless communication networks.

[0002] Extended Reality (XR) is an umbrella term for different realities including Virtual Reality (VR), Augmented Reality (AR) and Mixed Reality (MR), and is considered to be an essential technology to enable the realization of digital twins / meta universe. XR is incorporated as an agreed work item in 5G Advanced (i.e., 3GPP Release 18), which is targeted to provide a communication system framework that fulfils challenging needs of high data rate, very low latency and power efficient connectivity for XR applications.

[0003] Protocol Data Convergence Protocol (PDCP), Radio Link Control (RLC) and Medium Access Control (MAC) are layer-2 sub-layers, which are involved in a number of functionalities for the data plane processing of the transmitted and received packets. Buffer Status　Reporting　(BSR) reporting procedure involves sending the buffered data status (e.g., size of the buffered data) across different Logical channel Groups (LCGs). This facilitates the scheduling operation of the network, i.e., the network can allocate the uplink grants to a User Equipment (UE) in order to serve the buffered data at the UE. However, there is no information on the delay status of the buffered data. In general, buffered data may have different delay statuses as the data storage at the buffer may happen at different points in time. Moreover, the different services have different packet delay budgets which implies the buffered data (i.e., a packet or a Service Data Unit (SDU)) is subject to being discarded when it overshoots the packet delay budget limit, or any associated limit configured. The SDU discard procedure involves discarding the PDCP SDU when the associated timer has expired or the successful delivery of a PDCP SDU has been confirmed by a peer PDCP entity; e.g., through a PDCP status report.

[0004] For XR applications, a new mechanism for Delay Status Reporting (DSR) was introduced which involves reporting the remaining time information apart from the buffered data size information for a logical channel group. However, for XR multi-model services, there may be different types of traffic flows (for example, data, voice, video, haptics, text, and so on) with different requirements of latency and synchronization, wherein these different traffic flows may be mapped to the same LCG. As a result, existing delay status reporting for LCGs may lead to inefficient scheduling.

[0005] Currently, there is no standard mechanism to reliably report and manage scheduling for XR multi-modal services (i.e., multi-modal services are not supported). This will result in unsynchronized and inconsistent application performance and also cause inefficient use of network resources. This presents a significant barrier to widespread adoption and effective utilization of XR technologies, particularly multi-modal services. In an example, DSR carries a single delay information and buffer information for critical data.

[0006] As a data stream may comprise a variety of contents, there may be non-delay critical or delay-critical. The non-delay critical data could be lying ahead of delay-critical data in the buffer in accordance with its generation and buffering at the Layer 2 (as in the example depicted in FIG. 1). Non-delay critical data may use the transmission resources and disturb the low-latency scheduling requirement of XR services for delay-critical data. The legacy approaches suffered from this inefficiency and performance degradation for XR services, with no solution.

[0007] Further, non-delay critical data which is ahead of delay-critical data (as in the example depicted in FIG. 1) would consume transmission resources; however, such data is not considered while reporting DSR, which can lead to inefficient and inaccurate scheduling and can also adversely affect the performance for XR services.

[0008] Hence, there is a need in the art for solutions which will overcome the above mentioned drawback(s), among others.

[0009] The principal object of the embodiments herein is to disclose methods and systems for enhanced Delay Status Reporting (DSR) for extended reality (XR) in wireless communication networks, wherein a multi-entry DSR Medium Access Control (MAC) Control Element (CE) is used.

[0010] Another object of the embodiments herein is to disclose methods and systems for configuring a User Equipment (UE) for multi-entry DSR.

[0011] Another object of the embodiments herein is to disclose methods and systems for enabling the UE to determine, compose, and send the multi-entry DSR.

[0012] Another object of the embodiments herein is to disclose methods and systems for providing an enhanced DSR MAC CE composing and reporting for multiple thresholds for multi-modal services

[0013] Another object of the embodiments herein is to disclose methods and systems for configuring for multiple thresholds for enhanced DSR reporting.

[0014] Another object of the embodiments herein is to disclose methods and systems for signaling UE capability for enhanced DSR reporting (i.e., multi-entry DSR MAC CE).

[0015] Another object of the embodiments herein is to disclose methods and systems for providing multi-entry DSR MAC CE format including the extension field and multiple delay and buffer fields and identification LCID.

[0016] Another object of the embodiments herein is to disclose methods and systems for including non-delay critical data in the enhanced DSR MAC CE.

[0017] Another object of the embodiments herein is to disclose the DSR MAC CE having multiple delay thresholds to cater to differing requirements of multi-modal services.

[0018] Another object of the embodiments herein is to disclose the DSR MAC CE having an inclusion option for reporting and scheduling non-delay critical data lying ahead of delay critical data.

[0019] Another object of the embodiments herein is to disclose the DSR MAC CE having a mechanism for triggering, composing and transmitting a new MAC CE format and signaling to support multi-entry DSR.

[0020] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating at least one embodiment and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

[0021] Embodiments herein are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the following illustratory drawings. Embodiments herein are illustrated by way of examples in the accompanying drawings, and in which:

[0022] FIG. 1 depicts an example data stream, according to existing arts;

[0023] FIG. 2 depicts a wireless communication network, according to embodiments as disclosed herein;

[0024] FIG. 3 illustrates an enhanced delay status reporting procedure for XR services, according to embodiments as disclosed herein;

[0025] FIG. 4 illustrates an enhanced delay status report MAC CE generation procedure for XR services, according to embodiments as disclosed herein;

[0026] FIGs. 5A and 5B are flowcharts depicting the process of standardizing multi-entry DSR pertaining to multiple reporting thresholds and catering to multi-modal communication for XR, according to embodiments as disclosed herein;

[0027] FIG. 6 depicts the procedure for the UE indicating to the network in a UE capability information message as to whether the UE is capable of supporting multi-entry, according to embodiments as disclosed herein;

[0028] FIGs. 7A and 7B depict the process of the UE being configured for multi-entry DSR, according to embodiments as disclosed herein;

[0029] FIG. 8 depicts a process of triggering the multi-entry DSR at the UE, according to embodiments as disclosed herein;

[0030] FIGs. 9A and 9B depict the process of transmitting multi-entry DSR, according to embodiments as disclosed herein;

[0031] FIG. 10 depicts the DSR MAC CE (as adopted in the 3GPP specification), according to embodiments as disclosed herein; and

[0032] FIG. 11 is a block diagram of the UE, according to embodiments as disclosed herein.

[0033] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0034] For the purposes of interpreting this specification, the definitions (as defined herein) will apply and whenever appropriate the terms used in singular will also include the plural and vice versa. It is to be understood that the terminology used herein is for the purposes of describing particular embodiments only and is not intended to be limiting. The terms "comprising", "having" and "including" are to be construed as open-ended terms unless otherwise noted.

[0035] The words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.," , "i.e.," are merely used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein using the words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.," , "i.e.," is not necessarily to be construed as preferred or advantageous over other embodiments.

[0036] Embodiments herein may be described and illustrated in terms of blocks which carry out a described function or functions.　These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.　The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block.　Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure.　Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

[0037] It should be noted that elements in the drawings are illustrated for the purposes of this description and ease of understanding and may not have necessarily been drawn to scale. For example, the flowcharts / sequence diagrams illustrate the method in terms of the steps required for understanding of aspects of the embodiments as disclosed herein. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Furthermore, in terms of the system, one or more components / modules which comprise the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0038] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any modifications, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings and the corresponding description. Usage of words such as first, second, third etc., to describe components / elements / steps is for the purposes of this description and should not be construed as sequential ordering / placement / occurrence unless specified otherwise.

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

[0040] In describing the embodiments, descriptions related to technical contents well-known in the art and not associated directly with the disclosure will be omitted. Such an omission of unnecessary descriptions is intended to prevent obscuring of the main idea of the disclosure and more clearly transfer the main idea.

[0041] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Further, the size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals or different reference numerals.

[0042] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described below in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth below, but may be implemented in various different forms. The following embodiments are provided only to completely disclose the disclosure and inform those skilled in the art of the scope of the disclosure, and the disclosure is defined only by the scope of the appended claims. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, in describing the disclosure, a detailed description of known functions or constitution incorporated herein will be omitted in the case that it is determined that the description may make the subject matter of the disclosure unnecessarily unclear. The terms which will be described below are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the operators, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

[0043] Herein, it will be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, may be performed based on computer program instructions. These computer program instructions may be loaded individually or collectively onto at least one processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which perform through any one of, or in any combination of, the at least one processor of the computer or other programmable data processing apparatus, create means for performing the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer usable or computer-readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that perform the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus to produce a computer executed process such that the instructions that perform on the computer or other programmable data processing apparatus provide steps for executing the functions specified in the flowchart block(s).

[0044] Further, each block may represent a module, segment, or portion of code, which includes one or more executable instructions for executing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks (or functions) shown in succession may in fact be performed substantially concurrently or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved.

[0045] As used in embodiments of the disclosure, a "~unit / module" may refer to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the term including the word "~unit / module" does not always have a meaning limited to software or hardware. The "~unit / module" may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the "~unit / module" includes, for example, software elements, object-oriented software elements, components such as class elements and task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The components and functions provided by the "~unit / module" may be either combined into a smaller number of components and a "~unit / module," or divided into additional components and a "~unit / module." Moreover, the components and "~units / module" may be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card. Further, in the embodiments, the "~unit / module" may include one or more processors.

[0046] The entirety of the one or more computer programs may be stored in a single memory device, or the one or more computer programs may be divided with different portions stored in different multiple memory devices.

[0047] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP, e.g. a CPU), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display driver integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, microprocessors, microcontrollers, digital　signal processors, FPGA, ASIC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like. The one processor or the combination of processors executes instructions that can be stored in a memory, such as the　operating system, in order to control the overall operation of the device.　Also, the one processor or the combination of processors is also capable of executing other processes and programs　resident in the memory, such as processes for the disclosure.

[0048] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0049] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure. Additionally, or alternatively, such software may be a computer program [product] comprising instructions which, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure.

[0050] Any such software may be stored in the form of volatile or non-volatile storage such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0051] Hereinafter, the determination of priority between A and B in the present disclosure may refer to various actions such as selecting the one having a higher priority based on a predefined priority rule and performing an operation corresponding thereto, or omitting or dropping an operation corresponding to the one having a lower priority.

[0052] Hereinafter, "A or B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0053] In addition, "at least one of A, B, and C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0054] In addition, "at least one of A, B, or C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0055] Furthermore, "A / B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0056] Furthermore, "A, B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0057] Furthermore, "A and B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0058] Furthermore, "if condition A and condition B are satisfied," as described in the present disclosure, may not be limited to a case where both condition A and condition B are satisfied, but may be understood to include a case where either condition A or condition B is individually satisfied, both condition A and condition B are satisfied, or one or more additional conditions are satisfied in combination.

[0059] Furthermore, throughout this disclosure, ordinal terms such as "first," "second," "third," etc., (and similar qualifiers) are used merely to distinguish between different instances, occurrences, configurations, messages, stages, elements or aspects of elements, operations, or information as described herein. Unless the context clearly dictates otherwise, the use of such ordinal terms does not itself require that the elements, operations, or information distinguished by these terms be structurally different, numerically distinct, or substantively dissimilar. For example, a "first signal" and a "second signal" may refer to instances of the same signal transmitted at different times or containing the same core information despite minor variations, or they may refer to signals with different content or characteristics, depending on the specific context. Similarly, a "first value" and a "second value" may represent the same magnitude but measured or applied in different circumstances, or they may represent different magnitudes. The interpretation should be guided by the specific technical context, function, and relationship described in the relevant portion of the specification and claims.

[0060] Furthermore, the terms "first ~", "second ~", etc., as described in the present disclosure with respect to various elements (e.g., information, objects, operation, sequences, or the like), should not limit those elements. These terms may only be intended to distinguish one element from another, and may not be intended to indicate a specific order. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element.

[0061] Furthermore, even if "first ~" and "second ~" are described in the present disclosure, it may be understood that element(s) referred to by "first ~" and "second ~" may be the same or different. For example, in case of element(s) being information, first information and second information may both be the same information, and, in some cases, are separate and different information.

[0062] In addition, the terms "if ~" and "in case that ~" as used in the disclosure or claims may be interpreted to include the meanings of "when (or upon) ~," "in response to ~," "based on ~," or "according to ~," and may be used interchangeably with these expressions. In addition, expressions other than those exemplified herein may also be used, as long as they have substantially the same meaning and do not impair the technical features of the present disclosure. If a method step (e.g., transmit a signal) is performed according to the disclosure of the application in connection with one of the above terms (such as "in case that ~" or the like), it may be interpreted to include the meanings (disclosure) of a prior determination that a feature has a specific state "~" (e.g., a bit length is above X), and then perform the method step in response to said determination.

[0063] In addition, the term "not perform" as used in the present disclosure or claims may, in context, be understood to mean that the corresponding step is omitted or skipped. Such a term may be replaced with other terms having the same or substantially equivalent meaning.

[0064] In addition, "transmitting a message including A and B" as described in the present disclosure, may be understood as encompassing both (i) transmitting A and B in a single message, and (ii) transmitting A and B separately via multiple messages (e.g., transmitting a first message including A and a second message including B). This interpretation may also apply to messages that include two or more items (e.g., A, B, C), transmitted either together or separately.

[0065] In addition, "transmitting a message including A and transmitting a message including B" may also be interpreted as transmitting a message including A and B in a single message.

[0066] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure may be expressed in singular or plural form depending on the specific embodiments presented. However, such singular or plural expressions are selected appropriately for convenience of description, and the present disclosure is not limited to a singular or plural number of components. A component expressed in the plural form may be implemented as a single component, and a component expressed in the singular form may be implemented as multiple components.

[0067] The drawings or flowcharts described below illustrate example methods that may be implemented according to the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, various steps in each drawing or flowchart may overlap, occur in parallel, occur in a different order, or be repeated. In other examples, any step may be omitted or replaced with another step.

[0068] The process of the flowchart may be performed by a device. One or more of the steps of the　flowchart can be implemented by one or more processors / computer programs executing　instructions to perform the noted functions.

[0069] The methods and apparatuses proposed in the embodiments of the present disclosure may be disclosed in connection with drawings disclosing flowcharts to illustrate example methods that may be implemented according to the principles of the present disclosure. Such flowcharts may contain different branches and / or sub-branches. It is understood that the principles of the present disclosure do not only contain the combination of all branches / sub-branches disclosed in the embodiment, but the present disclosure also contains at least one isolated branch / isolated sub-branch, in particular to a single branch / single sub-branch.

[0070] The methods and apparatuses proposed in the embodiments of the present disclosure are not limited to each embodiment individually, but may also be applied in combination of all or some of the embodiments proposed in the disclosure. Therefore, the embodiments of the present disclosure may be modified and applied without significantly departing from the scope of the present disclosure, as would be understood by those skilled in the art.

[0071] In this case, even if certain wordings are described differently across embodiments, they may be used interchangeably or in substitution or in combination if their underlying concepts are equivalent. For example, for the same or equivalent concept, even if one embodiment uses the expression "A" and another embodiment uses the expression "B", such expressions may be understood interchangeably, in substitution, or in combination.

[0072] The terms used in the following description to refer to access nodes, network entities, messages, interfaces between network entities, various types of identification information, and the like, are provided merely for the convenience of explanation by way of example. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may also be used. Such terms may also be interchangeable with terms defined in any 3rd generation partnership project　(3GPP) technical specifications (TS) or similar technical specifications, e.g., from ETSI, where appropriate.

[0073] Hereinafter, a base station (BS) is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a 6G base station (sNB), a wireless access unit, a BS controller, or a node on a network.

[0074] Furthermore, the base station of the present disclosure may include a split architecture comprising a central unit (CU) and a distributed unit (DU). In this structure, the CU is configured to process the higher layers of the control and user planes, while the DU is configured to process lower-layer radio resource functions. The embodiments of the present disclosure may be equally applicable to 5G base station architectures in which such CU and DU functional splits are implemented. The embodiments of the present disclosure may be equally applicable to other base station architectures in which such CU and DU functional splits are not implemented.

[0075] A terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, a television, a connected car, or any other device / system capable of performing communication functions.

[0076] In the disclosure, a downlink (DL) refers to a radio link through which a BS transmits a signal to a terminal, and an uplink (UL) refers to a radio link through which a terminal transmits a signal to a BS.

[0077] Furthermore, hereinafter, 5th generation (5G) mobile communication technologies (e.g., 5G new radio (NR)), 6th generation (6G) mobile communication technologies (e.g., 6G Radio (6GR)) may be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, newly evolved mobile communication systems developed after 5G and 6G may be included. Furthermore, based on determinations by those skilled in the art, the embodiments of the present disclosure may also be applied to other communication systems (e.g., Wi-Fi systems) through some modifications without significantly departing from the scope of the present disclosure

[0078] In the following description, the terms physical channel and signal may be used interchangeably with data or control signal. For example, the term physical downlink shared channel (PDSCH) refers to a physical channel through which data is transmitted, but the term PDSCH may also be used to refer to the data itself. That is, in the present disclosure, the expression "transmit a physical channel" may be interpreted as being equivalent to the expression "transmit data or a signal via a physical channel."

[0079] Hereinafter, in the context of the present disclosure, higher layer signaling may refer to signaling corresponding to at least one or any combination of the following: master information block (MIB), system information block (SIB) or SIB M (M = 1, 2, ...), radio resource control (RRC), or medium access control (MAC) control element (CE), or a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as Layer 3 (L3) signaling.

[0080] In addition, Layer 1 (L1) signaling may refer to signaling corresponding to at least one or any combination of signaling techniques using the at least one or any combination of the following physical layer channels or signaling: physical downlink control channel (PDCCH), downlink control information (DCI), user equipment (UE)-specific DCI, group-common DCI, common DCI, scheduling DCI (e.g., DCI used for scheduling downlink or uplink data), non-scheduling DCI (e.g., DCI not used for scheduling downlink or uplink data) physical uplink control channel (PUCCH), or uplink control information (UCI). The L1 signaling message may be referred to as a physical layer signaling.

[0081] For example, the physical layer signaling (i.e., L1 signaling) may include downlink control information (DCI). In addition, the higher layer signaling may include a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 signaling. It should be noted, however, that the higher layer signaling is not limited to the aforementioned examples.

[0082] Hereinafter, the expression that information is configured by the BS, as used in the present disclosure or claims, may, in context, be understood to mean that the terminal receives the corresponding information from the BS via a physical layer signaling or a higher layer signaling. Such an expression may be replaced with other terms having the same or substantially equivalent meaning.

[0083] Hereinafter, the operational principle of the present disclosure will be described in detail with reference to the accompanying drawings.

[0084] The embodiments herein achieve methods and systems for enhanced Delay Status Reporting (DSR) for extended reality (XR) in wireless communication networks, wherein a multi-entry DSR Medium Access Control (MAC) Control Element (CE) is used. Referring now to the drawings, and more particularly to FIGS. 2 through 11, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.

[0085] Embodiments herein disclose methods and systems for enhanced Delay Status Reporting (DSR) for extended reality (XR) in wireless communication networks, wherein a multi-entry DSR Medium Access Control (MAC) Control Element (CE) is used. Embodiments herein disclose methods and systems for configuring the UE for multi-entry DSR. Embodiments herein disclose methods and systems for enabling a User Equipment (UE) to determine, compose, and send the multi-entry DSR. Embodiments herein disclose methods and systems for providing an enhanced DSR MAC CE composing and reporting for multiple thresholds for multi-modal services, configuring for multiple thresholds for enhanced DSR reporting, for signaling UE capability for enhanced DSR reporting (i.e., multi-entry DSR MAC CE), for providing multi-entry DSR MAC CE format including the extension field and multiple delay and buffer fields and identification Logical Channel Identity (LCID) or extended-LCID (eLCID), and for including non-delay critical data in the enhanced DSR MAC CE. The DSR MAC CE can have multiple delay thresholds to cater to differing requirements of multi-modal services, an inclusion option for reporting and scheduling non-delay critical data lying ahead of delay critical data, and a mechanism for triggering, composing and transmitting a new MAC CE format and signaling to support multi-entry DSR.

[0086] Embodiments herein use the terms 'enhanced DSR' and 'multi-entry DSR' interchangeably to refer to the enhanced DSR for extended reality (XR) in wireless communication networks, wherein a multi-entry DSR Medium Access Control (MAC) Control Element (CE) is used.

[0087] FIG. 2 depicts a wireless communication network, wherein a base station 202 (for example, a gNodeB (gNB)) in the network is connected to at least one User Equipment (UE) 201. The UE 201 indicates XR capability for multi-entry DSR and inclusion of the non-delay critical data information in the multi-entry DSR through a UE capability information message. The UE 201 can be configured by the network (NW) configuration for multi-entry DSR with multiple delay thresholds. The UE 201 can include non-delay critical data information in the multi-entry DSR.

[0088] An indication of multi-entry DSR for multiple thresholds can be included by the UE 201 through the multi-entry DSR MAC CE. The UE 201 can trigger the multi-entry DSR MAC CE when more than one delay threshold condition is satisfied. If the non-delay critical data is ahead of the delay critical data in the buffer, the UE 201 can also account for such non-delay critical data.

[0089] The format for the multi-entry DSR MAC CE includes an extension field, multiple instances of delay and buffer fields and an identification (e-)LCID. The (e-)LCID value set in the MAC sub-header by the UE 201 can be used to identify the multi-entry DSR MAC CE. The multi-entry DSR MAC CE comprises of a bitmap for LCGs (wherein a bit is set to 1 for a LCG which is to be reported, otherwise the bit is set to 0) and a set of delay information and buffer information pertaining to each of the delay thresholds which is to be reported. The multi-entry DSR MAC CE comprises of an extension bit, which can be used to separate the sets of delay information and buffer information

[0090] The UE 201 can transmit the multi-entry DSR MAC CE over available UL-SCH resources (if available), and the available resources can accommodate the multi-entry DSR MAC CE completely (including the associated MAC sub-header). If the UL-SCH resources are not available, or the available resources cannot accommodate the multi-entry DSR MAC CE completely (including the associated MAC sub-header), the UE 201 can trigger a scheduling request.

[0091] The UE 201 includes (or excludes) non-delay critical data information in the multi-entry DSR MAC CE (e.g., based on congestion activation status (or congestion deactivation status)), as indicated by the base station 202 for the UE 201 or relevant LCGs.

[0092] In an embodiment herein, the UE 201 ensures that at least two instances of delay information and buffer information are considered, while one or more instances of delay information and buffer information may be skipped, if available UL-SCH resources are not sufficient.

[0093] In an embodiment herein, the UE 201 informs the base station 202 whether it is capable of enhanced delay status reporting (i.e., multi-entry DSR). In an embodiment herein, the UE 201 can send this information in the RRC procedures for UE capability information retrieval. In an embodiment herein, the capability can be a UE Access Stratum (AS) capability. In an embodiment herein, the UE 201 can use a common capability for the XR for multi-entry DSR.

[0094] In an embodiment herein, the UE 201 can include the PDU Set Importance (PSI) information in the multi-entry DSR. In an embodiment herein, the UE 201 may not include the PSI information in the multi-entry DSR. In an embodiment herein, whether the UE 201 includes the PSI information or not in the multi-entry DSR can depend on whether congestion activation status or congestion deactivation status is indicated by the base station 202 for the relevant UE or relevant PDCP entity or relevant radio bearer or relevant logical channel or relevant logical channel group or relevant modality / modalities or QoS flow(s). In an embodiment herein, the UE 201 can include the PSI information in the multi-entry DSR, when congestion activation status is indicated by the base station 202. In an embodiment herein, the UE 201 may not include the PSI information in the multi-entry DSR, when congestion deactivation status is indicated by the base station 202.

[0095] In an embodiment herein, the UE 201 may include non-delay critical data related information in the multi-entry DSR. In an embodiment herein, the UE 201 may not include non-delay critical data related information in the multi-entry DSR. In an embodiment herein, whether the UE 201 does include or not include the non-delay critical data related information in the multi-entry DSR is dependent upon an indication or configuration (e.g., whether congestion activation status or congestion deactivation status is indicated) by the base station 202 for the relevant UE or relevant PDCP entity or relevant radio bearer or relevant logical channel or relevant logical channel group or relevant modality / modalities or QoS flow(s). In an embodiment herein, the UE 201 can include non-delay critical data related information in the multi-entry DSR, on the congestion activation status being indicated by the base station 202. In an embodiment herein, the UE 201 may not include non-delay critical data related information in the multi-entry DSR, when congestion deactivation status is indicated by the base station 202.

[0096] In an embodiment herein, the multi-entry DSR can be carried in a new MAC CE (e.g. this may be termed as enhanced DSR MAC CE or a multi-entry DSR MAC CE). The new MAC CE is identified by a MAC sub-header with a LCID or an extended LCID (eLCID). In an embodiment herein, the new MAC CE can be of a fixed size. In an embodiment herein, the new MAC CE can be of a variable size.

[0097] In an embodiment herein, the multi-entry DSR can be carried in the legacy MAC CE (e.g., this may be termed as DSR MAC CE). In an embodiment herein, the multi-entry DSR can be carried in an extended legacy MAC CE. The extended legacy MAC CE can be identified by a MAC sub-header with a LCID or an extended LCID (eLCID). In an embodiment herein, the extended legacy MAC CE can be of a fixed size. In an embodiment herein, the extended legacy MAC CE can be of a variable size.

[0098] In an embodiment herein, the UE 201 may include one or more delay information and / or buffer size information (i.e., one or more instances or fields that carry remaining time and / or buffer size) pertaining to at least one LCG in the enhanced DSR MAC CE (or multi-entry DSR MAC CE). The identification for the LCG may be based on a bitmap field wherein each bit of the bitmap indicates whether the corresponding LCG is being reported or is not being reported in the enhanced DSR MAC CE. For example, a bit set to 1 indicates that the corresponding LCG is being reported and a bit set to 0 indicates that the corresponding LCG is not being reported or vice-versa. The order of the bit in the bitmap for the corresponding LCG may pertain to or has been mapped to a specific LCG configured for the UE 201.

[0099] In an embodiment herein, for enhanced DSR MAC CE, the identification of one or more delay information and / or buffer information of a specific LCG may be based on a bitmap with a length of N bits. Each bit in the bitmap indicates whether the corresponding delay information and / or buffer information for the specific LCG is being reported or is not being reported in the enhanced DSR MAC CE. For example, a bit in the bitmap set to 1 indicates corresponding delay information and / or buffer information for the specific LCG is being reported and a bit in the bitmap set to 0 indicates corresponding delay information and / or buffer information for the specific LCG is not being reported or vice-versa. The order of the bit in the bitmap for corresponding delay information and / or buffer information for the specific LCG may pertain to or mapped to a specific reporting threshold configured for the specific LCG.

[0100] In an embodiment herein, for enhanced DSR MAC CE (or multi-entry DSR MAC CE), the identification of one or more delay information and / or buffer information of a specific LCG may be based on a field with a length of N bits. The field indicates the number of the delay information and / or buffer information instances for the specific LCG is being reported. For example, a field set to 2 indicates that 2 instances of delay information and / or buffer information for the specific LCG is being reported.

[0101] In an embodiment herein, for enhanced DSR MAC CE (or multi-entry DSR MAC CE), the identification of one or more delay information and / or buffer information of a specific LCG may be based on an extension field. The extension field with each instance of the delay information and / or buffer information for the specific LCG, indicates whether another instance of the delay information and / or buffer information is followed (i.e., being reported in the enhanced DSR MAC CE) for the same LCG or not. For example, the extension bit set to 1 indicates the next delay information and / or buffer information for the specific LCG is followed and the extension bit set to 0 indicates the next delay information and / or buffer information for the specific LCG is not followed or vice-versa.

[0102] In an embodiment herein, a LCG of the UE 201 may be configured with multi-entry DSR and / or one or more associated triggering thresholds and / or one or more associated reporting thresholds. The configuration may be provided in a RRC signaling; for example, a RRC reconfiguration message.

[0103] In an embodiment herein, a LCG of the UE 201 may be configured with legacy delay status reporting and / or associated triggering threshold and / or associated reporting threshold. The configuration may be provided in a RRC signaling; for example, a RRC reconfiguration message.

[0104] In an embodiment herein, a LCG of the UE 201 may be configured with both multi-entry DSR and / or one or more associated triggering thresholds and / or one or more associated reporting thresholds and with legacy delay status reporting and / or associated triggering threshold and / or associated reporting threshold. The configuration may be provided in a RRC signaling; for example, a RRC reconfiguration message.

[0105] In an embodiment herein, the configured triggering threshold is lower than the configured highest reporting threshold. In an embodiment herein, the configured triggering threshold is lower than the configured lowest reporting threshold. In an embodiment herein, the configured triggering threshold is between the lowest and the highest reporting threshold. In an embodiment herein, the configured triggering threshold is higher than the configured highest reporting threshold. In an embodiment herein, the configured triggering threshold is higher than the configured lowest reporting threshold. In an embodiment herein, the triggering threshold and / or reporting thresholds may be reconfigured (i.e. setup, modified or released) by a RRC signaling message; for example, a RRC reconfiguration message.

[0106] In an embodiment herein, the UE 201 can generate an enhanced DSR MAC CE (or multi-entry DSR MAC CE) only if uplink Shared Channel (UL-SCH) resources are available for a new transmission and the enhanced DSR MAC CE comprising all the delay information and / or buffer information for the LCGs that are to be reported can be accommodated in the UL-SCH resources. That is, the enhanced DSR MAC CE is required to include all the delay information of all LCGs which have pending DSRs when the MAC PDU containing this enhanced DSR MAC CE is to be built. This implies that the enhanced DSR MAC CE is always generated in the complete form and partial information is not conveyed.

[0107] In an embodiment herein, the UE 201 can generate an enhanced DSR MAC CE only if uplink Shared Channel (UL-SCH) resources are available for a new transmission and the enhanced DSR MAC CE comprising all the delay information and / or buffer information pertaining to the at least delay-critical data for the LCGs that are to be reported can be accommodated in the UL-SCH resources as a result of logical channel prioritization.

[0108] In an embodiment herein, the UE 201 can generate an enhanced DSR MAC CE only if uplink Shared Channel (UL-SCH) resources are available for a new transmission and the enhanced DSR MAC CE comprising all the delay information and / or buffer information pertaining to the at least non-delay-critical data for the LCGs that are to be reported can be accommodated in the UL-SCH resources as a result of logical channel prioritization.

[0109] In an embodiment herein, the UE 201 can generate an enhanced DSR MAC CE only if uplink Shared Channel (UL-SCH) resources are available for a new transmission and the enhanced DSR MAC CE comprising of at least one delay information and / or buffer information for the LCGs that are to be reported can be accommodated in the UL-SCH resources. That is, one or more delay information and / or buffer information for the LCGs that are to be reported can be skipped if the enhanced DSR MAC CE cannot be accommodated in the UL-SCH resources as a result of logical channel prioritization.

[0110] In an embodiment herein, the UE 201 can generate an enhanced DSR MAC CE only if uplink Shared Channel (UL-SCH) resources are available for a new transmission and the enhanced DSR MAC CE comprising of at least two instances of delay information and / or buffer information for the LCG(s) that are to be reported can be accommodated in the UL-SCH resources. That is, one or more instances of delay information and / or buffer information for the LCG(s) that are to be reported can be skipped if the enhanced DSR MAC CE cannot be accommodated in the UL-SCH resources as a result of logical channel prioritization.

[0111] In an embodiment herein, the UE 201 may skip one or more instances of delay information and / or buffer information for the LCG that are to be reported if enhanced DSR MAC CE (i.e., without skipping) cannot be accommodated in the UL-SCH resources as a result of logical channel prioritization.

[0112] In an embodiment herein, the UE 201 may skip one or more instances of delay information and / or buffer information for the LCG that are to be reported if enhanced DSR MAC CE (i.e., without skipping) cannot be accommodated in the UL-SCH resources as a result of logical channel prioritization, wherein the skipped one or more instances of delay information and / or buffer information for the LCG pertain to higher reporting thresholds than that of the delay information and / or buffer information for the LCG that are not skipped.

[0113] In an embodiment herein, the UE 201 may skip one or more instances of delay information and / or buffer information for the LCG that are to be reported if enhanced DSR MAC CE (i.e., without skipping) cannot be accommodated in the UL-SCH resources as a result of logical channel prioritization, wherein the skipped one or more instances of delay information and / or buffer information for the LCG pertain to lower reporting thresholds than that of the delay information and / or buffer information for the LCG that are not skipped.

[0114] In an embodiment herein, the UE 201 can generate a legacy DSR MAC CE, if uplink Shared Channel (UL-SCH) resources are available for a new transmission and the enhanced DSR MAC CE comprising all the delay information and / or buffer information for the LCGs that are to be reported cannot be accommodated in the UL-SCH resources as a result of logical channel prioritization. This also considers that legacy DSR MAC CEs can be completely accommodated in the UL-SCH resources as a result of logical channel prioritization.

[0115] In an embodiment herein, the UE 201 may generate and send either enhanced DSR MAC CE or (legacy) DSR MAC CE corresponding to the configuration or reconfiguration of the LCG.

[0116] In an embodiment herein, the UE 201 may generate and send either enhanced DSR MAC CE or (legacy) DSR MAC CE depending on the number of instances of the delay information and / or buffer information of the LCG to be reported. For example, if there is not more than one instance of the delay information and / or buffer information of each of the LCG(s) to be reported, UE generates (legacy) DSR MAC CE. If there are more than one instance of the delay information and / or buffer information of at least one LCG to be reported, the UE generates enhanced DSR MAC CE.

[0117] In an embodiment herein, the UE 201 may generate and send both enhanced DSR MAC CE or (legacy) DSR MAC CE in the same MAC PDU corresponding to the configuration or reconfiguration of the LCGs; e.g., the one set of LCGs are configured for enhanced DSR and the second set of LCGs are configured for legacy DSR.

[0118] In an embodiment herein, if the instance of delay information and / or buffer information for a higher reporting threshold is reported in a previous transmission of enhanced DSR MAC CE, a new DSR is not triggered at the UE 201 when the remaining time for this data falls below the triggering threshold.

[0119] In an embodiment herein, if the instance of delay information and / or buffer information for a higher reporting threshold is reported in a previous transmission of enhanced DSR MAC CE, a new DSR may be triggered at the UE 201 when the remaining time for this data falls below the triggering threshold.

[0120] In an embodiment herein, if the instance of delay information and / or buffer information for a non-delay-critical data is reported in a previous transmission of enhanced DSR MAC CE, a new DSR is not triggered at the UE 201 when this data becomes delay-critical data.

[0121] In an embodiment herein, if the instance of delay information and / or buffer information for a non-delay-critical data is reported in a previous transmission of enhanced DSR MAC CE, a new DSR may be triggered at the UE 201 when this data becomes delay-critical data.

[0122] FIG. 3 illustrates an enhanced delay status reporting procedure for XR services. In step 301, the UE 201 is configured for multi-entry DSR for one or more LCGs by the base station 202, which includes the triggering threshold, and one or more reporting thresholds. In step 302, the multi-entry DSR is triggered at the UE 201; i.e., one or more instances of delay information pertaining to reporting thresholds are to be reported. In step 303, the UE 201 checks if the UL-SCH resources can accommodate the multi-entry DSR MAC CE, along with the corresponding sub-header. If the UL-SCH resources can accommodate the multi-entry DSR MAC CE, along with the corresponding sub-header, in step 304, the multi-entry DSR MAC CE is generated at the UE 201, wherein a MAC entity (not shown) in the UE 201 instructs a multiplexing and assembly procedure to generate the multi-entry DSR MAC CE. If the UL-SCH resources cannot accommodate the multi-entry DSR MAC CE, along with the corresponding sub-header, in step 305, the UE 201 further checks if the UL-SCH resources can accommodate the legacy DSR MAC CE with the corresponding sub-header. If the UL-SCH resources can accommodate the legacy DSR MAC CE with the corresponding sub-header, in step 306, the legacy DSR MAC CE is generated at the UE 201 by reporting only one instance of delay information for the LCG, wherein a MAC entity (not shown) in the UE instructs a multiplexing and assembly procedure to generate the legacy DSR MAC CE. In an embodiment herein, the reported instance of delay information can pertain to the lowest reporting threshold. In an embodiment herein, if the UE 201 is not configured for multi-entry DSR for one or more LCGs by the base station 202 and if the UL-SCH resources can accommodate the legacy DSR MAC CE with the corresponding sub-header, the UE 201 can generate the legacy DSR MAC CE by reporting only one instance of delay information. The various actions in method 300 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 3 may be omitted.

[0123] FIG. 4 illustrates an enhanced delay status report MAC CE generation procedure for XR services. In step 401, the UE 201 is configured for multi-entry DSR for one or more LCGs by the base station 202, which includes the triggering threshold, and one or more reporting thresholds. In step 402, the multi-entry DSR is triggered at the UE 201; i.e., one or more instances of delay information pertaining to reporting thresholds are to be reported. In step 403, the UE 201 checks if the UL-SCH resources can accommodate the multi-entry DSR MAC CE, along with the corresponding sub-header. If the UL-SCH resources can accommodate the multi-entry DSR MAC CE, along with the corresponding sub-header, in step 404, the multi-entry DSR MAC CE is generated at the UE 201, wherein a MAC entity (not shown) in the UE instructs a multiplexing and assembly procedure to generate the multi-entry DSR MAC CE. If the UL-SCH resources cannot accommodate the multi-entry DSR MAC CE, along with the corresponding sub-header, in step 405, the multi-entry DSR MAC is generated at the UE 201 by skipping one more instances of delay information for a LCG that could not be accommodated, wherein a MAC entity (not shown) in the UE instructs a multiplexing and assembly procedure to generate the multi-entry DSR MAC CE. In an embodiment herein, the reported instance of delay information can pertain to the highest reporting threshold. The various actions in method 400 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 4 may be omitted.

[0124] FIGs. 5A and 5B are flowcharts depicting the process of standardizing multi-entry DSR pertaining to multiple reporting thresholds and catering to multi-modal communication for XR. In step 501, the UE 201 indicates to the network (i.e., the base station 202) in a UE capability information message as to whether the UE 201 is capable of supporting multi-entry DSR (i.e., multi-entry DSR MAC CE based reporting). The configuration comprises the multi-entry DSR parameters associated with a plurality of delay thresholds for at least one LCG. In an embodiment herein, the UE 201 can indicate whether the UE is capable of supporting the multi-entry DSR to the network in Radio Resource Control (RRC) procedures for UE capability information retrieval. In an embodiment herein, the UE 201 can indicate whether the UE is capable of supporting the multi-entry DSR to the network in a UE capability information message. The UE 201 can support multi-entry DSR based on at least one of UE implementation; and usage of eXR (Rel-19 enhanced XR) feature.

[0125] In step 502, the UE 201 is configured by the network with multi-entry DSR and associated configuration parameters, wherein this configuration is in response to receiving the UE capability information message by the network. The configuration can be indicated for at least one LCG of the UE; and included in a RRC reconfiguration message from the network. The configuration comprises at least one of the multi-entry DSR reporting; at least one associated triggering threshold; and / or at least one associated reporting threshold. The configuration further comprises an indication for one of inclusion or exclusion of non-delay-critical data information in the multi-entry DSR reporting.

[0126] In step 503, the UE 201 is further configured by the network for inclusion of non-delay critical data related information in the multi-entry DSR reporting for a specific LCG.

[0127] In step 504, the UE 201 determines if the delay status information is to be reported for one or more delay threshold(s) for at least one LCG. The UE 201 check if delay status information reporting is met for at least one configured delay threshold for the LC pertaining to a configured LCG. This can comprise the UE 201 determining if the presence of a buffered Service Data Unit (SDU)　for the LC for which time remaining before discardTimer expiry is less than the delay threshold. If an instance of at least one of delay information; and buffer information for a first reporting threshold is reported in a previous transmission of the multi-entry DSR MAC CE, the UE 201 skips triggering a new DSR when the remaining time for the delay status information falls below a second threshold. If the instance of at least one of delay information; and buffer information for a non-delay-critical data is reported in a previous transmission of the multi-entry DSR MAC CE, the UE 201 triggers a new DSR if the delay status information becomes delay-critical data.

[0128] If the delay status information is to be reported for one or more delay threshold(s) for at least one LCG, in step 505, the UE 201 triggers an assembly of the multi-entry DSR. The UE 201 includes non-delay critical data in the multi-entry DSR, if the network has indicated or configured for inclusion for a relevant LCG. The UE 201 does not include non-delay critical data in the multi-entry DSR, if the network has indicated or configured for exclusion for a relevant LCG. In an embodiment herein, the UE 201 reports delay information and buffer information associated with the different reporting thresholds in the LCG consecutively in an ascending order based on the values of the reporting thresholds. If the extension bit is set to 1, the UE 201 determines that another instance of delay and buffer information for the same LCG is to be included in the multi-entry DSR MAC CE, and includes the another instance of delay and buffer information for the same LCG in the multi-entry DSR MAC CE accordingly. If the extension bit is set to 0, the UE 201 determines that another instance of delay and buffer information for the same LCG is not to be included in the MAC CE. The multi-entry DSR MAC CE comprises a bitmap, buffer information and delay information corresponding to each of the delay thresholds for which the delay status information is to be reported; and an extension bit. The bitmap identifies at least one LCG for which delay status information is to be reported. The extension bit is configured to separate delay information and buffer information. The multi-entry DSR MAC CE can be of a variable size CE. The multi-entry DSR MAC CE can be identified by a logical channel identifier (LCID) value set in the MAC sub-header. The variable size CE comprises a variable number of delay information and buffer information for the triggered DSRs corresponding to the satisfied delay thresholds of the configured LCGs. In an embodiment herein, the UE 201 performs multi-entry delay status reporting on a per-LC basis.

[0129] In step 506, the UE 201 determines if the UL-SCH resources can accommodate the multi-entry DSR MAC CE, along with the MAC sub-header. If the UL-SCH resources can accommodate the multi-entry DSR MAC CE, along with the MAC sub-header, in step 507, the UE 201 transmits a multi-entry DSR MAC CE, wherein the multi-entry DSR MAC CE can include non-critical data in accordance with the multiple delay thresholds. If the UL-SCH resources cannot accommodate the multi-entry DSR MAC CE, along with the MAC sub-header, in step 508, the UE 201 triggers a scheduling request; i.e., the UE 201 transmits a scheduling request to the network. The various actions in method 500 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIGs. 5A and 5B may be omitted.

[0130] FIG. 6 depicts the procedure for the UE indicating to the network in a UE capability information message as to whether the UE is capable of supporting multi-entry. The UE 201 may indicate support (or no support) for multi-entry DSR to the network in a UE capability information message. The support for enhanced DSR corresponds to supporting the multi-entry DSR MAC CE reporting in accordance with the multiple delay thresholds that can be configured for the UE 201. As depicted in FIG. 6, the UE 201 can send the UE capability information indicating support for enhanced DSR in the RRC procedures in response to UE capability information retrieval; i.e., the network (i.e., the base station 202) sends a UE capability enquiry message to the UE 201 and the UE 201 responds with a UE capability information message including a field (for example, termed asmultipleEntryDelayStatusReport). In an embodiment herein, the UE 201 can indicate the support (or no support) for enhanced DSR based on the UE implementation. In an embodiment herein, the UE 201 can indicate the support (or no support) for enhanced DSR based on the usage of eXR (Rel-19 enhanced XR) feature.

[0131] FIGs. 7A and 7B depict the process of the UE being configured for multi-entry DSR. As depicted in FIG. 7A, the UE 201 receives configuration for enhanced DSR in response to transmission of UE capability information message. The configuration can be indicated for at least one Logical Channel Group (LCG) of the UE, i.e., on a per LCG basis. The configuration includes enhanced DSR reporting and / or one or more associated triggering thresholds and / or one or more associated reporting thresholds. The network (i.e., the base station 202) includes the configuration in the RRC reconfiguration message. The configuration comprises an indication for inclusion or exclusion of non-delay-critical data information in multi-entry DSR reporting. Accordingly, the UE 201 includes (or excludes) non-delay critical data information in the multi-entry DSR.

[0132] In an embodiment herein, as depicted in FIG. 7B, the UE 201 includes (or excludes) non-delay critical data information in the multi-entry DSR based on congestion activation status (or congestion deactivation status), as indicated by the network for UE or relevant LCG(s).

[0133] FIG. 8 depicts a process of triggering the multi-entry DSR at the UE. The UE 201 determines if delay status information reporting is met for one or more configured delay threshold(s) for a LC pertaining to a configured LCG. This comprises the presence of a buffered SDU for the LC for which the remaining time beforediscardTimerexpiry is less than the delay threshold. The UE 201 triggers the multi-entry DSR for the relevant configured LCG pertaining to the LC. If the instance of delay information and / or buffer information for a first reporting threshold is reported in a previous transmission of enhanced DSR MAC CE, the UE 201 skips triggering a new DSR when the remaining time for this data falls below a second reporting threshold. If the instance of delay information and / or buffer information for a non-delay-critical data is reported in a previous transmission of enhanced DSR MAC CE, the UE 201 triggers a new DSR when this data becomes delay-critical data.

[0134] FIGs. 9A and 9B depict the process of transmitting multi-entry DSR. As depicted in FIG. 9A, the UE 201 determines if there is any triggered enhanced DSR. The UE 201 further checks if there are available uplink (UL) SCH (UL-SCH) transmission resources and the available resources can completely accommodate the multi-entry DSR MAC CE, based on the following:

[0135] - Both delay critical data and non-delay critical data;

[0136] - The MAC sub-header for enhanced DSR MAC CE (i.e. 1 additional byte); and

[0137] - All the instances of the delay information and buffer information for all satisfied delay thresholds for configured LCGs for which DSRs are triggered.

[0138] If the UE 201 determines that UL-SCH resources are not available or are not sufficient to accommodate the multi-entry DSR, the UE 201 triggers a scheduling request (SR) for availing a new grant of resources to the network (i.e., the base station 202), so as to transmit the multi-entry DSR completely in the new grant. In an embodiment herein, the SR resource can be a resource configured for one of the LCs for which the multi-entry DSR has been triggered.

[0139] In an embodiment herein (as depicted in FIG. 9B), the UE 201 considers at least two instances of delay information and buffer information, while one or more instances of delay information and buffer information may be skipped, if available UL-SCH resources are not sufficient.

[0140] Upon triggering of enhanced DSR and availability of UL-SCH resources, the UE 201 assembles the multi-entry DSR MAC CE. The UE 201 utilizes the new MAC CE format for conveying the multi-entry DSR to the network (also termed as multi-entry DSR MAC CE). The UE 201 composes the multi-entry DSR MAC CE as a variable size CE, including a variable number of delay information and buffer information for the triggered DSRs corresponding to the satisfied delay thresholds of the configured LCGs. The UE 201 identifies the multi-entry DSR MAC CE by a new (e-)LCID value XXX, wherein this value in the MAC sub-header of multi-entry DSR MAC CE in the MAC PDU to be transmitted in UL direction is set by the UE 201. Table 1 depicts the values of on-octet eLCID for UL-SCH.

[0141] Code pointIndexLCID values0 to 21x64 to 28xReservedxxxxxxMulti-entry DSR

[0142] The UE 201 inserts a bitmap for indicating LCGs (wherein the bit is set to 1 for a LCG for which enhanced DSR is to be reported, and the bit is set to 0 for a LCG for which enhanced DSR does not have to be reported) and a set of delay information and buffer information pertaining to each of the satisfied delay thresholds for LCGs that are to be reported. The UE 201 inserts and sets an extension bit to separate the set of delay information and the buffer information.

[0143] In an embodiment herein, the extension bit conveys to the network (i.e., the receiver) whether another instance of delay and buffer information is expected or not, as there is no length field for this variable size MAC CE. If the extension bit is set to 1, this indicates that the next delay information and / or buffer information for the specific LCG is followed. If the extension bit is set to 0, this indicates that the next delay information and / or buffer information for the specific LCG is not followed (as depicted in FIG. 10, which depicts the DSR MAC CE (as adopted in the 3GPP specification)).

[0144] FIG. 11 is a block diagram of the UE. The device 201 is an electronic device capable of wireless communication and having various form factors, examples of the terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, a television, a connected car or any other device / system capable of performing wireless communication with a base station (BS) and / or another terminal through a wireless channel.

[0145] Referring to FIG. 11, the UE 201 may include at least one transceiver (hereinafter, referred to as simply "transceiver") 1101, at least one processor (hereinafter, referred to as simply "processor") 1102, and at least one memory (hereinafter, referred to as simply "memory") 1103. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 1101, the processor 1102, and the memory 1103 of the UE 201 may operate. However, components of the UE 201 are not limited to the example components illustrated in FIG. 11. In another embodiment, the UE 201 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 1101, the processor 1102, or the memory 1103 may be integrated in the form of one component.

[0146] The transceiver 1101 may be a communication circuit or communication circuitry that enables the UE 201 to perform wireless communication with a node or an entity of a network. For example, the transceiver 1101 may enable the UE 201 to transmit or receive a signal to or from a BS through cellular communication, or to transmit or receive a signal to or from another UE through cellular communication. For example, the transceiver 1101 may support at least one of various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (1101) may include all subsequent generations of evolved wireless communications.

[0147] According to an embodiment, the transceiver 1101 may include various circuit structures used to transmit or receive signals to or from a BS through a wireless channel. The signals may include control information and data. For example, the transceiver 1101 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 1101 may output a signal received through a wireless channel to the processor 1102 and may transmit, through a wireless channel, a signal output from the processor 1102.

[0148] According to an embodiment, the UE 201 may include a plurality of transceivers. For example, in the case of supporting evolved-universal terrestrial radio access-new radio (E-UTRA-NR) dual connectivity (EN-DC), the UE 201 may include a first transceiver supporting the 4G LTE wireless communication and a second transceiver supporting the 5G NR wireless communication. According to another embodiment, in the case of supporting NR-dual connectivity (NR-DC), the UE 201 may include a plurality of transceivers supporting the 5G NR wireless communication. According to still another embodiment, in the case of supporting near field wireless communication, the UE 201 may separately include a transceiver supporting at least one standard in the group of wireless communication protocol standards as defined in the protocol standards for Bluetooth, wireless local area network (WLAN) network (including institute of electrical and electronics engineers (IEEE) 802.11-2016 standard or its amendments, e.g., 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be, without being limited thereto).

[0149] The processor 1102 may control general operations of the UE 201 according to embodiments of the disclosure. The processor 1102 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 1102 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1103, individually, collectively or in any combination thereof. Further, the processor 1102 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0150] The processor 1102 may be electrically, operatively, and / or communicatively coupled to the transceiver 1101 to control the transceiver 1101.

[0151] The processor 1102 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. For example, the processor 1102 may include a communication processor (CP) configured to control communication operations and an application processor (AP) configured to control execution of an upper layer (for example, an application layer). In a specific embodiment, at least a part of the processor 1102 may be included in one chip and the other part of the processor 1102 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the transceiver 1101 or the memory 1103.

[0152] The processor 1102 may perform or control or cause an operation of the UE 201 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1102 may control operations of the UE 201 for processing a downlink signal received from a BS or generating and transmitting an uplink signal to a BS. To this end, the processor 1102 may execute a computer program, codes, or instructions stored in the memory 1103, so as to control other components of the UE 201 to enable execution of various operations.

[0153] The memory 1103 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1103 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0154] The memory 1103 may be electrically, operatively, and / or communicatively coupled to the processor 1102 and may be accessed by the processor 1102.

[0155] The memory 1103 may store a computer program, codes, or instructions executable by the processor 1102. According to an embodiment, a computer program, codes, or instructions executable by the processor 1102 may be either stored in a single memory device or separated and stored in a distributed manner in two or more memory devices. By executing the instructions stored in the memory 1103, the processor 1102 may perform various functions according to an embodiment of the disclosure.

[0156] According to an embodiment of the disclosure, operations of the UE 201 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1103 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0157] The processor 1102 can indicate to the network (i.e., the base station 202) in a UE capability information message as to whether the PROCESSOR 1102 is capable of supporting multi-entry DSR (i.e., multi-entry DSR MAC CE based reporting). The configuration comprises the multi-entry DSR parameters associated with a plurality of delay thresholds for at least one LCG. In an embodiment herein, the processor 1102 can indicate whether the UE is capable of supporting the multi-entry DSR to the network in Radio Resource Control (RRC) procedures for UE capability information retrieval. In an embodiment herein, the processor 1102 can indicate whether the UE is capable of supporting the multi-entry DSR to the network in a UE capability information message. The processor 1102 can support multi-entry DSR based on at least one of UE implementation; and usage of eXR (Rel-19 enhanced XR) feature.

[0158] The processor 1102 enables the UE 201 to be configured by the network with multi-entry DSR and associated configuration parameters, wherein this configuration is in response to receiving the UE capability information message by the network. The configuration can be indicated for at least one LCG of the UE; and included in a RRC reconfiguration message from the network. The configuration comprises at least one of the multi-entry DSR reporting; at least one associated triggering threshold; and / or at least one associated reporting threshold. The configuration further comprises an indication for one of inclusion or exclusion of non-delay-critical data information in the multi-entry DSR reporting.

[0159] The processor 1102 enables the UE 201 to be configured by the network for inclusion of non-delay critical data related information in the multi-entry DSR reporting for a specific LCG. In an embodiment herein, the PROCESSOR 1102 can be indicated as to status of the congestion, wherein the status can be one of congestion activation, and congestion deactivation.

[0160] The processor 1102 can determine if the delay status information is to be reported for more than one delay threshold for at least one LCG. The processor 1102 can check if delay status information reporting is met for at least one configured delay threshold for the LC pertaining to a configured LCG. This can comprise the processor 1102 determining if the presence of a buffered Service Data Unit (SDU)　for the LC for which time remaining before discardTimer expiry is less than the delay threshold. If an instance of at least one of delay information; and buffer information for a first reporting threshold is reported in a previous transmission of the multi-entry DSR MAC CE, the processor 1102 skips triggering a new DSR when the remaining time for the delay status information falls below a second threshold. If the instance of at least one of delay information; and buffer information for a non-delay-critical data is reported in a previous transmission of the multi-entry DSR MAC CE, the processor 1102 triggers a new DSR if the delay status information becomes delay-critical data.

[0161] If the delay status information is to be reported for more than one delay threshold for at least one LCG, the processor 1102 can trigger an assembly of the multi-entry DSR. The processor 1102 can include non-delay critical data in the multi-entry DSR, if the network has indicated a congestion activation status for a relevant LCG. The processor 1102 does not include non-delay critical data in the multi-entry DSR, if the network has indicated a congestion deactivation status for a relevant LCG. In an embodiment herein, the processor 1102 can report delay information and buffer information associated with the different reporting thresholds in the LCG consecutively in an ascending order based on the values of the reporting thresholds. If the extension bit is set to 1, the processor 1102 can determine that another instance of delay and buffer information for the same LCG is to be included in the multi-entry DSR MAC CE, and includes the another instance of delay and buffer information for the same LCG in the multi-entry DSR MAC CE accordingly. If the extension bit is set to 0, the processor 1102 can determine that another instance of delay and buffer information for the same LCG is not to be included in the MAC CE. The multi-entry DSR MAC CE comprises a bitmap, buffer information and delay information corresponding to each of the delay thresholds for which the delay status information is to be reported; and an extension bit. The bitmap identifies at least one LCG for which delay status information is to be reported. The extension bit is configured to separate delay information and buffer information. The multi-entry DSR MAC CE can be of a variable size CE. The multi-entry DSR MAC CE can be identified by a logical channel identifier (LCID) value set in the MAC sub-header. The variable size CE comprises a variable number of delay information and buffer information for the triggered DSRs corresponding to the satisfied delay thresholds of the configured LCGs. In an embodiment herein, the processor 1102 can perform multi-entry delay status reporting on a per-LC basis.

[0162] The processor 1102 can determine if the UL-SCH resources can accommodate the multi-entry DSR MAC CE, along with the MAC sub-header. If the UL-SCH resources can accommodate the multi-entry DSR MAC CE, along with the MAC sub-header, the processor 1102 can transmit a multi-entry DSR MAC CE, wherein the multi-entry DSR MAC CE includes non-critical data in accordance with the multiple delay thresholds. If the UL-SCH resources cannot accommodate the multi-entry DSR MAC CE, along with the MAC sub-header, the processor 1102 can trigger a scheduling request; i.e., the processor 1102 can transmit a scheduling request to the network.

[0163] In an example use case, consider that the UE 201 supports multi-model XR services. The UE 201 indicates its support for multi-entry DSR to the network; thereby, a multi-modal service can be efficiently scheduled. The UE 201 receives configuration for multi-entry DSR; thereby, multiple delay thresholds pertaining to the multi-modal service can be effectively configured to the UE 201. The UE 201 accounts non-delay critical data present ahead of delay critical data in the buffer; thereby, accurate scheduling is availed for the cumulative data pertaining to the multi-modal services. The UE 201 triggers the multi-entry DSR when one or more delay thresholds are met for multi-modal services. The UE 201 transmits the multi-entry DSR when UL-SCH can completely accommodate the multi-entry DSR MAC CE; otherwise, the UE 201 triggers a scheduling request in order to avail sufficient grant from the network to report the multi-entry DSR MAC CE. The UE 201 is able to satisfactorily operate a multi-modal XR service meeting the diverse scheduling requirements for the synchronization and latency for constituent modes of communication for the multi-modal service (for example, data, audio, video, haptics, and so on).

[0164] Embodiments herein optimize the performance of the UE 201, by preventing unsynchronized scheduling, thereby enhancing user experience. Embodiments herein address 3GPP enhancements for XR applications. Embodiments herein enable effective scheduling for multi-modal communication in dynamic wireless environments for XR. Embodiments herein also perform informed scheduling, as non-delay critical data is also informed; thereby improving scheduling decisions. Embodiments herein enhance the DSR and cater effectively for multi-modal communication.

[0165] According to embodiments, a method for multi-entry delay status reporting in a wireless communication system is provided. The method comprises receiving, by a User Equipment (UE), a configuration from a network, wherein the configuration comprises a multi-entry Delay Status Reporting (DSR) parameters associated with a plurality of delay thresholds for at least one Logical Channel Group (LCG); determining, by the UE, whether delay status information is to be reported for a plurality of delay thresholds for the at least one LCG, on receiving the configuration; triggering, by the UE, a multi-entry DSR procedure, on determining that the delay status information is to be reported for a plurality of delay thresholds; determining, by the UE, whether available uplink shared channel (UL-SCH) resources can accommodate a multi-entry DSR Medium Access Control (MAC) Control Element (CE) and an associated MAC sub-header; transmitting, by the UE, the multi-entry DSR MAC CE in accordance with the multiple delay thresholds, if the available UL-SCH resources can accommodate the multi-entry DSR MAC CE and the associated MAC sub-header; and transmitting, by the UE, a scheduling request to the network if the available UL-SCH resources cannot accommodate the multi-entry DSR MAC CE and the associated MAC sub-header.

[0166] For example, the method comprises indicating, by the UE, whether the UE is capable of supporting the multi-entry DSR to the network in one of Radio Resource Control (RRC) procedures for UE capability information retrieval, and a UE capability information message, wherein the support for the multi-entry DSR is based on at least one of UE implementation; and usage of eXR (Rel-19 enhanced XR) feature.

[0167] For example, the received configuration is indicated for at least one LCG of the UE; and included in a RRC reconfiguration message from the network. The received configuration comprises at least one of the multi-entry DSR reporting; at least one associated triggering threshold; and / or at least one associated reporting threshold; and an indication for one of inclusion or exclusion of non-delay-critical data information in the multi-entry DSR reporting.

[0168] For example, the method comprises including, by the UE, non-delay critical data information in the multi-entry DSR reporting, for a relevant LCG being indicated for inclusion of non-delay critical data information by the network; and not including, by the UE, non-delay critical data in the multi-entry DSR reporting, for a relevant LCG being indicated for exclusion of non-delay critical data information by the network.

[0169] For example, determining, by the UE, whether delay status information is to be reported comprises: checking, by the UE, if delay status information reporting is met for at least one configured delay threshold for the logical channel (LC) pertaining to a configured LCG, which comprises determining if the presence of buffered Service Data Unit (SDU)　for the LC for which time remaining before discardTimer expiry is less than the delay threshold; skipping triggering, by the UE, a new DSR when the remaining time for the delay status information falls below a second threshold, if an instance of at least one of delay information; and buffer information for a first reporting threshold is reported in a previous transmission of the multi-entry DSR MAC CE; and triggering, by the UE, a new DSR if the delay status information becomes delay-critical data, if the instance of at least one of delay information; and buffer information for a non-delay-critical data is reported in a previous transmission of the multi-entry DSR MAC CE.

[0170] For example, assembling the multi-entry DSR MAC CE comprises: identifying, by the UE, the multi-entry DSR MAC CE using a LCID value, wherein the LCID value in MAC sub-header of the multi-entry DSR MAC CE in the MAC PDU is set to be transmitted in an Uplink (UL) direction; inserting, by the UE, a bitmap for indicating LCGs and a set of delay information and buffer information pertaining to each of the satisfied delay thresholds for LCGs which are to be reported, wherein a bit is set to 1 for the LCG for which multi-entry DSR is to be reported, otherwise the bit is set to 0; and inserting and setting, by the UE, an extension bit to separate each set of delay information and buffer information.

[0171] For example, the method comprises reporting, by the UE, delay information and buffer information associated with the different reporting thresholds in the LCG consecutively in ascending order based on the values of the reporting thresholds.

[0172] For example, the method comprises: determining, by the UE, that another instance of delay and buffer information for the same LCG is included in the MAC CE, when the extension bit is set to 1; and determining, by the UE, that another instance of delay and buffer information for the same LCG is not included in the MAC CE, when the extension bit is set to 0.

[0173] For example, the multi-entry DSR MAC CE comprises: a bitmap identifying at least one LCG for which delay status information is to be reported; buffer information and delay information corresponding to each of the delay thresholds for which the delay status information is to be reported; and the extension bit configured to separate delay information and buffer information. The multi-entry DSR MAC CE is a variable size CE, and is identified by a logical channel identifier (LCID) value set in the MAC sub-header, wherein the variable size CE comprises a variable number of delay information and buffer information for the triggered DSRs corresponding to the satisfied delay thresholds of the configured LCGs.

[0174] For example, the multi-entry delay status reporting is performed on a per-LC basis.

[0175] For example, UE may indicate support (or no support) for multi-entry DSR to the network in a UE capability information message.

[0176] According to embodiments, a User Equipment (UE) is provided. The UE comprises a processor; a transceiver; and a memory. The processor is coupled with the transceiver, and the memory, and configured to receive a configuration from a network, wherein the configuration comprises multi-entry Delay Status Reporting (DSR) parameters associated with a plurality of delay thresholds for at least one Logical Channel Group (LCG); determine whether delay status information is to be reported for a plurality of delay thresholds for the at least one LCG, on receiving the configuration; trigger a multi-entry DSR procedure, on determining that the delay status information is to be reported for a plurality of delay thresholds; determine whether available uplink shared channel (UL-SCH) resources can accommodate a multi-entry DSR Medium Access Control (MAC) Control Element (CE) and an associated MAC sub-header; transmit the multi-entry DSR MAC CE in accordance with the multiple delay thresholds, if the available UL-SCH resources can accommodate the multi-entry DSR MAC CE and the associated MAC sub-header; and transmit a scheduling request to the network if the available UL-SCH resources cannot accommodate the multi-entry DSR MAC CE and the associated MAC sub-header.

[0177] According to embodiments, a method performed by a user equipment (UE) is provided. The method comprises receiving, from a network node, a radio resource control (RRC) configuration message including a delay status reporting (DSR) configuration of each logical channel group (LCG), the DSR configuration including a triggering threshold and one or more reporting threshold; after at least one DSR is triggered based on the triggering threshold, determining whether uplink shared channel (UL-SCH) resources can accommodate a DSR medium access control (MAC) control element (CE) plus subheader; in accordance with a determination that the UL-SCH resources can accommodate the DSR MAC CE plus the subheader, generating the DSR MAC CE; and transmitting a MAC protocol data unit (PDU) including the DSR MAC CE to the network node. The DSR MAC CE includes an instance associated with each threshold included in one more reporting threshold of each of one or more LCGs. For each of the one or more LCG and each threshold, the instance includes a remaining time associated with a corresponding reporting threshold of a corresponding LCG, and a buffer size associated with the corresponding reporting threshold of the corresponding LCG.

[0178] For example, the DSR MAC CE is identified by the sub-header with an extended logical channel identity (eLCID). The eLCID indicates a type of DSR MAC CE using the one or more reporting threshold.

[0179] For example, for each of the one or more LCG and each threshold, the instance includes an extension field. The extension field indicates whether a next remaining time and a next buffer size are followed by the remaining time and the buffer size or not.

[0180] For example, for each LCG, the triggering threshold is higher than a lowest reporting threshold of the ne or more reporting threshold.

[0181] For example, the DSR MAC CE includes a bitmap including bits corresponding to LCGs. Each of the bits indicates whether an instance for a corresponding LCG are reported or not reported.

[0182] For example, whether non-delay critical data related information is included in the DSR MAC CE or not is determined based on an indication received from the network node.

[0183] For example, the method comprises transmitting capability information to the network node. The capability information indicating that the UE supports the DSR MAC CE using the one or more reporting threshold.

[0184] For example, a method performed by a network node is provided. The method comprises transmitting, to a user equipment (UE), a radio resource control (RRC) configuration message including a delay status reporting (DSR) configuration of each logical channel group (LCG), the DSR configuration including a triggering threshold and one or more reporting threshold; in a case that at least one DSR is triggered based on the triggering threshold and uplink shared channel (UL-SCH) resources can accommodate a DSR medium access control (MAC) control element (CE) plus subheader, receiving a MAC protocol data unit (PDU) including the DSR MAC CE from the UE. The DSR MAC CE includes an instance associated with each threshold included in one more reporting threshold of each of one or more LCGs. For each of the one or more LCG and each threshold, the instance includes a remaining time associated with a corresponding reporting threshold of a corresponding LCG, and a buffer size associated with the corresponding reporting threshold of the corresponding LCG.

[0185] For example, the DSR MAC CE is identified by the sub-header with an extended logical channel identity (eLCID). The eLCID indicates a type of DSR MAC CE using the one or more reporting threshold.

[0186] For example, for each of the one or more LCG and each threshold, the instance includes an extension field. The extension field indicates whether a next remaining time and a next buffer size are followed by the remaining time and the buffer size or not.

[0187] For example, for each LCG, the triggering threshold is higher than a lowest reporting threshold of the ne or more reporting threshold.

[0188] For example, the DSR MAC CE includes a bitmap including bits corresponding to LCGs. Each of the bits indicates whether an instance for a corresponding LCG are reported or not reported.

[0189] For example, whether non-delay critical data related information is included in the DSR MAC CE or not is determined based on an indication provided from the network node.

[0190] For example, the method comprises receiving capability information from the UE. The capability information indicating that the UE supports the DSR MAC CE using the one or more reporting threshold.

[0191] According to embodiments, a user equipment (UE) is provided. The UE comprises at least one transceiver; at least one processor; and memory storing instructions that, when executed by the at least one processor, cause the at least one processor to receive, from a network node via the at least one transceiver, a radio resource control (RRC) configuration message including a delay status reporting (DSR) configuration of each logical channel group (LCG), the DSR configuration including a triggering threshold and one or more reporting threshold; after at least one DSR is triggered based on the triggering threshold, determining whether uplink shared channel (UL-SCH) resources can accommodate a DSR medium access control (MAC) control element (CE) plus subheader; in accordance with a determination that the UL-SCH resources can accommodate the DSR MAC CE plus the subheader, generate the DSR MAC CE; and transmit a MAC protocol data unit (PDU) including the DSR MAC CE to the network node via the at least one transceiver. The DSR MAC CE includes an instance associated with each threshold included in one more reporting threshold of each of one or more LCGs. For each of the one or more LCG and each threshold, the instance includes a remaining time associated with a corresponding reporting threshold of a corresponding LCG, and a buffer size associated with the corresponding reporting threshold of the corresponding LCG.

[0192] According to embodiments, a network node is provided. The network node comprises at least one transceiver; at least one processor; and memory storing instructions that, when executed by the at least one processor, cause the at least one processor to transmit, to a user equipment (UE), a radio resource control (RRC) configuration message including a delay status reporting (DSR) configuration of each logical channel group (LCG), the DSR configuration including a triggering threshold and one or more reporting threshold; and in a case that at least one DSR is triggered based on the triggering threshold and uplink shared channel (UL-SCH) resources can accommodate a DSR medium access control (MAC) control element (CE) plus subheader, receive a MAC protocol data unit (PDU) including the DSR MAC CE from the UE. The DSR MAC CE includes an instance associated with each threshold included in one more reporting threshold of each of one or more LCGs. For each of the one or more LCG and each threshold, the instance includes a remaining time associated with a corresponding reporting threshold of a corresponding LCG, and a buffer size associated with the corresponding reporting threshold of the corresponding LCG.

[0193] Meanwhile, although specific embodiments of the present disclosure have been described in detail, various modifications may be made without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims and equivalents thereof.

[0194] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of embodiments and examples, those skilled in the art will recognize that the embodiments and examples disclosed herein can be practised with modification within the scope of the embodiments as described herein.

Claims

1.A method performed by a user equipment (UE), the method comprising:receiving, from a network node, a radio resource control (RRC) configuration message including a delay status reporting (DSR) configuration of each logical channel group (LCG), the DSR configuration including a triggering threshold and one or more reporting threshold;after at least one DSR is triggered based on the triggering threshold, determining whether uplink shared channel (UL-SCH) resources can accommodate a DSR medium access control (MAC) control element (CE) plus subheader;in accordance with a determination that the UL-SCH resources can accommodate the DSR MAC CE plus the subheader, generating the DSR MAC CE; andtransmitting a MAC protocol data unit (PDU) including the DSR MAC CE to the network node,wherein the DSR MAC CE includes an instance associated with each threshold included in one more reporting threshold of each of one or more LCGs, andwherein, for each of the one or more LCG and each threshold, the instance includes:a remaining time associated with a corresponding reporting threshold of a corresponding LCG, anda buffer size associated with the corresponding reporting threshold of the corresponding LCG.2.The method of claim 1,wherein the DSR MAC CE is identified by the sub-header with an extended logical channel identity (eLCID), andwherein the eLCID indicates a type of DSR MAC CE using the one or more reporting threshold.3.The method of claim 1,wherein, for each of the one or more LCG and each threshold, the instance includes an extension field, andwherein the extension field indicates whether a next remaining time and a next buffer size are followed by the remaining time and the buffer size or not.4.The method of claim 1,wherein, for each LCG, the triggering threshold is higher than a lowest reporting threshold of the ne or more reporting threshold.5.The method of claim 1,wherein the DSR MAC CE includes a bitmap including bits corresponding to LCGs, andwherein each of the bits indicates whether an instance for a corresponding LCG are reported or not reported.6.The method of claim 1, wherein whether non-delay critical data related information is included in the DSR MAC CE or not is determined based on an indication received from the network node.7.The method of claim 1, further comprising:transmitting capability information to the network node,wherein the capability information indicating that the UE supports the DSR MAC CE using the one or more reporting threshold.8.A method performed by a network node, the method comprising:transmitting, to a user equipment (UE), a radio resource control (RRC) configuration message including a delay status reporting (DSR) configuration of each logical channel group (LCG), the DSR configuration including a triggering threshold and one or more reporting threshold; andin a case that at least one DSR is triggered based on the triggering threshold and uplink shared channel (UL-SCH) resources can accommodate a DSR medium access control (MAC) control element (CE) plus subheader, receiving a MAC protocol data unit (PDU) including the DSR MAC CE from the UE,wherein the DSR MAC CE includes an instance associated with each threshold included in one more reporting threshold of each of one or more LCGs, andwherein, for each of the one or more LCG and each threshold, the instance includes:a remaining time associated with a corresponding reporting threshold of a corresponding LCG, anda buffer size associated with the corresponding reporting threshold of the corresponding LCG.9.The method of claim 8,wherein the DSR MAC CE is identified by the sub-header with an extended logical channel identity (eLCID), andwherein the eLCID indicates a type of DSR MAC CE using the one or more reporting threshold.10.The method of claim 8,wherein, for each of the one or more LCG and each threshold, the instance includes an extension field, andwherein the extension field indicates whether a next remaining time and a next buffer size are followed by the remaining time and the buffer size or not.11.The method of claim 8,wherein, for each LCG, the triggering threshold is higher than a lowest reporting threshold of the ne or more reporting threshold.12.The method of claim 8,wherein the DSR MAC CE includes a bitmap including bits corresponding to LCGs, andwherein each of the bits indicates whether an instance for a corresponding LCG are reported or not reported.13.The method of claim 8, wherein whether non-delay critical data related information is included in the DSR MAC CE or not is determined based on an indication provided from the network node.14.The method of claim 8, further comprising:receiving capability information from the UE,wherein the capability information indicating that the UE supports the DSR MAC CE using the one or more reporting threshold.15.A user equipment (UE) comprising:at least one transceiver;at least one processor; andmemory storing instructions that, when executed by the at least one processor, cause the at least one processor to:receive, from a network node via the at least one transceiver, a radio resource control (RRC) configuration message including a delay status reporting (DSR) configuration of each logical channel group (LCG), the DSR configuration including a triggering threshold and one or more reporting threshold;after at least one DSR is triggered based on the triggering threshold, determining whether uplink shared channel (UL-SCH) resources can accommodate a DSR medium access control (MAC) control element (CE) plus subheader;in accordance with a determination that the UL-SCH resources can accommodate the DSR MAC CE plus the subheader, generate the DSR MAC CE; andtransmit a MAC protocol data unit (PDU) including the DSR MAC CE to the network node via the at least one transceiver,wherein the DSR MAC CE includes an instance associated with each threshold included in one more reporting threshold of each of one or more LCGs, andwherein, for each of the one or more LCG and each threshold, the instance includes:a remaining time associated with a corresponding reporting threshold of a corresponding LCG, anda buffer size associated with the corresponding reporting threshold of the corresponding LCG.

Images