Inter-device uplink control channel design

Abstract

An extended reality processing unit can receive control information reporting information in a control information reporting configuration from a wireless access network node. The processing unit can receive a downlink payload via long-range radio resources directed to the processing unit or to one or more extended reality devices communicatively coupled with the processing unit. The processing unit can attempt to decode the downlink payload and can transmit a status indication to the node indicating whether decoding the payload was successful or failed, the payload corresponding to a plurality of devices including the processing unit and / or one or more devices. The processing unit can store locally successfully decoded packets directed to a device to memory. The processing unit can transmit / retransmit locally stored packets to the device via short-range resources and can retain successfully decoded packets in memory until an acknowledgement is received via short-range resources that the device has successfully received / decoded the packets.

Description

Related applications

[0001] This application claims priority to U.S. non-provisional patent application No. 18 / 506,888, filed November 10, 2023, entitled “INTER-DEVICE UPLINK CONTROLCHANNEL DESIGN”, the entire contents of which are incorporated herein by reference. Background Technology

[0002] The term "New Radio" (NR), associated with fifth-generation mobile wireless communication systems ("5G"), refers to the technology used in the radio access network ("RAN"), which includes several Quality of Service (QoS) categories, including Ultra-Reliable Low Latency Communication ("URLLC"), Enhanced Mobile Broadband ("eMBB"), and Massive Machine-Type Communication ("mMTC"). The URLLC QoS category is associated with stringent latency requirements (e.g., low latency or low signal / message delay) and high radio performance reliability, while traditional eMBB use cases can be associated with high-capacity wireless communication, which allows for less stringent latency requirements (e.g., higher latency than URLLC) and less reliable radio performance compared to URLLC. Performance requirements for mMTC can be lower than those for eMBB use cases. Some use cases involving mobile devices or mobile user equipment (such as smartphones, wireless tablets, smartwatches, etc.) can impose varying resource loads or demands on a given RAN. RAN nodes can activate network power-saving modes to reduce power consumption. Summary of the Invention

[0003] The following is a simplified summary of the disclosed subject matter to provide a basic understanding of some embodiments. This content is not a broad overview of the embodiments. It is neither intended to identify key or essential elements of the embodiments nor to define the scope of the embodiments. Its sole purpose is to present some concepts of this disclosure in a simplified form as a prelude to the more detailed description that follows.

[0004] In an example embodiment, a method may include: receiving a control information report configuration from a radio access network node by a first user equipment including a processor, the control information report configuration including control information report information. The control information report information may include at least one resource grant indication specifying at least one uplink control channel resource, which can be used by the first user equipment to transmit at least one status indication corresponding to a downlink protocol data unit (DRU) service directed to the first user equipment or to at least one second user equipment communicatively coupled to the first user equipment. The first user equipment may include an extended reality processing unit. The second user equipment may include a terminal extended reality device. The method may further include: receiving at least one downlink protocol data unit by the first user equipment, and transmitting at least one status indication to the radio access network node using the at least one uplink control channel resource, the at least one status indication indicating at least one decoding status corresponding to at least one decoding attempt for decoding the at least one downlink protocol data unit.

[0005] At least one downlink protocol data unit can point to at least one second user equipment.

[0006] At least one decoding state may correspond to at least one failure in which at least one decoding attempt by the first user equipment has been determined to have failed to decode at least one downlink protocol data unit, and wherein at least one state indication includes at least one negative acknowledgment (“NACK”), the at least one negative acknowledgment indicating at least one failure in which at least one downlink protocol data unit was not successfully decoded.

[0007] In an embodiment, at least one decoding state may be a first decoding state. At least one state indication may be a first state indication. At least one decoding attempt may be a first decoding attempt by a first user equipment to decode at least one downlink protocol data unit. The first decoding state may be an acknowledgment indication indicating that the first result of the first decoding attempt is a successfully decoded downlink protocol data unit. The method may further include: the first user equipment storing the successfully decoded downlink protocol data unit in a memory, and the first user equipment transmitting the successfully decoded downlink protocol data unit to at least one second user equipment. The method may further include: the first user equipment receiving a second state indication from at least one second user equipment, the second state indication indicating a second decoding attempt by at least one second user equipment to decode the successfully decoded downlink protocol data unit, and based on the second state indication, the first user equipment performing a communication operation regarding the successfully decoded downlink protocol data unit.

[0008] In an embodiment, the second status indication may indicate that a second decoding attempt by at least one second user equipment has been determined to have failed to decode the successfully decoded downlink protocol data unit. Communication operations may include the first user equipment retransmitting the successfully decoded downlink protocol data unit to at least one second user equipment.

[0009] In an embodiment, receiving the second status indication and retransmitting the successfully decoded downlink protocol data unit to at least one second user equipment can help avoid at least one second user equipment transmitting a second status indication to a radio access network node (e.g., via long-range radio resources), indicating that at least one second user equipment has failed to decode the successfully decoded downlink protocol data unit. The second status indication may include a NACK indication.

[0010] In an embodiment, the second status indication may indicate that a second decoding attempt performed by at least one second user equipment has been determined to be a successful decoding of the successfully decoded downlink protocol data unit. The communication operation may include the first user equipment clearing the successfully decoded downlink protocol data unit from memory.

[0011] In an embodiment, a first downlink protocol data unit (MRD) in at least one downlink protocol data unit may point to a first user equipment (User Equipment). A second downlink protocol data unit in at least one MRD may point to at least one second user equipment (User Equipment). A first status indication in at least one status indication may indicate a first decoding state in at least one decoding state, corresponding to a first decoding attempt performed by the first User Equipment in at least one decoding attempt to decode the first downlink protocol data unit. A second status indication in at least one status indication may indicate a second decoding state in at least one decoding state, corresponding to a second decoding attempt performed by at least one second User Equipment in at least one decoding attempt to decode the second downlink protocol data unit. The control information report configuration may include a transmission multiplexing format indication specifying a transmission multiplexing format that the first User Equipment may use to transmit at least one status indication to a radio access network node, wherein the first status indication and the second status indication are transmitted using at least one uplink control channel resource according to the status indication multiplexing format. The status indication multiplexing format may be one of the following: code division multiplexing format or sequence multiplexing format.

[0012] In another example embodiment, an extended reality processing unit may include a processor configured to process executable instructions that, when executed by the processor, facilitate the execution of operations including: receiving a control information report configuration from a radio network node, the control information report configuration including a resource grant indication specifying an uplink control channel resource available for transmitting at least one status indication corresponding to a downlink service directed to an extended reality device communicatively coupled to the extended reality processing unit. These operations may further include: receiving downlink packets corresponding to a service flow directed to the extended reality device from the radio network node; attempting to decode the downlink packets to obtain a decoding attempt; and transmitting a status indication indicating the decoding status corresponding to the decoding attempt to the radio network node via the uplink control channel resource.

[0013] In an embodiment, the extended reality device may be a first extended reality device. The downlink packet may be a first downlink packet. The traffic flow directed to the extended reality device may be a first traffic flow. The decoding attempt may be a first decoding attempt. The decoding state may be a first decoding state. The state indication may be a first state indication indicating the first decoding state. These operations may further include: receiving a second downlink packet corresponding to a second traffic flow directed to a second extended reality device communicatively coupled to the extended reality processing unit; attempting to decode the second downlink packet to obtain a second decoding attempt; and transmitting a second state indication to a radio network node via the uplink control channel resource, indicating the second decoding state corresponding to the second decoding attempt.

[0014] The first status indication and the second status indication can be transmitted in the uplink control information message. The first status indication and the second status indication can be multiplexed in the uplink control information message according to one of the following: code division-based multiplexing format or sequence-based multiplexing format.

[0015] In an embodiment, the first decoding state may correspond to a first successful decoding of a first downlink packet. The first state indication may be an ACK indicating successful decoding of the first downlink packet. These operations may further include: storing the first downlink packet in memory, and transmitting the first downlink packet to a first extended reality device. In response to transmitting the first downlink packet to the first extended reality device, these operations may further include: receiving a third state indication indicating a second successful decoding of the first downlink packet by the first extended reality device, and erasing the first downlink packet from memory in response to receiving the third state indication.

[0016] In an embodiment, the first decoding state may correspond to the successful decoding of the first downlink packet. The first state indication may be an ACK indicating successful decoding of the first downlink packet. These operations may further include: storing the first downlink packet in memory, and transmitting the first downlink packet to the first extended reality device. In response to transmitting the first downlink packet to the first extended reality device, these operations may further include: receiving a third state indication indicating unsuccessful decoding of the first downlink packet by the first extended reality device. In response to receiving the third state indication, these operations may further include: retransmitting the first downlink packet to the first extended reality device.

[0017] In one embodiment, the downlink packet may be a first downlink packet. The decoding attempt may correspond to the extended reality processing unit failing to decode the downlink packet. The status indication may include a negative acknowledgment (“NACK”). In response to transmitting the NACK, these operations may further include: receiving a second downlink packet from a radio network node, the second downlink packet being a retransmitted version of the first downlink packet. These operations may further include: successfully decoding the second downlink packet to obtain a successfully decoded second downlink packet, storing the successfully decoded second downlink packet in memory, and transmitting the successfully decoded second downlink packet to the extended reality device.

[0018] In another example embodiment, a non-transitory machine-readable medium may include executable instructions that, when executed by a processor of an extended reality processing unit, facilitate the execution of operations including: receiving a control information report configuration from a radio network node, the configuration including at least one resource grant indication specifying at least one control channel resource available for transmitting at least one status indication corresponding to an extended reality service directed to at least one extended reality device communicatively coupled to the extended reality processing unit. These operations may include: receiving a first downlink packet from the radio network node, the first downlink packet corresponding to a first extended reality service flow directed to a first extended reality device among the at least one extended reality device. These operations may further include: attempting to decode the first downlink packet to obtain a first decoding attempt. These operations may include: receiving a second downlink packet from the radio network node, the second downlink packet corresponding to a second extended reality service flow directed to a second extended reality device among the at least one extended reality device. These operations may also include: attempting to decode the second downlink packet to obtain a second decoding attempt, and using at least one control channel resource to transmit a first state indication and a second state indication to the radio network node, the first state indication indicating a first decoding state corresponding to the first decoding attempt and the second state indication indicating a second decoding state corresponding to the second decoding attempt.

[0019] In an embodiment, the first state indication may be a negative acknowledgment (“NACK”). The second state indication may be an acknowledgment (“ACK”). These operations may further include: storing a second downlink packet in the memory of the extended reality processing unit, and transmitting the second downlink packet to a second extended reality device. In response to transmitting the NACK, these operations may further include: receiving a retransmitted version of the first downlink packet from a radio network node, storing the retransmitted version of the first downlink packet in the memory, and transmitting the retransmitted version of the first downlink packet to the first extended reality device. Attached Figure Description

[0020] Figure 1 The diagram illustrates the environment of a wireless communication system.

[0021] Figure 2 The illustration shows an example virtual reality device.

[0022] Figure 3 The illustration shows an example environment where any real-world device is tethered to a user device that manages the business flows associated with that device.

