Patent Description:
Some exemplary embodiments are related to a processor of a user equipment (UE) configured to perform operations. The operations include receiving channel state information (CSI) configuration information corresponding to downlink new radio (NR) traffic with non-integer periodicity, wherein the CSI configuration information includes one of CSI measurement configuration information, CSI reporting configuration information or CSI measurement configuration information and CSI reporting configuration information, receiving CSI measurement resources and reporting CSI feedback to a network.

The exemplary embodiments may be further understood with reference to the following description and the related appended drawings, wherein like elements are provided with the same reference numerals. The exemplary embodiments introduce techniques for handling traffic that may not match integer multiples of the units of time supported in new radio (NR). In one aspect, the exemplary embodiments relate to channel state information (CSI) feedback. As will be described in more detail below, some of the exemplary techniques described herein may enable a user equipment (UE) to implement power efficient CSI feedback for traffic such as eXtended reality (XR) traffic that may be generated at cadences which are not integer multiples of NR units of time (e.g., non-integer periodicity). In another aspect, the exemplary embodiments relate to connected discontinuous reception (cDRX). As will be described in more detail below, some of the exemplary techniques described herein enable the UE to implement cDRX for NR traffic that may be generated at cadences which are not integer multiples of NR's default timing.

The exemplary embodiments are described with regard to eXtended Reality (XR). Those skilled in the art will understand that XR is an umbrella term for different types of realities and may generally refer to real-and-virtual combined environments and associated human-machine interactions generated by computer technology and wearables. To provide some examples, the term XR may encompass augmented reality (AR), mixed reality (MR) and virtual reality (VR). However, any reference to XR being specific to a particular use case or type of traffic is merely provided for illustrative purposes. The exemplary embodiments apply to any type of NR traffic that may be generated at cadences which are not integer multiples of NR's default timing.

During operation, XR services may utilize multiple data flows in the uplink (UL) and/or downlink (DL). For example, in the DL, there may be a video stream, an audio stream and/or a data stream. In the UL, there may be a control stream and/or a pose stream. From a physical channel perspective, there may be different control channels and shared channels for each stream or multiple streams may share a control channel and/or shared channel. In some configurations, each stream may have different quality of service (QoS) requirements (e.g., block error rate (BLER), latency requirements, etc.).

In addition, the exemplary embodiments are described with regard to a UE. Those skilled in the art will understand that the UE may be any type of electronic component that is configured to communicate via a network, e.g., mobile phones, tablet computers, desktop computers, smartphones, phablets, embedded devices, wearables, Internet of Things (IoT) devices, etc. With regard to XR, in some configurations, the UE may be paired with a wearable device (e.g., a head mounted display (HMD), AR glasses, etc.). In this type of configuration, the UE may communicate directly with the network and then relay data to the wearable device which presents the XR content to the user (e.g., AR, VR, MR, etc.). In other configurations, the UE may be a wearable device that communicates directly with the network and presents the XR content to the user. Therefore, the UE as described herein is used to represent any electronic component that directly communicates with the network.

Although the exemplary embodiments are described with regard to providing enhancements for XR services, the exemplary embodiments are not limited to XR services and may apply to any type of NR traffic configured with non-integer periodicity. To provide another example, in industrial Internet of things (IIoT), traffic may be generated from an installed system with a long use life. In this type of scenario, it is difficult to modify the traffic generation periodicity to match any of NR's units of time. Those skilled in the art will understand how the exemplary techniques described herein may be applied to IIoT and any other type of NR traffic that may not match NR's default timing.

