Encoder selection

Abstract

An apparatus, method, and computer program product are provided for selecting an encoder for network coding. An example method may include receiving one or more encoder information messages from a set of network coding devices, the one or more encoder information messages associated with the set of network coding devices. The example method may also include transmitting a selection indication to at least one selected network coding device of the set of network coding devices, the selection indication indicating that the at least one selected network coding device is selected as an encoder for encoding at least one transport block (TB).

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application serial number 17 / 898,248, entitled “ENCODER SELECTION” and filed on August 29, 2022, which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to a wireless communication system with network coding (NC). Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary neither identifies the key or important elements of all aspects, nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a user equipment (UE) are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to receive one or more encoder information messages from a set of network decoding devices, the one or more encoder information messages being associated with the set of network decoding devices. The memory and the at least one processor coupled to the memory may also be configured to send a selection indication to at least one selected network decoding device in the set of network decoding devices, the selection indication indicating the selection of the at least one selected network decoding device as an encoder for encoding at least one transport block (TB).

[0008] In another aspect of the present disclosure, a method, computer-readable medium, and apparatus at a network decoding device, such as a roadside unit (RSU), a base station, or a user equipment (UE), are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to send an encoder information message to the UE, the encoder information message being associated with the network decoding device. The memory and the at least one processor coupled to the memory may also be configured to receive a selection indication from the UE based on the encoder information message, the selection indication indicating selection of at least one selected network decoding device as an encoder for encoding at least one TB, the at least one selected network decoding device including the network decoding device.

[0009] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0014] Figure 2Dis a diagram illustrating an example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 3 is a diagram illustrating an example of a base station and a network decoding device (such as a road side unit (RSU) or a user equipment (UE)) in an access network.

[0016] Figure 4A is a diagram illustrating example communications between UEs without network decoding.

[0017] Figure 4B is a diagram illustrating example communication between a UE and a network decoding device in case of network decoding.

[0018] Figure 5 is a diagram illustrating example communications between a UE and a network decoding device.

[0019] Figure 6 is a diagram illustrating example communications between a UE, a network entity, and a network coding device.

[0020] Figure 7 is a flow chart of a wireless communication method.

[0021] Figure 8 is a flow chart of a wireless communication method.

[0022] Fig. 9 is a flow chart of a wireless communication method.

[0023] Fig.10 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0024] Fig.11 is a diagram illustrating an example of a hardware implementation for an example network entity.

[0025] Fig.12 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0026] Network decoding can be used to increase system capacity and improve resource utilization. For example, network decoding can be used to reduce the number of retransmissions in the system. Network decoding can make it possible to increase the number of UEs or increase the service per UE while maintaining performance. Network decoding can be performed by a network decoding device such as an RSU, UE, or base station based on a network decoding request from a device. In some cases, instead of having a central network decoding device responsible for performing network decoding in a certain area, it may be beneficial to have multiple network decoding devices in the area to perform network decoding more efficiently. However, among the network decoding devices that may potentially perform network decoding in a certain area, in some cases, a subset of network decoding devices may be more suitable for performing network decoding due to having more power, more unused capabilities, less mobility, and staying in the area for a longer duration. The various aspects provided herein may enable a network decoding device or a network entity to select a subset of network decoding devices from a pool of network decoding devices in a region as an encoder for a transmission block (TB) for network decoding.

[0027] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations in which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0028] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0029] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0030] Thus, in one or more example aspects, specific implementations and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. As an example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0031] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and / or use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases may be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some actual settings, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The various techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0032] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0033] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0034] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0035] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0036] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive signals or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units via a wireless transmission medium.

[0037] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 110. CU110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0038] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as those defined by 3GPP. In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0039] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of communicating with the control plane and user plane of the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0040] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0041] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or communicate with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

[0042] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0043] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. These carriers may or may not be adjacent to each other. The allocation of carriers may be equivalent to DL and UL asymmetric (e.g., more or fewer carriers may be allocated to DL than to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0044] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use a DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more side link channels, such as a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), and a physical side link control channel (PSCCH). D2D communications may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi, LTE, or NR based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. The D2D communication link 158 may be used for side link communications between UEs 104.

[0045] Some examples of sidelink communications may include communications from vehicle to vehicle (V2V), vehicle to infrastructure (V2I) (e.g., from a vehicle-based communication device to a road infrastructure node such as a roadside unit (RSU)), vehicle to network (V2N) (e.g., from a vehicle-based communication device to one or more network nodes such as a base station), vehicle to pedestrian (V2P), cellular vehicle-to-everything (C-V2X), and / or combinations thereof, and / or a vehicle-based communication device communicating with other devices, which may be collectively referred to as vehicle-to-everything (V2X) communications. Sidelink communications may be based on V2X or other D2D communications, such as proximity services (ProSe), etc. In addition to UEs, sidelink communications may also be sent and received by other transmitting and receiving devices such as one or more RSUs 107, etc. Sidelink communications may be exchanged using a sidelink interface. In some aspects, one or more RSUs 107 may communicate with a UE 104 or a RU 140. In some aspects, one or more RSUs 107 may communicate with each other based on a sidelink interface.

[0046] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0047] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0048] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0049] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0050] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or may not be the same. The transmit direction and receive direction of the UE 104 may be the same or may not be the same.

[0051] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a converged (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU.

[0052] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device cluster arrangement. One or more of these devices may access the network collectively and / or individually.

[0053] Reference again Figure 1In some aspects, a network decoding device (such as an RSU 107, a base station 102, or a UE 104) may include an NC component 198. In some aspects, the NC component 198 may be configured to receive one or more encoder information messages from a set of network decoding devices, the one or more encoder information messages being associated with the set of network decoding devices. In some aspects, the NC component 198 may also be configured to send a selection indication to at least one selected network decoding device in the set of network decoding devices, the selection indication indicating the selection of at least one selected network decoding device as an encoder for encoding at least one TB. In some aspects, the NC component 198 may also be configured to send an encoder information message to the UE, the encoder information message being associated with the network decoding device. In some aspects, the NC component 198 may be configured to receive a selection indication from the UE based on the encoder information message, the selection indication indicating the selection of at least one selected network decoding device as an encoder for encoding at least one TB, the at least one selected network decoding device including the network decoding device.

[0054] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2CIn the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0055] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of equal size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4 or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0056]

[0057] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ*15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0058] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0059] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0060] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as a system information block (SIB)), and paging messages.