[0023] Figure 4 The illustration shows an example of control information reporting information in the control information reporting configuration.

[0024] Figure 5 The illustration shows an example of an uplink control information multiplexing message.

[0025] Figure 6 The illustration shows a timing diagram of an example embodiment of transmitting uplink services to a radio access network node based on autonomously authorized uplink resources.

[0026] Figure 7 The illustration shows a flowchart of an example embodiment of a method for improving the relative quality of service of an application to determine the transmission of relevant service flows.

[0027] Figure 8 A block diagram illustrating an example method embodiment is shown.

[0028] Figure 9 The diagram illustrates a block diagram of an example extended reality processing unit.

[0029] Figure 10 A block diagram illustrating an example of a non-transitory machine-readable medium embodiment is shown.

[0030] Figure 11 The illustration shows an example computer environment.

[0031] Figure 12 The diagram illustrates a block diagram of an example wireless user equipment. Detailed Implementation

[0032] As a preliminary point, those skilled in the art will readily understand that this embodiment has broad applicability and utility. In addition to those described herein, numerous methods, embodiments, and adaptations of this application, as well as many variations, modifications, and equivalent arrangements, will be apparent from or reasonably suggested by the spirit or scope of the various embodiments of this application.

[0033] Therefore, although this application has been described in detail herein with reference to various embodiments, it should be understood that this disclosure is an illustration of one or more concepts expressed in the various example embodiments and is made solely to provide a complete and feasible disclosure. The following disclosure is not intended and should not be construed as limiting this application or otherwise excluding any such other embodiments, adaptations, variations, modifications, and equivalent arrangements, and the embodiments described herein are limited only by the appended claims and their equivalents.

[0034] As used in this disclosure, in some embodiments, the terms "component," "system," etc., are intended to refer to or include computer-related entities or entities associated with operating means having one or more specific functions, wherein the entity may be hardware, a combination of hardware and software, software, or software in execution. As an example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable file, a thread in execution, computer-executable instructions, a program, and / or a computer. By way of illustration and not limitation, both an application running on a server and the server itself can be components.

[0035] One or more components may reside within a process and / or execution thread, and components may reside on a single computer and / or be distributed across two or more computers. Furthermore, these components may be executed from various computer-readable media on which various data structures are stored. These components may communicate via local and / or remote processes, such as according to signals having one or more data packets (e.g., data from one component interacting with another component in a local system, a distributed system, and / or with other systems across a network such as the Internet). As another example, a component may be a device having specific functions provided by mechanical parts operated by electrical or electronic circuitry, which in turn is operated by a software or firmware application executed by a processor, wherein the processor may be internal or external to the device and executes at least a portion of the software or firmware application. In yet another example, a component may be a device that provides specific functions through electronic components without mechanical parts, the electronic components including a processor therein to execute software or firmware that at least partially endows the electronic components with functionality. While various components have been illustrated as separate components, it should be understood that multiple components may be implemented as a single component, or a single component may be implemented as multiple components, without departing from the exemplary embodiments.

[0036] As used herein, the term "facilitation" refers to the act of a system, device, or component "facilitating" one or more actions or operations within the context of a complex computing environment in which multiple components and / or devices may be involved in computational operations. Non-limiting examples of actions that may or may not involve multiple components and / or devices include: transmitting or receiving data, establishing connections between devices, determining intermediate results toward obtaining a result, etc. In this regard, a computing device or component may facilitate an operation by playing any role in its completion. Therefore, when describing the operation of a component herein, it should be understood that, where an operation is described as being facilitated by a component, these operations may optionally be performed in cooperation with one or more other computing devices or components, such as, but not limited to, sensors, antennas, audio and / or visual output devices, other devices, etc.

[0037] Furthermore, the various embodiments can be implemented as methods, apparatus, or articles of art that use standard programming and / or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement the disclosed subject matter. The term "article of art" as used herein is intended to cover a computer program accessible from any computer-readable (or machine-readable) device or computer-readable (or machine-readable) storage / communication medium. For example, computer-readable storage media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, magnetic stripes), optical discs (e.g., compact discs (CDs), digital versatile discs (DVDs)), smart cards, and flash memory devices (e.g., cards, sticks, key drives). Of course, those skilled in the art will recognize that many modifications can be made to this configuration without departing from the scope or spirit of the various embodiments.

[0038] As an example use case illustrating the exemplary embodiments disclosed herein, virtual reality (“VR”) applications and VR variants (e.g., mixed reality and augmented reality) may perform optimally at certain times when using NR radio resources associated with URLLC, while at other times, lower performance levels may be sufficient. Virtual reality smart glasses devices can consume NR radio resources at a given broadband data rate with stricter radio latency and reliability standards to provide a satisfactory end-user experience.

[0039] 5G systems should support Extended Reality (“XR”) services. XR services can refer to or be called Reality of Everything services. XR services can include VR applications, which are widely adopted XR applications that provide immersive environments that stimulate the end-user's senses, allowing him or her to be “tricked” into feeling as if they are in an environment different from their actual surroundings. XR services can include Augmented Reality (“AR”) applications, which enhance the real-world environment by providing additional virtual-world elements through the user's senses of focusing on real-world elements in their actual surroundings. XR services can include Mixed Reality (“MR”) applications, which help to merge or integrate the virtual and real worlds, allowing the end-user of the XR service to interact with both elements of their real and virtual environments simultaneously.

[0040] Different XR use cases can be associated with certain radio performance objectives. Unlike URLLC or eMBB, a common thread in XR use cases is that achieving a satisfactory end-user experience typically requires high-capacity links with stringent radio and reliability levels. For example, some XR applications require 100 Mbps links with allowable radio latency of a few milliseconds, compared to a 5 Mbps URLLC link with a 1-millisecond radio budget. Therefore, the processes for 5G radio powerline design and association can be adapted to the new XR QoS categories and associated performance objectives.

[0041] XR services can be facilitated by services with certain characteristics associated with them. For example, XR services can often be periodic, with time-varying packet sizes and arrival rates. Furthermore, different packet traffic flows within a single XR communication session can have varying impacts on the end-user experience. For instance, smart glasses streaming 180-degree high-resolution frames can utilize a large portion of the broadband service capacity to satisfy the user experience. However, frames presented to the user's directional orientation (e.g., forward direction) are most important for a satisfactory end-user experience, while frames presented to the user's peripheral vision have a smaller impact. This can be associated with lower QoS requirements for transport packets compared to QoS requirements for directional traffic flows. Therefore, prioritizing certain flows or packets within an XR session can help efficiently utilize the communication system's capacity for service delivery. Additionally, due to the limited form factor of devices, XR-enabled devices (e.g., smart glasses, projection wearables, etc.) may be more power-constrained than traditional mobile handheld devices. Techniques to maximize energy-efficient operation at XR-enabled devices are desirable. Therefore, user equipment devices accessing XR services or XR sessions can be associated with one or more specific QoS parameter standards to meet the performance objectives of the XR service. Measured service values ​​or metrics can correspond to QoS or be analyzed relative to one or more parameter standards, such as data rate, end-to-end latency, or reliability.

[0042] High-capacity demand services, such as virtual reality applications, can pose performance challenges even to 5G NR capabilities. Therefore, while 5G NR systems can facilitate and support higher performance capabilities, the radio interface should still be optimized to support the extremely high capacity and low latency requirements of XR applications and XR data services.

[0043] Multimodal XR applications can integrate different technologies to provide a versatile and comprehensive user experience. For example, a multimodal XR application can use VR to immerse the user in a virtual training environment and then seamlessly switch to AR or MR to provide real-time feedback or overlay guidance information corresponding to physical objects that may appear in the environment viewed by the XR user. Such feedback or guidance information can be related to static objects or can be information that does not change frequently and can be called stable information.

[0044] The advantage of multimodal XR applications is their adaptability, facilitating interaction across different contexts and user preferences. XR applications can provide varying levels of immersion and interaction, allowing users to choose the most appropriate engagement mode based on their needs or the specific task at hand. Additionally, multimodal XR enables collaborative experiences, allowing users in different physical locations to interact within the same virtual space.

[0045] Multimodal XR applications extend beyond entertainment and gaming, with widespread adoption in fields such as healthcare, education, engineering, and marketing. Healthcare practitioners can use multimodal XR to simulate complex surgeries, educators can create interactive and immersive learning experiences, and architects can visualize and modify architectural designs in real time.

[0046] Now turn to the attached image. Figure 1Examples of a wireless communication system 100 supporting blind decoding of PDCCH candidate or search space according to one or more example embodiments of this disclosure are illustrated. The wireless communication system 100 may include one or more base stations 105, one or more user equipment (“UE”) devices 115, and a core network 130. In some examples, the wireless communication system 100 may include a long-range wireless communication network, including, for example, a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, communication with low-cost and low-complexity devices, or any combination thereof. As shown, examples of UE 115 may include a smartphone, laptop computer, tablet computer, car or other vehicle, or drone or other aircraft. Another example of a UE may be a virtual reality / extended reality device 117, such as smart glasses, a virtual reality headset, an augmented reality headset, and other similar devices that can provide the wearer with images, video, audio, touch, taste, or smell. A UE (such as XR device 117) can transmit or receive radio signals with RAN base station 105 via long-range radio link 125, or the UE / XR device can receive or transmit radio signals via short-range radio link 137, which may include a radio link with UE device 115, such as a Bluetooth link, a Wi-Fi link, etc. A UE (such as device 117) can communicate simultaneously via multiple radio links, such as via link 125 with base station 105 and via short-range radio links. XR device 117 can also communicate with a wireless UE via a cable or other wired connection. XR device 117 can offload processing functions or functions related to communication with the RAN to user equipment 115, which may be referred to as an intermediate user equipment or XR processing unit. The XR processing unit or RAN, or components thereof, may be implemented by one or more computer components, which may be referred to as [reference needed]. Figure 11 The XR processing unit may also include a reference. Figure 12 The component described.

[0047] Continue the discussion Figure 1Base station 105 (which may be referred to as a radio access network node or cell) can be distributed throughout a geographical area to form a wireless communication system 100, and can be devices of different forms or with different capabilities. Base station 105 and UE 115 can communicate wirelessly via one or more communication links 125. Each base station 105 can provide a coverage area 110, and UE 115 and base station 105 can establish one or more communication links 125 within the coverage area 110. Coverage area 110 may be an example of a geographical area in which base station 105 and UE 115 can support signal communication according to one or more radio access technologies.

[0048] UE 115 can be distributed throughout the entire coverage area 110 of the wireless communication system 100, and each UE 115 can be stationary or mobile, or both at different times. UE 115 can be devices of different forms or with different capabilities. Figure 1 The diagram illustrates some example UE 115s. The UE 115 described herein can communicate with various types of devices, such as other UE 115s, base station 105, or network devices (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network devices). Figure 1 As shown.

[0049] Base station 105 may communicate with core network 130, communicate with each other, or both. For example, base station 105 may interface with core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). Base station 105 may communicate with each other directly (e.g., directly between base stations 105) or indirectly (e.g., via core network 130) or both via backhaul links 120 (e.g., via X2, Xn, or other interfaces). In some examples, backhaul link 120 may include one or more radio links.

