Managing delay status reporting for an extended reality in a communication network system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. This patent application relates to a method for managing Delay Status Reporting (DSR) for an extended reality (XR) in a communication network system. The method includes receiving, from a network entity, via Radio Resource Control (RRC) signaling, information on Delay Status Reporting (DSR) configuration including an identifier of a Logical Channel Group (LCG) and a remaining time threshold parameter; based on the remaining time threshold parameter, determining whether each logical channel within the LCG satisfies DSR triggering conditions; and triggering the DSR for each logical channel within the LCG that satisfies the DSR triggering conditions.

Description

MANAGING DELAY STATUS REPORTING FOR AN EXTENDED REALITY IN A COMMUNICATION NETWORK SYSTEM

[0001] The present disclosure is related to wireless communication. More particularly, the present disclosure is related to managing Delay Status Reporting (DSR) for an extended reality (XR) in a communication network system.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] The principal object of the embodiments herein is to provide a method for managing Delay Status Reporting (DSR) for an extended reality (XR) in a communication network system.

[0009] Another object of the present disclosure is to provide a method and system for triggering an SR for the DSR for the XR in communication network system.

[0010] Yet another object of the present disclosure is to provide a method and system for a DSR triggering mechanism for XR in communication network system.

[0011] In an aspect, the objectives are achieved by providing a method for managing DSR for an XR in a communication network system. The method includes receiving by a User Equipment (UE) a DSR configuration per LCG from a network apparatus. Further, the method includes configuring by the UE the DSR for the XR based on the DSR configuration. Further, the method includes triggering by the UE a separate SR for each of the logical channels of the LCG that triggered the DSR based on the configured DSR per LCG. Further, the method includes using by the UE the separate SR based on the SR configuration of each of the logical channels of the LCG that triggered the DSR.

[0012] In an aspect, the objectives are achieved by providing a UE for managing DSR for an XR in a communication network system. The UE includes a memory, a processor, and a DSR configuration controller coupled to the memory and the processor. Further, the DSR configuration controller is configured to receive a DSR configuration per LCG from a network apparatus. Further, the DSR configuration controller configures the DSR for the XR based on the DSR configuration. Further, the DSR configuration controller is configured to trigger a separate SR for each of the logical channels of the LCG that triggered the DSR based on the configured DSR per LCG. Further, the DSR configuration controller uses the separate SR based on the SR configuration of each of the logical channels of the LCG that triggered the DSR.

[0013] The following description and accompanying drawings will enhance the understanding of these and other aspects of the embodiments. While the descriptions indicate preferred embodiments and specific details, they are provided for illustration purposes only and not as limitations. Many changes and modifications can be made within the scope of these embodiments.

[0014] The features and advantages of the present embodiments are illustrated in the accompanying drawings, where like reference letters indicate corresponding parts. The embodiments will be better understood from the following description with reference to the drawings.

[0015] FIG. 1 is a block diagram of a UE for managing DSR for XR in a communication network system according to embodiments as disclosed herein.

[0016] FIG. 2 is a flowchart that illustrates a method for managing DSR for XR in a communication network system according to embodiments as disclosed herein.

[0017] FIG. 3 is a flowchart that illustrates a working operation of an enhanced DSR handling mechanism at a MAC entity of the UE for the extended reality in the communication network system according to embodiments as disclosed herein.

[0018] FIG. 4 is a flowchart that illustrates the enhanced DSR handling mechanism at the MAC entity of the UE for extended reality in the communication network system according to other embodiments as disclosed herein.

[0019] FIG. 5 is a flowchart that illustrates a DSR triggering mechanism at the MAC entity of the UE for XR in the communication network system according to embodiments as disclosed herein.

[0020] FIG. 6 is a block diagram of a network entity for managing DSR for XR in a communication network system according to embodiments as disclosed herein.

[0021] FIG. 7 is a flowchart that illustrates a method of the UE for managing DSR for XR in a communication network system according to embodiments as disclosed herein.

[0022] FIG. 8 is a flowchart that illustrates a method of the network entity for managing DSR for XR in a communication network system according to embodiments as disclosed herein.

[0023] In one embodiment, a method performed by a UE in a wireless communication system is provided. The method comprising: receiving, from a network entity, via Radio Resource Control (RRC) signaling, information on Delay Status Reporting (DSR) configuration including an identifier of a Logical Channel Group (LCG) and a remaining time threshold parameter; and based on the remaining time threshold parameter, determining whether each logical channel within the LCG satisfies DSR triggering conditions; and triggering the DSR for each logical channel within the LCG that satisfies the DSR triggering conditions.

[0024] In one embodiment, the method, further comprising: determining that a smallest remaining value among running Packet Data Convergence Protocol (PDCP) discard timers for PDCP Service Data Units (PDCP SDUs), buffered for a logical channel within the LCG, that have not been transmitted in any Medium Access Control Protocol Data Unit (MAC PDU) and have not been reported as data volume in a DSR MAC Control Element (MAC CE), becomes below the remaining time threshold parameter; determining that there is no DSR pending for the logical channel; and triggering the DSR for the logical channel.

[0025] In one embodiment, the method, further comprising: determining at least one DSR pending; determining that UL-SCH resources are not available for a new transmission or the UL-SCH resources cannot accommodate a DSR MAC CE and a subheader of the DSR MAC CE as a result of logical channel prioritization; determining that there is no pending SR already triggered by a DSR procedure for the logical channel that triggered the DSR; and triggering the SR for the logical channel that triggered the DSR.

[0026] In one embodiment, the method, wherein a SR configuration of the logical channel that triggered the DSR is considered as corresponding SR configuration for the triggered SR.

[0027] In one embodiment, the method, further comprising: determining at least one DSR pending; determining that UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate a DSR MAC CE and a subheader of the DSR MAC CE as a result of logical channel prioritization; and instructing a Multiplexing and Assembly procedure to generate the DSR MAC CE.

[0028] In one embodiment, a method performed by a network entity in a wireless communication system is provided. The method comprising: transmitting, to a User Equipment (UE), via Radio Resource Control (RRC) signaling, information on Delay Status Reporting (DSR) configuration including an identifier of a Logical Channel Group (LCG) and a remaining time threshold parameter, wherein, based on the remaining time threshold parameter, whether each logical channel within the LCG satisfies DSR triggering conditions is determined, and wherein a DSR is triggered for each logical channel within the LCG that satisfies the DSR triggering conditions.

[0029] In one embodiment, the method, wherein, in case that a smallest remaining value among running Packet Data Convergence Protocol (PDCP) discard timers for PDCP Service Data Units (PDCP SDUs), buffered for a logical channel within the LCG, that have not been transmitted in any Medium Access Control Protocol Data Unit (MAC PDU) and have not been reported as data volume in a DSR MAC Control Element (MAC CE), becomes below the remaining time threshold parameter, and in case that there is no DSR pending for the logical channel, the DSR is triggered for the logical channel.

[0030] In one embodiment, a UE (user equipment) in a wireless communication system is provided. The UE comprising: memory stored one or more instructions; and at least one processor configure to execute the one or more instructions stored in the memory to: receive, from a network entity, via Radio Resource Control (RRC) signaling, information on Delay Status Reporting (DSR) configuration including an identifier of a Logical Channel Group (LCG) and a remaining time threshold parameter; and based on the remaining time threshold parameter, trigger a DSR for each logical channel within the LCG.

[0031] In one embodiment, the at least one processor further configure to execute the one or more instructions stored in the memory to: determine that a smallest remaining value among running Packet Data Convergence Protocol (PDCP) discard timers for PDCP Service Data Units (PDCP SDUs), buffered for a logical channel within the LCG, that have not been transmitted in any Medium Access Control Protocol Data Unit (MAC PDU) and have not been reported as data volume in a DSR MAC Control Element (MAC CE), becomes below the remaining time threshold parameter; determine that there is no DSR pending for the logical channel; and trigger the DSR for the logical channel within the LCG.

[0032] In one embodiment, the at least one processor further configure to execute the one or more instructions stored in the memory to: determine at least one DSR pending; determine that UL-SCH resources are not available for a new transmission or the UL-SCH resources cannot accommodate a DSR MAC CE and a subheader of the DSR MAC CE as a result of logical channel prioritization; determine that there is no pending SR already triggered by a DSR procedure for the logical channel that triggered the DSR; and trigger the SR for the logical channel that triggered the DSR.

[0033] In one embodiment, the UE, wherein a SR configuration of the logical channel that triggered the DSR is considered as corresponding SR configuration for the triggered SR.

