Method and apparatus for power saving mechanism for XR traffic

By introducing non-integer DRX cycle and DCP duration mechanisms into XR service, the power saving problem of XR service is solved, the matching and jitter adjustment between DRX and service arrival is realized, and the power management efficiency of XR service is improved.

CN118985145APending Publication Date: 2024-11-19LENOVO (BEIJING) LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280094660.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-05-27
Publication Date
2024-11-19

AI Technical Summary

Technical Problem

The existing extended reality (XR) services have challenges in power saving, especially because the non-integer cycle of XR services causes the DRX cycle to mismatch the service arrival, the SFN surround causes the DRX turn-on duration to mismatch the XR service arrival, and Dynamically monitor the PDCCH to save power difficulties considering the timing of jitter arrival.

Method used

By introducing a non-integer DRX loop mechanism in user equipment (UE) and network nodes, the inactivity timer start timing of the DRX group is delayed until the last transmission in multiple time slots is over, and the non-integer period DCP duration is used instead DRX-On-Duration, monitors the DRX-On-Duration bitmap to indicate the PDCCH transmission timing, and adjusts the DRX operation according to the jitter range information.

Benefits of technology

It effectively solves the problem of mismatch between DRX cycle and service arrival in the XR service characteristics, improves the power saving efficiency of XR service, dynamically monitors PDCCH to reduce power consumption, adapts to multi-slot scheduling, and improves the power management capabilities of XR service.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118985145A_ABST
    Figure CN118985145A_ABST
Patent Text Reader

Abstract

Embodiments of the invention relate to a method and apparatus for a power saving mechanism for augmented reality (XR) traffic. In accordance with an embodiment of the present application, a user equipment (UE) includes a processor and a transceiver coupled to the processor; and the processor is configured to: receive, via the transceiver, a first configuration of one or more serving cells in a discontinuous reception (DRX) group from a network, where the first configuration includes at least one of: DRX cycle information for determining a non-integer length value of a DRX cycle; or DRX start offset information indicating an offset value associated with a reference system frame number (SFN) in the time domain; and determining a first start timing of an opening duration window of the DRX group in the time domain according to at least one of the DRX cycle information or the DRX start offset information.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present application generally relate to wireless communication technology, and in particular, to methods and apparatus for power saving mechanisms for extended reality (XR) services. Background Art

[0002] Extended reality (XR) (including augmented reality (AR) and virtual reality (VR)) and cloud gaming (CG) bring new and promising categories of connected devices, applications and services. As a potential work area of ​​3GPP (3rd Generation Partnership Project) Rel-18, power saving of XR devices is one of the key topics. Currently, the details of power saving mechanisms for XR services have not been discussed. Summary of the invention

[0003] Some embodiments of the present application also provide a user equipment (UE). The UE includes a processor and a transceiver coupled to the processor; and the processor is configured to: receive a first configuration of one or more service cells in a discontinuous reception (DRX) group from a network via the transceiver, wherein the first configuration includes at least one of the following: DRX cycle information, which is used to determine a non-integer length value of the DRX cycle; or DRX start offset information, which indicates an offset value related to a reference system frame number (SFN) in a time domain; and determine a first start timing of an on-duration window of the DRX group in the time domain according to at least one of the DRX cycle information or the DRX start offset information.

[0004] In some embodiments, the processor of the UE is configured to determine a second start timing of the on-duration window of the DRX group in the time domain according to at least one of the DRX cycle information or the DRX start offset information.

[0005] In some embodiments, the first configuration further includes information associated with the reference SFN, and at least one of the first start timing or the second start timing of the on-duration window is further determined according to the information associated with the reference SFN.

[0006] In some embodiments, the DRX cycle information comprises one of: a downlink (DL) frame rate in the time domain, wherein the non-integer length value is determined based on the DL frame rate; and the non-integer length value.

[0007] In some embodiments, the unit is the offset value, which is associated with one of: a subframe, a slot, and a symbol.

[0008] In some embodiments, the processor of the UE is configured to: receive a second configuration of the one or more service cells in the DRX group from the network via the transceiver, wherein the second configuration indicates a subset of the on-duration window; and monitor a physical downlink control channel (PDCCH) transmission in the subset of the on-duration window according to the second configuration.

[0009] In some embodiments, the second configuration includes at least one of: a bitmap indication associated with the on-duration windows; or a list of information associated with one or more subsets of the on-duration windows.

[0010] In some embodiments, the information list indicates at least one of: a start timing of a subset within the one or more subsets of the on-duration windows; or a length of the subset within the one or more subsets of the on-duration windows.

[0011] In some embodiments, at least one of the first start timing of the on-duration window, the second start timing of the on-duration window, or the start timing of the subset within the one or more subsets is a start subframe or a start slot or a start symbol.

[0012] In some embodiments, the second configuration indicates which opportunities in the time domain are required to monitor the PDCCH transmissions in the subset of the On-Duration windows.

[0013] In some embodiments, the second configuration is received via radio resource control (RRC) signaling or a dynamic command.

[0014] In some embodiments, the processor of the UE is configured to: transmit jitter range information to the network via the transceiver, and wherein the jitter range information includes at least one of: a UL jitter range of data arrival time at the UE; or a probability of the UL jitter range.

[0015] In some embodiments, the processor of the UE is configured to receive, from the network via the transceiver on a serving cell in the DRX group, a single downlink control information (DCI) for scheduling multiple time slots in the time domain for a downlink (DL) or uplink (UL) of the UE, and wherein each time slot within the multiple time slots corresponds to a unique hybrid automatic repeat request (HARQ) process of the UE.

[0016] In some embodiments, in response to the single DCI for scheduling the multiple time slots for the DL or the UL and in response to receiving a PDCCH transmission on the serving cell in the DRX group indicating a new DL or UL transmission within the multiple time slots, the processor of the UE is configured to: not start the DRX inactivity timer for the DRX group; or delay the start timing of the DRX inactivity timer for the DRX group until the first symbol that appears in the time domain after the end of the timing of the last physical downlink shared channel (PDSCH) transmission within the multiple time slots.

[0017] In some embodiments, in response to the single DCI for scheduling the multiple time slots for the UL and in response to expiration of a DRX HARQ round trip time (RTT) timer for a physical uplink shared channel (PUSCH) transmission within the multiple time slots for a corresponding hybrid automatic repeat request (HARQ) process, the processor of the UE is configured to start a DRX retransmission timer for the UL for the corresponding HARQ process at a subsequent timing between: a symbol that first appears in the time domain after the expiration of the DRX HARQ RTT timer for the UL; and a symbol that first appears in the time domain after the end of the timing of the last PUSCH transmission within the multiple time slots.

[0018] Some embodiments of the present application also provide a user equipment (UE). The UE includes a processor and a transceiver coupled to the processor; and the processor is configured to: receive a second configuration of one or more serving cells in a discontinuous reception (DRX) group from a network via the transceiver, wherein the second configuration indicates a subset of an on-duration window of the DRX group in a time domain; and monitor a physical downlink control channel (PDCCH) transmission in the subset of the on-duration window according to the second configuration.

[0019] In some embodiments, the second configuration includes at least one of: a bitmap indication associated with the on-duration windows; or a list of information associated with one or more subsets of the on-duration windows.

[0020] In some embodiments, the information list indicates at least one of: a start timing of a subset within the one or more subsets of the on-duration windows; or a length of the subset within the one or more subsets of the on-duration windows.

[0021] In some embodiments, the second configuration indicates which opportunities in the time domain are required to monitor the PDCCH transmissions in the subset of the On-Duration windows.

[0022] In some embodiments, the processor of the UE is configured to: receive first information associated with the length of the DRX on-duration window from the network via the transceiver; receive DRX time slot offset information indicating a time slot delay value before starting the DRX on-duration window in the time domain from the network via the transceiver; receive second information associated with the DRX cycle in the time domain and the start offset value of the DRX cycle from the network via the transceiver; and determine the first start timing of the on-duration window of the DRX group in the time domain based on at least one of the first information, the DRX time slot offset information or the second information.

[0023] In some embodiments, the processor of the UE is configured to determine a second start timing of the on-duration window in the time domain according to at least one of the first information, the DRX slot offset information, or the second information.

[0024] In some embodiments, the processor of the UE is configured to: receive a first configuration of the one or more service cells in the DRX group from the network via the transceiver, wherein the first configuration includes at least one of the following: DRX cycle information, which is used to determine a non-integer length value of the DRX cycle; or DRX start offset information, which indicates an offset value related to a reference system frame number (SFN) in the time domain; and determine a first start timing of the open duration window of the DRX group in the time domain based on at least one of the DRX cycle information or the DRX start offset information.

[0025] In some embodiments, the processor of the UE is configured to determine a second start timing of the on-duration window in the time domain according to at least one of the DRX cycle information or the DRX start offset information.

[0026] In some embodiments, at least one of the start timing of the subset within the one or more subsets, the first start timing of the on-duration window, or the second start timing of the on-duration window is a start subframe or a start slot or a start symbol.

[0027] In some embodiments, the first configuration further includes information associated with the reference SFN, and wherein the start timing of the on-duration window is further determined according to the information associated with the reference SFN.

[0028] In some embodiments, the DRX cycle information comprises one of: a downlink (DL) frame rate in the time domain, wherein the non-integer length value is determined based on the DL frame rate; and the non-integer length value.

[0029] In some embodiments, the unit is the offset value, which is associated with one of: a subframe, a slot, and a symbol.

[0030] In some embodiments, the processor of the UE is configured to: transmit jitter range information to the network via the transceiver, and wherein the jitter range information includes at least one of: a UL jitter range of data arrival time at the UE; or a probability of the UL jitter range.

[0031] In some embodiments, the processor of the UE is configured to receive, from the network via the transceiver on a serving cell in the DRX group, a single downlink control information (DCI) for scheduling multiple time slots in the time domain for a downlink (DL) or uplink (UL) of the UE, and wherein each time slot within the multiple time slots corresponds to a unique hybrid automatic repeat request (HARQ) process of the UE.

[0032] In some embodiments, in response to the single DCI for scheduling the multiple time slots for the DL or the UL and in response to receiving a PDCCH transmission indicating a new DL or UL transmission within the multiple time slots, the processor of the UE is configured to: not start the DRX inactivity timer of the DRX group, or delay the start timing of the DRX inactivity timer of the DRX group until the first symbol that appears in the time domain after the end of the timing of the last physical downlink shared channel (PDSCH) transmission within the multiple time slots.

[0033] In some embodiments, in response to the single DCI for scheduling the multiple time slots for the UL and in response to expiration of a DRX HARQ round trip time (RTT) timer for a physical uplink shared channel (PUSCH) transmission within the multiple time slots for a corresponding hybrid automatic repeat request (HARQ) process, the processor of the UE is configured to start a DRX retransmission timer for the UL for the corresponding HARQ process at a subsequent timing between: a symbol that first appears in the time domain after the expiration of the DRX HARQ RTT timer for the UL; and a symbol that first appears in the time domain after the end of the timing of the last PUSCH transmission within the multiple time slots.