[0050] One or more of the base stations 105 described herein may include, or may be referred to by those skilled in the art as, base station, radio base station, access point, radio transceiver, NodeB, eNodeB (eNB), next-generation NodeB or gigabit NodeB (any of which may be referred to as bNodeB or gNB), home NodeB, home eNodeB or other suitable terms.

[0051] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, personal computer, or router. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances, vehicles, or smart meters.

[0052] like Figure 1 As shown, UE 115 can communicate with various types of devices, such as other UE 115s that can sometimes act as relays, as well as base station 105 and network devices including macro eNB or gNB, small cell eNB or gNB, or relay base station.

[0053] UE 115 and base station 105 can wirelessly communicate with each other on one or more carriers via one or more communication links 125. The term "carrier" can refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. UE 115 can be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0054] In some examples (e.g., in a carrier aggregation configuration), the carrier may also have acquisition signaling or control signaling that coordinates operation against other carriers. The carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and can be located according to a channel grid used for discovery by UE 115. The carrier can operate in standalone mode, where initial acquisition and connection can be performed by UE 115 via the carrier, or the carrier can operate in non-standalone mode, where the connection is anchored using different carriers (e.g., carriers of the same or different radio access technologies).

[0055] The communication link 125 shown in the wireless communication system 100 may include uplink transmission from UE 115 to base station 105, or downlink transmission from base station 105 to UE 115. The carrier may carry downlink or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0056] A carrier may be associated with a specific bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be a specific bandwidth (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz) of a carrier for a particular wireless access technology. Devices of the wireless communication system 100 (e.g., base station 105, UE 115, or both) may have a hardware configuration that supports communication over a specific carrier bandwidth, or may be configured to support communication over a single carrier bandwidth within a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or UE 115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, BWP) or all of the carrier bandwidth.

[0057] The signal waveform transmitted on a carrier can include multiple subcarriers (e.g., using multicarrier modulation (MCM) techniques such as Orthogonal Frequency Division Multiplexing (OFDM) or Discrete Fourier Transform Extended OFDM (DFT-S-OFDM). In a system employing MCM, a resource element can consist of one symbol period (e.g., the duration of a modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Therefore, the more resource elements the UE 115 receives and the higher the order of the modulation scheme, the higher the data rate that can be used for the UE. Wireless communication resources can refer to a combination of radio frequency spectrum resources, temporal resources (e.g., search space), or spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers can further improve the data rate or data integrity for communication with the UE 115.

[0058] It can support one or more parameter sets (numerology) for a carrier, where the parameter set can include subcarrier spacing (Δf) and cyclic prefix. A carrier can be divided into one or more BWPs with the same or different parameter sets. In some examples, UE 115 can be configured with multiple BWPs. In some examples, a single BWP for a carrier can be active at a given time, and communication for UE 115 can be restricted to one or more active BWPs.

[0059] The time interval between base station 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, where Δf max This can represent the maximum supported subcarrier spacing, and N f This can represent the maximum supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0060] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into several time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include several symbol periods (e.g., depending on the length of the cyclic prefix preceding each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots containing one or more symbols. In addition to the cyclic prefix, each symbol period may contain one or more (e.g., N) symbols. f (Number) sampling periods. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0061] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol cycles in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0062] Physical channels can be multiplexed on carriers using various techniques. Physical control channels and physical data channels can be multiplexed on downlink carriers, for example, using one or more of the following: Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM. A control region (e.g., a control resource set (CORESET)) for physical control channels can be defined by several symbol periods and can be extended across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search control regions or spaces for control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level for control channel candidates can refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a common search space set configured to send control information to multiple UEs 115, and a UE-specific search space set used to send control information to a specific UE 115. This document discloses other novel and non-traditional search spaces and configurations for monitoring and decoding them.

[0063] Base station 105 may provide communication coverage via one or more cells, such as macro cells, small cells, hotspots, or other types of cells, or any combination thereof. The term "cell" may refer to a logical communication entity used to communicate with base station 105 (e.g., via a carrier) and may be associated with an identifier used to distinguish neighboring cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other identifiers). In some examples, a cell may also refer to a geographic coverage area 110 or a portion of geographic coverage area 110 (e.g., a sector) in which the logical communication entity operates. The extent of such cells can range from small areas (e.g., structures, subsets of structures) to large areas, depending on various factors such as the capabilities of base station 105. For example, a cell may be or include buildings, subsets of buildings, or external space between geographic coverage areas 110 or space overlapping with geographic coverage areas 110.

[0064] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 115 with a service subscription to a network provider supporting the macro cell. In contrast, small cells can be associated with a lower-power base station 105 and can operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells can provide unrestricted access to UE 115 with a service subscription to a network provider, or they can provide restricted access to UE 115 associated with the small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a home or office). Base station 105 can support one or more cells and can also support communication on one or more cells using one or more component carriers.

[0065] In some examples, a carrier can support multiple cells, and different cells can be configured according to different protocol types (e.g., MTC, Narrowband Internet of Things (NB-IoT), Enhanced Mobile Broadband (eMBB)), which can provide access for different types of devices.

[0066] In some examples, base station 105 may be mobile, thus providing communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but these different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. Wireless communication system 100 may include, for example, a heterogeneous network, in which different types of base stations 105 use the same or different wireless access technologies to provide coverage for various geographic coverage areas 110.

[0067] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, base stations 105 can have similar frame timing, and transmissions from different base stations 105 can be approximately time-aligned. For asynchronous operation, base stations 105 can have different frame timing, and transmissions from different base stations 105 can be time-disaligned in some examples. The techniques described herein can be used for both synchronous and asynchronous operation.

[0068] Some UE 115 devices (such as MTC or IoT devices) can be low-cost or low-complexity devices that can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with base station 105 without human intervention. In some examples, M2M communication or MTC can include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that utilizes or presents this information to humans interacting with the application. Some UE 115 devices can be designed to collect information or automate the behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based billing.

[0069] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception, but not both simultaneously). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115 include entering a power-saving deep sleep mode when not engaged in active communication, operating on limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0070] Wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. UE 115 can be designed to support ultra-reliable, low-latency, or mission-critical functions (e.g., mission-critical functions). Ultra-reliable communication may include dedicated or group communication and may be supported by one or more mission-critical services, such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData). Support for mission-critical functions may include service prioritization, and mission-critical services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency are used interchangeably herein.

[0071] In some examples, UE 115 may also be able to communicate directly with other UE 115 via device-to-device (D2D) communication link 135 (e.g., using peer-to-peer (P2P) or D2D protocols). Communication link 135 may include a sidelink communication link. One or more UE 115s utilizing D2D communication (such as sidelink communication) may be within the geographic coverage area 110 of base station 105. Other UE 115s in such a group may be outside the geographic coverage area 110 of base station 105, or otherwise unable to receive transmissions from base station 105. In some examples, a group of UE 115s communicating via D2D communication may utilize a one-to-many (1:M) system, where a UE transmits to each other UE in the group. In some examples, base station 105 facilitates resource scheduling for D2D communication. In other cases, D2D communication is performed between UE 115s without involving base station 105.

[0072] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidechain communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination thereof. Vehicles may use signals to transmit information related to traffic conditions, signal control, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (e.g., roadside units), or communicate with the network via one or more RAN network nodes (e.g., base station 105) using vehicle-to-network (V2N) communication, or both. Figure 1In the diagram, vehicle UE 116 is shown inside the RAN coverage area, while vehicle UE 118 is shown outside the same RAN coverage area. Vehicle UE 115, wirelessly connected to the RAN, can be a sidechain relay to vehicle UE 116 within the RAN coverage area or to vehicle UE 118 outside the RAN coverage area.

[0073] Core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) routing packets or interconnecting to external networks. The control plane entity can manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for UE 115 served by base station 105 associated with core network 130. User IP packets can be transmitted through the user plane entity, which can provide IP address allocation and other functions. The user plane entity can connect to IP services 150 for one or more network operators. IP services 150 may include access to the Internet, intranet(s), IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0074] Some network devices (such as base station 105) may include sub-components, such as access network entity 140, which may be an example of an access node controller (ANC). Each access network entity 140 may communicate with UE 115 through one or more other access network transport entities 145, which may be referred to as a radio head, smart radio head, or transmit / receive point (TRP). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or combined into a single network device (e.g., base station 105).

[0075] Wireless communication system 100 can operate using one or more frequency bands, typically in the range of 300 MHz to 300 GHz. The region from 300 MHz to 3 GHz is generally referred to as the Ultra High Frequency (UHF) region or decimeter band because the wavelength range is from approximately one decimeter to one meter. UHF waves can be blocked or reoriented by buildings and environmental features, but these waves can penetrate structures sufficiently for macrocells to provide service to UE 115 located indoors. Compared to transmissions using smaller frequencies and longer waves in the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz, UHF wave transmission can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0076] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) region using a frequency band of 3 GHz to 30 GHz (also known as the centimeter band), or in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and the base station 105, and the EHF antennas of the respective devices can be smaller and closer together than UHF antennas. In some examples, this can facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions can be subject to even greater atmospheric attenuation and a shorter range than SHF or UHF transmissions. The techniques disclosed herein can be adopted across transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions can vary by country or regulatory body.

[0077] Wireless communication system 100 can utilize both licensed and unlicensed radio frequency spectrum bands. For example, wireless communication system 100 can employ Licensed Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology in unlicensed frequency bands, such as the 5 GHz Industrial, Scientific, and Medical (ISM) band. When operating in unlicensed radio frequency spectrum bands, devices such as base station 105 and UE 115 can employ carrier sensing for collision detection and avoidance. In some examples, operation in unlicensed frequency bands can be based on carrier aggregation configurations that combine component carriers operating in licensed frequency bands (such as LAA). Operation in unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, etc.

[0078] Base station 105 or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of base station 105 or UE 115 may be located within one or more antenna arrays or antenna panels that can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be juxtaposed at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with base station 105 may be located in different geographical locations. Base station 105 may have an antenna array with several rows and columns of antenna ports that base station 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, antenna panels may support radio frequency beamforming for signals transmitted via antenna ports.

[0079] Base station 105 or UE 115 can use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique can be referred to as spatial multiplexing. For example, multiple signals can be transmitted by a transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) (where multiple spatial layers are transmitted to the same receiving device) and multi-user MIMO (MU-MIMO) (where multiple spatial layers are transmitted to multiple devices).

[0080] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., base station 105, UE 115) to shape or manipulate an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array, such that some signals propagating relative to the antenna array in a particular orientation experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements can include the transmitting or receiving device applying amplitude offset, phase offset, or both to the signals carried via the antenna elements associated with that device. The adjustments associated with each antenna element can be defined by a beamforming weight set associated with a particular orientation (e.g., relative to the antenna array of the transmitting or receiving device, or relative to some other orientation).