[0061] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0062] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may be used to carry, among other things, a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0063] Figure 3 3 is a block diagram of a base station 310 in an access network communicating with a network decoding device 350 (such as a UE, base station, or RSU). In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0064] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates can be derived from reference signals and / or channel condition feedback sent by network decoding equipment 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx can modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0065] At the network decoding device 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the network decoding device 350. If the destination of multiple spatial streams is the network decoding device 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then uses a fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0066] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0067] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0068] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0069] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the network decoding device 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0070] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0071] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to combine Figure 1 The NC component 198 is used to perform various aspects.

[0072] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to combine Figure 1 The NC component 198 is used to perform various aspects.

[0073] In some wireless communication systems, network coding (NC) can be used to increase system capacity and improve resource utilization. For example, network coding can be used to reduce the number of retransmissions in the system. Network coding can enable the number of UEs to be increased or the service per UE to be increased while maintaining performance. Based on network coding, after an initial transmission, the retransmission of the original sender can be replaced by network coding. For example, Figure 4A 4 is a diagram illustrating example communications between UEs without network decoding. Figure 4A , UE 402A may send a transmission (TXa) to UE 402C. UE 402B may send a transmission (TXb) to UE 402D. In some aspects, UE 402A may also send a transmission (e.g., TXa) to UE 402D, and UE 402B may also send a transmission (e.g., TXb) to UE 402C. As an example, a transmission (e.g., TXa) from UE 402A to UE 402D may collide with another transmission (such as TXb), causing the transmission from UE 402A to UE 402D to be lost. As another example, a transmission (e.g., TXb) from UE 402B to UE 402C may collide with another transmission (such as TXa), causing the transmission from UE 402B to UE 402C to be lost.

[0074] Figure 4B 450 is a diagram illustrating an example communication between a UE and a network decoding device in the case of network decoding. Figure 4BAs illustrated in , UE 452A may send a transmission (e.g., TXa) to network decoding device 454 and UE 452B may also send a transmission (e.g., TXb) to network decoding device 454. Network decoding device 454 may be an RSU or UE that may be capable of performing network decoding. After receiving a transmission (e.g., TXa) from UE 452A and a transmission (e.g., TXb) from UE 452B, network decoding device 454 may encode the two transmissions (e.g., TXa and TXb) into the same transmission (e.g., f(TXa, Txb)). For example, network decoding device 454 may combine packets from two transmissions (e.g., TXa and TXb) to mix together. In some aspects, packets from two transmissions (e.g., TXa and TXb) may be encoded and mixed so that the number of encoded packets in transmission f(TXa, Txb) may be less than the total number of packets in the two transmissions. In conventional routing, packets may be stored and forwarded without packet combination. Using network decoding, transmit data from one transmission may be encoded with other transmit data from another transmission. A receiver may receive a combined transmission, which may include an encoding of transmit data from one transmission with other transmit data from another transmission. Different receivers or the same receiver may decode the combined transmission in different ways to decode transmit data from either transmission.

[0075] The network coding device 454 may send the transmission f(TXa, TXb) to both the UE 452C and the UE 452D. The transmission f(TXa, TXb) may be decoded by the UE 452C and the UE 452D. Depending on the decoding performed by the UE 452C and the UE 452D, both transmissions (e.g., TXa and TXb) may be decoded based on the transmission f(TXa, TXb). Therefore, network throughput and capacity may be improved by using network coding.

[0076] In some aspects, network decoding may be based on linear decoding, random network decoding, erasure coding, etc. In some aspects, erasure coding may be based on erasure coding. The erasure code may be a forward error correction code that transforms a message of k symbols into a message of n symbols, where n and k are positive integers, and n may be greater than or equal to k. In some aspects, the k symbols may be recovered by decoding a message of n symbols. For example, k symbols may be recovered from a subset of n symbols. In some aspects, a parity check may be performed that may be based on a single parity check code. For example, a network decoding device may receive a first message of one or more symbols collectively referred to as a, a second message of one or more symbols collectively referred to as b, and a third message of one or more symbols collectively referred to as c. The input for network decoding may be [a, b, c], and the network decoding device may encode the input as It can then be sent in a combined send. can represent a direct sum. In some aspects, any single erasure can be recovered. For example, if the received vector is The erased elements can be restored by summing the other elements: In some aspects, this erasure decoding can be viewed as a linear system (over a Galois field containing a finite number of elements) with three variables and four linearly independent constraints:

[0077]

[0078] In such a linear system, any three constraints (eg, one erasure) may be sufficient to determine the three variables.

[0079] Figure 5 is a diagram 500 illustrating example communications between a UE and a network coding device. Figure 5 An example protocol for sidelink communication using network decoding is illustrated. Figure 5 , UE 502A may be intended to send a TB to UE 502B. UE 502A may send the TB to a network decoding device 506 along with a network decoding request 508. In some aspects, the network decoding request 508 may be a network decoding request tag. In some aspects, the network decoding device 506 may be an RSU, a UE, a base station, etc. In some aspects, the network decoding device 506 may accept the network decoding request 508 upon receiving the network decoding request 508. In some aspects, the network decoding device 506 may accept the network decoding request 510 by sending a message to UE 502A indicating acceptance of the request 508. In some aspects, accepting the network decoding request 508 may require accepting encoding of the TB sent along with the network decoding request 508 as part of the network decoding transmission. In some aspects, after sending a message to UE 502A indicating acceptance of request 510, network decoding device 506 may perform network decoding at 512, which may be based on various coding schemes, such as linear coding, random network coding, erasure coding, etc. Performing network decoding at 512 may include encoding the TB sent with the network decoding request 508 as part of network decoding transmission 514. In some aspects, after performing network decoding at 512, network decoding device 506 may send network decoding transmission 514 to UE 502B so that UE 502B may decode network decoding transmission 514 to recover the TB sent with the network decoding request 508. In some aspects, one or more other TBs may be encoded in network decoding transmission 514. In some aspects, the network decoding device 506 may also transmit the network decoding transmission 514 to one or more other recipients associated with the one or more other TBs so that the one or more other recipients may recover the one or more other TBs upon receiving the network decoding transmission 514 .

[0080] Network decoding can be used to increase system capacity and improve resource utilization. For example, network decoding can be used to reduce the number of retransmissions in the system. Network decoding can make it possible to increase the number of UEs or increase the service per UE while maintaining performance. Network decoding can be performed by a network decoding device such as an RSU, UE, or base station based on a network decoding request from a device. In some cases, instead of having a central network decoding device responsible for performing network decoding in a certain area, it may be beneficial to have multiple network decoding devices in the area to perform network decoding more efficiently. However, among the network decoding devices that may potentially perform network decoding in a certain area, in some cases, a subset of network decoding devices may be more suitable for performing network decoding due to having more power, more unused capabilities, less mobility, and staying in the area for a longer duration. The various aspects provided herein may enable a network decoding device or a network entity to select a subset of network decoding devices from a pool of network decoding devices in a region as an encoder for a transmission block (TB) for network decoding.

