Apparatus and method for semi-persistent scheduling for multi-stream XR communications

Abstract

Aspects of the present disclosure relate to a method for wireless communication, the method comprising: receiving a first downlink semi-persistent scheduling configuration through radio resource control signaling, where the first semi-persistent scheduling configuration comprises a set of identifiers, the set of identifiers identifies at least one other downlink semi-persistent scheduling configuration associated with the first downlink semi-persistent scheduling configuration. The user equipment may use a scheduling configuration to temporarily enable decoding of a semi-persistent scheduling opportunity associated with the opportunity of failure.

Description

[0001] CROSS REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 376,726, filed on September 22, 2022, entitled “DEVICE AND METHOD FOR SEMIPERSISTENT SCHEDULING FOR MULTI-FLOW XR COMMUNICATIONS,” the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to wireless communications, and more particularly, to devices and methods for efficient XR communications. Background Art

[0004] A wireless communication system may include one or more network communication devices, such as a base station, which may also be referred to as an eNodeB (eNB), a next generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UE) or other suitable terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers). Additionally, a wireless communication system may support wireless communication across various radio access technologies, including third generation (3G) radio access technologies, fourth generation (4G) radio access technologies, fifth generation (5G) radio access technologies, and other suitable radio access technologies above 5G (e.g., sixth generation (6G)).

[0005] Extended reality (XR) is an umbrella term for different types of reality. One type of extended reality is virtual reality (VR), which is a rendered version of a delivered visual and audio scene. The rendering is designed to mimic as naturally as possible the visual and audio sensory stimulation of the real world as the observer or user moves within the limits defined by the application. Virtual reality typically (but not necessarily) requires the user to wear a head-mounted display (HMD) to completely replace the user's field of view with simulated visual components, and to wear headphones to provide accompanying audio to the user. Some form of user head and motion tracking will usually be present in VR to allow the visual and audio components of the simulation to be updated in order to ensure that from the user's perspective, items and sound sources remain consistent with the user's movements. Additional ways to interact with the virtual reality simulation may be provided.

[0006] Augmented reality (AR) is an extended reality when a user is provided with additional information or artificially generated items or content superimposed on their current environment. Such additional information or content is typically visual and / or auditory, and their observation of their current environment can be direct, without intermediate sensing, processing and rendering, or indirect, where their perception of their environment is relayed via sensors and can be augmented or processed. Mixed reality (MR) is an advanced form of AR in which some virtual elements are inserted into the physical scene with the intention of providing the illusion that these elements are part of the real scene.

[0007] XR refers to all real-world and virtual environments and human-computer interactions generated by computer technology and wearable devices. It includes representative forms such as AR, MR, and VR, as well as areas inserted between them. The level of virtuality ranges from partial sensory input to fully immersive VR. A key aspect of XR is the expansion of human experience, especially experiences related to presence (represented by VR) and cognitive acquisition (represented by AR).

[0008] Many XR use cases are characterized by quasi-periodic traffic (with possible jitter), with high data rates in the downlink for video streaming, combined with frequent uplink transmissions for gesture and control updates and uplink video streaming. Both downlink and uplink traffic for XR are also characterized by relatively tight packet delay budgets (PDBs). Summary of the invention

[0009] The present disclosure relates to methods, apparatus, and systems that support configurations for XR communications and use the configurations to save power.

[0010] Some implementations of the methods and apparatus described herein may also include a UE for wireless communication, at least one processor coupled to at least one memory, and the at least one processor is configured to enable the UE to: receive a first downlink semi-persistent scheduling configuration via radio resource control signaling, wherein the first semi-persistent scheduling configuration includes a set of identifiers that identify at least one other downlink semi-persistent scheduling configuration associated with the first downlink semi-persistent scheduling configuration.

[0011] In some implementations of the methods and apparatus described herein, the processor is further configured to detect a failure to receive a physical downlink shared channel (PDSCH) transmission opportunity of a first semi-persistent scheduling configuration, and in response to the detected failure, for a predetermined time period, disable decoding of at least one PDSCH transmission on a semi-persistent scheduling transmission opportunity of at least one other downlink semi-persistent scheduling configuration identified by a set of identifiers.

[0012] The processor may also be configured to cause the UE to: enable decoding of a semi-persistently scheduled transmission opportunity of at least one other downlink semi-persistent scheduling configuration identified by the set of identifiers after a predetermined time period. The predetermined time period may be a next occurrence of a PDSCH transmission of the first semi-persistent scheduling configuration.

[0013] In an embodiment, the first semi-persistent scheduling configuration specifies a primary semi-persistent scheduling configuration and at least one secondary semi-persistent scheduling configuration, and the predetermined time period is the next occurrence of transmission of the primary semi-persistent scheduling configuration. The processor may also be configured to cause the UE to: for the predetermined time period, after detecting a failure of a PDSCH transmission opportunity of the primary semi-persistent scheduling configuration, de-enable decoding of all PDSCH transmission opportunities for at least one secondary semi-persistent scheduling configuration.

[0014] In an embodiment, the UE detects a failure to receive a PDSCH transmission opportunity when the device does not detect a PDSCH transmission at a semi-persistent transmission opportunity of a first semi-persistent scheduling configuration.

[0015] Each of the first semi-persistent scheduling configurations and at least one other downlink semi-persistent scheduling configuration associated with the first semi-persistent scheduling configuration can be used for mixed reality (XR) communications. Each semi-persistent scheduling configuration can be associated with a different sensing channel, and the different sensing channels can include a video channel and an audio channel.

[0016] In other embodiments, a processor for wireless communication includes at least one memory and a controller coupled to the at least one memory, the controller being configured so that the controller: receives a first downlink semi-persistent scheduling configuration through radio resource control signaling, wherein the first semi-persistent scheduling configuration includes a set of identifiers, the set of identifiers identifying at least one other downlink semi-persistent scheduling configuration associated with the first downlink semi-persistent scheduling configuration. The controller can also be configured in a manner similar to the processor of the UE described above.

[0017] In an embodiment, a method performed by a UE includes: receiving a first downlink semi-persistent scheduling configuration via radio resource control signaling, wherein the first semi-persistent scheduling configuration includes a set of identifiers, the set of identifiers identifying at least one other downlink semi-persistent scheduling configuration associated with the first downlink semi-persistent scheduling configuration. The method may also include: detecting a failure to receive a physical downlink shared channel (PDSCH) transmission opportunity of the first semi-persistent scheduling configuration; and in response to the detected failure, disabling decoding of at least one PDSCH transmission on a semi-persistent scheduling transmission opportunity of at least one other downlink semi-persistent scheduling configuration identified by the set of identifiers for a predetermined time period. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 An example of a wireless communication system supporting efficient XR communications according to aspects of the present disclosure is illustrated.