[0081] Base station 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by base station 105 in different directions. For example, base station 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmissions in different beam directions may be used to identify (e.g., by a transmitting device (such as base station 105) or a receiving device (such as UE 115)) the beam direction that will be later transmitted or received by base station 105.

[0082] Some signals (such as data signals associated with a specific receiving device) may be transmitted by base station 105 in a single beam direction (e.g., the direction associated with the receiving device, such as UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted in one or more beam directions. For example, UE 115 may receive one or more signals transmitted by base station 105 in different directions and may report to the base station an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0083] In some examples, transmissions performed by a device (e.g., base station 105 or UE 115) may be executed using multiple beam directions, and the device may use a combination of digital precoding or radio frequency beamforming to generate a combined beam for transmission (e.g., from base station 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and this feedback may correspond to the number of beam configurations across the system bandwidth or one or more subbands. Base station 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)), which may or may not be precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel type codebook, linear combination type codebook, port selection type codebook). Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may employ similar techniques for transmitting signals multiple times in different directions (e.g., for identifying beam directions for subsequent transmissions or receptions by UE 115) or for transmitting signals in a single direction (e.g., for transmitting data to a receiving device).

[0084] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105, a receiving device (such as UE 115) may attempt multiple receiving configurations (e.g., directional listening). For example, the receiving device may attempt multiple receiving directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of receiving beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different sets of directional listening weights); or processing the received signal according to different sets of receiving beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these methods can be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving data signals). This single receiving configuration may be aligned on a beam direction determined based on listening according to different receiving configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0085] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer layer or Packet Data Convergence Protocol (PDCP) layer can be IP-based. The Radio Link Control (RLC) layer can perform packet segmentation and reassembly for communication over logical channels. The Medium Access Control (MAC) layer can perform priority processing and multiplexing from logical channels to transport channels. The MAC layer can also use error detection techniques, error correction techniques, or both to support MAC layer retransmissions to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and the base station 105 or core network 130 that supports radio bearers for user plane data. At the physical layer, transport channels can be mapped to physical channels.

[0086] UE 115 and base station 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to improve the likelihood of data being correctly received through communication link 125. HARQ can include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve MAC layer throughput under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device can support HARQ feedback within the same time slot, where the device can provide HARQ feedback in a specific time slot for data received in a previous symbol within the time slot. In other cases, the device can provide HARQ feedback in subsequent time slots or according to some other time interval.

[0087] Now go to Figure 2 The figure illustrates a virtual reality (“VR”) application system 200. In system 200, a wearable VR device 117 is shown from the perspective of a wearer or viewer. VR device 117 may include a central or gestural visual display portion 202, a left visual display portion 204, and a right visual display portion 206, which can be used to display primary visual information, left peripheral visual information, and right peripheral visual information, respectively. As shown, portions 202, 204, and 206 are separated by different lines, but it will be understood that hardware or software can facilitate a gradual transition between the display of primary and peripheral information.

[0088] As mentioned above, different XR use cases may require different corresponding radio performance. Typically, for XR use cases, but unlike for URLLC or eMBB use cases, a reasonable end-user experience requires a high-capacity radio link carrying XR data services (e.g., data streams including visual information) with stringent radio ratings (e.g., latency) and reliability levels. For example, some XR applications require a 100 Mbps link with an allowable radio latency of approximately 2 milliseconds, compared to a 5 Mbps URLLC link with a 1-millisecond radio latency budget.

[0089] Several characteristics of XR data services have been identified from the study: (1) XR service characteristics are usually periodic, with time-varying packet size and packet arrival rate; (2) Due to the limited device shape factor, XR-enabled devices can be more power-limited than conventional mobile handheld devices (e.g., smart glasses, projection wearables, etc.); (3) Multiple packet streams corresponding to different visual information in a given XR session are not perceived by the user as having the same impact on the end-user experience.

[0090] Therefore, in addition to requiring XR-specific power efficiency, smart glasses (such as wearable device 117) streaming 180-degree high-resolution frames require bandwidth capacity to provide the best user experience. However, it has been determined that data corresponding to frames carrying primary or central visual information (i.e., posture or frontal orientation) is most important for end-user satisfaction, while frames corresponding to peripheral visual information have a smaller impact on user experience. Therefore, accepting higher latency for less important traffic flows, so that resources that would otherwise be allocated to less important traffic flows can be used for traffic flows corresponding to more important services, or traffic flows corresponding to devices carrying more important services, can be used to optimize the overall capacity and performance of wireless communication systems (such as 5G communication systems using NR technologies, methods, systems, or devices). For example, a wireless data traffic flow carrying visual information for display on the central or posture visual display section 202 can have a higher priority than a wireless data traffic flow carrying visual information for the left visual display section 204 or the right visual display section 206.

[0091] The performance of a communication network in providing XR services can be determined, at least in part, based on user satisfaction with the XR services. Each user equipment device using XR services can be associated with one or more specific QoS parameter standards, with which measurements or metrics corresponding to the traffic flows that facilitate XR services can be analyzed. Adjusting traffic scheduling so that measured traffic flow metrics meet QoS parameters (such as, for example, data rate, end-to-end latency, or reliability) can benefit the user's XR experience.

[0092] 5G NR radio systems typically include a Physical Downlink Control Channel (“PDCCH”), which can be used to deliver downlink and uplink control information to cellular devices. The 5G control channel can facilitate operation according to the requirements of URLLC and eMBB use cases and can promote effective coexistence between these different QoS categories.

[0093] In embodiments, the user equipment can be deployed as an extended reality processing unit and can facilitate communication with the RAN node on behalf of a less capable terminal XR device (e.g., less capable in terms of processing power, battery capacity, transmitter power, etc.). The extended reality processing unit can include an "in-box" processing unit / device that facilitates signaling, traffic processing, and overall radio assistance for a terminal XR device (e.g., a helmet or glasses) that can communicate directly with the RAN node, but with reduced capabilities. Therefore, an intermediate XR processing unit (e.g., a laptop or smartphone positioned in the middle of the communication link between the RAN node and the terminal XR device) can facilitate a large subset of the load on radio functionality and operation, traffic processing, and battery consumption of the terminal XR device, thus leading to a more efficient terminal XR device design (e.g., requiring smaller battery size, less heat dissipation, etc.).

[0094] However, existing performance reporting processes do not support this novel extended reality processing unit deployment. For example, while using an intermediate XR processing unit to assist a terminal XR device offers performance advantages, the terminal XR device must independently report the decoding status or condition corresponding to each received payload protocol data unit (e.g., packet). For instance, according to conventional techniques, a terminal XR device receiving packets transmitted by a RAN node must generate and transmit an acknowledgment (“ACK”) or negative acknowledgment (“NACK”) status indication corresponding to the received service to the RAN node via an uplink control channel established by the RAN node for use by the terminal XR device and the resources corresponding to the uplink control channel. This exclusive allocation of control channel resources can lead to a degradation of the uplink capacity service capacity of the RAN node. Therefore, the embodiments disclosed herein facilitate aggregation and expected performance feedback reporting corresponding to XR services received at the XR processing unit.

[0095] According to the embodiments disclosed herein, an intermediate XR processing unit can determine, compile, and report to the serving RAN node, based on the decoding status corresponding to an attempt to decode a service by the XR processing unit, a performance feedback metric / status indication (e.g., ACK, NACK) corresponding to a service received by the XR processing unit and directed to one or more terminal XR devices communicatively coupled to the XR processing unit. For example, when the intermediate XR processing unit successfully decodes a service received from the RAN node and directed to two terminal XR devices, the XR processing unit can compile an uplink feedback report that aggregates feedback metrics / status indications corresponding to the two different XR devices and reports the status indications to the RAN node, even before the actual terminal XR devices receive and decode the corresponding service. Therefore, only a single uplink control channel between the RAN node and the intermediate processing unit can be used to carry both performance feedback metrics / status indications corresponding to the intermediate XR processing unit itself and feedback metrics / status indications corresponding to the terminal XR devices. The XR processing unit can transmit the feedback metrics / status indications according to a status indication multiplexing format.

[0096] To facilitate the embodiments disclosed herein, novel user equipment decoding and service buffering behavior embodiments may be used. For example, an intermediate XR processing unit may buffer received service packets for which aggregation performance reports or status indications have been triggered until one or more terminal XR devices to which the received service is directed have successfully decoded the service. For services directed to one or more terminal XR devices, the intermediate XR processing unit may have reported to the serving RAN node that they have been successfully received and decoded (e.g., the XR processing unit sends one or more ACK status indications corresponding to the received service to the RAN node). The intermediate XR processing unit may facilitate retransmission(s) of the received service that has been successfully decoded locally and stored in memory or a buffer without using the radio resources corresponding to the RAN node. If the terminal XR device to which the service that the intermediate XR processing unit successfully received and decoded has not decoded the service, payload retransmission may occur only locally from the intermediate XR processing unit to the terminal XR device that has not decoded the service. Therefore, the serving RAN node and the scarce radio interface resources corresponding to the RAN node may not be used for (multiple) local retransmissions. Therefore, the embodiments disclosed herein facilitate the processing of uplink performance feedback reports corresponding to a set of terminal XR devices that may be implementing or performing similar XR applications, thereby causing more energy-efficient and more efficient processing at the terminal XR devices. This helps to avoid overwhelming the radio interface corresponding to the serving RAN node with uplink control channel signaling overhead.

[0097] Using current technology, user equipment (UE) only compiles and transmits status indications (e.g., ACK or NACK indications) regarding its own service reception and decoding attempts. Using conventional techniques, decoding status reports transmitted to the RAN node are typically based on the actual decoding status generated by the UE to which the service is directed. According to embodiments disclosed herein, UE can compile and transmit to the serving RAN node status indications regarding its own services, as well as status indications corresponding to services directed to other UE devices. For example, according to conventional techniques, the device to which a service has successfully decoded a packet transmits a positive (ACK) report metric. However, embodiments disclosed herein facilitate the ability of a master device (e.g., an XR processing unit) to send performance feedback reports regarding services that have not actually been decoded at the intended slave device (e.g., a terminal XR device), but for which decoding has been attempted at the master device. According to embodiments disclosed herein, the master device can locally buffer received services directed to slave devices, forward the buffered services to the slave device, and if decoding is unsuccessful at the slave device, retransmit the buffered services locally to the slave device without involving the cellular radio interface of the serving RAN node. According to traditional technology, the master device that relays services to the terminal device only forwards downlink services without performing local buffering.

[0098] Now go to Figure 3 The figure illustrates an example environment 300, in which an extended reality device 117 is attached to an extended reality processing unit user equipment 115. Referring to its relationship as a communication session endpoint with respect to RAN node 105, device 117 may be referred to as a terminal XR device, while the extended reality processing unit 115 is located between the RAN node and the device. Regarding battery capacity (or the ability to be powered via a wired power source receiving power from a wall outlet) or processing power, the XR processing unit 115 may be more capable than the XR device 117. In this embodiment, the peripheral portion 204 / 206 of the VR / XR device 117 (e.g., ...) is connected to the peripheral portion 204 / 206 of the VR / XR device 117. Figure 2 As shown, a downlink service flow providing a service can be associated with a downlink service flow carrying a service to be displayed by the device's attitude section 202. In another example, two different service flows can carry services pointing to the right side 202R and the left side 202L of the attitude section 202, respectively, and therefore can be associated. In another example, an uplink service flow can carry a service associated with the downlink service flow.

