[go: up one dir, main page]

WO2024103369A1 - Surveillance de canal de commande de liaison descendante physique adaptative pour intervalles de temps variables entre des trames de trafic spécifiques à une application adjacente - Google Patents

Surveillance de canal de commande de liaison descendante physique adaptative pour intervalles de temps variables entre des trames de trafic spécifiques à une application adjacente Download PDF

Info

Publication number
WO2024103369A1
WO2024103369A1 PCT/CN2022/132754 CN2022132754W WO2024103369A1 WO 2024103369 A1 WO2024103369 A1 WO 2024103369A1 CN 2022132754 W CN2022132754 W CN 2022132754W WO 2024103369 A1 WO2024103369 A1 WO 2024103369A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcch
application
frame
traffic
specific traffic
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2022/132754
Other languages
English (en)
Inventor
Zhichao ZHOU
Ahmed Elshafie
Mickael Mondet
Huilin Xu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to PCT/CN2022/132754 priority Critical patent/WO2024103369A1/fr
Publication of WO2024103369A1 publication Critical patent/WO2024103369A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for adaptive physical downlink control channel (PDCCH) monitoring for variable time intervals between adjacent application-specific traffic frames.
  • PDCCH physical downlink control channel
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
  • Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, or the like) .
  • multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE) .
  • LTE/LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP) .
  • UMTS Universal Mobile Telecommunications System
  • a wireless network may include one or more network nodes that support communication for wireless communication devices, such as a user equipment (UE) or multiple UEs.
  • a UE may communicate with a network node via downlink communications and uplink communications.
  • Downlink (or “DL” ) refers to a communication link from the network node to the UE
  • uplink (or “UL” ) refers to a communication link from the UE to the network node.
  • Some wireless networks may support device-to-device communication, such as via a local link (e.g., a sidelink (SL) , a wireless local area network (WLAN) link, and/or a wireless personal area network (WPAN) link, among other examples) .
  • SL sidelink
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • New Radio which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the 3GPP.
  • NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and/or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM) ) on the uplink, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
  • OFDM orthogonal frequency division multiplexing
  • SC-FDM single-carrier frequency division multiplexing
  • DFT-s-OFDM discrete Fourier transform spread OFDM
  • MIMO multiple-input multiple-output
  • the UE may include a memory and one or more processors coupled to the memory.
  • the one or more processors may be configured to receive, from a network node, a configuration of a physical downlink control channel (PDCCH) skipping duration that is based at least in part on a frame rate for application-specific traffic and a jitter range of the application-specific traffic.
  • the one or more processors may be configured to receive, from the network node, data associated with a frame of the application-specific traffic.
  • PDCCH physical downlink control channel
  • the one or more processors may be configured to refrain from PDCCH monitoring, in connection with receiving the data associated with the frame, for the PDCCH skipping duration or a duration based at least in part on an indication that an arrival of a next frame of the application-specific traffic is prior to an end of the PDCCH skipping duration.
  • the application-specific traffic may be traffic associated with an extended reality (XR) application, a cloud-based application, a gaming application, or a video application.
  • XR extended reality
  • the UE may include a memory and one or more processors coupled to the memory.
  • the one or more processors may be configured to receive, from a network node, an indication of a frame rate for application-specific traffic.
  • the one or more processors may be configured to receive, from the network node, data associated with a frame of the application-specific traffic.
  • the one or more processors may be configured to refrain from PDCCH monitoring, after receiving the data associated with the frame, for a duration determined based at least in part on the frame rate for the application-specific traffic and a jitter range for the application-specific traffic.
  • the application-specific traffic may be traffic associated with an XR application, a cloud-based application, a gaming application, or a video application.
  • the network node may include a memory and one or more processors coupled to the memory.
  • the one or more processors may be configured to transmit, to a UE, a configuration of a PDCCH skipping duration that is based at least in part on a frame rate for application-specific traffic and a jitter range of the application-specific traffic.
  • the one or more processors may be configured to transmit, to the UE, data associated with a frame of the application-specific traffic.
  • the one or more processors may be configured to transmit, to the UE, an indication to trigger PDCCH monitoring prior to an end of the PDCCH skipping duration after reception, by the UE, of the frame, based at least in part on a determination that a PDCCH communication for a next frame of the application-specific traffic is to be transmitted prior to an end of the PDCCH skipping duration.
  • the application-specific traffic may be traffic associated with an XR application, a cloud-based application, a gaming application, or a video application.
  • the method may include receiving, from a network node, an indication of a frame rate for application-specific traffic.
  • the method may include receiving, from the network node, data associated with a frame of the application-specific traffic.
  • the method may include refraining from PDCCH monitoring, after receiving the data associated with the frame, for a duration determined based at least in part on the frame rate for the application-specific traffic and a jitter range for the application-specific traffic.
  • the method may include transmitting, to a UE, a configuration of a PDCCH skipping duration that is based at least in part on a frame rate for application-specific traffic and a jitter range of the application-specific traffic.
  • the method may include transmitting, to the UE, data associated with a frame of the application-specific traffic.
  • the method may include transmitting, to the UE, an indication to trigger PDCCH monitoring prior to an end of the PDCCH skipping duration after reception, by the UE, of the frame, based at least in part on a determination that a PDCCH communication for a next frame of the application-specific traffic is to be transmitted prior to an end of the PDCCH skipping duration.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE.
  • the set of instructions when executed by one or more processors of the UE, may cause the UE to receive, from a network node, a configuration of a PDCCH skipping duration that is based at least in part on a frame rate for application-specific traffic and a jitter range of the application-specific traffic.
  • the set of instructions when executed by one or more processors of the UE, may cause the UE to receive, from the network node, data associated with a frame of the application-specific traffic.
  • the set of instructions when executed by one or more processors of the UE, may cause the UE to refrain from PDCCH monitoring, in connection with receiving the data associated with the frame, for the PDCCH skipping duration or a duration based at least in part on an indication that an arrival of a next frame of the application-specific traffic is prior to an end of the PDCCH skipping duration.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE.
  • the set of instructions when executed by one or more processors of the UE, may cause the UE to receive, from a network node, an indication of a frame rate for application-specific traffic.
  • the set of instructions when executed by one or more processors of the UE, may cause the UE to receive, from the network node, data associated with a frame of the application-specific.
  • the set of instructions when executed by one or more processors of the UE, may cause the UE to refrain from PDCCH monitoring, after receiving the data associated with the frame, for a duration determined based at least in part on the frame rate for the application-specific traffic and a jitter range for the application-specific traffic.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node.
  • the set of instructions when executed by one or more processors of the network node, may cause the network node to transmit, to a UE, a configuration of a PDCCH skipping duration that is based at least in part on a frame rate for application-specific traffic and a jitter range of the application-specific traffic.
  • the set of instructions when executed by one or more processors of the network node, may cause the network node to transmit, to the UE, data associated with a frame of the application-specific traffic.
  • the set of instructions when executed by one or more processors of the network node, may cause the network node to transmit, to the UE, an indication to trigger PDCCH monitoring prior to an end of the PDCCH skipping duration after reception, by the UE, of the frame, based at least in part on a determination that a PDCCH communication for a next frame of the application-specific traffic is to be transmitted prior to an end of the PDCCH skipping duration.
  • the apparatus may include means for receiving, from a network node, a configuration of a PDCCH skipping duration that is based at least in part on a frame rate for application-specific traffic and a jitter range of the application-specific traffic.
  • the apparatus may include means for receiving, from the network node, data associated with a frame of the application-specific traffic.
  • the apparatus may include means for refraining from PDCCH monitoring, in connection with receiving the data associated with the frame, for the PDCCH skipping duration or a duration based at least in part on an indication that an arrival of a next frame of the application-specific traffic is prior to an end of the PDCCH skipping duration.
  • the apparatus may include means for receiving, from a network node, an indication of a frame rate for application-specific traffic.
  • the apparatus may include means for receiving, from the network node, data associated with a frame of the application-specific.
  • the apparatus may include means for refraining from PDCCH monitoring, after receiving the data associated with the frame, for a duration determined based at least in part on the frame rate for the application-specific traffic and a jitter range for the application-specific traffic.
  • the apparatus may include means for transmitting, to a UE, a configuration of a PDCCH skipping duration that is based at least in part on a frame rate for application-specific traffic and a jitter range of the application-specific traffic.
  • the apparatus may include means for transmitting, to the UE, data associated with a frame of the application-specific traffic.
  • the apparatus may include means for transmitting, to the UE, an indication to trigger PDCCH monitoring prior to an end of the PDCCH skipping duration after reception, by the UE, of the frame, based at least in part on a determination that a PDCCH communication for a next frame of the application-specific traffic is to be transmitted prior to an end of the PDCCH skipping duration.
  • aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network entity, network node, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.
  • aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios.
  • Techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements.
  • some aspects may be implemented via integrated chip embodiments or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, and/or artificial intelligence devices) .
  • Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and/or system-level components.
  • Devices incorporating described aspects and features may include additional components and features for implementation and practice of claimed and described aspects.
  • transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and/or summers) .
  • RF radio frequency
  • aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, and/or end-user devices of varying size, shape, and constitution.
  • Fig. 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.
  • Fig. 2 is a diagram illustrating an example of a network node in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.
  • UE user equipment
  • Fig. 3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure.
  • Fig. 4 is a diagram illustrating an example of a split-rendering extended reality (XR) system, in accordance with the present disclosure.
  • XR extended reality
  • Fig. 5 is a diagram illustrating an example of variable time intervals between XR frames, in accordance with the present disclosure.
  • Fig. 6 is a diagram illustrating an example of codepoints for indicating search space set group (SSSG) switching and physical downlink control channel (PDCCH) skipping, in accordance with the present disclosure.
  • SSSG search space set group
  • PDCCH physical downlink control channel
  • Figs. 7A-7D and 8 are diagrams illustrating examples associated with adaptive PDCCH monitoring for variable time intervals between adjacent XR frames, in accordance with the present disclosure.
  • Figs. 9-10 are diagrams illustrating example processes performed, for example, by a UE, in accordance with the present disclosure.
  • Fig. 11 is a diagram illustrating an example process performed, for example, by a network node, in accordance with the present disclosure.
  • Figs. 12-13 are diagrams of example apparatuses for wireless communication, in accordance with the present disclosure.
  • NR New Radio
  • RAT radio access technology
  • Fig. 1 is a diagram illustrating an example of a wireless network 100, in accordance with the present disclosure.
  • the wireless network 100 may be or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., Long Term Evolution (LTE) ) network, among other examples.
  • 5G e.g., NR
  • 4G e.g., Long Term Evolution (LTE) network
  • the wireless network 100 may include one or more network nodes 110 (shown as a network node 110a, a network node 110b, a network node 110c, and a network node 110d) , a user equipment (UE) 120 or multiple UEs 120 (shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e) , and/or other entities.
  • a network node 110 is a network node that communicates with UEs 120. As shown, a network node 110 may include one or more network nodes.
  • a network node 110 may be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit) .
  • RAN radio access network
  • a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station) , meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs) , one or more distributed units (DUs) , or one or more radio units (RUs) ) .
  • CUs central units
  • DUs distributed units
  • RUs radio units
  • a network node 110 is or includes a network node that communicates with UEs 120 via a radio access link, such as an RU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or a core network via a backhaul link, such as a CU.
  • a network node 110 may include multiple network nodes, such as one or more RUs, one or more CUs, and/or one or more DUs.
  • a network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G) , a gNB (e.g., in 5G) , an access point, a transmission reception point (TRP) , a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof.
  • the network nodes 110 may be interconnected to one another or to one or more other network nodes 110 in the wireless network 100 through various types of fronthaul, midhaul, and/or backhaul interfaces, such as a direct physical connection, an air interface, or a virtual network, using any suitable transport network.
  • a network node 110 may provide communication coverage for a particular geographic area.
  • the term “cell” can refer to a coverage area of a network node 110 and/or a network node subsystem serving this coverage area, depending on the context in which the term is used.
  • a network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or another type of cell.
  • a macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions.
  • a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions.
  • a femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 having association with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG) ) .
  • a network node 110 for a macro cell may be referred to as a macro network node.
  • a network node 110 for a pico cell may be referred to as a pico network node.
  • a network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. In the example shown in Fig.
  • the network node 110a may be a macro network node for a macro cell 102a
  • the network node 110b may be a pico network node for a pico cell 102b
  • the network node 110c may be a femto network node for a femto cell 102c.
  • a network node may support one or multiple (e.g., three) cells.
  • a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a network node 110 that is mobile (e.g., a mobile network node) .
  • base station or “network node” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof.
  • base station or “network node” may refer to a CU, a DU, an RU, a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) , or a Non-Real Time (Non-RT) RIC, or a combination thereof.
  • the terms “base station” or “network node” may refer to one device configured to perform one or more functions, such as those described herein in connection with the network node 110.
  • the terms “base station” or “network node” may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a quantity of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to duplicate performance of at least a portion of the function, and the terms “base station” or “network node” may refer to any one or more of those different devices.
  • the terms “base station” or “network node” may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device.
  • the terms “base station” or “network node” may refer to one of the base station functions and not another. In this way, a single device may include more than one base station.
  • the wireless network 100 may include one or more relay stations.
  • a relay station is a network node that can receive a transmission of data from an upstream node (e.g., a network node 110 or a UE 120) and send a transmission of the data to a downstream node (e.g., a UE 120 or a network node 110) .
  • a relay station may be a UE 120 that can relay transmissions for other UEs 120.
  • the network node 110d e.g., a relay network node
  • the network node 110a may communicate with the network node 110a (e.g., a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d.
  • a network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, or the like.
  • the wireless network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, or the like. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and/or different impacts on interference in the wireless network 100. For example, macro network nodes may have a high transmit power level (e.g., 5 to 40 watts) whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 to 2 watts) .
  • macro network nodes may have a high transmit power level (e.g., 5 to 40 watts)
  • pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 to 2 watts) .
  • a network controller 130 may couple to or communicate with a set of network nodes 110 and may provide coordination and control for these network nodes 110.
  • the network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link.
  • the network nodes 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link.
  • the network controller 130 may be a CU or a core network device, or may include a CU or a core network device.
  • the UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile.
  • a UE 120 may include, for example, an access terminal, a terminal, a mobile station, and/or a subscriber unit.
  • a UE 120 may be a cellular phone (e.g., a smart phone) , a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet) ) , an entertainment device (e.g., a music device, a video device, and/or a satellite radio)
  • Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs.
  • An MTC UE and/or an eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and/or a location tag, that may communicate with a network node, another device (e.g., a remote device) , or some other entity.
  • Some UEs 120 may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband IoT) devices.
  • Some UEs 120 may be considered a Customer Premises Equipment.
  • a UE 120 may be included inside a housing that houses components of the UE 120, such as processor components and/or memory components.
  • the processor components and the memory components may be coupled together.
  • the processor components e.g., one or more processors
  • the memory components e.g., a memory
  • the processor components and the memory components may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.
  • any number of wireless networks 100 may be deployed in a given geographic area.
  • Each wireless network 100 may support a particular RAT and may operate on one or more frequencies.
  • a RAT may be referred to as a radio technology, an air interface, or the like.
  • a frequency may be referred to as a carrier, a frequency channel, or the like.
  • Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
  • NR or 5G RAT networks may be deployed.
  • two or more UEs 120 may communicate directly using one or more sidelink channels (e.g., without using a network node 110 as an intermediary to communicate with one another) .
  • the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol) , and/or a mesh network.
  • V2X vehicle-to-everything
  • a UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the network node 110.
  • Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, or the like. For example, devices of the wireless network 100 may communicate using one or more operating bands.
  • devices of the wireless network 100 may communicate using one or more operating bands.
  • two initial operating bands have been identified as frequency range designations FR1 (410 MHz –7.125 GHz) and FR2 (24.25 GHz –52.6 GHz) . It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles.
  • FR2 which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz –300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
  • EHF extremely high frequency
  • ITU International Telecommunications Union
  • FR3 7.125 GHz –24.25 GHz
  • FR3 7.125 GHz –24.25 GHz
  • Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies.
  • higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz.
  • FR4a or FR4-1 52.6 GHz –71 GHz
  • FR4 52.6 GHz –114.25 GHz
  • FR5 114.25 GHz –300 GHz
  • sub-6 GHz may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies.
  • millimeter wave may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band.
  • frequencies included in these operating bands may be modified, and techniques described herein are applicable to those modified frequency ranges.
  • the UE 120 may include a communication manager 140.
  • the communication manager 140 may receive, from a network node, a configuration of a physical downlink control channel (PDCCH) skipping duration that is based at least in part on a frame rate for application-specific traffic and a jitter range of the application-specific traffic; receive, from the network node, data associated with a frame of the application-specific traffic; and refrain from PDCCH monitoring, in connection with receiving the data associated with the frame, for the PDCCH skipping duration or a duration based at least in part on an indication that an arrival of a next frame of the application-specific traffic is prior to an end of the PDCCH skipping duration. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.
  • PDCCH physical downlink control channel
  • the communication manager 140 may receive, from a network node, an indication of a frame rate for application-specific traffic; receive, from the network node, data associated with a frame of the application-specific traffic; and refrain from PDCCH monitoring, after receiving the data associated with the frame, for a duration determined based at least in part on the frame rate for the application-specific traffic and a jitter range for the application-specific traffic. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.
  • the network node 110 may include a communication manager 150.
  • the communication manager 150 may transmit, to a UE, a configuration of a PDCCH skipping duration that is based at least in part on a frame rate for application-specific traffic and a jitter range of the application-specific traffic; transmit, to the UE, data associated with a frame of the application-specific traffic; and transmit, to the UE, an indication to trigger PDCCH monitoring prior to an end of the PDCCH skipping duration after reception, by the UE, of the frame, based at least in part on a determination that a PDCCH communication for a next frame of the application-specific traffic is to be transmitted prior to an end of the PDCCH skipping duration.
  • the communication manager 150 may perform one or more other operations described herein.
  • Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.
  • Fig. 2 is a diagram illustrating an example 200 of a network node 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure.
  • the network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ⁇ 1) .
  • the UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ⁇ 1) .
  • the network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232.
  • a network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node.
  • Some network nodes 110 may not include radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs, or one or more DUs.
  • a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120) .
  • the transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120.
  • MCSs modulation and coding schemes
  • CQIs channel quality indicators
  • the network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS (s) selected for the UE 120 and may provide data symbols for the UE 120.
  • the transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI) ) and control information (e.g., CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and control symbols.
  • the transmit processor 220 may generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS) ) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) ) .
  • reference signals e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)
  • synchronization signals e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)
  • a transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) , shown as modems 232a through 232t.
  • each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232.
  • Each modem 232 may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream.
  • Each modem 232 may further use a respective modulator component to process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain a downlink signal.
  • the modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) , shown as antennas 234a through 234t.
  • a set of antennas 252 may receive the downlink signals from the network node 110 and/or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) , shown as modems 254a through 254r.
  • R received signals e.g., R received signals
  • each received signal may be provided to a demodulator component (shown as DEMOD) of a modem 254.
  • DEMOD demodulator component
  • Each modem 254 may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and/or digitize) a received signal to obtain input samples.
  • Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols.
  • a MIMO detector 256 may obtain received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols.
  • a receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller/processor 280.
  • controller/processor may refer to one or more controllers, one or more processors, or a combination thereof.
  • a channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and/or a CQI parameter, among other examples.
  • RSRP reference signal received power
  • RSSI received signal strength indicator
  • RSSRQ reference signal received quality
  • CQI CQI parameter
  • the network controller 130 may include a communication unit 294, a controller/processor 290, and a memory 292.
  • the network controller 130 may include, for example, one or more devices in a core network.
  • the network controller 130 may communicate with the network node 110 via the communication unit 294.
  • One or more antennas may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and/or one or more antenna arrays, among other examples.
  • An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements (within a single housing or multiple housings) , a set of coplanar antenna elements, a set of non-coplanar antenna elements, and/or one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components of Fig. 2.
  • a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and/or CQI) from the controller/processor 280.
  • the transmit processor 264 may generate reference symbols for one or more reference signals.
  • the symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by the modems 254 (e.g., for DFT-s-OFDM or CP-OFDM) , and transmitted to the network node 110.
  • the modem 254 of the UE 120 may include a modulator and a demodulator.
  • the UE 120 includes a transceiver.
  • the transceiver may include any combination of the antenna (s) 252, the modem (s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and/or the TX MIMO processor 266.
  • the transceiver may be used by a processor (e.g., the controller/processor 280) and the memory 282 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 7A-7D and 8-13) .
  • the uplink signals from UE 120 and/or other UEs may be received by the antennas 234, processed by the modem 232 (e.g., a demodulator component, shown as DEMOD, of the modem 232) , detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120.
  • the receive processor 238 may provide the decoded data to a data sink 239 and provide the decoded control information to the controller/processor 240.
  • the network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244.
  • the network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and/or uplink communications.
  • the modem 232 of the network node 110 may include a modulator and a demodulator.
  • the network node 110 includes a transceiver.
  • the transceiver may include any combination of the antenna (s) 234, the modem (s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and/or the TX MIMO processor 230.
  • the transceiver may be used by a processor (e.g., the controller/processor 240) and the memory 242 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 7A-7D and 8-13) .
  • the controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, and/or any other component (s) of Fig. 2 may perform one or more techniques associated with adaptive PDCCH monitoring for variable time intervals between adjacent application-specific trafficframes, as described in more detail elsewhere herein.
  • the controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, and/or any other component (s) of Fig. 2 may perform or direct operations of, for example, process 900 of Fig. 9, process 1000 of Fig. 10, process 1100 of Fig. 11, and/or other processes as described herein.
  • the memory 242 and the memory 282 may store data and program codes for the network node 110 and the UE 120, respectively.
  • the memory 242 and/or the memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication.
  • the one or more instructions when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the network node 110 and/or the UE 120, may cause the one or more processors, the UE 120, and/or the network node 110 to perform or direct operations of, for example, process 900 of Fig. 9, process 1000 of Fig. 10, process 1100 of Fig. 11, and/or other processes as described herein.
  • executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.
  • a UE (e.g., the UE 120) includes means for receiving, from a network node, a configuration of a PDCCH skipping duration that is based at least in part on a frame rate for application-specific traffic and a jitter range of the application-specific traffic; means for receiving, from the network node, data associated with a frame of the application-specific traffic; and/or means for refraining from PDCCH monitoring, in connection with receiving the data associated with the frame, for the PDCCH skipping duration or a duration based at least in part on an indication that an arrival of a next frame of the application-specific traffic is prior to an end of the PDCCH skipping duration.
  • the means for the UE to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.
  • a UE (e.g., the UE 120) includes means for receiving, from a network node, an indication of a frame rate for application-specific traffic; means for receiving, from the network node, data associated with a frame of the application-specific traffic; and/or means for refraining from PDCCH monitoring, after receiving the data associated with the frame, for a duration determined based at least in part on the frame rate for the application-specific traffic and a jitter range for the application-specific traffic.
  • the means for the UE to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.
  • a network node (e.g., the network node 110) includes means for transmitting, to a UE, a configuration of a PDCCH skipping duration that is based at least in part on a frame rate for application-specific traffic and a jitter range of the application-specific traffic; means for transmitting, to the UE, data associated with a frame of the application-specific traffic; and/or means for transmitting, to the UE, an indication to trigger PDCCH monitoring prior to an end of the PDCCH skipping duration after reception, by the UE, of the frame, based at least in part on a determination that a PDCCH communication for a next frame of the application-specific traffic is to be transmitted prior to an end of the PDCCH skipping duration.
  • the means for the network node to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.
  • While blocks in Fig. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components.
  • the functions described with respect to the transmit processor 264, the receive processor 258, and/or the TX MIMO processor 266 may be performed by or under the control of the controller/processor 280.
  • Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.
  • Deployment of communication systems may be arranged in multiple manners with various components or constituent parts.
  • a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station, or a network equipment may be implemented in an aggregated or disaggregated architecture.
  • a base station such as a Node B (NB) , an evolved NB (eNB) , an NR base station, a 5G NB, an access point (AP) , a TRP, or a cell, among other examples
  • NB Node B
  • eNB evolved NB
  • AP access point
  • TRP TRP
  • a cell a cell
  • a base station such as a Node B (NB) , an evolved NB (eNB) , an NR base station, a 5G NB, an access point (AP) , a TRP, or a cell, among other examples
  • a base station such as a Node B (NB) , an evolved NB (eNB) , an NR base station, a 5G NB, an access point (AP) , a TRP, or a cell, among other examples
  • AP access point
  • TRP TRP
  • a cell a cell, among other examples
  • Network entity or “network node”
  • An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit) .
  • a disaggregated base station e.g., a disaggregated network node
  • a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other network nodes.
  • the DUs may be implemented to communicate with one or more RUs.
  • Each of the CU, DU, and RU also can be implemented as virtual units, such as a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) , among other examples.
  • VCU virtual central unit
  • VDU virtual distributed unit
  • VRU virtual radio unit
  • Base station-type operation or network design may consider aggregation characteristics of base station functionality.
  • disaggregated base stations may be utilized in an IAB network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance) ) , or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN) ) to facilitate scaling of communication systems by separating base station functionality into one or more units that can be individually deployed.
  • a disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented for at least one unit virtually, which can enable flexibility in network design.
  • the various units of the disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.
  • Fig. 3 is a diagram illustrating an example disaggregated base station architecture 300, in accordance with the present disclosure.
  • the disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units (such as a Near-RT RIC 325 via an E2 link, or a Non-RT RIC 315 associated with a Service Management and Orchestration (SMO) Framework 305, or both) .
  • a CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as through F1 interfaces.
  • Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links.
  • Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links.
  • RF radio frequency
  • Each of the units may include one or more interfaces or be coupled with one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium.
  • Each of the units, or an associated processor or controller providing instructions to one or multiple communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission medium.
  • each of the units can include a wired interface, configured to receive or transmit signals over a wired transmission medium to one or more of the other units, and a wireless interface, which may include a receiver, a transmitter or transceiver (such as an RF transceiver) , configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
  • a wireless interface which may include a receiver, a transmitter or transceiver (such as an RF transceiver) , configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
  • the CU 310 may host one or more higher layer control functions.
  • control functions can include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among other examples.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • SDAP service data adaptation protocol
  • Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310.
  • the CU 310 may be configured to handle user plane functionality (for example, Central Unit –User Plane (CU-UP) functionality) , control plane functionality (for example, Central Unit –Control Plane (CU-CP) functionality) , or a combination thereof.
  • the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units.
  • a CU-UP unit can communicate bidirectionally with a CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration.
  • the CU 310 can be implemented to communicate with a DU 330, as necessary, for network control and signaling.
  • Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340.
  • the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP.
  • the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples.
  • FEC forward error correction
  • the DU 330 may further host one or more low PHY layers, such as implemented by one or more modules for a fast Fourier transform (FFT) , an inverse FFT (iFFT) , digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples.
  • FFT fast Fourier transform
  • iFFT inverse FFT
  • PRACH physical random access channel
  • Each layer (which also may be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.
  • Each RU 340 may implement lower-layer functionality.
  • an RU 340, controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing an FFT, performing an iFFT, digital beamforming, or PRACH extraction and filtering, among other examples, based on a functional split (for example, a functional split defined by the 3GPP) , such as a lower layer functional split.
  • each RU 340 can be operated to handle over the air (OTA) communication with one or more UEs 120.
  • OTA over the air
  • real-time and non-real-time aspects of control and user plane communication with the RU (s) 340 can be controlled by the corresponding DU 330.
  • this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
  • the SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements.
  • the SMO Framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (such as an O1 interface) .
  • the SMO Framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface) .
  • a cloud computing platform such as an open cloud (O-Cloud) platform 390
  • network element life cycle management such as to instantiate virtualized network elements
  • a cloud computing platform interface such as an O2 interface
  • Such virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, non-RT RICs 315, and Near-RT RICs 325.
  • the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, via an O1 interface. Additionally, in some implementations, the SMO Framework 305 can communicate directly with each of one or more RUs 340 via a respective O1 interface.
  • the SMO Framework 305 also may include a Non-RT RIC 315 configured to support functionality of the SMO Framework 305.
  • the Non-RT RIC 315 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence/Machine Learning (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 325.
  • the Non-RT RIC 315 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 325.
  • the Near-RT RIC 325 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, or both, as well as an O-eNB, with the Near-RT RIC 325.
  • the Non-RT RIC 315 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 325 and may be received at the SMO Framework 305 or the Non-RT RIC 315 from non-network data sources or from network functions. In some examples, the Non-RT RIC 315 or the Near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 315 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 305 (such as reconfiguration via an O1 interface) or via creation of RAN management policies (such as A1 interface policies) .
  • Fig. 3 is provided as an example. Other examples may differ from what is described with regard to Fig. 3.
  • Fig. 4 is a diagram illustrating an example 400 of a split-rendering extended reality (XR) system, in accordance with the present disclosure.
  • XR is an umbrella term encapsulating augmented reality (AR) , virtual reality (VR) , mixed reality (MR) , or any combination thereof.
  • AR augmented reality
  • VR virtual reality
  • MR mixed reality
  • Fig. 4 rendering for a scene on an XR display is split between an XR server 405 and an XR device 410 that includes the XR display.
  • on-device rendering and perception processing, on the XR device 410 may be augmented by graphics rendering by the XR server via wireless network (e.g., 5G) communications.
  • wireless network e.g., 5G
  • the XR server 405 may be an application server that serves an application client running on the XR device 410.
  • the XR server 405 may be an edge server (or an edge cloud) connected to a network node (e.g., network node 110) , such as a 5G/NR base station.
  • the XR device may be a UE (e.g., UE 120) , may be included in a UE, or may include a UE.
  • the XR device may include a wearable XR headset.
  • XR traffic is an example of application-specific traffic (e.g., traffic associated an application or a type of application) that is frame-based.
  • XR traffic from the XR server 405 may be deliver to the XR device 410 (e.g., via the network node) is bursts of traffic corresponding to frames to be displayed/rendered on the XR device.
  • Other types of application-specific traffic e.g., cloud gaming traffic (or traffic for other gaming related applications or cloud-based applications) , or video traffic, among other examples
  • cloud gaming traffic or traffic for other gaming related applications or cloud-based applications
  • video traffic may be frame-based as well.
  • the XR device 410 may transmit uplink data, including user pose data and/or input data, to the XR server 405 via the network node.
  • the user pose data may include a current pose of the XR device.
  • the user pose data may include a six degree of freedom (6-DoF) or three degree of freedom (3-DoF) pose of the XR headset, which may be tracked by sensors on the XR headset.
  • the uplink data may include input data, such as controller input from an XR controller.
  • the transmission rate of the pose and controller data may be the same as a video frame rate (e.g., 90 Hz) .
  • the XR server 405 and the XR device 410 may render each video frame, displayed on a display of the XR device 410, based on the latest pose information.
  • the XR server 405 may generate an XR scene (e.g., an updated XR scene) and perform XR viewport pre-rendering rasterization of the XR scene.
  • the XR server 405 may then encode the pre-rendered XR viewport as 2D media and transmit the encoded data (e.g., the 2D media for the pre-rendered viewport) to the XR device 410 via the network node (e.g., as downlink data) .
  • the XR device 410 may decode the 2D media, render the XR viewport using Asynchronous TimeWarp (ATW) rendering based on the latest pose tracking information, and display the rendered XR viewport for the updated scene of the display of the XR device 410.
  • Asynchronous TimeWarp Asynchronous TimeWarp
  • the delay from user motion to the updated scene being displayed on the display device may be minimized.
  • this delay may correspond to the motion-to-render-to-photon (M2R2P) time.
  • photon refers to the display device.
  • the M2R2P time may be equal to a sum of a 5G round trip time (5G-RTT) , a client multimedia processing time (e.g., the processing time of the XR device 410) , and the server multimedia processing time (e.g., the processing time of the XR server 405) .
  • 5G-RTT 5G round trip time
  • client multimedia processing time e.g., the processing time of the XR device 410
  • server multimedia processing time e.g., the processing time of the XR server 405
  • the 5G-RTT may be equal to the sum of an uplink latency associated with transmitting the uplink data from the XR device 410 to the XR server 405 and a downlink latency associated with transmitting the downlink data from the XR server 405 to the XR device 410.
  • Fig. 4 is provided as an example. Other examples may differ from what is described with respect to Fig. 4.
  • Fig. 5 is a diagram illustrating an example 500 of variable time intervals between XR frames, in accordance with the present disclosure.
  • XR traffic may be quasi-periodic with characteristics of low latency, high data rate, and high reliability requirements.
  • arrival times of XR traffic may vary due to jitter (where jitter is a variation or uncertainty in the arrival time of a communication, such as an expected or observed deviation of an actual arrival time of a packet relative to a scheduled arrival time of the packet) .
  • jitter is a variation or uncertainty in the arrival time of a communication, such as an expected or observed deviation of an actual arrival time of a packet relative to a scheduled arrival time of the packet
  • PDB packet delay budget
  • XR traffic may include different types of frames or slices, such as I-frames/slices (intra-coded picture frames/slices) and P-frames/slices (predicted picture frames/slices) .
  • Such XR frames may have variable sizes.
  • the average size ratio between one I-frame/slice and one P-frame/slice can be from 1.5 to 3.
  • the maximum ratio between two XR frames/slices can be up to 9.
  • Frames with discrepant sizes may require different volume processing and different RAN resources (e.g., different amounts of resources in the time domain and the frequency domain) for transmission of such XR frames.
  • the time interval between XR frames of different types of XR flows may also be variable, as shown in Fig. 5.
  • Fig. 5 shows an example cumulative distribution function (CDF) of time intervals between XR frames.
  • CDF cumulative distribution function
  • the time interval ( ⁇ T) between adjacent XR frames of different types may vary from 4 slots to 29 slots.
  • Fig. 5 is provided as an example. Other examples may differ from what is described with respect to Fig. 5.
  • Fig. 6 is a diagram illustrating an example 600 of codepoints for indicating search space set group (SSSG) switching and PDCCH skipping, in accordance with the present disclosure.
  • power saving is important for XR devices, such as XR UEs, due to limited battery size in such XR devices.
  • SSSG switching and/or PDCCH skipping may be used for UE power saving.
  • “PDCCH skipping” refers to a UE skipping PDCCH monitoring occasions (e.g., the UE refraining from monitoring for PDCCH during PDCCH monitoring occasions) .
  • a 2-bit codepoint may be indicated in specific downlink control information (DCI) and may be used to trigger SSSG switching of PDCCH skipping for a UE.
  • DCI downlink control information
  • different values (e.g., 00, 01, 10, and 11) of the 2-bit codepoint correspond to different UE behaviors (e.g., Behavior (Beh) 2 (SSSG#0) , Beh 2A (SSSG#1) , Beh 1A for duration T1, and Beh 1A for duration T2) .
  • Beh Behavior
  • SSSG#0 Beh 2A
  • Beh 1A Beh 1A for duration T1
  • Beh 1A for duration T2
  • a 2-bit codepoint with a value of 00 or 01 in the DCI triggers SSSG switching for the UE (e.g., to SSSG#0 or SSSG#1) .
  • a 2-bit codebook with a value of 10 in the DCI indicates PDCCH skipping with a first PDCCH skipping duration T1
  • a 2-bit codebook with a value of 11 in the DCI indicates PDCCH skipping with a second PDCCH skipping duration T2.
  • PDCCH skipping between XR frames may reduce power consumption by an XR UE.
  • the time intervals between different XR frames may be variable, and the PDCCH skipping duration indicated by the codepoint in the DCI is limited to two options (e.g., T1 and T2) .
  • the two available PDCCH skipping durations (e.g., T1 and T2) may not sufficiently cover the variable time intervals of XR frames for different types of XR traffic.
  • the PDCCH skipping will not be sufficient and the UE will perform unnecessary PDCCH monitoring, which results in unnecessary UE power consumption and reduced UE battery life.
  • the PDCCH skipping may cause the UE to miss DCI that schedules downlink data transmissions for the UE, which results in decreased reliability and increased latency for the UE.
  • a UE may receive, from a network node, a configuration of a PDCCH skipping duration that is based at least in part on a frame rate for application-specific traffic (e.g., XR traffic) and a jitter range of the application-specific traffic.
  • the UE may receive, from the network node, data associated with a frame of the application-specific traffic (e.g., an XR frame) .
  • the UE may refrain from PDCCH monitoring, after receiving the data associated with the frame, for the PDCCH skipping duration or a duration based at least in part on an indication that an arrival of a next frame of the application-specific traffic is prior to an end of the PDCCH skipping duration.
  • the PDCCH skipping duration may be a longest interval between adjacent frames based at least in part on the frame rate and the jitter range.
  • the UE 120 may refrain from PDCCH monitoring for the PDCCH skipping duration unless the UE receives an indication that triggers the UE to resume PDCCH monitoring prior to the end of the PDCCH skipping duration.
  • the UE may perform PDCCH skipping with an adaptive duration between adjacent frames of the application-specific (e.g., adjacent XR frames) such that excessive PDCCH monitoring is reduced without missing PDCCH communications.
  • UE power consumption may be reduced (e.g., by reducing excessive PDCCH monitoring) , resulting in increased UE battery life, without decreasing traffic reliability and without increasing traffic latency (e.g., due to missed DCI during PDCCH skipping) for XR traffic and/or other frame-based application-specific traffic, such as traffic associated with cloud-based applications, gaming applications (e.g., cloud gaming traffic) , or video applications (e.g., video streaming traffic) , among other examples.
  • gaming applications e.g., cloud gaming traffic
  • video applications e.g., video streaming traffic
  • Fig. 6 is provided as an example. Other examples may differ from what is described with respect to Fig. 6.
  • Figs. 7A-7D are diagrams illustrating an example 700 associated with adaptive PDCCH monitoring for variable time intervals between adjacent XR frames, in accordance with the present disclosure.
  • example 700 includes communication between a network node 110 and a UE 120.
  • the network node 110 and the UE 120 may be included in a wireless network, such as wireless network 100.
  • the network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.
  • the UE 120 may be an XR UE associated with an XR application. That is, the UE 120 may be, include, or be included in an XR device (e.g., XR device 410) .
  • the network node 110 may communicate XR traffic between an XR server (e.g., XR server 405) and the XR UE (e.g., the UE 120) .
  • the network node 110 may receive uplink XR traffic from the XR UE and transmit the uplink XR traffic to the XR server, and the network node may receive downlink XR traffic from the XR server and transmit the downlink XR traffic to the XR UE.
  • the network node 110 may include, be included in, or be the XR server (e.g., XR server 405) .
  • the network node 110 may transmit, and the UE 120 may receive, a configuration of a PDCCH skipping duration for XR traffic.
  • the network node 110 may configure the UE 120 to perform adaptive PDCCH skipping between frames of XR traffic.
  • the network node 110 may transmit configuration information to the UE 120, and the configuration information may indicate a configuration of a PDCCH skipping duration for skipping PDCCH monitoring (e.g., refraining from PDCCH monitoring) between frames of XR traffic to be transmitted to the UE 120.
  • the PDCCH skipping duration may be based at least in part on a frame rate for the XR traffic and a jitter range of the XR traffic.
  • the configuration information that indicates the configuration of the PDCCH skipping duration may be included in an RRC message or a MAC control element (MAC-CE) .
  • MAC-CE MAC control element
  • the network node 110 may determine the PDCCH skipping duration for the UE 120 based at least in part on the frame rate and the jitter range associated with the XR traffic.
  • the frame rate of the XR traffic may also be referred to as the “XR frame rate. ”
  • the network node 110 may know the XR frame rate for the XR traffic to be transmitted to the UE 120.
  • the network node 110 may store frame rates associated with one or more XR traffic flows, or the network node 110 may receive (e.g., from an XR server) an indication of the XR frame rate.
  • the XR frame rate for a specific type of XR traffic may be 60 frames per second (Fps) or 90 Fps, among other examples.
  • the network node 110 may determine a periodicity of the XR frames (e.g., an expected periodicity) based at least in part on the XR frame rate. For example, in a case in which the frame rate is 60 Fps, the time interval (e.g., the expected time interval) between adjacent XR frames is 16.67 ms.
  • the jitter range of the XR traffic is a time range within which the transmission of an XR frame may vary with respect to the expected periodicity of the XR traffic.
  • the jitter range of the XR traffic may be based at least in part on previous XR traffic arrival times and/or transmission times.
  • the jitter range (e.g., which may be calculated based at least in part on previous XR traffic arrival times and/or transmission times) may be specified in a wireless communication standard (e.g., a 3GPP standard) .
  • the jitter range may be [-8 ms, 8 ms] based on a 5%tile and 95%tile truncated distribution of XR frame arrival times. That is, in such examples, in a case in which the frame rate is 60 Fps, an XR frame may be expected to be transmitted to the UE 120 16.67 ⁇ 8 ms after successful transmission of the previous XR frame to the UE 120.
  • the network node 110 may determine the configured PDCCH skipping duration for the UE 120 as a longest interval between adjacent XR frames based at least in part on the XR frame rate and the jitter range.
  • the configured PDCCH skipping duration may be the sum of the expected time interval between adjacent XR frames (e.g., based on the XR frame rate) and the largest jitter value in the jitter range.
  • the configured PDCCH skipping duration may be 24.67 ms (e.g., 16.67 + 8 ms) .
  • the network node 110 may transmit, and the UE 120 may receive, one or more downlink communications associated with an XR frame.
  • the network node 110 may transmit an XR frame to the UE 120, and the UE 120 may receive the XR frame from the network node 110.
  • the transmission of the XR frame to the UE 120 may include one or more downlink communications.
  • the network node 110 may transmit, and the UE 120 may receive, a downlink communication that includes data associated with the XR frame.
  • the data associated with the XR frame may include XR data associated with a scene to be rendered/displayed in the XR frame.
  • the network node 110 may transmit, and the UE 120 may receive, a physical downlink shared channel (PDSCH) communication that includes the data associated with the XR frame.
  • the network node 110 may also transmit, and the UE 120 may receive, a PDCCH communication associated with the XR frame.
  • the PDCCH communication may include DCI that indicates scheduling information for the PDSCH communication and/or other information for decoding the PDSCH communication.
  • the UE 120 may receive the PDCCH communication associated with the XR frame, and receive and decode the PDSCH communication scheduled by the PDCCH communication to obtain the data associated with the XR frame.
  • the UE 120 may refrain from PDCCH monitoring for a duration in connection with receiving the XR frame (e.g., in connection with receiving the data associated with the XR frame) .
  • the UE 120 may enter a PDCCH skipping mode after successfully receiving the data associated with an XR frame (e.g., after successfully receiving and decoding the PDSCH communication associated with the XR frame) .
  • the UE 120 may refrain from monitoring for PDCCH. That is, the UE 120 may skip monitoring for PDCCH in one or more PDCCH occasions that occur while the UE 120 is in the PDCCH skipping mode.
  • the duration for which the UE 120 remains in the PDCCH skipping mode may be either the PDCCH skipping duration configured for the UE 120 or a duration based at least in part on an indication (e.g., from the network node 110) that an arrival of a next XR frame is prior to an end of the PDCCH skipping duration (from the reception of the XR frame by the UE 120) .
  • the indication that the arrival of the next XR frame is prior to the end of the PDCCH skipping duration may be an indication from the network node 110 to trigger PDCCH monitoring (by the UE 120) prior to the end of the PDCCH skipping duration.
  • the network node 110 may transmit, and the UE 120 may receive, an indication to trigger PDCCH monitoring for a next XR frame prior to the end of the configured PDCCH skipping duration.
  • the network node 110 may transmit the indication to trigger PDCCH monitoring based at least in part on a determination that a PDCCH communication for the next XR frame is to be transmitted to the UE 120 prior to an end of the PDCCH skipping duration (e.g., from when the UE 120 enters the PDCCH skipping mode after reception of the previous XR frame) .
  • the network node 110 may not transmit the indication to trigger PDCCH monitoring prior to the end of the configured PDCCH skipping duration in a case in which the next XR frame (e.g., the PDCCH communication associated with the next XR frame) is not to be transmitted to the UE 120 prior to the end of the configured PDCCH skipping duration (e.g., from when the UE 120 enters the PDCCH skipping mode) .
  • the next XR frame e.g., the PDCCH communication associated with the next XR frame
  • the end of the configured PDCCH skipping duration e.g., from when the UE 120 enters the PDCCH skipping mode
  • the indication to trigger PDCCH monitoring prior to the end of the configured PDCCH skipping duration may be a low-power wake-up signal (LP-WUS) .
  • the network node 110 may transmit the LP-WUS to the UE 120 while the UE 120 is in the PDCCH skipping mode.
  • the LP-WUS may indicate a possible arrival time point for the next XR frame.
  • the UE 120 may receive the LP-WUS while the UE 120 is in the PDCCH skipping mode, and the LP-WUS may trigger the UE 120 to resume PDCCH monitoring.
  • the indication to trigger PDCCH monitoring for the next XR frame prior to the end of the configured PDCCH skipping duration may be included in the PDSCH communication associated with the XR (e.g., the previous XR frame) . That is, although Fig. 7A shows the transmission of the indication to trigger PDCCH monitoring as separate from the transmission of the downlink communications associated with the XR frame, in some aspects, the PDSCH communication including the data for an XR frame may also include the indication to trigger PDCCH monitoring for the next frame prior to the end of the configured PDCCH skipping duration after reception and decoding of the PDSCH communication by the UE 120.
  • the PDSCH communication may include a PDCCH monitoring trigger indicator that indicates when to resume PDCCH monitoring for the next XR frame.
  • the PDCCH monitoring trigger indicator may also be referred to as a “PDSCH piggyback indicator” because the PDCCH monitoring trigger indicator is included in (or “piggybacks on” ) the PDSCH communication for the previous XR frame.
  • the PDCCH monitoring trigger indicator may be transmitted in reserved PDSCH resources of the PDSCH communication.
  • the PDCCH monitoring trigger indicator may indicate a time point (e.g., an exact time point) at which the UE 120 is to resume PDCCH monitoring.
  • the UE 120 may receive the PDCCH monitoring trigger when the UE 120 decodes the PDSCH communication associated with the XR frame, prior to entering the PDCCH skipping mode. The UE 120 may then resume PDCCH monitoring (after refraining from PDCCH monitoring in the PDCCH skipping mode) at the time point indicated by the PDCCH monitoring trigger indicator.
  • the UE 120 may resume PDCCH monitoring. After refraining from PDCCH monitoring for a duration after receiving the XR frame (e.g., the data associated with the XR frame) while in the PDCCH skipping mode, the UE 120 may exit the PDCCH skipping mode and resume monitoring for upcoming PDCCH communications. In a case in which the UE 120 does not receive the indication (e.g., the LP-WUS or the PDCCH monitoring trigger indicator) to trigger PDCCH monitoring prior to the end of the PDCCH skipping duration, the UE 120 may resume PDCCH monitoring after the configured PDCCH skipping duration.
  • the indication e.g., the LP-WUS or the PDCCH monitoring trigger indicator
  • the UE 120 may resume PDCCH monitoring prior to the end of the configured PDCCH skipping duration.
  • the indication e.g., the LP-WUS or the PDCCH monitoring trigger indicator
  • the UE 120 may resume PDCCH monitoring prior to the end of the configured PDCCH skipping duration.
  • the configured PDCCH skipping duration which may be determined as a longest interval between adjacent XR frames based at least in part on the XR frame rate and the jitter range, may be a default duration for refraining from PDCCH monitoring between XR frames, and the UE 120 may refrain from PDCCH monitoring for this default duration unless the UE 120 receives an indication (e.g., the LP-WUS or the PDCCH monitoring trigger indicator) that triggers the UE 120 to resume PDCCH monitoring prior to the end of the default duration.
  • the UE 120 may perform PDCCH skipping with an adaptive duration between XR frames such that excessive PDCCH monitoring is reduced without missing PDCCH communications.
  • UE power consumption may be reduced (e.g., by reducing excessive PDCCH monitoring) without increasing XR traffic latency (e.g., resulting from missed PDCCH communications) .
  • the UE 120 may receive a next XR frame.
  • the UE 120 may receive one or more downlink communications (e.g., a PDCCH communication and a PDSCH communication) associated with the next XR frame.
  • the UE 120 may receive the PDCCH communication associated with the next XR frame.
  • the PDCCH communication associated with the next frame may include (e.g., in DCI) scheduling information and/or other information for decoding the PDSCH communication associated with the next frame.
  • the UE 120 may receive and decode the PDSCH communication associated with the next frame, based at least in part on the information included (e.g., in the DCI) in the PDCCH communication, to obtain data for the next XR frame.
  • Fig. 7B shows an example 740 in which the network node 110 transmits an LP-WUS to trigger the UE 120 to resume PDCCH monitoring prior to the end of the configured PDCCH skipping duration.
  • the UE 120 may receive a first XR frame (shown as XR Frame 1 in Fig. 7B) .
  • the UE 120 may receive a PDCCH communication and a PDSCH communication associated with the first XR frame.
  • the PDSCH communication may include the data associated with the first XR frame.
  • the configured PDCCH skipping duration for the UE 120 may be determined as a maximum interval between adjacent XR frames based at least in part on the frame rate and the jitter range for the XR traffic.
  • the UE 120 may default to refraining from monitoring PDCCH for the configured PDCCH skipping duration, unless the UE 120 receives an LP-WUS that triggers the UE 120 to resume PDCCH monitoring prior to the end of the configured PDCCH skipping duration.
  • the network node 110 may transmit, to the UE 120, an LP-WUS to trigger the UE 120 to resume PDCCH monitoring.
  • the LP-WUS may trigger the UE 120 to resume PDCCH monitoring prior to the end of the configured PDCCH skipping duration.
  • the LP-WUS may be an indication that an arrival of a next XR frame (e.g., a second XR frame) is prior to an end of the configured PDCCH skipping duration.
  • the network node 110 may transmit the LP-WUS, and the UE 120 may receive the LP-WUS, while the UE 120 is in the PDCCH skipping mode.
  • the network node 110 may transmit the LP-WUS to the network node 110 when the next XR frame (e.g., the second XR frame) arrives at the network node 110 (e.g., when the next XR frame arrives in a buffer of the network node 110) to trigger the UE 120 to resume PDCCH monitoring to monitor for upcoming PDCCH/DCI for the next XR frame.
  • the network node 110 may transmit the LP-WUS to the UE 120 prior to transmitting the next XR frame to the UE 120.
  • the UE 120 may resume PDCCH monitoring based at least in part on receiving the LP-WUS.
  • the duration for which the UE 120 refrains from PDCCH monitoring while in the PDCCH skipping mode is based at least in part on when the UE 120 receives the LP-WUS.
  • the UE 120 may perform PDCCH monitoring to monitor for a PDCCH communication that includes DCI for scheduling/decoding the PDSCH associated with the second XR frame (shown in Fig. 7B as XR Frame 2) .
  • the UE 120 may receive the second XR frame.
  • the UE 120 may receive the PDCCH communication associated with the second XR frame, and the UE 120 may receive and decode the PDSCH communication associated with the second XR frame, based at least in part on the DCI in the PDCCH communication, to obtain the data for the second XR frame.
  • Fig. 7C shows an example 750 in which the network node 110 transmits a PDCCH monitoring trigger indicator in a PDSCH communication associated with an XR frame to trigger the UE 120 to resume PDCCH monitoring for a next XR frame prior to the end of the configured PDCCH skipping duration.
  • the UE 120 may receive a first XR frame (shown as XR Frame 1 in Fig. 7C) .
  • the UE 120 may receive a PDCCH communication and a PDSCH communication associated with the first XR frame.
  • the PDSCH communication associated with the first frame may include the data associated with the first XR frame.
  • the configured PDCCH skipping duration for the UE 120 may be determined as a maximum interval between adjacent XR frames based at least in part on the frame rate and the jitter range for the XR traffic.
  • the PDSCH communication associated with the first XR frame may include a PDCCH monitoring trigger indicator (also referred to as a “PDSCH piggyback indicator” ) that indicates when the UE 120 is to resume PDCCH monitoring for the next XR frame (after entering the PDCCH skipping mode in connection with receiving the PDSCH communication associated with the first XR frame) .
  • the PDCCH monitoring trigger indicator may indicate, to the UE 120, an exact time point at which the UE 120 is to resume PDCCH monitoring.
  • the PDCCH monitoring trigger indicator may indicate a time interval for PDCCH skipping (e.g., a time interval between the PDSCH communication associated with the first XR frame and the time point at which the UE 120 is to resume PDCCH monitoring for the next XR frame) .
  • the PDCCH monitoring trigger indicator may trigger the UE 120 to resume PDCCH monitoring at a time point associated with a possible arrival time of the next XR frame.
  • the PDCCH monitoring trigger indicator may trigger the UE 120 to start PDCCH monitoring for the next XR frame and a predicted (or expected) arrival time for the next XR frame minus a maximum jitter value in the jitter range.
  • the UE 120 may determine when to resume PDCCH monitoring for the next frame (e.g., the second frame) based at least in part on the PDCCH monitoring trigger indicator.
  • the UE 120 may enter the PDCCH skipping mode. While in the PDCCH skipping mode, the UE 120 may refrain from PDCCH monitoring. In some aspects, the UE 120 may remain in the PDCCH skipping mode (e.g., the UE 120 may refrain from PDCCH monitoring) for the time interval indicated by the PDCCH monitoring trigger indicator included in the PDSCH communication associated with the first XR frame. As shown by reference number 756, the UE 120 may resume PDCCH monitoring based at least in part on receiving the PDCCH monitoring trigger indicator.
  • the UE 120 may resume PDCCH monitoring for a second XR frame (shown as XR Frame 2 in Fig. 7C) after the time interval indicated by the PDCCH monitoring trigger indicator included in the PDSCH communication associated with the first XR frame.
  • the UE 120 may receive the second XR frame.
  • the UE 120 may receive the PDCCH communication associated with the second XR frame.
  • the UE 120 may then receive and decode the PDSCH communication associated with the second XR frame, based at least in part on the DCI in the PDCCH communication, to obtain the data for the second XR frame.
  • the UE 120 may be configured (or pre-configured) with a plurality of time intervals and respective index values for the plurality of time intervals, and the PDCCH monitoring trigger indicator included in the PDSCH communication (e.g., the PDSCH piggyback indicator) may indicate an index value corresponding to a time interval, of the plurality of time intervals.
  • the network node 110 may transmit, and the UE 120 may receive, a configuration of the plurality of time intervals and the respective index values.
  • the configuration of the plurality of time intervals and the respective index values may be included in the configuration information that indicates the configured PDCCH skipping duration for the UE 120 or another configuration transmitted to the UE 120 by the network node 110.
  • the configuration of the plurality of time intervals and the respective index values may be included in an RRC message or a MAC-CE.
  • multiple index values for the PDCCH monitoring trigger indicator may be encoded and configured for the UE 120 in a table.
  • the encoded table indicates a mapping between the index values (e.g., 0, 1, 2, 3, ...K) and the corresponding time intervals for PDCCH mapping (e.g., T0, T1, T2, T3, ...Tk) .
  • the PDCCH monitoring trigger indicator included in the PDSCH may convey only the index that corresponds to the time interval to be applied by the UE 120 for the PDCCH skipping.
  • the UE 120 may know the time interval to apply for PDCCH skipping when the UE 120 decodes the PDSCH communication including the PDCCH monitoring trigger indicator that indicates the index value. This may reduce signaling overhead as compared with the PDCCH monitoring trigger indicator conveying the exact time point information.
  • the codepoint (e.g., index value) to indicate the PDCCH skipping time interval is not limited to (e.g., may be greater than) 2 bits, so the PDCCH monitoring trigger indicator may map to a greater number of values than the DCI indication described in connection with Fig. 6.
  • the plurality of time intervals included in the table may include a minimum time interval, a maximum time interval, and time intervals separated by a step size between the minimum time interval and the maximum time interval.
  • the table of time intervals mapped to respective index values may include all possible time intervals separated by a certain step size in the range [4 slots, 29 slots] .
  • the step size may be configured for the UE 120.
  • the table may have multiple rows, with each row corresponding to a respective type of XR traffic frame rate. For example, because discrepant types of XR flows have different frame rates, the intervals for PDCCH skipping between the frames for different types of XR flows may be different.
  • Figs. 7A-7D illustrate operations for adaptive PDCCH monitoring for XR traffic.
  • the operations illustrated in Figs. 7A-7D and described above may be similarly performed for other types of application-specific traffic, such as traffic associated with a cloud-based application, a gaming application (e.g., cloud gaming traffic) , or a video application (e.g., video streaming traffic) , among other examples.
  • a gaming application e.g., cloud gaming traffic
  • a video application e.g., video streaming traffic
  • Figs. 7A-7D are provided as an example. Other examples may differ from what is described with respect to Figs. 7A-7D.
  • Fig. 8 is a diagram illustrating an example 800 associated with adaptive PDCCH monitoring for variable time intervals between adjacent XR frames, in accordance with the present disclosure.
  • example 800 includes communication between a network node 110 and a UE 120.
  • the network node 110 and the UE 120 may be included in a wireless network, such as wireless network 100.
  • the network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.
  • the UE 120 may be an XR UE associated with an XR application. That is, the UE 120 may be, include, or be included in an XR device (e.g., XR device 410) .
  • the network node 110 may communicate XR traffic between an XR server (e.g., XR server 405) and the XR UE (e.g., the UE 120) .
  • the network node 110 may receive uplink XR traffic from the XR UE and transmit the uplink XR traffic to the XR server, and the network node may receive downlink XR traffic from the XR server and transmit the downlink XR traffic to the XR UE.
  • the network node 110 may include, be included in, or be the XR server (e.g., XR server 405) .
  • the network node 110 may transmit, and the UE 120 may receive, an indication of a frame rate of XR traffic.
  • the network node 110 may know the frame rate for the XR traffic to be transmitted to the UE 120.
  • the network node 110 may store frame rates associated with one or more XR traffic flows, or the network node 110 may receive (e.g., from an XR server) an indication of the XR frame rate.
  • the network node 110 may determine a periodicity of the XR frames (e.g., an expected periodicity) based at least in part on the XR frame rate.
  • the network node 110 may transmit, to the UE 120, an indication of the frame rate for the XR traffic and/or the periodicity of the XR frames.
  • the network node 110 may indicate a configuration of the frame rate (or the periodicity of the XR frames) in an RRC message or a MAC-CE.
  • the UE 120 may determine a PDCCH skipping duration for refraining from PDCCH monitoring between XR frames based at least in part on the frame rate for the XR traffic and a jitter range of the XR traffic.
  • the jitter range of the XR traffic may be based at least in part on previous XR traffic arrival times and/or transmission times.
  • the jitter range may be specified in a wireless communication standard (e.g., a 3GPP standard) , and the UE 120 may be pre-configured with the jitter range.
  • the jitter range may be [-8 ms, 8 ms] based on a 5%tile and 95%tile truncated distribution of XR frame arrival times.
  • the UE 120 may autonomously determine the PDCCH skipping duration based at least in part on the indication of the XR frame rate received from the network node 110 and the jitter range. In some aspects, the UE 120 may determine the PDCCH skipping duration as a smallest interval between XR frames based at least in part on the frame rate for the XR traffic and the jitter range for the XR traffic. For example, the UE 120 may determine the PDCCH skipping duration as the expected interval between the XR frames (determined based on the XR frame rate) minus the maximum jitter in the jitter ranger.
  • the UE 120 may autonomously determine the PDCCH skipping duration (e.g., the time interval between when the UE 120 receives one XR frame and the UE 120 resumes PDCCH monitoring) as 8.67 ms (e.g., 16.67 –8 ms) .
  • the PDCCH skipping duration e.g., the time interval between when the UE 120 receives one XR frame and the UE 120 resumes PDCCH monitoring
  • the UE 120 may determine to resume PDCCH monitoring for the next XR frame at an earliest time point in the jitter range surrounding the expected reception time of the next XR frame (e.g., in the left margin of the max jitter of the next XR frame) .
  • the network node 110 may transmit, and the UE 120 may receive, one or more downlink communications associated with an XR frame.
  • the network node 110 may transmit an XR frame to the UE 120, and the UE 120 may receive the XR frame from the network node 110.
  • the transmission of the XR frame to the UE 120 may include one or more downlink communications.
  • the network node 110 may transmit, and the UE 120 may receive, a downlink communication that includes data associated with the XR frame.
  • the data associated with the XR frame may include XR data associated with a scene to be rendered/displayed in the XR frame.
  • the network node 110 may transmit, and the UE 120 may receive, a PDSCH communication that includes the data associated with the XR frame.
  • the network node 110 may also transmit, and the UE 120 may receive, a PDCCH communication associated with the XR frame.
  • the PDCCH communication may include DCI that indicates scheduling information for the PDSCH communication and/or other information for decoding the PDSCH communication.
  • the UE 120 may receive the PDCCH communication associated with the XR frame, and receive and decode the PDSCH communication scheduled by the PDCCH communication to obtain the data associated with the XR frame.
  • the UE 120 may refrain from PDCCH monitoring, in connection with receiving the XR frame (e.g., in connection with receiving the data associated with the XR frame) , for the PDCCH skipping duration determine by the UE 120.
  • the UE 120 may enter a PDCCH skipping mode after successfully receiving the data associated with an XR frame (e.g., after successfully receiving and decoding the PDSCH communication associated with the XR frame) .
  • the UE 120 may refrain from monitoring for PDCCH. That is, the UE 120 may skip monitoring for PDCCH in one or more PDCCH occasions that occur while the UE 120 is in the PDCCH skipping mode.
  • the UE 120 may remain in the PDCCH skipping mode for the PDCCH skipping duration determined by the UE 120 based at least in part on the XR frame rate and the jitter range. That is, by determining the PDCCH skipping duration, the UE 120 may autonomously determine when to resume PDCCH monitoring for the next XR frame based at least in part on the XR frame rate and the jitter range.
  • the UE 120 may resume PDCCH monitoring after the PDCCH skipping duration determined by the UE 120. After refraining from PDCCH monitoring for the PDCCH skipping duration after receiving the XR frame (e.g., the data associated with the XR frame) while in the PDCCH skipping mode, the UE 120 may exit the PDCCH skipping mode and resume monitoring for an upcoming PDCCH communication associated with the next XR frame.
  • the XR frame e.g., the data associated with the XR frame
  • the UE 120 may receive a next XR frame.
  • the UE 120 may receive one or more downlink communications (e.g., a PDCCH communication and a PDSCH communication) associated with the next XR frame.
  • the UE 120 may receive the PDCCH communication associated with the next XR frame.
  • the PDCCH communication associated with the next frame may include (e.g., in DCI) scheduling information and/or other information for decoding the PDSCH communication associated with the next frame.
  • the UE 120 may receive and decode the PDSCH communication associated with the next frame, based at least in part on the information included (e.g., in the DCI) in the PDCCH communication, to obtain data for the next XR frame.
  • the network node 110 may transmit, to the UE 120, an indication of a change to the frame rate for the XR traffic.
  • the indication of the change to the frame rate of the XR traffic may be included in DCI transmitted to the UE 120 (e.g., in a PDCCH communication while the UE 120 is monitoring for PDCCH) .
  • a DCI format may be enhanced to convey the indication of the change to the frame rate of the XR traffic.
  • the UE 120 may receive the indication of the change to the frame rate of the XR traffic, and the UE 120 may adjust the PDCCH skipping duration for refraining from PDCCH monitoring between XR frames based at least in part on the change to the frame rate for the XR traffic. For example, in connection with receiving an indication of an updated frame rate for the XR traffic, the UE 120 may determine an adjusted duration for PDCCH skipping between XR frames based at least in part on the updated frame rate and the jitter range. This may prevent unnecessary PDCCH monitoring when the frame rate is reduced, and thus reduce UE power consumption. Additionally, or alternatively, adjusting the PDCCH skipping duration may prevent DCI from being missed when the frame rate is increased, thus increasing reliability and reducing latency for XR traffic.
  • Fig. 8 illustrates operations for adaptive PDCCH monitoring for XR traffic.
  • the operations illustrated in Fig. 8 and described above may be similarly performed for other types of application-specific traffic, such as traffic associated with a cloud-based application, a gaming application (e.g., cloud gaming traffic) , or a video application (e.g., video streaming traffic) , among other examples.
  • a gaming application e.g., cloud gaming traffic
  • a video application e.g., video streaming traffic
  • Fig. 8 is provided as an example. Other examples may differ from what is described with respect to Fig. 8.
  • Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a UE, in accordance with the present disclosure.
  • Example process 900 is an example where the UE (e.g., UE 120) performs operations associated with adaptive PDCCH monitoring for variable time intervals between adjacent application-specific traffic frames.
  • process 900 may include receiving, from a network node, a configuration of a PDCCH skipping duration that is based at least in part on a frame rate for application-specific traffic and a jitter range of the application-specific traffic (block 910) .
  • the UE e.g., using communication manager 140 and/or reception component 1202, depicted in Fig. 12
  • process 900 may include receiving, from the network node, data associated with a frame of the application-specific traffic (block 920) .
  • the UE e.g., using communication manager 140 and/or reception component 1202, depicted in Fig. 12
  • process 900 may include refraining from PDCCH monitoring, in connection with receiving the data associated with the frame, for the PDCCH skipping duration or a duration based at least in part on an indication that an arrival of a next frame of the application-specific traffic is prior to an end of the PDCCH skipping duration (block 930) .
  • the UE e.g., using communication manager 140 and/or PDCCH skipping component 1208, depicted in Fig.
  • PDCCH skipping duration may refrain from PDCCH monitoring, in connection with receiving the data associated with the frame, for the PDCCH skipping duration or a duration based at least in part on an indication that an arrival of a next frame of the application-specific traffic is prior to an end of the PDCCH skipping duration, as described above.
  • Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • the application-specific traffic is XR traffic, traffic associated with a cloud-based application, traffic associated with a gaming application, or video traffic.
  • process 900 includes resuming PDCCH monitoring after the PDCCH skipping duration, or resuming PDCCH monitoring prior to the end of the PDCCH skipping duration based at least in part on receiving the indication that the arrival of the next frame is prior to the end of the PDCCH skipping duration.
  • process 900 includes receiving a PDCCH communication associated with the next frame based at least in part on resuming PDCCH monitoring.
  • the PDCCH skipping duration is a longest interval between frames of the application-specific traffic based at least in part on the frame rate for the application-specific traffic and the jitter range for the application-specific traffic.
  • process 900 includes receiving, from the network node, the indication that the arrival of the next frame is prior to the end of the PDCCH skipping duration.
  • receiving the indication that the arrival of the next frame is prior to the end of the PDCCH skipping duration includes receiving, during the PDCCH skipping duration, an LP-WUS for triggering the UE to resume PDCCH monitoring.
  • process 900 includes resuming PDCCH monitoring prior to the end of the PDCCH skipping duration based at least in part on receiving the LP-WUS.
  • receiving the data associated with the frame includes receiving a PDSCH communication associated with the frame
  • receiving the indication that the arrival of the next frame is prior to the end of the PDCCH skipping duration includes receiving, in the PDSCH communication associated with the frame, a PDCCH monitoring trigger indicator that indicates when to resume PDCCH monitoring for the next frame.
  • process 900 includes resuming PDCCH monitoring prior to the end of the PDCCH skipping duration based at least in part on the PDCCH monitoring trigger indicator.
  • process 900 includes receiving a configuration of a plurality of time intervals and respective index values for the plurality of time intervals, wherein the PDCCH monitoring trigger indicator indicates an index value corresponding to a time interval, of the plurality of time intervals, between the PDSCH communication associated with the frame and a time at which the UE is to resume PDCCH monitoring for the next frame.
  • the plurality of time intervals includes a minimum time interval, a maximum time interval, and time intervals separated by a step size between the minimum time interval and the maximum time interval.
  • process 900 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 9. Additionally, or alternatively, two or more of the blocks of process 900 may be performed in parallel.
  • Fig. 10 is a diagram illustrating an example process 1000 performed, for example, by a UE, in accordance with the present disclosure.
  • Example process 1000 is an example where the UE (e.g., UE 120) performs operations associated with adaptive PDCCH monitoring for variable time intervals between adjacent application-specific traffic frames.
  • process 1000 may include receiving, from a network node, an indication of a frame rate for application-specific traffic (block 1010) .
  • the UE e.g., using communication manager 140 and/or reception component 1202, depicted in Fig. 12
  • process 1000 may include receiving, from the network node, data associated with a frame of the application-specific traffic (block 1020) .
  • the UE e.g., using communication manager 140 and/or reception component 1202, depicted in Fig. 12
  • process 1000 may include refraining from PDCCH monitoring, after receiving the data associated with the frame, for a duration determined based at least in part on the frame rate for the application-specific traffic and a jitter range for the application-specific traffic (block 1030) .
  • the UE e.g., using communication manager 140 and/or PDCCH skipping component 1208, depicted in Fig. 12
  • Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • the application-specific traffic is XR traffic, traffic associated with a cloud-based application, traffic associated with a gaming application, or video traffic.
  • process 1000 includes resuming PDCCH monitoring after the duration determined based at least in part on the frame rate for the application-specific traffic and a jitter range for the application-specific traffic.
  • process 1000 includes receiving a PDCCH communication associated with a next frame of the application-specific traffic based at least in part on resuming PDCCH monitoring.
  • the duration is a smallest interval between frames of the application-specific traffic based at least in part on the frame rate for the application-specific traffic and the jitter range for the application-specific traffic.
  • the indication of a frame rate for application-specific traffic is included in an RRC message or a MAC-CE.
  • process 1000 includes receiving an indication of a change to the frame rate for the application-specific traffic, and adjusting the duration for refraining from PDCCH monitoring based at least in part on the change to the frame rate for the application-specific traffic.
  • the indication of the change to the frame rate of the application-specific traffic is included in DCI.
  • process 1000 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 10. Additionally, or alternatively, two or more of the blocks of process 1000 may be performed in parallel.
  • Fig. 11 is a diagram illustrating an example process 1100 performed, for example, by a network node, in accordance with the present disclosure.
  • Example process 1100 is an example where the network node (e.g., network node 110) performs operations associated with adaptive PDCCH monitoring for variable time intervals between adjacent application-specific traffic frames.
  • the network node e.g., network node 110
  • process 1100 may include transmitting, to a UE, a configuration of a PDCCH skipping duration that is based at least in part on a frame rate for application-specific traffic and a jitter range of the application-specific traffic (block 1110) .
  • the network node e.g., using communication manager 150 and/or transmission component 1304, depicted in Fig. 13
  • process 1100 may include transmitting, to the UE, data associated with a frame of the application-specific traffic (block 1120) .
  • the network node e.g., using communication manager 150 and/or transmission component 1304, depicted in Fig. 13
  • process 1100 may include transmitting, to the UE, an indication to trigger PDCCH monitoring prior to an end of the PDCCH skipping duration after reception, by the UE, of the frame, based at least in part on a determination that a PDCCH communication for a XR frame of the application-specific traffic is to be transmitted prior to an end of the PDCCH skipping duration (block 1130) .
  • the network node e.g., using communication manager 150 and/or transmission component 1304, depicted in Fig.
  • the UE 13) may transmit, to the UE, an indication to trigger PDCCH monitoring prior to an end of the PDCCH skipping duration after reception, by the UE, of the frame, based at least in part on a determination that a PDCCH communication for a next frame of the application-specific traffic is to be transmitted prior to an end of the PDCCH skipping duration, as described above.
  • Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • the application-specific traffic is XR traffic, traffic associated with a cloud-based application, traffic associated with a gaming application, or video traffic.
  • process 1100 includes transmitting, to the UE, the PDCCH communication associated with the next frame prior to the end of the PDCCH skipping duration after reception, by the UE, of the frame.
  • the PDCCH skipping duration is a longest interval between frames of the application-specific traffic based at least in part on the frame rate for the application-specific traffic and the jitter range for the application-specific traffic.
  • transmitting the indication to trigger PDCCH monitoring prior to an end of the PDCCH skipping duration includes transmitting, during the PDCCH skipping duration, an LP-WUS for triggering the UE to resume PDCCH monitoring.
  • transmitting the data associated with the frame includes transmitting a PDSCH communication associated with the frame, and transmitting the indication to trigger PDCCH monitoring prior to an end of the PDCCH skipping duration includes transmitting, in the PDSCH communication associated with the frame, a PDCCH monitoring trigger indicator that indicates when to resume PDCCH monitoring for the next frame.
  • process 1100 includes transmitting a configuration of a plurality of time intervals and respective index values for the plurality of time intervals, wherein the PDCCH monitoring trigger indicator indicates an index value corresponding to a time interval, of the plurality of time intervals, between the PDSCH communication associated with the frame and a time at which the UE is to resume PDCCH monitoring for the next frame.
  • the plurality of time intervals includes a minimum time interval, a maximum time interval, and time intervals separated by a step size between the minimum time interval and the maximum time interval.
  • process 1100 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 11. Additionally, or alternatively, two or more of the blocks of process 1100 may be performed in parallel.
  • Fig. 12 is a diagram of an example apparatus 1200 for wireless communication, in accordance with the present disclosure.
  • the apparatus 1200 may be a UE, or a UE may include the apparatus 1200.
  • the apparatus 1200 includes a reception component 1202 and a transmission component 1204, which may be in communication with one another (for example, via one or more buses and/or one or more other components) .
  • the apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using the reception component 1202 and the transmission component 1204.
  • the apparatus 1200 may include the communication manager 140.
  • the communication manager 140 may include one or more of a PDCCH skipping component 1208 and/or a PDCCH monitoring component 1210, among other examples.
  • the apparatus 1200 may be configured to perform one or more operations described herein in connection with Figs. 7A-7D and 8. Additionally, or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as process 900 of Fig. 9, process 1000 of Fig. 10, or a combination thereof.
  • the apparatus 1200 and/or one or more components shown in Fig. 12 may include one or more components of the UE described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 12 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.
  • the reception component 1202 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1206.
  • the reception component 1202 may provide received communications to one or more other components of the apparatus 1200.
  • the reception component 1202 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components of the apparatus 1200.
  • the reception component 1202 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2.
  • the transmission component 1204 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1206.
  • one or more other components of the apparatus 1200 may generate communications and may provide the generated communications to the transmission component 1204 for transmission to the apparatus 1206.
  • the transmission component 1204 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 1206.
  • the transmission component 1204 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2. In some aspects, the transmission component 1204 may be co-located with the reception component 1202 in a transceiver.
  • the reception component 1202 may receive, from a network node, a configuration of a PDCCH skipping duration that is based at least in part on a frame rate for application-specific traffic and a jitter range of the application-specific traffic.
  • the reception component 1202 may receive, from the network node, data associated with a frame of the application-specific traffic.
  • the PDCCH skipping component 1208 may refrain from PDCCH monitoring, in connection with receiving the data associated with the frame, for the PDCCH skipping duration or a duration based at least in part on an indication that an arrival of a next frame of the application-specific traffic is prior to an end of the PDCCH skipping duration.
  • the PDCCH monitoring component 1210 may resume PDCCH monitoring after the PDCCH skipping duration.
  • the PDCCH monitoring component 1210 may resume PDCCH monitoring prior to the end of the PDCCH skipping duration based at least in part on receiving the indication that the arrival of the next frame is prior to the end of the PDCCH skipping duration.
  • the reception component 1202 may receive a PDCCH communication associated with the next frame based at least in part on resuming PDCCH monitoring.
  • the reception component 1202 may receive, from the network node, the indication that the arrival of the next frame is prior to the end of the PDCCH skipping duration.
  • the PDCCH monitoring component 1210 may resume PDCCH monitoring prior to the end of the PDCCH skipping duration based at least in part on receiving the LP-WUS.
  • the PDCCH monitoring component 1210 may resume PDCCH monitoring prior to the end of the PDCCH skipping duration based at least in part on the PDCCH monitoring trigger indicator.
  • the reception component 1202 may receive a configuration of a plurality of time intervals and respective index values for the plurality of time intervals, wherein the PDCCH monitoring trigger indicator indicates an index value corresponding to a time interval, of the plurality of time intervals, between the PDSCH communication associated with the frame and a time at which the UE is to resume PDCCH monitoring for the next frame.
  • the reception component 1202 may receive, from a network node, an indication of a frame rate for application-specific traffic.
  • the reception component 1202 may receive, from the network node, data associated with a frame of the application-specific traffic.
  • the PDCCH skipping component 1208 may refrain from PDCCH monitoring, after receiving the data associated with the frame, for a duration determined based at least in part on the frame rate for the application-specific traffic and a jitter range for the application-specific traffic.
  • the PDCCH skipping component 1208 may determine the duration for refraining from PDCCH monitoring based at least in part on the frame rate for the application-specific traffic and the jitter ranger for the application-specific traffic.
  • the PDCCH monitoring component 1210 may resume PDCCH monitoring after the duration determined based at least in part on the frame rate for the application-specific traffic and a jitter range for the application-specific traffic.
  • the reception component 1202 may receive a PDCCH communication associated with a next frame of the application-specific traffic based at least in part on resuming PDCCH monitoring.
  • the reception component 1202 may receive an indication of a change to the frame rate for the application-specific traffic.
  • the PDCCH skipping component 1208 may adjust the duration for refraining from PDCCH monitoring based at least in part on the change to the frame rate for the application-specific traffic.
  • Fig. 12 The number and arrangement of components shown in Fig. 12 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 12. Furthermore, two or more components shown in Fig. 12 may be implemented within a single component, or a single component shown in Fig. 12 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 12 may perform one or more functions described as being performed by another set of components shown in Fig. 12.
  • Fig. 13 is a diagram of an example apparatus 1300 for wireless communication, in accordance with the present disclosure.
  • the apparatus 1300 may be a network node, or a network node may include the apparatus 1300.
  • the apparatus 1300 includes a reception component 1302 and a transmission component 1304, which may be in communication with one another (for example, via one or more buses and/or one or more other components) .
  • the apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using the reception component 1302 and the transmission component 1304.
  • the apparatus 1300 may include the communication manager 150.
  • the communication manager 150 may include a determination component 1308, among other examples.
  • the apparatus 1300 may be configured to perform one or more operations described herein in connection with Figs. 7A-7D and 8. Additionally, or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as process 1100 of Fig. 11, or a combination thereof.
  • the apparatus 1300 and/or one or more components shown in Fig. 13 may include one or more components of the network node described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 13 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory.
  • a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.
  • the reception component 1302 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1306.
  • the reception component 1302 may provide received communications to one or more other components of the apparatus 1300.
  • the reception component 1302 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components of the apparatus 1300.
  • the reception component 1302 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the network node described in connection with Fig. 2.
  • the transmission component 1304 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1306.
  • one or more other components of the apparatus 1300 may generate communications and may provide the generated communications to the transmission component 1304 for transmission to the apparatus 1306.
  • the transmission component 1304 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 1306.
  • the transmission component 1304 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the network node described in connection with Fig. 2. In some aspects, the transmission component 1304 may be co-located with the reception component 1302 in a transceiver.
  • the transmission component 1304 may transmit, to a UE, a configuration of a PDCCH skipping duration that is based at least in part on a frame rate for application-specific traffic and a jitter range of the application-specific traffic.
  • the transmission component 1304 may transmit, to the UE, data associated with a frame of the application-specific traffic.
  • the transmission component 1304 may transmit, to the UE, an indication to trigger PDCCH monitoring prior to an end of the PDCCH skipping duration after reception, by the UE, of the frame, based at least in part on a determination that a PDCCH communication for a next frame of the application-specific traffic is to be transmitted prior to an end of the PDCCH skipping duration.
  • the determination component 1308 may determine the PDCCH skipping duration based at least in part on the frame rate for the application-specific traffic and the jitter range of the application-specific traffic.
  • the transmission component 1304 may transmit, to the UE, the PDCCH communication associated with the next frame prior to the end of the PDCCH skipping duration after reception, by the UE, of the frame.
  • the transmission component 1304 may transmit a configuration of a plurality of time intervals and respective index values for the plurality of time intervals, wherein the PDCCH monitoring trigger indicator indicates an index value corresponding to a time interval, of the plurality of time intervals, between the PDSCH communication associated with the frame and a time at which the UE is to resume PDCCH monitoring for the next frame.
  • the transmission component 1304 may transmit, to a UE, an indication of a frame rate for application-specific traffic.
  • the transmission component 1304 may transmit, to the UE, an indication of a change to the frame rate for the application-specific traffic.
  • Fig. 13 The number and arrangement of components shown in Fig. 13 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 13. Furthermore, two or more components shown in Fig. 13 may be implemented within a single component, or a single component shown in Fig. 13 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 13 may perform one or more functions described as being performed by another set of components shown in Fig. 13.
  • a method of wireless communication performed by a user equipment (UE) comprising: receiving, from a network node, a configuration of a physical downlink control channel (PDCCH) skipping duration that is based at least in part on a frame rate for application-specific traffic and a jitter range of the application-specific traffic; receiving, from the network node, data associated with a frame of the application-specific traffic; and refraining from PDCCH monitoring, in connection with receiving the data associated with the frame, for the PDCCH skipping duration or a duration based at least in part on an indication that an arrival of a next frame of the application-specific traffic is prior to an end of the PDCCH skipping duration.
  • PDCCH physical downlink control channel
  • Aspect 2 The method of Aspect 1, wherein the application-specific traffic is extended reality (XR) traffic, traffic associated with a cloud-based application, traffic associated with a gaming application, or video traffic.
  • XR extended reality
  • Aspect 3 The method of any of Aspects 1-2, further comprising: resuming PDCCH monitoring after the PDCCH skipping duration; or resuming PDCCH monitoring prior to the end of the PDCCH skipping duration based at least in part on receiving the indication that the arrival of the next frame is prior to the end of the PDCCH skipping duration.
  • Aspect 4 The method of Aspect 3, further comprising: receiving a PDCCH communication associated with the next frame based at least in part on resuming PDCCH monitoring.
  • Aspect 5 The method of any of Aspects 1-4, wherein the PDCCH skipping duration is a longest interval between frames of the application-specific traffic based at least in part on the frame rate for the application-specific traffic and the jitter range for the application-specific traffic.
  • Aspect 6 The method of any of Aspects 1-5, further comprising: receiving, from the network node, the indication that the arrival of the next frame is prior to the end of the PDCCH skipping duration.
  • Aspect 7 The method of Aspect 6, wherein receiving the indication that the arrival of the next frame is prior to the end of the PDCCH skipping duration comprises: receiving, during the PDCCH skipping duration, a low power wake-up signal (LP-WUS) for triggering the UE to resume PDCCH monitoring.
  • LP-WUS low power wake-up signal
  • Aspect 8 The method of Aspect 7, further comprising: resuming PDCCH monitoring prior to the end of the PDCCH skipping duration based at least in part on receiving the LP-WUS.
  • Aspect 9 The method of Aspect 6, wherein receiving the data associated with the frame comprises receiving a physical downlink shared channel (PDSCH) communication associated with the frame, and wherein receiving the indication that the arrival of the next frame is prior to the end of the PDCCH skipping duration comprises: receiving, in the PDSCH communication associated with the frame, a PDCCH monitoring trigger indicator that indicates when to resume PDCCH monitoring for the next frame.
  • PDSCH physical downlink shared channel
  • Aspect 10 The method of Aspect 9, further comprising: resuming PDCCH monitoring prior to the end of the PDCCH skipping duration based at least in part on the PDCCH monitoring trigger indicator.
  • Aspect 11 The method of any of Aspects 9-10, further comprising: receiving a configuration of a plurality of time intervals and respective index values for the plurality of time intervals, wherein the PDCCH monitoring trigger indicator indicates an index value corresponding to a time interval, of the plurality of time intervals, between the PDSCH communication associated with the frame and a time at which the UE is to resume PDCCH monitoring for the next frame.
  • Aspect 12 The method of Aspect 11, wherein the plurality of time intervals includes a minimum time interval, a maximum time interval, and time intervals separated by a step size between the minimum time interval and the maximum time interval.
  • a method of wireless communication performed by a user equipment (UE) comprising: receiving, from a network node, an indication of a frame rate for application-specific traffic; receiving, from the network node, data associated with a frame of the application-specific traffic; and refraining from physical downlink control channel (PDCCH) monitoring, after receiving the data associated with the frame, for a duration determined based at least in part on the frame rate for the application-specific traffic and a jitter range for the application-specific traffic.
  • PDCCH physical downlink control channel
  • Aspect 14 The method of Aspect 13, wherein the application-specific traffic is extended reality (XR) traffic, traffic associated with a cloud-based application, traffic associated with a gaming application, or video traffic.
  • XR extended reality
  • Aspect 15 The method of any of Aspects 13-14, further comprising: resuming PDCCH monitoring after the duration determined based at least in part on the frame rate for the application-specific traffic and a jitter range for the application-specific traffic.
  • Aspect 16 The method of Aspect 15, further comprising: receiving a PDCCH communication associated with a next frame of the application-specific traffic based at least in part on resuming PDCCH monitoring.
  • Aspect 17 The method of any of Aspects 13-16, wherein the duration is a smallest interval between frames of the application-specific traffic based at least in part on the frame rate for the application-specific traffic and the jitter range for the application-specific traffic.
  • Aspect 18 The method of any of Aspects 13-17, wherein the indication of a frame rate for application-specific traffic is included in a radio resource control (RRC) message or a medium access control (MAC) control element (MAC-CE) .
  • RRC radio resource control
  • MAC-CE medium access control control element
  • Aspect 19 The method of any of Aspects 13-18, further comprising: receiving an indication of a change to the frame rate for the application-specific traffic; and adjusting the duration for refraining from PDCCH monitoring based at least in part on the change to the frame rate for the application-specific traffic.
  • Aspect 20 The method of Aspect 19, wherein the indication of the change to the frame rate of the application-specific traffic is included in downlink control information (DCI) .
  • DCI downlink control information
  • a method of wireless communication performed by a network node comprising: transmitting, to a user equipment (UE) , a configuration of a physical downlink control channel (PDCCH) skipping duration that is based at least in part on a frame rate for application-specific traffic and a jitter range of the application-specific traffic; transmitting, to the UE, data associated with a frame of the application-specific traffic; and transmitting, to the UE, an indication to trigger PDCCH monitoring prior to an end of the PDCCH skipping duration after reception, by the UE, of the frame, based at least in part on a determination that a PDCCH communication for a next frame of the application-specific traffic is to be transmitted prior to an end of the PDCCH skipping duration.
  • PDCCH physical downlink control channel
  • Aspect 22 The method of Aspect 21, wherein the application-specific traffic is extended reality (XR) traffic, traffic associated with a cloud-based application, traffic associated with a gaming application, or video traffic.
  • XR extended reality
  • Aspect 23 The method of any of Aspects 21-22, further comprising: transmitting, to the UE, the PDCCH communication associated with the next frame prior to the end of the PDCCH skipping duration after reception, by the UE, of the frame.
  • Aspect 24 The method of any of Aspects 21-23, wherein the PDCCH skipping duration is a longest interval between frames of the application-specific traffic based at least in part on the frame rate for the application-specific traffic and the jitter range for the application-specific traffic.
  • Aspect 25 The method of any of Aspects 21-24, wherein transmitting the indication to trigger PDCCH monitoring prior to an end of the PDCCH skipping duration comprises: transmitting, during the PDCCH skipping duration, a low power wake-up signal (LP-WUS) for triggering the UE to resume PDCCH monitoring.
  • LP-WUS low power wake-up signal
  • Aspect 26 The method of any of Aspects 21-24, wherein transmitting the data associated with the frame comprises transmitting a physical downlink shared channel (PDSCH) communication associated with the frame, and wherein transmitting the indication to trigger PDCCH monitoring prior to an end of the PDCCH skipping duration comprises: transmitting, in the PDSCH communication associated with the frame, a PDCCH monitoring trigger indicator that indicates when to resume PDCCH monitoring for the next frame.
  • PDSCH physical downlink shared channel
  • Aspect 27 The method of Aspect 26, further comprising: transmitting a configuration of a plurality of time intervals and respective index values for the plurality of time intervals, wherein the PDCCH monitoring trigger indicator indicates an index value corresponding to a time interval, of the plurality of time intervals, between the PDSCH communication associated with the frame and a time at which the UE is to resume PDCCH monitoring for the next frame.
  • Aspect 28 The method of Aspect 27, wherein the plurality of time intervals includes a minimum time interval, a maximum time interval, and time intervals separated by a step size between the minimum time interval and the maximum time interval.
  • Aspect 29 An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-28.
  • Aspect 30 A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-28.
  • Aspect 31 An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-28.
  • Aspect 32 A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-28.
  • Aspect 33 A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-28.
  • the term “component” is intended to be broadly construed as hardware and/or a combination of hardware and software.
  • “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and/or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • a “processor” is implemented in hardware and/or a combination of hardware and software. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware and/or a combination of hardware and software.
  • satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.
  • “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (e.g., a + a, a + a + a, a + a + b, a +a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c) .
  • the terms “has, ” “have, ” “having, ” or the like are intended to be open-ended terms that do not limit an element that they modify (e.g., an element “having” A may also have B) .
  • the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
  • the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or, ” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of” ) .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon divers aspects, la présente divulgation porte sur le domaine des communications sans fil. Selon certains aspects, un équipement utilisateur (UE) peut recevoir, en provenance d'un nœud de réseau, une configuration d'une durée de saut de canal de commande de liaison descendante physique (PDCCH) qui est basée au moins en partie sur une fréquence de trame pour un trafic spécifique à une application et une plage de gigue du trafic spécifique à l'application. L'UE peut recevoir, en provenance du nœud de réseau, des données associées à une trame du trafic spécifique à l'application. L'UE peut s'abstenir de surveiller le PDCCH, en connexion avec la réception des données associées à la trame, pour la durée de saut du PDCCH ou une durée basée, au moins en partie, sur une indication selon laquelle une arrivée d'une trame suivante du trafic spécifique à une application précède une fin de la durée de saut du PDCCH. De nombreux autres aspects sont décrits.
PCT/CN2022/132754 2022-11-18 2022-11-18 Surveillance de canal de commande de liaison descendante physique adaptative pour intervalles de temps variables entre des trames de trafic spécifiques à une application adjacente Ceased WO2024103369A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/132754 WO2024103369A1 (fr) 2022-11-18 2022-11-18 Surveillance de canal de commande de liaison descendante physique adaptative pour intervalles de temps variables entre des trames de trafic spécifiques à une application adjacente

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/132754 WO2024103369A1 (fr) 2022-11-18 2022-11-18 Surveillance de canal de commande de liaison descendante physique adaptative pour intervalles de temps variables entre des trames de trafic spécifiques à une application adjacente

Publications (1)

Publication Number Publication Date
WO2024103369A1 true WO2024103369A1 (fr) 2024-05-23

Family

ID=91083595

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/132754 Ceased WO2024103369A1 (fr) 2022-11-18 2022-11-18 Surveillance de canal de commande de liaison descendante physique adaptative pour intervalles de temps variables entre des trames de trafic spécifiques à une application adjacente

Country Status (1)

Country Link
WO (1) WO2024103369A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021217344A1 (fr) * 2020-04-27 2021-11-04 Oppo广东移动通信有限公司 Procédé de surveillance de canal, dispositif électronique et support de stockage
WO2021253431A1 (fr) * 2020-06-19 2021-12-23 Oppo广东移动通信有限公司 Procédé et appareil de surveillance d'un canal physique de commande de liaison descendante (pdcch)
WO2022155595A1 (fr) * 2021-01-18 2022-07-21 Intel Corporation Économie d'énergie en temps actif améliorée pour dispositifs d'équipement utilisateur
CN115190500A (zh) * 2021-04-01 2022-10-14 维沃移动通信有限公司 传输处理方法、终端及网络侧设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021217344A1 (fr) * 2020-04-27 2021-11-04 Oppo广东移动通信有限公司 Procédé de surveillance de canal, dispositif électronique et support de stockage
WO2021253431A1 (fr) * 2020-06-19 2021-12-23 Oppo广东移动通信有限公司 Procédé et appareil de surveillance d'un canal physique de commande de liaison descendante (pdcch)
WO2022155595A1 (fr) * 2021-01-18 2022-07-21 Intel Corporation Économie d'énergie en temps actif améliorée pour dispositifs d'équipement utilisateur
CN115190500A (zh) * 2021-04-01 2022-10-14 维沃移动通信有限公司 传输处理方法、终端及网络侧设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE: "Discussion on Potential Techniques for UE Power Saving", 3GPP TSG RAN WG1 #99 R1-1911928, 9 November 2019 (2019-11-09), XP051823109 *

Similar Documents

Publication Publication Date Title
US20240251285A1 (en) Delay status reporting
WO2024035485A1 (fr) Intervalles de mesure conditionnels pour trafic critique de retard
US20250063000A1 (en) Protocol data unit (pdu) set discard based on pdu set importance
US20230354315A1 (en) Multiple channels within configured grant occasions
US20240056862A1 (en) Conditional measurement gaps for delay critical traffic
US20240015586A1 (en) Predictive adaptation for a wireless link
US20250141615A1 (en) Common timing advance group for multiple transmit receive point operation
EP4655971A1 (fr) Rapport d'état de retard
WO2024103369A1 (fr) Surveillance de canal de commande de liaison descendante physique adaptative pour intervalles de temps variables entre des trames de trafic spécifiques à une application adjacente
US12483922B2 (en) Dynamic distributed extended reality compute
US12471106B2 (en) Downlink control information scheduling multiple downlink or uplink communications
US12457607B2 (en) Multi-slot physical downlink control channel monitoring
US20240334429A1 (en) Transmission of packet via multiple configured grant configurations
US12452862B2 (en) Physical downlink control channel skipping based on an anchor and an indication
US20240154687A1 (en) Latency capability indication for network-controlled repeater
US20230353333A1 (en) Dynamic indications of modifications to a periodic resource grant
WO2025050240A1 (fr) Réservation d'occasion de transmission de liaison montante
WO2024207282A1 (fr) Commutation de bande
US20230379908A1 (en) Discontinuous reception enhancements for reduced physical downlink control channel monitoring and jitter handling
US20240106519A1 (en) Beam-level selection based at least in part on a throughput requirement
WO2024097503A2 (fr) Indication de capacité de latence pour répéteur commandé par réseau
WO2024211288A1 (fr) Transmission de paquet par l'intermédiaire de multiples configurations d'autorisation configurées
WO2024026185A1 (fr) Signal de réveil pour porteuses multiples
EP4516034A1 (fr) Indications dynamiques de modifications apportées à une autorisation de ressource périodique
WO2025038239A1 (fr) Rejet d'ensemble d'unités de données de protocole (pdu) sur la base d'une importance d'ensemble de pdu

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22965550

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22965550

Country of ref document: EP

Kind code of ref document: A1