[0034] In one embodiment, the at least one processor further configure to execute the one or more instructions stored in the memory to: determine at least one DSR pending; determine that UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate a DSR MAC CE and a subheader of the DSR MAC CE as a result of logical channel prioritization; and instruct a Multiplexing and Assembly procedure to generate the DSR MAC CE.

[0035] In one embodiment, a network entity in a wireless communication system is provided. The network entity comprising: memory stored one or more instructions; and at least one processor configure to execute the one or more instructions stored in the memory to: transmit, to a User Equipment (UE), via Radio Resource Control (RRC) signaling, information on Delay Status Reporting (DSR) configuration including an identifier of a Logical Channel Group (LCG) and a remaining time threshold parameter, wherein, based on the remaining time threshold parameter, whether each logical channel within the LCG satisfies DSR triggering conditions is determined, and wherein a DSR is triggered for each logical channel within the LCG that satisfies the DSR triggering conditions.

[0036] In one embodiment, the network entity, wherein, in case that a smallest remaining value among running Packet Data Convergence Protocol (PDCP) discard timers for PDCP Service Data Units (PDCP SDUs), buffered for a logical channel within the LCG, that have not been transmitted in any Medium Access Control Protocol Data Unit (MAC PDU) and have not been reported as data volume in a DSR MAC Control Element (MAC CE), becomes below the remaining time threshold parameter, and in case that there is no DSR pending for the logical channel, the DSR is triggered for the logical channel.

[0037] 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. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. The term "or" as used herein, refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples are not be construed as limiting the scope of the embodiments herein.

[0038] As is existing in the field, embodiments are described and illustrated in terms of blocks that carry out a described function or functions.　These blocks, which 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 optionally be driven by firmware and software. The circuits, 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 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 be physically separated into two or more interacting and discrete blocks without departing from the scope of the proposed method.　Likewise, the blocks of the embodiments be physically combined into more complex blocks without departing from the scope of the proposed method.

[0039] Extended Reality (XR) technology, encompassing Virtual Reality (VR), Augmented Reality (AR), and Mixed Reality (MR), is rapidly evolving. These XR technologies are integrated into the 5G Advanced framework (3GPP Release 18), which aims to provide a communication network system that meets the demanding requirements of high data rates, low latency, and power-efficient connectivity for XR applications.

[0040] In the context of 5G networks, the Protocol Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Medium Access Control (MAC) sub-layers are used in the data plane for the processing of transmitted and received packets. Traditionally, the Buffer Status Report (BSR) procedure has been used to communicate the status of buffered data, such as the size of the buffered data, across different Logical Channel Groups (LCGs). This information is used for the network's scheduling operations, allowing the network to allocate uplink grants to User Equipment (UE) to serve the buffered data.

[0041] However, the BSR procedure lacks information on the delay status of the buffered data. This is problematic because the buffered data, (e.g., for the XR applications and services) may have been stored at different times, leading to varying delay statuses. Moreover, different services have different packet delay budgets, meaning that buffered data (e.g., a packet or Service Data Unit (SDU)) is subject to being discarded if it exceeds the packet delay budget limit or any other configured limit. The SDU discard procedure involves discarding a PDCP SDU when its associated timer expires or when the successful delivery of the PDCP SDU is confirmed by a peer PDCP entity, such as through a PDCP status report.

[0042] For XR applications, the existing buffer status reporting mechanisms may not be efficient or effective due to the extreme delay sensitivity and low latency requirements of these applications. As a result, a Delay Status Report (DSR) mechanism has been introduced, which includes both delay information and pertinent buffered data information. This enables the network to perform better scheduling for XR applications.

[0043] However, the existing DSR mechanism (as described in 3GPP TS 38321 v1800) presents several challenges and inefficiencies. These include redundant multiple transmissions for a Scheduling Request (SR) for the same DSR or DSRs belonging to the same Logical Channel Group, and ineffective triggering of SRs for the DSR. These issues can lead to ambiguities and inefficiencies in the network's scheduling operations, affecting the performance and user experience of XR applications.

[0044] Thus, it is desired to address the above-mentioned disadvantages, issues, or other shortcomings or at least provide a useful alternative.

[0045] Embodiments disclosed herein provide a system and method for the DSR handling for the XR in a communication network system. In an embodiment, the MAC entity of the UE triggers the SR for the DSR when the Uplink-Shared Channel (UL-SCH) resources are not available for a new transmission or the UL-SCH resources cannot accommodate the DSR MAC CE plus its sub-header as a result of logical channel prioritization, and there is no pending SR already triggered by the DSR procedure for a logical channel belonging to the LCG as of this DSR.

[0046] In an embodiment, the MAC entity of the UE triggers the SR of the logical channel for the LCG for which the PDCP SDU with the smallest remaining value of the PDCP discardTimers among all the data buffered for the (all) the logical channels of the LCG that has not been transmitted in any MAC PDU or reported as data volume in the DSR MAC CE becomes below the remainingTimeThreshold of the LCG when the DSR was triggered, and the UL-SCH resources are not available for the new transmission, or the UL-SCH resources cannot accommodate the DSR MAC CE plus its sub-header as a result of logical channel prioritization.

[0047] In existing methods for the DSR mechanism (i.e., 3GPP TS 38.321 v18.00), there are two primary drawbacks. Firstly, the DSR mechanism may lead to some ambiguities or inefficiencies, such as redundant multiple transmissions for the Scheduling Request for the same DSR or DSR belonging to the same Logical Channel Group. Secondly, the SR for the DSR may not be effectively triggered. These inefficiencies can result in suboptimal performance, particularly in scenarios requiring precise and timely data transmission, such as XR applications.

[0048] The proposed solution addresses the limitations of existing DSR mechanisms by ensuring that the DSR is triggered more effectively and efficiently. This is particularly important for XR applications, where latency and timely data transmission are used for maintaining a seamless user experience. By optimizing the DSR handling mechanism, the solution can reduce redundant transmissions and ensure that the SR for DSR is triggered when necessary, thereby improving the overall performance of the communication network system.

[0049] Furthermore, the enhanced DSR handling mechanism provided by the embodiments disclosed herein can be integrated with existing communication network system infrastructure, ensuring compatibility and ease of implementation. This approach improves the efficiency of data transmission for the XR applications and enhances the overall reliability and performance of the communication network system. The proposed solution ensures that the network can handle the high data rates and low latency requirements of XR applications, providing a better user experience and supporting the growing demand for advanced wireless communication technologies.

[0050] FIG. 1 is the block diagram of the UE (101) for managing the DSR for the XR in the communication network system, according to embodiments as disclosed herein.

[0051] Examples of the UE (101) can include, but are not limited to, Consumer Electronics (such as Mobile Phones and Smartphones), Tablets, Wearable Devices, Television, Computing Devices (such as Laptops, Notebooks, Desktops, Workstations, etc.), IoT Devices, Automotive Systems (such as connected cars, Autonomous Vehicles, Vehicle-to-Everything (V2X) communication devices, etc.), Enterprise Devices such as robotics, Specialized Equipment (such as Medical Devices, Public Safety Devices, etc.), Media Devices (such as Gaming Consoles, Streaming Devices, etc.).

[0052] Examples of the wireless communication network system include, but are not limited to, Cellular Networks (such as 2G, 3G, 4G, 5G, Beyond 5G (B5G) / 6G, or advanced cellular networks), Local Area Networks (LANs) (such as Wi-Fi, Li-Fi, etc.), Personal Area Networks (PANs) (such as Bluetooth, Zigbee, Z-Wave, etc.), Wide Area Networks (WANs) (such as Satellite Communication Networks, Long Range Wide Area Network, Narrowband IoT, Low-bandwidth communication for IoT, etc.), Metropolitan Area Networks (MANs), Machine-to-Machine (M2M), Ad Hoc and Mesh Networks, Emerging and Advanced Networks.

[0053] The UE (101) includes the processor (102), the memory (103), the communicator (104), and a DSR Configuration controller (105). For example, the UE (101) can include, but is not limited to, a mobile phone, a smartphone, tablets, laptops, Internet of Things (IoT) devices. The processor (102) communicates with the memory (103), the communicator (104) and the DSR configuration controller (105).

[0054] The processor (102) is configured to execute instructions stored in the memory (104) and to perform various processes. The processor (102) can include one or a plurality of processors, can be a general-purpose processor such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an artificial intelligence (AI) dedicated processor such as a neural processing unit (NPU).

[0055] The at least one processor (102) is configured for performing one or more operations, for example according to the operations as described in the present disclosure. The processor (102) may execute one or more instructions stored in the memory (103) to operation as described in the present disclosure.