[0034] Some embodiments of the present application also provide a user equipment (UE). The UE includes a processor and a transceiver coupled to the processor; and the processor is configured to receive a configuration of downlink control information (DCI) (DCP) functionality having a cyclic redundancy check (CRC) scrambled by a power-saving radio network temporary identifier (PS-RNTI) from a network via the transceiver, wherein the configuration includes at least one of the following: DCP cycle information, which is used to determine a non-integer length value of the DCP cycle; DCP start offset information, which indicates an offset value related to a reference system frame number (SFN) in the time domain; DCP time slot offset information, which indicates a time slot delay value before starting a DCP on-duration window in the time domain; or DCP on-duration information, which indicates which opportunities in the time domain are required for monitoring a physical downlink control channel (PDCCH) transmission in the on-duration window of the DCP cycle.

[0035] In some embodiments, the processor of the UE is configured to determine a start timing of an on-duration window of a DRX cycle in the time domain according to at least one of the DCP timeslot offset information, the DCP cycle information, or the DCP start offset information.

[0036] In some embodiments, the start timing of the on-duration window is a start subframe or a start time slot or a start symbol.

[0037] In some embodiments, the processor of the UE is configured to monitor the PDCCH transmission in the OnDuration window of the DCP cycle according to the DCP OnDuration information.

[0038] In some embodiments, the DCP on-duration information is a bitmap indication or an information list associated with the on-duration window.

[0039] In some embodiments, the configuration is received via radio resource control (RRC) signaling or a dynamic command.

[0040] Some embodiments of the present application also provide a network node (e.g., a base station (BS)). The network node includes a processor and a transceiver coupled to the processor; and the processor is configured to: receive from a user equipment (UE) via the transceiver a capability to support an operation for determining a start timing of an on-duration window of a discontinuous reception (DRX) group in a time domain of the UE; and transmit to the UE via the transceiver a configuration of one or more serving cells in the DRX group, wherein the configuration includes at least one of the following: DRX cycle information for determining a non-integer value of the DRX cycle; DRX start offset information indicating an offset value related to a reference system frame number (SFN) in the time domain; or information associated with the reference SFN.

[0041] In some embodiments, the start timing of the on-duration window is a start subframe or a start time slot or a start symbol.

[0042] Some embodiments of the present application also provide a network node (e.g., BS). The network node includes a processor and a transceiver coupled to the processor; and the processor is configured to: receive from a user equipment (UE) via the transceiver a capability to support operation of a physical downlink control channel (PDCCH) transmission in a subset of an on-duration window of a discontinuous reception (DRX) group for monitoring the UE; and transmit to the UE via the transceiver a configuration of one or more serving cells in the DRX group, wherein the configuration indicates a subset of the on-duration window of the DRX group in a time domain.

[0043] In some embodiments, the configuration indicates which opportunities in the time domain are required to monitor the PDCCH transmissions in the subset of the On-Duration windows.

[0044] In some embodiments, the configuration is transmitted via radio resource control (RRC) signaling or a dynamic command.

[0045] In some embodiments, the processor of the network node is configured to: receive jitter range information from the UE or the core network (CN) via the transceiver, and wherein the jitter range information includes at least one of: a DL jitter range of data arrival time at the network node; a UL jitter range of data arrival time at the UE; a probability of the DL jitter range; or a probability of the UL jitter range.

[0046] Some embodiments of the present application also provide a network node (e.g., a BS). The network node includes a processor and a transceiver coupled to the processor; and the processor is configured to: receive from a user equipment (UE) via the transceiver a capability to support an operation for determining a start timing of an on-duration window of a downlink control information (DCI) (DCP) cycle having a cyclic redundancy check (CRC) scrambled by a power-saving radio network temporary identifier (PS-RNTI) in a time domain of the UE; and transmit a configuration about DCP functionality to the UE via the transceiver, wherein the configuration includes at least one of the following: DCP cycle information for determining a non-integer length value of the DCP cycle; DCP start offset information indicating an offset value related to a reference system frame number (SFN) in the time domain; DCP slot offset information indicating a slot delay value before starting a DCP on-duration window in the time domain; or DCP on-duration information indicating which opportunities in the time domain are required for monitoring a physical downlink control channel (PDCCH) transmission in the on-duration window of the DCP cycle.

[0047] In some embodiments, the DCP on-duration information is a bitmap indication or an information list associated with the on-duration window.

[0048] In some embodiments, the configuration is transmitted via radio resource control (RRC) signaling or a dynamic command.

[0049] In some embodiments, the start timing of the on-duration window is a start subframe or a start time slot or a start symbol.

[0050] Some embodiments of the present application also provide a method that can be performed by a UE. The method includes: receiving a configuration of a serving cell in a discontinuous reception (DRX) group from a network, wherein the configuration includes at least one of the following: DRX cycle information, which is used to determine a non-integer length value of the DRX cycle; or DRX start offset information, which indicates an offset value related to a reference system frame number (SFN) in a time domain; and determining a start timing of an on-duration window of the DRX group according to at least one of the DRX cycle information or the DRX start offset information.

[0051] Some embodiments of the present application also provide a method that can be performed by a UE. The method includes: receiving a configuration of one or more serving cells in a discontinuous reception (DRX) group from a network, wherein the configuration indicates a subset of an on-duration window of the DRX group in a time domain; and monitoring a physical downlink control channel (PDCCH) transmission in the subset of the on-duration window according to the configuration.

[0052] Some embodiments of the present application also provide a method that can be performed by a UE. The method includes: receiving a configuration of downlink control information (DCI) (DCP) functionality with a cyclic redundancy check (CRC) scrambled by a power-saving radio network temporary identifier (PS-RNTI) from a network, wherein the configuration includes at least one of the following: DCP cycle information, which is used to determine a non-integer length value of the DCP cycle; DCP start offset information, which indicates an offset value related to a reference system frame number (SFN) in a time domain; DCP slot offset information, which indicates a slot delay value before starting a DCP on-duration window in the time domain; or DCP on-duration information, which indicates which opportunities in the time domain are required for monitoring a physical downlink control channel (PDCCH) transmission in an on-duration window of the DCP cycle.

[0053] Some embodiments of the present application provide a method, which can be performed by a network node (e.g., a BS). The method includes: receiving a capability from a user equipment (UE) to support an operation for determining a start timing of an on-duration window of a discontinuous reception (DRX) group in a time domain of the UE; and transmitting a configuration of one or more serving cells in the DRX group to the UE, wherein the configuration includes at least one of the following: DRX cycle information for determining a non-integer value of the DRX cycle; DRX start offset information indicating an offset value related to a reference system frame number (SFN) in the time domain; or information associated with the reference SFN.

[0054] Some embodiments of the present application provide a method, which can be performed by a network node (e.g., a BS). The method includes: receiving from a user equipment (UE) a capability to support operation of a physical downlink control channel (PDCCH) transmission in a subset of an on-duration window of a discontinuous reception (DRX) group for monitoring the UE; and transmitting to the UE a configuration of one or more serving cells in the DRX group, wherein the configuration indicates a subset of the on-duration window of the DRX group in a time domain.

[0055] Some embodiments of the present application provide a method, which can be performed by a network node (e.g., a BS). The method includes: receiving from a user equipment (UE) a capability to support an operation for determining a start timing of an on-duration window of a downlink control information (DCI) (DCP) cycle having a cyclic redundancy check (CRC) scrambled by a power-saving radio network temporary identifier (PS-RNTI) in a time domain of the UE; and transmitting a configuration about DCP functionality to the UE, wherein the configuration includes at least one of the following: DCP cycle information for determining a non-integer length value of the DCP cycle; DCP start offset information indicating an offset value related to a reference system frame number (SFN) in the time domain; DCP slot offset information indicating a slot delay value before starting a DCP on-duration window in the time domain; or DCP on-duration information indicating which opportunities in the time domain are required for monitoring a physical downlink control channel (PDCCH) transmission in the on-duration window of the DCP cycle.

[0056] Some embodiments of the present application also provide an apparatus for wireless communication. The apparatus includes: a non-transitory computer-readable medium having computer-executable instructions stored thereon; a receiving circuit system; a transmitting circuit system; and a processor coupled to the non-transitory computer-readable medium, the receiving circuit system, and the transmitting circuit system, wherein the computer-executable instructions cause the processor to implement any one of the above methods performed by a UE or a network node (e.g., a BS).

[0057] The details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] In order to describe the manner in which the advantages and features of the present application can be obtained, the description of the present application is presented by reference to specific embodiments of the present application illustrated in the accompanying drawings. These drawings depict only example embodiments of the present application and therefore should not be considered as limiting the scope thereof.

[0059] Figure 1 A schematic diagram illustrating a wireless communication system according to some embodiments of the present application.

[0060] Figure 2A and 2B An exemplary diagram illustrating non-integer periodicity of XR traffic according to some embodiments of the present application.

[0061] Figure 3 An exemplary flow chart for receiving configuration of serving cells in a DRX group according to some embodiments of the present application is illustrated.

[0062] Figure 4 An exemplary flow chart illustrating configuration of serving cells in a transmission DRX group according to some embodiments of the present application.

[0063] Figures 5 to 7 An exemplary diagram illustrating support for non-integer DRX cycles according to some embodiments of the present application.

[0064] Figure 8 An exemplary flow chart for receiving configuration of serving cells in a DRX group according to some embodiments of the present application is illustrated.

[0065] Fig. 9 An exemplary flow chart illustrating configuration of serving cells in a transmission DRX group according to some embodiments of the present application.

[0066] Fig.10 An exemplary diagram illustrating XR traffic arrival with jitter range according to some embodiments of the present application.

[0067] Fig.11 and 12 An exemplary diagram illustrating sparse DRX on-duration set by a bitmap according to some embodiments of the present application.

[0068] Fig.13 An exemplary diagram illustrating a MAC sub-PDU according to some embodiments of the present application.

[0069] Fig.14 An exemplary diagram regarding a DRX timer according to some embodiments of the present application is illustrated.

[0070] Fig.15 An exemplary flow chart illustrating configuration of DCP functionality according to some embodiments of the present application.

[0071] Fig.16 An exemplary diagram illustrating sparse DCP on-duration set by a bitmap according to some embodiments of the present application.

[0072] Fig.17 and 18 An exemplary block diagram illustrating an apparatus for power saving operation according to some embodiments of the present application. DETAILED DESCRIPTION

[0073] The detailed description of the accompanying drawings is intended as a description of the preferred embodiments of the present application and is not intended to represent the only form in which the present application can be practiced. It should be understood that the same or equivalent functions can be accomplished by different embodiments that are intended to be included in the spirit and scope of the present application.

[0074] Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings. To facilitate understanding, embodiments are provided under specific network architectures and new service scenarios (e.g., 3rd Generation Partnership Project (3GPP) LTE and Advanced LTE, 3GPP 5G NR, Advanced 5G, 6G, etc.). With due consideration, all embodiments in the present application are also applicable to similar technical issues as network architectures and new service scenarios evolve; and in addition, the terms cited in the present application may be changed, which should not affect the principles of the present application.

[0075] Figure 1 A schematic diagram illustrating a wireless communication system according to some embodiments of the present application.