[0081] Figure 6 600 is an example communication diagram illustrating a UE 602A, a network decoding device or network entity 604, and network decoding devices 606A and 606B. In some aspects, the network decoding device or network entity 604 may be a network node. The network node may be implemented as an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, a side link node, etc. The network entity may be implemented in an aggregated or monolithic base station architecture, or alternatively in a decomposed base station architecture, and may include one or more of a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. In some aspects, the network decoding device 606A may be an RSU, a UE, a base station, or other devices that may be capable of performing network decoding. In some aspects, the network decoding device 606B may be an RSU, a UE, a base station, or other devices that may be capable of performing network decoding.

[0082] In some aspects, at 611, the network decoding device or network entity 604 may determine that there may be an insufficient number of selected encoders for network decoding in an area associated with the network decoding device or network entity 604. The area may be a physical area or zone that may be defined by a network associated with the network decoding device or network entity 604 where the network decoding device or network entity 604 is currently located. An example of the area may be an area around a road intersection, such as 400m×400m. Another example may be an area associated with an autonomous vehicle platoon. In some aspects, at 611, the network decoding device or network entity 604 may determine that there may be an insufficient number of selected encoders for network decoding in the area based on a variety of reasons such as a network decoding encoder leaving an area associated with the network decoding device or network entity 604, or a surge in the number of devices (e.g., UEs) in the area, or a surge in the side link traffic in the area. In some aspects, to make the determination at 611, at 610, the network decoding device or network entity 604 may monitor mobility information or sidelink traffic associated with one or more UEs in the area, such as UE 602A and UE 602B, or one or more network decoding devices in the area, such as network decoding device 606A and network decoding device 606B. For example, in some aspects, the network decoding device or network entity 604 may receive information 608A from UE 602A indicating mobility of UE 602A. In some aspects, the information 608A may be sent based on the PSCCH or PSSCH when UE 602A is moving. In some aspects, the information 608A may include a UE identifier (ID) associated with the UE 602A, a zone identifier (ID) associated with the UE 602A (which may be a new zone ID associated with the zone to which the UE 602A is moving), global navigation satellite system (GNSS) information associated with the UE 602A, signaling traffic load related statistics associated with the UE 602A, etc. Similarly, the network decoding device or network entity 604 may also receive information 608B from the network decoding device 606A, information 608C from the network decoding device 606B, or information 608D from the UE 602B. Based on the received information 608A, 608B, 608C, and 608D, the network decoding device or network entity 604 may make a determination at 611.

[0083] In some aspects, upon determining that there may be an insufficient number of selected encoders for network decoding in an area associated with the network decoding device or network entity 604, the network decoding device or network entity 604 may send a report request 612 to one or more network decoding devices in the area (such as network decoding device 606A and network decoding device 606B). The report request may be a signaling requesting a report of a condition associated with selecting a network decoding device. In some aspects, if the network decoding device or network entity 604 is a base station, the report request 612 may be sent via downlink control information (DCI). In some aspects, the report request 612 may be broadcast to all network decoding devices in the area. In some aspects, if the network decoding device or network entity 604 is a network decoding device acting as an encoder head (e.g., a network decoding device responsible for selecting a network decoding device), the report request 612 may be sent via sidelink control information (SCI) such as SCI format 2 (SCI-2), a medium access control (MAC) control element (MAC-CE), a MAC header, etc.

[0084] Upon receiving the report request 612, the network decoding devices in the area (such as network decoding devices 606A and network decoding devices 606B) may send a status report 614 to the network decoding device or network entity 604. The status report may be a report from the network decoding device to the network entity or another network decoding device to facilitate the selection of the network decoding device for network decoding. The status report 614 may include one or more of the following: a GNSS location or zone ID of the network decoding device, movement information associated with the network decoding device (such as speed or destination), a remaining battery charge associated with the network decoding device, whether the network decoding device is connected to a power source for charging, whether the network decoding device has acted as a network encoder (e.g., for another area), one or more channel-related statistics of the network decoding device such as reference signal received power (RSRP)-related statistics, RSRP-related statistics of other devices, RSRP-related statistics (e.g., average RSRP) of one or more other devices in the group (e.g., classified based on the group ID), etc. In some aspects, if the network decoding device or network entity 604 is a base station, the status report 614 may be sent via a buffer status report (BSR), or a physical uplink shared channel (PUSCH). In some aspects, if the size of the status report 614 is greater than a threshold, the status report may be sent via the PUSCH. In some aspects, if the network decoding device or network entity 604 is a network decoding device, the status report 614 may be sent via an SCI, a MAC-CE, a MAC header, or a physical sidelink shared channel (PSSCH). If the size of the status report 614 is greater than a threshold, the status report may be sent via the PSSCH.

[0085] In some aspects, at 616, the network decoding device or network entity 604 may select one or more network decoding devices (e.g., network decoding device 606A) to act as a network decoding encoder based on the received status report (e.g., status report 614). In some aspects, the network decoding device or network entity 604 may calculate information related to one or more network decoding devices, such as: 1) how long the device can stay in the area; 2) the remaining power associated with the device and whether the device is connected for charging; 3) the channel performance associated with the device; 4) whether the device is busy with its own business and the potential capacity remaining for network decoding. Based on the calculated information, the network decoding device or network entity 604 may rank one or more network decoding devices and select one or more top-ranked network decoding devices to act as network decoding encoders. As an example, relatively stationary, fully charged, and more capable devices may be ranked higher.

[0086] In some aspects, the configuration of the methods associated with calculation and ranking may be configured at the network coding device or network entity 604 without signaling from the network. In some aspects, the configuration of the methods associated with calculation and ranking may be configured at the network coding device or network entity 604 based on signaling from a network entity.

[0087] In some aspects, upon determining that there may be an insufficient number of selected encoders for network decoding in an area associated with the network decoding device or network entity 604, the network decoding device or network entity 604 may not send a report request and may directly select one or more network decoding devices (e.g., network decoding device 606A) at 616 to act as network decoding encoders.

[0088] When one or more network decoding devices (e.g., network decoding device 606A) are selected at 616 to act as a network decoding encoder, the network decoding device or network entity 604 may send a selection indication 618 to indicate the selected network decoding device. The selection indication may be signaling for indicating the selected network decoding device for network decoding. In some aspects, the selection indication 618 may be sent based on a unicast. In some aspects, the selection indication 618 may be sent based on a broadcast. In some aspects, upon receiving the selection indication 618, the selected network decoding device (e.g., network decoding device 606A) may send an acknowledgement (ACK) or a negative acknowledgement (NACK) 620 to the network decoding device or network entity 604. In some aspects, the ACK / NACK 620 may be sent using uplink control information (UCI) or a scheduling request (SR). If the selected network decoding device sends an ACK, then in some aspects, UE 602A may send TB622 to the selected network decoding device (e.g., network decoding device 606A) so that the selected network decoding device (e.g., network decoding device 606A) may perform network decoding on the TB (e.g., at 624) and forward the TB to the destination of the TB (e.g., UE 602B) in sending 626.