[0056] The at least one processor (102) may include various processing circuitry and / or multiple processors. For example, as used herein, including the claims, the term "processor" may include various processing circuitry, including at least one processor, wherein one or more of at least one processor, individually and / or collectively in a distributed manner, may be configured to perform various functions described herein. As used herein, when "a processor", "at least one processor", and "one or more processors" are described as being configured to perform numerous functions, these terms cover situations, for example and without limitation, in which one processor performs some of recited functions and another processor(s) performs other of recited functions, and also situations in which a single processor may perform all recited functions. Additionally, the at least one processor may include a combination of processors performing various of the recited / disclosed functions, e.g., in a distributed manner. At least one processor may execute program instructions to achieve or perform various functions.

[0057] Further, the memory (103) of the UE (101) includes storage locations to be addressable through the processor (102). The memory (103) is not limited to a volatile memory and / or a non-volatile memory. Further, the memory (103) can include one or more computer-readable storage media. The memory (103) can include non-volatile storage elements. For example, non-volatile storage elements can include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (103) may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (103) is non-movable. In some examples, the memory (103) can be configured to store larger amounts of information than the memory. In an example, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0058] The communicator (104) is configured for communicating internally between internal hardware components and with external devices (client device) via one or more networks. The communicator (104) includes an electronic circuit that enables wired or wireless communication.

[0059] The DSR configuration controller (105) is configured to receive the DSR configuration per LCG from the network apparatus. Additionally, the DSR configuration controller (105) configures the DSR for the XR based on the DSR configuration. Furthermore, the DSR configuration controller (105) triggers the separate SR for each of the logical channels of the LCG that triggered the DSR based on the configured DSR per LCG. The separate SR is used by the DSR configuration controller (105) based on the SR configuration of each of the logical channels of the LCG that triggered the DSR.

[0060] In the UE (101), the DSR configuration controller (105) is configured to trigger the separate SR for each of the logical channels of the LCG that triggered the DSR based on the configured DSR per LCG. Moreover, the DSR configuration controller (105) configures the LCG for the DSR based on the DSR configuration. The logical channel of the plurality of logical channels of the LCG, which is having the smallest remaining value of the running PDCP discard timers among all PDCP SDUs buffered for the logical channel that have not been transmitted in any MAC PDU and have not been reported as data volume in a DSR MAC-CE, is detected by the DSR configuration controller (105). When the smallest remaining value falls below a remaining time threshold of the LCG, the DSR configuration controller (105) triggers the DSR for the detected logical channel of the LCG.

[0061] The DSR configuration controller (105) is also configured to determine whether the Uplink Shared Channel (UL-SCH) resources are not available for the new transmission or cannot accommodate the DSR MAC-CE plus its sub-header as a result of logical channel prioritization, the DSR configuration controller (105) triggers the the SR for the pending DSR on the detected logical channel of the LCG. The SR configuration of the detected logical channel is considered as the corresponding SR configuration for the triggered SR for the DSR.

[0062] The DSR configuration in the UE (101) includes the logical channel group identifier (lcg-Id) and the remaining time threshold parameter. The DSR configuration controller (105) in the UE (101) determines the pending DSR. The DSR configuration controller (105) in the UE (101) triggers the DSR. Upon triggering, the DSR configuration controller (105) in the UE (101) considers the DSR as pending. . The DSR configuration controller (105) maintains the DSR in the pending state until the DSR is cancelled.

[0063] When configured to detect the DSR triggering event for multiple logical channels of the LCG, the DSR configuration controller (105) in the UE (101) determines that UL-SCH resources are unavailable for the new transmission or that the UL-SCH resources cannot accommodate the DSR MAC-CE and its sub-header as a result of logical channel prioritization. The DSR configuration controller (105) triggers a separate SR for each of the logical channels of the LCG that triggered the DSR.

[0064] The DSR configuration controller (105) in the UE (101) is configured to determine whether UL-SCH resources are available for the new transmission and if the UL-SCH resources can accommodate the DSR MAC-CE and its sub-header as a result of logical channel prioritization. When the UL-SCH resources are available and can accommodate the DSR MAC-CE and its sub-header, the DSR configuration controller (105) instructs the Multiplexing and Assembly procedure to generate the DSR MAC-CE. If the UL-SCH resources are not available or cannot accommodate the DSR MAC-CE and its sub-header, the DSR configuration controller (105) triggers the SR, provided there is no pending SR already triggered by the DSR procedure for the same logical channel as the pending DSR.

[0065] The UE (101) ensures separate DSRs for each of the logical channels of the LCG that triggered the DSR based on the configured DSR per LCG. The UE (101) configures the LCG for the DSR based on the DSR configuration. Additionally, the UE (101) detects the logical channel of the plurality of logical channels of the LCG having the smallest remaining value of a running PDCP discard timers among all PDCP SDUs buffered for the logical channel that have not been transmitted in any MAC PDU and have not been reported as data volume in a DSR MAC-CE. When the smallest remaining value falls below the remaining time threshold of the LCG, the UE (101) triggers the DSR for the detected logical channel.

[0066] The UE (101) determines when UL-SCH resources are not available for a new transmission or the UL-SCH resources cannot accommodate the DSR MAC-CE plus its sub-header due to logical channel prioritization. In such cases, the UE (101) triggers the SR at the MAC entity. The UE (101) ensures that the SR for a pending DSR on the detected logical channel of the LCG, wherein a SR configuration of the detected logical channel is considered as the corresponding SR configuration for the triggered SR for the DSR.

