Method and wireless network for managing power savings for augmented reality (XR) services

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Embodiments herein disclose a method of managing power savings for XR services in a wireless network by a UE. The method includes receiving a radio bearer configuration including an identifier field. Further, the method includes determining whether the received radio bearer configuration includes an "isXR bearer" as an identifier field.

Description

Technical Field

[0001] Embodiments disclosed herein relate to wireless networks, and more particularly to methods and wireless networks for managing extended reality (XR) services. Background Art

[0002] The 5th generation (5G) mobile communication technology defines a wider frequency band so that high transmission rates and new services are possible, and can be realized not only in the "sub-6 GHz" frequency band such as 3.5 GHz, but also in the "higher than 6 GHz" frequency band called millimeter waves including 28 GHz and 39 GHz. In addition, it has been considered to realize 6G mobile communication technology (called super 5G system) in the terahertz frequency band (for example, 95 GHz to 3 THz frequency band) in order to realize a transmission rate fifty times faster than 5G mobile communication technology and an ultra-low latency of one tenth of 5G mobile communication technology.

[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC) and massive machine type communication (mMTC), standardization work on beamforming and massive MIMO has been ongoing for mitigating radio wave path loss and increasing radio wave transmission distance in mmWave, supporting parameter sets for efficient utilization of mmWave resources and dynamic operation of time slot formats (e.g., operation of multiple subcarrier spacings), initial access technology for supporting multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding methods such as LDPC (low-density parity check) codes for large-volume data transmission and polar codes for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing dedicated networks dedicated to specific services.

[0004] Currently, there are ongoing discussions on improvements and performance enhancements of initial 5G mobile communication technologies in consideration of the services that 5G mobile communication technologies are to support, and there is physical layer standardization on technologies such as V2X (Vehicle-to-Everything), which is used to assist driving determination of autonomous vehicles based on information about the location and status of vehicles transmitted by vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed), which is a system operation intended to comply with various regulatory-related requirements in unlicensed bands, NR UE power saving, non-terrestrial networks (NTN), which are UE-satellite direct communications for providing coverage in areas where communications with terrestrial networks are unavailable, and positioning.

[0005] In addition, the standardization of air interface architecture / protocols has been ongoing, involving technologies such as: Industrial Internet of Things (IIoT) to support new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access technology for simplifying the random access process (2-step RACH for NR). In terms of system architecture / services, 5G baseline architecture (e.g., service-based architecture or service-based interface) is also being standardized to combine network function virtualization (NFV) and software-defined network (SDN) technologies, as well as mobile edge computing (MEC) for receiving services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, the already exponentially growing number of connected devices will be connected to the communication network, and it is therefore expected that enhanced functions and performance of the 5G mobile communication system and integrated operation of connected devices will be necessary. To this end, new research is planned in the following areas: effectively supporting extended reality (XR) such as AR (augmented reality), VR (virtual reality), MR (mixed reality), etc.; improving 5G performance and reducing complexity using artificial intelligence (AI) and machine learning (ML); AI service support; metadata service support; and drone communication.

[0007] Furthermore, such developments in 5G mobile communication systems will serve as a foundation for developing new waveforms for providing coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional spatial multiplexing technologies using OAM (orbital angular momentum), and RIS (reconfigurable smart surface), and full-duplex technologies for increasing the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technologies for achieving 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 technologies for realizing services at a level of complexity that exceeds the limits of UE operating capabilities by utilizing ultra-high-performance communication and computing resources.

[0008] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with respect to the present disclosure. Summary of the invention

[0009] Technical issues The main purpose of the embodiments of this document is to disclose a method and system (or wireless network) for managing power saving of XR service reception in wireless communication, wherein a DRX mechanism for power saving (including the operation of a DRX timer for XR service reception) has been disclosed.

[0010] Another objective of the embodiments herein is to disclose a DRX mechanism for XR in a wireless network.

[0011] Another object of embodiments herein is to disclose multiple predefined configurations of DRX for XR and switching therebetween.

[0012] Another object of the embodiments herein is to disclose identification of an XR bearer field in radio bearer configuration signaling.

[0013] Another object of embodiments herein is to disclose UE capabilities regarding supporting multiple DRX configurations and XR power saving.

[0014] It is another object of embodiments herein to disclose a configurable or dynamic offset with respect to DRX advance / advance.

[0015] Solutions to the problem Therefore, an embodiment of the present invention provides a method for managing power saving of XR services in a wireless network. The method includes receiving, by a user equipment (UE), a radio bearer configuration including an identifier field. In addition, the method includes determining, by the UE, whether the received radio bearer configuration includes an "isXR bearer" field as an identifier field. In addition, the method includes performing, by the UE, one of the following: when determining that the radio bearer configuration includes the "isXR bearer" field, identifying that the radio bearer is related to the XR service, and when determining that the radio bearer configuration does not include the "isXR bearer" field, identifying that the radio bearer is not related to the XR service.

[0016] In an embodiment, the method includes receiving, by the UE, a configurable value or dynamic value of at least one of drx-StartOffsetXR and drx-slotOffsetXR in at least one of downlink control information (DCI), wake-up signal (WUS), downlink control indication (DCI) with cyclic redundancy code (CRC) scrambled by power saving radio network temporary identity (PS-RNTI) (DCP), wake-up radio (WUR), medium access control control element (MAC CE), and radio resource control (RRC) signaling from a network device for at least one XR service (or bearer or logical channel). In addition, the method includes applying, by the UE, at least one of drx-StartOffsetXR and drx-slotOffsetXR as a pre-ponement or a deferment for starting a drx-onDurationTimer for XR service reception. Furthermore, the method includes applying, by the UE, at least one of drx-StartOffsetXR and drx-slotOffsetXR to calculating at least one of short discontinuous reception (DRX) and long DRX for XR service reception.

[0017] In an embodiment, at least one of XR service reception and XR service transmission is performed by reusing at least one of a cell radio network temporary identity (C-RNTI) and a configured scheduling radio network temporary identity (CS-RNTI) for unicast reception and unicast transmission.

[0018] In an embodiment, if the XR service is multiplexed with at least one of a non-XR service and a legacy unicast on the same medium access control protocol data unit (MAC PDU), the XR service uses at least one of a C-RNTI and a CS-RNTI.

[0019] In an embodiment, the method includes receiving, by the UE, a radio resource control (RRC) reconfiguration message, the RRC reconfiguration message including a set of configured values ​​for at least one of drx-StartOffsetXR and drx-slotOffsetXR. In addition, the method includes applying, by the UE, at least one value from the set of configured values ​​to change the start of drx-onDurationTimer based on an indication from at least one of DCI, WUS, DCP, WUR, and MAC CE, the at least one of the DCI, WUS, DCP, WUR, and MAC CE being scrambled using at least one of an XR-RNTI, XR-CS-RNTI, C-RNTI, and CS-RNTI for reception of an XR service, wherein at least one value from the set of configured values ​​is indicated by an index to the set of configured values ​​or a bitmap or field indicating the configuration value to be applied.

[0020] In an embodiment, the method includes configuring at least one DRX configuration parameter from a plurality of DRX configurations for a UE. The at least one DRX configuration parameter includes at least one of a drx-OnDurationTimer, a drx-inactivityTimer, a round trip time (RTT) timer, and a retransmission timer. The network device configures at least one DRX configuration parameter from a plurality of DRX configurations for the UE. In addition, the method includes associating a DRX configuration from a plurality of DRX configurations with an XR session for an XR service based on the at least one DRX configuration parameter.

[0021] In an embodiment, the method includes determining, by the UE, whether there is at least one DRX configuration for the XR service during the DRX active time. In addition, the method includes monitoring, by the UE, a physical downlink control channel (PDCCH) search space for the XR service during the DRX active time.

[0022] In an embodiment, the method includes indicating a capability of supporting multiple DRX configurations through at least one of a UE capability information exchange procedure and UE assistance information.

[0023] In an embodiment, the method comprises indicating in a UE capability message whether the UE supports power saving preference for XR.

[0024] In an embodiment, the method comprises indicating a maximum number of DRX configurations supported by the UE.

[0025] In an embodiment, the method includes indicating in UE assistance information a preference for at least one of: a common DRX configuration for legacy unicast and XR services, separate DRX configurations for legacy unicast and XR services, a common DRX configuration or a per-service DRX configuration, a preferred RTT timer value for XR services, and a preferred retransmission timer value.

[0026] In an embodiment, the method includes identifying, by the UE, whether at least two DRX configurations are applied to one or more XR service receptions. In addition, the method includes switching, by the UE, between at least two DRX configurations among a plurality of DRX configurations. In addition, the method includes receiving, by the UE, an indication of a suitable DRX configuration among at least two DRX configurations for XR reception using at least one of DCI, WUS, WUR, and MAC CE.

[0027] In an embodiment, the indicated DRX configuration is applicable for a predefined time.

[0028] In an embodiment, the method includes receiving, by the UE, a MAC CellGroupConfig message. The MAC CellGroupConfig message configures medium access control (MAC) parameters for a cell group, the MAC parameters including at least one of setting of drx-Config for at least one of legacy unicast and XR service reception, setting of drx-ConfigSecondaryGroup, release of drx-Config, and release of drx-ConfigSecondaryGroup.

[0029] In an embodiment, the DRX configurations differ in at least one parameter including at least one of the following: drx-onDurationTimer, drx-inactivityTimer, drx-HARQ-RTT-TimerUL, drx-HARQ-RTT-TimerDL, drx-RetransmissionTimerUL, drx-RetransmissionTimerDL, drx-SlotOffsetXR, drx-SlotOffsetXR-static, drx-Shortcycle, drx-ShortcycleTimer, drx-LongCycle, drx-StartOffsetXR and drx-StartOffsetXR-static.

[0030] In an embodiment, the HARQ process for XR services is common and shared with traditional unicast or non-XR services.

[0031] Therefore, an embodiment of the present invention provides a method for managing power saving of XR services in a wireless network. The method includes sending, by a network device, to a UE in the wireless network, an identifier field including an "isXR bearer" field to identify a radio bearer configuration related to an XR service. In addition, the method includes managing the XR service in the wireless network based on the radio bearer configuration including the "isXR bearer" field by the network device.

[0032] In an embodiment, the method includes sending a configurable value or a dynamic value for at least one of drx-StartOffsetXR and drx-slotOffsetXR in at least one of DCI, WUS, DCP, WUR, MAC CE, and RRC signaling to the UE for XR service.

[0033] In an embodiment, the method comprises sending an RRC reconfiguration message including a set of configured values ​​for at least one of drx-StartOffsetXR and drx-slotOffsetXR to the UE for XR service.