[0089] In some aspects, under certain conditions such as anticipating leaving the area or leaving a queue group associated with the network decoding device or network entity 604 (a queue group may be a group assigned by the network that may include one or more other UEs such as UE 602A and UE 602B), the network decoding device or network entity 604 may send an encoder head indication 628 to a network decoding device (e.g., network decoding device 606A), so that the network decoding device may be responsible for making future decisions to select network decoding devices (e.g., similar to the responsibility of the network decoding device or network entity 604 in the process described in conjunction with 611-618). In some aspects, a queue may be associated with autonomous vehicles (e.g., associated with each UE), some of which form a group and follow one another. Devices within a queue group may communicate with each other to share sensor data, etc., to make it safer for the vehicle.

[0090] In some aspects, UE 602A may receive information from each of network decoding device 606A, network decoding device 606B, or one or more other network decoding devices. The information may be broadcast to one or more UEs and may indicate that network decoding device 606A, network decoding device 606B, or one or more other network decoding devices can act as a network encoder, respectively. The information may include GNSS information associated with network decoding device 606A, network decoding device 606B, or one or more other network decoding devices and one or more parameters indicating that the network decoding device can act as a network encoder (the one or more parameters may also include capabilities associated with the network decoding device). The information may be sent via an SCI such as SCI-2, MAC-CE, MAC header or subheader, RRC message, etc. In some aspects, at 615, UE 602A may select one or more of network decoding device 606A, network decoding device 606B, or one or more other network decoding devices to act as a network encoder for transmitting or retransmitting a TB (e.g., TB 622) based on information about network decoding device 606A, network decoding device 606B, or one or more other network decoding devices, such as capabilities, distance (between UE 602A and the network decoding device), etc., respectively. In some aspects, UE 602A may select one network decoding device associated with an RSRP above a threshold. In some aspects, UE 602A may select a network decoding device (of network decoding device 606A, network decoding device 606B, or one or more other network decoding devices) that covers a wider range associated with an RSRP above a threshold (e.g., based on the distance between the decoding devices).

[0091] A TB (e.g., TB 622) may include one or more IDs associated with the selected network decoding device (e.g., in a header). In some aspects, in addition to the packet ID and UE ID, the header of the TB may also include another ID so that the selected encoder may use the same configuration to collect feedback for the TB in the NC packet using another ID. Each TB of the packet may use one PSFCH for feedback. In some aspects, if a TB is carried in a different network decoding packet associated with a different selected network encoder, a different ID may be used for the same TB. In some aspects, the same ID (e.g., another ID) may be used for different network decoding packets, and if one encoder monitors the NC packets transmitted from other encoders, the encoder may calculate the expected time slot for feedback from another ID. In some aspects, the ID of the TB may also be included in the header of the NC packet. In some aspects, another ID may be calculated by hashing the packet ID and the UE ID, and all UEs and encoders may know the hash so that the UEs and encoders may know the other ID without including it in the NC packet. Therefore, feedback for a TB of an encoder may be understood by other encoders associated with the TB. In some aspects, the header of the TB may include information for coordinating network decoding transmissions from different encoders (network decoding device 606A, network decoding device 606B, or two or more selected encoders in one or more other network decoding devices) to avoid the encoders from simultaneously transmitting transmissions carrying TBs (e.g., including transmission 626). For example, a transmission sequence associated with each encoder may be included (e.g., indicating which encoder may transmit first, which encoder may transmit second, etc.). The second encoder in the sequence may not transmit the TB until the first encoder has transmitted the TB. In some aspects, the time slot range associated with each encoder for transmitting the TB may be included in the header. For example, the first encoder may transmit in time slot 3n, the second encoder may transmit in time slot 3n+1, the third encoder may transmit in time slot 3n+2, etc.

[0092] Figure 7 700 is a flow chart of a wireless communication method. The method may be performed by a network node (eg, UE 104, UE 602A; device 1004, network entity 1002).

[0093] At 702, UE 602A may receive one or more encoder information messages from a network decoding device set, the one or more encoder information messages being associated with the network decoding device set. For example, UE 602A may receive one or more encoder information messages (e.g., 608A, 608B, 608C, or 608D) from a network decoding device set, the one or more encoder information messages being associated with the network decoding device set. In some aspects, 702 may be performed by NC component 198.

[0094] At 704, UE 602A may send a selection indication to at least one selected network decoding device in the set of network decoding devices, the selection indication indicating the selection of at least one selected network decoding device as an encoder for encoding at least one TB. For example, UE 602A may send a selection indication (e.g., 618) to at least one selected network decoding device in the set of network decoding devices, the selection indication indicating the selection of at least one selected network decoding device as an encoder for encoding at least one TB. In some aspects, 704 may be performed by NC component 198.

[0095] Figure 8 800 is a flow chart of a wireless communication method. The method may be performed by a network node (eg, UE 104, UE 602A; device 1004, network entity 1002).

[0096] At 802, UE 602A may receive one or more encoder information messages from a network decoding device set, the one or more encoder information messages being associated with the network decoding device set. For example, UE 602A may receive one or more encoder information messages (e.g., 608A, 608B, 608C, or 608D) from a network decoding device set, the one or more encoder information messages being associated with the network decoding device set. In some aspects, 802 may be performed by NC component 198. In some aspects, the encoder information message may include a capability indication indicating the ability to act as an encoder associated with a network decoding device. In some aspects, the encoder information message may include a GNSS location associated with a network decoding device. In some aspects, the encoder information message may include one or more of the following: a zone ID associated with a network decoding device, mobile information including a speed or destination associated with a network decoding device, a remaining amount of power associated with a network decoding device, a coverage indication indicating a coverage area associated with a network decoding device, a power charging indication associated with a network decoding device, or one or more RSRP statistics associated with a network decoding device. In some aspects, at least one selected network decoding device is associated with a maximum coverage area in a subset of a set of network decoding devices, and wherein the subset of the set of network decoding devices is associated with an RSRP above a threshold. In some aspects, at least one selected network decoding device is randomly selected in a subset of a set of network decoding devices, and wherein the subset of the set of network decoding devices is associated with an RSRP above a threshold. In some aspects, the encoder information message is received via an SCI, a MAC-CE, a MAC header, an RRC message, or a PSSCH.

