Handling new radio (NR) traffic configured with non-integer periodicity

Abstract

The present disclosure relates to handling new radio (NR) traffic configured with non-integer periodicity. A user equipment (UE) is configured to report channel state information (CSI). The UE: receives CSI configuration information corresponding to downlink new radio (NR) traffic with non-integer periodicity, where 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; receives CSI measurement resources; and reports CSI feedback to a network.

Description

[0001] Priority / Incorporation by Reference

[0002] This application claims priority to PCT application PCT / CN2021 / 098692, entitled “Handling New Radio (NR) Traffic Configured with Non-Integer Periodicity,” filed on June 7, 2021, the entire contents of which are incorporated herein by reference. Background Art

[0003] In New Radio (NR) networks, for any of a variety of reasons, there may be traffic generated at a cadence that is not an integer multiple of the time units supported in NR. For example, augmented reality (AR) and virtual reality (VR) applications may have traffic that is not supported by any NR time unit. In NR, the existing solution to this type of timing problem is to over-provision resources. However, this is an inefficient use of network resources and can cause user equipment (UE) to experience power loss. Therefore, there is a need for enhanced management of NR traffic that does not match NR's default timing. Summary of the Invention

[0004] Some example embodiments relate to a processor of a user equipment (UE) configured to perform operations including: receiving channel state information (CSI) configuration information corresponding to downlink New Radio (NR) traffic with a non-integer periodicity, wherein the CSI configuration information includes CSI measurement configuration information, CSI reporting configuration information, or one of CSI measurement configuration information and CSI reporting configuration information; receiving CSI measurement resources; and reporting CSI feedback to a network.

[0005] Other exemplary embodiments relate to a processor of a base station configured to perform operations including: transmitting channel state information (CSI) configuration information corresponding to downlink New Radio (NR) traffic with a non-integer period to a user equipment (UE), wherein the CSI configuration information includes one or more of CSI measurement configuration information and CSI reporting configuration information; transmitting CSI measurement resources; and receiving CSI feedback from the UE.

[0006] Still further exemplary embodiments relate to a processor of a user equipment (UE) configured to perform operations including: receiving connected discontinuous reception (cDRX) configuration information for downlink New Radio (NR) traffic with a non-integer period; implementing a cDRX cycle based on the configuration information; and receiving a physical downlink control channel (PDCCH) during an on-duration of the cDRX cycle.

[0007] Additional example embodiments relate to a processor of a base station configured to perform operations including: transmitting connected discontinuous reception (cDRX) configuration information for downlink New Radio (NR) traffic with a non-integer period to a user equipment (UE); and transmitting a physical downlink control channel (PDCCH) during an on-duration of a cDRX cycle implemented by the UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 Exemplary network arrangements are shown according to various exemplary embodiments.

[0009] Figure 2 An exemplary user equipment (UE) is shown in accordance with various exemplary embodiments.

[0010] Figure 3 An exemplary base station is shown in accordance with various exemplary embodiments.

[0011] Figure 4 A signaling diagram of channel state information (CSI) feedback for extended reality (XR) is shown according to various exemplary embodiments.

[0012] Figure 5 An example of CSI reporting every two downlink (DL) semi-persistent scheduling (SPS) reception opportunities is shown.

[0013] Figure 6 An example of CSI measurement resources configured as multiples of the DL SPS period is shown.

[0014] Figure 7 An exemplary CSI-ReportPeriodicityAndOffset radio resource control (RRC) parameter configured to include an indication of supported non-integer periodicity and offset is shown.

[0015] Figure 8 An exemplary CSI-resourceperiodityandoffset RRC parameter configured to include an indication of supported non-integer periods and offsets for periodic and semi-persistent non-zero power (NZP) CSI-RS is shown.

[0016] Figure 9 An exemplary CSI-resourceperiodityandoffset RRC parameter configured to include an indication of supported non-integer periods and offsets for periodic and semi-persistent CSI-IM is shown.

[0017] Figure 10Examples of the relationship between physical downlink shared channel (PDSCH) allocation, CSI measurement, and CSI reporting according to various exemplary embodiments are shown.

[0018] Figure 11 A signaling diagram for implementing a connected discontinuous reception (cDRX) cycle for DL ​​traffic configured with a non-integer periodicity is shown according to various exemplary embodiments.

[0019] Figure 12 An example of using a combination of long DRX and short DRX to match the DL traffic cycle is shown.

[0020] Figure 13 An example of using a physical downlink control channel (PDCCH) wake-up signal (WUS) to indicate dynamic traffic according to various exemplary embodiments is shown.

[0021] Figure 14 Examples of an SRS-PeriodicityandOffset RRC parameter configured to include an indication of supported non-integer periodicity and offsets for a sounding reference signal (SRS) are shown, according to various exemplary embodiments.

[0022] Figure 15 Examples of an SRS-PeriodicityandOffset RRC parameter configured to include an indication of supported non-integer periodicity and offset for SRS are shown according to various exemplary embodiments. DETAILED DESCRIPTION

[0023] The exemplary embodiments may be further understood with reference to the following description and associated drawings, in which similar elements have the same reference numerals. The exemplary embodiments introduce techniques for handling traffic that may not match an integer multiple of a time unit 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 a cadence (e.g., a non-integer period) that is not an integer multiple of a NR time unit. On the other hand, the exemplary embodiments relate to connected discontinuous reception (cDRX). As will be described in more detail below, some of the exemplary techniques described herein may enable a UE to implement cDRX for NR traffic that is generated at a cadence that is not an integer multiple of NR's default timing.