[0067] The DSR configuration includes the lcg-Id and the remaining time threshold parameter. The DSR configuration controller (105) in the UE (101) determines the pending DSR. The DSR configuration controller (105 triggers the DSR. The DSR configuration controller (105) considers the DSR as pending upon triggering and maintains the DSR in the pending state until the DSR is cancelled.

[0068] The UE (101) detects the DSR triggering event for multiple logical channels of the LCG. Additionally, the UE (101) determines that UL-SCH resources are unavailable for the new transmission or that the UL-SCH resources cannot accommodate the DSR MAC-CE and its sub-header as a result of logical channel prioritization. Consequently, the UE (101) triggers a separate SR for each of the logical channels of the LCG that triggered the DSR.

[0069] The UE (101) further determines whether the UL-SCH resources are available for the new transmission and if the UL-SCH resources can accommodate the DSR MAC-CE and its sub-header as a result of logical channel prioritization. When the UL-SCH resources are available and can accommodate the DSR MAC-CE and its sub-header, the UE (101) instructs the Multiplexing and Assembly procedure to generate the DSR MAC-CE. The UE (101) triggers the SR when there is no pending SR already triggered by the DSR procedure for the same logical channel as the configured DSR, and when the UL-SCH resources are not available or cannot accommodate the DSR MAC-CE and its sub-header.

[0070] In an embodiment, the DSR configuration controller (105) triggers the SR for DSR when the UL-SCH resources are not available for the new transmission or the UL-SCH resources cannot accommodate the DSR MAC-CE plus its sub-header as a result of logical channel prioritization, and there is no pending SR already triggered by the DSR procedure for the same logical channel belonging to the LCG as of this DSR.

[0071] FIG. 2 is a flowchart that illustrates a method for managing DSR for an XR in a communication network system according to embodiments as disclosed herein. At block 201, the UE (101) receives the DSR configuration per LCG from the network apparatus. The DSR configuration received from the network apparatus includes parameters and settings that guide the UE (101) in managing delay status reporting efficiently.

[0072] At block 202, the UE (101) configures the DSR for the XR based on the DSR configuration. The UE (101) interprets the received configuration and applying it to its internal settings. The configuration process ensures that the UE (101) is aligned with the network's expectations and can handle delay status reporting in a manner that optimizes performance and resource utilization.

[0073] At block 203, the UE (101) triggers the separate SR for each of the logical channels of the LCG that triggered the DSR based on the configured DSR per LCG. This triggering mechanism is a response to the UE (101)'s need to communicate its data scheduling requirements via delay status reporting to the network. By triggering separate or multiple SRs, the UE (101) can request the necessary resources to handle the data traffic associated with XR applications. This maintains the quality of service and ensuring that the UE (101) can meet the demands of XR applications.

[0074] At block 204, the UE (101) configures the separate SR based on an SR configuration of each of the logical channels of the LCG that triggered the DSR. The UE (101) sets up the SRs based on the specific configuration of the logical channel. The logical channel configuration defines how the SRs are managed and ensures that the UE (101) can efficiently handle separate and / or multiple SRs if needed. This ensures that the SRs are aligned with the network's resource allocation, leading to efficient handling of SRs and resource allocation for the XR in the communication network system.

[0075] The proposed solution discloses the method where the UE (101) initially receives the DSR configuration for XR from the network and then it sets up the DSR for the XR. Additionally, it triggers the SR configuration as per LCG. This ensures the efficient handling of SRs and resource allocation for XR in the communication network system. By following the proposed solution, the UE (101) can optimize its performance and provide a seamless XR experience to the user. This method is particularly beneficial in scenarios where XR applications demand high bandwidth and low latency, making efficient resource management for maintaining the quality of service.

[0076] FIG. 3 is a flowchart illustrating the enhanced DSR handling mechanism at the MAC entity of the UE for extended reality in the communication network system according to embodiments disclosed herein.

[0077] At step 301, the DSR configuration controller (105) checks whether at least one DSR is pending. If there is a pending DSR, the process continues to step 302.

[0078] In step 302, the DSR configuration controller (105) checks if UL-SCH resources are available for a new transmission and if the UL-SCH resources can accommodate the DSR MAC CE along with its sub header as a result of logical channel prioritization. If both conditions are met, the process continues to step 303. If either of the conditions is not met, the process continues to step 304.

[0079] At step 303, the MAC entity of the UE (101) instructs the multiplexing and assembly procedure to generate the DSR MAC CE.

[0080] In step 304, the DSR configuration controller (105) checks if there are any pending SRs already triggered by the DSR procedure for at least one logical channel belonging to the LCG. If yes, the process continues to step 305.

[0081] At step 305, the MAC entity of the UE (101) triggers a scheduling request.

[0082] In an embodiment, one or more permutations or combinations of the embodiments described further in the invention can be utilized for the DSR handling mechanism. In an embodiment, the DSR is associated up to the LCG level, and how to select which SR (of which logical channel) to trigger is determined by the UE (101) implementation among the logical channels of the LCG.

[0083] In an embodiment, the MAC entity of the UE (101) skips selecting the logical channel of the LCG to trigger the SR for the DSR, which has no valid Physical Uplink Control Channel (PUCCH) resources configured. Further, in the case when all the logical channels of the LCG have no valid PUCCH resources configured for the SR, the UE (101) selects one of the logical channels of the LCG to trigger the SR for the DSR, and thereby a random access procedure is triggered.

[0084] In an embodiment, the MAC entity of the UE (101) skips selecting the logical channel of the LCG to trigger the SR for the DSR for which valid PUCCH resources are not available (for example, when the pertinent cell is in cell DRX non-active time). Further, in the case when all the logical channels of the LCG are not having valid PUCCH resources available for the SR, the UE (101) selects one of the logical channels of the LCG to trigger the SR for the DSR, and thereby the random access procedure is triggered.

[0085] In an embodiment, the MAC entity of the UE (101) skips selecting the logical channel of the LCG to trigger the SR for the DSR for which logicalChannelSR-Mask is set to true. That is, the MAC entity of the UE (101) selects the logical channel of the LCG to trigger the SR for the DSR for which logicalChannelSR-Mask is set to false.

[0086] In an embodiment, the MAC entity of the UE (101) skips selecting the logical channel of the LCG to trigger the SR for the DSR for which logicalChannelSR-DelayTimer is running at the time of the DSR triggering event. That is, the MAC entity of the UE (101) selects the logical channel of the LCG to trigger the SR for the DSR for which logicalChannelSR-DelayTimer is not running at the time of the DSR triggering event.

[0087] In an embodiment, the MAC entity of the UE (101) skips selecting the logical channel of the LCG to trigger the SR for the DSR for which sr-ProhibitTimer is running at the time of the DSR triggering event. That is, the MAC entity of the UE (101) selects the logical channel of the LCG to trigger the SR for the DSR for which sr-ProhibitTimer is not running at the time of the DSR triggering event.

[0088] In an embodiment, the MAC entity of the UE (101) triggers the SR for the DSR when the UL-SCH resources available for the new transmission do not meet LCP mapping restrictions of the logical channel that triggered the DSR. Further, the SR is transmitted on the SR configuration of this logical channel of the LCG. In an example, the MAC entity shall:

[0089] 1> if there is at least one DSR pending:

[0090] 2> if UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the DSR MAC CE plus its sub header as a result of logical channel prioritization:

[0091] 3> instruct the Multiplexing and Assembly procedure to generate the DSR MAC CE;

[0092] 2> if a DSR has been triggered and logicalChannelSR-DelayTimer is not running:

[0093] 3> if there is no UL-SCH resource available for a new transmission; or

[0094] 3> if the MAC entity is configured with configured uplink grant(s) and the DSR was triggered for a logical channel for which logicalChannelSR-Mask is set to false; or

[0095] 3> if the UL-SCH resources available for a new transmission do not meet the LCP mapping restrictions configured for the logical channel that triggered the DSR:

[0096] 4> trigger a Scheduling Request.

[0097] In an embodiment, the MAC entity of the UE (101) triggers the SR for DSR when the UL-SCH resources available for a new transmission do not meet LCP mapping restrictions for all the logical channels of the LCG.

[0098] In an embodiment, the network configures the UE (101) in the RRC signaling message wherein all the logical channels of the LCG are configured with the same SR configuration.

[0099] In an embodiment, the network configures the UE (101) in the RRC signaling message wherein the SR configuration for DSR is configured per LCG, that is, SR configuration is not configured per logical channel.

[0100] In an embodiment, the network configures the UE (101) in the RRC signaling message wherein an SR configuration for DSR is configured for one or more logical channels of the LCG. Further, only the logical channel(s) of the LCG that are configured with the SR configuration for DSR are considered for the transmission of the SR for the DSR.

[0101] In an embodiment, when the DSR triggering event occurs for multiple logical channels of the LCG and the uplink resources are not available for a new transmission or the UL-SCH resources cannot accommodate the DSR MAC CE plus its sub-header as a result of logical channel prioritization, then each of the pertinent logical channels of the LCG triggers one separate SR for DSR.

[0102] In an embodiment, when the DSR triggering event occurs for multiple logical channels of the LCG and the uplink resources are not available for the new transmission or the UL-SCH resources cannot accommodate the DSR MAC CE plus its sub-header as a result of logical channel prioritization, then one logical channel of the LCG triggers the SR for DSR.

[0103] In an embodiment, the MAC entity of the UE (101) triggers SR of the logical channel for the LCG for which the PDCP SDU with the smallest remaining value of PDCP discardTimers among all the data buffered for the (all) the logical channels of the LCG that has not been transmitted in any MAC PDU or reported as data volume in the DSR MAC CE becomes below remainingTimeThreshold of the LCG when the DSR was triggered and the UL-SCH resources are not available for the new transmission or the UL-SCH resources cannot accommodate the DSR MAC CE plus its sub-header as a result of logical channel prioritization. Further, in an embodiment, when the DSR triggering events occur for multiple logical channels of the LCG simultaneously and the uplink resources are not sufficient to accommodate DSR MAC CE, then each of the pertinent logical channels of the LCG triggers one separate SR for DSR. In an alternative embodiment, when the DSR triggering events occur for multiple logical channels of the LCG simultaneously and the uplink resources are not sufficient to accommodate DSR MAC CE, then only one logical channel of the LCG triggers the SR for DSR.

[0104] In an embodiment, the UE (101) is utilized for triggering the SR or multiple SRs for the configured DSR per LCG. Initially, the UE (101) configures the LCG associated with the DSR. Further, the UE (101) detects the logical channel of a plurality of logical channels of the LCG having the smallest remaining value of the running PDCP discard timers among all PDCP SDUs buffered for the logical channel. These SDUs have not been transmitted in any MAC PDU and are not reported as data volume in the DSR MAC CE. The smallest remaining PDCP discard timer value is required to fall below a predefined or pre-configured remaining time threshold for the LCG, further triggering the DSR for the detected logical channel of the LCG. The UE (101) determines the UL-SCH resources are either unavailable for the new transmissions or may not accommodate the DSR MAC-Control Element (CE) along with its sub-header due to Logical Channel Prioritization. If these conditions are met, the UE (101)'s (101) MAC entity triggers the SR for the pending DSR for the detected logical channel of the LCG. The SR configuration of the detected logical channel is utilized as the corresponding SR configuration for the triggered SR associated with the DSR. This process ensures efficient uplink resource allocation by prioritizing logical channels.

[0105] Further, the method involves the UE (101) detecting the DSR triggering event for multiple logical channels within the LCG. Upon detecting the triggering event, the UE (101) determines that UL-SCH resources are either unavailable for the new transmission or insufficient to provide a DSR MAC CE along with its sub-header due to logical channel prioritization. Further, the UE (101) triggers a separate SR for each of the logical channels of the LCG that triggered the DSR. This process confirms that all logical channels required for the DSR are addressed individually.

[0106] In an embodiment, the MAC entity of the UE (101) triggers the SR for DSR when the UL-SCH resources are not available for a new transmission or the UL-SCH resources cannot accommodate the DSR MAC CE plus its sub-header as a result of logical channel prioritization and there is no pending SR already triggered by the DSR procedure for at least one logical channel belonging to the LCG as of this DSR.

[0107] In an embodiment, the MAC entity of the UE (101) triggers the SR for DSR when the UL-SCH resources are not available for the new transmission or the UL-SCH resources cannot accommodate the DSR MAC CE plus its sub-header as a result of logical channel prioritization and there is no pending SR already triggered by the DSR procedure for a logical channel belonging to the LCG as of this DSR. An example of specification is provided as follows.

[0108] In an example if there is at least one DSR pending, the MAC entity shall:

[0109] 1> if UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the DSR MAC CE plus its sub header as a result of logical channel prioritization:

[0110] 2> instruct the Multiplexing and Assembly procedure to generate the DSR MAC CE;

[0111] 1> else if there is no pending SR already triggered by the DSR procedure for a logical channel belonging to the LCG as of this DSR:

[0112] 2> trigger a Scheduling Request.

[0113] FIG 4 is the flowchart that illustrates the enhanced DSR handling mechanism at the MAC entity of the UE for extended reality in the communication network system according to another embodiment as disclosed herein. FIG 4 discloses the handling of the DSR in the UE (101).

[0114] At step 401, the MAC entity of the UE (101) determines a logical channel of the LCG for which the PDCP SDU with the smallest remaining value of PDCP discard timers among all the buffered data for the logical channel of the LCG that has not been transmitted in any MAC PDU or reported as data volume in a DSR MAC CE becomes below the remainingTimeThreshold of the LCG. This ensures that the data with the discard timer is prioritized for transmission, thereby enhancing the efficiency and reliability of the communication system, especially for extended reality applications that require low latency and high data throughput.

[0115] At step 402, upon determining the logical channel, the MAC entity triggers the DSR for the corresponding LCG. This initiates the process of requesting uplink resources from the network, which is necessary for the transmission of the buffered data. The timely triggering of the DSR ensures that the data is transmitted before the discard timer expires, thus preventing data loss and maintaining the quality of service.

[0116] At step 403, the MAC entity verifies if there is no DSR pending that is triggered for the same logical channel of the LCG since the last transmission of the DSR MAC CE. If this condition is met, the process proceeds to step 404. This verification step avoids redundant DSRs, which can lead to unnecessary signaling overhead and inefficient use of network resources.

[0117] At step 404, the MAC entity checks if there is at least one DSR pending. If yes, the process proceeds to step 405. This step ensures that the MAC entity is aware of any pending DSRs and can manage them appropriately to avoid conflicts and ensure efficient resource allocation.

[0118] At step 405, the MAC entity checks two conditions: one is whether UL-SCH resources are available for a new transmission, and the other is whether the UL-SCH resources can accommodate the DSR MAC CE plus its sub header as a result of logical channel prioritization. If both conditions are met, the process proceeds to step 406. If either of the conditions is not met, the process continues to step 407. This ensures that the necessary resources are available for the transmission of the DSR, thereby preventing transmission failures and ensuring the reliability of the communication system.

[0119] At step 406, the MAC entity of the UE (101) instructs the multiplexing and assembly procedure to generate the DSR MAC CE. This involves the actual creation of the DSR MAC CE, which is then transmitted to the network to request the necessary uplink resources.

[0120] At step 407, the MAC entity checks if there is no pending SR already triggered by the DSR procedure for the same logical channel belonging to the LCG as of this DSR. If this condition is met, the process continues to step 408. This ensures that there are no conflicts between the DSR and SR procedures, which could lead to inefficient resource allocation and potential transmission failures.

[0121] At step 408, the MAC entity of the UE (101) triggers the SR. This involves the actual transmission of the SR to the network, requesting the necessary uplink resources for the transmission of the buffered data.

[0122] In an embodiment, the MAC entity of the UE (101) triggers a DSR for the LCG if there is no DSR pending that is triggered for the same logical channel of the LCG since the last transmission of the DSR MAC CE for the logical channel of the LCG for which the PDCP SDU with the smallest remaining value of PDCP discard timers among all the data buffered for the (all) logical channel of the LCG that has not been transmitted in any MAC PDU or reported as data volume in the DSR MAC CE becomes below the remainingTimeThreshold of the LCG. This embodiment ensures that the DSR is triggered only when necessary, thereby optimizing the use of network resources and enhancing the efficiency and reliability of the communication system.

[0123] In an example, the RRC controls the DSR procedure by configuring the following parameter:

[0124] - remainingTimeThreshold: the threshold on remaining time for triggering a DSR for an LCG.

[0125] If an LCG is configured for delay status reporting, the MAC entity shall:

[0126] 1> if the smallest remaining value of the PDCP discardTimers among all the data buffered for the LCG that has not been transmitted in any MAC PDU or reported as data volume in a DSR MAC CE becomes below remainingTimeThreshold of the LCG; and

[0127] 1> if there is no DSR pending that is triggered for same logical channel of the LCG since the last transmission of a DSR MAC CE:

[0128] 2> trigger a DSR for the LCG.

[0129] If there is at least one DSR pending, the MAC entity shall:

[0130] 1> if UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the DSR MAC CE plus its sub header as a result of logical channel prioritization:

[0131] 2> instruct the Multiplexing and Assembly procedure to generate the DSR MAC CE;

[0132] 1> else if there is no pending SR already triggered by the DSR procedure for the same logical channel as of this DSR:

[0133] 2> trigger a Scheduling Request.

[0134] In an example, the Delay Status Reporting (DSR) procedure is used to provide the serving gNB with delay status of LCGs. This delay status for an LCG includes remaining time, which is the smallest remaining value of the PDCPdiscardTimers among SDUs buffered for the LCG as specified in clause 7.3 in TS 38.323 [4], and the total amount of delay-critical UL data for the LCG according to the data volume calculation procedure specified in clause 5.5 in TS 38.322 [3] and clause 5.6 in TS 38.323 [4] for the associated RLC and PDCP entities, respectively.

[0135] The RRC controls the DSR procedure by configuring the following parameter: -remainingTimeThreshold: the threshold on remaining time for triggering a DSR for an LCG.

[0136] The logical channel that has smallest remaining value of the PDCP discardTimers among all the data buffered for the LCG that has not been transmitted in any MAC PDU or reported as data volume in a DSR MAC CE which becomes below remainingTimeThreshold of the LCG is considered to trigger the DSR. When the SR is triggered for the DSR, the SR configuration of this logical channel is considered as corresponding SR configuration for the triggered SR for the DSR.

[0137] In an embodiment, the MAC entity of the UE (101) triggers the SR of the logical channel with the highest priority among the logical channels of the LCG.

[0138] In an embodiment, the MAC entity of the UE (101) triggers SR of the logical channel with the highest priority among the logical channels that have (non-zero) delay-critical uplink data of the LCG.

[0139] In an embodiment, the Logical Channel Identity (LCH ID) of the logical channel for which the SR should be triggered for DSR is explicitly configured per LCG by the network via RRC signaling. That is, no additional dedicated SR configuration for LCG is configured, but legacy SR for Buffer Status Report (BSR) is reused for DSR purposes. Only the representative logical channel will be configured.

[0140] In an embodiment, the DSR configuration controller (105) triggers the SR of the logical channel for the LCG for which the PDCP SDU with the smallest remaining value of PDCP discard timers among all the data buffered for all the logical channels of the LCG that have not been transmitted in any MAC PDU or reported as data volume in the DSR MAC CE becomes below the remaining time threshold of the LCG when the DSR was triggered, and the UL-SCH resources are not available for a new transmission or the UL-SCH resources cannot accommodate the DSR MAC CE plus its sub-header as a result of logical channel prioritization.

[0141] Embodiments disclosed herein provide a system and method for an enhanced DSR triggering mechanism for the XR in the communication network system. When the LCG is configured for delay status reporting, the MAC entity of the UE (101) triggers the DSR for the LCG if the smallest remaining value of the PDCP discardTimers among all the data buffered for the LCG that has not been transmitted in any MAC PDU or reported as data volume in the DSR MAC CE becomes below the remainingTimeThreshold of the LCG, and if at least one of the following conditions are met: (a) there is no DSR pending (or triggered) for the LCG since the configuration or reconfiguration of DSR functionality for the LCG by the upper layers, which is not used to disable the DSR function (for the LCG), and (b) there is no DSR pending for the LCG since the last transmission of the DSR MAC CE.

[0142] FIG. 5 is the flowchart that illustrates the DSR triggering mechanism at the MAC entity of the UE for XR in the communication network system according to embodiments as disclosed herein.

[0143] At step 501, the MAC entity of the UE (101) determines if the smallest remaining value of the PDCP discard timers among all the data buffered for the LCG that has not been transmitted in any MAC PDU or reported as data volume in a DSR MAC CE becomes below remainingTimeThreshold of the LCG (501).

[0144] At step 502, the DSR configuration controller (105) checks for any DSR pending for the LCG since the configuration or reconfiguration by the upper layers. This check is applicable when the configuration is not used to disable the DSR function for the LCG. If this check confirms no pending DSR, the process proceeds to step 505; otherwise, it proceeds to step 503.

[0145] At step 503, the DSR configuration controller (105) determines whether there is any DSR pending for the LCG since the last transmission of a DSR MAC CE. If there is no pending DSR, the process proceeds to step 505, and if there is a pending DSR, the process proceeds to step 504.

[0146] At step 504, the MAC entity of the UE (101) skips triggering the DSR for the LCG.

[0147] At step 505, the MAC entity of the UE (101) triggers the DSR for the LCG.

[0148] In an embodiment, one or more permutations or combinations of the embodiments described further in the invention can be utilized for the DSR handling mechanism.

[0149] In an embodiment, when an LCG is configured for delay status reporting, the MAC entity of the UE (101) triggers the DSR for the LCG if the smallest remaining value of the PDCP discard timers among all the data buffered for the LCG that has not been transmitted in any MAC PDU or reported as data volume in the DSR MAC CE becomes below remainingTimeThreshold of the LCG and if at least one of the following conditions is met:

[0150] There is no DSR pending (or triggered) for the LCG since the configuration or reconfiguration of DSR functionality by the upper layers, which is not used to disable the DSR function.

[0151] There is no DSR pending for the LCG since the last transmission of a DSR MAC CE.

[0152] In an embodiment, an example of 3GPP specification is provided that depicts the DSR triggering mechanism as follows:

[0153] In an example, if an LCG is configured for delay status reporting, the MAC entity shall:

[0154] 1> if the smallest remaining value of the PDCP discardTimers among all the data buffered for the LCG that has not been transmitted in any MAC PDU or reported as data volume in the DSR MAC CE becomes below remainingTimeThreshold of the LCG; and

[0155] if there is no DSR pending for the LCG since the configuration or reconfiguration of DSR functionality by the upper layers, which is not used to disable the DSR function; or

[0156] if there is no DSR pending for the LCG since the last transmission of a DSR MAC CE:

[0157] 2> trigger a DSR for the LCG.

[0158] In an embodiment, when the LCG is configured for delay status reporting, the MAC entity of the UE (101) triggers the DSR for the LCG if the smallest remaining value of the PDCP discardTimers among all the data buffered for the LCG that has not been transmitted in any MAC PDU or reported as data volume in the DSR MAC CE becomes belowremainingTimeThresholdof the LCG and if at least one of the following conditions are met:

[0159] There is no DSR pending (or triggered) for the LCG since the configuration or reconfiguration of DSR functionality for the LCG by the upper layers, which is not used to disable the DSR function (for the LCG).

[0160] There is no DSR pending for the LCG since the last transmission of the DSR MAC CE.

[0161] In an embodiment, examples of 3GPP specification are provided that depicts the DSR triggering mechanism as follows:

[0162] In an example, if the LCG is configured for delay status reporting, the MAC entity shall:

[0163] 1> if the smallest remaining value of the PDCPdiscardTimers among all the data buffered for the LCG that has not been transmitted in any MAC PDU or reported as data volume in the DSR MAC CE becomes belowremainingTimeThresholdof the LCG; and

[0164] if there is no DSR pending for the LCG since the configuration or reconfiguration of DSR functionality for the LCG by the upper layers, which is not used to disable the DSR function (for the LCG); or

[0165] if there is no DSR pending for the LCG since the last transmission of the DSR MAC CE:

[0166] 2> trigger the DSR for the LCG.

[0167] In an example, if the LCG is configured for delay status reporting, the MAC entity shall:

[0168] 1> if the smallest remaining value of the PDCPdiscardTimers among all the data buffered for the LCG that has not been transmitted in any MAC PDU or reported as data volume in the DSR MAC CE becomes belowremainingTimeThresholdof the LCG:

[0169] if there is no DSR pending for the LCG since the configuration or reconfiguration of DSR functionality for the LCG by the upper layers, which is not used to disable the DSR function (for the LCG); or

[0170] if there is no DSR pending for the LCG since the last transmission of the DSR MAC CE:

[0171] 3> trigger the DSR for the LCG.

[0172] In an embodiment, when the LCG is configured for delay status reporting, the MAC entity of the UE (101) triggers the DSR for the LCG if the smallest remaining value of the PDCPdiscardTimers among all the data buffered for the LCG that has not been transmitted in any MAC PDU or reported as data volume in the DSR MAC CE becomes belowremainingTimeThresholdof the LCG and if at least one of the following conditions are met:

[0173] There is no DSR pending (or triggered) for the LCG since the configuration or reconfiguration of DSR functionality for the LCG by the upper layers, which enables the DSR function (for the LCG).

[0174] There is no DSR pending for the LCG since the last transmission of the DSR MAC CE.

[0175] In an embodiment, the LCG-specific DSR configuration is considered to be enabled for the DSR reporting by default (or implicitly) when it is configured.

[0176] In an embodiment, the LCG-specific DSR configuration is considered to be disabled for the DSR reporting by default (or implicitly) when it is released.

[0177] In an embodiment, the LCG-specific DSR configuration is explicitly enabled for the DSR reporting by the Radio Resource Control (RRC) signaling when it is configured (e.g., through MAC-CellGroupConfig in the RRCReconfiguration message) or by the MAC signaling after it is configured.

[0178] In an embodiment, the LCG-specific DSR configuration is explicitly disabled for the DSR reporting by the RRC signaling when it is released in the RRC signaling or by the MAC signaling before it is released.

[0179] In an embodiment, an example of 3GPP specification is provided that depicts the DSR configuration and enabling / disabling as follows.

[0180] In an example:

[0181] - MAC-CellGroupConfig

[0182] The IE MAC-CellGroupConfig is used to configure MAC parameters for a cell group, including DRX.

[0183] -- ASN1START

[0184] -- TAG-MAC-CELLGROUPCONFIG-START

[0185] MAC-CellGroupConfig ::= SEQUENCE {

[0186] ....

[0187] dsr-ConfigToAddModList-r18 SEQUENCE (SIZE (1..maxNrofLCGs-r18)) OF LCG-DSR-Config-r18 OPTIONAL, -- Need N

[0188] dsr-ConfigToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofLCGs-r18)) OF LCG-Id-r18 OPTIONAL,