[0097] At 803, UE 602A may select at least one selected network decoding device as an encoder for encoding at least one TB. For example, UE 602A may select at least one selected network decoding device as an encoder for encoding at least one TB (e.g., at 615). In some aspects, 803 may be performed by NC component 198.

[0098] At 804, UE 602A may send a selection indication to at least one selected network decoding device in the set of network decoding devices, the selection indication indicating the selection of at least one selected network decoding device as an encoder for encoding at least one TB. For example, UE 602A may send a selection indication (e.g., 618) to at least one selected network decoding device in the set of network decoding devices, the selection indication indicating the selection of at least one selected network decoding device as an encoder for encoding at least one TB. In some aspects, 804 may be performed by NC component 198. In some aspects, a header of at least one TB is associated with a feedback ID, a packet ID, and a UE ID associated with the UE, the feedback ID being used to calculate an expected time slot for feedback representing an ACK or NACK for at least one TB. In some aspects, the feedback ID is represented via a hash, a hash function, or a hash procedure. In some aspects, a header of at least one TB may include first information representing a transmission sequence for each network decoding device in at least one selected network decoding device. In some aspects, the header of at least one TB may include first information indicating a time slot indication that a time slot for each of at least one selected network decoding device is available for transmission. In some aspects, the header of at least one TB may include at least one encoder ID of at least one selected network decoding device.

[0099] Fig. 9 900 is a flow chart of a wireless communication method. The method may be performed by a network decoding device (eg, UE 104, RSU 107, network decoding device 606A / 606B; apparatus 1104, network entity 1202).

[0100] At 902, the network decoding device may send an encoder information message to the UE, the encoder information message being associated with the network decoding device. For example, the network decoding device 606A may send an encoder information message (e.g., 608A) to the UE, the encoder information message being associated with the network decoding device. In some aspects, 902 may be performed by the NC component 198.

[0101] At 904, the network decoding device may receive a selection indication from the UE based on the encoder information message, the selection indication indicating the selection of at least one selected network decoding device as an encoder for encoding at least one TB, the at least one selected network decoding device including the network decoding device. For example, the network decoding device 606A may receive a selection indication (e.g., 618) from the UE 104 based on the encoder information message, the selection indication indicating the selection of at least one selected network decoding device as an encoder for encoding at least one TB, the at least one selected network decoding device including the network decoding device. In some aspects, 904 may be performed by the NC component 198.

[0102] Fig.10 1000 is a flow chart of a wireless communication method. The method may be performed by a network decoding device (eg, UE 104, RSU 107, network decoding device 606A / 606B; apparatus 1104, network entity 1202).

[0103] At 1002, the network decoding device may send an encoder information message to the UE, and the encoder information message is associated with the network decoding device. For example, the network decoding device 606A may send an encoder information message (e.g., 608A) to the UE, and the encoder information message is associated with the network decoding device. In some aspects, 1002 may be performed by the NC component 198. In some aspects, the encoder information message may include a capability indication, which indicates the ability to act as an encoder associated with the network decoding device. In some aspects, the encoder information message may include a GNSS position associated with the network decoding device. In some aspects, the encoder information message may include one or more of the following: a zone ID associated with the network decoding device, mobile information including a speed or destination associated with the network decoding device, a remaining power associated with the network decoding device, a coverage indication representing a coverage area associated with the network decoding device, a power charging indication associated with the network decoding device, or one or more RSRP statistics associated with the network decoding device. In some aspects, at least one selected network decoding device is associated with a maximum coverage area in a subset of a set of network decoding devices, and wherein the subset of the set of network decoding devices is associated with an RSRP above a threshold. In some aspects, at least one selected network decoding device is randomly selected in a subset of a set of network decoding devices, and wherein the subset of the set of network decoding devices is associated with an RSRP above a threshold. In some aspects, the encoder information message is sent via SCI, MAC-CE, MAC header, RRC message, or PSSCH.

[0104] At 1004, the network decoding device may receive a selection indication from the UE based on the encoder information message, the selection indication indicating the selection of at least one selected network decoding device as an encoder for encoding at least one TB, the at least one selected network decoding device including the network decoding device. For example, the network decoding device 606A may receive a selection indication (e.g., 618) from the UE 104 based on the encoder information message, the selection indication indicating the selection of at least one selected network decoding device as an encoder for encoding at least one TB, the at least one selected network decoding device including the network decoding device. In some aspects, 1004 may be performed by the NC component 198.

[0105] At 1006, the network decoding device may encode at least one TB based on the selection indication (e.g., 624) and send the encoded at least one TB (e.g., 626). For example, the network decoding device 606A may encode at least one TB based on the selection indication and send the encoded at least one TB. In some aspects, 1006 may be performed by the NC component 198. In some aspects, the header of at least one TB is associated with a feedback ID, a packet ID, and a UE ID associated with the UE, and the feedback ID is used to calculate the expected time slot of the feedback representing the ACK or NACK for the at least one TB. In some aspects, the feedback ID is represented via a hash, a hash function, or a hash procedure. In some aspects, the header of at least one TB may include first information representing a transmission sequence for each network decoding device in at least one selected network decoding device. In some aspects, the header of at least one TB may include first information representing a time slot indication that a time slot for each network decoding device in at least one selected network decoding device can be sent. In some aspects, the header of at least one TB may include at least one encoder ID of at least one selected network decoding device.

[0106] Fig.111100 is a diagram illustrating an example of a hardware implementation for an apparatus 1104. The apparatus 1104 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1104 may include a cellular baseband processor 1124 (also referred to as a modem) coupled to one or more transceivers 1122 (e.g., a cellular RF transceiver). The cellular baseband processor 1124 may include on-chip memory 1124'. In some aspects, the apparatus 1104 may also include one or more subscriber identity module (SIM) cards 1120 and an application processor 1106 coupled to a secure digital (SD) card 1108 and a screen 1110. The application processor 1106 may include on-chip memory 1106'. In some aspects, the device 1104 may also include a Bluetooth module 1112, a WLAN module 1114, a satellite system module 1116 (e.g., a GNSS module), one or more sensor modules 1118 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1126, a power source 1130, and / or a camera 1132. The Bluetooth module 1112, the WLAN module 1114, and the satellite system module 1116 may include an on-chip transceiver (TRX) / receiver (RX). The cellular baseband processor 1124 communicates with the UE 104 and / or with a RU associated with the network entity 1102 through the transceiver 1122 via one or more antennas 1180. The cellular baseband processor 1124 and the application processor 1106 may each include a computer-readable medium / memory 1124', 1106', respectively. The additional memory module 1126 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1124', 1106', 1126 may be non-transitory. The cellular baseband processor 1124 and the application processor 1106 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 1124 / application processor 1106, enables the cellular baseband processor 1124 / application processor 1106 to perform the various functions described herein. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1124 / application processor 1106 when executing the software. The cellular baseband processor 1124 / application processor 1106 may be a component of the network decoding device 350 and may include the memory 360 and / or at least one of the TX processor 368 , the RX processor 356 , and the controller / processor 359 .In one configuration, the device 1104 may be a processor chip (modem and / or applications) and include only the cellular baseband processor 1124 and / or the application processor 1106, and in another configuration, the device 1104 may be an entire UE (eg, see. Figure 3 350) and includes additional modules of device 1104.