[0019] Figure 2 An example of a block diagram of a device supporting efficient XR communications according to aspects of the present disclosure is illustrated.

[0020] Figure 3 A flow chart of a method for supporting efficient XR communication according to aspects of the present disclosure is illustrated.

[0021] Figure 4 Illustrated are examples of SPS configuration information elements that support efficient XR communication according to aspects of the present disclosure.

[0022] Figure 5 Illustrated are examples of CG configuration information elements that support efficient XR communication according to aspects of the present disclosure.

[0023] Fig. 6A and Figure 6B An example of a relevant XR communication flow according to aspects of the present disclosure is illustrated.

[0024] Figure 7 A flow chart of a method for supporting efficient XR communication according to aspects of the present disclosure is illustrated.

[0025] Figure 8 An example of a block diagram of a processor that supports efficient XR communications according to aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0026] XR and related services are diverse, and the characteristics of data streams (e.g., video) may change "on the fly" while the services are running over New Radio (NR). Therefore, additional information about the running services from higher layers (e.g., QoS flow association, frame-level QoS, Application Data Unit (ADU)-based or Protocol Data Unit (PDU) set-based QoS, XR-specific QoS, etc.) may be beneficial to facilitate an informed choice of radio parameters. XR application sensing by UE and gNB can improve user experience, increase the ability of the NR system to support XR services, and reduce UE power consumption.

[0027] Connected-mode discontinuous reception (C-DRX) can be used to help XR devices save power and therefore operate for longer periods of time without being charged, or otherwise reduce overall energy consumption. However, XR traffic characteristics (such as non-integer traffic periodicity and jitter) may result in missed opportunities to schedule XR video frames within the on-duration of a DRX cycle. For example, a video frame may arrive after the on-duration and therefore be scheduled in the next DRX cycle, which in turn increases the associated latency. This increase in latency may be undesirable because XR packets delivered outside the delay budget may be useless.

[0028] For XR services, where the XR application has multiple flows with different traffic characteristics, semi-persistent scheduling (SPS) can be used to help schedule transmissions corresponding to different services in a timely manner when using a single DRX configuration. If a single DRX configuration matching one flow does not satisfy the PDBs of other flows, multiple simultaneous DRX configurations, each matching a traffic flow, are suitable for achieving both high UE power saving gains and many satisfied UEs. However, enabling multiple simultaneously active DRX configurations comes at the cost of higher complexity and also involves further enhancement and standardization work. On the other hand, providing SPS opportunities based on expected traffic arrivals can lead to system improvements.

[0029] Multimode XR applications typically have multiple interdependent streams with different business characteristics, for example, corresponding to different human senses (audio, video, tactile, etc.). These emerging XR services use synchronized parallel streams to reach users for an appropriate service experience. Due to their quasi-periodic nature, data for different streams of multimode XR applications can be mapped to different SPS configurations for the downlink (DL). According to the currently defined behavior, the UE attempts to decode the (multiple) PDSCHs on the SPS configuration, regardless of whether there is DL data on one of the SPS opportunities carrying data for other streams of the multimode application. Since the user can only enjoy the full experience when the UE receives data for all streams, there is limited value in further receiving data for the stream when data for one stream is not detected. For example, if only tactile data is available, but there is no video and audio data, the quality of experience is significantly reduced, and efficiency can be improved by not decoding tactile data without associated video and audio data.

[0030] An ADU is the smallest data unit that can be independently processed by an application (such as a process for processing out-of-order traffic data). A video frame can be an I frame, a P frame, or can be composed of I slices and / or P slices. I frames / I slices are more important and larger than P frames / P slices. An ADU can be one or more I slices, P slices, I frames, P frames, or a combination thereof. It should be noted that for the scope of the present disclosure, the term PDU set can be used interchangeably with the term ADU.

[0031] A service-oriented design that considers XR service characteristics (e.g., (a) variable packet arrival rate: packets arrive at 30 to 120 frames / second with some jitter, (b) packets have variable and large packet size, (c) B / P frames depend on I frames, and (d) the presence of multiple services / data streams in the uplink (such as gesture and video scenes)) can achieve more efficient XR service delivery by meeting XR service requirements for a larger number of UEs or by UE power saving.

[0032] The latency requirement of XR services on the RAN side (air interface) is modeled as a Packet Delay Budget (PDB). The PDB is a finite time budget for packets to be sent from the gNB to the UE over the air.

[0033] For a given packet, the delay of the packet over the air interface is measured from the time the packet arrives at the gNB to the time the packet is successfully delivered to the UE. If the delay is greater than a given PDB for the packet, the packet violates the PDB, otherwise the packet is considered successfully delivered. The value of the PDB may vary for different applications and traffic types, depending on the application, the value of the PDB may be 10 to 20 milliseconds, as explained in TR 26.926.

[0034] According to R1-2112245, the 5G arrival time of data bursts on the downlink can be quasi-periodic, i.e., with a period of jitter. Some of the factors that cause jitter in burst arrivals include varying server rendering time, encoder time, RTP packetization time, link between server and 5G gateway, etc. 3GPP agreed to use a truncated Gaussian distribution for the simulation assumption of XR evaluation model DL service arrival jitter, the truncated Gaussian distribution has a mean: 0ms, standard deviation: 2ms, range: [-4ms, 4ms] (baseline), [-5ms, 5ms] (optional).

[0035] An application may have certain delay requirements for the ADU, which may not be adequately translated into a packet delay budget requirement. For example, if the ADU delay budget (ADB) is 10ms, then the PDB can be set to 10ms only if all packets of the ADU arrive at the 5G system at the same time. If the packets are dispersed, then the ADU delay budget is measured based on the arrival of the first packet of the ADU or the last packet of the ADU. In either case, a given ADB will result in different PDB requirements for different packets of the ADU. It may be beneficial to specify an ADB for the 5G system.

[0036] If the scheduler and / or UE know the delay budget for a packet / ADU, the gNB can take this knowledge into account when scheduling transmissions, e.g., by giving priority to transmissions that are close to their delay budget limit instead of scheduling (e.g., UL) transmissions. The UE can also use such knowledge to determine: 1) whether UL transmissions corresponding to transmissions that exceed its delay budget can be discarded (e.g., PUCCH, UL gestures, or PUSCH in response to PDSCH), and further, without waiting for retransmissions of PDSCH or keeping erroneously received PDSCH in a buffer for soft combining if the retransmission will never occur, and 2) how much of its channel occupancy time can be shared with the gNB when using unlicensed spectrum.