[0099] Design of uplink control channel between devices.

[0100] like Figure 3As shown, in Action 1, the centralized XR processing unit 115 can receive an inter-device uplink control channel configuration 310 from the serving RAN node 105. This configuration may be referred to as a control information reporting configuration. Configuration 310 may include at least one resource grant indication specifying at least one uplink control channel resource. This uplink control channel resource may be used by the XR processing unit 115 to transmit at least one status indication corresponding to a downlink protocol data unit service directed to the XR processing unit or to at least one terminal XR device 117A or 117B (which may be communicatively coupled to the XR processing unit). Configuration 310 may include grant resource information corresponding to the uplink control channel resource and an activation indication indicating that the indicated grant uplink control channel resource can be used to facilitate uplink transmissions to the RAN node 105, including inter-device feedback reports (e.g., ACK or NACK status indications reported by the XR processing unit corresponding to packet decoding attempts performed by the XR processing unit). If inter-device feedback is enabled in configuration 310, configuration 310 may include an indication of the inter-device feedback transmission mode, which may be referred to as a status indication multiplexing format and may be indicated as code division-based multiplexing or sequence-based multiplexing. Using the sequence-based feedback transmission format, processing unit 115 may sequentially transmit feedback metrics (e.g., ACK or NACK) corresponding to the service 320 received in action 2, directed to terminal XR devices 117A or 117B, via status indication report message 325, through the uplink control channel resource set indicated as authorized in configuration 310. Message 325 may include one or more terminal XR device identifiers, each corresponding to one or more feedback metrics / status indications transmitted via the sequence-based status indication multiplexing format. If a code division-based feedback transmission status indication multiplexing format is indicated in configuration 310, the central XR processing unit 115 can transmit, for example, a feedback metric corresponding to terminal XR device 117A or 117B via the entire authorized set of uplink control channel resources indicated in configuration 310, wherein each status indication (e.g., ACK or NACK) reported in message 325 is encoded using a scrambling code associated with the terminal XR device 117A or 117B corresponding to the given status indication.

[0101] Therefore, in action 3, when the XR processing unit 115 receives a downlink service 320 directed to one or more terminal XR devices 117A or 117B in action 2, the XR processing unit 115 may attempt to decode one or more packets corresponding to service 320 using decoding information corresponding to the terminal XR devices(s), which may have been pre-configured to the XR processing unit. In action 4, based on the decoding status (e.g., successful decoding or decoding failure) corresponding to service 320 determined by the XR processing unit 115, the processing unit may trigger the transmission of an inter-device feedback report status indication message 325. The status indication report message 325 includes a status indication corresponding to the decoding attempts of the service packets corresponding to service 320. According to the configured status indication multiplexing format (e.g., sequence-based multiplexing or code division-based multiplexing), the status indication indicates the determined decoding status or condition and includes a terminal XR device identifier corresponding to the one or more terminal XR devices 117A or 117B to which service 320 is directed.

[0102] As described with reference to Action 3, XR processing unit 115 can locally store the received and successfully decoded service packets corresponding to service 320. These service packets may include service packets pointing to one or more terminal XR devices 117A or 117B, and a positive (e.g., ACK) status indication has been transmitted to RAN node 105 for these service packets. In Action 5, XR processing unit 115 can forward the buffered, successfully decoded service packets to the one or more terminal XR devices 117A or 117B to which the successfully decoded and buffered packets are directed via an inter-device link (e.g., 5G side link 135 or device-specific link 137 (which may be a Wi-Fi link)). Therefore, in Action 6, the final decoding status / status indication corresponding to the forwarded service packets for one or more terminal XR devices 117A or 117B can be determined, and the XR processing unit transmits the buffered service packets to one or more terminal XR devices 117A or 117B (e.g., the terminal XR devices may transmit ACK or NACK to the XR processing unit via the inter-device link).

[0103] In action 7, when a positive decoding feedback (e.g., ACK) is received from terminal XR device 117A or 117B, indicating that a service packet forwarded to one or more devices has been successfully decoded, the XR processing unit / 115 can clear or erase one or more buffered service packets that were buffered by the XR processing unit after successful decoding in action 3, and for these packets, the XR processing unit has received a positive decoding feedback indication from one or more terminal XR devices corresponding to the ACK. However, when a negative decoding feedback status indication (e.g., NACK) is received from one or more terminal XR devices 117A or 117B, the XR processing unit 115 can retain the service corresponding to the NACK in a local storage buffer and can retransmit the packet corresponding to the NACK via local inter-device payload retransmission using link 137 / 137. Therefore, RAN node 105 can avoid the burden of retransmitting multiple XR service packets that the terminal XR device failed to decode via the resources corresponding to the long-range link 125 between the RAN node and the XR device by offloading retransmissions to XR processing unit 115, thereby enabling XR processing unit to facilitate retransmissions via local non-cellular links 135 or 137. Furthermore, a single uplink control channel can be used to deliver via a single message 325 performance feedback metrics / status indications corresponding to service packets that the XR processing unit attempts to decode, directed to the XR processing unit itself and / or to one or more terminal XR devices 117A or 117B, thus minimizing the use of long-range radio link resources used to carry uplink control information.

[0104] Now go to Figure 4 The figure illustrates an example control information report configuration 310. The extended reality processing unit can receive configuration information 310, which includes authorized resource information 410 indicating resources (e.g., time or frequency resources) corresponding to uplink control channels that can be used to transmit status indications in the report, such as reference... Figure 3 The report 325 is described. Configuration information in configuration 310 may include an activation indication 415, indicating whether inter-device feedback reporting via message 325 is supported via authorized uplink control channel resources (indicated in resource information 410). Configuration information 310 may include an inter-device feedback transmission mode indication 420, specifying a status indication multiplexing format.

[0105] Now go to Figure 5 This diagram illustrates an example transmission multiplexing format 500, which can be used in uplink control information messages, such as references. Figure 3Message 325 is described to transmit a status indication corresponding to a packet pointing to the XR processing unit and / or the terminal XR device, indicating whether the XR processing unit has successfully or failed to decode it. In an embodiment exemplified by format 500, a sequence-based feedback transmission format is shown, according to which the XR processing unit can transmit feedback metrics (e.g., status indications such as ACK or NACK indications) corresponding to the XR processing unit or the terminal XR device, sequentially or in parallel, via a subset or more subsets of authorized uplink control resources authorized in configuration 310. Information transmitted according to format 500 may include one or more device indications 505, indicating one or more terminal XR devices corresponding to the feedback metric / status indication 510. Figure 5 In embodiments not shown, utilizing a code division-based feedback transmission format, the XR processing unit can transmit status indications of multiple user equipments in parallel over time via the entire authorized resource set of the authorized uplink control channel in configuration 310. Utilizing code division-based multiplexing, the XR processing unit can encode each status indication contained in uplink message 325 using a scrambling code associated with the user equipment corresponding to the status indication. For example... Figure 5 As shown, it depicts sequence-based multiplexing. In a code division-based multiplexing embodiment, instead of an identifier preceding the status indication (e.g., identifier 505 receives ACK / NACK indication 510), multiple status indications can be transmitted in the uplink control channel message and can be encoded separately using scrambling codes corresponding to the WTRU (e.g., XR processing unit or one or more terminal XR devices) of the status indication in the generation message 325.

[0106] Now go to Figure 6 This figure illustrates a timing diagram of an example embodiment of method 600, which facilitates indication of the status of downlink traffic packets corresponding to XR processing unit 115 or terminal XR device 117. In action 605, the central XR processing unit / WTRU 115 can be configured to process, manage, or otherwise facilitate various radio functions, typically corresponding to serving RAN nodes, with respect to one or more adjacent terminal XR devices / WTRUs 117. It can receive uplink control channel configuration from RAN node 105, which may be referred to as control information report configuration and may include... Figure 4 The descriptions and references shown Figure 4 The described information. The control information report configuration may include authorized uplink control channel resource information (e.g., time and frequency resources). The control information report configuration may include an activation indication specifying inter-device uplink control information (“UCI”) scheduling via authorized uplink control resources for use via a reference. Figure 3 The described message 325 carries a retransmission status indication (e.g., HARQ feedback) associated with a service directed to one or more terminal XR devices 117 or to an XR processing unit 115. The control information report configuration may include uplink control channel transmission format information, which may be referred to as a transmission multiplexing format indication, specifying the transmission multiplexing format suitable for transmitting the status indication corresponding to the XR processing unit 115 or one or more XR devices 117, such as code division multiplexing or sequence multiplexing. (Status indications corresponding to more than one XR device 117 and / or XR processing unit 115 may be transmitted in a single uplink control information message 325 according to the multiplexing format indicated in the control information report configuration.)

[0107] In action 610, the central XR processing unit 115 can receive downlink payloads directed to the XR processing unit WTRU or to one or more terminal XR devices 117. In action 615, the XR processing unit 115 can transmit one or more status indications in a UCI message to the radio access network node 105, indicating whether the XR processing unit successfully or failed to decode services directed to one or more terminal XR devices 117 or to the XR processing unit itself. The XR processing unit 115 can transmit one or more status indications in a UCI message to the radio access network node 105 according to the transmission multiplexing format indicated in the uplink control channel configuration received in action 605. The XR processing unit 115 can compile or generate UCI messages according to the transmission multiplexing format (e.g., sequence-based transmission multiplexing format or code division-based transmission multiplexing format), and can transmit UCI messages in action 615 according to one or more uplink control channel resources indicated in the configuration received in action 605.

[0108] In action 620, XR processing unit 115 may locally store the downlink service received in action 610 that has been successfully decoded by the XR processing unit. In action 625, XR processing unit 115 may forward the service received in action 610 to the terminal XR device 117 to which the service is directed. If XR processing unit 115 receives a HARQ NACK status indication from one or more terminal XR devices 117 that forwarded the service to it in action 625 in action 630, XR processing unit may retransmit the service to those one or more terminal XR devices. If XR processing unit 115 receives a HARQ ACK status indication from one or more terminal XR devices 117 that forwarded the service to it in action 625 in action 635, XR processing unit may clear or erase the downlink payload stored locally in action 620.