[0076] like Figure 1 , the wireless communication system 100 includes at least one base station (BS) 101 and at least one UE 102. Specifically, for illustrative purposes, the wireless communication system 100 includes one BS 101 and two UEs 102 (eg, UE 102a and UE 102b). Figure 1 A specific number of BSs 101 and UEs 102 are depicted in FIG. 1 , but it is contemplated that any number of BSs 101 and UEs 102 may be included in the wireless communication system 100 .

[0077] The wireless communication system 100 is compatible with any type of network capable of sending and receiving wireless communication signals. For example, the wireless communication system 100 is compatible with wireless communication networks, cellular telephone networks, networks based on time division multiple access (TDMA), networks based on code division multiple access (CDMA), networks based on orthogonal frequency division multiple access (OFDMA), LTE networks, networks based on 3GPP, 3GPP 5G networks, satellite communication networks, high altitude platform networks, and / or other communication networks.

[0078] BS 101 may also be referred to as an NG-RAN node, a RAN node, an access point, an access terminal, a base station, a macro cell, a Node B, an enhanced Node B (eNB), a gNB, a home Node B, a relay node or a device, or described using other terms used in the art. BS 101 is typically part of a radio access network that may include a controller communicatively coupled to BS 101.

[0079] According to some embodiments of the present application, UE 102 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), a vehicle-mounted computer, a network device (e.g., a router, a switch, and a modem), etc. According to some other embodiments of the present application, UE 102 may include a portable wireless communication device, a smart phone, a cellular phone, a flip phone, a device with a subscriber identity module, a personal computer, a selective call receiver, or any other device capable of sending and receiving communication signals on a wireless network.

[0080] According to some other embodiments of the present application, UE 102 may include a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, etc. In addition, UE 102 may be referred to as a subscriber unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal or a device, or described using other terms used in the art.

[0081] Figure 1 Both UE 102a and UE 102b in the embodiment of the present invention can transmit information to BS 101 and receive control information from BS 101, for example, via an LTE or NR Uu interface.

[0082] Generally, for XR services, DRX is a key feature for power saving in UE. During DRX active time, UE monitors PDCCH transmissions of C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI and AI-RNTI of MAC entity. It allows UE to stop monitoring PDCCH during time periods when there is no data activity, thereby saving power. However, there are some challenges in using DRX for power saving of XR services.

[0083] For example, a typical XR DL frame rate may be 60 or 120 frames per second (fps), where the frame periodicity is 16.67 ms (i.e., 1000 ms / 60) or 8.33 ms (i.e., 1000 ms / 120), which is a non-integer. The DRX on-duration start position is in units of subframes or in units of ms, as defined in the following formula defined in 3GPP specification TS 38.321.

[0084] [(SFN×10)+Subframe Number] modulo (drx-ShortCycle)=(drx-StartOffset) modulo (drx-ShortCycle); or

[0085] [(SFN×10)+subframe number] modulo (drx-LongCycle)=drx-StartOffset.

[0086] For example, RRC signaling can control DRX operation by configuring the following parameters:

[0087] -drx-LongCycleStartOffset: long DRX cycle and drx-StartOffset, which define the subframes where the long and short DRX cycles start; and / or

[0088] -drx-ShortCycle (optional): short DRX cycle.

[0089] As defined in 3GPP Rel-15 or Rel-16, the configurable connected DRX (CDRX) long cycle value is 10ms, 20ms, 32ms, 40ms, etc., and the configurable CDRX short cycle value is 2ms, 3ms, 5ms, 6ms, 7ms, 8ms, 10ms, 14ms, 16ms, 20ms, 30ms, 32ms, 35ms, etc.

[0090] Figure 2A and 2B An exemplary diagram illustrating non-integer periodicity of XR traffic according to some embodiments of the present application.

[0091] refer to Figure 2A , the XR service burst may be 60fps, where the frame periodicity is 16.67ms. Four XR service bursts with three frame periodicities occupy 50ms in the time domain. In some embodiments, a DRX cycle with a length of 16ms may be used. However, using a 16ms DRX cycle will cause the last XR service burst to miss the on-duration of the DRX cycle, because three 16ms DRX cycles occupy 48ms in the time domain, which is 2ms less. In other words, the service misses the on-duration of the DRX cycle. In some other embodiments, a DRX cycle with a length of 17ms may be used. However, using a 17ms DRX cycle also has a problem in that it will cause additional delays in waiting for the on-duration of the DRX cycle. Therefore, in the example Figure 2A There is a DRX problem for XR services in the embodiment shown in FIG.

[0092] refer to Figure 2B, there may be a SFN wraparound mismatch between XR DL traffic (e.g., 60fps) and the DRX start offset. The traditional DRX pattern repeats every 10,240ms, which is equal to one superframe period. A superframe contains 1024 SFNs, e.g., SFN 0 to SFN 1023. However, this superframe period is not divisible by the XR periodicity. Therefore, when the SFN wraps back to 0 every superframe 10,240ms, a mismatch occurs between the DRX on duration and the arrival of XR DL traffic. Figure 2B This shows the SFN surround mismatch for 60fps XR DL service when the DRX start offset is set to 0. Figure 2B As shown in FIG. 1 , the burst arrival (60 Hz) has a frame periodicity of 16.67 ms. When using DRX cycle 50 / 3 ms and DRX start offset 0 ms, each three DRX cycles may have lengths of 17 ms, 17 ms, and 16 ms, respectively. 10,240 ms = 204 × 50 ms + 40 ms. Therefore, the last 40 ms in the superframe (i.e., SFN 1020, SFN 1021, SFN 1022, and SFN 1023, as shown in FIG. 1 ) Figure 2B ) is divided into "17ms+17ms+6ms". At the end of the superframe (i.e., after 6ms), the DRX on duration starts because the SFN returns to 0 and the subframe number is 0, but the actual XR DL traffic arrives 10ms (i.e., 0.6 frames) later (after 16ms). This mismatch problem will also lead to XR capacity loss due to larger latency and / or larger UE power consumption to maintain the same latency performance.

[0093] In addition, there may be variable arrival bursts of XR traffic. For XR services, DL traffic bursts are periodic with some time jitter in the arrival timing at the BS. The jitter may be due to random delays originating from the frame encoder in the edge server and / or network transmission time from the wireless system. This jitter may cause a rhythm mismatch between the XR traffic and the CDRX cycle. Due to the late packet arrival, the UE will increase the wake-up time. Due to the early packet arrival, it is challenging to schedule DL data within the packet delay budget (PDB) of the BS.

[0094] In addition, some solutions propose to support the allocation of multiple resources to handle large XR application packets. Multi-slot scheduling can be used to avoid multiple DCI transmissions. In this case, it is foreseeable that the PDCCH indicating a new UL / DL transmission or retransmission is less likely to be received before the end of the last transmission in the bundle. Therefore, some embodiments of the present application provide a solution that prevents the UE from starting the inactivity timer and drx-RetransmissionTimerUL too early (which may cause more power consumption) as in traditional operations.

[0095] In view of the above, the embodiments of the present application design a more efficient power saving mechanism for XR devices. The embodiments of the present application aim to solve DRX-related problems taking into account the characteristics of XR services, including: how to solve the mismatch between the current DRX cycle and the arrival of XR services due to the non-integer periodicity of the XR services; how to solve the mismatch between the DRX cycle and the arrival of XR services due to the fact that the super frame number (HFN) period (10240ms) cannot be divided by the XR period (e.g., 17ms) in the case of SFN surround; how to dynamically monitor PDCCH to save power while considering the arrival timing with some jitter; and / or how to adapt DRX operation to multi-slot scheduling in a single DCI to save power.

[0096] More specifically, some embodiments of the present application introduce a mechanism to overcome the non-integer periodicity of XR services. In some embodiments of the present application, in order to achieve more efficient DRX operation for power saving of XR devices, the UE monitors PDCCH transmissions in a subset of DRX-On-Duration via semi-static configuration or dynamic commands according to the DRX-On-Duration bitmap indication. In some embodiments of the present application, in order to achieve more efficient DRX operation for power saving of XR devices, the start timing of drx-InactivityTimer and drx-RetransmissionTimerUL of the DRX group is delayed until the symbol (not repeated) that first appears in the time domain after the end of the last transmission within a bundle of transport blocks (TBs) scheduled by a single DCI. In some embodiments of the present application, in order to achieve more efficient DRX operation for power saving of XR devices, a non-integer period DCP duration replaces the DRX-On-Duration.

[0097] More details will be described below in conjunction with the accompanying drawings. It should be well known to those skilled in the art that the words "first", "second", and "third" are only used for clear description and should not be regarded as any substantial limitations, such as sequence limitations.

[0098] Figure 3 An exemplary flow chart for receiving configuration of serving cells in a DRX group according to some embodiments of the present application is illustrated. Figure 3 The exemplary method 300 in the embodiment may be performed by a UE. Although described with respect to a UE, it should be understood that other devices may be configured to perform the same Figure 3 A similar approach to the one used in this paper.

[0099] exist Figure 3 In the exemplary method 300 in FIG. 1 , in operation 301, a UE (e.g., Figure 1UE 102 shown in FIG. 1 ) receives a request from a network (e.g., Figure 1 1 ) receives a configuration (denoted as a first configuration for simplicity) of one or more serving cells in a DRX group. The first configuration may include at least one of the following: DRX cycle information, which is used to determine a non-integer length value of the DRX cycle; or DRX start offset information, which indicates an offset value related to a reference SFN in the time domain. In some embodiments, the unit is an offset value, which is associated with one of the following: a subframe, a time slot, and a symbol.

[0100] In operation 302, the UE determines a start timing (expressed as a first start timing for simplicity) of an on-duration window of a DRX group according to at least one of the DRX cycle information or the DRX start offset information.

[0101] In some embodiments, the UE determines a further start timing (expressed as a second start timing for simplicity) of the on-duration window of the DRX group in the time domain according to at least one of the DRX cycle information or the DRX start offset information.

[0102] In some embodiments, the first configuration further includes information associated with a reference SFN, and at least one of the first start timing or the second start timing of the opening duration window is further determined according to the information associated with the reference SFN.

[0103] In some embodiments, the DRX cycle information includes a downlink (DL) frame rate in the time domain, and the non-integer length value is determined based on the DL frame rate. In some other embodiments, the DRX cycle information includes a non-integer length value. Figures 5 to 7 The embodiments are described as follows.

[0104] In some embodiments, the UE may receive a further configuration (denoted as a second configuration for simplicity) of one or more serving cells in the DRX group from the network. The second configuration indicates a subset of the on-duration window. The UE may monitor PDCCH transmissions in the subset of the on-duration window according to the second configuration.

[0105] In some embodiments, the second configuration includes at least one of the following:

[0106] (1) a bitmap indication (e.g., drx-On-Duration bitmap) that is associated with an on-duration window; or

[0107] (2) An information list (e.g., drx-On-Duration list) associated with one or more subsets of the on-duration window. In an embodiment, the information list indicates at least one of the following: a start timing of a subset within the one or more subsets of the on-duration window; or a length of a subset within the one or more subsets of the on-duration window.

[0108] In some embodiments, at least one of the first start timing of the on-duration window, the second start timing of the on-duration window, or the start timing of a subset within one or more subsets is: a start subframe or a start slot or a start symbol.