[0037] 1) The remaining delay budget for DL ​​transmission may be indicated to the UE in the downlink control information (DCI) (e.g., for grouping of video frames / slices / ADUs) or via MAC-CE (e.g., for ADUs / video frames / slices), and 2) The remaining delay budget for UL transmission may be indicated to the gNB via UL transmissions (such as uplink control information (UCI), physical uplink shared channel (PUSCH) transmissions, etc.).

[0038] ADU-related QoS aspects of XR, such as ADU Error Rate (AER), ADU Delay Budget (ADB), and ADU Content Policy (referred to as ADP, which is the percentage of packets / bits of the ADU that are to be received in order to correctly decode the ADU), can be communicated to the RAN to optimize communications.

[0039] The present disclosure provides an embodiment of a solution for providing power saving gains for XR multimode applications. The concept of associated SPS configuration is introduced. Certain defined UE behaviors for receiving PDSCH on SPS timings of associated SPS configurations are detailed in the present disclosure. For example, in the case where no PDSCH transmission is detected on an SPS timing for one SPS configuration in an associated SPS configuration group, the UE can temporarily disable the reception of PDSCH for other SPS configurations in the associated SPS configuration group. This achieves some additional power saving gains and reduces the processor load, heat generation, etc. of the UE.

[0040] Aspects of the disclosure are described in the context of a wireless communication system.Aspects of the disclosure are also illustrated and described with reference to device diagrams and flow diagrams.

[0041] Figure 1 An example of a wireless communication system 100 that supports effective XR communication according to aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 102, one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technologies, including the Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communication system 100 may support radio access technologies above 5G. Additionally, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0042] One or more network entities 102 may be dispersed throughout a geographic area to form a wireless communication system 100. One or more network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN), a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next generation NodeB (gNB), or other suitable terms. The network entity 102 and the UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, the network entity 102 and the UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0043] The network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, the network entity 102 and the UE 104 may support wireless communications of signals associated with services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, the network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0044] One or more UEs 104 may be dispersed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device or a subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, a station, a terminal or a client, etc. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device or a Machine Type Communication (MTC) device, etc. In some implementations, UE 104 may be stationary in the wireless communication system 100. In some other implementations, UE 104 may be mobile in the wireless communication system 100.

[0045] One or more UEs 104 may be devices in different forms or with different capabilities. Figure 1 Some examples of UE 104 are illustrated in FIG. UE 104 may be able to communicate with various types of devices such as network entity 102, other UE 104, or network devices (e.g., core network 106, packet data network 108, relay device, integrated access and backhaul (IAB) node, or another network device), such as Figure 1 Additionally or alternatively, the UE 104 can support communications with other network entities 102 or UEs 104, which can act as relays in the wireless communication system 100.

[0046] The UE 104 may also support wireless communications directly with other UEs 104 via a communication link 114. For example, the UE 104 may support wireless communications directly with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, the UE 104 may support wireless communications directly with another UE 104 via a PC5 interface.

[0047] The network entity 102 may support communication with the core network 106, or with another network entity 102, or both. For example, the network entity 102 may be connected to the core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2 or another network interface). The network entities 102 may communicate with each other via the backhaul links 116 (e.g., via X2, Xn or another network interface). In some implementations, the network entities 102 may communicate with each other directly (e.g., between the network entities 102). In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106). In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as radio heads, smart radio heads, or transmission-reception points (TRPs).

[0048] In some implementations, the network entity 102 may be configured in a disaggregated architecture that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 102 may include one or more of the following: a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN intelligent controller (RIC) (e.g., a near real-time RIC (Near-RTRIC), a non-real-time RIC (Non-RT RIC)), a service management and orchestration (SMO) system, or any combination thereof.

[0049] The RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entity 102 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 102 may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0050] The functional split between CU, DU and RU can be flexible, and different functions can be supported depending on which functions are performed at the CU, DU or RU (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions and any combination thereof). For example, a functional split of a protocol stack can be adopted between the CU and the DU, so that the CU can support one or more layers of the protocol stack, and the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functions and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU can be connected to one or more DUs or RUs, and one or more DUs or RUs can host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, media access control (MAC) layer) functions and signaling, and each DU or RU can be at least partially controlled by the CU160.

[0051] Additionally or alternatively, a functional split of the protocol stack may be employed between the DU and the RU, such that the DU may support one or more layers of the protocol stack, and the RU may support one or more different layers of the protocol stack. The DU may support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and the DU or between the DU and the RU may be within the protocol layer (e.g., some functions for the protocol layer may be performed by one of the CU, DU, or RU, while other functions of the protocol layer may be performed by different ones of the CU, DU, or RU).

[0052] The CU may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU may be connected to one or more DUs via a mid-range communication link (e.g., F1, F1-c, F1-u), and the DU may be connected to one or more RUs via a front-haul communication link (e.g., an open front-haul (FH) interface). In some implementations, the mid-range communication link or the front-haul communication link may be implemented according to an interface (e.g., a channel) between layers of a protocol stack supported by a corresponding network entity 102 communicating via such a communication link.

[0053] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., mobility management entity (MME), access and mobility management function (AMF)) and user plane entities that route packets or interconnect with external networks (e.g., serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearer, signal bearer, etc.) for one or more UEs 104 served by one or more network entities 102 associated with the core network 106.

[0054] The core network 106 may communicate with the packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. The UE 104 may establish a session (e.g., a protocol data unit (PDU) session, etc.) with the core network 106 via the network entity 102. The core network 106 may use the established session (e.g., the established PDU session) to route traffic (e.g., control information, data, etc.) between the UE 104 and the application server 118. The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106).

[0055] In the wireless communication system 100, the network entity 102 and the UE 104 may use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, the network entity 102 and the UE 104 may support different resource structures. For example, the network entity 102 and the UE 104 may support different frame structures. In some implementations, such as in 4G, the network entity 102 and the UE 104 may support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, the network entity 102 and the UE 104 may support various frame structures (i.e., multiple frame structures). The network entity 102 and the UE 104 may support various frame structures based on one or more digital technologies.