[0024] The exemplary embodiments are described with respect to extended reality (XR). Those skilled in the art will understand that XR is an umbrella term for different types of reality and may generally refer to a combined real and virtual environment and associated human-computer interactions generated through computer technology and wearable devices. To provide some examples, the term XR may encompass augmented reality (AR), mixed reality (MR), and virtual reality (VR). However, any reference to XR that is specific to a particular traffic use case or type is provided for illustrative purposes only. The exemplary embodiments are applicable to any type of NR traffic that may be generated at a cadence that is not an integer multiple of the default timing of NR.

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

[0026] In addition, the exemplary embodiments are described with respect to UE. Those skilled in the art will understand that UE can be any type of electronic component configured to communicate via a network, for example, a mobile phone, a tablet computer, a desktop computer, a smart phone, a tablet phone, an embedded device, a wearable device, an Internet of Things (IoT) device, etc. With respect to XR, in some configurations, the UE can be paired with a wearable device (e.g., a head-mounted display (HMD), AR glasses, etc.). In this type of configuration, the UE can communicate directly with the network and then relay the data to a wearable device (e.g., AR, VR, MR, etc.) that presents the XR content to the user. In other configurations, the UE can 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 communicates directly with the network.

[0027] Although the exemplary embodiments are described with respect to providing enhancements for XR services, the exemplary embodiments are not limited to XR services and are applicable to any type of NR traffic configured with a non-integer period. To provide another example, in the Industrial Internet of Things (IIoT), traffic may be generated from installed systems with long service lives. In this type of scenario, it is difficult to modify the traffic generation period to match any of NR's time units. 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.

[0028] In one aspect, exemplary embodiments introduce CSI feedback enhancements for XR. As will be described in more detail below, CSI feedback enhancements including measurements and / or reporting that match traffic arrivals are introduced to improve UE power savings and performance with respect to XR (or any other type of traffic that may not match the existing timing of NR). In addition, exemplary enhancements are introduced that implement periodic (P) and semi-persistent (SP) CSI measurements and reporting that match the application traffic period and offset. In addition, CSI feedback measurements and / or reporting that match 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 specific implementations of CSI feedback techniques, or used independently of other CSI feedback techniques.

[0029] In another aspect, 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 periods for cDRX configurations, use of a combination of long and short DRX to match traffic periods, and use of 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 of other cDRX mechanisms.

[0030] Figure 1 An exemplary network arrangement 100 according to various exemplary embodiments is shown. The exemplary network arrangement 100 includes a UE 110. Those skilled in the art will appreciate that the UE 110 can be any type of electronic component configured to communicate via a network, such as a mobile phone, tablet computer, desktop computer, smartphone, phablet, embedded device, wearable device (e.g., HMD, AR glasses, etc.), Internet of Things (IoT) device, etc. It should also be understood that an actual network arrangement can include any number of UEs used by any number of users. Therefore, for illustrative purposes, only an example with a single UE 110 is provided.

[0031] UE 110 can be configured to communicate with one or more networks. In the example of network configuration 100, the network with which UE 110 can wirelessly communicate is a 5G NR radio access network (RAN) 120. However, UE 110 can also communicate with other types of networks (e.g., 5G cloud RAN, next generation RAN (NG-RAN), long term evolution (LTE) RAN, traditional cellular networks, WLAN, etc.), and UE 110 can also communicate with a network via a wired connection. With respect to the exemplary embodiment, UE 110 can establish a connection with 5G NR RAN 120. Therefore, UE 110 can have a 5G NR chipset to communicate with NR RAN 120.