[0109] In some embodiments, the second configuration indicates which occasions in the time domain are required to monitor for PDCCH transmissions in a subset of the On-Duration window.

[0110] In some embodiments, the second configuration is received via RRC signaling (eg, an RRC reconfiguration message) or a dynamic command (eg, a DCI or a MAC CE).

[0111] In some embodiments, the UE may transmit jitter range information to the network. The jitter range information includes at least one of: a UL jitter range of the data arrival time at the UE; or a probability of a UL jitter range. Figures 11 to 13 The embodiments are described as follows.

[0112] In some embodiments, the UE may receive a single downlink control information (DCI) from the network on a serving cell in a DRX group for scheduling multiple time slots in a time domain for a downlink (DL) or uplink (UL) of the UE. Each time slot within the multiple time slots corresponds to a unique hybrid automatic repeat request (HARQ) process of the UE.

[0113] In some embodiments, in response to a single DCI for scheduling multiple time slots for DL ​​or UL and in response to receiving a PDCCH transmission on a serving cell in a DRX group indicating a new DL or UL transmission within the multiple time slots, the UE may not start the DRX inactivity timer for the DRX group, or the UE may delay the start timing of the DRX inactivity timer for the DRX group until a symbol that first appears in the time domain after the end of the timing of the last PDSCH transmission within the multiple time slots.

[0114] In some embodiments, in response to a single DCI for scheduling multiple time slots for the UL and in response to the expiration of a DRX HARQ round trip time (RTT) timer for PUSCH transmission in multiple time slots for a corresponding HARQ process, the UE may start a DRX retransmission timer for the UL for the corresponding HARQ process at a subsequent timing between: a symbol that first appears in the time domain after the expiration of the DRX HARQ RTT timer for the UL; and a symbol that first appears in the time domain after the end of the timing of the last PUSCH transmission in the multiple time slots. Specific examples are in Fig.14 The embodiments are described as follows.

[0115] Figure 4 An exemplary flow chart illustrating configuration of serving cells in a transmission DRX group according to some embodiments of the present application. Figure 4 The exemplary method 400 in FIG. 4 may be performed by a network node (eg, a BS). Although described with respect to a BS, it should be understood that other devices may be configured to perform the same. Figure 4 A similar approach to the one used in this paper.

[0116] exist Figure 4 In the exemplary method 400 of , in operation 401, a network node (e.g., Figure 1 BS101 shown in FIG. 1) from UE (such as Figure 1 102) receives a capability to support operations for determining a start timing of an on-duration window of a DRX group in a time domain of the UE. In operation 402, the network node transmits a configuration of one or more serving cells in the DRX group to the UE. The configuration may include at least one of the following:

[0117] (1) DRX cycle information, which is used to determine a non-integer value of the DRX cycle;

[0118] (2) DRX start offset information (e.g., DRX-Start-Offset-Ext), which indicates an offset value related to a reference SFN in the time domain; or

[0119] (3) Information associated with the reference SFN.

[0120] In some embodiments, the start timing of the on-duration window is the start subframe or the start time slot or the start symbol.

[0121] Those skilled in the art should understand that the sequence of operations in the exemplary process 300 or 400 may be changed, and some operations in the exemplary process 300 or 400 may be eliminated or modified without departing from the spirit and scope of the present disclosure. The details described in all other embodiments of the present application are applicable to Figure 3 and 4In any embodiment of the present invention. In addition, Figure 3 and 4 The details described in any of the embodiments apply to Figures 1 to 2B and Figures 5 to 18 All embodiments of the invention.

[0122] Figures 5 to 7 An exemplary diagram illustrating support for non-integer DRX cycles according to some embodiments of the present application.

[0123] Figure 5 An embodiment is shown in which DRX-Start-Offset-Ext=0, XR DL frame rate=60fps, and DRX cycle length=1000 / 60ms (i.e., 16.67ms, which is a non-integer). For example, the DRX start offset (i.e., DRX-Start-Offset-Ext) is 0, such as Figure 5 In these embodiments, the UE may determine the Nth starting position of the DRX-On-Duration based on the non-integer DRX cycle and the DRX-Start-Offset-Ext relative to the reference SFN (e.g., SFN0). In these embodiments, when the XR DL frame rate is 60fps, the UE may determine that the DRX mode is 0, 17ms, 34ms (i.e., 17ms+17ms), 50ms (i.e., 17ms+17ms+16ms), etc.

[0124] For example, in Figure 5 In an embodiment, the BS may send a DRX configuration to the UE, where the DRX configuration includes:

[0125] (1) DRX-Start-Offset-Ext, which indicates an offset value related to the time reference SFN=0. The unit is a subframe. A subframe is 1 ms. In different embodiments, a subframe may include 1 time slot, 2 time slots, 4 time slots, etc.

[0126] (2) Non-integer DRX cycle, which has a non-integer value indicating the real rhythm of the service. The unit is ms.

[0127] a) This can be made of 2 parameters (X, Y). Sample Y times every X duration.

[0128] b) This can be just 1 parameter "X / Y".

[0129] (a) For frame rate = 60fps, DRX cycle length = 1000 / 60ms.

[0130] (b) For frame rate = 30fps, DRX cycle length = 1000 / 30ms.

[0131] (c) For frame rate = 90fps, DRX cycle length = 1000 / 90ms.

[0132] (3) drx-onDurationTimer: The duration at the start of a DRX cycle. drx-onDurationTimer may also be referred to as “DRX on-duration window” or “DRX-On-Duration”.

[0133] (4)drx-SlotOffset: Delay before starting drx-onDurationTimer.

[0134] (5) drx-InactivityTimer: The duration after a PDCCH opportunity where the PDCCH indicates a new UL or DL ​​transmission by the MAC entity of the UE.

[0135] (6) drx-RetransmissionTimerDL (per DL HARQ process, except broadcast process): maximum duration until a DL retransmission is received.

[0136] (7) drx-RetransmissionTimerUL (per UL HARQ process): Maximum duration until a grant for UL retransmission is received.

[0137] exist Figure 5 In an embodiment of the present invention, the DRX configuration received by the UE may include a non-integer value for the DRX cycle length configuration. The MAC entity of the UE shall sequentially consider that the Nth (N>=0) DRX-On-Duration start position occurs in the following subframes:

[0138] Formula (1): [(SFN×10)+subframe number]=ceil(DRX-Start-Offset-Ext+N×Non-integerDRX cycle) modulo (1024×10)

[0139] Then, the MAC entity of the UE may start the drx-onDurationTimer for this DRX group after drx-SlotOffset from the start of the subframe.

[0140] Figure 6 Other embodiments are shown where DRX-Start-Offset-Ext=0, XR DL frame rate=60fps, and DRX cycle length=1000 / 60ms (i.e., 16.67ms, which is a non-integer). For example, the DRX start offset is 0, such as Figure 6In these embodiments, when the frame rate is 60fps, the UE may determine that the DRX mode is 0, 16ms, 33ms (ie, 16ms+17ms), 50ms (ie, 16ms+17ms+17ms), etc.

[0141] For example, in Figure 6 In the embodiment of Figure 5 The above DRX configuration in the embodiment is the same or similar DRX configuration. Figure 6 In an embodiment of the present invention, the DRX configuration received by the UE may include a non-integer value for the DRX cycle length configuration. The MAC entity of the UE shall sequentially consider that the Nth (N>=0) DRX-On-Duration start position occurs in the following subframes:

[0142] Formula (2): [(SFN×10)+subframe number]=floor(DRX-Start-Offset-Ext+N×Non-integerDRX cycle) modulo (1024×10)

[0143] Then, the MAC entity of the UE may start the drx-onDurationTimer for this DRX group after drx-SlotOffset from the start of the subframe.

[0144] Figure 7 Additional embodiments are shown where DRX-Start-Offset-Ext=0, XR DL frame rate=60fps, and DRX cycle length=1000 / 60ms (i.e., 16.67ms, which is a non-integer). In these embodiments, the BS may configure timeReferenceSFN to be 512, and DRX-Start-Offset-Ext is related to the timeReferenceSFN (i.e., 512). For example, the DRX start offset is 14, as shown in FIG. Figure 7 The UE may determine the DRX start position according to timeReferenceSFN (i.e., 512) and DRX-Start-Offset-Ext (i.e., 14). The BS may send a DRX configuration to the UE, wherein the DRX configuration includes:

[0145] (1) timeReferenceSFN = 512

[0146] (2) DRX-Start-Offset-Ext, which indicates an offset value related to a reference SFN=512.

[0147] and Figure 5 and 6 Similar to the embodiment of Figure 7In the embodiment of the present invention, the MAC entity of the UE shall sequentially consider that the Nth (N>=0) DRX-On-Duration start position appears in the following subframes:

[0148] Formula (3): [(SFN×10)+subframe number]=ceil(timeReferenceSFN×10+DRX-Start-Offset-Ext+N×Non-integer DRX cycle)) modulo (1024×10); or

[0149] Formula (4): [(SFN×10)+subframe number]=floor(timeReferenceSFN×10+DRX-Start-Offset-Ext+N×Non-integer DRX cycle) modulo (1024×10)

[0150] Then, the MAC entity of the UE may start the drx-onDurationTimer for this DRX group after drx-SlotOffset from the start of the subframe.

[0151] Figures 5 to 7 An embodiment supporting non-integer DRX cycles is described, which considers the DRX-Start-Offset-Ext of the DRX-On-Duration with a granularity of subframes. In some additional embodiments of the present application supporting non-integer DRX cycles, a finer granularity of DRX-Start-Offset-Ext of the DRX-On-Duration may be considered, for example, the unit is a time slot. The MAC entity of the UE shall sequentially consider that the Nth (N>=0) starting position of the DRX-On-Duration occurs in the following time slots:

[0152] Formula (5): [(SFN×numberOfSlotsPerFrame)+time slot number in frame]=ceil(timeReferenceSFN×numberOfSlotsPerFrame+DRX-Start-Offset-Ext+N×Non-integerDRX cycle×numberOfSlotsPerSubFrame) modulo (1024×numberOfSlotsPerFrame); or

[0153] Formula (6): [(SFN×numberOfSlotsPerFrame)+time slot number in frame]=floor(timeReferenceSFN×numberOfSlotsPerFrame+DRX-Start-Offset-Ext+N×Non-integerDRX cycle×numberOfSlotsPerSubFrame)) modulo (1024×numberOfSlotsPerFrame)

[0154] Then, the MAC entity of the UE may start the drx-onDurationTimer for this DRX group from the beginning of the timeslot.

[0155] In yet another additional embodiment of the present application that supports non-integer DRX cycles, a finer granularity DRX-Start-Offset-Ext of DRX-On-Duration may be considered, for example, the unit is symbol. The MAC entity of the UE shall sequentially consider that the Nth (N>=0) DRX-On-Duration start position appears in the following symbols:

[0156] Formula (7): [(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+number of slots in frame×numberOfSymbolsPerSlot+number of symbols in slot]=ceil(timeReferenceSFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+DRX-Start-Offset-Ext+N×Non-integer DRX cycle×numberOfSlotsPerSubFrame×numberOfSymbolsPerSlot) modulo (1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot); or

[0157] Formula (8): [(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+time slot number in frame×numberOfSymbolsPerSlot+symbol number in time slot]=floor(timeReferenceSFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+DRX-Start-Offset-Ext+N×Non-integer DRX cycle×numberOfSlotsPerSubFrame×numberOfSymbolsPerSlot) modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)

[0158] Then, the MAC entity of the UE may start the drx-onDurationTimer for this DRX group from the beginning of the symbol number.

[0159] In yet an additional embodiment of the present application that supports non-integer DRX cycles, in the case of BS CU-DU separation, the BS-CU may send non-integer DRX cycle information to the BS-DU in an F1AP message (e.g., UE CONTEXT SETUP REQUEST message, or UE CONTEXT MODIFICATIONREQUEST message), so that the BS-DU can determine the DRX-On-Duration mode of the DRX group based on the non-integer DRX cycle information.

[0160] In an embodiment, a Non-integer DRX cycle information element (IE) may be added in the DRX Cycle IE, for example, as shown in Table 1.

[0161] Table 1

[0162]

[0163] In another embodiment, the value range of the Long DRX Cycle Length IE or the Short DRX Cycle Length IE may be extended to include non-integer values ​​of non-integer DRX cycles, for example, as shown in Table 2.

[0164] Table 2

[0165]

[0166]

[0167] The details described in all other embodiments of this application apply to Figures 5 to 7 In any embodiment of the present invention. In addition, Figures 5 to 7 The details described in any of the embodiments apply to Figures 1 to 4 and Figures 8 to 18 All embodiments of the invention.

[0168] Figure 8 An exemplary flow chart for receiving configuration of serving cells in a DRX group according to some embodiments of the present application is illustrated. Figure 8 The exemplary method 800 in the embodiment may be performed by a UE. Although described with respect to a UE, it should be understood that other devices may be configured to perform the same Figure 8 A similar approach to the one used in this paper.

[0169] exist Figure 8 In the exemplary method 800 in FIG. 8 , in operation 801, a UE (e.g., Figure 1 UE 102 shown in FIG. 1 ) receives a request from a network (e.g., Figure 1 1) receives a configuration of one or more serving cells in a DRX group (represented as a first configuration for simplicity). The configuration indicates a subset of an on-duration window of the DRX group in the time domain. In operation 802, the UE monitors PDCCH transmissions in the subset of the on-duration window according to the configuration.

[0170] In some embodiments, the configuration includes at least one of: a bitmap indication (e.g., drx-On-Durationbitmap) associated with the on-duration window; or an information list (e.g., drx-On-Duration list) associated with one or more subsets of the on-duration window. In an embodiment, the information list indicates at least one of: a start timing of a subset within the one or more subsets of the on-duration window; or a length of a subset within the one or more subsets of the on-duration window.

[0171] In some embodiments, the configuration indicates which opportunities in the time domain are required for monitoring PDCCH transmissions in a subset of the on-duration windows. Figures 5 to 7 The embodiments are described as follows.

[0172] In some embodiments, the UE may receive information associated with the length of the DRX on-duration window from the network (represented as first information for simplicity), receive DRX slot offset information indicating a time slot delay value before the start of the DRX on-duration window in the time domain from the network; receive information associated with the DRX cycle in the time domain and the start offset value of the DRX cycle from the network (represented as second information for simplicity), and determine the start timing of the on-duration window of the DRX group in the time domain according to at least one of the first information, the DRX slot offset information, or the second information (represented as first start timing for simplicity). In an embodiment, the UE may determine the start timing of the on-duration window in the time domain according to at least one of the first information, the DRX slot offset information, or the second information (represented as second start timing for simplicity).

[0173] In some embodiments, the UE may receive a configuration of one or more serving cells in a DRX group from the network (represented as a first configuration for simplicity). The first configuration includes at least one of the following: DRX cycle information, which is used to determine a non-integer length value of the DRX cycle; or DRX start offset information, which indicates an offset value related to a reference system frame number (SFN) in the time domain. In some embodiments, the unit is an offset value, which is associated with one of the following: a subframe, a time slot, and a symbol. The UE may determine a first start timing of an on-duration window of the DRX group in the time domain according to at least one of the DRX cycle information or the DRX start offset information. In an embodiment, the UE may determine a second start timing of the on-duration window in the time domain according to at least one of the DRX cycle information or the DRX start offset information.

[0174] In some embodiments, at least one of the start timing of a subset within the one or more subsets, the first start timing of an on-duration window, or the second start timing of an on-duration window is: a start subframe or a start time slot or a start symbol.

[0175] In some embodiments, the first configuration further includes information associated with a reference SFN, and the start timing of the on-duration window is further determined according to the information associated with the reference SFN.

[0176] In some embodiments, the DRX cycle information includes a DL frame rate in the time domain, and the non-integer length value is determined based on the DL frame rate. In some other embodiments, the DRX cycle information includes a non-integer length value. Figures 5 to 7 The embodiments are described as follows.

[0177] In some embodiments, the UE may transmit jitter range information to the network. The jitter range information includes at least one of: a UL jitter range of data arrival time at the UE; or a probability of a UL jitter range.

[0178] In some embodiments, the UE may receive a single DCI from the network on a serving cell in a DRX group for scheduling multiple time slots in a time domain for the UE's DL or UL. Each time slot within the multiple time slots corresponds to a unique HARQ process of the UE.

[0179] In some embodiments, in response to a single DCI for scheduling multiple time slots for DL ​​or UL and in response to receiving a PDCCH transmission indicating a new DL or UL transmission within the multiple time slots, the UE may not start the DRX inactivity timer for the DRX group, or the UE may delay the start timing of the DRX inactivity timer for the DRX group until the first symbol that appears in the time domain after the end of the timing of the last DSCH transmission within the multiple time slots.

[0180] In some embodiments, in response to a single DCI for scheduling multiple time slots for the UL and in response to expiration of a DRXHARQ round trip time (RTT) timer for a physical uplink shared channel (PUSCH) transmission within multiple time slots for a corresponding hybrid automatic repeat request (HARQ) process, the UE may start a DRX retransmission timer for the UL for the corresponding HARQ process at a subsequent timing between: a symbol that first appears in the time domain after expiration of the DRX HARQ RTT timer for the UL; and a symbol that first appears in the time domain after the timing of the last PUSCH transmission within the multiple time slots ends. Specific examples are in Fig.14 The embodiments are described as follows.

[0181] Fig. 9 An exemplary flow chart illustrating configuration of serving cells in a transmission DRX group according to some embodiments of the present application. Fig. 9 The exemplary method 900 in FIG. 1 may be performed by a network node (eg, a BS). Although described with respect to a BS, it should be understood that other devices may be configured to perform the same. Fig. 9 A similar approach to the one used in this paper.

[0182] exist Fig. 9 In the exemplary method 900 of , in operation 901, a network node (e.g., Figure 1 BS101 shown in FIG. 1) from UE (such as Figure 1 102) receives a capability to support operation of PDCCH transmission in a subset of the on-duration window of the DRX group for monitoring the UE. In operation 902, the UE transmits a configuration of one or more serving cells in the DRX group to the UE. The configuration indicates a subset of the on-duration window of the DRX group in the time domain. Specific examples are described in Figures 11 to 13 The embodiments are described as follows.

[0183] In some embodiments, the configuration indicates which occasions in the time domain are required to monitor for PDCCH transmissions in a subset of the On-Duration windows.

[0184] In some embodiments, the configuration is transmitted via RRC signaling (eg, an RRC reconfiguration message) or a dynamic command (eg, a DCI or a MAC CE).

[0185] In some embodiments, the network node may receive jitter range information from the UE or the core network (CN). The jitter range information may include at least one of the following:

[0186] (1) DL jitter range of data arrival time at network nodes;

[0187] (2) UL jitter range of data arrival time at the UE;

[0188] (3) probability of DL jitter range; or

[0189] (4) Probability of UL jitter range.

[0190] Those skilled in the art should understand that the sequence of operations in the exemplary process 800 or 900 may be changed, and some operations in the exemplary process 800 or 900 may be eliminated or modified without departing from the spirit and scope of the present disclosure. The details described in all other embodiments of the present application are applicable to the present invention. Figure 8 and 9 In any embodiment of the present invention. In addition, Figure 8 and 9 The details described in any of the embodiments apply to Figures 1 to 7 and Figures 10 to 18 All embodiments of the invention.

[0191] Fig.10 An exemplary diagram illustrating XR traffic arrival with jitter range according to some embodiments of the present application. Fig.10 As shown in FIG. 1 , the DRX-On-Duration within the DRX cycle may have a jitter range, for example, [-4, 4] ms. [-4, 4] ms may also be expressed as [-4 ms, 4 ms], etc. Without departing from the spirit and scope of the present disclosure, each end value of the jitter range may vary according to different embodiments. The jitter range may also be referred to as a DL jitter range, etc.

[0192] Fig.11 and 12 An exemplary schematic diagram illustrating a sparse DRX on-duration set by a bitmap according to some embodiments of the present application is shown. Fig.11 and 12As shown in , the UE should monitor PDCCH transmission at the beginning of DRX-On-Duration in the DRX cycle. A DRX cycle consists of "on duration" and "DRX opportunity". Fig.10 Similar to the embodiment, Fig.11 and 12 The DL jitter range in the embodiment of is also [-4,4]ms. Fig.11 and 12 In an embodiment, the PDCCH transmission may be monitored over the DRX-On-Duration according to the DRX-On-Duration bitmap. For example, the UE monitors only a subset of the DRX-On-Duration according to the DRX-On-Duration bitmap.

[0193] exist Fig.11 or Fig.12 In an embodiment, the BS may receive separate DL / UL jitter ranges from the CN or the application layer of the BS. For example, the jitter range list may include one or more jitter ranges (for example, including the following 3 jitter ranges) and corresponding probability levels. Each jitter range may indicate an arrival jitter range relative to a configured periodic arrival time. Each probability level corresponding to a jitter range may indicate a probability associated with the jitter range. The probability level may be (0,1). A higher probability level may indicate a higher probability. The probability level may be indicated by a 'high', 'medium' or 'low' value instead of a numerical value. In an embodiment, the jitter range list includes 3 jitter ranges and corresponding probability levels:

[0194] (1) Jitter range [0,3]ms

[0195] Probability level = 0.5

[0196] (2) Jitter range [-4,0]ms

[0197] Probability level = 0.3

[0198] (3) Jitter range [3,4] ms

[0199] Probability level = 0.9

[0200] exist Fig.11 In an embodiment, the BS may send a DRX configuration to the UE in an RRC reconfiguration message. The DRX configuration may include at least one of the following:

[0201] (1) drx-onDurationTimer, which indicates the duration at the start of the DRX cycle;

[0202] (2) drx-LongCycleStartOffset: long DRX cycle and drx-StartOffset, which define the subframes where the long and short DRX cycles start;

[0203] (3)DRX ShortCycle: short DRX cycle;

[0204] (4) Non-integer DRX cycle: a non-integer value indicating the actual rhythm of the service;

[0205] (5) DRX-Start-Offset-Ext: indicates the offset value related to the time reference SFN;

[0206] (6) timeReferenceSFN: system SFN used as a reference for DRX-Start-Offset-Ext;

[0207] (7) drx-SlotOffset: It indicates the delay before starting drx-onDurationTimer;

[0208] (8) drx-On-Duration bitmap, which indicates which PDCCH monitoring opportunity (e.g., subframe, time slot, or symbol) is required for PDCCH monitoring on DRX-On-Duration. For example, drx-On-Duration bitmap is 100111001, such as Fig.11 For example:

[0209] a) The first / leftmost bit of this bitmap corresponds to the first subframe on the DRX-On-Duration.