[0034] In an embodiment, the method comprises configuring at least one DRX configuration parameter from a plurality of DRX configurations for the UE.

[0035] Therefore, an embodiment of the present invention provides a UE including an XR service controller coupled to a processor and a memory. The XR service controller is configured to receive a radio bearer configuration including an identifier field. In addition, the XR service controller is configured to determine whether the received radio bearer configuration includes an "isXR bearer" field as an identifier field. In addition, the XR service controller is configured to perform one of the following: when it is determined that the radio bearer configuration includes the "isXR bearer" field, it is identified that the radio bearer is related to the XR service; and when it is determined that the radio bearer configuration does not include the "isXR bearer" field, it is identified that the radio bearer is not related to the XR service.

[0036] Therefore, an embodiment of the present invention provides a network device including an XR service controller coupled to a processor and a memory. The XR service controller is configured to send a radio bearer configuration including an identifier field as an "isXR bearer" field to a UE in a wireless network to identify that the radio bearer is related to the XR service. In addition, the XR service controller is configured to manage the XR service in the wireless network based on the radio bearer configuration including the "isXR bearer" field.

[0037] Therefore, an embodiment of the present invention provides a method performed by a user equipment (UE) in a communication system. The method includes: receiving a radio bearer configuration associated with a radio bearer; determining whether the radio bearer configuration includes an identifier field associated with extended reality (XR); and based on determining that the radio bearer configuration includes the identifier field, identifying that the radio bearer is associated with an XR service.

[0038] In an embodiment, the method includes performing XR service communications associated with the XR service based on the identification.

[0039] In an embodiment, the XR service communication is scheduled based on a physical downlink control channel (PDCCH) addressed to one of the first radio network temporary identity (RNTI) or the second RNTI.

[0040] In an embodiment, wherein the first RNTI is one of a Cell-RNTI (C-RNTI) or a Configured Scheduling-RNTI (CS-RNTI).

[0041] In an embodiment, the second RNTI is one of an XR-RNTI or an XR-CS-RNTI.

[0042] In an embodiment, where the PDCCH is addressed to the first RNTI, XR service communications are multiplexed with communications associated with non-XR services.

[0043] In an embodiment, a hybrid automatic repeat request (HARQ) process for XR services is a process shared with a HARQ process for non-XR services.

[0044] In an embodiment, the method includes: receiving configuration information associated with a plurality of discontinuous reception (DRX) configurations; and monitoring a PDCCH search space for an XR service based on a first DRX configuration among the plurality of DRX configurations.

[0045] In an embodiment, multiple DRX configurations differ from each other in at least one DRX parameter including at least one of the following: drx-onDurationTimer, drx-inactivityTimer, drx-HARQ-RTT-TimerUL, drx-HARQ-RTT-TimerDL, drx-RetransmissionTimerUL, drx-RetransmissionTimerDL, drx-SlotOffsetXR, drx-SlotOffsetXR-static, drx-Shortcycle, drx-ShortcycleTimer, drx-LongCycle, drx-StartOffsetXR or drx-StartOffsetXR-static.

[0046] In an embodiment, the method includes: switching to a second DRX configuration among a plurality of DRX configurations, wherein the second DRX configuration is different from the first DRX configuration; and monitoring a PDCCH search space for an XR service based on the second DRX configuration.

[0047] Therefore, an embodiment of the present invention provides a UE, which includes a transceiver; and a processor coupled to the transceiver. In an embodiment, the processor is configured to: receive a radio bearer configuration associated with a radio bearer; determine whether the radio bearer configuration includes an identifier field associated with extended reality (XR); and based on determining that the radio bearer configuration includes the identifier field, identify that the radio bearer is associated with the XR service.

[0048] Therefore, an embodiment of the present invention provides a method performed by a network device in a communication system. The method includes: identifying whether a radio bearer is associated with an extended reality (XR) service; based on identifying that the radio bearer is associated with the XR service, sending a radio bearer configuration associated with the radio bearer, wherein the radio bearer configuration includes an identifier field associated with the XR; and performing communication associated with the XR service.

[0049] Therefore, an embodiment of the present invention provides a network device including a transceiver and a processor coupled to the transceiver. In an embodiment, the processor is configured to: identify whether a radio bearer is associated with an extended reality (XR) service; based on identifying that the radio bearer is associated with the XR service, send a radio bearer configuration associated with the radio bearer, wherein the radio bearer configuration includes an identifier field associated with the XR; and perform communication associated with the XR service.

[0050] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and accompanying drawings. However, it should be understood that, although indicating at least one embodiment and many specific details thereof, the following description is given by way of illustration and not 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.

[0051] Prior to proceeding with the following description, it may be helpful to set forth definitions of certain words and phrases used throughout this patent document: the terms "include" and "comprising" and their derivatives mean including but not limited to; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with" and their derivatives may mean including, included therein, interconnected with, containing, contained therein, connected to or connected with, coupled to or coupled with, communicating with, cooperating with, interleaved, juxtaposed, proximate, bound to or bound with, having, having the property of, etc.; and the term "controller" means any device, system, or part thereof that controls at least one operation, such device may be implemented in hardware, firmware, or software, or some combination of at least two thereof. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0052] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or a portion thereof suitable for implementation in a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disk (DVD) or any other type of memory. "Non-transitory" computer-readable media do not include wired, wireless, optical or other communication links that transmit transient electrical signals or other signals. Non-transitory computer-readable media include media in which data can be permanently stored and media in which data can be stored and then rewritten, such as rewritable optical disks or erasable memory devices.

[0053] Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.

[0054] Beneficial Effects of the Invention According to the present disclosure, a method and system (or wireless network) for managing power saving of XR service reception in wireless communication may be provided, wherein a DRX mechanism for power saving (including operation of a DRX timer for XR service reception) has been disclosed.

[0055] According to the present disclosure, a DRX mechanism for XR in a wireless network may be provided.

[0056] According to the present disclosure, multiple predefined configurations of DRX for XR and switching between them may be provided.

[0057] According to the present disclosure, identification of an XR bearer field in radio bearer configuration signaling may be provided.

[0058] According to the present disclosure, UE capabilities supporting multiple DRX configurations and XR power saving may be provided.

[0059] According to the present disclosure, a configurable or dynamic offset for DRX advance / advance may be provided. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] The embodiments disclosed herein are shown in the accompanying drawings, and the same reference numerals indicate corresponding parts in the various drawings throughout the drawings. The embodiments disclosed herein will be better understood according to the following description with reference to the accompanying drawings.

[0061] Figure 1 A wireless network for managing power conservation for XR services according to embodiments disclosed herein is shown.

[0062] Figure 2 Various hardware components of a UE according to embodiments disclosed herein are shown.

[0063] Figure 3 Various hardware components of a network device according to embodiments disclosed herein are shown.

[0064] Figure 4 A flowchart of a method implemented by a UE for managing power saving of XR services in a wireless network according to an embodiment disclosed herein is shown.

[0065] Figure 5 A flowchart of a method for managing power conservation for XR services in a wireless network according to an embodiment disclosed herein is shown.

[0066] Figure 6 A flow chart illustrating configurable or dynamic offset operation of common DRX for XR and legacy unicast / non-XR reception according to embodiments disclosed herein is shown.

[0067] Figure 7 A flow chart illustrating an operational flow of active time determination for common DRX for XR and legacy unicast / non-XR reception according to embodiments disclosed herein.

[0068] Figure 8 A flow chart illustrating the operational flow of DRX timer operation for common DRX for XR and legacy unicast / non-XR reception when a MAC PDU is received in a configured downlink allocation according to embodiments disclosed herein.

[0069] Figure 9 A flow chart illustrating the operational flow of DRX timer operation for common DRX for XR and legacy unicast / non-XR reception when PDCCH indicates DL transmission according to embodiments disclosed herein.

[0070] Figure 10 A flow chart of a dynamic offset operation of DRX for XR service reception according to an embodiment disclosed herein is shown.

[0071] Figure 11 A flow chart illustrating an operational flow for active time determination for XR service reception according to embodiments disclosed herein.

[0072] Figure 12 A flow chart illustrating the operational flow of a DRX timer operation for DRX for XR service reception when a MAC PDU is received in a configured downlink allocation according to embodiments disclosed herein.

[0073] Figure 13 A flow chart illustrating the operational flow of a DRX timer operation for DRX for XR service reception when a PDCCH indicates a DL transmission according to an embodiment disclosed herein.

[0074] Figure 14 An electronic device according to an embodiment of the present disclosure is shown.

[0075] Figure 15 A network device according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0076] Discussed below Figures 1 to 15 The various embodiments used to describe the principles of the present disclosure in this patent document are for illustration only and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0077] The embodiments of the present invention and their various features and advantageous details are explained more fully with reference to the non-limiting embodiments shown in the accompanying drawings and described in detail in the following description. Descriptions of well-known components and processing techniques are omitted so as not to unnecessarily obscure the embodiments of the present invention. The examples used herein are intended only to facilitate understanding of the ways in which the embodiments of the present invention can be practiced, and further enable those skilled in the art to practice the embodiments of the present invention. Therefore, the examples should not be interpreted as limiting the scope of the embodiments of the present invention.

[0078] 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 a fundamental technology that enables the digital twin / metaverse. XR was incorporated as an agreed work item in the fifth generation (5G) advanced (i.e., the third generation partnership project (3GPP) release 18), with the goal of providing a communication system framework that meets the challenging requirements of high data rates, very low latency, and power-efficient connectivity for XR applications. In particular, to save power for XR, a discontinuous reception (DRX) mechanism may be required.

[0079] It is desirable to address the shortcomings or at least provide a useful alternative.

[0080] Without loss of generality or specificity, the provided embodiments can be interchangeably interpreted and applied to at least one XR service, bearer, logical channel, transport channel, physical channel, or QoS flow, etc.

[0081] The embodiments of the present invention implement a method for managing power saving of XR services in a wireless network. The method includes receiving, by a UE, a radio bearer configuration including an identifier field. The method includes determining, by the UE, whether the received radio bearer configuration includes an "isXR bearer" field as an identifier field. In addition, the method includes performing one of the following by the UE: when determining that the radio bearer configuration includes the "isXR bearer" field, identifying that the radio bearer is related to the XR service, and when determining that the radio bearer configuration does not include the "isXR bearer" field, identifying that the radio bearer is not related to the XR service.