[0189] ....

[0190] LCG-DSR-Config-r18 ::= SEQUENCE {

[0191] lcg-Id-r18 LCG-Id-r18,

[0192] remainingTimeThreshold-r18 INTEGER (1..64)

[0193] }

[0194] LCG-Id-r18 ::= INTEGER (0..maxLCG-ID)

[0195] -- TAG-MAC-CELLGROUPCONFIG-STOP

[0196] -- ASN1STOP

[0197] dsr-ConfigToAddModList

[0198] List of LCG-specific DSR configurations to add or modify. The LCG-specific DSR configuration is considered to be enabled for DSR reporting by default when it is configured.

[0199] dsr-ConfigToReleaseList

[0200] List of LCG-specific DSR configurations to release. The LCG-specific DSR configuration is considered to be disabled for DSR reporting by default when it is released.

[0201] lcg-Id

[0202] Identifier of the Logical Channel Group which the DSR configuration refers to.

[0203] remainingTimeThreshold

[0204] Remaining time threshold used for triggering DSR for the Logical Channel Group, as specified in TS 38.321. Value in number of milliseconds.

[0205] In an embodiment, the DSR configuration includes the timer configuration for LogicalChannelSR-DelayTimer (or DSR- LogicalChannelSR-DelayTimer), which is applied to the relevant logical channel of the LCG if the logical channel is configured with a parameter logicalChannelSR-DelayTimerApplied (or DSR-logicalChannelSR-DelayTimerApplied) set as TRUE. This indicates to apply the delay timer (LogicalChannelSR-DelayTimer or DSR- LogicalChannelSR-DelayTimer) for SR transmission for this logical channel (e.g. SR for the DSR). LogicalChannelSR-DelayTimer or DSR- LogicalChannelSR-DelayTimer may be configured along with the DSR configuration for a specific LCG or collectively for all the configured LCGs. Further, the relevant logical channel of the LCG may be configured with a parameter logicalChannelSR-Mask. This indicates to mask or block the SR transmission for this logical channel (e.g. SR for the DSR).