[0210] b) A value of 0 in this bitmap indicates that the corresponding subframe is not allowed to be used for PDCCH monitoring.

[0211] c) A value of 1 in this bitmap indicates that the corresponding subframe is allowed to be used for PDCCH monitoring.

[0212] exist Fig.11In an embodiment, after receiving the DRX configuration, the UE may determine the PDCCH monitoring timing on the DRX-On-Duration according to the value 1 in the drx-On-Duration bitmap. In some embodiments, the UE may determine the periodic starting position of the DRX-On-Duration according to the prior art (e.g., 3GPP specification TS 38.321vg70). In some other embodiments, the UE may determine the periodic starting position of the DRX-On-Duration according to any of the above embodiments related to the non-integer length value of the DRX cycle of the present application. The UE may start the drx-onDurationTimer for this DRX group. Then, the UE may determine the internal PDCCH monitoring mode of the DRX-On-Duration according to the drx-On-Duration bitmap.

[0213] If the UE receives a new PDCCH transmission (DL or UL) on the serving cell in this DRX group, the UE may start DRX in the internal mode of DRX-On-Duration according to the drx-On-Duration bitmap. The UE may start or restart the drx-InactivityTimer for this DRX group in the symbol that first appears in the time domain after the end of PDCCH reception.

[0214] exist Fig.12 In the embodiment of the present invention, the BS may send a DRX-On-Duration command associated with a drx-On-Duration bitmap via a DCI or a MAC CE. A specific example of a MAC CE is described in Fig.13 The DRX-On-Duration command may indicate which PDCCH timing (eg, subframe, time slot, or symbol) is required for PDCCH monitoring on DRX-On-Duration. For example:

[0215] (1) The first / leftmost bit in the drx-On-Duration bitmap corresponds to the subframe that first appears in the DRX-On-Duration in the time domain.

[0216] (2) A value of 0 in the bitmap indicates that the corresponding subframe is not allowed to be used for PDCCH monitoring.

[0217] (3) A value of 1 in the bitmap indicates that the corresponding subframe is allowed to be used for PDCCH monitoring. For example, the bitmap in the DRX-On-Duration command is 100111011. Fig.12 Displayed in.

[0218] After the UE receives the DRX-On-Duration command via DCI or MAC CE, the UE may:

[0219] (1) In the current DRX cycle, the DRX-On-Duration command is applied starting from DRX-On-Duration; or

[0220] (2) In the next DRX cycle, the DRX-On-Duration command is applied starting from DRX-On-Duration. Fig.12 , during the on-duration of the DRX cycle of bitmap 111111111, the UE may receive a DRX-On-Duration command including bitmap 100111011; and then, the UE may apply the DRX-On-Duration command starting from DRX-On-Duration in the next DRX cycle with a DL jitter range of [-4,4] ms.

[0221] Fig.11 and 12 An embodiment of PDCCH monitoring is described, where each bit in the drx-On-Duration bitmap corresponds to a subframe granularity. In some additional embodiments of the present application, PDCCH transmissions may be monitored on DRX-On-Duration according to the drx-On-Duration bitmap, where each bit corresponds to a time slot granularity. That is, the drx-On-Duration bitmap field may be used to indicate the time slots required for PDCCH monitoring on DRX-On-Duration. For example:

[0222] (1) The first / leftmost bit in the bitmap corresponds to the first time slot on the DRX-On-Duration.

[0223] (2) A value of 0 in the bitmap indicates that the corresponding time slot is not allowed to be used for PDCCH monitor.

[0224] (3) A value of 1 in the bitmap indicates that the corresponding time slot is allowed to be used for the PDCCH monitor.

[0225] In some embodiments of the present application where the PDCCH transmission may be monitored over the DRX-On-Duration according to a list of starting offset values ​​plus length values, the UE monitors the PDCCH transmission over the DRX-On-Duration according to only the list of starting offset values ​​plus length values ​​instead of monitoring the PDCCH transmission over the DRX-On-Duration as described above. Fig.11 and 12In an embodiment, a subset of DRX-On-Duration is monitored according to the drx-On-Duration bitmap. For example, a list (e.g., drx-On-Duration list) may include three items:

[0226] (1) The start offset of the first item indicates that the UE starts PDCCH monitoring at an offset relative to the start of the DRX-On-Duration. For example, the value is 0 ms.

[0227] - The length of the first item indicates the time length of PDCCH monitoring. For example, the value is 1 ms.

[0228] (2) The start offset of the second item indicates that the UE starts PDCCH monitoring at an offset relative to the start of the DRX-On-Duration. For example, the value is 3 ms.

[0229] -The length of the second item indicates the time length of PDCCH monitoring. For example, the value is 3ms.

[0230] (3) The start offset of the third item indicates that the UE starts PDCCH monitoring at an offset relative to the start of the DRX-On-Duration. For example, the value is 9 ms.

[0231] - The length of the third item indicates the time length of PDCCH monitoring. For example, the value is 1 ms.

[0232] Specifically, refer to Fig.11 In some embodiments, the BS may send a DRX configuration to the UE in an RRC reconfiguration message, and the DRX configuration includes at least one of the following:

[0233] (1) drx-onDurationTimer, which indicates the duration at the start of the DRX cycle;

[0234] (2) drx-SlotOffset, which indicates the delay before starting drx-onDurationTimer;

[0235] (3) drx-On-Duration list, which indicates one or more periods required for PDCCH monitoring on DRX-On-Duration. The item size of this list can be greater than or equal to 1. Each item in the list can include at least one of the following:

[0236] (a) a start offset which instructs the UE to start PDCCH monitoring at an offset relative to the start of the DRX-On-Duration; or

[0237] (b) Length, which indicates the time length for which the UE should keep monitoring. The default value of the length may be 1 ms.

[0238] In some embodiments, in the case of BS CU-DU separation, the CU may send a "bitmap indication associated with DRX-On-Duration" or an "information list associated with one or more subsets of DRX-On-Duration" to the DU, which helps the DU configure the drx-On-Duration bitmap or drx-On-Duration list. In some embodiments, the CU may recommend which PDCCH monitoring opportunity (e.g., subframe, time slot or symbol) is required for PDCCH monitoring on DRX-On-Duration for the DU, and send the PDCCH monitoring opportunity to the DU as a reference.

[0239] For example:

[0240] (1) The CU may recommend a drx-On-Duration list for the DU and send the drx-On-Duration list to the DU as a reference; or

[0241] (2) CU may recommend a drx-On-Duration bitmap for a DU and send the drx-On-Duration bitmap to the DU as a reference. In an embodiment, the CU may send a jitter range list to the DU, which helps the DU configure the drx-On-Duration bitmap.

[0242] After receiving the DRX configuration, the UE may determine the PDCCH monitoring timing on the DRX-On-Duration according to the drx-On-Duration list information in the DRX configuration.

[0243] In an embodiment, the BS may send a DRX-On-Duration command associated with a drx-On-Duration list via a DCI or a MAC CE. Fig.13 The embodiment is described as follows. For example, the DRX-On-Duration command MAC CE includes a drx-On-Duration list indicating one or more periods required for PDCCH monitoring on DRX-On-Duration. The item size of this list may be greater than or equal to 1. Each item in the list may include at least one of the following:

[0244] (1) a start offset, which instructs the UE to start PDCCH monitoring at an offset relative to the start of the DRX-On-Duration; or

[0245] (2) Length, which indicates the time length for which the UE should keep monitoring. The default value of the length may be 1 ms.

[0246] After the UE receives the DRX-On-Duration command via DCI or MAC CE, the UE may:

[0247] (1) In the current DRX cycle, the DRX-On-Duration command is applied starting from DRX-On-Duration; or

[0248] (2) In the next DRX cycle, the DRX-On-Duration command is applied starting from DRX-On-Duration.

[0249] Fig.13 An exemplary diagram illustrating a MAC sub-PDU according to some embodiments of the present application. In the exemplary case of a DRX-On-Duration command MAC CE, the BS may send this MAC CE and a MAC sub-header to the UE in a MAC sub-PDU. Fig.13 In the embodiment, in the MAC sub-PDU including the MAC CE, the DRX-On-Duration command MAC CE may be a fixed-size or variable-size MAC CE. For example, the length of the fixed-size MAC CE may be 8 bits or 16 bits.

[0250] like Fig.13 As shown in FIG. 1 , in a MAC sub-PDU including a MAC CE, the MAC sub-header may include at least one of the following:

[0251] (1) LCID: Logical Channel ID field, which identifies the type of the corresponding DRX-On-Duration command MAC CE.

[0252] (2) L: Length field, which indicates the length of the variable-size MAC CE in bytes. Each MAC subheader has an L field, except for the subheader corresponding to the fixed-size MAC CE. The size of the L field is indicated by the F field.

[0253] (3) F: Format field, which indicates the size of the length field. Each MAC subheader has an F field, except for the subheader corresponding to a fixed-size MAC CE. The size of the F field can be 1 bit. A value of 0 in the F field indicates an 8-bit length field. A value of 1 in the F field indicates a 16-bit length field.

[0254] Fig.14 An exemplary diagram regarding a DRX timer according to some embodiments of the present application is illustrated. Fig.14Embodiments of the present invention relate to delaying the start timing of drx-InactivityTimer and drx-RetransmissionTimerUL. In these embodiments, if multi-slot scheduling is received in a single DCI carried on a PDCCH transmission, the start timing of drx-InactivityTimer and drx-RetransmissionTimerUL of the DRX group is delayed. Multi-slot scheduling in a single DCI can be used for UL or DL. Multi-slot scheduling for new transmission means scheduling multiple initial transmission TBs (not repeated). Multi-slot scheduling for retransmission means scheduling multiple retransmission TBs (not repeated).

[0255] Fig.14 Some embodiments of relate to the start timing of the drx-InactivityTimer. In these embodiments, if the PDCCH transmission indicates a new transmission (DL or UL) on a serving cell in this DRX group, and if the new transmission is one of multiple slot new transmissions indicated in a single DCI, the UE may:

[0256] (1) upon receiving a PDCCH transmission for a new transmission, the drx-InactivityTimer of the DRX group is not started; or

[0257] (2) Delay the start timing of the drx-InactivityTimer of this DRX group until the first symbol that appears in the time domain after the last PDSCH transmission (in a bundle or timeslot group) ends.

[0258] Fig.14 Some other embodiments of relate to the start timing of drx-RetransmissionTimerUL. In these embodiments, if the PDCCH transmission indicates a UL transmission on a serving cell in this DRX group, and if the UL transmission is one of the multi-slot transmissions indicated in a single DCI, the UE may:

[0259] (1) starting drx-HARQ-RTT-TimerUL for the corresponding HARQ process in the symbol that first appears in the time domain after the end of the first transmission (within the bundle) of the corresponding PUSCH transmission; and

[0260] (2) Stop drx-RetransmissionTimerUL for the corresponding HARQ process.

[0261] In these embodiments, if the drx-HARQ-RTT-TimerUL expires, and if the drx-HARQ-RTT-TimerUL for the corresponding HARQ process is associated with a multi-slot transmission indicated in a single DCI, the UE may start the drx-RetransmissionTimerUL for the corresponding HARQ process at a subsequent timing within the following two timings:

[0262] (1) In the symbol that first appears in the time domain after the expiration of drx-HARQ-RTT-TimerUL.

[0263] (2) Until the symbol that first appears in the time domain after the last PUSCH transmission (within a bundle or slot group) ends.

[0264] The details described in all other embodiments of this application apply to Figures 11 to 14 In any embodiment of the present invention. In addition, Figures 11 to 14 The details described in any of the embodiments apply to Figures 1 to 10 and Figures 15 to 18 All embodiments of the invention.

[0265] Fig.15 An exemplary flow chart illustrating configuration of DCP functionality according to some embodiments of the present application. Fig.15 The exemplary method 1500 in FIG. 1 may be performed by a network node (eg, a BS). Although described with respect to a BS, it should be understood that other devices may be configured to perform the same. Fig.15 A similar approach to the one used in this paper.

[0266] exist Fig.15 In the exemplary method 1500 of , in operation 1501, a network node (e.g., Figure 1 BS101 shown in FIG. 1) from UE (such as Figure 1 102) receives a capability to support operations for determining a start timing of an on-duration window of a DCP cycle in a time domain of the UE. In some embodiments, the configuration is transmitted via RRC signaling (e.g., an RRC reconfiguration message) or a dynamic command (e.g., a DCI or a MAC CE). In some embodiments, the start timing of the on-duration window is: a start subframe or a start time slot or a start symbol.

[0267] In operation 1502, the network node transmits a configuration regarding DCP functionality to the UE. Fig.16 The configuration may include at least one of the following:

[0268] (1) DCP cycle information, which is used to determine the non-integer length value of the DCP cycle;

[0269] (2) DCP start offset information (e.g., DCP-Start-Offset-Ext), which indicates an offset value related to a reference SFN in the time domain;

[0270] (3) DCP on duration window, which indicates the duration at the start of the DCP cycle;

[0271] (4) DCP Slot Offset, which indicates the delay before starting the DCP on-duration window;

[0272] (5) DCP-LongCycleStartOffset: Long DCP cycle and DCP start offset, which defines the subframe where the long and short DCP cycles start;

[0273] (6) DCP ShortCycle: short DCP cycle; or

[0274] (7) DCP on-duration information, which indicates which opportunity(s) in the time domain are required for monitoring PDCCH transmission in the on-duration window of the DCP cycle. In some embodiments, the DCP on-duration information is a bitmap indication (e.g., drx-On-Duration bitmap) or an information list (e.g., drx-On-Duration list) associated with the on-duration window.

[0275] Those skilled in the art will appreciate that the sequence of operations in the exemplary process 1500 may be changed and some operations in the exemplary process 1500 may be eliminated or modified without departing from the spirit and scope of the present disclosure. The details described in all other embodiments of the present application apply to Fig.15 In addition, in Fig.15 The details described in the embodiments apply to Figures 1 to 14 And all embodiments of 16 to 18.

[0276] Some other embodiments of the present application relate to exemplary flow charts that can be performed by a UE for receiving configurations of serving cells in a DRX group. Although described with respect to a UE, it should be understood that other devices can be configured to perform methods similar to these embodiments. In this exemplary flow chart, a UE (e.g., Figure 1 UE 102 shown in FIG. 1 ) receives a request from a network (e.g., Figure 1 101 shown in FIG. 10A ) receives configuration regarding DCP functionality. In some embodiments, the configuration may be received via RRC signaling (e.g., an RRC reconfiguration message) or a dynamic command (e.g., a DCI or a MAC CE). The configuration may include at least one of the following:

[0277] (1) DCP cycle information, which is used to determine the non-integer length value of the DCP cycle;

[0278] (2) DCP start offset information (e.g., DCP-Start-Offset-Ext), which indicates an offset value related to a reference SFN in the time domain;

[0279] (3) DCP on duration window, which indicates the duration at the start of the DCP cycle;

[0280] (4) DCP Slot Offset: The delay before starting the DCP open duration window;

[0281] (5) DCP-LongCycleStartOffset: Long DCP cycle and DCP start offset, which defines the subframe where the long and short DCP cycles start;

[0282] (6) DCP ShortCycle: short DCP cycle; or

[0283] (7) DCP on-duration information, which indicates which timing(s) in the time domain are required for monitoring PDCCH transmission in the on-duration window of the DCP cycle.

[0284] In some embodiments, the UE may determine the start timing of the on-duration window of a DRX cycle in the time domain according to at least one of the DCP timeslot offset, the DCP cycle information, or the DCP start offset information. In an embodiment, the start timing of the on-duration window is the start subframe or the start timeslot or the start symbol.

[0285] In some embodiments, the UE may determine the Nth start position of the DRX duration based on the non-integer DRX cycle, DCP-Start-Offset and DCP-Slot-offset. The DCP on-duration start position is in subframes or in ms, as defined in the following formula.

[0286] Formula (9): [(SFN×10)+Subframe Number] modulo (DCP-ShortCycle)=(DCP-Start-Offset) modulo (DCP-ShortCycle); or

[0287] Formula (10): [(SFN×10)+subframe number] modulo (DCP-LongCycle)=DCP-Start-Offset.

[0288] Then, the MAC entity of the UE may start the DCP-onDurationTimer after the DCP-SlotOffset from the start of the subframe.

[0289] In some embodiments, the UE may monitor the PDCCH transmission in the on-duration window of the DCP cycle according to the DCP on-duration information. In an embodiment, the DCP on-duration information is a bitmap indication or information list associated with the on-duration window. Fig.16 The embodiments are described as follows.

[0290] Those skilled in the art will appreciate that the sequence of operations in the exemplary process 1500 may be changed and some operations in the exemplary process 1500 may be eliminated or modified without departing from the spirit and scope of the present disclosure. The details described in all other embodiments of the present application apply to Fig.15 In addition, in Fig.15 The details described in the embodiments apply to Figures 1 to 14 And all embodiments of 16 to 18.

[0291] Fig.16 An exemplary diagram illustrating sparse DCP on-duration set by a bitmap according to some embodiments of the present application. Fig.16 Embodiments of the invention relate to replacing a non-integer period DCP duration of DRX-On-Duration. Fig.16 In an embodiment of the present application, similar to the embodiment of the present application as described above, the UE may periodically monitor the DCP (DCI with CRC scrambled by PS-RNTI) command based on a non-integer DCP cycle and DCP-Start-offset. If the DCP command indicates to monitor PCCCH transmission, the UE may start PDCCH monitoring activities for C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI and AI-RNTI of the MAC entity.

[0292] exist Fig.16 In an embodiment, the BS may send a DCP configuration to the UE, where the DCP configuration includes:

[0293] (1) PS-RNTI, which is used to indicate by which DCI with CRC is scrambled. The PS-RNTI may be different from the PS-RNTI as defined in 3GPP Rel-16.

[0294] (2) Search space ID, which indicates the search space ID used to acquire the PDCCH scrambled by the PS-RNTI. This ID may be independent of the search space ID used to acquire the PDCCH of the PS-RNTI as defined in 3GPP Rel-16.

[0295] (3) The size of DCI.

[0296] (4) DCP-onDuration Timer: The duration at the start of the DCP cycle. DCP-onDurationTimer can also be called DCP-onDuration Window or DCP On Duration.

[0297] (5) DCP Slot Offset: The delay before starting the DCP open duration window;

[0298] (6) DCP-Start-Offset: The subframe where the long and short DCP cycles start;

[0299] (7) DCP-Start-Offset-Ext, which indicates the offset relative to the time reference SFN=0

[0300] (8) DCP-Non-integer cycle, which has a non-integer value indicating the true rhythm of the service.

[0301] For 60fps, DCP-Non-integer cycle=1000 / 60ms.

[0302] For 30fps, DCP-Non-integer cycle=1000 / 30ms.

[0303] For 90fps, DCP-Non-integer cycle=1000 / 90ms.

[0304] (9) DCP-On-Duration-bitmap, which is used to indicate which subframe(s) are required for PDCCH monitoring on DCP-On-Duration-Time:

[0305] • The first / leftmost bit in this bitmap corresponds to the first subframe on the DRX-On-Duration-Time.

[0306] • A value of 0 in this bitmap indicates that the corresponding subframe is not allowed to be used for PDCCH monitoring.

[0307] • A value of 1 in this bitmap indicates that the corresponding subframe is allowed to be used for PDCCH monitoring.

[0308] (10) InactivityTimer: It indicates the duration after a PDCCH opportunity where the PDCCH indicates a new UL or DL ​​transmission by the MAC entity.

[0309] In some embodiments, in the case of BS CU-DU separation, the CU may recommend which PDCCH monitoring opportunity (e.g., subframe, time slot or symbol) is required for PDCCH monitoring on DCP-On-Duration for the DU, and send the PDCCH monitoring opportunity to the DU as a reference. For example:

[0310] (1) The CU may recommend a dcp-On-Duration list for the DU and send the dcp-On-Duration list to the DU as a reference; or

[0311] (2) The CU may recommend a dcp-On-Duration bitmap for the DU and send the dcp-On-Duration bitmap to the DU as a reference.

[0312] exist Fig.16 In an embodiment of the present invention, if the UE receives a DCP configuration in an active bandwidth part (BWP), the UE may determine the Nth start position of the DCP duration based on a non-integer DCP period and DCP-Start-offset. For example, the determination formula may be the same as any one of formulas (1) to (8) described above. Fig.16 In some embodiments, if the UE is in DRX inactive time, the UE may monitor the DCP indication during the DCP duration. In some embodiments, the UE may receive a DCP command and determine to start PDCCH monitoring activities for C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI and AI-RNTI of the MAC entity. In some embodiments, if the DCP indication received from the lower layer of the UE indicates that the UE enters the DRX active time, the UE may:

[0313] (1) Start the InactivityTimer immediately after the minimum preparation interval; or

[0314] (2) Start the InactivityTimer after an offset, which may be indicated in the DCP indication or configured in a previous RRC message.

[0315] The details described in all other embodiments of this application apply to Fig.16 In addition, in Fig.16 The details described in the embodiments apply to Figures 1 to 15 , 17 and 18 of all embodiments.

[0316] Fig.17 An exemplary block diagram illustrating a device 1700 for power saving operation according to some embodiments of the present application. Fig.17 , the apparatus 1700 may include at least one non-transitory computer-readable medium 1702, at least one receiving circuit system 1704, at least one transmitting circuit system 1706, and at least one processor 1708 coupled to the non-transitory computer-readable medium 1702, the receiving circuit system 1704, and the transmitting circuit system 1706. The at least one processor 1708 may be a CPU, a DSP, a microprocessor, etc. The apparatus 1700 may be a network node (e.g., a BS) or a UE configured to perform the methods described above, etc.