[0107] As discussed herein, in some aspects, the NC component 198 may be configured to receive one or more encoder information messages from a set of network decoding devices, the one or more encoder information messages being associated with the set of network decoding devices. In some aspects, the NC component 198 may also be configured to send a selection indication to at least one selected network decoding device in the set of network decoding devices, the selection indication indicating the selection of at least one selected network decoding device as an encoder for encoding at least one TB. In some aspects, the NC component 198 may also be configured to send an encoder information message to the UE, the encoder information message being associated with the network decoding device. In some aspects, the NC component 198 may be configured to receive a selection indication from the UE based on the encoder information message, the selection indication indicating the selection of at least one selected network decoding device as an encoder for encoding at least one TB, the at least one selected network decoding device including the network decoding device.

[0108] As shown, the device 1104 may include multiple components configured for various functions. In one configuration, the device 1104 (and specifically, the cellular baseband processor 1124 and / or the application processor 1106) includes a component for receiving one or more encoder information messages from a network decoding device set, and the one or more encoder information messages are associated with the network decoding device set. In some aspects, the device 1104 may also include a component for sending a selection indication to at least one selected network decoding device in the network decoding device set, and the selection indication indicates the selection of at least one selected network decoding device as an encoder for encoding at least one TB. In some aspects, the device 1104 may also include a component for selecting at least one selected network decoding device as an encoder for encoding at least one TB. The component may be an NC component 198 of the device 1104 configured to perform the function recorded by the component. As described herein, the device 1104 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, a component may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the component.

[0109] Fig.121200 is a diagram illustrating an example of a hardware implementation for a network entity 1202. The network entity 1202 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1202 may include at least one of a CU 1210, a DU 1230, or a RU 1240. For example, depending on the layer functionality handled by the NC component 198, the network entity 1202 may include a CU 1210; both a CU 1210 and a DU 1230; each of the CU 1210, the DU 1230, and the RU 1240; the DU 1230; both a DU 1230 and a RU 1240; or a RU 1240. The CU 1210 may include a CU processor 1212. The CU processor 1212 may include an on-chip memory 1212'. In some aspects, the CU 1210 may also include an additional memory module 1214 and a communication interface 1218. CU 1210 communicates with DU 1230 via a midhaul link, such as an F1 interface. DU 1230 may include a DU processor 1232. DU processor 1232 may include on-chip memory 1232'. In some aspects, DU 1230 may also include an additional memory module 1234 and a communication interface 1238. DU 1230 communicates with RU 1240 via a fronthaul link. RU 1240 may include a RU processor 1242. RU processor 1242 may include on-chip memory 1242'. In some aspects, RU 1240 may also include an additional memory module 1244, one or more transceivers 1246, an antenna 1280, and a communication interface 1248. RU 1240 communicates with UE 104. On-chip memory 1212', 1232', 1242' and additional memory modules 1214, 1234, 1244 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1212, 1232, 1242 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0110] As discussed above, in some aspects, the NC component 198 may be configured to receive one or more encoder information messages from a set of network decoding devices, the one or more encoder information messages being associated with the set of network decoding devices. In some aspects, the NC component 198 may also be configured to send a selection indication to at least one selected network decoding device in the set of network decoding devices, the selection indication indicating the selection of at least one selected network decoding device as an encoder for encoding at least one TB. In some aspects, the NC component 198 may also be configured to send an encoder information message to the UE, the encoder information message being associated with the network decoding device. In some aspects, the NC component 198 may be configured to receive a selection indication from the UE based on the encoder information message, the selection indication indicating the selection of at least one selected network decoding device as an encoder for encoding at least one TB, the at least one selected network decoding device including the network decoding device.

[0111] The NC component 198 may be within one or more processors of one or more of the CU 1210, the DU 1230, and the RU 1240. The NC component 198 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. The network entity 1202 may include a variety of components configured for various functions. In one configuration, the network entity 1202 includes a component for sending an encoder information message to the UE, the encoder information message being associated with a network decoding device. The network entity 1202 may also include a component for receiving a selection indication from the UE based on the encoder information message, the selection indication indicating the selection of at least one selected network decoding device as an encoder for encoding at least one TB, the at least one selected network decoding device including the network decoding device. The network entity 1202 may also include a component for encoding at least one TB based on the selection indication. The network entity 1202 may also include a component for sending the encoded at least one TB. The means may be the NC component 198 of the network entity 1202 configured to perform the functions recited by the means. As described above, the network entity 1202 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, the means may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the means.

[0112] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The attached method claims provide the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0113] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ......", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0114] As used in this disclosure outside of the claims, the phrase "based on" includes all interpretations and should not be limited to any single interpretation unless specifically recorded or indicated as such. For example, the phrase "based on A" (where "A" may be information, a condition, a factor, etc.) may be interpreted as: "at least based on A", "partially based on A", "at least partially based on A", "only based on A" or "based on A alone". Therefore, as disclosed herein, in one aspect, "based on A" may refer to "at least based on A". In another aspect, "based on A" may refer to "partially based on A". In another aspect, "based on A" may refer to "at least partially based on A". In another aspect, "based on A" may refer to "only based on A". In another aspect, "based on A" may refer to "based on A alone". In another aspect, "based on A" may refer to any combination of alternative interpretations. As used in the claims, the phrase "based on A" should be interpreted as "at least based on A", unless otherwise specifically stated.

[0115] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0116] Aspect 1 is an apparatus for communicating at a UE, the apparatus comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and, based at least in part on information stored in the memory, the at least one processor being configured to: receive one or more encoder information messages from a set of network decoding devices, the one or more encoder information messages being associated with the set of network decoding devices; and send a selection indication to at least one selected network decoding device in the set of network decoding devices, the selection indication indicating selection of the at least one selected network decoding device as an encoder for encoding at least one TB.

[0117] Aspect 2 is an apparatus according to aspect 1, wherein each of the one or more encoder information messages may include a capability indication indicating the ability to act as the encoder associated with the corresponding network decoding device in the set of network decoding devices.