[0109] Therefore, after XR processing unit 115 receives payload packets destined for one or more terminal XR devices 117 from RAN 105 via link 125-1 and successfully decodes the payload packets, XR processing unit can send an ACK / NACK transmission to RAN 105 (e.g., XR processing unit can transmit a status indication) indicating the decoding status (e.g., successful decoding or decoding failure) corresponding to the XR processing unit's attempt to decode the payload packet. By storing the payload destined for terminal XR processing device 117 locally, XR processing unit 115 can transmit an ACK or NACK corresponding to the received payload to RAN 105 before the terminal XR device to which the payload is destined actually receives and decodes the payload. After receiving an ACK corresponding to the payload packet from terminal XR device 117, XR processing unit 115 can clear or erase the stored payload. If XR processing unit 115 receives a NACK from the terminal XR device 117 to which the locally stored payload is directed, the XR processing unit can retransmit the stored payload to the terminal XR device. This helps prevent the terminal XR device from transmitting the NACK to the radio access network node 105 using the long-range radio resources corresponding to link 125-2, and also helps prevent the radio access network node from retransmitting payload packets to the terminal XR device via the resources corresponding to link 125-2. XR processing unit 115 can send ACK / NACK feedback corresponding to one or more packets directed to another device that has not yet received or attempted to decode packets(multiple) of its packets. Therefore, as long as the XR processing unit can receive and decode packets from RAN 105, it can send an ACK or NACK to RAN 105, thus reducing delays and stalls associated with HARQ reporting, regardless of the reception quality of the terminal XR device to which the payload is directed. Furthermore, the XR processing unit can facilitate the delivery of the payload to the terminal XR device even if multiple retransmissions occur via the inter-device link (e.g., retransmission from XR processing unit 115 to terminal XR device 117 via link 135 / 137 between XR processing unit 115 and terminal XR device 117), thus reducing the use of radio resources corresponding to the long-range links 125-2 between RAN 105 and terminal XR device 117 for retransmitting the payload.

[0110] Now go to Figure 7 The figure illustrates a flowchart of example embodiment 700. Method 700 begins at action 705. In action 710, the user equipment (which may be an extended reality processing unit, or may include an extended reality processing unit) can receive a control information report configuration from the serving RAN node. The control information report configuration may include a reference Figure 4The configuration information 310 shown describes the information. In action 715, the XR processing unit can receive downlink service payloads from the serving RAN node, such as one or more packets directed to one or more terminal XR devices, or one or more packets directed to the XR processing unit itself. In action 720, the XR processing unit can attempt to decode one or more packets received in action 715. In action 725, the XR processing unit can transmit a control channel information message to the serving RAN, which includes one or more status indicators indicating one or more attempts to decode one or more packets in action 720. This control channel information message can be an uplink control channel information message and can include one or more ACK or NACK status indicators corresponding to the attempt to decode the service payload received in action 715.

[0111] In action 730, the Extended Reality (XR) processing unit can determine whether the attempt to decode the service received at 715 was successful. It will be understood that the determination in action 730 can occur before action 725 transmits one or more status indications, as the status indications are based on the decoding results of the attempt to decode the service received at 715. If action 730 determines that the XR processing unit's attempt to decode the packet was unsuccessful, then in addition to transmitting the corresponding NACK indication to the serving RAN in action 725, in response to transmitting the NACK status indication in action 725, the XR processing unit can receive a retransmission of the undecoded packet, with the NACK status indication transmitted at action 725 corresponding to this undecoded packet.

[0112] Returning to the description of action 730, if the Extended Reality processing unit determines that the packet has been successfully decoded, then in action 735, in addition to transmitting the corresponding ACK status indication indicating successful decoding of the packet in action 725, the Extended Reality processing unit may store the successfully decoded packet in memory. This memory may be part of, local to, or external to the Extended Reality processing unit. In action 740, the Extended Reality processing unit may transmit the packet that was successfully decoded in action 720, corresponds to the ACK status indication transmitted in action 725, and was stored in memory or a buffer in action 730, to the terminal XR device to which the packet is directed. In action 745, the Extended Reality processing unit may determine whether a positive status indication (e.g., ACK) has been received from the terminal XR device to which the packet was transmitted in action 740. If it is determined that a positive status indication corresponding to the packet transmitted in action 740 has not yet been received from the terminal Extended Reality device to which the packet was transmitted in action 740, the Extended Reality processing unit may retrieve the packet from memory and retransmit the packet to the terminal Extended Reality device to which the packet is directed. If the Extended Reality processing unit determines in action 745 that it has received a positive status indication (e.g., ACK) corresponding to the transmitted packet from the terminal XR device that transmitted the packet to it in action 740, then in action 750, the Extended Reality processing unit can clear / erase / delete the packet from memory. Method 700 ends in action 760.

[0113] Now go to Figure 8 The figure illustrates an example embodiment of method 800, comprising: at block 805, a first user equipment including a processor receiving a control information report configuration from a radio access network node, the control information report configuration including at least one resource grant indication indicating at least one uplink control channel resource, the at least one uplink control channel resource being usable by the first user equipment to transmit at least one status indication corresponding to a downlink protocol data unit service, the downlink protocol data unit service being directed to the first user equipment or to at least one second user equipment communicatively coupled to the first user equipment; at block 810, the first user equipment receiving at least one downlink protocol data unit; and at block 815, the first user equipment transmitting at least one status indication to the radio access network node using the at least one uplink control channel resource, the at least one status indication indicating at least one decoding status corresponding to at least one decoding attempt for decoding at least one downlink protocol data unit.

[0114] Now go to Figure 9The figure illustrates an example extended reality processing unit, including: in block 905, a processor configured to process executable instructions that, when executed by the processor, facilitate the execution of operations including: receiving a control information report configuration from a radio network node, the control information report configuration including a resource grant indication specifying an uplink control channel resource, the uplink control channel resource being available for transmitting at least one status indication corresponding to a downlink service directed to an extended reality device communicatively coupled to the extended reality processing unit; in block 910, receiving a downlink packet corresponding to a service flow directed to the extended reality device from the radio network node; in block 915, attempting to decode the downlink packet to obtain a decoding attempt; and in block 920, transmitting via the uplink control channel resource to the radio network node an indication of the status of the decoding attempt. The operation further includes: in block 925, where the extended reality device is a first extended reality device, where the downlink packet is a first downlink packet, where the traffic flow to the extended reality device is a first traffic flow, where the decoding attempt is a first decoding attempt, where the decoding state is a first decoding state, where the status indication is a first status indication indicating the first decoding state, and wherein these operations further include: in block 930, receiving a second downlink packet corresponding to a second traffic flow to a second extended reality device communicatively coupled to the extended reality processing unit; in block 935, attempting to decode the second downlink packet to obtain a second decoding attempt; and in block 940, transmitting a second status indication to a radio network node via the uplink control channel resource, which indicates the second decoding state corresponding to the second decoding attempt.

[0115] Now go to Figure 10The figure illustrates a non-transitory machine-readable medium 1000, including: in block 1005, executable instructions that, when executed by a processor of an extended reality processing unit, facilitate the execution of operations including: receiving a control information report configuration from a radio network node, the control information report configuration including at least one resource grant indication specifying at least one control channel resource, the at least one control channel resource being available for transmitting at least one status indication corresponding to an extended reality service directed to at least one extended reality device communicatively coupled to the extended reality processing unit; and in block 1010, receiving a first downlink packet from a radio network node, the first downlink packet corresponding to a directive to at least one extended reality device. The first extended reality traffic flow of the first extended reality device in the first extended reality device; in block 1015, attempting to decode the first downlink packet to obtain a first decoding attempt; in block 1020, receiving a second downlink packet from a radio network node, the second downlink packet corresponding to a second extended reality traffic flow pointing to a second extended reality device in at least one extended reality device; in block 1025, attempting to decode the second downlink packet to obtain a second decoding attempt; and in block 1030, transmitting a first state indication and a second state indication to the radio network node using at least one control channel resource, the first state indication indicating a first decoding state corresponding to the first decoding attempt, and the second state indication indicating a second decoding state corresponding to the second decoding attempt.

[0116] To provide additional context for the various embodiments described herein, Figure 11 The following discussion is intended to provide a brief, general description of a suitable computing environment 1100 in which various embodiments of the embodiments described herein can be implemented. While the embodiments have been described above in the general context of computer-executable instructions that can run on one or more computers, those skilled in the art will recognize that these embodiments may also be implemented in combination with other program modules and / or as a combination of hardware and software.

[0117] Typically, program modules include routines, programs, components, data structures, etc., that perform specific tasks or implement specific abstract data types. Furthermore, those skilled in the art will understand that these methods can be implemented using other computer system configurations, including single-processor or multi-processor computer systems, minicomputers, mainframe computers, IoT devices, distributed computing systems, and personal computers, handheld computing devices, microprocessor-based or programmable consumer electronics, each of which can be operatively coupled to one or more associated devices.

[0118] The embodiments described herein can also be implemented in a distributed computing environment, where certain tasks are performed by remote processing devices linked via a communication network. In a distributed computing environment, program modules can reside on both local and remote storage devices.

[0119] Computing devices typically include a variety of media, which may include computer-readable storage media, machine-readable storage media, and / or communication media, the terms being used herein in ways distinct from each other. A computer-readable storage media or a machine-readable storage media can be any available storage medium accessible by a computer, and includes volatile and non-volatile media, removable and non-removable media. By way of example and not limitation, a computer-readable storage media or a machine-readable storage media can be implemented in conjunction with any method or technology used for storing information, such as computer-readable or machine-readable instructions, program modules, structured data, or unstructured data.

[0120] Computer-readable storage media may include, but are not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD), Blu-ray disc (BD) or other optical disc storage devices, magnetic cartridges, magnetic tapes, disk storage devices or other magnetic storage devices, solid-state drives or other solid-state storage devices, or other tangible and / or non-transitory media that can be used to store desired information. In this regard, the terms “tangible” or “non-transitory” used herein to describe storage devices, memories, or computer-readable media should be understood to exclude only the propagation of transient signals themselves as a modifier, and do not waive the rights to all standard storage devices, memories, or computer-readable media that do not merely propagate transient signals themselves.

[0121] Computer-readable storage media can be accessed by one or more local or remote computing devices, for example via access requests, queries or other data retrieval protocols, for various operations concerning the information stored on the media.

[0122] Communication media typically embody computer-readable instructions, data structures, program modules, or other structured or unstructured data as data signals (such as modulated data signals, carrier waves, or other transmission mechanisms), and include any medium for delivering or transmitting information. The term "modulated data signal" or signal refers to a signal whose characteristics are set or altered in a manner that encodes information in one or more signals. By way of example and not limitation, communication media include wired media (such as wired networks or direct wired connections) and wireless media, such as acoustic, RF, infrared, and other wireless media.

[0123] Refer again Figure 11 An example environment 1100 for implementing the various embodiments described herein includes a computer 1102, which includes a processing unit 1104, system memory 1106, and a system bus 1108. The system bus 1108 couples system components, including but not limited to system memory 1106, to the processing unit 1104. The processing unit 1104 can be any processor from a variety of commercially available processors and may include cache memory. Dual microprocessors and other multiprocessor architectures may also be used as the processing unit 1104.

[0124] System bus 1108 can be any of several types of bus architectures, which can also interconnect to memory buses (with or without memory controllers), peripheral buses, and local buses using any of the various commercially available bus architectures. System memory 1106 includes ROM 1110 and RAM 1112. The Basic Input / Output System (BIOS) can be stored in non-volatile memory, such as ROM, erasable programmable read-only memory (EPROM), or EEPROM, and its BIOS contains basic routines that facilitate the transfer of information between components within computer 1102, such as during startup. RAM 1112 may also include high-speed RAM, such as static RAM for caching data.