[0056] One or more digital technologies may be supported in the wireless communication system 100, and the digital technologies may include subcarrier spacing and cyclic prefixes. A first digital technology (e.g., μ = 0) may be associated with a first subcarrier spacing (e.g., 15kHz) and a conventional cyclic prefix. In some implementations, a first digital technology (e.g., μ = 0) associated with a first subcarrier spacing (e.g., 15kHz) may utilize one time slot for each subframe. A second digital technology (e.g., μ = 1) may be associated with a second subcarrier spacing (e.g., 30kHz) and a conventional cyclic prefix. A third digital technology (e.g., μ = 2) may be associated with a third subcarrier spacing (e.g., 60kHz) and a conventional cyclic prefix or an extended cyclic prefix. A fourth digital technology (e.g., μ = 3) may be associated with a fourth subcarrier spacing (e.g., 120kHz) and a conventional cyclic prefix. A fifth digital technology (e.g., μ = 4) may be associated with a fifth subcarrier spacing (e.g., 240kHz) and a conventional cyclic prefix.

[0057] The time intervals of resources (e.g., communication resources) can be organized according to frames (also referred to as radio frames). Each frame can have a duration, for example, a duration of 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, a duration of 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0058] Additionally or alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., a certain number) of time slots. The number of time slots in each subframe may also depend on one or more digital technologies supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth digital technologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with the corresponding subcarrier spacings of 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz may utilize a single time slot for each subframe, two time slots for each subframe, four time slots for each subframe, eight time slots for each subframe, and 16 time slots for each subframe, respectively. Each time slot may include a certain number (e.g., a certain number) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots for a subframe may depend on the digital technology. For a conventional cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on the digital technology. It should be understood that references to a first digital technology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0059] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc. based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range representations FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some implementations, the network entity 102 and the UE 104 can perform wireless communications over the one or more operating frequency bands. In some implementations, FR1 can be used by the network entity 102 and the UE 104 and other devices or apparatuses for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by the network entity 102 and the UE 104 and other devices or apparatuses for short-range, high data rate capabilities.

[0060] FR1 may be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 may be associated with a first digital technology (e.g., μ=0) including a 15kHz subcarrier spacing, a second digital technology (e.g., μ=1) including a 30kHz subcarrier spacing, and a third digital technology (e.g., μ=2) including a 60kHz subcarrier spacing. FR2 may be associated with one or more digital technologies (e.g., at least 2 digital technologies). For example, FR2 may be associated with a third digital technology (e.g., μ=2) including a 60kHz subcarrier spacing, and a fourth digital technology (e.g., μ=3) including a 120kHz subcarrier spacing.

[0061] Figure 2 FIG. 2 illustrates a block diagram of a device 202 that supports efficient XR communication according to aspects of the present disclosure. Figure 2 The device 202 may be an example of a network entity 102 or a UE 104 as described herein. The device 202 may support wireless communications with one or more network entities 102, UEs 104, or any combination thereof. The device 202 may include components for bidirectional communication, including components for sending and receiving communications, such as a processor 204, a memory 206, a transceiver 208, and an I / O controller 210. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0062] The processor 204, memory 206, transceiver 208, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 204, memory 206, transceiver 208, or various combinations thereof, or components thereof may support methods for performing one or more operations described herein.

[0063] In some implementations, the processor 204, memory 206, transceiver 208, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of components configured as or otherwise supporting the functions described in the present disclosure. In some implementations, the processor 204 and the memory 206 coupled to the processor 204 may be configured to perform one or more functions described herein (e.g., execution of instructions stored in the memory 206 by the processor 204).

[0064] For example, processor 204 may support wireless communications at device 202 according to examples as disclosed herein. Processor 204 may be configured to or otherwise support efficient XR communications.

[0065] The processor 204 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 204 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 204. The processor 204 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 206) to cause the device 202 to perform various functions of the present disclosure.

[0066] The memory 206 may include random access memory (RAM) and read-only memory (ROM). The memory 206 may store computer-readable, computer-executable code including instructions that, when executed by the processor 204, cause the device 202 to perform various functions described herein. The code may be stored in a non-transient computer-readable medium (such as a system memory or other type of memory). In some implementations, the code may not be directly executable by the processor 204, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, the memory 206 may include a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0067] I / O controller 210 can manage input and output signals for device 202. I / O controller 210 can also manage peripheral devices that are not integrated into device 202. In some implementations, I / O controller 210 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 210 can utilize an operating system, such as

[0068] Or other known operating systems. In some implementations, I / O controller 210 can be implemented as part of a processor (such as processor M08). In some implementations, a user can interact with device 202 via I / O controller 210 or via hardware components controlled by I / O controller 210.

[0069] In some implementations, the device 202 may include a single antenna 212. However, in some other implementations, the device 202 may have more than one antenna 212 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be able to simultaneously send or receive multiple wireless transmissions. The transceiver 208 may communicate bidirectionally via one or more antennas 212, wired or wireless links as described herein. For example, the transceiver 208 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 208 may also include a modem to modulate packets, provide modulated packets to one or more antennas 212 for transmission, and demodulate packets received from one or more antennas 212.

[0070] Figure 3 A flow chart of a method 300 for supporting efficient XR communication according to aspects of the present disclosure is illustrated. The operations of the method 300 may be implemented by a device or components thereof as described herein. For example, elements of the method 300 may be performed by a network entity 102 or a UE 104, as described in reference to Figure 1 and Figure 2 In some implementations, a device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, a device may use dedicated hardware to perform aspects of the described functions.

[0071] At 305, the method may include receiving an SPS configuration. The operations of 305 may be performed according to examples as described herein. In some implementations, aspects of the operations of 305 may be performed as described in reference to Figure 1 The device described is used to perform the

[0072] In an embodiment, the SPS configuration is received using RRC control signaling by the UE 104. For example, the SPS configuration may be sent from a base station to one or more UEs as an information element on a control channel. Figure 4 An example of an information element (IE) that conveys an SPS configuration (SPS-Config) that supports efficient XR communication according to aspects of the present disclosure is illustrated.

[0073] like Figure 4 As illustrated in , the SPS configuration may indicate a set of associated SPS configurations. According to one implementation, the SPS configuration includes a new field that configures (if present) a list of identifiers that identify the associated SPS configurations. In one example, the network may configure the set of associated SPS configurations based on signaling information received from the core network (e.g., via a session management function (SMF)).

[0074] To efficiently support multimode applications, the application function (AF) may provide the policy control function (PCF) with the service flow coordination group ID and group level processing requirements. This information of associated service flows belonging to multimode XR applications may also be propagated to the RAN to allow the gNB scheduler to efficiently perform resource allocation tasks and admission control. According to one implementation, information of the associated SPS configuration (which may be derived from information of the associated service flows provided by the core network) is used by the UE 104 to further enhance power saving for XR applications and provide capacity gains.