[0082] The method can be used to manage power saving of XR in wireless communication, wherein a DRX mechanism for power saving (including the operation of a DRX timer for XR service reception) has been disclosed. Based on the provided method, an enhanced DRX mechanism ensures power saving as well as low latency for XR packet transmission. Therefore, the user experience and UE / network performance are improved.

[0083] Referring now to the drawings, and more particularly to Figures 1 to 13 , wherein like reference numerals designate corresponding features consistently throughout the drawings, at least embodiments are shown.

[0084] Figure 1 A wireless network (300) for managing XR services according to an embodiment disclosed herein is shown. The wireless network (300) may be, for example, but not limited to, a fourth generation (4G) network, a fifth generation (5G) network, a sixth generation (6G) network, an open radio access network (ORAN), etc. In an embodiment, the wireless network (300) includes a UE (100) and a network device (200). The UE (100) may be, for example, but not limited to, a laptop, a smartphone, a desktop computer, a notebook, a device-to-device (D2D) device, a vehicle-to-everything (V2X) device, a foldable phone, a smart TV, a tablet, an immersive device, and an Internet of Things (IoT) device. The network device (200) may be, for example, but not limited to, a gNB, an eNB, a new radio (NR) transceiver, etc.

[0085] The UE (100) receives a radio bearer configuration including an identifier field. In addition, the UE (100) determines whether the received radio bearer configuration includes an "isXR bearer" field as an identifier field. In an embodiment, upon determining that the radio bearer configuration includes the "isXR bearer" field, the UE (100) recognizes that the radio bearer is related to the XR service. In another embodiment, upon determining that the radio bearer configuration does not include the "isXR bearer" field, the UE (100) recognizes that the radio bearer is not related to the XR service.

[0086] In an embodiment, one or more dedicated RNTIs are utilized to receive or send multiple XR data or control channels. The allocation of RNTIs may be per XR bearer, per XR service, per XR stream / substream, or per XR logical channel. In an embodiment, the RNTI may also be assigned to a group of one of an XR bearer, or service, or stream, or substream, or logical channel. The RNTI may also be one or more of an XR-RNTI and an XR-CS-RNTI to address dynamic and / or semi-persistent and / or configured permission / allocation based scheduling of XR.

[0087] In an embodiment, scheduling based on each of XR-RNTI and XR-CS-RNTI for XR services / bearers can be based on a dedicated DRX configuration. In an embodiment, scheduling based on one or more of XR-RNTI and / or XR-CS-RNTI for XR services / bearers can also share the same DRX configuration, i.e., configure and utilize a grouping of DRX configurations.

[0088] In an embodiment, one or more XR service reception and / or transmission can be performed by reusing C-RNTI and / or CS-RNTI of unicast reception and / or transmission.

[0089] In an embodiment, each XR-RNTI and XR-CS-RNTI based on XR service / bearer scheduling shares the same DRX configuration with traditional unicast (or non-XR) reception.

[0090] In an embodiment, if XRdrx is configured for a MAC entity of a UE (100) in RRC_CONNECTED state, the MAC entity uses DRX operation to non-continuously monitor the PDCCH for XR reception (i.e., addressed to XR-RNTI and / or XR-CS-RNTI), which DRX operation is only used to configure the relevant activated serving cells for one or more XR services. The relevant activated serving cells for XR-RNTI or XR-CS-RNTI monitoring are configured according to the XR radio bearer in the RRC reconfiguration message from the network device (200) providing the "serving cell" to which the relevant XR service is to be provided. In an embodiment, the MAC entity uses DRX operation to non-continuously monitor the PDCCH of all activated serving cells for XR reception.

[0091] In an embodiment, separate PDCCH search spaces may be configured for legacy unicast (or non-XR) services and XR services.In an embodiment, more than one XR service may share a PDCCH search space.

[0092] In an embodiment, the MAC entity of the UE (100) may share a DRX on-duration timer (i.e., drx-onDurationTimer) and / or a DRX inactivity timer (i.e., drx-InactivityTimer) of an XR configuration of one or more XR services with a unicast (non-XR or legacy unicast) DRX configuration, however, based on latency requirements, the MAC entity may have a separate XR configuration for one or more XR services for a round trip time (RTT) timer (i.e., drx-HARQ-RTT-TimerDL-XR and / or drx-HARQ-RTT-TimerUL-XR) and / or a retransmission timer (i.e., drx-RetransmissionTimerDL-XR and / or drx-RetransmissionTimerUL-XR) in at least one of the downlink direction and the uplink direction, rather than the unicast (non-XR or legacy unicast) DRX configuration.

[0093] In an embodiment, the radio bearer configuration includes a field "isXR bearer" to distinguish or identify whether the radio bearer is related to XR. In an embodiment, at least one dedicated logical channel with at least one logical channel identifier (e.g., LC ID) or LCID range (e.g., XR control channel, XRCCH and / or XR service channel, XRTCH) is used to distinguish the reception and / or transmission of multiplexing and / or demultiplexing of XR control / service content from non-XR or traditional unicast control / service content. In this case, if the XR service is multiplexed with non-XR services and / or traditional unicast on the same MAC PDU, the XR service can also use the same C-RNTI / CS-RNTI. In addition, the embodiments of this article assume that XR-RNTI / XR-CS-RNTI is used for XR; however, it is obvious to those of ordinary skill in the art that C-RNTI / CS-RNTI can also be used for the described behavior without loss of generality.

[0094] In an embodiment, example specification text is provided showing operational details of XR DRX in conjunction with a unicast (or non-XR) DRX configuration.

[0095] Discontinuous Reception (DRX): The MAC entity may be configured by RRC with DRX functionality that controls the UE's PDCCH monitoring activity for the MAC entity's C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, AI-RNTI, SL-RNTI, SLCS-RNTI, SL Semi-Persistent Scheduling V-RNTI, XR-RNTI, and XR-CS-RNTI. When using DRX operation, the MAC entity may also monitor the PDCCH as required (as disclosed herein). When in RRC_CONNECTED, if DRX is configured, the MAC entity may monitor the PDCCH discontinuously using the DRX operation specified in this clause for all activated serving cells; otherwise, the MAC entity may monitor the PDCCH as specified in TS 38.213. While in RRC_CONNECTED, if XR DRX is configured, then for "relevant" activated serving cells, the MAC entity may monitor the PDCCH non-continuously using DRX operation as specified in this clause. Otherwise, the MAC entity may monitor the PDCCH as specified in TS 38.213.

[0096] RRC can control DRX operation by configuring the following parameters: a) drx-onDurationTimer : Duration when the DRX cycle starts; b) drx-SlotOffset :start drx-onDurationTimer Previous delay; c) drx-InactivityTimer : The duration after the PDCCH opportunity when the PDCCH indicates a new uplink (UL) or downlink (DL) transmission of the MAC entity; d) drx-RetransmissionTimerDL (per DL HARQ process, except broadcast process): maximum duration until a DL retransmission is received; e) drx-RetransmissionTimerUL (per UL HARQ process): maximum duration until a grant for UL retransmission is received; f) drx-LongCycleStartOffset : Long DRX cycle and drx-StartOffset , which defines the subframes at which the long DRX cycle and the short DRX cycle start; g) drx-ShortCycle (Optional): Short DRX cycle; h) drx-ShortCycleTimer (Optional): The UE (100) may follow the duration of the short DRX cycle; i) drx-HARQ-RTT-TimerDL (per DL HARQ process, except broadcast process): minimum duration before which the MAC entity expects a DL allocation for HARQ retransmission; j) drx-HARQ-RTT-TimerUL (per UL HARQ process): minimum duration before which the MAC entity expects a UL HARQ retransmission grant; k) ps-Wakeup (Optional): Start association if DCP is not detected. drx- onDurationTimer Configuration; l) drx-RetransmissionTimerDL-XR (Per DL HARQ process for XR): Maximum duration until a DL XR retransmission is received; m) drx-HARQ-RTT-TimerDL-XR (Per DL HARQ process for XR): Minimum duration before a DL XR allocation for HARQ retransmissions that the MAC entity expects; n) drx-RetransmissionTimerUL-XR (per UL HARQ process): maximum duration until a grant for UL retransmission is received; and o) drx-HARQ-RTT-TimerUL-XR (Per UL HARQ process): Minimum duration before the MAC entity expects a UL HARQ retransmission grant.

[0097] In an embodiment, a dynamic parameter (drx-StartOffsetXR-dyna) can be signaled by a network device (200) to a UE (100) which provides at least one of an advance or delay for starting a drx-onDurationTimer by a signaled offset value in order to receive XR. Such a change in the DRX start time is required due to an XR frame rate mismatch and / or a variation from the configured DRX and / or jitter in the arrival of XR data. In an embodiment, drx-StartOffsetXR-dyna may also consist of two parts or parameters, e.g., drx-StartOffsetXR and / or drx-slotOffsetXR, in order to have both a subframe offset and a slot level offset, respectively. The parameters drx-StartOffsetXR and / or drx-slotOffsetXR may be dynamically signaled by the network device (200) to the UE (100) by utilizing at least one of downlink control information (DCI, e.g., scheduling DCI), presence or absence or location of a wake-up signal (WUS) and / or embedded information (e.g., PDCCH / DCI based signaling), wake-up radio (WUR) sequence / pattern, or presence or absence and / or location of a MAC control element (CE).

[0098] The parameters drx-StartOffsetXR and / or drx-slotOffsetXR may be associated with one or more specific XR services, or may be commonly applicable to all configured XR services. The identification of the drx-StartOffsetXR and / or drx-slotOffsetXR parameters for a specific XR service is by an associated DCI, WUS, WUR or MAC CE addressed to (or scrambled by) an XR-RNTI or XR-CS-RNTI or C-RNTI, or at least one of an associated DCI, WUS, WUR or MAC CE carrying XR service field information. drx-StartOffsetXR and / or drx-slotOffsetXR may be applicable or valid within one or more DRX cycles, and the validity duration may also be indicated or configured to the UE (100).

[0099] In addition, drx-StartOffsetXR and / or drx-slotOffsetXR can be respectively defined and configured as "drx-StartOffsetXR-shortDRX and / or drx-slotOffsetXR-shortDRX" for a short DRX cycle and / or respectively defined and configured as "drx-StartOffsetXR-longDRX and / or drx-slotOffsetXR-LongDRX" for a long DRX cycle or respectively defined and configured as a common parameter "drx-StartOffsetXR and / or drx-slotOffsetXR" for a short DRX cycle and / or a long DRX cycle. In an alternative embodiment, a set of values ​​of drx-StartOffsetXR and / or drx-slotOffsetXR for one or more XR services is configured by the network device (200) through RRC (re)configuration, and the UE (100) applies the configured values ​​to advance or delay the start of drx-onDurationTimer based on receiving a DCI, WUS, WUR or MAC CE scrambled with XR-RNTI or XR-CS-RNTI or C-RNTI. In an example, an index to the set of configured values ​​is received or a bitmap or field representing the configured values ​​is received to be applied. This is in Figure 6 Shown in.