[0118] Aspect 3 is an apparatus according to any one of aspects 1 to 2, wherein each of the one or more encoder information messages may include a GNSS position associated with a corresponding network decoding device in the set of network decoding devices.

[0119] Aspect 4 is an apparatus according to any one of Aspects 1 to 3, wherein each of the one or more encoder information messages may include one or more of the following: a zone ID associated with a corresponding network decoding device in the set of network decoding devices, movement information including a speed or destination associated with the corresponding network decoding device in the set of network decoding devices, a remaining power associated with the corresponding network decoding device in the set of network decoding devices, a coverage indication representing a coverage area associated with the corresponding network decoding device in the set of network decoding devices, a power charging indication associated with the corresponding network decoding device in the set of network decoding devices, or one or more RSRP statistics associated with the corresponding network decoding device in the set of network decoding devices.

[0120] Aspect 5 is an apparatus according to any one of aspects 1 to 4, wherein the at least one processor is configured to: select the at least one selected network decoding device as the encoder for encoding the at least one TB.

[0121] Aspect 6 is an apparatus according to any one of Aspects 1 to 5, wherein the at least one selected network decoding device is associated with a maximum coverage area in a subset of the set of network decoding devices, and wherein the subset of the set of network decoding devices is associated with an RSRP above a threshold.

[0122] Aspect 7 is an apparatus according to any one of Aspects 1 to 5, wherein the at least one selected network decoding device is randomly selected from a subset of the set of network decoding devices, and wherein the subset of the set of network decoding devices is associated with an RSRP above a threshold.

[0123] Aspect 8 is an apparatus according to any one of Aspects 1 to 7, wherein the header of the at least one TB is associated with a feedback ID, a group ID, and a UE ID associated with the UE, and the feedback ID is used to calculate an expected time slot representing feedback of ACK or NACK for the at least one TB.

[0124] Aspect 9 is an apparatus according to any one of aspects 1 to 8, wherein the feedback ID is represented via a hash, a hash function, or a hash procedure.

[0125] Aspect 10 is an apparatus according to any one of aspects 1 to 9, wherein a header of the at least one TB may include first information indicating a transmission sequence for each of the at least one selected network decoding device.

[0126] Aspect 11 is an apparatus according to any one of aspects 1 to 10, wherein the header of the at least one TB may include first information indicating a time slot indication for available transmission of a time slot for each of the at least one selected network decoding device.

[0127] Aspect 12 is an apparatus according to any one of aspects 1 to 11, wherein a header of the at least one TB may include at least one encoder ID of the at least one selected network coding device.

[0128] Aspect 13 is an apparatus according to any one of Aspects 1 to 12, wherein the one or more encoder information messages are received via sidelink control information (SCI), a medium access control (MAC) control element (CE) (MAC-CE), a MAC header, a radio resource control (RRC) message, or a physical sidelink shared channel (PSSCH).

[0129] Aspect 14 is an apparatus according to any one of aspects 1 to 13, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna is configured to send the selection indication.

[0130] Aspect 15 is an apparatus for communicating at a network decoding device, the apparatus comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and, based at least in part on information stored in the memory, the at least one processor being configured to: send an encoder information message to a UE, the encoder information message being associated with the network decoding device; and receive a selection indication from the UE based on the encoder information message, the selection indication indicating selection of at least one selected network decoding device as an encoder for encoding at least one TB, the at least one selected network decoding device including the network decoding device.

[0131] Aspect 16 is the apparatus according to aspect 15, wherein the encoder information message may include a capability indication indicating a capability of acting as the encoder associated with the network coding device.

[0132] Aspect 17 is an apparatus according to any one of aspects 15 to 16, wherein the encoder information message may include a GNSS location associated with the network decoding device.

[0133] Aspect 18 is an apparatus according to any one of Aspects 15 to 17, wherein the encoder information message may include one or more of the following: a zone ID associated with the network decoding device, movement information including a speed or destination associated with the network decoding device, a remaining power associated with the network decoding device, a coverage indication representing a coverage area associated with the network decoding device, a power charging indication associated with the network decoding device, or one or more RSRP statistics associated with the network decoding device.

[0134] Aspect 19 is an apparatus according to any one of Aspects 15 to 18, wherein the at least one selected network decoding device is associated with a maximum coverage area in a subset of a set of network decoding devices, and wherein the subset of the set of network decoding devices is associated with an RSRP above a threshold.

[0135] Aspect 20 is an apparatus according to any one of Aspects 15 to 19, wherein the at least one selected network decoding device is randomly selected from a subset of a set of network decoding devices, and wherein the subset of the set of network decoding devices is associated with an RSRP above a threshold.

[0136] Aspect 21 is an apparatus according to any one of aspects 15 to 20, wherein the header of the at least one TB is associated with a feedback ID, a group ID, and a UE ID associated with the UE, and the feedback ID is used to calculate an expected time slot representing feedback of ACK or NACK for the at least one TB.

[0137] Aspect 22 is an apparatus according to any one of aspects 15 to 21, wherein the feedback ID is represented via a hash, a hash function, or a hash procedure.

[0138] Aspect 23 is an apparatus according to any one of aspects 15 to 22, wherein a header of the at least one TB may include first information indicating a transmission sequence for each of the at least one selected network decoding device.

[0139] Aspect 24 is an apparatus according to any one of aspects 15 to 23, wherein the header of the at least one TB may include first information indicating a time slot indication for available transmission of a time slot for each of the at least one selected network decoding device.

[0140] Aspect 25 is an apparatus according to any one of aspects 15 to 24, wherein a header of the at least one TB may include at least one encoder ID of the at least one selected network coding device.

[0141] Aspect 26 is an apparatus according to any one of Aspects 15 to 25, wherein the encoder information message is sent via sidelink control information (SCI), a medium access control (MAC) control element (CE) (MAC-CE), a MAC header, a radio resource control (RRC) message, or a physical sidelink shared channel (PSSCH).

[0142] Aspect 27 is an apparatus according to any one of aspects 15 to 26, wherein the at least one processor is further configured to: encode the at least one TB based on the selection indication; and transmit the encoded at least one TB.

[0143] Aspect 28 is an apparatus according to any one of aspects 15 to 27, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna is configured to receive the selection indication.

[0144] Aspect 29 is a method for wireless communication implementing any one of aspects 1 to 14.

[0145] Aspect 30 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 14.

[0146] Aspect 31 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 14.

[0147] Aspect 32 is a method for implementing wireless communication of any one of aspects 15 to 28.

[0148] Aspect 33 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 15 to 28.

[0149] Aspect 34 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 15 to 28.

Claims