[0075] In an embodiment, the SPS configuration comprises a group identifier, wherein the group identifier defines a group of associated SPS configurations.Each SPS configuration that is part of the group of associated SPS configurations has been configured with the same group identifier.

[0076] Additionally, the SPS configuration received at 305 may designate an SPS configuration in the set of associated SPS configurations as a primary SPS configuration and other SPS configurations in the set as secondary SPS configurations. The significance of these designations will be discussed in further detail below.

[0077] At 310, the method may include initiating XR communication based on the SPS configuration received at 305. The operations of 305 may be performed according to the examples described herein. In some implementations, aspects of the operations of 305 may be described in detail with reference to Figure 1 The device described is used to perform the

[0078] Fig. 6A An embodiment of XR communication using three different XR data streams is illustrated. The XR data streams may have different offsets, which are indicated in the SPS configuration element. Fig. 6A In the example, XR stream 1 has a first offset, XR stream 2 has a second offset greater than the first offset, and XR stream 3 has a third offset greater than the second offset. Each XR stream can transmit sensory data, such as video, audio, and tactile data, and each sensory data can have different parameters from at least one of the other XR service streams, such as QoS, packet size, periodicity, etc. Fig. 6A Each box in may represent one or more associated data packets, which may also be referred to as an SPS opportunity.

[0079] At 315, the method may include detecting a failure to successfully receive a PDSCH transmission opportunity. The operations of 315 may be performed according to examples as described herein. In some implementations, aspects of the operations of 315 may be performed as described in reference to Figure 1 The described device is used to perform

[0080] The UE 104 may detect a failure to successfully receive a PDSCH transmission opportunity by detecting no PDSCH signal at the time and frequency specified for the XR service flow. In other words, the UE 104 may detect a failure to receive a PDSCH transmission or SPS opportunity when the UE does not receive a PDSCH transmission at all, which may be the result of, for example, a transmission failure of a base station or a UE hardware failure.

[0081] In another embodiment, the UE may detect a failure to receive the PDSCH when the UE fails to successfully decode a PDSCH transmission within a PDB for the transmission. This may be caused, for example, when the radio environment is so noisy that the UE cannot successfully decode the transmission even after potential retransmission attempts. Thus, a failure to receive a PDSCH transmission opportunity may occur when the transmission is not received, or when the transmission is received but not successfully processed within the PDB.

[0082] At 320, the method may include: for a predetermined time, disabling decoding of the SPS opportunity, and at 325, enabling decoding of the SPS opportunity after the predetermined time. The operations of 320 and 325 may be performed according to examples as described herein. In some implementations, aspects of the operations of 320 and 325 may be performed as described in reference to Figure 1 The device described is used to perform the

[0083] According to an embodiment, when no PDSCH is detected on an SPS transmission opportunity associated with an SPS configuration, the UE 104 skips monitoring and / or decoding the PDSCH and / or PDCCH monitoring on the SPS transmission opportunity. For example, the UE 104 disables decoding of the SPS opportunity associated with the failed PDSCH transmission opportunity detected at 315. In an embodiment, when the UE 104 does not detect any PDSCH transmission on the previous SPS transmission opportunity associated with the SPS configuration, the UE 104 does not attempt to decode the PDSCH on the SPS transmission opportunity.

[0084] In an embodiment, at 320, disabling decoding of SPS opportunities includes temporarily disabling reception of data on an SPS configuration when the UE 104 does not detect downlink data transmission for an associated stream / SPS configuration, which may result in increased power savings for XR applications.

[0085] When different streams (logical channels (LCH) or data radio bearers (DRB)) of a multi-stream XR application (e.g., a multimode application) are mapped to different associated SPS configurations, when the UE 104 has not received any data on one of the SPS transmission opportunities of the associated SPS configuration group, the UE 104 may temporarily stop receiving data on other associated SPS configurations. For example, for a predetermined time, the processor 204 of the UE 104 may disable receiving / decoding of the SPS opportunity, the data of the SPS opportunity may not be stored in the memory 206, and / or the transceiver 208 may be disabled and not process the data of the SPS opportunity.

[0086] When data of one of the input signals of the multimode application has not been sent / received in the downlink, there is little or no benefit in receiving data of other input signals of the XR application. Instead, the UE 104 saves power even by not attempting to decode other data associated with the failed PDSCH transmission opportunity.

[0087] Figure 6B An embodiment of disabling decoding of SPS opportunities for a predetermined time at 320 is illustrated in FIG. Figure 6B In the embodiment shown in , UE 104 detects a failure to receive the first PDSCH transmission opportunity of XR stream 2. UE 104 then disables decoding of the associated SPS configurations (which are crossed out in the figure) of XR stream 1 and XR stream 3, and resumes decoding at the next SPS opportunity of XR stream 2. In various embodiments, the predetermined time may have different configurations.

[0088] In an embodiment, after UE 104 detects a failure to receive a PDSCH transmission opportunity of one SPS configuration in the associated SPS configuration group at 315, it does not decode the PDSCH and / or PDCCH on the SPS transmission opportunities of other associated SPS configurations in the associated SPS configuration group for a predetermined time. In one example, the predetermined time corresponds to an SPS cycle.

[0089] According to one embodiment, the UE 104 stops decoding the PDSCH and / or PDCCH on the SPS transmission occasions of other associated SPS configurations until the next SPS transmission occasion of the SPS configuration for which PDSCH reception failed. Figure 6B An example of such an embodiment is explained below.

[0090] like Figure 6B As can be seen in FIG. 1 , UE 104 fails to decode the PDSCH on the first SPS transmission opportunity of the second SPS configuration (XR-stream 2). This failure triggers UE 104 to stop monitoring the PDSCH and / or PDCCH of other associated SPS configurations. Figure 6BIn the example, the configuration includes a first SPS configuration corresponding to XR-stream 1 and a third SPS configuration corresponding to XR-stream 3. Figure 6B As shown in , UE 104 disables decoding of the SPS transmission opportunity of the first SPS configuration (XR-stream 1) and the next two SPS transmission opportunities of the third SPS configuration (XR-stream 3). At 325, UE 104 enables PDSCH and / or PDCCH decoding (applying traditional behavior) at the beginning of the second SPS transmission opportunity of the second SPS configuration (XR-stream 2).