[0125] Computer 1102 also includes an internal hard disk drive (HDD) 1114 (e.g., EIDE, SATA), one or more external storage devices 1116 (e.g., floppy disk drive (FDD) 1116, memory stick or flash drive reader, memory card reader, etc.), and an optical disc drive 1120 (e.g., capable of reading from or writing to CD-ROMs, DVDs, BDs, etc.). Although the internal HDD 1114 is illustrated as being located within computer 1102, the internal HDD 1114 can also be configured for external use in a suitable chassis (not shown). Additionally, although not shown in environment 1100, a solid-state drive (SSD) may be used in addition to or in place of HDD 1114. HDD 1114, external storage devices(s) 1116, and optical disc drive 1120 may be connected to system bus 1108 via HDD interface 1124, external storage interface 1126, and optical disc drive interface 1128, respectively. The interface 1124 for external driver implementation may include at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) 1394 interface technologies. Other external driver connectivity technologies are also contemplated in the embodiments described herein.

[0126] These drives and their associated computer-readable storage media provide non-volatile storage of data, data structures, computer-executable instructions, etc. For computer 1102, these drives and storage media accommodate storage of any data in a suitable digital format. Although the above description of computer-readable storage media refers to a corresponding type of storage device, those skilled in the art will understand that other types of computer-readable storage media (whether currently existing or to be developed in the future) may also be used in the example operating environment, and further, any such storage media may contain computer-executable instructions for performing the methods described herein.

[0127] Multiple program modules can be stored in the drive and RAM 1112, including an operating system 1130, one or more application programs 1132, other program modules 1134, and program data 1136. All or part of the operating system, application programs, modules, and / or data can also be cached in RAM 1112. The systems and methods described herein can be implemented using a variety of commercially available operating systems or combinations of operating systems.

[0128] Computer 1102 may optionally include emulation technology. For example, a hypervisor (not shown) or other intermediary may emulate a hardware environment for operating system 1130, and the emulated hardware may optionally be different from the hardware used in the emulation. Figure 11 The hardware shown is illustrated. In such an embodiment, operating system 1130 may include one of a plurality of virtual machines (VMs) hosted at computer 1102. Furthermore, operating system 1130 may provide a runtime environment for application 1132, such as the Java Runtime Environment or the .NET Framework. A runtime environment is a consistent execution environment that allows application 1132 to run on any operating system that includes that runtime environment. Similarly, operating system 1130 may support containers, and application 1132 may be in the form of a container, which is a lightweight, standalone, executable software package that includes, for example, application-specific code, runtime, system tools, system libraries, and settings.

[0129] Furthermore, computer 1102 may include a security module, such as a Trusted Processing Module (TPM). For example, before loading the next boot component, the boot component uses the TPM to hash the next boot component over time and waits for the result to match a security value. This process can occur at any layer of the computer 1102's code execution stack, for example, at the application execution level or at the operating system (OS) kernel level, thereby achieving security at any code execution level.

[0130] Users can input commands and information into computer 1102 through one or more wired / wireless input devices, such as keyboard 1138, touchscreen 1140, and pointing devices such as mouse 1142. Other input devices (not shown) may include microphones, infrared (IR) remote controls, radio frequency (RF) remote controls or other remote controls, joysticks, virtual reality controllers and / or virtual reality headsets, game controllers, styluses, image input devices (e.g., cameras), gesture sensor input devices, visual motion sensor input devices, emotion or face detection devices, biometric input devices (e.g., fingerprint or iris scanners), etc. These and other input devices are typically connected to processing unit 1104 via input device interface 1144, which can be coupled to system bus 1108, but can be connected via other interfaces, such as parallel ports, IEEE 1394 serial ports, game ports, USB ports, IR interfaces, BLUETOOTH® interfaces, etc.

[0131] Monitor 1146 or other types of display devices can also be connected to system bus 1108 via an interface such as video adapter 1148. In addition to monitor 1146, the computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc.

[0132] Computer 1102 can operate in a networked environment using logical connections to one or more remote computers (such as (multiple) remote computers 1150) via wired and / or wireless communications. The (multiple) remote computers 1150 can be workstations, server computers, routers, personal computers, laptops, microprocessor-based entertainment devices, peer-to-peer devices, or other common network nodes, and typically include many or all of the elements described relative to computer 1102, although for simplicity, only memory / storage device 1152 is illustrated. The depicted logical connections include wired / wireless connections to a local area network (LAN) 1154 and / or a larger network (e.g., a wide area network (WAN) 1156). Such LAN and WAN network environments are common in offices and companies and facilitate enterprise-wide computer networks (such as intranets), all of which can connect to global communication networks such as the Internet.

[0133] When used in a LAN network environment, computer 1102 can connect to local area network 1154 via a wired and / or wireless communication network interface or adapter 1158. Adapter 1158 can facilitate wired or wireless communication to LAN 1154, which may also include a wireless access point (AP) configured thereon for communicating with adapter 1158 in wireless mode.

[0134] When used in a WAN network environment, computer 1102 may include modem 1160, or may be connected to a communication server on WAN 1156 via other means (such as via the Internet) for establishing communication over WAN 1156. Modem 1160 (which may be internal or external, wired or wireless) may be connected to system bus 1108 via input device interface 1144. In a networked environment, program modules depicted relative to computer 1102 or portions thereof may be stored in remote memory / storage device 1152. It will be understood that the network connections shown are examples, and other methods for establishing communication links between computers may be used.

[0135] When used in a LAN or WAN network environment, computer 1102 can access cloud storage systems or other network-based storage systems, in addition to or replacing external storage device 1116 as described above. Typically, the connection between computer 1102 and the cloud storage system can be established via LAN 1154 or WAN 1156, for example, by adapter 1158 or modem 1160. When computer 1102 is connected to an associated cloud storage system, external storage interface 1126 can manage the storage provided by the cloud storage system, just like other types of external storage, with the help of adapter 1158 and / or modem 1160. For example, external storage interface 1126 can be configured to provide access to cloud storage sources as if these sources were physically connected to computer 1102.

[0136] Computer 1102 can be operable to communicate with any wireless device or entity operatively configured in wireless communication, such as printers, scanners, desktop and / or portable computers, portable data assistants, communication satellites, any device or location associated with a wirelessly detectable tag (e.g., kiosks, newsstands, store shelves, etc.), and telephones. This can include Wi-Fi and BLUETOOTH® wireless technologies. Therefore, communication can be a predefined structure like a traditional network, or simply self-organizing communication between at least two devices.