In one aspect, the exemplary embodiments introduce CSI feedback enhancements for XR. As will be described in more detail below, CSI feedback enhancements including measurement and/or reporting matched to traffic arrival are introduced to improve UE power saving and performance with regard to XR (or any other type of traffic that may not match NR's existing timing). Further, exemplary enhancements to enable periodic (P) and semi-persistent (SP) CSI measurement and reporting matched to the application traffic periodicity and offset are introduced In addition, CSI feedback measurement and/or reporting matched to semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) reception are introduced. The exemplary CSI feedback enhancements described herein may be used in conjunction with currently implemented CSI feedback techniques, future implementations of CSI feedback techniques or independently from other CSI feedback techniques.

In another aspect, the exemplary embodiments introduce cDRX enhancements for XR. As will be described in more detail below, UE power efficient cDRX configurations for XR traffic (or any other type of NR traffic that may not match NR's default timing) are introduced. These enhancements may include non-integer periodicity for cDRX configuration, using a combination of long DRX and short DRX to match traffic periodicity and using a physical downlink control channel (PDCCH) wake up signal (WUS) to indicate dynamic traffic. The exemplary cDRX enhancements described herein may be used in conjunction with currently implemented cDRX mechanisms, future implementations of cDRX mechanisms or independently from other cDRX mechanisms.

<FIG> shows an exemplary network arrangement <NUM> according to various exemplary embodiments. The exemplary network arrangement <NUM> includes a UE <NUM>. Those skilled in the art will understand that the UE <NUM> may be any type of electronic component that is configured to communicate via a network, e.g., mobile phones, tablet computers, desktop computers, smartphones, phablets, embedded devices, wearables (e.g., HMD, AR glasses, etc.), Internet of Things (IoT) devices, etc. It should also be understood that an actual network arrangement may include any number of UEs being used by any number of users. Thus, the example of a single UE <NUM> is merely provided for illustrative purposes.

The UE <NUM> may be configured to communicate with one or more networks. In the example of the network configuration <NUM>, the network with which the UE <NUM> may wirelessly communicate is a <NUM> NR radio access network (RAN) <NUM>. However, the UE <NUM> may also communicate with other types of networks (e.g. <NUM> cloud RAN, a next generation RAN (NG-RAN), a long term evolution (LTE) RAN, a legacy cellular network, a WLAN, etc.) and the UE <NUM> may also communicate with networks over a wired connection. With regard to the exemplary embodiments, the UE <NUM> may establish a connection with the <NUM> NR RAN <NUM>. Therefore, the UE <NUM> may have a <NUM> NR chipset to communicate with the NR RAN <NUM>.

The <NUM> NR RAN <NUM> may be a portion of a cellular network that may be deployed by a network carrier (e.g., Verizon, AT&T, T-Mobile, etc.). The <NUM> NR RAN <NUM> may include, for example, cells or base stations (Node Bs, eNodeBs, HeNBs, eNBS, gNBs, gNodeBs, macrocells, microcells, small cells, femtocells, etc.) that are configured to send and receive traffic from UEs that are equipped with the appropriate cellular chip set.

The UE <NUM> may connect to the <NUM> NR-RAN <NUM> via the gNB 120A. Those skilled in the art will understand that any association procedure may be performed for the UE <NUM> to connect to the <NUM> NR-RAN <NUM>. For example, as discussed above, the <NUM> NR-RAN <NUM> may be associated with a particular cellular provider where the UE <NUM> and/or the user thereof has a contract and credential information (e.g., stored on a SIM card). Upon detecting the presence of the <NUM> NR-RAN <NUM>, the UE <NUM> may transmit the corresponding credential information to associate with the <NUM> NR-RAN <NUM>. More specifically, the UE <NUM> may associate with a specific base station (e.g., gNB 120A). However, as mentioned above, reference to the <NUM> NR-RAN <NUM> is merely for illustrative purposes and any appropriate type of RAN may be used.

The network arrangement <NUM> also includes a cellular core network <NUM>, the Internet <NUM>, an IP Multimedia Subsystem (IMS) <NUM>, and a network services backbone <NUM>. The cellular core network <NUM> may be considered to be the interconnected set of components that manages the operation and traffic of the cellular network. The cellular core network <NUM> also manages the traffic that flows between the cellular network and the Internet <NUM>. The IMS <NUM> may be generally described as an architecture for delivering multimedia services to the UE <NUM> using the IP protocol. The IMS <NUM> may communicate with the cellular core network <NUM> and the Internet <NUM> to provide the multimedia services to the UE <NUM>. The network services backbone <NUM> is in communication either directly or indirectly with the Internet <NUM> and the cellular core network <NUM>. The network services backbone <NUM> may be generally described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a suite of services that may be used to extend the functionalities of the UE <NUM> in communication with the various networks.

<FIG> shows an exemplary UE <NUM> according to various exemplary embodiments. The UE <NUM> will be described with regard to the network arrangement <NUM> of <FIG>. The UE <NUM> may include a processor <NUM>, a memory arrangement <NUM>, a display device <NUM>, an input/output (I/O) device <NUM>, a transceiver <NUM> and other components <NUM>. The other components <NUM> may include, for example, an audio input device, an audio output device, a power supply, a data acquisition device, ports to electrically connect the UE <NUM> to other electronic devices, etc..

The processor <NUM> may be configured to execute a plurality of engines of the UE <NUM>. For example, the engines may include a CSI feedback for XR engine <NUM> and a cDRX for XR engine <NUM>. The CSI feedback for XR engine <NUM> may perform various operations related to the exemplary CSI feedback enhancements described herein. These operations may include, but are not limited to, receiving CSI configuration information, identifying CSI resources, performing CSI measurements and reporting CSI feedback. The cDRX for XR engine <NUM> may perform various operations related to the exemplary cDRX enhancements described herein. These operations may include, but are not limited to, receiving cDRX configuration information, implementing a cDRX cycle and receiving PDCCH.

The above referenced engines <NUM>, <NUM> each being an application (e.g., a program) executed by the processor <NUM> is merely provided for illustrative purposes. The functionality associated with the engines <NUM>, <NUM> may also be represented as a separate incorporated component of the UE <NUM> or may be a modular component coupled to the UE <NUM>, e.g., an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information. The engines may also be embodied as one application or separate applications. In addition, in some UEs, the functionality described for the processor <NUM> is split among two or more processors such as a baseband processor and an applications processor. The exemplary embodiments may be implemented in any of these or other configurations of a UE.

The memory arrangement <NUM> may be a hardware component configured to store data related to operations performed by the UE <NUM>. The display device <NUM> may be a hardware component configured to show data to a user while the I/O device <NUM> may be a hardware component that enables the user to enter inputs. The display device <NUM> and the I/O device <NUM> may be separate components or integrated together such as a touchscreen. The transceiver <NUM> may be a hardware component configured to establish a connection with the <NUM> NR-RAN <NUM> and/or any other appropriate type of network. Accordingly, the transceiver <NUM> may operate on a variety of different frequencies or channels (e.g., set of consecutive frequencies).

<FIG> shows an exemplary base station <NUM> according to various exemplary embodiments. The base station <NUM> may represent any access node (e.g., gNB 120A, etc.) through which the UE <NUM> may establish a connection and manage network operations.

The base station <NUM> may include a processor <NUM>, a memory arrangement <NUM>, an input/output (I/O) device <NUM>, a transceiver <NUM>, and other components <NUM>. The other components <NUM> may include, for example, a battery, a data acquisition device, ports to electrically connect the base station <NUM> to other electronic devices, etc..

The processor <NUM> may be configured to execute a plurality of engines of the base station <NUM>. For example, the engines may include a CSI for XR engine <NUM> and a cDRX configuration for XR engine <NUM>. The CSI for XR engine <NUM> may perform various operations related to the exemplary CSI feedback enhancements described herein. The operations may include but are not limited to, transmitting CSI feedback configurations information, transmitting CSI resources and receiving CSI feedback. The cDRX configuration for XR engine <NUM> may perform various operations related to the exemplary cDRX enhancements described herein. The operations may include, but are not limited to, transmitting cDRX configurations information and transmitting PDCCH in accordance with the cDRX configuration.

The above noted engines <NUM>, <NUM> being an application (e.g., a program) executed by the processor <NUM> is only exemplary. The functionality associated with the engines <NUM>, <NUM> may also be represented as a separate incorporated component of the base station <NUM> or may be a modular component coupled to the base station <NUM>, e.g., an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information. In addition, in some base stations, the functionality described for the processor <NUM> is split among a plurality of processors (e.g., a baseband processor, an applications processor, etc.). The exemplary embodiments may be implemented in any of these or other configurations of a base station.

The memory <NUM> may be a hardware component configured to store data related to operations performed by the base station <NUM>. The I/O device <NUM> may be a hardware component or ports that enable a user to interact with the base station <NUM>. The transceiver <NUM> may be a hardware component configured to exchange data with the UE <NUM> and any other UE in the system <NUM>. The transceiver <NUM> may operate on a variety of different frequencies or channels (e.g., set of consecutive frequencies). Therefore, the transceiver <NUM> may include one or more components (e.g., radios) to enable the data exchange with the various networks and UEs.

As mentioned above, in one aspect, the exemplary embodiments introduce CSI feedback enhancements for XR. <FIG> shows a signaling diagram <NUM> of CSI feedback for XR according to various exemplary embodiments. The signaling diagram <NUM> is described with regard to the network arrangement <NUM> of <FIG> and the UE <NUM> of <FIG>.

The signaling diagram <NUM> includes the UE <NUM> and the gNB 120A. In <NUM>, the UE <NUM> receives CSI measurement and/or reporting configuration information. In some embodiments, the CSI measurement and/or reporting configuration information may be provided to the UE <NUM> in one or more radio resource control (RRC) messages. In other embodiments, the CSI measurement and/or reporting configuration information may be provided to the UE <NUM> in one or more access control (MAC) control elements (CEs). However, the exemplary embodiments are not limited to RRC messages or MAC CEs, the CSI measurement and reporting configuration information may be provided to the UE <NUM> in any appropriate manner.

Various CSI feedback enhancements for XR will be described in detail below. Subsequently, examples of how the network may provide the UE <NUM> with the corresponding CSI measurement and reporting configuration information will be provided.

In <NUM>, the gNB 120A configures CSI measurement resources to the UE <NUM>. CSI resources may include channel measurement resources (CMR) and interference measurement resources (IMR). The CMRs may include one or more non-zero power (NZP) CSI-reference signals (RS). In NR, periodic and semi-persistent CMRs are supported. The periodicity and offset of these CMRs resources may be characterized in slots or in any other appropriate manner. Throughout this description, any reference to a particular type of CMR is merely provided for illustrative purposes, the exemplary embodiments may apply to any appropriate type of CMR.

The IMRs may include one or more zero power (ZP)-CSI-RS, NZP-CSI-RS or a combination thereof. Throughout this description, the terms "ZP IMR" and "CSI-IM" may be used interchangeably to identify the same type of CSI resources and "IMR" may refer to "ZP IMR," "NZP IMR" or a combination of "ZP IMR" and NZP IMR. In NR, periodic and semi-persistent IMRs are supported. The periodicity and offset of these IMRs may be characterized in slots or in any other appropriate manner. Throughout this description, any reference to a particular type of IMR is merely provided for illustrative purposes, the exemplary embodiments may apply to any appropriate type of IMR.

In <NUM>, the UE <NUM> performs CSI measurements based on the CSI measurement resources. In <NUM>, the UE <NUM> reports CSI feedback to the gNB 120A.

For XR service, the stream may be generated at cadences which are not integer multiples of NR units of time. To provide one example, XR video stream generation may occur at <NUM> or <NUM> frames per second. The exemplary embodiments introduce CSI measurement and reporting techniques to handle these types of timing issues in an efficient manner.

In some embodiments, the exemplary enhancements may be applied to only IMR. For example, periodic/semi-persistent CMR may be generated at a periodicity of X milliseconds (ms) where X represents an integer value (e.g., <NUM>, <NUM>, <NUM>, <NUM>, etc.) while periodic/semi-persistent IMR may be generated at a periodicity of Y ms where Y represents a non-integer value (e.g., <NUM>/<NUM>, <NUM>/<NUM>, etc.). In another embodiments, the exemplary enhancements may be applied to only CMR. In a further embodiment, the exemplary enhancements may be applied to both CMR and IMR.

In one example, the periodicity of the CSI reporting may be the same as the DL SPS periodicity or a multiple of the DL periodicity. The periodicity of the CSI reporting may be non-integer. <FIG> shows an example of CSI reporting every two DL SPS reception occasions.

The periodicity of the CSI measurement resource may also be non-integer and based on the DL SPS periodicity or a multiple of the DL periodicity. For example, the CSI measurement resource periodicity may be represented by (M1/M2) where M1 and M2 each represent an integer value. <FIG> shows an example of CSI measurement resources configured as a multiple of the DL SPS periodicity.

To enable periodic and semi-persistent CSI reporting with non-integer periodicity and offset, the CSI reporting and/or measurement configuration information may include an indication of the M1 integer, the M2 integer and an offset integer. <FIG> shows an example CSI-ReportPeriodicityAndOffset RRC parameter configured to include an indication of the supported non-integer periodicity and offset.

To indicate to the UE <NUM> the non-integer periodicity and offset for the CMR configuration, the CSI reporting and measurement configuration information may include an indication of the M1 integer, the M2 integer and an offset integer. <FIG> shows an example CSI-ResourcePeriodicityAndOffset RRC parameter configured to include an indication of the supported non-integer periodicity and offset for periodic and semi-persistent NZP CSI-RS.

To indicate to the UE <NUM> the non-integer periodicity and offset for the IMR configuration, the CSI reporting and measurement configuration information may include an indication of the M1 integer, the M2 integer and an offset integer. <FIG> shows an example CSI-ResourcePeriodicityAndOffset RRC parameter configured to include an indication of the supported non-integer periodicity and offset for periodic and semi-persistent CSI-IM.

In some embodiments, an association between the DL SPS configuration and the CSI measurement and reporting configuration may be implemented. In one example, the CSI reporting and measurement configuration is associated with the DL SPS configuration. Thus, in this example, the UE <NUM> may receive DL SPS configuration information and then determine the CSI measurement and reporting configuration based on the preconfigured association. In another example, the DL SPS configuration is associated with the CSI measurement and reporting configurations. Thus, in this example, the UE <NUM> may receive the CSI measurement and reporting configuration information and then determine the DL SPS configuration based on the preconfigured association. In a further example, an information element (IE) may be introduced that indicates to the UE <NUM> a relationship between the DL SPS configuration and the CSI measurement and reporting configuration.

For the exemplary enhancements to the CSI measurement resources, it may be beneficial to restrict the presence of CSI-RS to the DL SPS PDSCH. In some embodiments, the CSI-FrequencyOccupation RRC parameter is not explicitly configured according to the DL SPS PDSCH frequency allocation. Instead, the UE <NUM> may adapt the CSI measurement operations to the DL SPS PDSCH configuration. This allows these enhancements to be implemented without creating additional RRC signaling overhead.

Further, in some embodiments, the CSI-ReportingBand RRC parameter is not explicitly configured according to the DL SPS PDSCH frequency allocation. Instead, the UE <NUM> may adapt the CSI reporting operations to the DL SPS PDSCH configuration. For example, if the PDSCH is from physical resource block (PRB) <NUM> to PRB <NUM>, then CSI measurement is assumed for a CSI subband or subbands enclosed in the PDSCH only. This allows these enhancements to be implemented without additional RRC signaling overhead.

In some embodiments, an association of wideband and subband CSI and PDCSCH resource allocation may be implemented. For example, PDSCH may support two resource allocation types, e.g., Type <NUM> and Type <NUM>. For Type <NUM>, if interleaving is configured, this may indicate to the UE <NUM> that wideband CSI feedback is to be performed. For Type <NUM>, if interleaving is not used, this may indicate to the UE <NUM> that PDSCH allocation is to be quantized according to the CSI subband size and subband CSI feedback is to be performed. When Type <NUM> is configured, this may indicate to the UE <NUM> that wideband feedback is to be performed. Thus, the PDSCH resource allocation type may indicate to the UE <NUM> how the CSI feedback is to be reported.

<FIG> shows an example <NUM> of the relationship between PDSCH allocation, CSI measurement and CSI reporting according to carious exemplary embodiments. In the example <NUM>, the NZP CSI-RS and CSI-IM are limited to PRBs with PDSCH allocation. Thus, the NZP CSI-RS and the CSI-IM may be conditioned to the PDSCH. However, the exemplary embodiments are not limited to this arrangement. In other embodiments, the NZP CSI-RS and CSI-IM may be found outside the PRBs with PDSCH allocation.

The example <NUM> shows two alternatives for CSI reporting. In alternative one, the reporting subbands may be the CSI subbands that completely overlap PRBs with PDCSH allocation. In alternative two, the reporting subbands may be any CSI subband that overlaps PRBs with PDSCH allocation. In some embodiments, extension to PRB n may be implemented for SCI subband-<NUM>.

Since the CSI timing may be configured to align with the traffic periodicity, in some embodiments, the hybrid automatic repeat request (HARQ) feedback timing may also be aligned with the traffic periodicity. Accordingly, periodic CSI feedback, semi-persistent CSI feedback or the exemplary CSI feedback triggered by DL SPS activation may be transmitted to the gNB 120A together with the HARQ feedback. This allows the UL transmission time duration to be minimized because instead of two separate PUCCH transmissions, one for CSI feedback and one for HARQ feedback, both CSI feedback and HARQ with their periodicity matched to the DL traffic can be sent in the same PUCCH. Thus, the CSI feedback may be multiplexed with the HARQ feedback on a PUCCH transmission that is matched to the periodicity of the DL traffic.

In addition, sounding reference signals (SRS) may be configured with a non-integer periodicity and offset. Those skilled in the art will understand that SRS generally refers to an uplink reference signal that may be used by a base station (e.g., gNB 120A) to estimate channel quality. SRS may be configured in a periodic or a semi-persistent manner. Further SRS for positioning may also be configured. The exemplary embodiments apply to periodic SRS, semi-persistent SRS or any other appropriate type of SRS.

The exemplary embodiments introduce a periodicity and offset for SRS transmission that is configured to match the periodicity of XR traffic. In some embodiments, the periodicity and offset for SRS may be matched with downlink traffic arrival. This may facilitate coordinated beamforming. In other embodiments, the periodicity and offset may be matched with uplink traffic so one transmission (e.g., SRS appended or prepended to the PUSCH) or two narrowly spaced transmissions of SRS and PUSCH may be supported.

To indicate to the UE <NUM> the non-integer periodicity and offset for the SRS configuration, the base station may transmit SRS configuration information to the UE <NUM> using one or more RRC messages. The SRS configuration information may include an indication of the M1 integer, the M2 integer and an offset integer. <FIG> shows an example of an SRS-PeriodicityandOffset RRC parameter configured to include an indication of the supported non-integer periodicity and offset for SRS.

Alternatively, instead of M1 and M2 integers, the SRS configuration information may include a time parameter indicating a frequency at which SRS is to be transmitted. <FIG> shows an example of SRS-PeriodicityandOffset RRC parameter configured to include an indication of the supported non-integer periodicity and offset for SRS.

In some embodiments, the CSI feedback may be fully or partially based on the PDSCH demodulation reference signal (DMRS). When CSI feedback is based on PDSCH DMRS, the CMR may be provided by the DMRS of the scheduled PDSCH or configured PDSCH (e.g., SPS). The IMR may be provided either by un-used tones in a code division multiplexing (CDM) group of the DMRS or by ZP IMR and/or NZP IMR. The UE <NUM> may calculate channel quality indicator (CQI) according to the CMR and/or IMRs. Further, if PDSCH is at a rank larger than <NUM>, then the UE <NUM> may also recommend rank adaption. For example, if the PDSCH is at rank <NUM>, the UE <NUM> may report a rank indicator (RI) of <NUM>, <NUM> or <NUM> in the feedback.

In another aspect, the exemplary embodiments relate to cDRX for XR. Those skilled in the art will understand that cDRX is a power saving mechanism implemented by the UE <NUM> in RRC connected state. The cDRX cycle may comprise an onDuration during which the UE <NUM> is scheduled to monitor the PDCCH. Outside of the onDuration, the UE <NUM> may have an opportunity to utilize a sleep mode of inactivity and conserve power. Throughout this description, reference to a power saving mode or a sleep mode of inactivity does not necessarily mean putting the processor <NUM>, the transmitter, and the receiver of the UE <NUM> to sleep, in hibernation, or in deactivation. For example, the processor <NUM> (e.g., baseband and/or application) may continue to execute other applications or processes. The sleep mode of inactivity relates to conserving power by discontinuing a continuous processing functionality relating to operations that enable the UE <NUM> to receive data that may be transmitted to the UE <NUM> and transmit data to the network. The exemplary embodiments include enhancements for adapting cDRX to XR traffic which may be generated with a non-integer periodicity.

As indicated above, in NR, there may be DL traffic configured with a non-integer periodicity. For example, in XR, audio and video streams may be generated at cadences which are not integer multiples of NR's default timing. In one configuration of DL traffic with non-integer periodicity, the UE <NUM> may expect SPS transmissions from the network at slot mod(g(k),NSlotPerRadioFrame) where <MAT> and k is a running index. In addition, there may be an initial offset characterized in slots and two integers to derive the periodicity M<NUM> and M<NUM>. In some embodiments, when jitter is expected, SPS configuration may be adjusted with the jitter range. However, the above referenced DL traffic characteristics are merely provided for illustrative purposes. The exemplary embodiments may be applicable to DL traffic configured with non-integer periodicity in any appropriate manner.

In a TDD system, there may be DL slots, UL slots and mixed slots (with both DL and UL symbols) in a radio frame. In some embodiments, a symbol may be a semi-statically configured as a DL symbol (e.g., semi-static DL symbol), semi-statically configured as an UL symbol (e.g., semi-static UL symbol) or semi-statically configured as a flexible symbol. If an occasion for DRX, CSI measurement or SR transmission with a non-integer periodicity configuration is configured to collide with an UL slot or at least one static/semi-statical UL symbol in a slot, then the occasion may be deferred to the next available occasion which does not collide with any semi-static UL symbol. If an occasion for CSI feedback with non-integer periodicity is configured to collide with an UL slot or at least one semi-statical DL symbol in a slot, then the occasion may be deferred to the next available occasion which does not collide with any semi-static DL symbol.

<FIG> shows a signaling diagram <NUM> for implementing a cDRX cycle for DL traffic configured with non-integer periodicity according to various exemplary embodiments.

In <NUM>, the UE <NUM> receives cDRX configuration information. This configuration information may indicate to the UE <NUM> the configuration of a cDRX cycle for DL traffic configured with non-integer periodicity. In <NUM>, the UE <NUM> is camped on the gNB 120A in the RRC connected state and implements the cDRX cycle.

In <NUM>, an onDuration of the cDRX cycle occurs. In <NUM>, during the onDuration, the gNB 120A transmits control information to the UE <NUM> over the PDCCH. This control information may indicate to the UE <NUM> that a subsequent data reception or a subsequent transmission is scheduled.

To define a non-integer cDRX cycle, an additional long DRX value may be added to the DRX-config RRC parameter. For example, the long DRX value may be <NUM>/<NUM> which is equal to <NUM>/<NUM> for <NUM> frames per second. In another example, the long DRX value may be <NUM>/<NUM> which is equal to <NUM>/<NUM> for <NUM> frames per second. However, these values are merely provided for illustrative purposes, any appropriate value may be utilized.

Under conventional circumstances, DRX frames may be calculated using a subframe number (SFN) and a DRX offset value. Here, the conventional DRX cycle may be modified within one SFN periodicity as floor([(SFN × <NUM>) + subframe number] modulo (drxLongCycle)) = drxStartOffset. In some embodiments, this floor function may be rounded or a ceil function may be used. The DRX cycle may be derived based on SFN value where SFN is <NUM> bit with a range of [<NUM>, <NUM>]. Therefore, at SFN wraparound, there may be an issue as show in the below example:.

SFN = <NUM>, <NUM>,<NUM>,<NUM>,<NUM>, using floor function, <MAT> , DRX offset = <NUM>; This results in <MAT> <MAT>.

In one embodiment, the cDRX cycle may be derived using hyper-frame number (HFN) + SFN. This may not entirely eliminate the SFN wraparound issues but may mitigate the severity. The cDRX cycle may be represented as floor([(HFN × <NUM> + SFN × <NUM>) + subframe number] modulo (drxLongCycle)) = drxStartOffset.

In some embodiments, for the SFN and HFN wrap around issue, the gNB 120A may send a MAC CE to indicate the change of drxStartOffset when needed. For instance, within the context of the example provided above where DRX offset = <NUM>, at wrap around, the GNB 120A may instruct the UE <NUM> to switch the drxStartOffset to <NUM>. Alternatively, a MAC CE may be sent in a broadcast or groupcast to multiple UEs since the SFN wrap is cell specific. In another alternative, UE <NUM> and the gNB 120A may be preconfigured with a non-integer DRX cycle adjustment parameter to autonomously adjust the DRX offset following the same rule.

In a different approach, a combination of long DRX and short DRX may be used to match DL traffic periodicity. <FIG> shows an example of using a combination of long DRX and short DRX to match DL traffic periodicity.

The example shown in <FIG> uses <NUM> frames per second as an example (e.g., <NUM>/<NUM> = <NUM>/<NUM>) and thus, the long DRX cycle may be set to <NUM>. The short DRX timer may be set to <NUM>, which indicates that there are <NUM> short DRX cycles within <NUM> long DRX cycle. When the drx inactivity timer expires or a DRX command MAC CE is received by the UE <NUM>, if the short cycle is used, the cycle may be represented by {[SFN × <NUM>) + subframe number]modulo (drxLongCycle)}modulo (drxShortCycle) = (drx StartOffset) modulo (drx Short Cycle).

If the MAC entity is in active time, the UE <NUM> may monitor the PDCCH in the normal manner. If the PDCCH indicates a new transmission (DL or UL), then the drx inactivity timer is to be started or restarted in the first symbol after the end of the PDCCH reception. In case of SPS or configured grant (CG) XR traffic, the drx inactivity timer may start as well in order to start the short DRX cycle. Thus, as shown in <FIG>, the MAC procedure may enable the start of the drx inactivity timer with PDSCH reception and PUSCH transmission.

With a <NUM> long DRX cycle, there may be wrap around issues. The techniques described above may also be applied in this instance to mitigate the wrap around issues. For instance, HFN may be utilized so the time to start the long DRX cycle and the short DRX cycle may be represented by ([(HFN × <NUM> + SFN × <NUM>) + subframe number] modulo (drxLongCycle)) = drxStartOffset and {[HFN × <NUM> + (SFN × <NUM>) + subframe number]modulo (drxLongCycle)}modulo drx ShortCycle = (drxStartOf fset)modulo (drx Short Cycle).

Here, at SFN or HFN wrap around, the drxStartOffset may be shifted. For example, drxStartOffset = <NUM>, drxLongCycle = <NUM>,drxShortCycle = <NUM> at the SFN wrap around, drxStartOffset is changed from <NUM> to <NUM> to equal [<NUM><NUM>].

In another approach, a PDCCH WUS may be used to indicated dynamic traffic. <FIG> shows an example of using PDCCH WUS to indicate dynamic traffic according to various exemplary embodiments.

Under conventional circumstances, if the UE <NUM> detects a PDCCH WUS (e.g., downlink control information (DCI) format <NUM>-<NUM>) and the PDCCH WUS indicated no wakeup, the UE <NUM> may skip the DRX cycle. That is, instead of monitoring the PDCCH during an onDuration, the UE <NUM> may utilize the sleep mode of inactivity. However, in XR, the UE <NUM> may wakeup every DRX cycle when the DRX cycle matches the traffic periodicity.

The exemplary embodiments use the field within the PDCCH WUS to indicate additional information for the SPS PDSCH and CG PUSCH. For example, differential modulation and coding scheme (MCS) compared to SPS can be sent per UE to adapt the modulation/coding rate on top of the SPS configuration. In another example, the PDCCH WUS may be used to indicate an extension to the resource allocation when packets are relatively large for this DRX cycle.

When adapting the PDCCH WUS, if only long DRX is used, the PDCCH WUS may be transmitted before every DRX and either MCS or resource size for SPS and CG can be adopted before the DRX onDuration. In another embodiment, PDCCH WUS may not be transmitted before short DRX. In this example, at least MCS adaption can be used for all DRX onDurations within he long/short DRX cycle. <FIG> shows a gNB configuration to align XR traffic before PDCCH WUS is transmitted.

Those skilled in the art will understand that the above-described exemplary embodiments may be implemented in any suitable software or hardware configuration or combination thereof. An exemplary hardware platform for implementing the exemplary embodiments may include, for example, an Intel x86 based platform with compatible operating system, a Windows OS, a Mac platform and MAC OS, a mobile device having an operating system such as iOS, Android, etc. The exemplary embodiments of the above described method may be embodied as a program containing lines of code stored on a non-transitory computer readable storage medium that, when compiled, may be executed on a processor or microprocessor.

Claim 1:
A processor of a user equipment, UE, configured to perform operations comprising:
receiving channel state information, CSI, configuration information corresponding to downlink new radio, NR, traffic with non-integer periodicity, wherein the CSI configuration information includes one of CSI measurement configuration information, CSI reporting configuration information or CSI measurement configuration information and CSI reporting configuration information;
receiving CSI measurement resources; and
reporting CSI feedback to a network.