[0091] In another embodiment, when a failure to receive a PDSCH opportunity is detected at 315, UE 104 disables decoding of the PDSCH and / or PDCCH opportunity on the next SPS transmission opportunity of the associated SPS configuration. In other words, one SPS transmission opportunity for each of the associated SPS configurations is disabled for PDSCH and / or PDCCH decoding. In such an embodiment, Figure 6B , after the first opportunity that XR stream 2 fails, the first opportunity of XR stream 3 and the second opportunity of XR stream 1 will be skipped, and decoding will be resumed for the second opportunity of XR stream 3.

[0092] In another embodiment, the predetermined time is linked to a timer configured to run for the predetermined time. For example, UE 104 may start the timer in response to detecting a failed PDSCH transmission on an SPS transmission opportunity. In one implementation, as long as the timer is running, UE 104 does not decode the PDSCH and / or PDCCH on the SPS transmission opportunity of the associated SPS configuration group, for example, by de-enabling PDSCH and / or PDCCH decoding for all SPS transmission opportunities of the group. An example of the duration of the timer is 10 milliseconds, but other times may be used.

[0093] At 325, after the timer expires, the UE 104 enables PDSCH and / or PDCCH decoding on the SPS transmission opportunity - in other words, the UE 104 applies traditional behavior after the timer expires. In one example, the timer value is pre-configured or fixed according to the standard. In some embodiments, the timer value is configured in the SPS configuration, for example, by an indication in the SPS-Config IE.

[0094] As noted above, in an embodiment, when an SPS configuration is received at 305, one SPS configuration in the set of associated SPS configurations is configured as a primary SPS configuration. In one implementation, other SPS configurations in the set of associated SPS configurations are defined as secondary SPS configurations. When the PDSCH timing fails at the SPS transmission timing of one SPS configuration in the associated SPS configuration group at 315, the UE 104 may stop decoding the PDSCH and / or PDCCH on the SPS transmission timing of the associated SPS configuration group until the next SPS transmission timing of the primary SPS configuration. In such an embodiment, the predetermined time of 320 is the time until the next SPS transmission timing of the primary SPS configuration. In an embodiment, the SPS configuration for video data is designated as the primary SPS configuration for multi-mode XR applications.

[0095] According to one embodiment, the UE 104 is configured to, after detecting a failed PDSCH transmission on an SPS transmission opportunity of one SPS configuration in the associated SPS configuration group at 315, disable or do not disable decoding of SPS transmission opportunities of other associated SPS configurations. The configuration may be signaled via higher layer signaling (e.g., RRC signaling), for example, as part of the SPS configuration. In one implementation, the configuration may be signaled via DCI (e.g., SPS activation DCI) or MAC control element (CE) signaling.

[0096] At 330, the method may include utilizing the DCI to activate or deactivate the SPS configuration. The operations of 330 may be performed according to examples as described herein. In some implementations, aspects of the operations of 330 may be performed as described in reference to Figure 1 Although 330 is presented as Figure 3 , but activation or deactivation may be performed at any time after the SPS configuration is received at 305 .

[0097] According to an embodiment, a single DCI indicating activation or deactivation of an SPS configuration as part of an associated SPS configuration group activates or deactivates the entire SPS configuration group. According to one implementation, the UE 104 activates or deactivates the SPS configuration in response to receiving an SPS activation or deactivation DCI for a single SPS configuration configured with one or more associated SPS configurations. That is, the DCI activates or deactivates not only the SPS configuration indicated by the DCI, but also the SPS configuration configured as an associated SPS configuration.

[0098] In an embodiment, the DCI indicating activation or deactivation of an SPS configuration includes a new field indicating whether the UE 104 should also activate or deactivate the associated SPS configuration. Thus, the DCI may include an indication of activating or deactivating an SPS configuration, and the UE 104 may be configured to activate or deactivate all associated SPS configurations based on the indication.

[0099] According to one implementation, in response to receiving an SPS activation DCI for an SPS configuration configured with a set of associated SPS configurations, UE 104 activates not only the SPS configuration indicated by the DCI, but also the SPS configuration configured as the associated SPS configuration, wherein the associated SPS configuration is activated using a given time offset. In one example, the DCI indicates a time offset for the associated SPS configuration. In another embodiment, the SPS configuration is configured with one or more time offsets to be applied to the activation of the corresponding associated SPS configuration.

[0100] Although process 300 has been explained with respect to downlink communications and SPS, the same principles and techniques may also be applied to uplink (UL) communications.

[0101] Figure 7 A flow chart of a method 700 for supporting efficient XR communication according to aspects of the present disclosure is illustrated. The operations of the method 700 may be implemented by a device or components thereof as described herein. For example, the operations of the method 700 may be performed by a UE 104, as described in reference to Figure 1 and Figure 2 In some implementations, a device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, a device may use dedicated hardware to perform aspects of the described functions.

[0102] At 705, the method may include receiving a CG configuration. The operations of 705 may be performed according to examples as described herein. In some implementations, aspects of the operations of 705 may be performed as described in reference to Figure 1 The device described is used to perform the

[0103] According to one embodiment, the uplink configured grant (CG) configuration includes a set of associated CG configurations. According to an embodiment, the CG configuration (eg, IE ConfiguredGrant-Config) contains a new field that (if present) identifies a list of identifiers of the associated CG configurations. Figure 5 An example of such an IE is provided in

[0104] In one example, the network configures a set of associated CG configurations based on signaling information received from a core network (e.g., SMF). According to one implementation, information of the associated CG configurations (which may be derived from information of the associated service flow provided by the core network) is used by UE 104 to enhance power saving for XR applications and provide capacity gains.

[0105] At 710, the method may include initiating XR communication using the CG configuration received at 705. The operations of 710 may be performed according to examples as described herein. In some implementations, aspects of the operations of 710 may be performed as described in reference to Figure 1 The device described is used to perform the

[0106] At 715, the method may include detecting a failed PUSCH transmission. The operations of 715 may be performed according to examples as described herein. In some implementations, aspects of the operations of 715 may be performed as described in reference to Figure 1 The device described is used to perform the

[0107] Some of the reasons for failed PUSCH transmissions are different from the failed PDSCH transmission occasion at 315. For example, a PUSCH transmission failure may be caused by hardware or software (including a failure of a codec to perform operations in a timely or accurate manner), or caused by jitter. In some instances, a failure of a PUSCH transmission may be due to a lack of data available for transmission.

[0108] In some XR communications, the packet arrival rate is determined by the frame generation rate (e.g. 60fps). Therefore, the average packet arrival periodicity is given by the inverse of the frame rate, e.g. 16.6667ms = 1 / 60fps. Jitter-free periodic arrivals result in an arrival time at the gNB for a packet with index k (= 1, 2, 3, ...) of