[0100] In the example, the following are the dynamic parameters: a) drx-StartOffsetXR : The advance or delay of starting drx-onDurationTimer in subframes or milliseconds; and b) drx-slotOffsetXR : Start the advance or delay of drx-onDurationTimer in time slots or sub-milliseconds.

[0101] In an embodiment, when one or more XR services are configured and / or accessed by the UE (100), the MAC entity determines the active time of DRX, such as Figure 7 The example specification is shown below: In an example, when DRX is configured, the active time for the serving cells in the DRX group includes the following times: a. For DRX group configuration drx-onDurationTimer or drx-InactivityTimer Running (consider when XR is configured drx-StartOffsetXR and / or drx-slotOffsetXR offset); or b. drx-RetransmissionTimerDL , drx-RetransmissionTimerUL , drx- RetransmissionTimerDL-XR ,drx-RetransmissionTimerUL-XR or drx- RetransmissionTimerSL is running on any serving cell in the DRX group; or c. ra-ContentionResolutionTimer or msgB-ResponseWindow is running; or d. Scheduling request is sent on PUCCH and is pending. If the serving cell is part of a non-terrestrial network, then for all SR configurations with pending SRs SR_COUNTER When 0, the activity time starts after the Scheduling Request transmission is performed plus the UE-gNB RTT; or e. After successfully receiving a random access response for a random access preamble that is not selected by the MAC entity among contention-based random access preambles, a new transmission indicating that the C-RNTI addressed to the MAC entity has not been received.

[0102] In an embodiment, at least one HARQ process configured or allocated for XR is separated from at least one HARQ process configured or allocated for traditional unicast (or non-XR) reception. The configuration or allocation can be based on at least one of the applicable time slot according to the configuration, the indicated RNTI, the HARQ process identifier, etc. The MAC entity determines that the HARQ process of the received MAC PDU in the configured downlink allocation for unicast is configured or allocated for XR or traditional unicast (or non-XR), and thus operates the relevant RTT timer for the downlink and / or the retransmission timer for the downlink. In addition, when the MAC entity determines that the HARQ process of the received MAC PDU in the configured downlink allocation for unicast is configured or allocated for XR, the MAC entity does not stop the drx-RetransmissionTimerDL-PTM for MBS point-to-multipoint groupcast.

[0103] In an embodiment, one or more HARQ processes for XR services are common and shared with traditional unicast or non-XR services. That is, multiplexing (or demultiplexing) of XR and non-XR services is allowed on the MAC transport block, and C-RNTI / CS-RNTI is used to address the MAC TB. Demultiplexing (or multiplexing) of XR and non-XR MAC SDUs is performed by the MAC demultiplexer (or Mux) entity using MAC header information (e.g., LCID field).

[0104] In an embodiment, the DRX process Figure 8 is depicted in and illustrated by the following example specification: In an example, when DRX is configured, the MAC entity may: 1> If a MAC PDU is received in a configured downlink allocation for unicast: 2> If the corresponding HARQ process is configured or allocated for XR: 3> Start the transmission for the corresponding HARQ process in the first symbol after the corresponding transmission carrying DL HARQ feedback ends drx-HARQ-RTT-TimerDL-XR ; 3> Stop the corresponding HARQ process drx-RetransmissionTimerDL-XR .

[0105] 2>Otherwise: 3> Start the transmission for the corresponding HARQ process in the first symbol after the corresponding transmission carrying DL HARQ feedback ends drx-HARQ-RTT-TimerDL ; 3> Stop the corresponding HARQ process drx-RetransmissionTimerDL 3> Stop the corresponding HARQ process drx-RetransmissionTimerDL-PTM .

[0106] In an embodiment, at least one HARQ process configured or allocated for XR is separated from at least one HARQ process configured or allocated for traditional unicast (or non-XR) reception. The MAC entity determines whether the HARQ process for the transmitted MAC PDU in the configured uplink grant is configured or allocated for XR or traditional unicast (or non-XR), and correspondingly, operates the relevant HARQ RTT timer for the uplink and / or the DRX retransmission timer for the uplink. This is illustrated by the example specification shown in Table 1.

[0107] [Table 1. Example]

[0108] In an embodiment, if the HARQ-RTT-TimerDL-XR expires and if data of the corresponding HARQ process is not successfully decoded, the MAC entity starts the drx-RetransmissionTimerDL-XR for the corresponding HARQ process in the first symbol after the HARQ-RTT-TimerDL-XR expires.

[0109] In an embodiment, if the HARQ-RTT-TimerUL-XR expires, the MAC entity starts the drx-RetransmissionTimerUL-XR for the corresponding HARQ process in the first symbol after the HARQ-RTT-TimerUL-XR expires.