[0206] In an embodiment, an example of 3GPP specification is provided that depicts the DSR configuration and LogicalChannelSR-DelayTimer as follows:

[0207] - MAC-CellGroupConfig

[0208] The IE MAC-CellGroupConfig is used to configure MAC parameters for a cell group, including DRX.

[0209] -- ASN1START

[0210] -- TAG-MAC-CELLGROUPCONFIG-START

[0211] MAC-CellGroupConfig ::= SEQUENCE {

[0212] ....

[0213] dsr-ConfigToAddModList-r18 SEQUENCE (SIZE (1..maxNrofLCGs-r18)) OF LCG-DSR-Config-r18 OPTIONAL, -- Need N

[0214] dsr-ConfigToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofLCGs-r18)) OF LCG-Id-r18 OPTIONAL,

[0215] ....

[0216] LCG-DSR-Config-r18 ::= SEQUENCE {

[0217] lcg-Id-r18 LCG-Id-r18,

[0218] remainingTimeThreshold-r18 INTEGER (1..64)

[0219] DSR-logicalChannelSR-DelayTimer ENUMERATED { sf20, sf40, sf64, sf128, sf512, sf1024, sf2560, spare1} OPTIONAL, -- Need R

[0220] }

[0221] LCG-Id-r18 ::= INTEGER (0..maxLCG-ID)