[0109] k / F*1000[ms],

[0110] Where F is a given frame generation rate (per second). This periodic packet arrival implicitly assumes a fixed delay contributed from the network side, including fixed video encoding time, fixed network transmission delay, etc.

[0111] However, in real systems, varying frame coding delays and network delivery times introduce jitter in the packet arrival time at the gNB. In this model, the jitter is modeled as a random variable added on top of the periodic arrivals. The jitter follows a truncated Gaussian distribution with certain statistical parameters.

[0112] The given parameter values ​​and the considered frame generation rate (60 or 120 in this model) ensure that the packets arrive in order (i.e., the arrival time of the next packet is always greater than the arrival time of the previous packet). Therefore, periodic arrivals with jitter give arrival times for packets with index k (=1, 2, 3, ...) as

[0113] Offset + k / F*1000 + J [ms],

[0114] Where F is a given frame generation rate (per second), and J is a random variable that captures jitter. The actual traffic arrival timing of traffic for each UE 104 may be shifted by an arbitrary UE-specific offset. Therefore, jitter may cause PUSCH transmissions to not be delivered in time.

[0115] At 720, the method may include: for a predetermined time, disabling PUSCH transmission, and at 725, the method may include: after the predetermined time, enabling PUSCH transmission. The operations of 720 and 725 may be performed according to the examples described herein. In some implementations, aspects of the operations of 720 and 725 may be performed as described in reference to Figure 1 The device described is used to perform the

[0116] According to one embodiment, when CGPUSCH transmission on the CG resources of one of the CG configuration groups in the associated CG configuration groups fails, the UE 104 temporarily disables PUSCH transmission on the CG resources of the associated CG configuration at 720. Assuming that different service flows (LCH / DRB) of a multi-stream XR application (e.g., a multimode application) are mapped to different associated CG configurations, when the UE has not yet sent a MAC PDU on the resources of one of the CG resources in the associated CG configuration group (e.g., because there is no data available for transmission), the UE 104 temporarily stops uplink transmission of other associated CG configurations. When the data of one of the input signals of the multimode application has not been sent in the uplink, there is little benefit in sending the data of other input signals of the XR application. In contrast, the UE 104 configured according to an embodiment of the present disclosure can save power by not even sending other associated data, so that all input signals are sent or none of them are sent. In one example, the UE discards data planned to be transmitted on the disabled CG resources.

[0117] The embodiments discussed above with respect to process 300 provide details of how long the UE can disable reception of the associated SPS configuration in the context of a predetermined time, including using a timer, waiting for the next instance of the primary XR stream transmission, waiting for the next CG cycle, and waiting for the next transmission opportunity of the failed stream. These embodiments also apply to the predetermined time of process 700.

[0118] The above embodiments are not limited to the case where PDSCH is not detected at the SPS transmission opportunity or no UL data is available for CGPUSCH transmission, but can be applied to the case where PDSCH reception at the SPS opportunity and UL transmission on CG resources are unsuccessful, such as PDSCH / CG PUSCH is not received correctly. Therefore, the embodiments of the present disclosure are applicable to the case where resources are not successfully received by the target entity, regardless of the reason.

[0119] Figure 8 An example of a processor 800 that supports efficient XR communications according to aspects of the present disclosure is illustrated. The processor 800 may be an example of a processor configured to perform various operations according to examples as described herein. The processor 800 may include a controller 802 that is configured to perform various operations according to examples as described herein. The processor 800 may optionally include at least one memory 804, such as an L1 / L2 / L3 cache. Additionally or alternatively, the processor 800 may optionally include one or more arithmetic logic units (ALUs) 800. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0120] The processor 800 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, obtain, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., processor 800), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), etc.).

[0121] The controller 802 may be configured to manage and coordinate various operations (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 800 so that the processor 800 supports various operations according to the examples as described herein. For example, the controller 802 may operate as a control unit of the processor 800 that generates control signals that manage the operation of various components of the processor 800. These control signals include: enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0122] The controller 802 may be configured to extract (e.g., obtain, retrieve, receive) instructions from the memory 804 and determine (multiple) subsequent instructions to be executed so that the processor 800 supports various operations according to the examples as described herein. The controller 802 may be configured to track the memory addresses of instructions associated with the memory 804. The controller 802 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, the controller 802 may be configured to interpret instructions and determine control signals to be output to other components of the processor 800 so that the processor 800 supports various operations according to the examples as described herein. Additionally or alternatively, the controller 802 may be configured to manage data flow within the processor 800. The controller 802 may be configured to control data transfer between registers, arithmetic logic units (ALUs), and other functional units of the processor 800.

[0123] The memory 804 may include one or more caches (e.g., memory local to or included in the processor 800, or other memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some implementations, the memory 804 may reside within or on a processor chipset (e.g., local to the processor 800). In some other implementations, the memory 804 may reside external to the processor chipset (e.g., remote from the processor 800).

[0124] The memory 804 may store computer-readable, computer-executable code including instructions that, when executed by the processor 800, cause the processor 800 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. The controller 802 and / or the processor 800 may be configured to execute computer-readable instructions stored in the memory 804 so that the processor 800 performs various functions. For example, the processor 800 and / or the controller 802 may be coupled to or coupled to the memory 804, and the processor 800, the controller 802, and the memory 804 may be configured to perform various functions described herein. In some examples, the processor 800 may include multiple processors, and the memory 804 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform various functions described herein.

[0125] One or more ALUs 800 may be configured to support various operations according to examples as described herein. In some implementations, one or more ALUs 800 may reside in or on a processor chipset (e.g., processor 800). In some other implementations, one or more ALUs 800 may reside outside a processor chipset (e.g., processor 800). One or more ALUs 800 may perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs 800 may receive input operands and an opcode that determines the operation to be performed. One or more ALUs 800 may be configured with various logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to operations. Additionally or alternatively, one or more ALUs 800 may support logical operations, such as AND, OR, XOR, NOR, and NAND, so that one or more ALUs 800 can process conditional operations, comparisons, and bitwise operations.

[0126] The processor 800 may support wireless communications according to examples as disclosed herein. The processor 800 may be configured or operable to support components for efficient XR communications.

[0127] It should be noted that the methods described herein describe possible implementations, and that operations and steps may be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0128] The various illustrative blocks and components associated with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0129] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on a computer-readable medium or sent on a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination thereof. Features that implement the functions may also be physically located in various locations, including being distributed so that portions of the functions are implemented in different physical locations.