[0032] The 5G NR RAN 120 may be part of a cellular network that may be deployed by a network operator, such as Verizon, AT&T, T-Mobile, etc. The 5G NR RAN 120 may include, for example, cells or base stations (Node B, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to send and receive communication traffic from UEs equipped with appropriate cellular chipsets.

[0033] UE 110 may connect to 5G NR-RAN 120 via gNB 120A. Those skilled in the art will appreciate that any relevant procedures may be performed for UE 110 to connect to 5G NR-RAN 120. For example, as described above, 5G NR-RAN 120 may be associated with a particular cellular provider, where UE 110 and / or its user has protocol and credential information (e.g., stored on a SIM card). Upon detecting the presence of 5G NR-RAN 120, UE 110 may transmit corresponding credential information to associate with 5G NR-RAN 120. More specifically, UE 110 may associate with a particular base station (e.g., gNB 120A). However, as described above, reference to 5G NR-RAN 120 is for illustrative purposes only, and any suitable type of RAN may be used.

[0034] Network arrangement 100 also includes a cellular core network 130, the Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network services backbone 160. Cellular core network 130 can be considered an interconnected collection of components that manage the operation and traffic of a cellular network. Cellular core network 130 also manages traffic flowing between the cellular network and the Internet 140. IMS 150 can generally be described as an architecture for delivering multimedia services to UE 110 using IP protocols. IMS 150 can communicate with cellular core network 130 and the Internet 140 to provide multimedia services to UE 110. Network services backbone 160 communicates directly or indirectly with the Internet 140 and cellular core network 130. Network services backbone 160 can generally be described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a set of services that can be used to extend the functionality of UE 110 to communicate with various networks.

[0035] Figure 2 An exemplary UE 110 is shown according to various exemplary embodiments. Figure 1 100 is used to describe the UE 110. The UE 110 may include a processor 205, a memory arrangement 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, and other components 230. The other components 230 may include, for example, an audio input device, an audio output device, a power source, a data acquisition device, a port for electrically connecting the UE 110 to other electronic devices, and the like.

[0036] The processor 205 may be configured to execute multiple engines of the UE 110. For example, the engines may include a CSI feedback for XR engine 235 and a cDRX for XR engine 240. The CSI feedback for XR engine 235 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 240 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 a PDCCH.

[0037] The engines 235, 240 described above are each provided as an application (e.g., a program) executed by the processor 205 for illustrative purposes only. The functionality associated with the engines 235, 240 may also be represented as a separate integrated component of the UE 110, or may be a modular component coupled to the UE 110, such as an integrated circuit with or without firmware. For example, an integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. The engines may also be embodied as one application or multiple separate applications. In addition, in some UEs, the functionality described for the processor 205 is shared between two or more processors, such as a baseband processor and an application processor. The exemplary embodiments may be implemented in any of these or other configurations of the UE.

[0038] The memory arrangement 210 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 215 may be a hardware component configured to display data to a user, while the I / O device 220 may be a hardware component that enables user input. The display device 215 and the I / O device 220 may be separate components or may be integrated together (such as a touch screen). The transceiver 225 may be a hardware component configured to establish a connection with the 5G NR-RAN 120 and / or any other suitable type of network. Thus, the transceiver 225 may operate on a variety of different frequencies or channels (e.g., a contiguous group of frequencies).

[0039] Figure 3 An exemplary base station 300 is shown in accordance with various exemplary embodiments. Base station 300 may represent any access node (e.g., gNB 120A, etc.) that UE 110 may use to establish a connection and manage network operations.

[0040] Base station 300 may include a processor 305, a memory arrangement 310, input / output (I / O) devices 315, a transceiver 320, and other components 325. Other components 325 may include, for example, a battery, data acquisition devices, ports for electrically connecting base station 300 to other electronic devices, and the like.

[0041] The processor 305 may be configured to execute multiple engines of the base station 300. For example, the engines may include a CSI for XR engine 330 and a cDRX configuration for XR engine 335. The CSI for XR engine 330 may perform various operations related to the exemplary CSI feedback enhancements described herein. These operations may include, but are not limited to, transmitting CSI feedback configuration information, transmitting CSI resources, and receiving CSI feedback. The cDRX configuration for XR engine 335 may perform various operations related to the exemplary cDRX enhancements described herein. These operations may include, but are not limited to, transmitting cDRX configuration information and transmitting a PDCCH according to the cDRX configuration.

[0042] The engines 330 and 335 described above as applications (e.g., programs) executed by the processor 305 are merely exemplary. The functionality associated with the engines 330 and 335 may also be represented as separate, integrated components of the base station 300, or may be modular components coupled to the base station 300, such as integrated circuits with or without firmware. For example, an integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. Furthermore, in some base stations, the functionality described for the processor 305 is split between multiple processors (e.g., a baseband processor, an application processor, etc.). The exemplary embodiments may be implemented in any of these or other configurations of the base station.

[0043] The memory 310 may be a hardware component configured to store data related to operations performed by the base station 300. The I / O device 315 may be a hardware component or port that enables a user to interact with the base station 300. The transceiver 320 may be a hardware component configured to exchange data with the UE 110 and any other UE in the system 100. The transceiver 320 may operate on a variety of different frequencies or channels (e.g., a set of continuous frequencies). Therefore, the transceiver 320 may include one or more components (e.g., radio components) to enable data exchange with various networks and UEs.

[0044] As described above, in one aspect, exemplary embodiments introduce CSI feedback enhancements for XR. Figure 4 A signaling diagram 400 for CSI feedback for XR is shown according to various exemplary embodiments. Figure 1 The network arrangement 100 and Figure 2 The signaling diagram 400 is described with reference to the UE 110 of FIG.

[0045] Signaling diagram 400 includes UE 110 and gNB 120A. At 405, UE 110 receives CSI measurement and / or reporting configuration information. In some embodiments, the CSI measurement and / or reporting configuration information may be provided to UE 110 in one or more radio resource control (RRC) messages. In other embodiments, the CSI measurement and / or reporting configuration information may be provided to UE 110 in one or more access control (MAC) control elements (CEs). However, example embodiments are not limited to RRC messages or MAC CEs, and the CSI measurement and reporting configuration information may be provided to UE 110 in any suitable manner.

[0046] Various CSI feedback enhancements for XR are described in detail below. Subsequently, an example of how the network can provide corresponding CSI measurement and reporting configuration information to UE 110 will be provided.

[0047] At 410, gNB 120A configures CSI measurement resources for UE 110. The CSI resources may include channel measurement resources (CMRs) and interference measurement resources (IMRs). CMRs may include one or more non-zero power (NZP) CSI reference signals (RSs). In NR, periodic and semi-persistent CMRs are supported. The period and offset of these CMR resources may be characterized by time slots or in any other suitable manner. Throughout this specification, any reference to a specific type of CMR is provided for illustrative purposes only, and the exemplary embodiments are applicable to any suitable type of CMR.

[0048] IMR may include one or more zero-power (ZP)-CSI-RS, NZP-CSI-RS, or a combination thereof. Throughout this specification, the terms "ZP IMR" and "CSI-IM" may be used interchangeably to identify the same type of CSI resource, 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 period and offset of these IMRs may be characterized in time slots or in any other appropriate manner. Throughout this specification, any reference to a specific type of IMR is provided for illustrative purposes only, and the exemplary embodiments are applicable to any appropriate type of IMR.

[0049] At 415, UE 110 performs CSI measurement based on the CSI measurement resource. At 420, UE 110 reports CSI feedback to gNB 120A.

[0050] For XR services, streams may be generated at a cadence that is not an integer multiple of NR time units. To provide an example, XR video stream generation may occur at 60 or 120 frames per second. The exemplary embodiments introduce CSI measurement and reporting techniques to handle these types of timing issues in an efficient manner.

[0051] In some embodiments, the exemplary enhancements may be applied only to IMR. For example, periodic / semi-persistent CMR may be generated with a period of X milliseconds (ms), where X represents an integer value (e.g., 1, 2, 5, 10, etc.), while periodic / semi-persistent IMR may be generated with a period of Y ms, where Y represents a non-integer value (e.g., 25 / 3, 10 / 3, etc.). In another embodiment, the exemplary enhancements may be applied only to CMR. In another embodiment, the exemplary enhancements may be applied to both CMR and IMR.

[0052] In one example, the periodicity of CSI reporting may be the same as the DL SPS periodicity or a multiple of the DL periodicity.The periodicity of CSI reporting may be non-integer. Figure 5 An example of CSI reporting every two DL SPS reception opportunities is shown.

[0053] The period of the CSI measurement resource may also be non-integer and based on a multiple of the DL SPS period or the DL period. For example, the CSI measurement resource period may be represented by (M1 / M2), where M1 and M2 each represent an integer value. Figure 6 An example of CSI measurement resources configured as multiples of the DL SPS period is shown.

[0054] To enable periodic and semi-persistent CSI reporting with non-integer periodicity and offset, the CSI report and / or measurement configuration information may include an indication of an M1 integer, an M2 integer, and an offset integer. Figure 7 An exemplary CSI-ReportPeriodicityAndOffset RRC parameter configured to include an indication of supported non-integer periodicity and offset is shown.

[0055] To indicate to UE 110 the non-integer period and offset for CMR configuration, the CSI reporting and measurement configuration information may include an indication of an M1 integer, an M2 integer, and an offset integer. Figure 8 Exemplary CSI RRC parameters configured to include an indication of supported non-integer periods and offsets for periodic and semi-persistent NZP CSI-RS are shown.

[0056] To indicate to UE 110 the non-integer period and offset for IMR configuration, the CSI reporting and measurement configuration information may include an indication of an M1 integer, an M2 integer, and an offset integer. Figure 9An exemplary CSI-resourceperiodityandoffset RRC parameter configured to include an indication of supported non-integer periods and offsets for periodic and semi-persistent CSI-IM is shown.

[0057] 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 110 may receive the DL SPS configuration information and then determine the CSI measurement and reporting configuration based on the pre-configured association. In another example, the DL SPS configuration is associated with the CSI measurement and reporting configuration. Thus, in this example, the UE 110 may receive the CSI measurement and reporting configuration information and then determine the DL SPS configuration based on the pre-configured association. In another example, an information element (IE) may be introduced that indicates to the UE 110 the relationship between the DL SPS configuration and the CSI measurement and reporting configuration.

[0058] For example enhancements to 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 based on the DL SPS PDSCH frequency allocation. Instead, UE 110 can adapt the CSI measurement operation to the DL SPS PDSCH configuration. This allows these enhancements to be implemented without incurring additional RRC signaling overhead.

[0059] Furthermore, in some embodiments, the CSI-ReportingBand RRC parameter is not explicitly configured based on the DL SPS PDSCH frequency allocation. Instead, UE 110 can adapt the CSI reporting operation to the DL SPS PDSCH configuration. For example, if the PDSCH is from physical resource block (PRB) 10 to PRB 19, CSI measurements are assumed only for the CSI subband or subbands encapsulated in the PDSCH. This allows these enhancements to be implemented without requiring additional RRC signaling overhead.

[0060] In some embodiments, association of wideband and subband CSI with PDCSCH resource allocation can be implemented. For example, PDSCH can support two resource allocation types (e.g., Type 0 and Type 1). For Type 1, if staggering is configured, this can indicate to UE 110 that wideband CSI feedback will be performed. For Type 1, if staggering is not used, this can indicate to UE 110 that PDSCH allocations will be quantized according to the CSI subband size and that subband CSI feedback will be performed. When Type 0 is configured, this can indicate to UE 110 that wideband feedback will be performed. Therefore, the PDSCH resource allocation type can indicate to UE 110 how CSI feedback will be reported.

[0061] Figure 10 Example 1000 illustrates the relationship between PDSCH allocation, CSI measurement, and CSI reporting according to various exemplary embodiments. In example 1000, NZP CSI-RS and CSI-IM are confined to PRBs with PDSCH allocations. Thus, NZP CSI-RS and CSI-IM may be subject to PDSCH constraints. However, exemplary embodiments are not limited to this arrangement. In other embodiments, NZP CSI-RS and CSI-IM may be located outside of PRBs with PDSCH allocations.

[0062] Example 1000 illustrates two alternatives for CSI reporting. In alternative one, the reporting subband can be a CSI subband that completely overlaps with a PRB with a PDSCH allocation. In alternative two, the reporting subband can be any CSI subband that overlaps with a PRB with a PDSCH allocation. In some embodiments, extension to PRB n can be implemented for SCI subband-2.

[0063] Because CSI timing can be configured to align with traffic periods, in some embodiments, hybrid automatic repeat request (HARQ) feedback timing can also be aligned with traffic periods. Thus, periodic CSI feedback, semi-persistent CSI feedback, or exemplary CSI feedback triggered by DL SPS activation can be transmitted to gNB 120A along with HARQ feedback. This allows UL transmit 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 feedback, whose periodicity matches the DL traffic, can be sent in the same PUCCH. Thus, CSI feedback can be multiplexed with HARQ feedback on a PUCCH transmission that matches the period of DL traffic.

[0064] Furthermore, a sounding reference signal (SRS) can be configured with a non-integer period and offset. Those skilled in the art will appreciate that an SRS generally refers to an uplink reference signal that can be used by a base station (e.g., gNB 120A) to estimate channel quality. An SRS can be configured in a periodic or semi-persistent manner. Furthermore, an SRS for positioning can also be configured. The exemplary embodiments are applicable to periodic SRS, semi-persistent SRS, or any other suitable type of SRS.

[0065] Example embodiments introduce a period and offset for SRS transmissions configured to match the period of XR traffic. In some embodiments, the period and offset for SRS can be matched to downlink traffic arrival. This can facilitate coordinated beamforming. In other embodiments, the period and offset can be matched to uplink traffic, thereby supporting either SRS or PUSCH transmissions (e.g., SRS appended to or pre-pended to PUSCH) or two narrowly spaced transmissions.

[0066] To indicate the non-integer period and offset for SRS configuration to UE 110, the base station may use one or more RRC messages to transmit SRS configuration information to UE 110. The SRS configuration information may include an indication of an M1 integer, an M2 integer, and an offset integer. Figure 14 An example of an SRS-PeriodicityandOffset RRC parameter configured to include an indication of supported non-integer periodicity and offset for SRS is shown.

[0067] Alternatively, instead of the M1 integer and the M2 integer, the SRS configuration information may include a time parameter indicating a frequency at which the SRS is to be transmitted. Figure 15 An example of an SRS-PeriodicityandOffset RRC parameter configured to include an indication of supported non-integer periodicity and offset for SRS is shown.

[0068] In some embodiments, CSI feedback may be based entirely or partially on a PDSCH demodulation reference signal (DMRS). When CSI feedback is based on a PDSCH DMRS, a CMR may be provided by the DMRS of a scheduled PDSCH or a configured PDSCH (e.g., SPS). An IMR may be provided by unused tones in a code division multiplexing (CDM) group of the DMRS or by ZP IMR and / or NZP IMR. The UE 110 may calculate a channel quality indicator (CQI) based on the CMR and / or IMR. In addition, if the PDSCH is at a rank greater than 1, the UE 110 may also recommend rank adaptation. For example, if the PDSCH is at rank 3, the UE 110 may report a rank indicator (RI) of 1, 2, or 3 in the feedback.

[0069] On the other hand, exemplary embodiments relate to cDRX for XR. Those skilled in the art will appreciate that cDRX is a power saving mechanism implemented by a UE 110 in an RRC connected state. The cDRX cycle may include an on-duration during which the UE 110 is scheduled to monitor the PDCCH. Outside of the on-duration, the UE 110 may have the opportunity to utilize an inactive sleep mode and save power. Throughout this specification, references to a power saving mode or an inactive sleep mode do not necessarily mean that the processor 205, transmitter, and receiver of the UE 110 are put to sleep, dormant, or disabled. For example, the processor 205 (e.g., baseband and / or application) may continue to execute other applications or processes. The inactive sleep mode involves saving power by interrupting continuous processing functions related to operations that enable the UE 110 to receive data that may be transmitted to the UE 110 and transmit data to the network. Exemplary embodiments include enhancements for adapting cDRX to XR traffic that may be generated in non-integer periods.

[0070] As indicated above, in NR, there may be DL traffic configured with non-integer periodicity. For example, in XR, audio and video streams may be generated at a cadence that is not an integer multiple of the default timing of NR. In one configuration with DL traffic with non-integer periodicity, UE 110 may generate DL traffic in time slots mod(g(k),N SlotPerRadioFrame ) where SPS transmissions from the network are expected and k is a running index. Furthermore, there may be two integers, M1 and M2, representing an initial offset and a derived period in time slots. In some embodiments, when jitter is expected, the SPS configuration may be adjusted using a jitter range. However, the above DL traffic characteristics are provided for illustrative purposes only. The exemplary embodiments are applicable to DL traffic configured with non-integer periods in any suitable manner.

[0071] In a TDD system, a radio frame may include DL slots, UL slots, and mixed slots (having both DL and UL symbols). In some embodiments, symbols may be semi-statically configured as DL symbols (e.g., semi-static DL symbols), semi-statically configured as UL symbols (e.g., semi-static UL symbols), or semi-statically configured as variable symbols. If a timing for DRX, CSI measurement, or SR transmission with a non-integer period configuration is configured to conflict with a UL slot or at least one static / semi-static UL symbol in a slot, the timing may be postponed to the next available timing that does not conflict with any semi-static UL symbol. If a timing for CSI feedback with a non-integer period configuration is configured to conflict with a UL slot or at least one semi-static DL symbol in a slot, the timing may be postponed to the next available timing that does not conflict with any semi-static DL symbol.

[0072] Figure 11 A signaling diagram 1100 is shown for implementing a cDRX cycle for DL ​​traffic configured with a non-integer periodicity according to various exemplary embodiments.

[0073] In 1105, UE 110 receives cDRX configuration information. The configuration information may indicate to UE 110 the configuration of a cDRX cycle for DL ​​traffic with a non-integer period. In 1110, UE 110 camps on gNB 120A in an RRC connected state and implements the cDRX cycle.

[0074] At 1115, the OnDuration of the cDRX cycle occurs. At 1120, during the OnDuration, gNB 120A transmits control information on the PDCCH to UE 110. The control information may indicate to UE 110 that a subsequent data reception or a subsequent transmission is scheduled.

[0075] To define a non-integer cDRX cycle, an additional long DRX value can be added to the DRX-config RRC parameter. For example, for 60 frames per second, the long DRX value can be 1000 / 60, which is equal to 50 / 3. In another example, for 45 frames per second, the long DRX value can be 1000 / 45, which is equal to 200 / 9. However, these values ​​are provided for illustrative purposes only, and any suitable values ​​may be utilized.

[0076] Under normal circumstances, a DRX frame can be calculated using a subframe number (SFN) and a DRX offset value. Here, the normal DRX cycle can be modified within one SFN cycle as floor([(SFN×10)+subframe number]modulo(drxLongCycle))=drxStartOffset. In some embodiments, this floor function can be rounded or a ceiling function can be used. The DRX cycle can be derived based on the SFN value, where the SFN is a 10-bit value in the range [0,1023]. Therefore, when the SFN wraps around, there may be problems as shown in the following example:

[0077] SFN=1022、1023、0、1、2,use floor function, DRX offset = 0; this results in

[0078] In one embodiment, the cDRX cycle can be derived using the hyperframe number (HFN) + SFN. This may not completely eliminate the SFN wraparound problem, but it may reduce its severity. The cDRX cycle can be expressed as

[0079] floor([(HFN×10240+SFN×10)+subframe number]modulo(drxLongCycle))=drxStartOffset.

[0080] In some embodiments, for SFN and HFN wraparound issues, gNB 120A may send a MAC CE to indicate a change in drxStartOffset when needed. For example, in the context of the example provided above, where DRX Offset = 0, GNB 120A may instruct UE 110 to switch drxStartOffset to 11 when wraparound occurs. Alternatively, the MAC CE may be sent to multiple UEs in a broadcast or multicast, as SFN wraparound is cell-specific. In another alternative, UE 110 and gNB 120A may be preconfigured with non-integer DRX cycle adjustment parameters to autonomously adjust DRX Offset following the same rules.

[0081] In a different approach, a combination of long DRX and short DRX can be used to match the DL traffic cycle. Figure 12 An example of using a combination of long DRX and short DRX to match the DL traffic cycle is shown.

[0082] Figure 12 The example shown uses 60 frames per second as an example (e.g., 1000 / 60=50 / 3), and therefore the long DRX cycle can be set to 50. The short DRX timer can be set to 2, indicating that there are 2 short DRX cycles within 1 long DRX cycle. When the drx inactivity timer expires or the UE 110 receives a DRX command MAC CE, if a short cycle is used, the cycle can be represented by: {[SFN×10)+subframe number] modulo(drxLongCycle)}modulo(drxShortCycle)=((drxStartOffset)modulo(drxShortCycle).

[0083] If the MAC entity is in active time, the UE 110 can monitor the PDCCH in a normal manner. If the PDCCH indicates a new transmission (DL or UL), the DRX Inactivity Timer will be started or restarted in the first symbol after the end of PDCCH reception. In the case of SPS or Configuration Grant (CG) XR traffic, the DRX Inactivity Timer may also be started to start a short DRX cycle. Therefore, if Figure 12 As shown, the MAC procedure may be able to start the drx-inactivity timer with PDSCH reception and PUSCH transmission.

[0084] With a long DRX cycle of 50ms, there may be wraparound issues. In this case, the above-mentioned techniques can also be applied to mitigate wraparound issues. For example, HFN can be used, so the time to start the long DRX cycle and the short DRX cycle can be expressed as follows: ([(HFN×10240+SFN×10)+subframe number]modulo(drxLongCycle))=drxStartOffset and {[HFN×10240+(SFN×10)+subframe number]modulo(drxLongCycle)}modulo drxShortCycle=(drxStartOffset)modulo(drxShortCycle).

[0085] Here, when SFN or HFN wraps around, drxStartOffset may be shifted. For example, when SFN wraps around, drxStartOffset=0, drxLongCycle=50, drxShortCycle=17, drxStartOffset changes from 0 to 11 to equal [[3 4 5 6 7 8 9 10 11 12 13 14 15 16 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 910 11 12 13 14 15 16 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 0 1 2 3 4 5 6 7 8 9]

[0086] In another method, PDCCH WUS can be used to indicate dynamic traffic. Figure 13 An example of using the PDCCH WUS to indicate dynamic traffic according to various exemplary embodiments is shown.

[0087] Under normal circumstances, if UE 110 detects a PDCCH WUS (e.g., downlink control information (DCI) formats 2-6) and the PDCCH WUS indicates no wake-up, UE 110 may skip the DRX cycle. That is, instead of monitoring the PDCCH during the on-duration, UE 110 may utilize an inactive sleep mode. However, in XR, when the DRX cycle matches the traffic period, UE 110 may wake up every DRX cycle.

[0088] An exemplary embodiment uses fields within the PDCCH WUS to indicate additional information for the SPS PDSCH and CG PUSCH. For example, a differential modulation and coding scheme (MCS) compared to the SPS can be sent per UE to accommodate the modulation / coding rate on top of the SPS configuration. In another example, the PDCCH WUS can be used to indicate an extension of the resource allocation when the packet is relatively large for the DRX cycle.

[0089] When adapting to PDCCH WUS, if only long DRX is used, the PDCCH WUS may be transmitted before each DRX, and the MCS or resource size used for SPS and CG may be adopted before the DRX On Duration. In another embodiment, the PDCCH WUS may not be transmitted before short DRX. In this example, at least MCS adaptation is applicable to all DRX On Durations within the long / short DRX cycle. Figure 13 Shown is the gNB configuration for aligning XR traffic before transmitting PDCCH WUS.

[0090] Example

[0091] In a first embodiment, a user equipment (UE) includes: a transceiver configured to communicate with a network; and a processor communicatively coupled to the transceiver and configured to perform operations including: receiving channel state information (CSI) configuration information corresponding to downlink New Radio (NR) traffic with a non-integer periodicity, wherein the CSI configuration information includes CSI measurement configuration information, CSI reporting configuration information, or one of CSI measurement configuration information and CSI reporting configuration information; receiving CSI measurement resources; and reporting CSI feedback to the network.

[0092] In a second embodiment, a base station includes: a transceiver configured to communicate with a user equipment (UE); and a processor communicatively coupled to the transceiver and configured to perform operations including: transmitting channel state information (CSI) configuration information corresponding to downlink New Radio (NR) traffic with a non-integer period to the user equipment (UE), wherein the CSI configuration information includes one or more of CSI measurement configuration information and CSI reporting configuration information; transmitting CSI measurement resources; and receiving CSI feedback from the UE.

[0093] In a third embodiment, a user equipment (UE) includes: a transceiver configured to communicate with a network; and a processor communicatively coupled to the transceiver and configured to perform operations including: receiving connected discontinuous reception (cDRX) configuration information for downlink New Radio (NR) traffic with a non-integer period; implementing a cDRX cycle based on the configuration information; and receiving a physical downlink control channel (PDCCH) during an on-duration of the cDRX cycle.

[0094] In a fourth embodiment, a base station includes: a transceiver configured to communicate with a user equipment (UE); and a transceiver communicatively coupled to the transceiver and configured to perform operations including: transmitting connected discontinuous reception (cDRX) configuration information for downlink New Radio (NR) traffic with a non-integer period to the user equipment (UE); and transmitting a physical downlink control channel (PDCCH) during an on-duration of a cDRX cycle implemented by the UE.

[0095] In a fifth embodiment, a processor of a user equipment (UE) is configured to perform operations including: receiving sounding reference signal (SRS) configuration information corresponding to new radio (NR) traffic with a non-integer period; and transmitting the SRS to a base station of a network.

[0096] In a sixth embodiment, according to the processor of the fifth embodiment, a period of the SRS is a non-integer period configured based on downlink traffic.

[0097] In a seventh embodiment, the processor according to the fifth embodiment, wherein the period of the SRS is a non-integer period configured based on uplink traffic.

[0098] In an eighth embodiment, the processor according to the seventh embodiment, wherein the SRS is attached or pre-set to a physical uplink shared channel (PUSCH).

[0099] In a ninth embodiment, the processor according to the eighth embodiment, wherein the PUSCH is a configuration grant PUCSH.

[0100] In a tenth embodiment, the processor according to the fifth embodiment, wherein the SRS configuration information is included in an RRC message, and the RRC message includes the first integer, the second integer, and an offset integer.

[0101] In an eleventh embodiment, the processor according to the fifth embodiment, wherein the SRS configuration information is included in an RRC message, the RRC message including a time-based parameter and an offset integer of a frequency at which the SRS is to be transmitted.

[0102] In a twelfth embodiment, a processor of a base station is configured to perform operations including: transmitting connected discontinuous reception (cDRX) configuration information for downlink New Radio (NR) traffic with a non-integer period to a user equipment (UE); and transmitting a physical downlink control channel (PDCCH) during an on-duration of a cDRX cycle implemented by the UE.

[0103] In a thirteenth embodiment, the processor according to the twelfth embodiment, the operations further comprising transmitting a medium access control (MAC) control element (CE) indicating a change in drxStartOffset.

[0104] In a fourteenth embodiment, the processor according to the thirteenth embodiment, wherein the MAC CE is sent in a broadcast or multicast.

[0105] In a fifteenth embodiment, the processor according to the twelfth embodiment, wherein the cDRX cycle comprises a combination of a short DRX cycle and a long DRX cycle.

[0106] In a sixteenth embodiment, according to the processor of the twelfth embodiment, the operations further comprise: transmitting a PDCCH wake-up signal (WUS), wherein the PDCCH WUS includes information for a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH).

[0107] In a seventeenth embodiment, the processor of the sixteenth embodiment, wherein the information includes an indication of a differential modulation and coding scheme (MCS) or an extended resource allocation.

[0108] In an eighteenth embodiment, according to the processor of the twelfth embodiment, the operations further comprise: transmitting a PDCCH wake-up signal (WUS), wherein the PDCCH WUS includes information for a configuration grant (CG) physical uplink shared channel (PUSCH).

[0109] In a nineteenth embodiment, the processor according to the twelfth embodiment, the operations further comprising transmitting a PDCCH wake-up signal (WUS), wherein downlink traffic is aligned before the PDCCH WUS.

[0110] In a twentieth embodiment, a processor of a user equipment (UE) is configured to perform operations including: receiving channel state information (CSI) configuration information corresponding to downlink New Radio (NR) traffic with a non-integer period, wherein the CSI configuration information includes CSI measurement configuration information, CSI reporting configuration information, or one of CSI measurement configuration information and CSI reporting configuration information; receiving CSI measurement resources; and reporting CSI feedback to a network.

[0111] In a twenty-first embodiment, according to the processor of the twentieth embodiment, the operations further include: identifying a type 1 physical downlink shared channel (PDSCH) resource allocation or a type 0 PDSCH resource allocation with staggering; and determining that wideband CSI feedback is to be used based on the identification.

[0112] In a twenty-second embodiment, the processor according to the twentieth embodiment, the operations further comprising: identifying a type 1 physical downlink shared channel (PDSCH) resource allocation without interleaving; and determining that subband CSI feedback is to be used based on the identification.

[0113] In a twenty-third embodiment, the processor according to the twentieth embodiment, wherein the CSI measurement resources are limited to physical resource blocks (PRBs) with physical downlink shared channel (PDSCH) assignments.

[0114] In a twenty-fourth embodiment, the processor according to the twentieth embodiment, wherein reporting the CSI feedback comprises multiplexing the CSI feedback and hybrid automatic repeat request (HARQ) feedback.

[0115] In a twenty-fifth embodiment, the processor according to the twentieth embodiment, wherein the channel measurement resource (CMR) is provided by a demodulation reference signal (DMRS).

[0116] In a twenty-sixth embodiment, the processor of the twentieth embodiment, wherein the interference measurement resource (IMR) is provided by one of an unused tone in a code division multiplexing (CDM) group of a demodulation reference signal (DMRS), a zero power (ZP) IMR, or a non-zero power (NZP) IMR.

[0117] In a twenty-seventh embodiment, a processor of a base station is configured to perform operations including: transmitting channel state information (CSI) configuration information corresponding to downlink New Radio (NR) traffic with a non-integer period to a user equipment (UE), wherein the CSI configuration information includes one or more of CSI measurement configuration information and CSI reporting configuration information; transmitting CSI measurement resources; and receiving CSI feedback from the UE.

[0118] In a twenty-eighth embodiment, the processor according to the twenty-seventh embodiment, wherein the CSI measurement and reporting configuration information is included in a radio resource control (RRC) message, the RRC message including a first integer, a second integer, and an offset integer, and wherein the first integer and the second integer are used by the UE to derive a non-integer CSI reporting period.

[0119] In a twenty-ninth embodiment, the processor according to the twenty-eighth embodiment, wherein the CSI measurement and reporting configuration information is included in a radio resource control (RRC) message, the RRC message includes a first integer, a second integer, and an offset integer, and wherein the first integer and the second integer are used by the UE to derive a non-integer period for a channel measurement resource (CMR).

[0120] In a thirtieth embodiment, the processor according to the twenty-eighth embodiment, wherein the CSI measurement and reporting configuration information is included in a radio resource control (RRC) message, the RRC message includes a first integer, a second integer, and an offset integer, and wherein the first integer and the second integer are used by the UE to derive a non-integer period of an interference measurement resource (IMR).

[0121] In a thirty-first embodiment, according to the processor of the twenty-eighth embodiment, the operations further comprise: transmitting to the UE an information element (IE) indicating a relationship between downlink semi-persistent scheduling (SPS) and CSI measurement and reporting opportunities.

[0122] Those skilled in the art will appreciate that the exemplary embodiments described above may be implemented with any suitable software configuration or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, mobile devices with operating systems such as iOS, Android, etc. The exemplary embodiments of the above methods may be embodied as a program comprising lines of code stored on a non-transitory computer-readable storage medium, which, when compiled, may be executed on a processor or microprocessor.

[0123] Although this patent application describes various combinations of various embodiments, each with different features, those skilled in the art will understand that any feature of one embodiment may be combined with features of other embodiments in any manner not publicly denied, or with features that are not functionally or logically inconsistent with the operation or described function of the device of the embodiments disclosed herein.

[0124] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

[0125] It will be apparent to those skilled in the art that various modifications may be made to the present disclosure without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is intended to cover modifications and variations of the present disclosure provided that these modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. A processor of a user equipment (UE), the processor being configured to perform operations, the operations comprising: Receiving channel state information (CSI) configuration information corresponding to downlink New Radio (NR) traffic with a non-integer periodicity, wherein the CSI configuration information includes CSI measurement configuration information, CSI reporting configuration information, or one of CSI measurement configuration information and CSI reporting configuration information; receiving CSI measurement resources; and Report CSI feedback to the network. 2 . The processor according to claim 1 , wherein the CSI measurement resources include channel measurement resources (CMRs) and interference measurement resources (IMRs), and the IMRs are transmitted by the network with a non-integer period. 3 . The processor according to claim 1 , wherein a period of the CSI report is a non-integer period based on a downlink semi-persistent scheduling (SPS) period. 4 . The processor of claim 1 , wherein the period of the CSI report is a non-integer period based on one or more downlink semi-persistent scheduling (SPS) periods. 5 . The processor according to claim 1 , wherein a period of the CSI measurement resource is a non-integer period based on one or more downlink semi-persistent scheduling (SPS) periods.

6. The processor of claim 1 , wherein the CSI configuration information is included in a radio resource control (RRC) message, the RRC message comprising a first integer, a second integer, and an offset integer, and wherein the first integer and the second integer are used to derive a non-integer CSI reporting period.

7. The processor of claim 1 , wherein the CSI configuration information is included in a radio resource control (RRC) message, the RRC message comprising a first integer, a second integer, and an offset integer, and wherein the first integer and the second integer are used to derive a non-integer period of a channel measurement resource (CMR).

8. The processor of claim 1 , wherein the CSI configuration information is included in a radio resource control (RRC) message, the RRC message comprising a first integer, a second integer, and an offset integer, and wherein the first integer and the second integer are used to derive a non-integer period of an interference measurement resource (IMR).

9. The processor of claim 1 , the operations further comprising: An information element (IE) indicating a relationship between downlink semi-persistent scheduling (SPS) and CSI measurement and reporting opportunities is received from the network.

10. The processor of claim 1, wherein the CSI-FrequencyOccupation is determined based on a downlink semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) frequency allocation. 11 . The processor of claim 1 , wherein the CSI-ReportingBand is determined based on a downlink semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) frequency allocation.

12. A processor of a base station configured to perform operations comprising: Transmitting channel state information (CSI) configuration information corresponding to downlink New Radio (NR) traffic with a non-integer period to a user equipment (UE), wherein the CSI configuration information includes one or more of CSI measurement configuration information and CSI reporting configuration information; Transmit CSI measurement resources; and CSI feedback is received from the UE.

13. The processor of claim 12 , wherein the CSI measurement and reporting configuration information is included in a radio resource control (RRC) message, the RRC message comprising a first integer, a second integer, and an offset integer, and wherein the first integer and the second integer are to be used by the UE to derive a non-integer CSI reporting period.

Images