[0317] Although elements such as at least one processor 1708, receive circuitry 1704, and transmit circuitry 1706 are described in the singular in this figure, the plural form is contemplated unless explicitly limited to the singular. In some embodiments of the present application, receive circuitry 1704 and transmit circuitry 1706 may be combined into a single device, such as a transceiver. In certain embodiments of the present application, apparatus 1700 may further include an input device, a memory, and / or other components.

[0318] In some embodiments of the present application, a non-transitory computer-readable medium 1702 may store thereon computer-executable instructions to enable a processor to implement the method described or illustrated above with respect to a UE or a network node (e.g., a BS). For example, when the computer-executable instructions are executed, the processor 1708 interacts with the receiving circuit system 1704 and the transmitting circuit system 1706 to perform the steps described or illustrated above with respect to a UE or a network node (e.g., a BS).

[0319] Fig.18 A further exemplary block diagram illustrating an apparatus 1800 for power saving operation according to some embodiments of the present application. Fig.18 , the device 1800 (e.g., a BS or a UE) may include at least one processor 1802 and at least one transceiver 1804 coupled to the at least one processor 1802. The transceiver 1804 may include at least one separate receive circuit system 1806 and transmit circuit system 1808, or at least one integrated receive circuit system 1806 and transmit circuit system 1808. The at least one processor 1802 may be a CPU, a DSP, a microprocessor, etc.

[0320] According to some embodiments of the present application, when the device 1800 is a UE, the processor 1802 is configured to: receive a first configuration of one or more service cells in a discontinuous reception (DRX) group from the network via the transceiver 1804, wherein the first configuration includes at least one of the following: DRX cycle information, which is used to determine a non-integer length value of the DRX cycle; or DRX start offset information, which indicates an offset value related to a reference SFN in the time domain; and determine a first starting timing of an opening duration window of the DRX group in the time domain according to at least one of the DRX cycle information or the DRX start offset information.

[0321] According to some embodiments of the present application, when the device 1800 is a UE, the processor 1802 is configured to: receive a second configuration of one or more service cells in a DRX group from the network via the transceiver 1804, wherein the second configuration indicates a subset of an on-duration window of the DRX group in the time domain; and monitor PDCCH transmissions in the subset of the on-duration windows according to the second configuration.

[0322] According to some embodiments of the present application, when the device 1800 is a UE, the processor 1802 is configured to: receive a configuration regarding DCP functionality from the network via the transceiver 1804, wherein the configuration includes at least one of the following: DCP cycle information, which is used to determine a non-integer length value of the DCP cycle; DCP start offset information, which indicates an offset value related to a reference SFN in the time domain; or DCP on-duration information, which indicates which opportunities in the time domain are required for monitoring PDCCH transmission in the on-duration window of the DCP cycle.

[0323] According to some other embodiments of the present application, when the device 1800 is a network node (e.g., a BS), the processor 1802 is configured to: receive from the UE via the transceiver 1804 a capability to support operations for determining a start timing of an open duration window of a DRX group in a time domain of the UE; and transmit to the UE via the transceiver 1804 a configuration of one or more service cells in the DRX group, wherein the configuration includes at least one of the following: DRX cycle information for determining a non-integer value of the DRX cycle; DRX start offset information indicating an offset value related to a reference SFN in the time domain; or information associated with the reference SFN.

[0324] According to some other embodiments of the present application, when the device 1800 is a network node (e.g., a BS), the processor 1802 is configured to: receive from the UE via the transceiver 1804 a capability to support operations for PDCCH transmission in a subset of the on-duration window of a DRX group for monitoring the UE; and transmit to the UE via the transceiver 1804 a configuration of one or more service cells in the DRX group, wherein the configuration indicates a subset of the on-duration window of the DRX group in the time domain.

[0325] According to some other embodiments of the present application, when the device 1800 is a network node (e.g., a BS), the processor 1802 is configured to: receive from the UE via the transceiver 1804 a capability to support operations for determining a start timing of an on-duration window of a DCP cycle in a time domain of the UE; and transmit to the UE via the transceiver 1804 a configuration regarding DCP functionality, wherein the configuration includes at least one of the following: DCP cycle information for determining a non-integer length value of the DCP cycle; DCP start offset information indicating an offset value associated with a reference SFN in the time domain; or DCP on-duration information indicating which opportunities in the time domain are required for monitoring PDCCH transmission in the on-duration window of the DCP cycle.

[0326] The method of the present disclosure can be implemented on a programmed processor. However, the controller, flow chart and module can also be implemented on a general or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit components, an integrated circuit, a hardware electronic or logic circuit (such as a discrete element circuit), a programmable logic device, etc. In general, any device with a finite state machine capable of implementing the flow chart shown in the figure can be used to implement the processing functions of the present disclosure.

[0327] Although the present disclosure has been described with its specific embodiments, it is apparent that many alternatives, modifications and variations may be apparent to those skilled in the art. For example, various components of the embodiments may be interchanged, added or replaced in other embodiments. In addition, the operation of the disclosed embodiments does not require all elements of each figure. For example, it will enable a person of ordinary skill in the art to make and use the teachings of the present disclosure by simply adopting the elements of the independent claims. Therefore, the embodiments of the present disclosure as set forth herein are intended to be illustrative rather than restrictive. Various changes may be made without departing from the spirit and scope of the present disclosure.

[0328] In this file, the term "includes / including" or any other variation thereof is intended to cover non-exclusive inclusion, so that the process, method, article or equipment comprising a series of elements not only includes those elements, but also may include other elements that are not explicitly listed or inherent to this process, method, article or equipment. In the absence of more constraints, an element starting with "a / an" or the like does not exclude the presence of additional identical elements in the process, method, article or equipment comprising the element. In addition, the term "another" is defined as at least the second or more. As used herein, the term "having" and the like are defined as "including". For example, the expression of "A and / or B" or "at least one of A and B" may include any and all combinations of words listed together with the expression. For example, the expression "A and / or B" or "at least one of A and B" may include A, B or both A and B. The words "first", "second", etc. are only used to clearly illustrate the embodiments of the present application, and are not used to limit the essence of the present application.

Claims

1. A user equipment UE, comprising: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: Receiving, via the transceiver, a first configuration of one or more serving cells in a discontinuous reception (DRX) group from a network, wherein the first configuration includes at least one of the following: DRX cycle information, which is used to determine a non-integer length value of a DRX cycle; or DRX start offset information indicating an offset value related to a reference system frame number SFN in the time domain; and A first start timing of an on-duration window of the DRX group in the time domain is determined according to at least one of the DRX cycle information or the DRX start offset information.

2. The UE according to claim 1, wherein the processor of the UE is configured to determine a second start timing of the on-duration window of the DRX group in the time domain according to at least one of the DRX cycle information or the DRX start offset information.

3. The UE according to claim 1 or claim 2, wherein the first configuration further includes information associated with the reference SFN, and wherein at least one of the first start timing or the second start timing of the open duration window is further determined according to the information associated with the reference SFN.

4. The UE of claim 1, wherein the processor of the UE is configured to: receiving, via the transceiver, from the network a second configuration of the one or more serving cells in the DRX group, wherein the second configuration indicates a subset of the on-Duration windows; and Physical Downlink Control Channel (PDCCH) transmissions in the subset of the OnDuration windows are monitored according to the second configuration.

5. The UE of claim 4, wherein the second configuration comprises at least one of: a bitmap indication associated with the on-duration window; or A list of information associated with one or more subsets of the on-duration windows.

6. The UE according to claim 5, wherein the information list indicates at least one of the following: a start timing of a subset within the one or more subsets of the on-duration windows; or The length of the subset within the one or more subsets of the on-duration windows. 7 . The UE according to claim 4 , wherein the second configuration indicates which opportunities in the time domain are required to monitor the PDCCH transmissions in the subset of the on-Duration windows.

8. The UE according to any one of claims 4, 5 and 7, wherein the second configuration is received via Radio Resource Control (RRC) signaling or a dynamic command.

9. A UE according to claim 1, wherein the processor of the UE is configured to receive a single downlink control information DCI for scheduling multiple time slots in the time domain for a downlink DL or uplink UL of the UE from the network via the transceiver on a serving cell in the DRX group, and wherein each time slot within the multiple time slots corresponds to a unique hybrid automatic repeat request HARQ process of the UE.

10. The UE of claim 9, wherein in response to the single DCI for scheduling the multiple time slots for the DL or the UL and in response to receiving a PDCCH transmission on the serving cell in the DRX group indicating a new DL or UL transmission within the multiple time slots, the processor of the UE is configured to: not starting the DRX inactivity timer of the DRX group; or The start timing of the DRX inactivity timer of the DRX group is delayed until a symbol first appears in the time domain after the timing of the last physical downlink shared channel (PDSCH) transmission in the plurality of time slots ends.

11. The UE of claim 9, wherein in response to the single DCI for scheduling the plurality of time slots for the UL and in response to expiration of a DRX HARQ round trip time (RTT) timer for physical uplink shared channel (PUSCH) transmissions within the plurality of time slots for a corresponding hybrid automatic repeat request (HARQ) process, the processor of the UE is configured to start a DRX retransmission timer for the UL for the corresponding HARQ process at a subsequent timing between: a symbol that first occurs in the time domain after the expiration of the DRX HARQ RTT timer for the UL; and A symbol that first appears in the time domain after the timing of the last PUSCH transmission in the plurality of time slots ends.

12. A user equipment UE, comprising: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: receiving, via the transceiver, from a network a second configuration of one or more serving cells in a discontinuous reception (DRX) group, wherein the second configuration indicates a subset in an on-duration window time domain of the DRX group; and Physical Downlink Control Channel (PDCCH) transmissions in the subset of the OnDuration windows are monitored according to the second configuration.

13. The UE of claim 12, wherein the second configuration comprises at least one of: a bitmap indication associated with the on-duration window; or A list of information associated with one or more subsets of the on-duration windows.

14. The UE of claim 12, wherein the processor of the UE is configured to: receiving, via the transceiver, first information associated with a DRX On-Duration window length from the network; receiving, via the transceiver, from the network DRX time slot offset information indicating a time slot delay value before starting the DRX on-duration window in the time domain; receiving, via the transceiver, from the network, second information associated with the DRX cycle in the time domain and a start offset value of the DRX cycle; and A first start timing of the on-duration window of the DRX group in the time domain is determined according to at least one of the first information, the DRX time slot offset information, or the second information.

15. A network node, comprising: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: receiving, via the transceiver, from a user equipment UE, a capability to support an operation for determining a start timing of an on-duration window of a discontinuous reception (DRX) group in a time domain of the UE; and transmitting, via the transceiver, to the UE, a configuration of one or more serving cells in the DRX group, wherein the configuration comprises at least one of: DRX cycle information, which is used to determine a non-integer value of a DRX cycle; DRX start offset information indicating an offset value related to a reference system frame number SFN in the time domain; or Information associated with the reference SFN.