[0130] Computer readable medium includes both non-transient computer storage medium and communication medium, and communication medium includes any medium that helps to transfer computer program from one position to another position.Non-transient storage medium can be any available medium, and it can be accessed by general or special-purpose computer.As an example and not limitation, non-transient computer readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage device, magnetic disk storage device or other magnetic storage device or any other non-transient medium, it can be used to carry or store required program code components in the form of instruction or data structure and can be accessed by general or special-purpose computer or general or special-purpose processor.

[0131] Any connection may be appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave), the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) are all included in the definition of computer-readable medium. Disks and optical disks as used herein include CDs, laser optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and blue-ray disks, wherein disks typically reproduce data magnetically, and optical disks reproduce data optically using lasers. The above combination is also included in the scope of computer-readable media.

[0132] As used herein (including in the claims), "or" is used in a list of items (e.g., a list of items beginning with phrases such as "at least one" or "one or more" or "one or two") to indicate an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a set of closed conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on". In addition, as used herein (including in the claims), a "set" may include one or more elements.

[0133] When referring to a network entity, the terms "send," "receive," or "communicate" may refer to any part of a network entity of a RAN (e.g., a base station, CU, DU, RU) that communicates with another device (e.g., directly or via one or more other network entities).

[0134] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "superior to other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0135] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein can be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE) for wireless communication, comprising: at least one memory; as well as at least one processor, coupled to the at least one memory, and configured to cause the UE to: receiving a first downlink semi-persistent scheduling configuration via radio resource control signaling, The first semi-persistent scheduling configuration includes a set of identifiers, and the set of identifiers identifies at least one other downlink semi-persistent scheduling configuration associated with the first downlink semi-persistent scheduling configuration.

2. The UE according to claim 1, wherein the processor is further configured to: detecting a failure to receive a physical downlink shared channel (PDSCH) transmission opportunity of the first semi-persistent scheduling configuration; and In response to detecting the failure, decoding of at least one PDSCH transmission is disabled on semi-persistently scheduled transmission opportunities of the at least one other downlink semi-persistent scheduling configuration identified by the set of identifiers for a predetermined time period.

3. The UE according to claim 2, wherein the processor is further configured to cause the UE to: After the predetermined time period, decoding of the semi-persistent scheduling transmission opportunities of the at least one other downlink semi-persistent scheduling configuration identified by the set of identifiers is enabled. 4 . The UE of claim 3 , wherein the predetermined time period is a next occurrence of PDSCH transmission of the first semi-persistent scheduling configuration.

5. The UE of claim 3, wherein the first semi-persistent scheduling configuration specifies a primary semi-persistent scheduling configuration and at least one secondary semi-persistent scheduling configuration, and the predetermined time period is a next occurrence of transmission of the primary semi-persistent scheduling configuration.

6. The UE according to claim 5, wherein the processor is further configured to enable the UE to: for the predetermined time period, after detecting a failure of the PDSCH transmission opportunity of the primary semi-persistent scheduling configuration, disable decoding of all PDSCH transmission opportunities for the at least one secondary semi-persistent scheduling configuration.

7. The UE of claim 2, wherein the processor is further configured to detect the failure to receive the PDSCH transmission opportunity when the UE does not detect a PDSCH transmission at a semi-persistent transmission opportunity of the first semi-persistent scheduling configuration.

8. The UE of claim 1, wherein each of the first semi-persistent scheduling configurations and the at least one other downlink semi-persistent scheduling configuration associated with the first semi-persistent scheduling configuration is used for mixed reality (XR) communication.

9. The UE of claim 8, wherein each semi-persistent scheduling configuration is associated with a different sensing channel.

10. The UE of claim 9, wherein the different sensing channels include a video channel and an audio channel.

11. A processor for wireless communication, comprising: at least one memory; as well as A controller is coupled to the at least one memory and is configured such that the controller: receiving a first downlink semi-persistent scheduling configuration via radio resource control signaling, The first semi-persistent scheduling configuration includes a set of identifiers, and the set of identifiers identifies at least one other downlink semi-persistent scheduling configuration associated with the first downlink semi-persistent scheduling configuration.

12. The processor of claim 11, wherein the controller is further configured to: detecting a failure to receive a physical downlink shared channel (PDSCH) transmission opportunity of the first semi-persistent scheduling configuration; and In response to detecting the failure, decoding of at least one PDSCH transmission is disabled on semi-persistently scheduled transmission opportunities of the at least one other downlink semi-persistent scheduling configuration identified by the set of identifiers for a predetermined time period.

13. The processor of claim 12, wherein the controller is further configured such that the controller: After the predetermined time period, decoding of the semi-persistent scheduling transmission opportunities of the at least one other downlink semi-persistent scheduling configuration identified by the set of identifiers is enabled.

14. The processor of claim 13, wherein the predetermined time period is a next occurrence of a PDSCH transmission of the first semi-persistent scheduling configuration.

15. The processor of claim 13, wherein the first semi-persistent scheduling configuration specifies a primary semi-persistent scheduling configuration and at least one secondary semi-persistent scheduling configuration, and the predetermined time period is a next occurrence of transmission of the primary semi-persistent scheduling configuration.

16. The processor of claim 15, wherein the controller is further configured to enable the controller to: for the predetermined time period, after detecting a failure of a PDSCH transmission opportunity of the primary semi-persistent scheduling configuration, disable decoding of all PDSCH transmission opportunities for the at least one secondary semi-persistent scheduling configuration.

17. The processor of claim 12, wherein the controller is further configured to detect the failure to receive the PDSCH transmission opportunity when the controller does not detect a PDSCH transmission on a semi-persistent transmission opportunity of the first semi-persistent scheduling configuration.

18. The processor of claim 11, wherein each of the first semi-persistent scheduling configurations and the at least one other downlink semi-persistent scheduling configuration associated with the first semi-persistent scheduling configuration is used for mixed reality (XR) communications.

19. A method performed by a user equipment (UE), the method comprising: receiving a first downlink semi-persistent scheduling configuration via radio resource control signaling, The first semi-persistent scheduling configuration includes a set of identifiers, and the set of identifiers identifies at least one other downlink semi-persistent scheduling configuration associated with the first downlink semi-persistent scheduling configuration.

20. The method according to claim 19, further comprising: detecting a failure to receive a physical downlink shared channel (PDSCH) transmission opportunity of the first semi-persistent scheduling configuration; as well as In response to detecting the failure, decoding of at least one PDSCH transmission is disabled on semi-persistently scheduled transmission opportunities of the at least one other downlink semi-persistent scheduling configuration identified by the set of identifiers for a predetermined time period.

Images