[0110] In an embodiment, when the UE (100) is configured for XR services, the received drx-StartOffsetXR and / or drx-SlotOffsetXR are used to calculate the start of at least one of a short DRX cycle and a long DRX cycle. In addition, a common value of drx-StartOffsetXR and / or drx-SlotOffsetXR for all configured XR services is received and applied, or alternatively, specific values ​​for drx-StartOffsetXR and / or drx-SlotOffsetXR are received for one or more configured XR services, and the common value is derived (e.g., the UE (100) derives the common value by considering the maximum value among all values ​​of drx-StartOffsetXR and / or drx-SlotOffsetXR received in the positive direction and the negative direction (e.g., maximum (drx-StartOffsetXR + drx-SlotOffsetXR) or (drx-StartOffsetXRmax + drx-SlotOffsetXRmax) or maximum (drx-StartOffsetXR)). In addition, in an embodiment, the offsets in different activated cells may be different due to different XR services. In order to have the same DRX configuration and / or operation, a common calculated value or signaled value may be utilized.

[0111] [Table 2. Example]

[0112] In an embodiment, separate retransmission timers (e.g., drx-RetransmissionTimerDL-XR and drx-RetransmissionTimerUL-XR) and RTT timers (drx-HARQ-RTT-Timer DL-XR and drx-HARQ-RTT-TimerUL-XR) are configured for XR services. These timers are maintained separately for HARQ processes corresponding to DL receptions with XR-RNTI or XR-CS-RNTI.

[0113] In an embodiment, when short DRX is used for (or configured for) at least one XR service and a legacy unicast (or non-XR service), the network device (200) applies (or the UE (100) calculates and applies) a minimum short DRX for at least one of the XR service and the legacy unicast (or non-XR).

[0114] In an embodiment, DRX operation is performed in Figure 9 and as shown in Table 3 below.

[0115] [Table 3]

[0116] A PDCCH indicating activation of SPS, configured grant type 2, configured XR grant of configured grant type 2, or configured sidelink grant of configured grant type 2 is considered to indicate a new transmission, as shown in Table 4.

[0117] [Table 4]

[0118] In an embodiment, the MAC entity of the UE (100) may have additional timers for the DRX On Duration timer, DRX Inactivity timer, RTT timer (i.e., drx-HARQ-RTT-TimerDL-XR and / or drx-HARQ- RTT-TimerUL-XR ) and / or retransmission timer (i.e., drx-RetransmissionTimerDL-XR and / or drx- RetransmissionTimerUL-XR ) of a separate XR configuration for one or more XR services.

[0119] In an embodiment, example specification text is provided showing operational details of one or more XR DRX configurations.The one or more XR DRX configurations can be additional and / or independent of unicast (or non-XR) DRX configurations.

[0120] Discontinuous Reception (DRX) for XR: For XR, the MAC entity may be configured by RRC with DRX functionality per XR-RNTI or per XR-CS-RNTI, which controls the UE's PDCCH monitoring activity for the MAC entity's XR-RNTI and XR-CS-RNTI, as specified in TS38.331. When in RRC_CONNECTED, if XR DRX is configured, the MAC entity is allowed to discontinuously monitor the PDCCH for the XR-RNTI or XR-CS-RNTI using the XR DRX operation specified in this clause; otherwise, the MAC entity monitors the PDCCH for the XR-RNTI or XR-CS-RNTI, as specified in TS 38.213. The XR DRX operation specified in this clause is performed separately for each XR-RNTI or XR-CS-RNTI and is independent of the DRX operation specified in the 3GPP standard specification.

[0121] The RRC controls the operation of the XR DRX per XR-RNTI or per XR-CS-RNTI by configuring the following parameters: a. drx-onDurationTimerXR : duration of the DRX cycle or adjusted DRX cycle when it starts, if any; b. drx-SlotOffsetXR-static : drx-onDurationTimerXR Delay before starting; c. drx-InactivityTimerXR : The duration after the PDCCH opportunity when the PDCCH indicates a new DL or UL XR transmission of the MAC entity; d. drx-LongCycleStartOffsetXR : Defines the long DRX cycle of the subframe where the long DRX cycle starts drx- LongCycle-XR and drx-StartOffset-XR-static ; e. drx-RetransmissionTimerDL-XR (per DL HARQ process for XR): maximum duration before a DL XR retransmission is received; f. drx-HARQ-RTT-TimerDL-XR (per DL HARQ process for XR): minimum duration before which the MAC entity expects a DL XR allocation to perform a HARQ retransmission; g. drx-RetransmissionTimerUL-XR (per UL HARQ process): maximum duration before receiving a grant for UL retransmission; h. drx-HARQ-RTT-TimerUL-XR (per UL HARQ process): minimum duration before which the MAC entity expects a UL HARQ retransmission grant; and i. ps-WakeupXR (Optional): Start association if DCP is not detected. drx- onDurationTimerXR Configuration.

[0122] In an embodiment, the parameters drx-StartOffsetXR and / or drx-SlotOffsetXR may be dynamically signaled to the UE (100) by the network device (200) by utilizing at least one of downlink control information (DCI, e.g., scheduling DCI), presence or absence or location of a wake-up signal (WUS) and / or embedded information (e.g., PDCCH-based signaling), wake-up radio (WUR) sequence / pattern, or presence or absence and / or location of a MAC control element (CE). The parameters drx-StartOffsetXR and / or drx-SlotOffsetXR may be associated with one or more specific XR services (e.g., XR-RNTI or XR-CS-RNTI), or may be commonly applicable to all configured XR services. The identification of the drx-StartOffsetXR and / or drx-SlotOffsetXR parameters for a particular XR service is performed by an associated DCI, WUS, WUR or MAC CE addressed to (or scrambled by) an XR-RNTI or XR-CS-RNTI, or at least one of an associated DCI, WUS, WUR or MAC CE carrying XR service field information. The drx-StartOffsetXR and / or drx-slotOffsetXR may be applicable or valid in one or more DRX cycles, and the validity duration may also be indicated or configured to the UE (100).

[0123] In addition, drx-StartOffsetXR and / or drx-slotOffsetXR may be defined and configured as "drx-StartOffsetXR-shortDRX and / or drx-slotOffsetXR-shortDRX" for a short DRX cycle and / or as "drx-StartOffsetXR-longDRX and / or drx-slotOffsetXR-LongDRX" for a long DRX cycle or as "drx-StartOffsetXR-longDRX and / or drx-slotOffsetXR-LongDRX" for a short DRX cycle and / or or long DRX cycle are defined and configured as common parameters "drx-StartOffsetXR and / or drx-slotOffsetXR", respectively. In an alternative embodiment, a set of values ​​of drx-StartOffsetXR and / or drx-slotOffsetXR for one or more XR services are configured by the network device (200) through RRC (re)configuration, and the UE (100) applies the configured values ​​to advance or delay the start of drx-onDurationTimer based on receiving a DCI, WUS, WUR or MAC CE scrambled with XR-RNTI or XR-CS-RNTI, for example, receiving an index to a set of configured values ​​or receiving a bitmap or field indicating the configured values ​​to be applied. This Figure 10 Shown in.

[0124] In the examples, the following is used for dynamic parameters: a. drx-StartOffsetXR : Start in subframes or milliseconds drx-onDurationTimerXR the advancement or delay of b. drx-SlotOffsetXR : Start in time slots or sub-milliseconds drx-onDurationTimerXR advance or delay.

[0125] In an embodiment, when XR DRX is configured for an XR-RNTI or an XR-CS-RNTI, the active time includes when the drx-onDurationTimerXR or drx-InactivityTimerXR or drx- RetransmissionTimerDL-XR or drx-RetransmissionTimerUL-XR The time when a scheduling request for XR is sent on PUCCH and is pending. Figure 11 Shown in.

[0126] In an embodiment, if a MAC PDU is received in a configured downlink assignment for XR and if HARQ feedback is configured and / or enabled and / or sent, the MAC entity starts drx-HARQ-RTT-TimerDL-XR for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying DL HARQ feedback. Figure 12 Shown in.

[0127] When XR DRX is configured for XR-RNTI or XR-CS-RNTI, the MAC entity can be used for XR-RNTI or XR-CS-RNTI as shown in Table 5.

[0128] [Table 5]

[0129] In an embodiment, the start of drx-onDurationTimerXR is provided. If dynamic parameters are provided for XR services drx-StartOffsetXR and / or drx-SlotOffsetXR (e.g., addressed by XR-RNTI or XR-CS-RNTI), then based on drx-StartOffsetXR and / or drx-SlotOffsetXR to advance or delay drx-onDurationTimerXR The beginning of.

[0130] [Table 6. Example]

[0131] In an embodiment, if the PDCCH indicates a DL XR transmission and if HARQ feedback is configured and / or enabled and / or sent, the MAC entity starts the drx-HARQ-RTT-TimerDL-XR for the corresponding HARQ process in the first symbol after the corresponding transmission carrying the DL HARQ feedback ends. In addition, the MAC entity stops the drx-RetransmissionTimerDL-XR for the corresponding HARQ process. This Figure 13 Shown in.

[0132] In an embodiment, if the PDCCH indicates UL XR transmission, the MAC entity starts drx-HARQ-RTT-TimerUL-XR for the corresponding HARQ process in the first symbol after the first transmission (within a bundle) of the corresponding PUSCH transmission ends, and stops drx-HARQ-RTT-TimerUL-XR for the corresponding HARQ process. drx-RetransmissionTimerUL-XR , as shown in Table 7.

[0133] [Table 7. Example]

[0134] A PDCCH indicating activation of XR SPS or configured XR grant type 2 is considered to indicate a new transmission, as shown in Table 8.

[0135] [Table 8]

[0136] If it is not a complete PDCCH opportunity (eg, the active time for the XR-RNTI or XR-CS-RNTI starts or ends in the middle of a PDCCH opportunity), the MAC entity does not need to monitor the PDCCH for the XR-RNTI or XR-CS-RNTI.

[0137] Alternatively, in an embodiment, the network device (200) configures a plurality of DRX configuration parameters for the UE (100), such as drx-OnDurationTimer, drx-inactivityTimer, RTT timer and retransmission timer. An XR session is associated with one DRX configuration. The network device (200) signals which DRX configuration to use to monitor the PDCCH and the offset to apply to start the corresponding drx-OnDurationTimer via at least one of a DCI, a WUS, a WUR sequence and a MAC CE.

[0138] In an embodiment, when the PDCCH search spaces for XR and other legacy services are separated and the UE (100) is configured with a different DRX configuration for XR (such as any of the above embodiments), the UE (100) monitors only the PDCCH search space for XR during the DRX active time for XR and does not monitor the PDCCH search space for other services.

[0139] In an embodiment, if there is one or more DRX configurations for each XR service, the UE (100) monitors only the PDCCH search space for the XR service during the DRX active time for that service. If some XR services share the same DRX configuration, the UE (100) monitors only the PDCCH search space for those XR services during the DRX active time for those services.

[0140] In an embodiment, the UE (100) indicates the ability to support multiple DRX configurations through at least one of a UE capability exchange procedure and UE assistance information. The UE (100) also indicates whether the UE (100) supports power saving preferences for XR. In an example, the drx-preferenceXR included in the PowSavs-Parameters in the UE capability message indicates support for power saving preferences for XR. In addition, the UE (100) can be configured with DRX-PreferenceConfig-XR by the network device (200) to allow UE assistance information about the UE's XR DRX preference to achieve power saving, and to provide a prohibit timer for controlling the reporting frequency. The UE (100) also indicates the maximum number of DRX configurations that the UE can support. In another embodiment, the UE indicates the preference in the UE assistance information, at least one of the following, or a combination thereof: a) Common DRX configuration for legacy unicast and XR services, b) Separate DRX configurations for legacy unicast and XR services, and / or c) Common or per-service, preferred RTT and retransmission timer values ​​for XR services.

[0141] In an embodiment, if the cell group supports XR, the MAC-CellGroupConfig message for configuring MAC parameters for the cell group includes a drx-ConfigXR for establishing or releasing one or more XR services, and may include a drx-ConfigXR for drx-onDurationTimerXR , drx-inactivityTimerXR , drx-HARQ-RTT-TimerUL- XR , drx-HARQ-RTT-TimerDL-XR , drx-RetransmissionTimerUL-XR , drx- RetransmissionTimerDL-XR , drx-SlotOffsetXR-static , drx-Shortcyle-XR , drx- ShortcyTimer-XR , drx-LongCycle-XR and drx-StartOffsetXR-static XRDRX configuration parameters of at least one of .

[0142] In an embodiment, the MAC-CellGroupConfig message for configuring MAC parameters for a cell group includes the establishment or release of drx-Config and / or drx-ConfigSeconddaryGroup for conventional unicast, which can be shared for XR reception, and additionally includes at least one DRX parameter for XR reception, such as drx-HARQ-RTT-TimerUL-XR , drx-HARQ-RTT-TimerDL-XR , drx-RetransmissionTimerUL-XR , drx- RetransmissionTimerDL-XR ,drx-Shortcycycle-XR and drx-ShortcycleTimer-XR .

[0143] In an embodiment, one or more DRX configurations may be applied to one or more XR streams or streams or frame types of XR services, and the DRX configuration may be switched between multiple DRX configurations (e.g., different DRX configurations at different times), and the applicable DRX configuration is indicated by at least one of DCI, WUS, WUR, or MAC CE (e.g., using a bitmap or index of the applicable DRX configuration). The RNTI used for one or more XR DRX configurations and / or XR reception can be a C-RNTI or an XR-RNTI or one of multiple XR-RNTIs. The indicated DRX configuration may be applicable for a specified time and / or until a new DRX configuration is indicated. The multiple DRX configurations may differ in at least one parameter including: drx-onDurationTimerXR, drx-inactivityTimerXR, drx-HARQ-RTT-TimerUL-XR, drx-HARQ-RTT-TimerDL-XR, drx-RetransmissionTimerUL-XR, drx-RetransmissionTimerDL-XR, drx-SlotOffsetXR-static, drx-Shortcycle-XR, drx-ShortcycleTimer-XR, drx-LongCycle-XR, and drx-StartOffsetXR-static. In another embodiment, one or more DRX configurations may operate in parallel.

[0144] Figure 2 Various hardware components of a UE (100) according to an embodiment disclosed herein are shown. In an embodiment, the UE (100) includes a processor (110), a communicator (120), a memory (130), and an XR service controller (140). The processor (110) is coupled to the communicator (120), the memory (130), and the XR service controller (140).

[0145] The XR service controller (140) determines whether the radio bearer configuration includes an identifier field that is an "isXR bearer" field. In an embodiment, upon determining that the radio bearer configuration includes the "isXR bearer" field, the XR service controller (140) identifies that the radio bearer is related to the XR service. In another embodiment, upon determining that the radio bearer configuration does not include the "isXR bearer" field, the XR service controller (140) identifies that the radio bearer is not related to the XR service.

[0146] In an embodiment, the XR service controller (140) also receives a configurable value or a dynamic value of at least one of drx-StartOffsetXR and drx-slotOffsetXR in at least one of DCI, WUS, DCP, WUR, MAC CE, and RRC signaling from a network device (200) for the XR service. The configurable value is provided to the UE (100) via RRC signaling. The configurable value may be a set of one or more preconfigured values ​​that can be static or semi-static in nature. The dynamic value may be an index to the configurable value and can typically be provided via a faster signaling mechanism (e.g., MAC CE or DCI), and can be provided whenever the value of the offset to be applied needs to be changed.

[0147] In addition, the XR service controller (140) applies at least one of drx-StartOffsetXR and drx-slotOffsetXR as an advance or delay for starting drx-onDurationTimer for XR service reception. In addition, the XR service controller (140) applies at least one of drx-StartOffsetXR and drx-slotOffsetXR to calculate at least one of short DRX and long DRX for XR service reception. Short DRX generally involves a short DRX cycle that can switch from a DRX sleep state to a DRX on (DRX ON) state more quickly, thereby supporting lower latency, thereby supporting lower latency. Long DRX generally involves a long DRX for promoting higher power savings, but the transition time from the DRX sleep state to the DRX ON state is longer, thereby requiring a higher latency at the expense of higher latency.

[0148] In an embodiment, the XR service controller (140) also receives an RRC reconfiguration message including a set of configured values ​​for at least one of drx-StartOffsetXR and drx-slotOffsetXR. In addition, the XR service controller (140) applies at least one of the set of configured values ​​to change the start of drx-onDurationTimer based on an indication from at least one of DCI, WUS, DCP, WUR, and MAC CE scrambled using at least one of the received XR-RNTI, XR-CS-RNTI, C-RNTI, and CS-RNTI for the XR service. At least one of the values ​​from the set of configured values ​​is indicated by an index to the set of configured values ​​or a bitmap or field indicating the configured values ​​to be applied.

[0149] In an embodiment, the XR service controller (140) further configures at least one DRX configuration parameter from a plurality of DRX configurations for the UE (100). The at least one DRX configuration parameter includes a drx-OnDurationTimer, a drx-inactivityTimer, an RTT timer, and a retransmission timer. The network device configures at least one DRX configuration parameter from a plurality of DRX configurations for the UE (100). In addition, the XR service controller (140) associates the DRX configuration from the plurality of DRX configurations with the XR session for the XR service based on the at least one DRX configuration parameter.

[0150] In an embodiment, the XR service controller (140) further determines whether there is at least one DRX configuration for the XR service during the DRX active time. Furthermore, the XR service controller (140) monitors the PDCCH search space for the XR service during the DRX active time.

[0151] In an embodiment, the XR service controller (140) further indicates the capability of supporting multiple DRX configurations through at least one of a UE capability information exchange process and UE assistance information. In another embodiment, the XR service controller (140) further indicates in the UE capability message whether the UE (100) supports power saving preference for XR. In another embodiment, the XR service controller (140) further indicates the maximum number of DRX configurations supported by the UE (100).

[0152] In an embodiment, the XR service controller (140) also indicates in the UE assistance information a preference for at least one of: a common DRX configuration for legacy unicast and XR services, separate DRX configurations for legacy unicast and XR services, a common DRX configuration or a per-service DRX configuration, a preferred RTT timer value for XR services, and a preferred retransmission timer value.

[0153] In an embodiment, the XR service controller (140) further identifies whether at least two DRX configurations are applied to one or more XR service receptions. In addition, the XR service controller (140) switches between at least two DRX configurations from a plurality of DRX configurations. In addition, the XR service controller (140) receives an indication of a suitable DRX configuration among at least two DRX configurations for XR reception using at least one of DCI, WUS, WUR, and MAC CE. The indicated DRX configuration is applicable to a predefined time. The predefined time is set by the UE (100) and / or the network device (200). The DRX configurations differ in at least one parameter including at least one of the following: drx-onDurationTimer, drx-inactivityTimer, drx-HARQ-RTT-TimerUL, drx-HARQ-RTT-TimerDL, drx-RetransmissionTimerUL, drx-RetransmissionTimerDL, drx-SlotOffsetXR, drx-SlotOffsetXR-static, drx-Shortcycle, drx-ShortcycleTimer, drx-LongCycle, drx-StartOffsetXR and drx-StartOffsetXR-static.

[0154] In an embodiment, the XR service controller (140) further receives a MAC CellGroupConfig message. The MAC CellGroupConfig message configures MAC parameters for the cell group, the MAC parameters including at least one of setting of drx-Config for at least one of conventional unicast and XR service reception, setting of drx-ConfigSecondaryGroup, release of drx-Config, and release of drx-ConfigSecondaryGroup.

[0155] The XR service controller (140) is 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, hard-wired circuits, etc., and may optionally be driven by firmware.

[0156] In addition, the processor (110) is configured to execute instructions stored in the memory (130) and perform various processes. The communicator (120) is configured to communicate internally between internal hardware components and to communicate with external devices via one or more networks. The memory (130) also stores instructions to be executed by the processor (110). The memory (130) may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or an electrically programmable memory (EPROM) or an electrically erasable programmable (EEPROM) memory. In addition, in some examples, the memory (130) may 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 propagating signal. However, the term "non-transitory" should not be interpreted as the memory (130) being non-removable. In some examples, a non-transitory storage medium may store data that can change over time (e.g., in a random access memory (RAM) or a cache).

[0157] although Figure 2 Various hardware components of the UE (100) are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, the UE (100) may include fewer or greater numbers of components. In addition, the labels or names of the components are for illustrative purposes only and do not limit the scope of the present disclosure. One or more components can be combined together to perform the same or substantially similar functions in the UE (100).

[0158] Figure 3 Various hardware components of a network device (200) according to an embodiment disclosed herein are shown. The network device (200) includes a processor (210), a communicator (220), a memory (230), and an XR service controller (240). The processor (210) is coupled to the communicator (220), the memory (230), and the XR service controller (240).

[0159] The XR service controller (240) sends a radio bearer configuration including an identifier field as an "isXR bearer" field to a UE (100) in a wireless network (300) to identify that the radio bearer is related to the XR service. Based on the radio bearer configuration including the "isXR bearer" field, the XR service controller (240) manages the XR service in the wireless network (300).

[0160] In an embodiment, the XR service controller (240) further sends a configurable value or dynamic value for at least one of drx-StartOffsetXR and drx-slotOffsetXR to the UE (100) for XR service in at least one of DCI, WUS, DCP, WUR, MAC CE and RRC signaling.

[0161] In another embodiment, the XR service controller (240) further sends an RRC reconfiguration message including a set of configured values ​​for at least one of drx-StartOffsetXR and drx-slotOffsetXR to the UE (100) for the XR service. In another embodiment, the XR service controller (240) further configures DRX configuration parameters from a plurality of DRX configurations for the UE (100).

[0162] The XR service controller (240) is 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, hard-wired circuits, etc., and may optionally be driven by firmware.

[0163] In addition, the processor (210) is configured to execute instructions stored in the memory (230) and perform various processes. The communicator (220) is configured to communicate internally between internal hardware components and communicate with external devices via one or more networks. The memory (230) also stores instructions to be executed by the processor (210). The memory (230) may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or an electrically programmable memory (EPROM) or an electrically erasable programmable (EEPROM) memory. In addition, in some examples, the memory (230) may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not implemented in a carrier wave or a propagating signal. However, the term "non-transitory" should not be interpreted as the memory (230) being non-removable. In some examples, a non-transitory storage medium may store data that can change over time (e.g., in a random access memory (RAM) or a cache).

[0164] although Figure 3 Various hardware components of the network device (200) are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, the network device (200) may include fewer or greater numbers of components. In addition, the labels or names of the components are for illustrative purposes only and do not limit the scope of the present disclosure. One or more components can be combined together to perform the same or substantially similar functions in the network device (200).

[0165] Figure 4 A flow chart (400) is shown of a method implemented by a UE (100) for managing power saving of XR services in a wireless network (300) according to embodiments disclosed herein. Operations (402-408) are processed by an XR service controller (140).

[0166] At S402, the method includes receiving a radio bearer configuration including an identifier field. At step 404, the method includes determining whether the radio bearer configuration includes an "isXR bearer" field as an identifier field. At step 406, the method includes identifying that the radio bearer is related to the XR service when it is determined that the radio bearer configuration includes the "isXR bearer" field. At step 408, the method includes identifying that the radio bearer is not related to the XR service when it is determined that the radio bearer configuration does not include the "isXR bearer" field.

[0167] Figure 5 A flow chart (500) is shown of a method for managing power conservation of XR services in a wireless network (300) according to embodiments disclosed herein. Operations (502-504) are processed by an XR service controller (240).

[0168] At step 502, the method includes sending a radio bearer configuration including an identifier field as an "isXR bearer" field to a UE (100) in a wireless network (300) to identify that the radio bearer is related to the XR service. At step 504, the method includes managing the XR service in the wireless network based on the radio bearer configuration including the "isXR bearer" field (504).

[0169] Based on the provided approach, the enhanced DRX mechanism ensures power saving as well as low latency for XR packet transmission, thereby improving user experience and UE / network performance.

[0170] Figure 6 A flow chart (600) is shown of configurable or dynamic offset operations for common DRX for XR and legacy unicast / non-XR reception according to embodiments disclosed herein. Operations (602-606) are processed by the XR service controller (140).

[0171] In step 602, the MAC entity of the UE (100) receives configurable or dynamic values ​​of drx-StartOffsetXR and drx-slotOffsetXR in at least one of DCI, WUS, DCP, WUR, MAC CE, and RRC signaling from the network device (200). In step 604, the MAC entity applies drx-StartOffsetXR and drx-slotOffsetXR as an advance or delay for starting a drx-onDurationTimer "common" for one or more XR service reception and traditional unicast or non-XR service reception. In step 606, the MAC entity applies drx-StartOffsetXR and drx-slotOffsetXR to calculate at least one of short DRX and long DRX "common" for one or more XR service reception and traditional unicast or non-XR service reception.

[0172] Figure 7 A flow chart illustrating an operational flow of active time determination for common DRX for XR and legacy unicast / non-XR reception according to embodiments disclosed herein. Operations (702-706) are processed by the XR service controller (140).

[0173] At step 702 , the MAC entity of the UE ( 100 ) determines an active time of common DRX for one or more XR service receptions and conventional unicast / non-XR receptions. In step 704, the MAC entity of the UE (100) determines an activity time including a time during which at least one of the following conditions is maintained: such as a drx-onDurationTimer or a drx-InactivityTimer configured for the DRX group is running (when XR is configured, taking into account the offsets of drx-StartOffsetXR and / or drx-slotOffsetXR), or a drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-RetransmissionTimerDL-XR, drx-RetransmissionTimerUL-XR, or drx-RetransmissionTimerSL is running on any serving cell in the DRX group, or a ra-ContentionResolutionTimer or msgB-ResponseWindow is running, or a scheduling request is sent on the PUCCH and is pending, or a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity has not been received after successfully receiving a random access response for a random access preamble that was not selected by the MAC entity among contention-based random access preambles. At step 706 , the MAC entity of the UE ( 100 ) monitors the PDCCH and receives downlink in the determined active time for one or more XR service reception and conventional unicast / non-XR reception.

[0174] Figure 8 A flow chart (800) illustrating the operational flow of DRX timer operation for common DRX for XR and legacy unicast / non-XR reception when a MAC PDU is received in a configured downlink allocation according to embodiments disclosed herein. Operations (802-812) are handled by the XR service controller (140).

[0175] In step 802, the method includes determining whether a MAC PDU is received in the configured downlink allocation and whether a corresponding HARQ process is configured or allocated for XR for public DRX. When it is determined that a MAC PDU is not received in the configured downlink allocation, and if a corresponding HARQ process is not configured or allocated for XR for public DRX, then in step 804, the MAC entity starts a drx-HARQ-RTT TimerDL for the corresponding HARQ process in the first symbol after the corresponding transmission carrying DL HARQ feedback ends. In step 806, the MAC entity stops the drx-RetransmissionTimerDL for the corresponding HARQ process. In step 808, the MAC entity stops the drx-RetransmissionTimerDL-PTM for the corresponding HARQ process.

[0176] Upon determining that a MAC PDU is received in a configured downlink allocation, and if a corresponding HARQ process is configured or allocated for XR for common DRX, the MAC entity starts a drx-HARQ-RTT TimerDL-XR for the corresponding HARQ process in the first symbol after the corresponding transmission carrying DL HARQ feedback ends in step 810. In step 812, the MAC entity stops a drx-RetransmissionTimerDL-XR for the corresponding HARQ process.

[0177] Figure 9 A flow chart (900) showing the operational flow of DRX timer operation for common DRX for XR and legacy unicast / non-XR reception when PDCCH indicates DL transmission according to embodiments disclosed herein. Operations (902-912) are handled by the XR service controller (140).

[0178] In step 902, for common DRX, the method includes determining whether the PDCCH monitored in the active time indicates DL transmission and whether the corresponding HARQ process is configured or allocated for XR. When determining whether the PDCCH monitored in the active time does not indicate DL transmission, and if the corresponding HARQ process is not configured or allocated for XR, then in step 904, the MAC entity starts the drx-HARQ-RTT-TimerDL for the corresponding HARQ process in the first symbol after the corresponding transmission carrying DL HARQ feedback ends. In step 906, the MAC entity stops the drx-RetransmissionTimerDL of the corresponding HARQ process whose HARQ feedback is reported. In step 908, the MAC entity stops the drx-RetransmissionTimerDL-PTM for the corresponding HARQ process.

[0179] Upon determining that the PDCCH monitored in the active time indicates a DL transmission, and if the corresponding HARQ process is configured or allocated for XR, the MAC entity starts the drx-HARQ-RTT-TimerDL-XR for the corresponding HARQ process in the first symbol after the corresponding transmission carrying the DL HARQ feedback ends in step 910. In step 912, the MAC entity stops the drx-RetransmissionTimerDL-XR for the corresponding HARQ process for which the HARQ feedback is reported.

[0180] Figure 10 A flow chart (1000) is shown of dynamic offset operations for DRX for XR service reception according to embodiments disclosed herein. Operations (1002-1006) are processed by the XR service controller (140).

[0181] In step 1002, the MAC entity of the UE (100) receives a dynamic value of drx-StartOffsetXR and / or drx-slotOffsetXR in at least one of DCI, WUS, DCP, WUR and MAC CE from a network device (200) for at least one configured XR service. In step 1004, the MAC entity of the UE (100) applies drx-StartOffsetXR and / or drx-slotOffsetXR as an advance or delay for starting a drx-onDurationTimer for receiving the corresponding XR service. In step 1006, the MAC entity of the UE (100) applies drx-StartOffsetXR and / or drx-slotOffsetXR to calculate at least one of a short DRX and a long DRX for receiving the corresponding XR service.

[0182] Figure 11 A flowchart (1100) illustrates an operational flow for active time determination for XR service reception according to embodiments disclosed herein. Operations (1102-1106) are processed by the XR service controller (140).

[0183] At step 1102, the MAC entity of the UE (100) determines an active time for XR service reception. At step 1104, the MAC entity of the UE (100) determines an active time for XR service, the active time including a time for which at least one of the following conditions is maintained: drx-onDurationTimerXR or drx-InactivityTimerXR or drx-RetransmissionTimerDL-XR or drxRetransmissionTimerUL-XR such as for XR-RNTI or XR-CS-RNTI is running, and a scheduling request for XR is sent on PUCCH and is pending. At step 1106, the MAC entity of the UE (100) monitors PDCCH and receives a downlink in the active time determined for XR service reception.

[0184] Figure 12 A flow chart (1200) illustrating the operational flow of DRX timer operation for DRX of XR service reception when a MAC PDU is received in a configured downlink allocation according to embodiments disclosed herein. Operations (1202-1206) are processed by the XR service controller (140).

[0185] In step 1202, for DRX configured for XR service, the MAC entity determines that a MAC PDU is received in a downlink allocation configured for XR. Upon determining that a MAC PDU is received in a downlink allocation configured for XR, then in step 1204, if HARQ feedback is configured and / or enabled and / or sent, the MAC entity starts a drx-HARQ-RTT-TimerDL-XR for the corresponding HARQ process in the first symbol after the corresponding transmission carrying DL HARQ feedback ends. Then, upon determining that a MAC PDU is not received in a downlink allocation configured for XR, the operation loops back to step 1202. In step 1206, the MAC entity stops a drx-RetransmissionTimerDL-XR for the corresponding HARQ process.

[0186] Figure 13 A flow chart (1300) illustrating the operational flow of DRX timer operation for DRX for XR service reception when PDCCH indicates DL transmission according to embodiments disclosed herein. Operations (1302-1306) are processed by the XR service controller (140).

[0187] In step 1302, the UE (100) determines whether DRX is configured for XR service and whether the PDCCH monitored in the active time indicates DL transmission. Upon determining that DRX is configured for XR service and if the PDCCH monitored in the active time indicates DL transmission, then in step 1304, the MAC entity starts drx-HARQ-RTTTimerDL-XR for the corresponding HARQ process in the first symbol after the corresponding transmission carrying DL HARQ feedback ends. Upon determining that DRX is not configured for XR service and if the PDCCH monitored in the active time does not indicate DL transmission, the operation loops back to step 1302. In step 1306, the MAC entity stops drx-RetransmissionTimerDL-XR for the corresponding HARQ process for which its HARQ feedback is reported.

[0188] According to an embodiment, a method performed by a user equipment (UE) in a communication system may be provided.

[0189] According to an embodiment, the method may include receiving a radio bearer configuration including an identifier field.

[0190] According to an embodiment, the method may include determining whether the radio bearer configuration includes an isXR bearer field as an identifier field.

[0191] According to an embodiment, one of the following is identified: based on determining that the radio bearer configuration includes the isXR bearer field, identifying that the radio bearer is related to an extended reality (XR) service, or based on determining that the radio bearer configuration does not include the isXR bearer field, identifying that the radio bearer is not related to the XR service.

[0192] According to an embodiment, the method may include receiving, from a network device for at least one XR service, a configurable value associated with the XR service or a dynamic value associated with the XR service of at least one of drx-StartOffsetXR or drx-slotOffsetXR for at least one of downlink control information (DCI), a wake-up signal (WUS), a DCI with a cyclic redundancy code (CRC) scrambled by a power saving radio network temporary identity (PS-RNTI) (DCP), a wake-up radio (WUR), a medium access control control element (MAC CE), or a radio resource control (RRC) signaling.

[0193] According to an embodiment, the method may include applying at least one of drx-StartOffsetXR or drx-slotOffsetXR as an advance or delay for starting drx-onDurationTimer for XR service reception.

[0194] According to an embodiment, the method may include applying at least one of drx-StartOffsetXR or drx-slotOffsetXR to calculate at least one of short discontinuous reception (DRX) or long DRX for XR service reception.

[0195] According to an embodiment, at least one of XR service reception or XR service transmission can be performed by reusing at least one of a cell radio network temporary identifier (C-RNTI) or a configured scheduling radio network temporary identifier (CS-RNTI) for unicast reception or unicast transmission.

[0196] According to an embodiment, wherein the XR service may use at least one of the C-RNTI or the CS-RNTI when the XR service is multiplexed with at least one of the non-XR service or the legacy unicast on the same medium access control protocol data unit (MAC PDU).

[0197] According to an embodiment, the method may include receiving a radio resource control (RRC) reconfiguration message including a set of configured values ​​for at least one of drx-StartOffsetXR or drx-slotOffsetXR.

[0198] According to an embodiment, the method may include applying at least one value from the set of configured values ​​to change the start instance of the drx-onDurationTimer based on an indication from at least one of a DCI, a WUS, a DCP, a WUR, and a MAC CE encrypted using at least one of a received XR-RNTI, an XR-CS-RNTI, a C-RNTI, or a CS-RNTI for an XR service.

[0199] According to an embodiment, at least one value from the set of configured values ​​may be indicated by an index to the set of configured values ​​or a bitmap or field representing the configured value to be applied.

[0200] According to an embodiment, the method may include receiving information to configure at least one DRX configuration parameter from a plurality of DRX configurations for the UE, wherein the at least one DRX configuration parameter includes at least one of a drx-OnDurationTimer, a drx-inactivityTimer, a round trip time (RTT) timer, or a retransmission timer.

[0201] According to an embodiment, the method may include associating a DRX configuration from a plurality of DRX configurations with an XR session for the XR service based on at least one DRX configuration parameter.

[0202] According to an embodiment, the method may include determining whether there is at least one DRX configuration for the XR service during the DRX active time.

[0203] According to an embodiment, the method may include monitoring a physical downlink control channel (PDCCH) search space for XR services during the DRX active time.

[0204] According to an embodiment, the method may include indicating at least one of: the ability to support multiple DRX configurations through at least one of the UE capability information exchange process or the UE assistance information; whether the UE in the UE capability message supports power saving preference for XR; the maximum number of DRX configurations supported by the UE; or a preference for at least one of the following in the UE assistance information: a common DRX configuration for legacy unicast and XR services, separate DRX configurations for legacy unicast and XR services, a common DRX configuration or a per-service DRX configuration, or a preferred RTT timer value and a preferred retransmission timer value for XR services.

[0205] According to an embodiment, the method may include identifying whether at least two DRX configurations are applied to one or more XR service receptions.

[0206] According to an embodiment, the method may comprise switching between at least two DRX configurations from a plurality of DRX configurations.

[0207] According to an embodiment, the method may include receiving an indication of a suitable DRX configuration among at least two DRX configurations for XR reception using at least one of DCI, WUS, WUR or MAC CE.

[0208] According to an embodiment, the indicated DRX configuration may be applicable for a predefined time.

[0209] According to an embodiment, the method may include receiving a MAC CellGroupConfig message, wherein the MAC CellGroupConfig message configures medium access control (MAC) parameters for the cell group, the MAC parameters including at least one of setting of drx-Config for at least one of legacy unicast or XR service reception, setting of drx-ConfigSecondaryGroup, release of drx-Config, or release of drx-ConfigSecondaryGroup.

[0210] According to an embodiment, the DRX configuration may differ in at least one parameter including at least one of the following: drx-onDurationTimer, drx-inactivityTimer, drx-HARQ-RTT-TimerUL, drx-HARQ-RTT-TimerDL, drx-RetransmissionTimerUL, drx-RetransmissionTimerDL, drx-SlotOffsetXR, drx-SlotOffsetXR-static, drx-Shortcycle, drx-ShortcycleTimer, drx-LongCycle, drx-StartOffsetXR or drx-StartOffsetXR-static.

[0211] According to an embodiment, the HARQ process for XR services may be a common and shared process with traditional unicast or non-XR services.

[0212] According to an embodiment, a method performed by a network device in a communication system may be provided.

[0213] According to an embodiment, the method may include sending a radio bearer configuration including an identifier field as an isXR bearer field to a user equipment (UE) to identify that the radio bearer is related to an extended reality (XR) service.

[0214] According to an embodiment, the method may include managing XR services in the wireless network based on a radio bearer configuration including an isXR bearer field.

[0215] According to an embodiment, the method may include performing at least one of the following: sending a configurable value or a dynamic value to the UE, the configurable value or the dynamic value being used for at least one of drx-StartOffsetXR or drx-slotOffsetXR of at least one of downlink control information (DCI) for XR services, a wake-up signal (WUS), a DCI with a cyclic redundancy code (CRC) scrambled by a power saving radio network temporary identifier (PS-RNTI) (DCP), a wake-up radio (WUR), a medium access control control element (MAC CE), or a radio resource control (RRC) signaling.

[0216] According to an embodiment, the method may include sending an RRC reconfiguration message to the UE, the RRC reconfiguration message including a set of configured values ​​for at least one of drx-StartOffsetXR or drx-slotOffsetXR for the XR service.

[0217] According to an embodiment, the method may include configuring at least one DRX configuration parameter from a plurality of DRX configurations for the UE.

[0218] Figure 14 An electronic device according to an embodiment of the present disclosure is shown.

[0219] refer to Figure 14 , the electronic device 1400 may include a processor 1410, a transceiver 1420, and a memory 1430. However, all the components shown are not required. The electronic device 1400 may be composed of Figure 14 In addition, according to another embodiment, the processor 1410, the transceiver 1420, and the memory 1430 may be implemented as a single chip.

[0220] The electronic device 1400 may correspond to the above-mentioned UE.

[0221] The above-mentioned components will now be described in detail.

[0222] The processor 1410 may include one or more processors or other processing devices that control the functions, processes and / or methods provided. The operations of the electronic device 1400 may be implemented by the processor 1410.

[0223] The transceiver 1420 may include an RF transmitter for up-converting and amplifying a transmission signal, and an RF receiver for down-converting the frequency of a reception signal. However, according to another embodiment, the transceiver 1420 may be implemented by more or less components than those shown in the components.

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

[0225] The memory 1430 may store control information or data included in the signal obtained by the electronic device 1400. The memory 1430 may be connected to the processor 1410 and store at least one instruction or protocol or parameter for the provided functions, processes and / or methods. The memory 1430 may include a read-only memory (ROM) and / or a random access memory (RAM) and / or a hard disk and / or a CD-ROM and / or a DVD and / or other storage devices.

[0226] Figure 15 A network device according to an embodiment of the present disclosure is shown.

[0227] refer to Figure 15, the network device 1500 may include a processor 1510, a transceiver 1520, and a memory 1530. However, all of the components shown are not required. The network device 1500 may be composed of Figure 15 In addition, according to another embodiment, the processor 1510, the transceiver 1520, and the memory 1530 may be implemented as a single chip.

[0228] The above-mentioned components will now be described in detail.

[0229] Processor 1510 may include one or more processors or other processing devices that control the functions, processes, and / or methods provided. The operations of network device 1500 may be implemented by processor 1510.

[0230] The transceiver 1520 may include an RF transmitter for up-converting and amplifying a transmission signal, and an RF receiver for down-converting the frequency of a reception signal. However, according to another embodiment, the transceiver 1520 may be implemented by more or less components than those shown in the components.

[0231] The transceiver 1520 may be connected to the processor 1510 and transmit and / or receive signals. The signals may include control information and data. In addition, the transceiver 1520 may receive signals through a wireless channel and output the signals to the processor 1510. The transceiver 1520 may transmit signals output from the processor 1510 through a wireless channel.

[0232] The memory 1530 may store control information or data included in the signal obtained by the network device 1500. The memory 1530 may be connected to the processor 1510 and store at least one instruction or protocol or parameter for the provided functions, processes and / or methods. The memory 1530 may include a read-only memory (ROM) and / or a random access memory (RAM) and / or a hard disk and / or a CD-ROM and / or a DVD and / or other storage devices.

[0233] The various actions, actions, boxes, steps, etc. in the flowcharts (400-1300) may be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some actions, actions, boxes, steps, etc. may be omitted, added, modified, skipped, etc. without departing from the scope of the present disclosure.

[0234] The embodiments disclosed herein can be implemented by at least one software program running on at least one hardware device and performing network management functions to control an element. An element may be at least one of a hardware device or a combination of a hardware device and a software module.

[0235] The foregoing description of specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, easily modify and / or adjust such specific embodiments for various applications without departing from the general concepts, and therefore, such adjustments and modifications should and are intended to be understood within the meaning and scope of equivalents of the disclosed embodiments. It should be understood that the wording or terminology employed herein is for descriptive and not limiting purposes. Therefore, although the embodiments herein have been described in terms of at least one embodiment herein, those skilled in the art will recognize that the embodiments herein can be practiced with modifications within the spirit and scope of the embodiments described herein.

[0236] Although the present disclosure has been described by various embodiments, various changes and modifications may be suggested to one skilled in the art. The present disclosure is intended to encompass such changes and modifications as fall within the scope of the appended claims.

Claims

1. A method performed by a user equipment UE in a communication system, the method comprising: receiving a radio bearer configuration associated with the radio bearer; Determining whether the radio bearer configuration includes an identifier field associated with extended reality XR; as well as Based on determining that the radio bearer configuration includes the identifier field, identifying that the radio bearer is associated with an XR service.

2. The method according to claim 1, further comprising: performing XR service communications associated with the XR service based on the identifying, The XR service communication is scheduled based on a physical downlink control channel PDCCH addressed to one of the first radio network temporary identifier RNTI or the second RNTI, The first RNTI is one of a cell-RNTI C-RNTI or a configured scheduling-RNTI CS-RNTI, and The second RNTI is one of XR-RNTI and XR-CS-RNTI.

3. The method according to claim 2, wherein: In case the PDCCH is addressed to the first RNTI, the XR service communications are multiplexed with communications associated with non-XR services.

4. The method according to claim 1, wherein: The hybrid automatic repeat request HARQ process for the XR service is a process shared with the HARQ process for the non-XR service.

5. The method according to claim 1, further comprising: receiving configuration information associated with a plurality of discontinuous reception (DRX) configurations; as well as A PDCCH search space for the XR service is monitored based on a first DRX configuration among the multiple DRX configurations.

6. The method according to claim 5, wherein: The multiple DRX configurations differ from each other in at least one DRX parameter including at least one of the following: drx-onDurationTimer, drx-inactivityTimer, drx-HARQ-RTT-TimerUL, drx-HARQ-RTT-TimerDL, drx-RetransmissionTimerUL, drx-RetransmissionTimerDL, drx-SlotOffsetXR, drx-SlotOffsetXR-static, drx-Shortcycle, drx-ShortcycleTimer, drx-LongCycle, drx-StartOffsetXR or drx-StartOffsetXR-static.

7. The method according to claim 5, further comprising: Switching to a second DRX configuration among the multiple DRX configurations, wherein the second DRX configuration is different from the first DRX configuration; and A PDCCH search space for the XR service is monitored based on the second DRX configuration.

8. A user equipment UE in a communication system, the UE comprising: Transceiver; as well as a processor coupled to the transceiver and configured to: receiving a radio bearer configuration associated with the radio bearer; Determining whether the radio bearer configuration includes an identifier field associated with extended reality XR; and Based on determining that the radio bearer configuration includes the identifier field, identifying that the radio bearer is associated with an XR service.

9. The UE according to claim 8, wherein: The processor is further configured to: perform XR service communications associated with the XR service based on the identifying, The XR service communication is scheduled based on a physical downlink control channel PDCCH addressed to one of the first radio network temporary identifier RNTI or the second RNTI, The first RNTI is one of a cell-RNTI C-RNTI or a configured scheduling-RNTI CS-RNTI, and The second RNTI is one of XR-RNTI and XR-CS-RNTI.

10. The UE according to claim 9, wherein: In case the PDCCH is addressed to the first RNTI, the XR service communications are multiplexed with communications associated with non-XR services.

11. The UE according to claim 8, wherein: The hybrid automatic repeat request HARQ process for the XR service is a process shared with the HARQ process for the non-XR service.

12. The UE according to claim 8, wherein: The processor is further configured to: receiving configuration information associated with a plurality of discontinuous reception (DRX) configurations; and A PDCCH search space for the XR service is monitored based on a first DRX configuration among the multiple DRX configurations.

13. The UE according to claim 12, wherein: The multiple DRX configurations differ from each other in at least one parameter including at least one of the following items: drx-onDurationTimer, drx-inactivityTimer, drx-HARQ-RTT-TimerUL, drx-HARQ-RTT-TimerDL, drx-RetransmissionTimerUL, drx-RetransmissionTimerDL, drx-SlotOffsetXR, drx-SlotOffsetXR-static, drx-Shortcycle, drx-ShortcycleTimer, drx-LongCycle, drx-StartOffsetXR or drx-StartOffsetXR-static.

14. A method performed by a network device in a communication system, the method comprising: Identify whether the radio bearer is associated with an extended reality (XR) service; Based on identifying that the radio bearer is associated with the XR service, sending a radio bearer configuration associated with the radio bearer, wherein the radio bearer configuration includes an identifier field associated with the XR; and Performing communications associated with the XR service.

15. A network device in a communication system, the network device comprising: Transceiver; as well as a processor coupled to the transceiver and configured to: Identify whether the radio bearer is associated with an extended reality (XR) service; Based on identifying that the radio bearer is associated with the XR service, sending a radio bearer configuration associated with the radio bearer, wherein the radio bearer configuration includes an identifier field associated with the XR; and Performing communications associated with the XR service.

Images