[0222] -- TAG-MAC-CELLGROUPCONFIG-STOP

[0223] -- ASN1STOP

[0224] DSR-logicalChannelSR-DelayTimer

[0225] Value in number of subframes. Value sf20 corresponds to 20 subframes, sf40 corresponds to 40 subframes, and so on.

[0226] In an embodiment, logicalChannel-SRDelayTimer is used to determine triggering a Scheduling Request for DSR as specified in the following example given below:

[0227] If there is at least one DSR pending, the MAC entity shall:

[0228] 1> if UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the DSR MAC CE plus its sub header as a result of logical channel prioritization:

[0229] 2> instruct the Multiplexing and Assembly procedure to generate the DSR MAC CE;

[0230] 1> else if there is no pending SR already triggered by the DSR procedure for the same logical channel as of this DSR and logicalChannel-SRDelayTimer for DSR is not configured or not running:

[0231] 2> trigger a Scheduling Request.

[0232] In an embodiment, if the DSR MAC CE cannot be accommodated in the available UL grant and there is no pending SR already triggered for DSR for same logical channel and the logicalChannel-SRDelayTimer for DSR is not configured or not running, the MAC entity will trigger the SR for DSR using the SR configuration associated with the logical channel which triggered the DSR. An example of specification is provided as follows:

[0233] If there is at least one DSR pending, the MAC entity shall:

[0234] 1> if UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the DSR MAC CE plus its sub header as a result of logical channel prioritization:

[0235] 2> instruct the Multiplexing and Assembly procedure to generate the DSR MAC CE;

[0236] 1> else if there is no pending SR already triggered by the DSR procedure for the same logical channel as of this DSR and logicalChannel-SRDelayTimer for DSR is not configured or not running:

[0237] 2> trigger the Scheduling Request using the SR configuration associated with the logical channel which triggered the DSR.

[0238] In an embodiment, the UE (101) releases the DSR configuration for DSR reporting when the UE (101) is released from RRC_CONNECTED to RRC_IDLE state (e.g. when UE (101) receives a RRCRelease message, when requested by upper layers, when data-InactivityTimer expires) and / or when the UE (101) is released from RRC_CONNECTED to RRC_INACTIVE state (e.g. when UE (101) receives a RRCRelease with suspendConfig message) and / or when the UE (101) receives RRCReestablishment message and / or the UE (101) detects or encounter a Radio Link Failure and / or the UE (101) receives RRCReconfiguration with Sync and / or UE (101) performs mobility (e.g. UE (101) receives RRCReconfiguration with mobility command or RRCReconfiguration with Sync message) and / or when the UE (101) performs a MAC RESET procedure.

[0239] In an embodiment, when the LCG is configured for delay status reporting, the DSR configuration controller (104) triggers the DSR for the LCG if the smallest remaining value of the PDCP discardTimers among all the data buffered for the LCG that has not been transmitted in any MAC PDU or reported as data volume in the DSR MAC CE becomes below remainingTimeThreshold of the LCG and if at least one of the following conditions are met:

[0240] There is no DSR pending (or triggered) for the LCG since the configuration or reconfiguration of DSR functionality for the LCG by the upper layers, which is not used to disable the DSR function (for the LCG). There is no DSR pending for the LCG since the last transmission of the DSR MAC CE.

[0241] FiG. 6 is a block diagram of a network entity 600 (that refers to network apparatus) according to an embodiment of the present disclosure.

[0242] The network entity 600 can be used to realize the DU, CU-UP, CU-CP, gNB, eNB source base station, destination station, source DU, source CU-UP, destination DU, destination CU-UP, destination CU-CP, master base station, secondary base station, OAM, UDM, AMF, SMF or UPF, etc. of the present disclosure.

[0243] Referring to the Figure 6, the network entity 600 may include at least one processor 610, a transceiver 620 and a memory 630. However, all of the illustrated components are not essential. The network entity 600 may be implemented by more or less components than those illustrated in Figure 6. In addition, the at least one processor 610 and the transceiver 620 and the memory 630 may be implemented as a single chip according to another embodiment.

[0244] The aforementioned components will now be described in detail.

[0245] The at least one processor 610 may include one or more processors or other processing devices that control the proposed function, process, and / or method. Operation of the network entity 600 aforementioned in this disclosure may be implemented by the processor 610. The processor 610 may execute one or more instructions stored in the memory 630 to operation as described above.

[0246] The at least one processor 610 may include various processing circuitry and / or multiple processors. For example, as used herein, including the claims, the term "processor" may include various processing circuitry, including at least one processor, wherein one or more of at least one processor, individually and / or collectively in a distributed manner, may be configured to perform various functions described herein. As used herein, when "processor", "at least one processor" and "one or more processors" are described as being configured to perform numerous functions, these terms cover situations, for example and without limitation, in which one processor performs some of recited functions and another processor(s) performs other of recited functions, and also situations in which a single processor may perform all recited functions. Additionally, the at least one processor may include a combination of processors performing various of the recited / disclosed functions, e.g., in a distributed manner. At least one processor may execute program instructions to achieve or perform various functions.

[0247] The transceiver 620 may include a RF transmitter for up-converting and amplifying a transmitted signal, and a RF receiver for down-converting a frequency of a received signal. However, according to another embodiment, the transceiver 620 may be implemented by more or less components than those illustrated in components.

[0248] The transceiver 620 may be connected to the processor 610 and transmit and / or receive a signal. The signal may include control information and data. In addition, the transceiver 620 may receive the signal through a wireless channel and output the signal to the processor 610. The transceiver 620 may transmit a signal output from the processor 610 through the wireless channel.

[0249] The memory 630 may store the control information or the data included in a signal obtained by the network entity 600. The memory 630 may be connected to the processor 610 and store at least one instruction or a protocol or a parameter for the proposed function, process, and / or method. The memory 630 may include read-only memory (ROM) and / or random access memory (RAM) and / or hard disk and / or CD-ROM and / or DVD and / or other storage devices.

[0250] FIG. 7 is a flowchart that illustrates a method of the UE for managing DSR for XR in a communication network system according to embodiments as disclosed herein.

[0251] Referring to Figure 7, in 710, according to an embodiment, the UE 101 receives, from a network entity (600), via Radio Resource Control (RRC) signaling (e.g. MAC-CellGroupConfig information), information on Delay Status Reporting (DSR) configuration (i.e. LCG-DSR-Config-r18). The DSR configuration includes an identifier of a Logical Channel Group (LCG) and a remaining time threshold parameter. The remaining time threshold parameter indicates a threshold on a remaining time for triggering a DSR for a logical channel within an LCG.