[0137] Now go to Figure 12The figure illustrates a block diagram of example UE 1260. UE 1260 may include a smartphone, wireless tablet, wireless-enabled laptop computer, wearable device, machine equipment that can facilitate vehicle telematics, etc. UE 1260 includes a first processor 1230, a second processor 1232, and shared memory 1234. UE 1260 includes a radio front-end circuitry 1262, which may be referred to herein as a transceiver, but should be understood to generally include transceiver circuitry, separate filters, and features for facilitating communication over a wireless link (e.g., Figure 1 A separate antenna for signal transmission and reception of one or more wireless links 125, 135, or 137 shown. Furthermore, transceiver 1262 may include multiple sets of circuitry, or may be tunable to accommodate different frequency ranges, different modulation schemes, or different communication protocols to facilitate long-range wireless links (such as link 125), device-to-device links (such as link 135), and short-range wireless links (such as link 137).

[0138] Continue describing Figure 12 UE 1260 may also include SIM 1264 or SIM profile, which may include information stored in memory (memory 1234 or a separate memory portion) for facilitating communication with... Figure 1 Wireless communication of RAN 105 or core network 130 shown. Figure 12 The SIM 1264 is shown as a single component in the shape of a traditional SIM card, but it will be understood that the SIM 1264 can represent multiple SIM cards, multiple SIM profiles, or multiple eSIMs, some or all of which can be implemented in hardware or software. It will be understood that a SIM profile may include security credentials such as encryption keys, values ​​that can be used to generate encryption keys, or information related to the connection between the SIM 1264 and another device (which may be...). Figure 1 Information shared between components of RAN 105 or core network 130 (as shown in the diagram). SIM profile 1264 may also include unique identification information for that SIM or SIM profile, such as the International Mobile Subscriber Identity (“IMSI”) or information that may constitute an IMSI.

[0139] SIM 1264 is shown coupled to both the first processor portion 1230 and the second processor portion 1232. This implementation offers the advantage that the first processor portion 1230 does not need to request or receive information or data that the second processor 1232 can request from SIM 1264, thus eliminating the use of the first processor as a "man-in-the-middle" when the second processor uses information from the SIM in performing its functions and executing applications. The first processor 1230 (which may be a modem processor or a baseband processor) is shown smaller than processor 1232 (which may be a more complex application processor) to visually indicate the relative level of complexity (i.e., processing power and performance) and the corresponding relative level of operating power consumption between the two processor portions. When the UE 1260 does not require the second processor section 1232 to execute applications and process application-related data, keeping the second processor section 1232 in sleep / inactive / low-power state provides the following advantages: reduced power consumption when the UE only needs to use the first processor section 1230 in listening mode for monitoring routine configuration bearer management and mobility management / maintenance processes, or for monitoring the search space that the UE has been configured to monitor while the second processor section remains inactive / sleep.

[0140] UE 1260 may also include sensors 1266, such as temperature sensors, accelerometers, gyroscopes, barometers, humidity sensors, etc., which can provide signals to the first processor 1230 or the second processor 1232. Output devices 1268 may include, for example, one or more visual displays (e.g., computer monitors, VR devices, etc.), acoustic transducers (such as speakers or microphones), vibration components, etc. Output devices 1268 may include software that interfaces with output devices (e.g., visual displays, speakers, microphones, tactile devices, olfactory or gustatory devices, etc., external to UE 1260).

[0141] The following glossary of terms given in Table 1 may be applied to one or more descriptions of the embodiments disclosed herein. Table 1

[0142] The above description includes non-limiting examples of the various embodiments. It is certainly not possible to describe every conceivable combination of components or methods for the purpose of describing the disclosed subject matter, and those skilled in the art will recognize that further combinations and arrangements of the various embodiments are possible. The disclosed subject matter is intended to cover all such changes, modifications, and variations falling within the spirit and scope of the appended claims.

[0143] Regarding the various functions performed by the aforementioned components, devices, circuits, systems, etc., unless otherwise indicated, the terminology used to describe such components (including references to "device") is intended to also include any structure (e.g., functional equivalent) that performs the specified functions of the described component, even if it is not structurally equivalent to the disclosed structure. Furthermore, while specific features of the disclosed subject matter may be disclosed only with respect to one of several implementations, such features may be combined with one or more other features of other implementations, as may be desirable and advantageous for any given or particular application.

[0144] The terms “exemplary” and / or “illustrative” or variations thereof, as may be used herein, are intended to refer to examples, instances, or illustrations. For the avoidance of ambiguity, the subject matter disclosed herein is not limited to such examples. Furthermore, any aspect or design described herein as “exemplary” and / or “illustrative” is not necessarily to be construed as superior to or advantageous over other aspects or designs, nor does it exclude equivalent structures and techniques known to those skilled in the art. Moreover, with respect to the use of the terms “include,” “have,” “comprising,” and other similar words in the detailed description or claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open-ended transitional phrase—without excluding any additional or other elements.

[0145] The term “or” as used herein is intended to mean inclusive rather than exclusive. For example, the phrase “A or B” is intended to include instances of A, instances of B, and instances of both A and B. Additionally, the articles “a” and “an” as used in this application and the appended claims should generally be interpreted as meaning “one or more” unless otherwise specified or clearly indicated from the context to the singular form.

[0146] The term "set" used in this paper excludes the empty set, i.e., a set containing no elements. Therefore, a "set" in the subject matter disclosure includes one or more elements or entities. Similarly, the term "group" used in this paper refers to a collection of one or more entities.

[0147] The terms “first,” “second,” “third,” etc., used in the claims are for clarity only and do not otherwise indicate or imply any temporal order unless the context clearly states otherwise. For example, “first determination,” “second determination,” and “third determination” do not indicate or imply that the first determination precedes the second determination, or vice versa.

[0148] The description of the illustrative embodiments disclosed herein (including those described in the abstract) is not intended to be exhaustive or to limit the disclosed embodiments to the precise form disclosed. While specific embodiments and examples have been described herein for illustrative purposes, various modifications are possible within the scope of such embodiments and examples, as will be appreciated by those skilled in the art. In this regard, while the subject matter has been described herein in conjunction with various embodiments and corresponding drawings, it should be understood where applicable that other similar embodiments may be used, or modifications and additions may be made to the described embodiments to perform the same, similar, alternative, or substituted functions as the disclosed subject matter without departing from its scope. Therefore, the disclosed subject matter should not be limited to any single embodiment described herein, but should be interpreted broadly and comprehensively in accordance with the appended claims.

Claims

1. A method comprising: A first user equipment including a processor receives a control information report configuration from a radio access network node. The control information report configuration includes at least one resource grant indication, which indicates at least one uplink control channel resource. The at least one uplink control channel resource can be used by the first user equipment to transmit at least one status indication corresponding to a downlink protocol data unit service, which is directed to the first user equipment or to at least one second user equipment communicatively coupled to the first user equipment. The first user equipment receives at least one downlink protocol data unit; as well as The first user equipment transmits at least one status indication to the radio access network node using the at least one uplink control channel resource, the at least one status indication indicating at least one decoding status corresponding to at least one decoding attempt for decoding the at least one downlink protocol data unit.

2. The method according to claim 1, wherein the at least one downlink protocol data unit points to the at least one second user equipment.

3. The method of claim 1, wherein the at least one decoding state corresponds to at least one failure in which the at least one decoding attempt performed by the first user equipment has been determined to have failed to decode the at least one downlink protocol data unit, and wherein the at least one state indication includes at least one negative acknowledgment ("NACK") indicating that the at least one failure in decoding the at least one downlink protocol data unit was unsuccessful.

4. The method of claim 1, wherein the at least one decoding state is a first decoding state, wherein the at least one state indication is a first state indication, wherein the at least one decoding attempt is a first decoding attempt by the first user equipment to decode the at least one downlink protocol data unit, wherein the first decoding state is an acknowledgment indication, the acknowledgment indication indicating that the first result of the first decoding attempt is a successfully decoded downlink protocol data unit, and the method further comprises: The first user equipment stores the successfully decoded downlink protocol data unit into a memory; The first user equipment transmits the successfully decoded downlink protocol data unit to the at least one second user equipment; The first user equipment receives a second status indication from the at least one second user equipment, the second status indication indicating a second decoding attempt by the at least one second user equipment to decode the successfully decoded downlink protocol data unit; as well as Based on the second status indication, the first user equipment performs a communication operation regarding the successfully decoded downlink protocol data unit.

5. The method of claim 4, wherein the second state indication indicates that the second decoding attempt performed by the at least one second user equipment has been determined to have failed to decode the successfully decoded downlink protocol data unit, and wherein the communication operation includes the first user equipment retransmitting the successfully decoded downlink protocol data unit to the at least one second user equipment.

6. The method of claim 5, wherein receiving the second status indication and retransmitting the successfully decoded downlink protocol data unit to the at least one second user equipment helps to avoid the at least one second user equipment transmitting the second status indication to the radio access network node, the second status indication indicating that the at least one second user equipment has not successfully decoded the successfully decoded downlink protocol data unit.

7. The method of claim 6, wherein the second status indication includes a NACK indication.

8. The method of claim 4, wherein the second state indication indicates that the second decoding attempt performed by the at least one second user equipment is determined to be a successful decoding of the successfully decoded downlink protocol data unit, and wherein the communication operation includes the first user equipment clearing the successfully decoded downlink protocol data unit from the memory.

9. The method of claim 1, wherein the first downlink protocol data unit in the at least one downlink protocol data unit points to the first user equipment, wherein the second downlink protocol data unit in the at least one downlink protocol data unit points to the at least one second user equipment, wherein the first status indication in the at least one status indication indicates a first decoding state in the at least one decoding state, the first decoding state corresponding to a first decoding attempt performed by the first user equipment in the at least one decoding attempt to decode the first downlink protocol data unit, and wherein the second status indication in the at least one status indication indicates a second decoding state in the at least one decoding state, the second decoding state corresponding to a second decoding attempt performed by the at least one second user equipment in the at least one decoding attempt to decode the second downlink protocol data unit.

10. The method of claim 9, wherein the control information report configuration includes a transmission multiplexing format indication, the transmission multiplexing format indication specifying a transmission multiplexing format that can be used by the first user equipment to transmit the at least one status indication to the radio access network node, and wherein the first status indication and the second status indication are transmitted according to the status indication multiplexing format using the at least one uplink control channel resource.

11. The method of claim 10, wherein the status indication multiplexing format is one of the following: code division multiplexing format or sequence multiplexing format.

12. An extended reality processing unit, comprising: A processor is configured to process executable instructions that, when executed by the processor, facilitate the execution of operations, including: The system receives a control information report configuration from a radio network node. The control information report configuration includes a resource grant indication that specifies uplink control channel resources. The uplink control channel resources can be used to transmit at least one status indication corresponding to a downlink service, which is directed to an extended reality device communicatively coupled to the extended reality processing unit. Receive downlink packets corresponding to the service flow directed to the extended reality device from the radio network node; An attempt was made to decode the downlink packet to obtain a decoding attempt; and A status indication is transmitted to the radio network node via the uplink control channel resources, the status indication indicating the decoding status corresponding to the decoding attempt.

13. The extended reality processing unit of claim 12, wherein the extended reality device is a first extended reality device, the downlink packet is a first downlink packet, the traffic flow pointing to the extended reality device is a first traffic flow, the decoding attempt is a first decoding attempt, the decoding state is a first decoding state, the state indication is a first state indication indicating the first decoding state, and the operation further includes: Receive a second downlink packet corresponding to a second service flow, the second service flow being directed to a second extended reality device communicatively coupled to the extended reality processing unit; Attempt to decode the second downlink packet to obtain a second decoding attempt; as well as A second status indication is transmitted to the radio network node via the uplink control channel resources. The second status indication indicates a second decoding status corresponding to the second decoding attempt.

14. The extended reality processing unit of claim 13, wherein the first state indication and the second state indication are transmitted in an uplink control information message.

15. The extended reality processing unit of claim 14, wherein the first state indication and the second state indication are multiplexed in the uplink control information message according to one of the following: a code division-based multiplexing format or a sequence-based multiplexing format.

16. The extended reality processing unit of claim 13, wherein the first decoding state corresponds to a first successful decoding of the first downlink packet, wherein the first state indication is an acknowledgment ("ACK") of the first successful decoding of the first downlink packet, and wherein the operation further comprises: Store the first downlink packet in memory; Transmit the first downlink packet to the first extended reality device; In response to transmitting the first downlink packet to the first extended reality device, a third status indication is received, the third status indication indicating a second successful decoding of the first downlink packet by the first extended reality device; as well as In response to receiving the third state indication, the first downlink packet is erased from the memory.

17. The extended reality processing unit of claim 13, wherein the first decoding state corresponds to successful decoding of the first downlink packet, wherein the first state indication is an ACK indicating the successful decoding of the first downlink packet, and wherein the operation further comprises: Store the first downlink packet in memory; Transmit the first downlink packet to the first extended reality device; In response to transmitting the first downlink packet to the first extended reality device, a third status indication is received, the third status indication indicating that the first extended reality device failed to decode the first downlink packet; as well as In response to receiving the third state indication, the first downlink packet is retransmitted to the first extended reality device.

18. The extended reality processing unit of claim 12, wherein the downlink packet is a first downlink packet, wherein the decoding attempt corresponds to the extended reality processing unit not decoding the downlink packet, wherein the status indication includes a negative acknowledgment ("NACK"), and wherein the operation further includes: In response to transmitting the NACK, a second downlink packet is received from the radio network node, the second downlink packet being a retransmission version of the first downlink packet; Successfully decode the second downlink packet to obtain the successfully decoded second downlink packet; Store the successfully decoded second downlink packet into memory; as well as The successfully decoded second downlink packet is transmitted to the extended reality device.

19. A non-transitory machine-readable medium comprising executable instructions that, when executed by a processor of an extended reality processing unit, facilitate the execution of operations, said operations including: The control information report configuration received from the radio network node includes at least one resource grant indication, which indicates at least one control channel resource. The at least one control channel resource can be used to transmit at least one status indication corresponding to an extended reality service, which points to at least one extended reality device communicatively coupled to the extended reality processing unit. A first downlink packet is received from the radio network node, the first downlink packet corresponding to a first extended reality traffic flow, the first extended reality traffic flow being directed to the first extended reality device among the at least one extended reality device; Attempt to decode the first downlink packet to obtain the first decoding attempt; A second downlink packet is received from the radio network node, the second downlink packet corresponding to a second extended reality traffic flow, the second extended reality traffic flow being directed to the second extended reality device among the at least one extended reality device; Attempt to decode the second downlink packet to obtain a second decoding attempt; as well as The first state indication and the second state indication are transmitted to the radio network node using the at least one control channel resource. The first state indication indicates a first decoding state corresponding to the first decoding attempt, and the second state indication indicates a second decoding state corresponding to the second decoding attempt.

20. The non-transitory machine-readable medium of claim 19, wherein the first state indicator is a negative acknowledgment ("NACK"), wherein the second state indicator is an acknowledgment ("ACK"), and wherein the operation further comprises: The second downlink packet is stored in the memory of the extended reality processing unit; The second downlink packet is transmitted to the second extended reality device; In response to transmitting the NACK, a retransmitted version of the first downlink packet is received from the radio network node; The retransmitted version of the first downlink packet is stored in the memory; as well as The retransmitted version of the first downlink packet is transmitted to the first extended reality device.

Images