1. An apparatus for communicating at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: receiving one or more encoder information messages from a set of network decoding devices, the one or more encoder information messages being associated with the set of network decoding devices; as well as A selection indication is sent to at least one selected network decoding device from the set of network decoding devices, the selection indication indicating selection of the at least one selected network decoding device as an encoder for encoding at least one transport block (TB).

2. The apparatus of claim 1, wherein each of the one or more encoder information messages comprises a capability indication representing an ability to act as the encoder associated with a corresponding network decoding device in the set of network decoding devices.

3. The apparatus of claim 1, wherein each of the one or more encoder information messages comprises a global navigation satellite system (GNSS) location associated with a corresponding network decoding device in the set of network decoding devices.

4. The apparatus of claim 1 , wherein each of the one or more encoder information messages comprises one or more of: a zone identifier (ID) associated with a corresponding network decoding device in the set of network decoding devices, movement information including a speed or a destination associated with the corresponding network decoding device in the set of network decoding devices, a remaining power associated with the corresponding network decoding device in the set of network decoding devices, a coverage indication representing a coverage area associated with the corresponding network decoding device in the set of network decoding devices, a power charging indication associated with the corresponding network decoding device in the set of network decoding devices, or one or more reference signal received power (RSRP) statistics associated with the corresponding network decoding device in the set of network decoding devices.

5. The apparatus of claim 1 , wherein the at least one processor is configured to: The at least one selected network decoding device is selected as the encoder for encoding the at least one TB.

6. An apparatus according to claim 5, wherein the at least one selected network decoding device is associated with a maximum coverage area in a subset of the set of network decoding devices, and wherein the subset of the set of network decoding devices is associated with a reference signal received power (RSRP) above a threshold.

7. The apparatus of claim 5, wherein the at least one selected network decoding device is randomly selected from a subset of the set of network decoding devices, and wherein the subset of the set of network decoding devices is associated with a reference signal received power (RSRP) above a threshold.

8. The apparatus according to claim 1, wherein a header of the at least one TB is associated with a feedback identifier (ID), a packet ID, and a UE ID associated with the UE, wherein the feedback identifier (ID) is used to calculate an expected time slot for feedback representing an acknowledgment (ACK) or a negative acknowledgment (NACK) for the at least one TB.

9. The apparatus of claim 8, wherein the feedback ID is represented via a hash, a hash function, or a hash procedure. 10 . The apparatus according to claim 1 , wherein a header of the at least one TB includes first information indicating a transmission sequence for each of the at least one selected network decoding device. 11 . The apparatus according to claim 1 , wherein a header of the at least one TB comprises first information indicating a time slot indication of available transmission of a time slot for each of the at least one selected network decoding device.

12. The apparatus of claim 1, wherein a header of the at least one TB comprises at least one encoder identifier (ID) of the at least one selected network decoding device.

13. The apparatus of claim 1, wherein the one or more encoder information messages are received via sidelink control information (SCI), a medium access control (MAC) control element (CE) (MAC-CE), a MAC header, a radio resource control (RRC) message, or a physical sidelink shared channel (PSSCH).

14. The apparatus of claim 1, further comprising at least one of a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna is configured to transmit the selection indication.

15. An apparatus for communicating at a network decoding device, the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: sending an encoder information message to a user equipment (UE), the encoder information message being associated with the network decoding device; and A selection indication is received from the UE based on the encoder information message, the selection indication indicating selection of at least one selected network coding device as an encoder for encoding at least one transport block (TB), the at least one selected network coding device comprising the network coding device.

16. The apparatus of claim 15, wherein the encoder information message includes a capability indication representing a capability to act as the encoder associated with the network coding device.

17. The apparatus of claim 15, wherein the encoder information message comprises a Global Navigation Satellite System (GNSS) location associated with the network decoding device.

18. The apparatus of claim 15, wherein the encoder information message comprises one or more of: a zone identifier (ID) associated with the network decoding device, movement information including a speed or destination associated with the network decoding device, a remaining battery associated with the network decoding device, a coverage indication representing a coverage area associated with the network decoding device, a power charging indication associated with the network decoding device, or one or more reference signal received power (RSRP) statistics associated with the network decoding device.

19. An apparatus according to claim 15, wherein the at least one selected network decoding device is associated with a maximum coverage area in a subset of a set of network decoding devices, and wherein the subset of the set of network decoding devices is associated with a reference signal received power (RSRP) above a threshold.

20. The apparatus of claim 15, wherein the at least one selected network decoding device is randomly selected from a subset of a set of network decoding devices, and wherein the subset of the set of network decoding devices is associated with a reference signal received power (RSRP) above a threshold.

21. The apparatus of claim 15, wherein a header of the at least one TB is associated with a feedback identifier (ID), a packet ID, and a UE ID associated with the UE, the feedback identifier (ID) being used to calculate an expected time slot for feedback representing an acknowledgment (ACK) or a negative acknowledgment (NACK) for the at least one TB.

22. The apparatus of claim 21, wherein the feedback ID is represented via a hash, a hash function, or a hash procedure.

23. The apparatus according to claim 15, wherein a header of the at least one TB includes first information indicating a transmission sequence for each of the at least one selected network decoding device.

24. The apparatus according to claim 15, wherein a header of the at least one TB includes first information indicating a time slot indication for available transmission of a time slot for each of the at least one selected network decoding devices.

25. The apparatus of claim 15, wherein a header of the at least one TB comprises at least one encoder identifier (ID) of the at least one selected network decoding device.

26. The apparatus of claim 16, wherein the encoder information message is transmitted via a sidelink control information (SCI), a medium access control (MAC) control element (CE), (MAC-CE), MAC header, radio resource control (RRC) message or physical sidelink shared channel (PSSCH).

27. The apparatus of claim 15, wherein the at least one processor is configured to: encoding the at least one TB based on the selection indication; and The encoded at least one TB is transmitted.

28. The apparatus of claim 15, further comprising at least one of a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna is configured to receive the selection indication.

29. A method of communicating at a user equipment (UE), the method comprising: receiving one or more encoder information messages from a set of network decoding devices, the one or more encoder information messages being associated with the set of network decoding devices; as well as A selection indication is sent to at least one selected network decoding device from the set of network decoding devices, the selection indication indicating selection of the at least one selected network decoding device as an encoder for encoding at least one transport block (TB).

30. A method for communicating at a network decoding device, the method comprising: sending an encoder information message to a user equipment (UE), the encoder information message being associated with the network decoding device; as well as A selection indication is received from the UE based on the encoder information message, the selection indication indicating selection of at least one selected network coding device as an encoder for encoding at least one transport block (TB), the at least one selected network coding device comprising the network coding device.

Images