[0252] In 720, based on the remaining time threshold parameter, the UE 101 determines whether each logical channel within the LCG satisfies DSR triggering conditions. The DSR triggering conditions include (i) if a smallest remaining value among running Packet Data Convergence Protocol (PDCP) discard timers for PDCP Service Data Units (PDCP SDUs), buffered for a logical channel within the LCG, that have not been transmitted in any Medium Access Control Protocol Data Unit (MAC PDU) and have not been reported as data volume in a DSR MAC Control Element (MAC CE), becomes below the remaining time threshold parameter, and (ii) that there is no DSR pending for the logical channel.

[0253] In 730, the UE 101 triggers the DSR for each logical channel within the LCG that satisfies the DSR triggering conditions.

[0254] FIG. 8 is a flowchart that illustrates a method of the network entity for managing DSR for XR in a communication network system according to embodiments as disclosed herein.

[0255] Referring to Figure 8, in 810, according to an embodiment, the network entity 600 transmits, to a UE (101), via Radio Resource Control (RRC) signaling (e.g. MAC-CellGroupConfig information), information on Delay Status Reporting (DSR) configuration (i.e. LCG-DSR-Config-r18). The DSR configuration includes an identifier of a Logical Channel Group (LCG) and a remaining time threshold parameter. The remaining time threshold parameter indicates a threshold on a remaining time for triggering a DSR for a logical channel within an LCG.

[0256] In an embodiment, based on the remaining time threshold parameter, whether each logical channel within the LCG satisfies DSR triggering conditions is determined. The DSR triggering conditions include (i) if a smallest remaining value among running Packet Data Convergence Protocol (PDCP) discard timers for PDCP Service Data Units (PDCP SDUs), buffered for a logical channel within the LCG, that have not been transmitted in any Medium Access Control Protocol Data Unit (MAC PDU) and have not been reported as data volume in a DSR MAC Control Element (MAC CE), becomes below the remaining time threshold parameter, and (ii) that there is no DSR pending for the logical channel.

[0257] In an embodiment, a DSR is triggered for each logical channel within the LCG that satisfies the DSR triggering conditions.

[0258] 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 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 ofpreferredembodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments as described herein.

[0259] In addition, computer-readable storage media may be provided in the form of non-transitory storage media. The 'non-transitory storage medium' is a tangible device and only means that it does not contain a signal (e.g., electromagnetic waves). This term does not distinguish a case in which data is stored semi-permanently in a storage medium from a case in which data is temporarily stored. For example, the non-transitory recording medium may include a buffer in which data is temporarily stored.

[0260] The specific examples provided to explain the embodiments according to the present disclosure are merely a combination of each standard, method, detail method, and operation, and the various embodiments described herein can be performed through a combination of at least two or more techniques among the various techniques described. In addition, at this time, it can be performed according to a method determined through a combination of one or at least two or more of the aforementioned techniques. For example, it may be possible to perform a combination of parts of the operation of one embodiment with parts of the operation of another embodiment.

Claims

1.A method of a User Equipment (UE) in wireless communication, comprising:receiving, from a network entity, via Radio Resource Control (RRC) signaling, information on Delay Status Reporting (DSR) configuration including an identifier of a Logical Channel Group (LCG) and a remaining time threshold parameter;based on the remaining time threshold parameter, determining whether each logical channel within the LCG satisfies DSR triggering conditions; andtriggering the DSR for each logical channel within the LCG that satisfies the DSR triggering conditions.2.The method of claim 1, further comprising:determining that a smallest remaining value among running Packet Data Convergence Protocol (PDCP) discard timers for PDCP Service Data Units (PDCP SDUs), buffered for a logical channel within the LCG, that have not been transmitted in any Medium Access Control Protocol Data Unit (MAC PDU) and have not been reported as data volume in a DSR MAC Control Element (MAC CE), becomes below the remaining time threshold parameter;determining that there is no DSR pending for the logical channel; andtriggering the DSR for the logical channel.3.The method of claim 2, further comprising:determining at least one DSR pending;determining that UL-SCH resources are not available for a new transmission or the UL-SCH resources cannot accommodate a DSR MAC CE and a subheader of the DSR MAC CE as a result of logical channel prioritization;determining that there is no pending SR already triggered by a DSR procedure for the logical channel that triggered the DSR; andtriggering the SR for the logical channel that triggered the DSR.4.The method of claim 3, wherein a SR configuration of the logical channel that triggered the DSR is considered as corresponding SR configuration for the triggered SR.5.The method of claim 1, further comprising:determining at least one DSR pending;determining that UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate a DSR MAC CE and a subheader of the DSR MAC CE as a result of logical channel prioritization; andinstructing a Multiplexing and Assembly procedure to generate the DSR MAC CE.6.A method of a network entity in wireless communication, comprising:transmitting, to a User Equipment (UE), via Radio Resource Control (RRC) signaling, information on Delay Status Reporting (DSR) configuration including an identifier of a Logical Channel Group (LCG) and a remaining time threshold parameter,wherein, based on the remaining time threshold parameter, whether each logical channel within the LCG satisfies DSR triggering conditions is determined, andwherein a DSR is triggered for each logical channel within the LCG that satisfies the DSR triggering conditions.7.The method of claim 6, wherein,in case that a smallest remaining value among running Packet Data Convergence Protocol (PDCP) discard timers for PDCP Service Data Units (PDCP SDUs), buffered for a logical channel within the LCG, that have not been transmitted in any Medium Access Control Protocol Data Unit (MAC PDU) and have not been reported as data volume in a DSR MAC Control Element (MAC CE), becomes below the remaining time threshold parameter, andin case that there is no DSR pending for the logical channel,the DSR is triggered for the logical channel.8.A User Equipment (UE) in wireless communication, comprising:memory storing one or more instructions; andat least one processor configured to execute the one or more instruction stored in the memory to:receive, from a network entity, via Radio Resource Control (RRC) signaling, information on Delay Status Reporting (DSR) configuration including an identifier of a Logical Channel Group (LCG) and a remaining time threshold parameter; andbased on the remaining time threshold parameter, determine whether each logical channel within the LCG satisfies DSR triggering conditions; andtrigger the DSR for each logical channel within the LCG that satisfies the DSR triggering conditions.9.The UE of claim 8, the at least one processor further configured to execute the one or more instruction stored in the memory to:determine that a smallest remaining value among running Packet Data Convergence Protocol (PDCP) discard timers for PDCP Service Data Units (PDCP SDUs), buffered for a logical channel within the LCG, that have not been transmitted in any Medium Access Control Protocol Data Unit (MAC PDU) and have not been reported as data volume in a DSR MAC Control Element (MAC CE), becomes below the remaining time threshold parameter;determine that there is no DSR pending for the logical channel; andtrigger the DSR for the logical channel.10.The UE of claim 9, the at least one processor further configured to execute the one or more instruction stored in the memory to:determine at least one DSR pending;determine that UL-SCH resources are not available for a new transmission or the UL-SCH resources cannot accommodate a DSR MAC CE and a subheader of the DSR MAC CE as a result of logical channel prioritization;determine that there is no pending SR already triggered by a DSR procedure for the logical channel that triggered the DSR; andtrigger the SR for the logical channel that triggered the DSR.11.The UE of claim 10, wherein a SR configuration of the logical channel that triggered the DSR is considered as corresponding SR configuration for the triggered SR.12.The UE of claim 8, the at least one processor further configured to execute the one or more instruction stored in the memory to:determine at least one DSR pending;determine that UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate a DSR MAC CE and a subheader of the DSR MAC CE as a result of logical channel prioritization; andinstruct a Multiplexing and Assembly procedure to generate the DSR MAC CE.13.A network entity in wireless communication, comprising:memory storing one or more instructions; andat least one processor configured to execute the one or more instruction stored in the memory to:transmit, to a User Equipment (UE), via Radio Resource Control (RRC) signaling, information on Delay Status Reporting (DSR) configuration including an identifier of a Logical Channel Group (LCG) and a remaining time threshold parameter,wherein, based on the remaining time threshold parameter, whether each logical channel within the LCG satisfies DSR triggering conditions is determined, andwherein a DSR is triggered for each logical channel within the LCG that satisfies the DSR triggering conditions.14.The network entity of claim 13, wherein,in case that a smallest remaining value among running Packet Data Convergence Protocol (PDCP) discard timers for PDCP Service Data Units (PDCP SDUs), buffered for a logical channel within the LCG, that have not been transmitted in any Medium Access Control Protocol Data Unit (MAC PDU) and have not been reported as data volume in a DSR MAC Control Element (MAC CE), becomes below the remaining time threshold parameter, andin case that there is no DSR pending for the logical channel,the DSR is triggered for the logical channel.

Images