Mode 1 network entity initiated network coding handover

Abstract

The first device may communicate the SL NC TB with the second device. At least one of the first device and the second device may be a UE. The first device may send a first message to a network entity, the first message including first location information indicating movement of the UE from a first zone to a second zone. The first message may have first location information associated with the UE. The UE may be in SL communication with a first encoder in the first region. The network entity may obtain the first message from the first device. The network entity may initialize an NC handover of the UE to a second encoder of the second zone in response to the first location information indicating movement of the UE from the first zone to the second zone.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application serial number 17 / 814,471, filed on July 22, 2022, entitled “MODE 1 NETWORK ENTITY INITIATED NETWORK CODING HANDOVER,” which is expressly incorporated herein by reference in its entirety. Background Art

[0003] The present disclosure relates generally to communication systems, and more particularly to network coding handover systems.

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. 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 continued mobile broadband evolution promulgated by the 3rd 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. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that adopt these technologies. Summary of the Invention

[0006] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects. This summary is not intended to identify key or critical elements of all aspects, nor is it intended to delineate 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 the more detailed description that will be presented later.

[0007] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication at a first device are provided. The apparatus may include a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to communicate a sidelink (SL) transport block (TB) for network coding (NC) with a second device. At least one of the first device or the second device may include a user equipment (UE). Based at least in part on information stored in the memory, the at least one processor may be configured to send a first message to a network entity, the first message including first location information indicating movement of the UE from a first area to a second area.

[0008] In one aspect of the present disclosure, an apparatus for wireless communication at a first device is provided. The apparatus may include means for communicating a SL TB for an NC with a second device. At least one of the first device or the second device may include a UE. The apparatus may include means for sending a first message to a network entity, the first message including first location information indicating movement of the UE from a first area to a second area.

[0009] In one aspect of the present disclosure, a method for wireless communication at a first device is provided. The method may include communicating a SL TB for an NC with a second device. At least one of the first device or the second device may include a UE. The method may include sending a first message to a network entity, the first message including first location information indicating movement of the UE from a first area to a second area.

[0010] In one aspect of the present disclosure, a computer-readable storage medium storing computer-executable code on a first device is provided. When executed by a processor, the code may cause the processor to communicate a SL TB for an NC with a second device. At least one of the first device or the second device may include a UE. When executed by the processor, the code may cause the processor to send a first message to a network entity, the first message including first location information indicating movement of the UE from a first area to a second area.

[0011] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication at a network entity are provided. The apparatus may have a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to obtain a first message from a first device, the first message including first location information associated with a UE, the UE performing SL communication with a first encoder associated with a first zone. Based at least in part on information stored in the memory, the at least one processor may be configured to initialize NC handover of the UE to a second encoder in the second zone in response to the first location information indicating movement of the UE from the first zone to the second zone.

[0012] In one aspect of the present disclosure, an apparatus for wireless communication at a network entity is provided. The apparatus may include means for obtaining a first message from a first device, the first message including first location information associated with a UE, the UE in SL communication with a first encoder associated with a first zone. The apparatus may include means for initiating NC handover of the UE to a second encoder in the second zone in response to the first location information indicating movement of the UE from the first zone to the second zone.

[0013] In one aspect of the present disclosure, a method for wireless communication at a network entity is provided. The method may include obtaining a first message from a first device, the first message including first location information associated with a UE, the UE in SL communication with a first encoder associated with a first zone. The method may include initiating NC handover of the UE to a second encoder in the second zone in response to the first location information indicating movement of the UE from the first zone to the second zone.

[0014] In one aspect of the present disclosure, a computer-readable storage medium storing computer-executable code at a network entity is provided. When executed by a processor, the code may cause the processor to obtain a first message from a first device, the first message including first location information associated with a UE, the UE in SL communication with a first encoder associated with a first zone. When executed by the processor, the code may cause the processor to initiate NC handover of the UE to a second encoder in the second zone in response to the first location information indicating movement of the UE from the first zone to the second zone.

[0015] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication at a second encoder are provided. The apparatus may include a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to receive an NC handover request from a network entity. Based at least in part on the information stored in the memory, the at least one processor may be configured to send a SL NC TB to a UE based on the NC handover request.

[0016] In one aspect of the present disclosure, an apparatus for wireless communication at a second encoder is provided. The apparatus may include a component for receiving an NC handover request from a network entity. The apparatus may include a component for sending a SL NC TB to a UE based on the NC handover request.

[0017] In one aspect of the present disclosure, a method for wireless communication at a second encoder is provided. The method may include receiving an NC handover request from a network entity. The method may include sending a SL NC TB to a UE based on the NC handover request.

[0018] In one aspect of the present disclosure, a computer-readable storage medium storing computer-executable code at a second encoder is provided, which, when executed by a processor, may cause the processor to receive an NC handover request from a network entity. The code, when executed by the processor, may cause the processor to send a SL NC TB to a UE based on the NC handover request.

[0019] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication at a network entity are provided. The apparatus may include a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to output, to a second encoder, a first NC handover request for the second encoder to communicate a SL TB with a UE. Based at least in part on the information stored in the memory, the at least one processor may be configured to output, to the second encoder, a first grant for transmitting a SL NC TB using a first SL resource, or to the UE, a second grant for transmitting the SL TB using a second SL resource.

[0020] In one aspect of the present disclosure, an apparatus for wireless communication at a network entity is provided. The apparatus may include means for outputting a first NC handover request to a second encoder for communicating a SL TB between the second encoder and a UE. The apparatus may include means for outputting a first grant to the second encoder for transmitting a SL NC TB using a first SL resource, or outputting a second grant to the UE for transmitting the SL TB using a second SL resource.

[0021] In one aspect of the present disclosure, a method for wireless communication at a network entity is provided. The method may include outputting a first NC handover request to a second encoder for communicating a SL TB between the second encoder and a UE. The method may include outputting a first grant to the second encoder for transmitting a SL NC TB using a first SL resource, or outputting a second grant to the UE for transmitting the SL TB using a second SL resource.

[0022] In one aspect of the present disclosure, a computer-readable storage medium storing computer-executable code at a network entity is provided. When executed by a processor, the code may cause the processor to output a first NC handover request to a second encoder for the second encoder to communicate a SL TB with a UE. When executed by the processor, the code may cause the processor to output a first grant to the second encoder to send a SL NC TB using a first SL resource, or to output a second grant to the UE to send the SL TB using a second SL resource.

[0023] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication at a first device are provided. The apparatus may have a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to send a sidelink (SL) transport block (TB) to a second device or receive the sidelink (SL) transport block (TB) from the second device for network decoding (NC), respectively, wherein at least one of the first device or the second device may include a user equipment (UE). Based at least in part on the information stored in the memory, the at least one processor may also be configured to send a first message to a network entity, the first message having first location information indicating movement of the UE from a first area to a second area.

[0024] In one aspect of the present disclosure, an apparatus for wireless communication at a first device is provided. The apparatus includes means for sending a SL TB to a second device or receiving the SL TB from the second device for NC, respectively, wherein at least one of the first device or the second device comprises a UE. The apparatus includes means for sending a first message to a network entity, the first message including first location information indicating movement of the UE from a first area to a second area.

[0025] In one aspect of the present disclosure, a method for wireless communication at a first device is provided. The method includes sending a SL TB to a second device or receiving the SL TB from the second device for use in a NC, respectively, wherein at least one of the first device and the second device comprises a UE. The method also includes sending a first message to a network entity, the first message including first location information indicating movement of the UE from a first area to a second area.

[0026] In one aspect of the present disclosure, a computer-readable storage medium storing computer-executable code at a first device is provided. When executed by a processor, the code causes the processor to send a SL TB to a second device or receive the SL TB from the second device for use in a NC, wherein at least one of the first device and the second device comprises a UE. When executed by the processor, the code further causes the processor to send a first message to a network entity, the first message including first location information indicating movement of the UE from a first area to a second area.

[0027] In one aspect of the present disclosure, an apparatus for wireless communication at a network entity is provided. The apparatus may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to obtain a first message from a first device, the first message including a location of a UE performing SL communication with a first encoder in a first transmission zone. Based at least in part on information stored in the memory, the at least one processor may be further configured to initiate an NC handover of the UE to a second encoder in the second transmission zone in response to the location indicating movement of the UE from the first transmission zone to the second transmission zone.

[0028] In one aspect of the present disclosure, an apparatus for wireless communication at a network entity is provided. The apparatus includes means for obtaining a first message from a first device, the first message including a location of a UE in SL communication with a first encoder in a first transmission zone. The apparatus includes means for initiating NC handover of the UE to a second encoder in the second transmission zone in response to the location indicating movement of the UE from the first transmission zone to a second transmission zone.

[0029] In one aspect of the present disclosure, a method for wireless communication at a network entity is provided. The method includes obtaining a first message from a first device, the first message including a location of a UE in SL communication with a first encoder in a first transmission zone. The method also includes initiating an NC handover of the UE to a second encoder in the second transmission zone in response to the location indicating movement of the UE from the first transmission zone to a second transmission zone.

[0030] In one aspect of the present disclosure, a computer-readable storage medium storing computer-executable code at a network entity is provided. The code, when executed by a processor, causes the processor to obtain a first message from a first device, the first message including a location of a UE that is in SL communication with a first encoder in a first transmission zone. The code, when executed by the processor, further causes the processor to initiate an NC handover of the UE to a second encoder in the second transmission zone in response to the location indicating movement of the UE from the first transmission zone to the second transmission zone.

[0031] In one aspect of the present disclosure, an apparatus for wireless communication at a destination encoder is provided. Network decoding for a UE may be handed over to the destination encoder. The apparatus may include a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to receive an NC handover request from a network entity. Based at least in part on the information stored in the memory, the at least one processor may also be configured to transmit a SL NC TB to the UE based on the NC handover request.

[0032] In one aspect of the present disclosure, an apparatus for wireless communication at a destination encoder is provided. Network decoding for a UE may be handed over to the destination encoder. The apparatus includes means for receiving an NC handover request from a network entity. The apparatus also includes means for transmitting a SL NC TB with the UE based on the NC handover request.

[0033] In one aspect of the present disclosure, a method for wireless communication at a destination encoder is provided. Network decoding for a UE may be handed over to the destination encoder. The method includes receiving an NC handover request from a network entity. The method also includes transmitting a SL NC TB with the UE based on the NC handover request.

[0034] In one aspect of the present disclosure, a computer-readable storage medium storing computer-executable code at a destination encoder is provided, which when executed by a processor causes the processor to receive an NC handover request from a network entity and transmit a SL NC TB with a UE based on the NC handover request.

[0035] In one aspect of the present disclosure, an apparatus for wireless communication at a network entity is provided. The apparatus may include a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to output, to a destination encoder, a first NC handover request for the destination encoder to transmit a SL NC to a UE or to receive the SL NC from the UE, respectively. Based at least in part on the information stored in the memory, the at least one processor may also be configured to output, to one of the destination encoder or the UE, a grant to transmit the SL NC TB using SL resources.

[0036] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication at a network entity are provided. The apparatus may include a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to output, to a destination encoder, a first NC handover request for the destination encoder to send a SL NC TB to a UE or to receive the SL NC TB from the UE, respectively. Based at least in part on the information stored in the memory, the at least one processor may also be configured to output, to one of the destination encoder or the UE, a grant to use SL resources to send the SL NC TB.

[0037] In one aspect of the present disclosure, an apparatus for wireless communication at a network entity is provided. The apparatus includes means for outputting a first NC handover request to a destination encoder for the destination encoder to transmit a SL NC TB to a UE or to receive the SL NC TB from the UE, respectively. The apparatus also includes means for outputting a grant to one of the destination encoder or the UE to transmit the SL NC TB using SL resources.

[0038] In one aspect of the present disclosure, a method for wireless communication at a network entity is provided. The method includes outputting a first NC handover request to a destination encoder for the destination encoder to send a SL NC TB to a UE or receive the SL NC TB from the UE, respectively. The method also includes outputting a grant to one of the destination encoder or the UE to use SL resources to send the SL NC TB.

[0039] To accomplish the foregoing and related objectives, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features are indicative of only some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0042] Figure 2B is a diagram illustrating an example of a DL channel within a subframe according to various aspects of the present disclosure.

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

[0044] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0045] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0046] Figure 4A is a diagram illustrating an example of a side link slot structure.

[0047] Figure 4B is a diagram illustrating an example of a side link slot structure.

[0048] Figure 5 is a diagram illustrating an example of side link communication between devices.

[0049] Figure 6A is a diagram illustrating example aspects of sidelink communications between devices in a network.

[0050] Figure 6B This is an example Figure 6A Schematic diagram of a communication link between wireless devices.

[0051] Figure 6C This is an example Figure 6A Schematic diagram of a communication link between wireless devices.

[0052] Figure 6D This is an example Figure 6A Schematic diagram of a communication link between wireless devices.

[0053] Figure 7A is a diagram illustrating example aspects of sidelink communications between devices in a network using NC.

[0054] Figure 7B This is an example Figure 7A Schematic diagram of a communication link between wireless devices.

[0055] Figure 7C This is an example Figure 7ASchematic diagram of a communication link between wireless devices.

[0056] Figure 7D This is an example Figure 7A Schematic diagram of a communication link between wireless devices.

[0057] Figure 7E This is an example Figure 7A Schematic diagram of a communication link between wireless devices.

[0058] Figure 8A is a diagram illustrating example aspects of an NC handover request according to various aspects of the present disclosure.

[0059] Figure 8B is a diagram illustrating example aspects of a confirmation message that may be sent in response to an NC handover request according to various aspects of the present disclosure.

[0060] Figure 8C is a diagram illustrating example aspects of a SL NC TB according to various aspects of the present disclosure.

[0061] Figure 9 is a connection flow diagram illustrating example aspects of sidelink communications between devices using NC.

[0062] Figure 10A is a diagram illustrating example aspects of sidelink communications between devices using NC at a first time.

[0063] Figure 10B It is an example of the second time Figure 10A An illustration of example aspects in .

[0064] Figure 10C This is an example Figure 10B Schematic diagram of a communication link between wireless devices.

[0065] Figure 11 is a connection flow diagram illustrating example aspects of sidelink communication between devices using NC, where the source UE moves between zones.

[0066] Figure 12A is a diagram illustrating another example aspect of sidelink communication between devices using NC at a first time.

[0067] Figure 12B It is an example of the second time Figure 12A An illustration of example aspects in .

[0068] Figure 12C This is an example Figure 12B Schematic diagram of a communication link between wireless devices.

[0069] Figure 13is a connection flow diagram illustrating another example aspect of sidelink communication between devices using NC, where the destination UE moves between zones.

[0070] Figure 14 is a flow chart of a method for conducting wireless communications.

[0071] Figure 15 is a flow chart of a method for conducting wireless communications.

[0072] Figure 16 is a flow chart of a method for conducting wireless communications.

[0073] Figure 17 is a flow chart of a method for conducting wireless communications.

[0074] Figure 18 is a flow chart of a method of conducting wireless communications.

[0075] Figure 19 is a flow chart of a method for conducting wireless communications.

[0076] Figure 20 is a flow chart of a method for conducting wireless communications.

[0077] Figure 21 is a flow chart of a method for conducting wireless communications.

[0078] Figure 22 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0079] Figure 23 is a diagram illustrating an example of a hardware implementation for an example network entity.

[0080] Figure 24 is a diagram illustrating an example of an encoder and a UE in an access network. DETAILED DESCRIPTION

[0081] Wireless signals that are scheduled to overlap in time, overlap in frequency, or be adjacent in frequency may interfere with each other. Such interference may occur between wireless devices that send sidelink (SL) messages that are scheduled to overlap in time, overlap in frequency, or be adjacent in frequency. For example, when a first SL message and a second SL message are scheduled to overlap in time, overlap in frequency, or be adjacent in frequency, a first user equipment (UE) broadcasting the first SL message may interfere with the first UE's reception of the second SL message broadcast by the second UE.

[0082] Network coding (NC) is a network technology that uses an encoder to receive two or more messages sent by UEs in the network, encode the two or more messages to generate a joint message, and transmit an NC transmission containing the joint message. The message transmitted by the UE may be referred to as a transport block (TB). An NC transmission may also be referred to as an NC TB. In other words, the encoder may combine packets from TBs previously transmitted by two or more UEs in the network to create an NC TB, and may transmit the combined packets as an NC TB after receiving the TBs transmitted by the UEs. The encoder may also retransmit the original two or more TBs transmitted by the UEs in the network as part of the NC TB. Therefore, in one aspect, an encoder that transmits an NC TB after receiving two or more TBs transmitted by a UE in the network can provide a layer of redundancy for the two or more TBs, as the NC TB may contain the joint message of the two or more TBs. The NC TB may also contain the two or more TBs separately from the joint message, thereby adding another layer of redundancy.

[0083] In one aspect, a wireless device may receive two or more TBs transmitted by a UE in a network and may also receive an NC TB transmitted by an encoder. The wireless device may be another UE. If the wireless device misses receiving or fails to successfully decode one of the two or more TBs transmitted by a UE in the network, the wireless device may use the NC TB to recover the lost TB, or may use the NC TB to decode the TB that failed to be decoded. Retransmitting two or more TBs in an NC TB by the encoder receiving the TB may increase system capacity and improve resource utilization because if the UE can use the NC TB to recover the lost TB, the UE may not retransmit the TB to other UEs in the area. Retransmitting two or more TBs in an NC TB may improve the latency of retransmissions by the original UE because the UE may not retransmit the TB to other UEs as frequently. Retransmitting two or more TBs in an NC TB may improve reception of the TB by wireless devices receiving the TB in the area because the UE may receive redundant TBs from the encoder to recover the lost TB or the TB that failed to be successfully decoded.

[0084] When a first UE moves from a first geographic location (i.e., a first zone) having a first encoder to a second geographic location (i.e., a second zone) having a second encoder, the NC may not function properly. For example, the first encoder in the first zone may receive TBs from other UEs in the first zone, but may not receive the first TB from the first UE. The first UE may move so quickly away from the first encoder in the first zone that the first encoder may not be able to receive the first TB sent by the first UE. This may prevent the first encoder from generating a joint message for NC transmission including the first TB. In another example, the first UE may not be able to receive the NC TB from the first encoder. The first UE may move so quickly away from the first encoder in the first zone that the first UE may not be able to receive the NC TB containing redundant TBs sent by the UE in the first zone. When the UE moves from a first zone having a first encoder to a second zone having a second encoder, a network entity such as a base station or a component of a base station may coordinate with the UE and encoder using the NC to perform a handover from the first encoder in the first zone to the second encoder in the second zone. A request to handover communication with a UE from one encoder to another encoder in an NC system may be referred to as an NC handover request.

[0085] To initiate a handover of a designated UE from a first encoder to a second encoder, a network entity, such as a base station or a component of a base station, may periodically receive location information associated with the designated UE. In one aspect, the designated UE may send the location information associated with the designated UE to the network entity. In another aspect, an encoder, such as a roadside unit (RSU), may send location information associated with the encoder's subordinate UEs (e.g., including location information associated with the designated UE) to the network entity. When the network entity determines that the designated UE is moving from a first region having a first encoder to a second region having a second encoder, the network entity may use the reported location information to initiate a handover of the designated UE from the first encoder (i.e., the source encoder) to the second encoder (i.e., the destination encoder). In one aspect, the network entity may initiate the handover by providing an NC handover request to the second encoder. The network entity may optionally provide the NC handover request to the first encoder. The second encoder may transmit a confirmation message to the network entity indicating whether the NC handover request associated with the designated UE was accepted, whether the second encoder has buffered the TB from the designated UE, and / or whether the second encoder successfully received and decoded the TB from the first encoder. In some aspects, the second encoder may transmit an acknowledgment message to the first encoder to confirm acceptance of the NC handover request. In some aspects, the first encoder may resend a TB to a designated UE after initiating the handover. The resent TB may be, for example, a TB previously sent by a UE in the first zone or an NC TB previously sent by the first encoder, the resent TB containing a joint message with the TB previously sent by the UE in the first zone. The header of the resent TB may indicate NC handover. Resending the TB may provide the second encoder with an additional opportunity to receive the TB at a later time.

[0086] The set of UEs and the first encoder may be configured to communicate TBs to each other using SL in the first zone. Such TBs may be referred to as SL TBs. In other words, each UE in the set of UEs may separately send an SL TB to the first encoder or receive the SL TB from the first encoder, and vice versa. The first encoder may encode the SL TBs received from the set of UEs to generate a joint transmission for NC TBs based on the SL TBs received by the first encoder from the set of UEs. This joint transmission may be referred to as an SL NCTB. This joint transmission may include a joint message of two or more SL TBs received by the first encoder and encoded to form a joint message. This joint transmission may include a set of two or more SL TBs received by the first encoder. The network entity may use location information associated with the set of UEs to track the location of the set of UEs in the first zone. This location information may be sent to the network entity via a message from each UE in the set of UEs or from the first encoder that tracks location information associated with the set of UEs. Such a message with location information may be, for example, an uplink transmission to the network entity.

[0087] A message with location information associated with one of the UEs in the set of UEs may indicate movement of the UE from a first zone associated with a first encoder to a second zone associated with a second encoder. For example, a first message with first location information associated with the UE may be sent to a network entity after a second message with second location information associated with the UE. The network entity that receives the first message after the second message may determine, based on the first location information, that the UE is moving from the first zone toward the second zone, or has moved from the first zone to the second zone. In response to the first location information indicating movement of the UE from the first zone to the second zone, the network entity may initiate an NC handover of the UE from the first encoder associated with the first zone to the second encoder associated with the second zone. The network entity may send an NC handover request to the second encoder and, optionally, to the first encoder. The second encoder may receive the NC handover request and, in response, may send a SL NC TB to the UE or may receive a SL TB from the UE. The network entity may send a grant to the second encoder to use SL resources to send a SL NC TB to the UE, or may send a grant to the UE to use SL resources to send a SL TB to the second encoder. The first encoder may receive the NC handover request and, in response, may resend the SL TB or SL NC TB for receipt by the second encoder.

[0088] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does 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 detailed description includes specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0089] Several aspects of the telecommunications system are also presented with reference to various apparatuses and methods. These apparatuses 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 can 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.

[0090] As an example, any combination of an element or any part of an element or an element can be implemented as a "processing system", which includes one or more processors. The example of a processor includes a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gate logic component, a discrete hardware circuit and other suitable hardware configured to perform the various functions described throughout this 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 an instruction, an instruction set, a code, a code segment, a program code, a program, a subroutine, a software component, an application, a software application, a software package, a routine, a subroutine, an object, an executable, a thread of execution, a process, a function or any combination thereof.

[0091] Thus, in one or more example aspects, specific implementations and / or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. A storage medium may be any available medium that can be accessed by a computer. By way of 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.

[0092] Although various aspects, specific implementations and / or use cases are described in this application by way of illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, aspects, specific implementations and / or use cases may be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user equipment, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may be specifically for use cases or applications, or may not be specifically for use cases or applications, the examples described may have a wide range of applicability. Aspects, specific implementations and / or use cases may be within the scope of chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the scope of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some actual environments, the devices in conjunction with the various aspects and features described may also include additional components and features for implementing and practicing the various aspects claimed and described. 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 / accumulators, etc.). The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, including chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, and the like.

[0093] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways with various components or parts. In a 5G NR system or network, a network node, a network entity, a mobility element of the 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) performing base station functions) can be implemented in an aggregated architecture or a 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 known as a standalone BS or a monolithic BS) or a decomposed base station.

[0094] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack that is 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 across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and 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).

[0095] 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 (a 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. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0096] Figure 1FIG100 is a diagram illustrating an example of a wireless communication system and 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, which 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 the 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.

[0097] 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 transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the communication interface of the unit, may be configured to communicate with one or more of the other units via the transmission medium. For example, the units may include a wired interface configured to receive or transmit signals to one or more of the other units over a wired transmission medium. Additionally, the units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or transmit signals, or both, to one or more of the other units over a wireless transmission medium.

[0098] In some aspects, the 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 that is configured to communicate signals with other control functions hosted by the CU 110. The CU 110 may be configured to handle user plane functions (i.e., central unit-user plane (CU-UP)), control plane functions (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, the 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, the CU 110 may be implemented to communicate with the DU 130 for network control and signaling.

[0099] The 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, the DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on a functional split (such as that defined by 3GPP). In some aspects, the DU 130 may further host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 130 or with control functions hosted by the CU 110.

[0100] Lower layer functions may be implemented by one or more RUs 140. In some deployments, a RU 140 controlled by a 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 a functional split (such as a lower layer functional split). 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 control and user plane communications with 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 CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0101] The SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 105 can be configured to interact with a cloud computing platform (such as Open Cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the 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 implementations, the SMO framework 105 can communicate with hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some implementations, the SMO framework 105 can 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 .

[0102] 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 in communication with the near-RT RIC 125 (e.g., 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 through data collection and actions via an interface (e.g., 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.

[0103] In some implementations, to generate AI / ML models 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 non-network data sources or from network functions 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 in 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).

[0104] At least one of the CU 110, DU 130, and RU 140 may be referred to as a base station 102. Thus, the base station 102 may include one or more of the CU 110, DU 130, and RU 140 (each component is indicated by a dashed 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 that includes 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 called a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmissions from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmissions from RU 140 to UE 104. The communication link may utilize multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be over one or more carriers. For each carrier allocated in a carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction, base station 102 / UE 104 may utilize spectrum with a bandwidth of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.). The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared 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).

[0105] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. Such UEs 104 may also communicate with the encoder 152 using the D2D communication link 158. The RU 140 may also be configured to communicate with the UE 104 or the encoder 152 using the D2D communication link 158 or a cellular (Uu) link (such as an uplink or downlink). The D2D communication link 158 may use the DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more SL channels, such as a physical SL broadcast channel (PSBCH), a physical SL discovery channel (PSDCH), a physical SL shared channel (PSSCH), and a physical SL control channel (PSCCH). The D2D communication may be performed via a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0106] Some examples of SL communications may include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I) (e.g., from a vehicle-based communication device to an encoder such as a roadside unit (RSU) or road infrastructure node), 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 vehicle-based communication devices 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 the UE, SL communications may also be sent and received by other transmitting and receiving devices, such as the encoder 152 or the base station 102, etc. The PC5 interface may be used to exchange sidelink communications, such as in conjunction with Figure 4A and Figure 4B Although the example in Figure 4A and Figure 4B The following description of an example time slot structure may provide examples for SL communications related to 5G NR, but the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0107] 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 the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available before communicating.

[0108] 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 (interchangeably) referred to 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 it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) that is identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

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

[0110] With the above in mind, unless otherwise specified, if the term "sub-6 GHz" or the like 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. Furthermore, unless otherwise specified, if the term "millimeter wave" or the like 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.

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

[0112] 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 terminology. The base station 102 may be implemented as an integrated access backhaul (IAB) node, a relay node, a SL node, a converged (monolithic) base station having 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. A collection of base stations that may include disaggregated base stations and / or converged base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0113] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is a control node that handles signaling between the UE 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity processing, access authorization, and subscription management. The one or more location servers 168 are exemplified as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. Generally speaking, however, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Positioning Center (MPC), and the like. The GMLC 165 and LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurement results and assistance information from the NG-RAN and UE 104 via the AMF 161 to calculate the position of the UE 104. The NG-RAN may utilize one or more positioning methods to determine the position of the UE 104. Positioning the UE 104 may involve signal measurements, position estimates, and optional velocity calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signals may be based on one or more of a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or other systems / signals / sensors.

[0114] Examples of UE 104 include a cellular phone, a smartphone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of UE 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart monitor, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0115] Reference again Figure 1In certain aspects, the UE 104 may have an NC location tracking component 198 configured to communicate a SL TB with a second device for NC. At least one of the first device or the second device may include a UE. At least one of the first device or the second device may include an encoder. Communicating the SL TB with the device may include sending the SL TB to the device or receiving the SL TB from the device. The NC location tracking component 198 may be configured to send a first message to a network entity, the first message including first location information indicating movement of the UE from the first area to the second area. Although one UE 104 is shown in diagram 100 as having the NC location tracking component 198, each of the UEs 104 shown in diagram 100 may have the NC location tracking component 198. The UE 104 may also be configured to use the NC location tracking component 198 to send the SL NC TB to a second device (such as another UE or an encoder) or receive the SL NC TB from the second device, respectively. In certain aspects, base station 102 may include an NC handover initialization component 199 configured to obtain a first message from a first device, the first message including first location information associated with a UE engaged in SL communication with a first encoder. The first encoder may be associated with a first zone. NC handover initialization component 199 may be configured to initialize NC handover of the UE to a second encoder in the second zone in response to the first location information indicating movement of the UE from the first zone to the second zone. NC handover initialization component 199 may be configured to output a first NC handover request to the second encoder for communicating a SL TB with the UE. NC handover initialization component 199 may be configured to output a first grant to the second encoder to transmit a SL NC TB using first SL resources, or to output a second grant to the UE to transmit a SL TB using second SL resources. In certain aspects, encoder 152 may include an NC handover execution component 197 configured to receive an NC handover request from a network entity. The NC handover request may be a downlink transmission. The NC handover execution component 197 may be configured to send a SL NC TB to the UE based on the NC handover request. Although the following description may focus on V2X, the concepts described herein may be applicable to other similar fields, such as any devices that communicate with each other using a D2D communication link (such as SL). Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0116] 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 2CFIG250 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 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 2C In 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 can be configured with any of the various available slot formats 0 to 61. Slot formats 0 and 1 are all DL and all UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The slot format is configured for the UE via a received slot format indicator (SFI) (dynamically configured via DL control information (DCI) or semi-statically / statically configured via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

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

[0118]

[0119] Table 1: Parameter set, SCS and CP

[0120] In one aspect, the parameter set, SCS, and cyclic prefix of a subframe may be defined by Table 1 above. For normal CP (14 symbols / slot), different parameter sets μ0 to 4 may allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 may allow 4 slots per subframe. Accordingly, for normal CP and parameter set μ, there may be 14 symbols / slots and 2 μ time slots / 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 can be 15kHz, and the subcarrier spacing for parameter set μ=4 can be 240kHz. The symbol length / duration can be inversely related to the subcarrier spacing. Figures 2A to 2D An example is provided for a normal CP with 14 symbols per slot and a parameter set μ=2 with 4 slots per subframe. The slot duration may be 0.25 ms, the subcarrier spacing may be 60 kHz, and the symbol duration may be approximately 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).

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

[0122] 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 a specific 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).

[0123] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The 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 comprising six RE groups (REGs), each REG comprising 12 consecutive REs within an OFDM symbol of a RB. The PDCCH within a BWP may be referred to as a control resource set (CORESET). During a PDCCH monitoring opportunity on the 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), where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a specific subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. The secondary synchronization signal (SSS) may be within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and 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 system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent over the PBCH, such as the system information block (SIB), and paging messages.

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

[0125] Figure 2D Examples 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 a scheduling request, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (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 additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0126] Figure 33 is a block diagram illustrating communication between a base station 310 and a UE 350 in an access network. The base station 310 and the UE 350 can communicate using a Uu link or using a D2D communication link (e.g., SL, V2X). This communication can be based on SL using the PC5 interface. In the DL, Internet Protocol (IP) packets can be provided to the controller / processor 375. The controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. The controller / processor 375 provides RRC layer functions 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 functions associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions 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.

[0127] 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 onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The Tx processor 316 handles the mapping to the signal constellation diagram based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be separated into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying the time-domain OFDM symbol stream. The OFDM stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. The channel estimates may be derived from a reference signal and / or channel state feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier using a corresponding spatial stream for transmission.

[0128] At the UE 350, each receiver 354Rx receives a signal via 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 functions associated with various signal processing functions. The Rx processor 356 can perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the Rx processor 356. The Rx processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted 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 a controller / processor 359, which implements layer 3 and layer 2 functionality.

[0129] 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 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 an ACK and / or NACK protocol to support HARQ operations.

[0130] Similar to the functions described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions 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 functions 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.

[0131] Channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 may be used by the Tx processor 368 to select 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.

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

[0133] 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 and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0134] At least one of the Tx processor 368, the Rx processor 356, and the controller / processor 359 may be configured to perform a combined Figure 1 Aspects of the NC position tracking component 198.

[0135] At least one of the Tx processor 316, the Rx processor 370, and the controller / processor 375 may be configured to perform a combined Figure 1 The NC handover initializes various aspects of component 199.

[0136] Figure 24 24 is a block diagram of a base station 2410 communicating with an encoder 2450 in an access network. The base station 2410 and the encoder 2450 can communicate using a Uu link or using a D2D communication link (e.g., SL, V2X). This communication can be based on SL using a PC5 interface. In the DL, Internet Protocol (IP) packets can be provided to the controller / processor 2475. The controller / processor 2475 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. The controller / processor 2475 provides RRC layer functions 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 functions associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions 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.

[0137] The transmit (Tx) processor 2416 and receive (Rx) processor 2470 implement Layer 1 functions associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on transport channels, forward error correction (FEC) coding / decoding of transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The Tx processor 2416 handles the mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols are then separated into parallel streams. Each stream is then mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined 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 a channel estimator 2474 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from a reference signal and / or channel state feedback sent by the encoder 2450. Each spatial stream may then be provided to a different antenna 2420 via a separate transmitter 2418Tx. Each transmitter 2418Tx may modulate a radio frequency (RF) carrier using a corresponding spatial stream for transmission.

[0138] At encoder 2450, each receiver 2454Rx receives a signal via its corresponding antenna 2452. Each receiver 2454Rx recovers the information modulated onto the RF carrier and provides the information to a receive (Rx) processor 2456. Tx processor 2468 and Rx processor 2456 implement Layer 1 functions associated with various signal processing functions. Rx processor 2456 can perform spatial processing on the information to recover any spatial streams destined for encoder 2450. If multiple spatial streams are destined for encoder 2450, Rx processor 2456 can combine them into a single OFDM symbol stream. Rx processor 2456 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted by base station 2410. These soft decisions may be based on channel estimates computed by a channel estimator 2458. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 2410. The data and control signals are then provided to a controller / processor 2459, which implements layer 24 and layer 2 functionality.

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

[0140] Similar to the functions described in conjunction with DL transmission performed by the base station 2410, the controller / processor 2459 provides RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions 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 functions 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.

[0141] Channel estimates derived by the channel estimator 2458 from a reference signal or feedback sent by the base station 2410 may be used by the Tx processor 2468 to select appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the Tx processor 2468 may be provided to different antennas 2452 via separate transmitters 2454Tx. Each transmitter 2454Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0142] UL transmissions are processed at the base station 2410 in a manner similar to that described in conjunction with the receiver functionality at the encoder 2450. Each receiver 2418Rx receives a signal through its corresponding antenna 2420. Each receiver 2418Rx recovers information modulated onto an RF carrier and provides the information to an Rx processor 2470.

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

[0144] At least one of the Tx processor 2468, the Rx processor 2456, and the controller / processor 2459 may be configured to perform a combined Figure 1 The NC handover executes various aspects of component 197.

[0145] At least one of the Tx processor 2416, the Rx processor 2470, and the controller / processor 2475 may be configured to perform a combined Figure 1 The NC handover initializes various aspects of component 199.

[0146] Figure 4A includes a diagram 400 illustrating example aspects of a slot structure that may be used for SL communication (eg, between UE 104, encoder 152, etc.), and Figure 4B Diagram 410 illustrating these example aspects is included. In some examples, the slot structure may be within a 5G / NR frame structure. In other examples, the slot structure may be within an LTE frame structure. While the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies. Figure 4A and Figure 4B The example slot structure in is only an example, and other SL communications may have different frame structures and / or different channels for SL communications. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each slot may include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot may include 14 symbols, and for slot configuration 1, each slot may include 7 symbols. Figure 400 illustrates a single resource block that may correspond to a single slot transmission of, for example, a 0.5 ms transmit time interval (TTI). The physical SL control channel may be configured to occupy multiple physical resource blocks (PRBs), for example, 10, 12, 15, 20, or 25 PRBs. The PSCCH may be limited to a single subchannel. For example, the PSCCH duration may be configured to be 2 symbols or 3 symbols. For example, a subchannel may include 10, 15, 20, 25, 50, 75, or 100 PRBs. Resources for SL transmission may be selected from a resource pool comprising one or more subchannels. As a non-limiting example, a resource pool may include between 1 and 27 subchannels. A PSCCH size may be established for the resource pool, for example, between 10% and 100% of a subchannel within a duration of 2 or 3 symbols. Figure 4ADiagram 410 in Figure 4 illustrates an example where the PSCCH occupies approximately 50% of a subchannel, as an example to illustrate the concept of the PSCCH occupying a portion of a subchannel. The physical SL shared channel (PSSCH) occupies at least one subchannel. In some examples, the PSCCH may include a first portion of SL control information (SCI), and the PSSCH may include a second portion of the SCI.

[0147] A resource grid can be used to represent the frame structure. Each time slot can include a resource block (RB) (also called a physical RB (PRB)) that extends over 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme. Figure 4A and Figure 4B As illustrated, some of the REs may include control information in the PSCCH and some may include a demodulation RS (DMRS).At least one symbol may be used for feedback. Figure 4A and Figure 4B An example is illustrated with two symbols for a physical SL feedback channel (PSFCH) with adjacent gap symbols. The symbols before and / or after the feedback can be used to transition between receiving data and sending feedback. The gap enables the device to switch from operating as a transmitting device to preparing to operate as a receiving device, for example, in a subsequent time slot. As illustrated, data can be sent in the remaining REs. The data can include data messages as described herein. The positioning of any of the data, DMRS, SCI, feedback, gap symbols, and / or listen-before-talk (LBT) symbols can be different from Figure 4A and Figure 4B Illustrated example. In some aspects, multiple time slots can be aggregated together.

[0148] Figure 5 An example 500 of SL communication between devices is illustrated. The communication may be based on a combination of Figure 4A and Figure 4BThe timeslot structure of the various aspects described. For example, UE 502 may transmit SL TB 514, for example, including a control channel (e.g., PSCCH) and / or a corresponding data channel (e.g., PSSCH), which may be received by UE 504, UE 506, or UE 508. The control channel may include information for decoding the data channel (e.g., SL control information (SCI)), which includes reservation information, such as information about time and / or frequency resources reserved for data channel transmission. For example, the SCI may indicate the TTI and the number of RBs that will be occupied by the data transmission. The SCI may also be used by the receiving device to avoid interference by avoiding transmission on reserved resources. In addition to SL reception, UE 502, UE 504, UE 506, or UE 508 may each have the capability of SL transmission. Therefore, UE 504, UE 506, and UE 508 are illustrated as transmitting SL TB 515, SL TB 516, and SL TB 520, respectively. SL TB 514, SL TB 515, SL TB 516, or SL TB 520 may be unicast, broadcast, or multicast to nearby devices. For example, UE 504 may transmit SL TB 515 intended for reception by other UEs within zone 501 of UE 504, and UE 506 may transmit SL TB 516. UEs outside zone 501 may not receive SL TBs transmitted within zone 501. For example, UE 504 may transmit SL TB 515 intended for reception by UE 502 and UE 506 within zone 501, but UE 508 may not receive SL TB 515. The encoder may have a larger transmission and reception range than the UE. For example, encoder 507 may be able to transmit SL TB 518 that can be received by each of UE 502, UE 504, UE 506, and UE 508, regardless of whether these UEs are in zone 501. Encoder 507 may communicate TBs with UE 502, UE 504, UE 506, and UE 508. For example, encoder 507 may broadcast SLTB 518 to UE 502, UE 504, UE 506, and UE 508. UE 502, UE 504, UE 506, and UE 508 may receive SLTB 518 from encoder 507. UE 502 may send SLTB 514 to encoder 507, and encoder 507 may receive SLTB 514 from UE 502. UE 504 may send SLTB 515 to encoder 507, and encoder 507 may receive SLTB 515 from UE 504. UE 506 may send SLTB 516 to encoder 507, and encoder 507 may receive SLTB 516 from UE 506.UE 508 may transmit SL TB 520 to encoder 507, and encoder 507 may receive SL TB 520 from UE 508. Transmitting or receiving one or more TBs or messages between encoder 507 and one or more of UE 502, UE 504, UE 506, or UE 508 may be referred to as communicating with one of the UEs. Encoder 507 may be, for example, an RSU or a base station. One or more of UE 502, UE 504, UE 506, or UE 508 may include, for example, a combination thereof. Figure 1 The encoder 507 may include a combination of Figure 1 Component 197 described.

[0149] Sidelink communication may be based on different types or modes of resource allocation mechanisms. In a first resource allocation mode (which may be referred to herein as "Mode 1"), centralized resource allocation may be provided by a network entity. For example, the network entity 509 may determine resources for SL communication and may allocate resources to UE 502, UE 504, UE 506, UE 508, or encoder 507 for SL TBs. The network entity 509 may provide the allocated SL resources in one or more downlink TBs 521. The network may provide a grant of SL resources in at least one of a time or a frequency at which the UE or encoder may use to send SL TBs via the network entity 509. For example, Figure 4A SL resources shown in FIG400 and / or Figure 4B In this first mode, the UE receives an allocation of SL resources from a wireless device designated to allocate SL resources, such as a network entity 509. In this first mode, the encoder receives an allocation of SL resources from a wireless device designated to allocate SL resources, such as a network entity 509. The network entity 509 may be a base station, such as a Figure 1 102 in the base station), another UE designated by the base station to allocate SL resources (such as Figure 1 UE 104 in the UE 104) or an RSU designated by the base station to allocate SL resources (such as Figure 1 Encoder 152 in).

[0150] In a second resource allocation mode (which may be referred to herein as "Mode 2"), distributed resource allocation may be provided. In Mode 2, each UE may autonomously determine resources for SL TBs. In order to coordinate the selection of SL resources by the various UEs, each UE may use listening techniques to monitor resource reservations of other SL UEs and may select resources for SL TBs from unreserved resources. A device communicating based on SL may determine one or more radio resources used by other devices in the time and frequency domains in order to select SL TB resources that avoid conflicts with other devices.

[0151] SL communication and / or resource reservation may be periodic or aperiodic, where the UE may reserve resources for a TB in the current timeslot and up to two future timeslots (as discussed below).

[0152] In a second mode (e.g., Mode 2), each UE may autonomously select resources for SL communication, for example, without a central entity (such as a base station) indicating the resources to be used for the device. A first UE may reserve the selected resources in order to inform other UEs about the resources that the first UE intends to use for SL TB.

[0153] In some examples, resource selection for SL communication can be based on a listening-based mechanism. For example, before selecting resources for data transmission, the UE can first determine whether the resources have been reserved by other UEs.

[0154] For example, as part of a listening mechanism for resource allocation mode 2, a UE may determine (e.g., listen) whether the selected SL resource has been reserved by other UEs before selecting the SL resource for data transmission. If the UE determines that the SL resource has not been reserved by other UEs, the UE may use the selected SL resource for sending data, for example, in a PSSCH transmission. The UE may estimate or determine which radio resources (e.g., SL resources) may be in use and / or reserved by other UEs by detecting and decoding SL control information (SCI) sent by other UEs. The UE may use a listening-based resource selection algorithm to estimate or determine which radio resources are in use and / or reserved by other UEs. The UE may receive an SCI from another UE, the SCI including reservation information based on a resource reservation field included in the SCI. The UE may continuously monitor (e.g., listen) and decode the SCI from the peer UE. The SCI may include reservation information, for example, indicating that a particular UE has selected a time slot and RB for future transmission. The UE may exclude resources used and / or reserved by other UEs from the set of candidate resources used by the UE for SL transmission, and the UE may select / reserve resources for SL transmission from resources that are not used and therefore form the set of candidate resources. The UE may continuously perform listening for SCIs with resource reservations in order to maintain a set of candidate resources from which the UE may select one or more resources for SL transmission. Once the UE selects a candidate resource, the UE may send an SCI indicating its own reservation of resources for SL transmission. The number of resources (e.g., subchannels per subframe) reserved by the UE may depend on the size of the data to be sent by the UE. Although this example is described with respect to a UE receiving reservation information from another UE, the reservation information may also be received from an RSU or other device that communicates based on SL.

[0155] At least one of UE 502, UE 504, UE 506, or UE 508 may be configured to perform a combined Figure 1 Aspects of the NC position tracking component 198.

[0156] The network entity 509 may be configured to perform the combined Figure 1 The NC handover initializes various aspects of component 199.

[0157] The encoder 507 may be configured to perform a combined Figure 1 The NC handover executes various aspects of component 197.

[0158] When multiple wireless devices receive transmissions simultaneously, these transmissions may interfere with each other. In one aspect, a first transmission transmitted from a first wireless device to a second wireless device may interfere with a second transmission transmitted from a third wireless device to the second wireless device. For example, Figure 5 In the example, SL TB 515 transmitted from UE 506 to UE 502 may interfere with SL TB 516 transmitted from UE 504 to UE 502.

[0159] Figure 6A A diagram 600 illustrating a network is shown having a UE 602 configured to transmit a SL signal 614 (e.g., a SL TB), a UE 606 configured to transmit a SL signal 612 (e.g., a SL TB), and a network entity 609 configured to transmit a downlink signal 619 to the UE within a zone 616. The downlink signal 619 may include a SL resource grant. In some aspects, Figures 6B to 6D Shown Figure 6A Communication links between wireless devices in the. Figures 6B to 6D May not be shown Figure 6A All possible communication links between wireless devices in zone 616 are possible because data sent to devices in zone 616 can be received by one, some, or all of the devices in zone 616.

[0160] The network entity 609 may determine resources for SL communication (eg, under Mode 1 SL resource allocation) and may allocate SL resources to the UEs 602 and 606 using downlink signals 619, which may include SL resource grants. Figure 6BA diagram 620 is shown with a communication link 621 between a UE 606 and a network entity 609 and a communication link 622 between a UE 602 and the network entity 609. The communication link 621 may be a Uu communication link that enables DL transmissions from the network entity 609 to the UE 602 and enables UL transmissions from the UE 602 to the network entity 609. The communication link 622 may be a Uu communication link that enables DL transmissions from the network entity 609 to the UE 606 and enables UL transmissions from the UE 606 to the network entity 609. The UE 602 may request one or more SL resource grants from the network entity 609 using the communication link 621. The network entity 609 may send one of the SL resource grants as a downlink signal 619 to the UE 602 using the communication link 621 (i.e., G) to grant the UE 602 SL resources that the UE 602 may use for SL communications. The SL resource grant may be used by the UE 602 to send SL transmissions, such as Figure 6A 6. UE 606 may utilize communication link 622 to request one or more SL resource grants from network entity 609. Network entity 609 may utilize communication link 622 (i.e., G) to transmit one of the SL resource grants as downlink signal 619 to UE 606 to grant UE 606 SL resources that UE 606 may utilize for SL communication. The SL resource grant may be used by UE 606 to transmit SL communications, such as Figure 6A SL signal 614 in.

[0161] The UEs may send SL TBs to each other using the SL resource grants obtained from the network entity 609 . Figure 6C Diagram 640 is shown with a communication link 641 between UE 602 and UE 604 and a communication link 642 between UE 602 and UE 608. Communication link 641 may be an SL communication link that enables SL transmission from UE 602 to UE 604 and enables SL transmission from UE 604 to UE 602. For example, communication link 641 may enable transmission of SL signal 612 from UE 604 to be received by UE 602. Communication link 642 may be an SL communication link that enables SL transmission from UE 602 to UE 608 and enables SL transmission from UE 608 to UE 602. For example, communication link 642 may enable transmission of SL signal 612 from UE 608 to be received by UE 602. UE 602 may use Figure 6C Communication links 641 and 642 in the broadcast, unicast or multicast Figure 6A One or more of the SL signals 612 in.

[0162] Figure 6DDiagram 660 is shown with a communication link 661 between UE 606 and UE 604 and a communication link 662 between UE 606 and UE 608. Communication link 661 may be an SL communication link that enables SL transmission from UE 606 to UE 604 and enables SL transmission from UE 604 to UE 606. For example, communication link 661 may enable transmission of SL signal 614 from UE 604 to be received by UE 606. Communication link 662 may be an SL communication link that enables SL transmission from UE 606 to UE 608 and enables SL transmission from UE 608 to UE 606. For example, communication link 662 may enable transmission of SL signal 614 from UE 608 to be received by UE 606. UE 606 may use Figure 6C Communication links 661 and 662 in the broadcast, unicast or multicast Figure 6A One or more of the SL signals 614 in.

[0163] If the SL signal 612 and the SL signal 614 are transmitted with overlapping resources (e.g., overlapping frequencies and overlapping times), one or more receiving devices may fail in decoding one or more TBs of the SL signal 612 and the SL signal 614. The UE 602 may multicast or unicast one of the SL signals 612 to the UEs 604 and 608 in the zone 616 using the SL resources allocated by the network entity 609 via the downlink signal 619, such as Tx a UE 606 may also use SL resources allocated by network entity 609 via downlink signal 619 to multicast or unicast one of SL signals 614, such as Tx 1, to UE 604 and UE 608 in zone 616 during overlapping time periods using frequencies that may interfere with SL signal 612. b Because UE 602 and UE 606 may use overlapping SL resources to send SL TBs, UE 604 and UE 608 may miss receiving (ie, miss successfully decoding) one of SL signals 612 and / or one of SL signals 614 .

[0164] In one aspect, UE 602 may use Figure 6C The communication link 641 in Figure 6A One of the SL signals 612 in Tx a Multicast to UE 604 and use Figure 6C The communication link 642 in the UE 606 multicasts one of the SL signals 612 to the UE 608. At the same time, the UE 606 can use Figure 6D The communication link 661 in Figure 6A One of the SL signals 614 in Tx bMulticast to UE 604 and use Figure 6D The communication link 642 in the UE 608 multicasts one of the SL signals 614 to the UE 608. The broadcast of one of the SL signals 612 and / or one of the SL signals 614 may use V2X or another type of SL communication. a and Tx b The broadcast of Tx may have overlapping SL resources (overlapping time domain and overlapping frequency domain), so the UE 604 a or Tx b The reception of Tx may fail and / or the UE 604 may a or Tx b Alternatively, due to interference, UE 604 and / or UE 608 may fail to receive Tx a to decode, and / or may fail to decode the Tx b UE 602 may try to decode by repeatedly multicasting or unicasting Tx a (SL TB of SL signal 612) to use error correction until UE 604 and UE 608 confirm receipt of Tx a Similarly, UE 606 may try to transmit the message by repeatedly multicasting or unicasting Tx b (SL TB of SL signal 614) to use error correction until UE 604 and UE 608 confirm receipt of Tx b Such retransmissions may waste resources, especially if region 616 has many other UEs (not shown) performing such transmissions.

[0165] Figure 7A shows an example similar to Figure 6A FIG700 is a diagram of a network of networks. Figure 7A UEs 702, 704, 706, and 708 in FIG. 6A to 6D UEs 602, 604, 606 and 608 in. Figure 7A The network entity 709 in may be similar to 6A to 6D The network entity 609 in. Figure 7A The network in may have an encoder 707 that is configured to encode TB using NC to increase system capacity and improve resource utilization. In some aspects, Figures 7B to 7E Shown Figure 7A Communication links between wireless devices in the. Figures 7B to 7E May not be shown Figure 7A All possible communication links between wireless devices in zone 716 are possible because data sent to devices in zone 716 can be received by one, some, or all of the devices in zone 716.

[0166] Similar to Figure 6A The network entity 609 in Figure 7A The network entity 709 in may also determine resources for SL communication and may allocate resources to one or more of the UEs 702, 704, 706, and 708 using a downlink signal 719. The downlink signal 719 may include a SL resource grant. Figure 7B Diagram 720 is shown with a communication link 721 between UE 706 and network entity 709, a communication link 722 between UE 702 and network entity 709, and a communication link 723 between encoder 707 and network entity 709. Communication link 721 may be a Uu communication link that enables DL transmissions from network entity 709 to UE 702 and UL transmissions from UE 702 to network entity 709. Communication link 722 may be a Uu communication link that enables DL transmissions from network entity 709 to UE 706 and UL transmissions from UE 706 to network entity 709. Communication link 723 may be a Uu communication link that enables DL transmissions from network entity 709 to encoder 707 and UL transmissions from encoder 707 to network entity 709. UE 702 may request one or more SL resource grants from network entity 709 using communication link 721. The network entity 709 may use the communication link 721 (i.e., G) to send one or more SL resource grants as downlink signals 719 to the UE 702 to grant the UE 702 SL resources that the UE 702 may use for SL communications. The one or more SL resource grants may be used by the UE 702 to send SL transmissions, such as Figure 7A 719 (e.g., SL TB). UE 706 may request one or more SL resource grants from network entity 709 using communication link 722. Network entity 709 may transmit one or more of the SL resource grants as downlink signal 719 to UE 706 using communication link 722 (i.e., G) to grant UE 706 SL resources that UE 706 may use for SL communication. The one or more SL resource grants may be used by UE 706 to transmit SL transmissions, such as Figure 7A The encoder 707 may use a communication link 723 to request one or more SL resource grants from the network entity 709. The network entity 709 may use a communication link 723 (i.e., G) to send one or more of the SL resource grants as a downlink signal 719 to the encoder 707 to grant the encoder 707 SL resources that the encoder 707 may use for SL communication. The SL resource grants may be used by the encoder 707 to send SL transmissions, such as Figure 7A SL signal 717 (e.g., SL TB or SL NC TB) in.

[0167] Similar to Figure 6A UE in Figure 7B The UEs in the network may use the SL resource grant obtained from the network entity 709 to send SL TBs to each other. Figure 7C Diagram 740 is shown with a communication link 741 between UE 702 and UE 708, a communication link 742 between UE 702 and UE 704, and a communication link 743 between UE 702 and encoder 707. Communication link 741 may be an SL communication link that enables SL transmission from UE 702 to UE 704 and from UE 704 to UE 702. Communication link 742 may be an SL communication link that enables SL transmission from UE 702 to UE 708 and from UE 708 to UE 702. Communication link 743 may be an SL communication link that enables SL transmission from UE 702 to encoder 707 and from encoder 707 to UE 702. UE 702 may use Figure 7C Communication links 741, 742 and 743 in the broadcast, unicast or multicast Figure 7A One or more of the SL signals 712 in.

[0168] Figure 7D Diagram 760 is shown with a communication link 761 between UE 706 and UE 708, a communication link 762 between UE 706 and UE 704, and a communication link 763 between UE 706 and encoder 707. Communication link 761 may be an SL communication link that enables SL transmission from UE 706 to UE 704 and from UE 704 to UE 706. Communication link 762 may be an SL communication link that enables SL transmission from UE 706 to UE 708 and from UE 708 to UE 706. Communication link 763 may be an SL communication link that enables SL transmission from UE 706 to encoder 707 and from encoder 707 to UE 706. UE 706 may use Figure 7D Communication links 761, 762, 763 in the broadcast, unicast or multicast Figure 7A One or more of the SL signals 714 in.

[0169] Similar to Figure 6A The transmission of SL signal 612 and SL signal 614 in Figure 7AThe transmission of the SL signal 712 and the SL signal 714 in the zone 716 may have overlapping resources in the time domain or the frequency domain, or may have resources in the frequency domain that are close enough to interfere with each other. Using overlapping or interfering resources to transmit the SL signal 712 and the SL signal 714 may cause one or more receiving devices to miss receiving one or more TBs of the SL signal 712 and the SL signal 714, or fail to decode the one or more TBs of the SL signal 712 and the SL signal 714. The UE 702 may use the SL resources allocated by the network entity 709 to multicast or unicast one of the SL signals 712 to the UEs 704, UEs 708, and encoders 707 in the zone 716, such as Tx a UE 706 may also use the SL resources allocated by network entity 709 to multicast or unicast one of the SL signals 714 to UE 704, UE 708, and encoder 707 in zone 716 during the overlapping time period, such as Tx b Because UE 702 and UE 706 may use overlapping or interfering SL resources to transmit SL TBs, UE 704 and UE 708 may miss receiving or miss successfully decoding one of SL signals 712 and / or one of SL signals 714, such as the Tx signal of SL signal 712. a or Tx of SL signal 714 b .

[0170] Encoder 707 may be a device such as an RSU or UE configured to encode TBs according to an NC algorithm (as explained in more detail below) to generate NC transmissions (ie, SL NC TBs or NCTBs) that may be sent to UEs 704 and 708 . Figure 7E Diagram 780 is shown with a communication link 781 between encoder 707 and UE 704 and a communication link 782 between encoder 707 and UE 708. Communication link 781 may be an SL communication link that enables SL transmission from encoder 707 to UE 704 and from UE 704 to encoder 707. Communication link 782 may be an SL communication link that enables SL transmission from encoder 707 to UE 708 and from encoder 707 to UE 706. Encoder 707 may use Figure 7E Communication links 781 and 782 in the broadcast, unicast or multicast Figure 7A One or more of the SL signals 717 in.

[0171] As explained in more detail below, an NC algorithm may be used to generate an NC TB. The NC algorithm may use a single parity check code to correct an erasure. For example, an encoder may add additional linear independence constraints to a linear system on a Galois field to recover erasures. The NC algorithm may be described as follows. The input to the encoder may be a set of messages, such as a vector [a, b], where a is a first message and b is a second message, or such as a vector [a, b, c], where a is a first message, b is a second message, and c is a third message. In addition to combinations of the same message (i.e., joint messages), the output of the encoder may be a vector of the same message, such as or The combination of messages may be generated in any suitable manner, for example via AND (a+b), OR (a or b), or Function generation. Output of the encoder It can be viewed as a linear system with three variables and four linearly independent constraints on a Galois field, such as:

[0172]

[0173] Four linearly independent constraints Any three of can be used to determine one of the three variables [a, b, c]. For example, if the receiving device successfully decodes a and b and does not successfully decode c, the receiving device can use a, b, and On the other hand, if the receiving device successfully decodes a and c and fails to decode b, the receiving device can use a, c and To recover the lost b.

[0174] about Figure 7A In the diagram 700, the input vector to the encoder 707 may be TB Tx a and TB Tx b (ie, the input vector [Tx a ,Tx b ]), and the encoder 707 may encode those inputs to generate NC TB f(Tx a ,Tx b In one aspect, f(Tx a ,Tx b ) can be defined as a vector The value is an additional linearly dependent constraint added to the system. On the other hand, f(Tx a ,Tx b ) can be defined as no TB Tx a and TB Tx bVector The encoder 707 can convert the vector Output to a receiving device, such as UE 704 or UE 708.

[0175] If UE 704 or UE 708 is missing a TB (such as TB Tx a and TB Tx b ), the UE can use the output vector of encoder 707 to reconstruct the lost message. For example, if the received vector is Then we can sum the other values To restore the erased element Tx b .in other words, Figure 7A The NC of diagram 700 in can be viewed as an overdetermined linear system (on a Galois field) with two variables and three linearly independent constraints, where any two constraints (one erasure) are sufficient to determine the value of the missing variable.

[0176] The encoder 707 may send NC TB f(Tx a ,Tx b ) as Figure 7A The encoder 707 may send the NC TB f(Tx) to the UE 704 or the UE 708. a ,Tx b ),like Figure 7E As shown, this allows the receiving device to retrieve the TB Tx of the SL signal 712 a or TB Tx of SL signal 714 b In one aspect, NC TB f(Tx a ,Tx b ) may be an output vector sent as one of the SL signals 717 In one aspect, the encoder 707 may not resend the SL TB Tx a and Tx b Send added constraints (for example, ) as one of the SL signals 717, because the value Tx a like Figure 7C As shown, it is sent by UE 702, and Tx b like Figure 7D As shown, it is sent by UE 706. Then, as long as the UE knows the three constraints , either UE 704 or UE 708 can retrieve the missing value. Figure 7A Two SL TB variables are shown (Tx of SL signal 712a and Tx of SL signal 714 b ), but any number of SL TBs can be used in a similar manner for NC systems. For example, in a system with three simultaneously transmitting UEs, where the first UE transmits SL TB a, the second UE transmits SL TB b, and the third UE transmits SL TB c, the input [a, b, c] can be encoded as The received vector Can be used to sum over others To restore the erased SL TB b.

[0177] NC can be centralized, meaning that a designated device, such as an encoder for a zone, can perform NC for devices in the zone, and non-designated devices cannot perform NC for devices in the zone. For example, encoder 707 can be a designated encoder for zone 716, such that encoder 707 performs NC for UEs 702, 704, 706, and 708 in zone 716. As described above, encoder 707 can provide an NC TB that performs NC on packets (e.g., Tx of SL signal 712) previously sent by UEs 704 and 708 to receiving devices in zone 716, such as UEs 702 and 706. a and Tx of SL signal 714 b ) are combined. For example, the NC TB of the SL signal 717 may include a combination of one of the SL signals 712 and one of the SL signals 714. The combination of one of the SL signals 712 and one of the SL signals 714 is Figure 7A The diagram 700 in FIG is shown as a function f(Tx a ,Tx b In one aspect, the encoder 707 can a and Tx b Performing XOR to apply the NC algorithm to one or more of the SL signals 712 and one or more of the SL signals 714 to generate In other words, the function f(Tx a ,Tx b ) can be input Tx a and Tx b Configuring encoder 707 to retransmit SL signal 712 and SL signal 714 as SL signal 717 can improve the retransmission latency because the SL messages from UE 702 and UE 706 are retransmitted by encoder 707 as NC TB. Similarly, Figure 7AAs an example of how the joint transmission of NC TBs can improve reception, if UE 704 receives one of the SL signals 714 from UE 706 as Tx b , but not one of the SL signals 712 is received from UE 702 as Tx a , then UE704 may receive one of the SL signals 717 from encoder 707 as a signal containing Tx b and Tx a The joint message f(Tx a ,Tx b ). UE704 can use the previously received Tx b With f(Tx a ,Tx b ) are used together to determine the lost Tx a Since f(Tx a ,Tx b ) can be Tx a and Tx b XOR combination of (for example, ), so it can be achieved by Up-reverse Tx b XOR combination to derive the lost Tx a The network entity 709 may be configured to designate one or more devices for performing NC within the region 716 , such as the encoder 707 within the region 716 .

[0178] The NC system increases system capacity and improves resource utilization by reducing the number of retransmissions in the system while maintaining performance. This can enable an increase in the number of UEs or the amount of traffic per UE, as more UEs can send messages to each other within a region with the increased reliability provided by the encoder. After an initial transmission (e.g., one of SL signals 712 by UE 702 and one of SL signals 714 by UE 706), each retransmission by the original transmitter can be replaced or supplemented by one of the NC TBs (e.g., SL signal 717) transmitted by the encoder (e.g., encoder 707) using NC.

[0179] Each of the transmissions of SL signal 712, SL signal 714, and SL signal 717 may be performed using SL resources allocated by network entity 709 using an SL resource grant transmitted using downlink signal 719. Communication with network entity 709 (e.g., downlink signal 719) may be performed using Uu resources. In some aspects, communication with network entity 709 may be performed using other resources, such as SL resources using SL signals or other signals. Encoder 707 may be an element of another wireless device, such as an element of network entity 709 or an element of UE 702. Thus, in one aspect, SL signal 717 may transmit both SL signal 712 and SL signal 717.

[0180] Figure 9 A connection flow diagram 900 illustrating an example of sidelink communication between an example UE 902, a UE 904, and an encoder 908 and a network entity 906 coordinating NC between the UE 902, the UE 904, and the encoder 908 is shown. The UE 902, the UE 904, the network entity 906, and the encoder 908 may be similar to Figure 7A 704, a network entity 709, and an encoder 707. The UE 902 may send a SL resource request 912 to the network entity 906, and the encoder 908 may send a SL resource request 913 to the network entity 906. At 914, in response to receiving the SL resource request, the network entity 906 may provide a grant of SL resources to the UE 902 and the encoder 908. In one aspect, the network entity 906 may provide a grant of SL resources to the device without first receiving a SL resource request, for example, by determining that the wireless device is configured to send messages using SL resources. The network entity 906 may send a SL resource grant 916 to the UE 902 to allow the UE 902 to send one or more SL messages, and the network entity 906 may send a SL resource grant 917 to the encoder 908 to allow the encoder 908 to send one or more SL messages. Downlink transmissions and uplink transmissions with the network entity 906 and the UE 902 and with the network entity 906 and the encoder 908 may be performed using Uu resources.

[0181] The UE 902 may send a SL TB 918 to wireless devices that may receive signals within the area, such as the UE 904 and the encoder 908. The UE 902 may send the SL TB 918 using SL resources provided by the SL resource grant 916 received from the network entity 906. The UE 902 may send the SL TB 918 with a network decoding request flag, which may be used to instruct a device such as the encoder 908 to encode the SL TB. The UE 902 may send the SL TB 918 separately from the network decoding request flag, which may also be sent to the encoder 908. For example, the UE 902 may send an NC request 915 to the encoder 908 to request the encoder 908 to encode the SL TB 918 using an NC. The encoder 908 may be any suitable device configured to decode TBs, such as an RSU, a UE relay, another UE, or a base station (e.g., a gNB). The encoder 908 may send an ACK / NACK 919 to the UE 902 for the request to encode the SL TB 918. For example, the encoder 908 may send an ACK to confirm receipt or acceptance of decoding the SL TB 918, and may send a NACK to indicate a failure to receive the SL TB 918. The encoder 908 may use the SL resources provided by the SL resource grant 917 from the network entity 906 to send the ACK / NACK 919 for the request. At 920, in response to receiving the SL TB 918, the encoder 908 may associate the SL TB 918 with a UE in the region of the encoder 908, such as a UE. Figure 7A The encoder 908 may transmit the SL NC TB 922 to the UE 904. The encoder may transmit the SL NC TB 922 using the SL resources provided by the SL resource grant 917 from the network entity 906.

[0182] The UE 902 may use one or both of the received SL TB 918 and the SL NC TB 922 to recover from erasures of failed transmissions. For example, the UE 902 may use the SL NC TB 922 to recover from failed decoding of the SL TB 922 by summing the SL NC TB 918 with other TB values ​​received from other UEs in the same zone. On the other hand, the UE 902 may use the SLNC TB 922 and the SL TB 918 to recover from failed decoding of a TB received from another UE in the same zone by summing the SL NC TB 922 and the SL TB 918 with other TB values ​​received from other UEs in the same zone to recover the erased TB.

[0183] Although the network entity 906 can coordinate with UEs and encoders within the same zone, transmissions may be lost when a device migrates from one zone to another. Additional coordination can be used to enable the network entity to hand over network decoding from an encoder in one zone to an encoder in another zone. The network entity can act as a coordination component and can be opaque to the devices (e.g., the devices can not send any of the TBs of these devices to the coordinating network entity). For example, the network entity can send an NC handover request to one or more encoders to coordinate the handover from one encoder to another encoder, the encoder can send a confirmation message to the network entity to provide the network entity with context information about the handover, and the SL NC TB (NC send) can include one or more indicators in its header to provide context information to the receiving encoder or UE.

[0184] Figure 8AA diagram of an NC handover request 800 is shown, including an encoder ID field 802, an encoder ID field 804, an encoder transmit field 806, a UE transmit field 808, a transmit type field 810, and an additional handover request field set 812. Each of the fields may have one or more bits for indicating context information associated with the NC handover request 800. The encoder ID field 802 may be used to provide an identifier (ID) of a first encoder, or source encoder, for the NC handover request 800. The encoder ID field 804 may be used to provide an ID of a second encoder, or destination decoder, for the NC handover request 800. The encoder transmit field 806 may be used to indicate whether an encoder should transmit a SL NC TB to another encoder (e.g., a first encoder associated with a first zone transmits a SL NC TB to a second encoder associated with a second zone, or a second encoder associated with a second zone transmits a SL NC TB to a first encoder associated with the first zone), where the UE is moving from the first zone to the second zone. The UE transmit field 808 may be used to indicate whether an encoder should transmit or retransmit a SL TB to a UE in the zone associated with the encoder. The transmission type field 810 may be used to indicate whether the encoder should transmit the TB for NC purposes (e.g., whether the TB is an NC transmission, whether the encoder should encode the SL NC TB for transmission). The additional handover request field set 812 may be used to provide the encoder with additional information that may be used to perform an NC handover from the encoder to another encoder, such as the UE ID, the region ID of the region from which the UE is moving, the region ID of the region to which the UE is moving, or the size of the SL TB associated with the UE. Although the NC handover request 800 is shown as having an encoder ID field 802, an encoder ID field 804, an encoder transmission field 806, a UE transmission field 808, a transmission type field 810, and an additional handover request field set 812, in some aspects, the NC handover request 800 may have more or fewer fields. For example, in one aspect, the NC handover request may not have a transmission type field.

[0185] Figure 8BA diagram of an acknowledgement message 820 is shown that includes a handover accept field 822, a buffer field 824, an acknowledgement (ACK) or negative acknowledgement (ACK / NACK) field 826, and an additional acknowledgement field set 828. Acknowledgement message 820 may be in uplink control information (UCI) format. Each of the fields may have one or more bits for indicating context information associated with acknowledgement message 820. Handover accept field 822 may be used to provide an indication of whether the transmitting encoder has accepted the incoming NC handover request. Buffer field 824 may be used to provide an indication of whether the transmitting encoder has buffered SL NC TBs for transmission to the UE. ACK / NACK field 826 may be used to provide an indication of whether the transmitting encoder has successfully received the SL NC TB from another encoder. Additional acknowledgement field set 828 may be used to provide feedback to a network entity or to another encoder in response to receiving the NC handover request. While the confirmation message 820 is shown with a handover accepted field 822, a buffer field 824, an ACK / NACK field 826, and an additional set of confirmation fields 828, in some aspects, the confirmation message 820 may have more or fewer fields. For example, in one aspect, the confirmation message may not have a buffer field.

[0186] Figure 8C A diagram of a SL NC TB 840 is shown including a header 841 and a payload 848. The payload may include data that may be used by a receiving UE to reconstruct the lost message, such as Figure 7A f(Tx) of the SL signal 717 a ,Tx b ), or a vector for received messages a, b, and c The header 841 may include an NC handover request ID field 842, an encoder ID field 844, and an additional NC send field set 846. Each of the fields may have one or more bits for indicating context information associated with the SL NC TB 840. The NC handover request ID field 842 may be used to provide an NC handover request (such as Figure 8A842, the encoder ID field 844, and the additional NC send field set 846.

[0187] Figure 10A Diagram 1000 illustrating a network having zone 1016 with UEs 1002 , 1004 , and 1006 and encoder 1007 , and zone 1026 with encoder 1027 at time t 0 is shown. Figure 10B Shown is an example Figure 10A FIG1040 is a diagram of a network in which UE 1002 moves from zone 1016 to zone 1026 at time t1. UEs 1002, 1004, and 1006 may be similar to 7A to 7E UE 702, 704 and 706 in. Encoders 1007 and 1027 can be similar to 7A to 7E Encoder 707 in. Figure 10C The communication links between the network entity 1009 and the UEs 1002 , 1004 , 1006 and encoders 1007 and 1027 at time t1 are shown.

[0188] like Figure 10A As shown in diagram 1000 in FIG. 1 , UE 1002 may send a SL signal 1012 (eg, SL TB, such as SL TB Tx) to UE 1004 and encoder 1007. a ). UE 1006 may send a SL signal 1014 (eg, SL TB, such as SL TB Tx) to UE 1004 and encoder 1007. b ).like Figure 10A Figure 1000 and Figure 10B As shown in FIG. 1040 , UE 1002 may Figure 10A The zone 1016 at time t0 moves to Figure 10B 1026 at time t1 in the region. UE 1002 may send a SL signal 1012 (eg, SL TB, such as SL TB Tx) to UE 1004 and encoder 1007. aWhile UE 1006 is moving from region 1016 to region 1026, UE 1002 may also send a SL signal 1014 (eg, SL TB, such as SLTB Tx) to UE 1004 and encoder 1007. b ).from Figure 10A From time t0 to Figure 10B At time t1, UE 1006 may not move outside of zone 1016.

[0189] If UE 1002 stays in zone 1016 long enough so that UE 1004 can move to Figure 10B The Tx of the SL signal 1012 is successfully received before the zone 1026 at time t1 a , Tx of SL signal 1014 b or f(Tx a ,Tx b ) (i.e., it does not fail in decoding it), then the UE 1004 can successfully receive the Tx of the SL signal 1012 using the NC technology. a and Tx of SL signal 1014 b For example, in one aspect, if UE 1004 does not receive SL signal 1017 at f(Tx a ,Tx b ) successfully receives the Tx of SL signal 1012 a and Tx of SL signal 1014 b , then UE 1004 has successfully received the Tx of SL signal 1012 a and Tx of SL signal 1014 b On the other hand, if the UE 1004 does not receive the SL signal 1014 at Tx b Successfully received SL signal 1012 Tx a and f(Tx of SL signal 1017 a ,Tx b ), UE 1004 can use Tx a Reverse f(Tx a ,Tx b ) function to derive Tx b On the other hand, if the UE 1004 does not receive the SL signal 1012 at Tx a Successfully received SL signal 1014 Tx b and f(Tx of SL signal 1017 a ,Tx b ), UE 1004 can use Tx bReverse f(Tx a ,Tx b ) function to derive Tx a .

[0190] However, if the UE 1002 successfully receives the Tx of the SL signal 1014 a , Tx of SL signal 1012 b Or f(Tx of SL signal 1012 a ,Tx b ), the UE 1004 moves from the zone 1016 to the zone 1026 before at least two of the zones 1016 and 1026, then without additional coordination from the network entity 1009, the UE 1004 may not successfully receive the Tx signal of the SL signal 1014. a and Tx of SL signal 1017 b For example, the UE 1004 may receive the Tx signal 1012 of the SL a Previously, UE 1004 may move to zone 1026, thereby preventing UE 1004 from receiving the Tx signal 1012 of SL. a On the other hand, the encoder 1007 may receive the SL signal 1017 Tx a Previously, the UE 1004 may move to the region 1026, thereby preventing the encoder 1007 from generating the f(Tx a ,Tx b ).

[0191] Network entity 1009 may communicate with any one of UE 1002, UE 1004, UE 1006, encoder 1007 and / or encoder 1027 to coordinate the successful transmission of SL signal 1012, SL signal 1014 and SL signal 1017 to UE 1004, even if UE 1002 moves from region 1016 to region 1026 before UE 1004 can successfully receive SL signal 1012 or SL signal 1017. Figure 10CA diagram 1080 is shown having a communication link 1081 between encoder 1007 and network entity 1009, a communication link 1082 between UE 1006 and network entity 1009, a communication link 1083 between UE 1004 and network entity 1009, a communication link 1084 between UE 1002 and network entity 1009, a communication link 1085 between encoder 1027 and network entity 1009, and a communication link 1086 between encoder 1007 and encoder 1027. Communication link 1081 may be a Uu communication link that implements DL signals 1019 from network entity 1009 to encoder 1007 and implements UL transmissions 1018 from encoder 1007 to network entity 1009. Communication link 1082 may be a Uu communication link that implements DL signals 1019 from network entity 1009 to UE 1006 and implements UL transmission 1013 from UE 1006 to network entity 1009. Communication link 1083 may be a Uu communication link that implements DL signals 1019 from network entity 1009 to UE 1004 and implements UL transmission 1015 from UE 1004 to network entity 1009. Communication link 1084 may be a Uu communication link that implements DL signals 1019 from network entity 1009 to UE 1002 and implements UL transmission 1011 from UE 1002 to network entity 1009. Communication link 1085 may be a Uu communication link that implements DL signals 1019 from network entity 1009 to encoder 1027 and implements UL transmission 1038 from encoder 1027 to network entity 1009. DL signal 1019 may be, for example, a SL resource grant or an NC handover request. UL transmission 1011 from UE 1002 may be, for example, a request for SL resources or location information associated with UE 1002 (e.g., BSR, UE ID, current zone ID, GNSS location information, geographic location). UL transmission 1013 from UE 1006 may be, for example, a request for SL resources or location information associated with UE 1006. UL transmission 1015 from UE 1004 may be, for example, a request for SL resources or location information associated with UE 1004. UL transmission 1018 from encoder 1007 may be, for example, a request for SL resources, location information associated with UEs in zone 1016 (e.g., UEs 1002, 1004, and 1006 at time t0, UEs 1004 and 1006 at time t1), or a confirmation message associated with the NC handover request. The UL transmission 1038 from the encoder 1027 may be, for example, a request for SL resources, location information associated with a UE in the zone 1016 (eg, UE 1002 at time t1), or a confirmation message associated with the NC handover request.

[0192] The communication link 1086 may be an SL communication link that enables SL transmission from the encoder 1007 to the encoder 1027 and from the encoder 1027 to the encoder 1007. In another aspect, the communication link 1086 may be a backhaul link or a midhaul link between the encoder 1007 and the encoder 1027. The encoder 1007 may use Figure 10C Communication link 1086 in broadcast, unicast or multicast Figure 10A The encoder 1027 (eg, SL TB or SL NC TB) may use one or more of the SL signals 1017 (eg, SL TB or SL NC TB) in the Figure 10C Communication link 1086 in broadcast, unicast or multicast Figure 10A The SL signal 1017 from the encoder 1007 may be, for example, an SL TB, an SL NC TB, or an acknowledgment message. The SL signal 1037 from the encoder 1027 may be, for example, an SL TB, an SL NC TB, or an acknowledgment message.

[0193] Network entity 1009 may send DL signal 1019 to any of UE 1002, UE 1004, UE 1006, encoder 1007, and / or encoder 1027 to coordinate the successful transmission of SL signal 1012, SL signal 1014, and SL signal 1017 to UE 1004, even if UE 1002 moves from region 1016 to region 1026 before UE 1004 can successfully receive SL signal 1012 or SL signal 1017. For example, at time t1, UE 1002 may send one or more of SL signals 1012 to encoder 1027, and encoder 1027 may send one or more of SL signals 1012 to encoder 1007 as SL signal 1037. Encoder 1027 may have a larger sidelink transmission range than UE 1002, or may be able to communicate with encoder 1007 via other means, such as a backhaul or midhaul link. Network entity 1009 may be configured to obtain information that UE 1002 is moving from zone 1016 to zone 1026 and initiate an NC handover from encoder 1007 to encoder 1027. NC handover is a handover from one encoder to another, where each encoder is configured to retransmit received transmissions using NC. Network entity 1009 may receive periodic location information from UE 1002, or may receive periodic location information about UEs in zone 1016 from encoder 1007, or may receive periodic location information about UEs in zone 1026 from encoder 1027. The periodic location information may indicate to network entity 1009 that UE 1002 is moving from zone 1016 to zone 1026. Encoder 1007 may receive SL signal 1012 from UE 1002 and SL signal 1014 from UE 1006, and retransmit the received transmissions as SL signal 1017. The network entity 1009 may also be configured to allocate appropriate SL resources to each device, for example, to allocate SL resources to the encoder 1027 to allow the encoder 1027 to forward the SL signal from the UE 1002 to the encoder 1007 .

[0194] Figure 11 A connection flow diagram 1100 illustrating an example of sidelink communication between UE 1102, UE 1104, encoder 1108, and encoder 1110 and a network entity 1106 coordinating NC between UE 1102, UE 1104, encoder 1108, and encoder 1110 is shown. UE 1102, UE 1104, network entity 1106, encoder 1108, and encoder 1110 may be similar to 10A to 10C10. UE 1002, UE 1004, network entity 1009, encoder 1007, and encoder 1027 in FIG. When UE 1102 moves from an area covered by encoder 1108 to an area covered by encoder 1110, network entity 1106 may coordinate NC between encoder 1108 and encoder 1110. Encoder 1108 and encoder 1110 may communicate with each other using PSCCH or PSFCH.

[0195] UE 1102 may provide location information 1112 to network entity 1106 via a message, such as sent over the uplink. This may allow network entity 1106 to be aware of the movement of UE 1102. Location information 1112 may include, for example, a BSR. The BSR may include, for example, a UE identifier (ID), a new zone ID (e.g., 10A to 10C The location information 1112 may be provided to the network entity 1106 periodically (e.g., every 100 ms, every second, or every 10 seconds), or in response to an event, such as movement from the UE's last reported or transmitted location that meets or exceeds a threshold (e.g., 20 m).

[0196] The encoder 1108 may provide location information 1113 to the network entity 1106 via a message such as an uplink transmission. This may allow the network entity 1106 to be aware of the movement of any UE in SL communication with the encoder 1108. The location information 1113 may provide location information about any UE affiliated with the encoder 1108. The location information 1113 may include a report of the location of any UE affiliated with the encoder 1108 (e.g., communicating with the encoder 1108 within a threshold time period (e.g., 10 seconds)). The location information 1113 may include, for example, a region ID, a GNSS position, or a geographic location of each UE in the set of UEs associated with the encoder 1108. The region ID may be a lossy and / or compressed form of the GNSS position or geographic location of the UE. The region ID may identify a first region. The location information 1113 may also include location information associated with the encoder 1108. The encoder 1108 may be configured to periodically provide the location information 1113 to the network entity 1106, or may be configured to provide the location information 1113 to the network entity 1106 in response to an event, such as movement of the UE or encoder 1108 from its last reported location that meets or exceeds a threshold (e.g., 20 m) or a request from the network entity 1106. The location information 1113 may also include the number of UEs belonging to the encoder 1108 in its region.

[0197] At 1114, network entity 1106 may use at least a portion of one or both of location information 1112 and / or location information 1113 to determine movement of UE 1102 from the first region to the second region. In one aspect, network entity 1106 may process multiple received location information transmissions to generate a map of mobile UEs (e.g., vehicles), which network entity 1106 may use to determine that the UE is moving from one region to another. At 1114, network entity 1106 may use such a map to determine that UE 1102 is moving from the region of encoder 1108 to the region of encoder 1110.

[0198] In response to determining that UE 1102 is moving from the region of encoder 1108 to the region of encoder 1110, network entity 1106 may make a handover request (eg, Figure 8A NC handover request 800 in is initialized. Network entity 1106 may send a handover request 1116 as a downlink transmission to encoder 1110 (i.e., the destination encoder). Network entity 1106 may send a handover request 1117 as a downlink transmission to encoder 1108 (i.e., the source encoder). Handover request 1116 and handover request 1117 may be the same or different. For example, handover request 1116 may have the encoder ID of encoder 1110 and handover request 1117 may have the encoder ID of encoder 1108, or handover request 1116 may have a subset of the information of handover request 1117, or vice versa. Handover requests 1116 and / or 1117 may be in any suitable format, such as a DCI format, a MAC-CE format, or a newly defined format for NC handover.

[0199] The handover request 1116 and / or 1117 may include an indication of a destination encoder (e.g., a second encoder in a second zone, where the UE 1102 moves from a first zone having a first encoder to a second zone having a second encoder). The destination encoder may be encoder 1110. In one aspect, the handover request 1116 and / or 1117 may include a destination encoder ID field for the TB. For example, Figure 8A The encoder ID field 804 of the NC handover request 800 in the example may store the encoder ID of the encoder 1110. The handover request 1116 and / or 1117 may include an indication of the encoder 1108 in the source encoder ID field for the TB. In one aspect, the handover request 1116 and / or 1117 may include a source encoder ID field for the TB. For example, Figure 8A The encoder ID field 802 of the NC handover request 800 in the example may store the encoder ID of the encoder 1108. The handover request 1116 and / or 1117 may include an instruction for the encoder 1108 to send the SL NC TB to the encoder 1110. For example, Figure 8A The encoder send field 806 of the NC handover request 800 in the NC handover request 800 may store an indication of whether the encoder 1110 should send the SL NC TB to the encoder 1108. In one aspect, the handover request 1116 and / or 1117 may include, for example, in the send type field, a bit to indicate that the encoder 1108 should send the TB to the encoder 1110 for NC purposes. For example, when this bit is set, the handover request 1116 and / or 1117 may indicate that the encoder 1108 should send the SL NC TB 1126 to the encoder 1110. In one aspect, Figure 8A The encoder transmit field 806 of the NC handover request 800 in the network entity 1106 may store such a bit. The network entity 1106 may be configured to set the bit in response to the encoder 1110 not having a TB in the encoder's buffer. The handover request 1116 and / or 1117 may include an indication that the handover request 1116 and / or 1117, respectively, is for NC purposes. In one aspect, the handover request 1116 and / or 1117 may include a bit to indicate that the handover request 1116 and / or 1117, respectively, is for NC purposes. For example, Figure 8A The transmission type field 810 of the NC handover request 800 in the UE 1104 may include such a bit. In one aspect, the handover request 1116 and / or 1117 may include an instruction to the encoder 1108 to send the SL NC TB 1126 to the UE 1104. For example, such an instruction may be included in Figure 8A In the additional handover request field set 812 of the NC handover request 800 in.

[0200] The handover request 1116 and / or 1117 may include a grant of SL resources in at least one of time or frequency to the encoder 1110 and / or encoder 1108, respectively. The network entity 1106 may provide the grant of SL resources in a separate transmission, such as Figure 9 1108. The SL resource grant 917 in FIG. The SL resource grant may be a time domain resource allocation (TDRA) and / or a frequency domain resource allocation (FDRA). The TDRA and / or FDRA may indicate which source the encoder 1110 may use to perform the NC including the handed-over SL TB 1122. The handover request 1116 and the handover request 1117 may be sent to each of the encoders 1110 and 1108 via unicast, respectively. If the handover request 1116 and the handover request 1117 are identical, the handover request may be sent to the encoders 1110 and 1108 via multicast. The handover request 1116 and the handover request 1117 may constitute a multicast or broadcast transmission. In other words, the handover requests may be combined in a single transmission.

[0201] At 1118, the encoder 1110 may process the handover. The encoder 1110 may send a confirmation message 1120 to the network entity 1106 in response to the handover request 1116, such as Figure 8B The encoder 1110 may also send a confirmation message 1121 to the encoder 1108 in response to the handover request 1116, which may contain the same or different elements as the confirmation message 1120. The confirmation message 1120 and / or the confirmation message 1121 may be sent to the network entity 1106 as a message such as an uplink transmission. The confirmation message 1120 and / or the confirmation message 1121 may be sent in an uplink control information (UCI) format. The confirmation message 1120 and / or the confirmation message 1121 may be sent in a custom format created for NC handover, such as Figure 8B Confirmation message 820 in. SL resources may be used to send confirmation message 1121. Although confirmation message 1121 and confirmation message 1121 are shown in connection flow diagram 1100 as being sent before UE 1102 sends SL TB 1122, confirmation message 1121 and confirmation message 1121 may be sent after encoder 1108 encodes the SL TB at 1124.

[0202] The confirmation message 1120 and / or the confirmation message 1121 may include at least one of the following: (a) an indication of acceptance of the NC handover request, (b) an indication of rejection of the NC handover request, (c) an indication of buffering of the SL NC TB, (d) an indication of unbuffered SL NC TB, (e) an indication of successful reception of the SL NC TB, or (f) an indication of failed reception of the SL NC TB. Such indications may be stored, for example, in Figure 8BThe encoder 1110 may be configured to respond to an NC handover request differently from other handover requests. The encoder 1110 may be configured to reject a handover request identified as NC in the handover request 1116 based on the number of UEs associated with the encoder 1110 meeting or exceeding a lower threshold number, and may be configured to reject a handover request identified as a different type of handover based on the number of UEs associated with the encoder 1110 meeting or exceeding a higher threshold number that is higher than the lower threshold number. The encoder 1110 may be configured to accept a handover request identified as NC in the handover request 1116 based on the number of UEs associated with the encoder 1110 meeting or falling below a lower threshold number, and may be configured to accept a handover request identified as a different type of handover based on the number of UEs associated with the encoder 1110 meeting or falling below a higher threshold number. In other words, encoder 1110 may have different threshold numbers associated with different types of handover requests.

[0203] If network entity 1106 receives a confirmation message 1120 indicating that encoder 1110 cannot perform NC handover (e.g., network entity 1106 receives an indication of a rejection of the NC handover request, an indication of no buffering of the SL NC TB, or an indication of failed reception of the SL NC TB), network entity 1106 may be configured to use a different encoder than encoder 1110. Network entity 1106 may then send a new handover request similar to handover request 1116 to the newly selected encoder. For example, network entity 1106 may send handover request 1138 to encoder 1140. Encoder 1140 may also be in the second region to which UE 1104 is traveling.

[0204] If the network entity 1106 receives a confirmation message 1120 indicating that the encoder 1110 can perform the NC handover, the network entity 1106 may be configured to output to the encoder 1110 a SL resource grant 1135 for transmitting the SL TB 1123 to the encoder 1108 if the SL resource grant was not included in the handover request 1116. The encoder 1110 may have a more powerful transmitter or transceiver than the UE 1102 and the UE 1104, thereby allowing the encoder 1110 to transmit the SL TB 1123 to wireless devices outside the second zone. The network entity 1106 may also output to the encoder 1108 a SL resource grant 1136 for transmitting the SL NC TB 1126 to the UE 1104.

[0205] At 1119, encoder 1108 may process handover request 1117 and / or confirmation message 1121. For example, encoder 1108 may resend SL TB 1122 to ensure encoder 1110 receives it. The resent SL TB 1122 may include an NC command for encoder 1110 to encode the TB. The resent SL TB 1122 may include at least a portion of handover request 1117, allowing encoder 1110 to receive both the TB and the handover request if encoder 1110 missed one or both. The handover request may include a bit indicating an NC handover. The handover request may include an encoder ID indicating that encoder 1110 should take over NC decoding. This saves signaling and allows the original encoder to attempt to send the TB again. If encoder 1110 did not have the TB in its buffer, encoder 1110 now has the TB.

[0206] Network entity 1106 may send a SL resource grant 1134 to UE 1102 for sending SL TB 1122. SL resource grant 1134 may enable UE 1102 to send SL TB 1122 to UE 1104 and encoder 1108 in a first zone. SL resource grant 1134 may enable UE 1102 to send SL TB 1122 to encoder 1110 in a second zone. UE 1102 may send SL TB 1122. UE 1104 may receive SL TB 1122, which may be within range of UE 1102, which is moving to a different zone. Encoder 1108 may receive SL TB 1122, which may be within range of UE 1102, which is moving to a different zone. Encoder 1110 may receive SL TB 1122, which may now be within range of UE 1102 if UE 1102 is moving toward the region of encoder 1110. If encoder 1110 receives SL TB 1122, encoder 1110 may send SL TB 1122 to encoder 1108 as SL TB 1123—essentially forwarding SL TB 1122 if encoder 1108 does not successfully receive SL TB 1122 from UE 1102. At 1124, in response to receiving SL TB 1122 and / or SL TB 1123, encoder 1108 may encode the received SL TB along with other TBs received by UEs in the region of encoder 1108 (e.g., SL TB 1122, SL TB 1123, or other SL TBs received in the first region). The encoder 1108 may send the SL NC TB 1126 to the UE 1104. The SL NC TB 1126 may be, for example Figure 8C SL NC TB 840 in.

[0207] Figure 12A Diagram 1200 illustrating a network having region 1216 with UEs 1202 , 1204 , and 1206 and encoder 1207 , and region 1226 with encoder 1227 at time t 0 is shown. Figure 12B Shown is an example Figure 12A FIG1240 is a diagram of a network in which UE 1204 moves from zone 1216 to zone 1226 at time t1. UEs 1202, 1204, and 1206 may be similar to 10A to 10C UE 1002, 1004 and 1006 in. Encoders 1207 and 1227 may be similar to 10A to 10C Encoders 1007 and 1027 in. Figure 12C The communication links between the network entity 1209 and the UEs 1202 , 1204 , 1206 and encoders 1207 and 1227 at time t1 are shown.

[0208] like Figure 12A As shown in diagram 1200 in FIG. 1 , UE 1202 may send a SL signal 1212 (eg, SL TB, such as SL TB Tx) to UE 1204 and encoder 1207. a ). UE 1206 may send a SL signal 1214 (eg, SL TB, such as SL TB Tx) to UE 1204 and encoder 1207. b ).like Figure 12A FIG1200 and FIG1201 Figure 12B As shown in FIG. 1240 , UE 1204 may Figure 12A Zone 1216 at time t0 moves to Figure 12B While UE 1202 is moving from zone 1216 to zone 1226, UE 1204 may send a SL signal 1212 (eg, SL TB, such as SLTB Tx) to UE 1204 and encoder 1207. a ), and UE 1206 may send a SL signal 1214 (eg, SL TB, such as SL TBTx) to UE 1204 and encoder 1207. b If UE 1204 stays in zone 1216 long enough so that UE 1204 can move to Figure 12B Tx successfully receives SL signal 1212 before zone 1226 at time t1 a , SL signal 1214 Tx b or f(Tx) of the SL signal 1217 (eg, SL NCTB) a ,Tx b) (i.e., it does not fail in decoding it), then the UE 1204 can successfully receive the Tx of the SL signal 1212 using the NC technology. a and SL signal 1214 Tx b For example, in one aspect, if UE 1204 does not receive SL signal 1217 at f(Tx a ,Tx b ) successfully receives the Tx of SL signal 1212 a and SL signal 1214 Tx b , then UE1204 has successfully received the Tx of SL signal 1212 a and SL signal 1214 Tx b On the other hand, if the UE 1204 does not receive the SL signal 1214 at Tx b Successfully received SL signal 1212 Tx a and SL signal 1217 f(Tx a ,Tx b ), UE 1204 can use Tx a Reverse f(Tx a ,Tx b ) function to derive Tx b On the other hand, if the UE 1204 does not receive the SL signal 1212 at Tx a Successfully received SL signal 1214 Tx b and SL signal 1217 f(Tx a ,Tx b ), UE 1204 can use Tx b Reverse f(Tx a ,Tx b ) function to derive Tx a .

[0209] However, if the UE 1204 successfully receives the Tx of the SL signal 1214 a , SL signal 1212 Tx b Or f(Tx of SL signal 1212 a ,Tx b ), the UE 1204 moves from the zone 1216 to the zone 1226 before at least two of the zones 1216 and 1226, then without additional coordination from the network entity 1209, the UE 1204 may not successfully receive the Tx signal of the SL signal 1214. a and SL signal 1217 Tx b For example, the UE 1204 may receive the Tx of the SL signal 1212 aPreviously, UE 1204 may move to zone 1226. On the other hand, UE 1204 may receive Tx of SL signal 1212. b Before, UE 1204 may move to region 1226. On the other hand, the encoder 1207 may send the SL signal 1217 to UE 1204. a ,Tx b ), UE 1204 may move to zone 1226.

[0210] Network entity 1209 may communicate with any of UE 1202, UE 1204, UE 1206, encoder 1207 and / or encoder 1227 to coordinate the successful transmission of SL signal 1212, SL signal 1214 and SL signal 1217 to UE 1204, even if UE 1204 moves from region 1216 to region 1226 before UE 1204 can successfully receive SL signal 1212, SL signal 1214 or SL signal 1217. Figure 12CDiagram 1280 is shown with a communication link 1281 between encoder 1207 and network entity 1209, a communication link 1282 between UE 1206 and network entity 1209, a communication link 1283 between UE 1202 and network entity 1209, a communication link 1284 between UE 1204 and network entity 1209, a communication link 1285 between encoder 1227 and network entity 1209, and a communication link 1286 between encoder 1207 and encoder 1227. Communication link 1281 may be a Uu communication link that implements DL signals 1219 from network entity 1209 to encoder 1207 and implements UL transmissions 1218 from encoder 1207 to network entity 1209. Communication link 1282 may be a Uu communication link that implements DL signals 1219 from network entity 1209 to UE 1206 and implements UL transmissions 1213 from UE 1206 to network entity 1209. Communication link 1283 may be a Uu communication link that implements DL signals 1219 from network entity 1209 to UE 1202 and implements UL transmissions 1215 from UE 1202 to network entity 1209. Communication link 1284 may be a Uu communication link that implements DL signals 1219 from network entity 1209 to UE 1204 and implements UL signals 1211 from UE 1204 to network entity 1209. Communication link 1285 may be a Uu communication link that implements DL signals 1219 from network entity 1209 to encoder 1227 and implements UL transmissions 1238 from encoder 1227 to network entity 1209. DL signal 1219 may be, for example, a SL resource grant or an NC handover request. UL signal 1211 from UE 1202 may be, for example, a request for SL resources or location information associated with UE 1202 (e.g., BSR, UE ID, current zone ID, GNSS location information, geographic location). UL transmission 1213 from UE 1206 may be, for example, a request for SL resources or location information associated with UE 1206. UL transmission 1215 from UE 1204 may be, for example, a request for SL resources or location information associated with UE 1204. UL transmission 1218 from encoder 1207 may be, for example, a request for SL resources, location information associated with UEs in zone 1216 (e.g., UEs 1202, 1204, and 1206 at time t0, UEs 1204 and 1206 at time t1), or a confirmation message associated with the NC handover request. The UL transmission 1238 from the encoder 1227 may be, for example, a request for SL resources, location information associated with a UE in the zone 1216 (eg, UE 1202 at time t1), or a confirmation message associated with the NC handover request.

[0211] Communication link 1286 may be an SL communication link that enables SL transmission from encoder 1207 to encoder 1227 and SL transmission from encoder 1227 to encoder 1207. In another aspect, communication link 1286 may be a backhaul or midhaul connection between encoder 1207 and encoder 1227. Encoder 1207 may use Figure 12C Communication link 1286 to broadcast, unicast or multicast Figure 12A The encoder 1227 (eg, SL TB or SL NC TB) may use one or more of the SL signals 1217 (eg, SL TB or SL NC TB) in the Figure 12C Communication link 1286 to broadcast, unicast or multicast Figure 12A The SL signal 1217 from the encoder 1207 may be, for example, an SL TB, an SL NC TB, or an acknowledgment message. The SL signal 1237 from the encoder 1227 may be, for example, an SL TB, an SL NC TB, or an acknowledgment message.

[0212] Network entity 1209 may send DL signal 1219 to any of UE 1202, UE 1204, UE 1206, encoder 1207, and / or encoder 1227 to coordinate the successful transmission of SL signal 1212, SL signal 1214, and DL signal 1219 to UE 1204, even if UE 1204 moves from region 1216 to region 1226 before UE 1204 can successfully receive SL signal 1212, SL signal 1214, or SL signal 1217. For example, at time t1, encoder 1207 may send f(Tx) of SL signal 1217 to encoder 1227. a ,Tx b ), then, the encoder 1227 may send f(Tx) of the SL signal 1217 to the UE 1204. a ,Tx b ) as f(Tx of SL signal 1237 a ,Tx b ). SL signal 1237 f(Tx a ,Tx b ) may include a complete vector of all linearly independent constants, thereby allowing the UE 1204 to reconstruct the Tx of the SL signal 1212 a and SL signal 1214 Tx b, even if UE 1204 fails to receive some of SL signals 1212, SL signals 1214, and SL signals 1217. Encoder 1207 may have a larger sidelink transmission range than UE 1202 or UE 1206, encoder 1227 may have a more sensitive antenna than UE 1204 or may be better equipped to handle interference, or encoder 1207 may be able to communicate with encoder 1227 via other means, such as a backhaul or midhaul link. Network entity 1209 may be configured to obtain information that UE 1204 is moving from zone 1216 to zone 1226 and initiate an NC handover from encoder 1207 to encoder 1227. Network entity 1209 may also be configured to allocate appropriate SL resources to each device, for example, allocating SL resources to encoder 1227 to allow encoder 1227 to transmit SL signal 1237 to UE 1204.

[0213] Figure 13 1300 illustrates an example of sidelink communication between UE 1302, UE 1304, encoder 1308, and encoder 1310 and a network entity 1306 coordinating NC between UE 1302, UE 1304, encoder 1308, and encoder 1310. UE 1302, UE 1304, network entity 1306, encoder 1308, and encoder 1310 may be similar to Figure 10A 13. UE 1002, UE 1004, network entity 1009, encoder 1007, and encoder 1027 in FIG. When UE 1304 moves from an area covered by encoder 1308 to an area covered by encoder 1310, network entity 1306 may coordinate NC between encoder 1308 and encoder 1310. Encoder 1308 and encoder 1310 may communicate with each other using PSCCH or PSFCH.

[0214] UE 1304 may provide location information 1312 to network entity 1306 via a first message, such as sent via an uplink. Location information 1312 may be associated with UE 1304. This may allow network entity 1306 to be aware of the movement of UE 1304. Location information 1312 may include, for example, a BSR. The BSR may include, for example, a UE identifier (ID), a new zone ID (e.g., Figure 10A The location information 1312 may be provided to the network entity 1306 in response to an event, such as movement from the UE's last reported location that meets or exceeds a threshold value (e.g., 20 meters).

[0215] The encoder 1308 may provide location information 1313 to the network entity 1306 via a message such as an uplink transmission. The location information 1313 may be associated with one or more UEs in SL communication with the encoder 1308. This may allow the network entity 1306 to be aware of the movement of any UE in SL communication with the encoder 1308. The location information 1313 may report the location of any UE affiliated with the encoder 1308 (e.g., communicating with the encoder 1308 within a threshold time period (e.g., 10 seconds)). The location information 1313 may include, for example, a region ID, a GNSS position, or a geographic location for each UE in the set of UEs affiliated with the encoder 1308. The region ID may be a lossy and / or compressed form of the GNSS position or geographic location of the UE. The location information 1313 may also include the location of the encoder 1308. The encoder 1308 may be configured to periodically provide location information 1313 to the network entity 1306, or may be configured to provide location information 1313 to the network entity 1306 in response to an event, such as movement of the UE or encoder 1308 from its last reported location that meets or exceeds a threshold value (e.g., 20 m). The location information 1313 may also include the number of UEs belonging to the encoder 1308 in its zone, which may be used by the network entity 1306 to determine whether the encoder 1308 should send an SL NC TB 1326 in addition to the SL NC TB 1332 sent by the encoder 1310 (e.g., if the zone is particularly congested).

[0216] At 1314, network entity 1306 may use at least a portion of one or both of location information 1312 and / or location information 1313 to determine movement of UE 1304 from a first region to a second region. In one aspect, network entity 1306 may process multiple received location information transmissions to create a map of mobile UEs (e.g., vehicles), which network entity 1306 may use to determine that a UE is moving from one region to another. At 1314, network entity 1306 may use such a map to determine that UE 1304 is moving from a region of encoder 1308 to a region of encoder 1310.

[0217] In response to determining that UE 1304 is moving from the region of encoder 1308 to the region of encoder 1310, network entity 1306 may initiate a handover request. Network entity 1306 may send a handover request 1316 to encoder 1310 (i.e., the destination encoder) as a downlink transmission. Network entity 1306 may send a handover request 1317 to encoder 1308 (i.e., the source encoder) as a downlink transmission. The handover request 1316 and the handover request 1317 may be the same or different. The handover request 1316 and / or 1317 may be in any suitable format, such as a DCI format or a MAC-CE format. The handover request 1317 and / or 1317 may be Figure 8A 8. The handover request 1316 and / or 1317 may include an indication of a destination encoder, such as encoder 1310. In one aspect, the handover request 1316 and / or 1317 may include a destination encoder field for the TB, such as the encoder ID of encoder 1310. The handover request 1316 and / or 1317 may include an indication of a source encoder, such as encoder 1308. In one aspect, the handover request 1316 and / or 1317 may include a source encoder field for the TB, such as the encoder ID of encoder 1308. The handover request 1316 and / or 1317 may include an indication for encoder 1308 to send a SL NC TB to encoder 1310. In one aspect, the handover request 1316 and / or 1317 may include a bit indicating that encoder 1308 should send a TB to encoder 1310 for NC purposes. For example, when this bit is set, handover request 1316 and / or 1317 may indicate that encoder 1308 should send SL NC TB 1326 to encoder 1310. Network entity 1306 may be configured to set this bit in response to encoder 1310 not having a TB in its buffer. Network entity 1306 may know what encoder 1310 has in its buffer based on previous communications with encoder 1310. Handover request 1316 and / or 1317 may include an indication that handover request 1316 and / or 1317, respectively, is for NC purposes. In one aspect, handover request 1316 and / or 1317 may include a bit to indicate that handover request 1316 and / or 1317, respectively, is for NC purposes. Handover request 1316 and / or 1317 may include an indication for encoder 1308 to send SL NC TB to the UE. In one aspect, the handover request 1316 and / or 1317 may include instructions for the encoder 1308 to send the SL NC TB 1326 to the UE 1304 .

[0218] Handover requests 1316 and / or 1317 may include grants of SL resources in at least one of time or frequency to encoder 1310 and / or encoder 1308, respectively. Network entity 1306 may provide the grants of SL resources in separate transmissions. The grants of SL resources may be TDRAs and / or FDRAs. The TDRAs and / or FDRAs may indicate which source encoder 1310 may use to perform the NC containing the handed-over SL TB 1322. Handover requests 1316 and 1317 may be sent to encoders 1310 and 1308, respectively, via unicast. If handover requests 1316 and 1317 are identical, the handover requests may be sent to encoders 1310 and 1308 via multicast. Handover requests 1316 and 1317 may constitute a multicast or broadcast transmission. In other words, the handover requests may be combined in a single transmission.

[0219] At 1318, encoder 1310 may process the handover. Encoder 1310 may send a handover confirmation 1320 to network entity 1306 in response to handover request 1316. Encoder 1310 may also send a handover confirmation 1321 to encoder 1308 in response to handover request 1316, which may contain the same or different elements as handover confirmation 1320. Handover confirmation 1320 and / or handover confirmation 1321 may be Figure 8B 1322. The handover confirmation 1320 and / or the handover confirmation 1321 may be sent to the network entity 1306 as a message such as an uplink transmission. The handover confirmation 1320 and / or the handover confirmation 1321 may be sent in an uplink control information (UCI) format or a new format. The handover confirmation 1321 may be sent using SL resources. Although the handover confirmation 1321 and the handover confirmation 1321 are shown in the connection flow diagram 1300 as being sent before the UE 1302 sends the SL TB 1322, the handover confirmation 1321 and the handover confirmation 1321 may be sent after the encoder 1308 encodes the SL TB at 1324.

[0220] Handover confirmation 1320 and / or handover confirmation 1321 may include at least one of: (a) an indication of acceptance of the NC handover request, (b) an indication of rejection of the NC handover request, (c) an indication of buffering of the SL NC TB, (d) an indication of unbuffered SL NC TB, (e) an indication of successful reception of the SL NC TB, or (f) an indication of failed reception of the SL NC TB. Encoder 1310 may be configured to respond differently to the NC handover request than to other handover requests. Encoder 1310 may be configured to reject a handover request identified as NC in handover request 1316 based on the number of UEs associated with encoder 1310 meeting or exceeding a lower threshold number, and may be configured to reject a handover request identified as a different type of handover based on the number of UEs associated with encoder 1310 meeting or exceeding a higher threshold number than the lower threshold number.

[0221] If network entity 1306 receives handover confirmation 1320 indicating that encoder 1310 cannot perform NC handover (e.g., network entity 1306 receives an indication of a rejection of an NC handover request, an indication of no buffering of an SL NC TB, or an indication of failed reception of an SL NC TB), network entity 1306 may be configured to use a different encoder than encoder 1310. Network entity 1306 may then send a new handover request similar to handover request 1316 to the newly selected encoder. For example, network entity 1306 may send handover request 1338 to encoder 1340. Encoder 1340 may also be in the second zone to which UE 1304 is traveling.

[0222] If the network entity 1306 receives the handover confirmation 1320 indicating that the encoder 1310 can perform the NC handover, the network entity 1306 can be configured to output a SL resource grant 1335 to the encoder 1310 for sending the SL NC TB if the SL resource grant was not included in the handover request 1316. The network entity 1306 can also output a SL resource grant 1336 to the encoder 1308 for sending the SL NC TB 1326 to the encoder 1310. The encoder 1308 can have a more powerful transmitter or transceiver than the UE 1302 and the UE 1304, thereby allowing the encoder 1308 to send the SL NC TB 1326 to wireless devices outside the first zone.

[0223] At 1319, encoder 1308 may process handover request 1317 and / or handover confirmation 1321. In one aspect, encoder 1308 may receive an indication of buffering of SL NC TB 1332, or may receive an indication of successful receipt of SL NC TB 1332. In response, encoder 1308 may remove the TB from its buffer. In another aspect, encoder 1308 may resend SL NC TB 1326 as SL NC TB 1330 to ensure that encoder 1310 receives it. Encoder 1308 may send SL TB 1322 to encoder 1310 as SL TB 1323, along with an indication of the NC command for encoder 1310 to encode the TB. The retransmission of the SL NC TB 1326 may include at least a portion of the handover request 1317, allowing encoder 1310 to receive both the NC TB and the handover request if encoder 1310 missed one or both. The handover request may include a bit indicating an NC handover. The handover request may include an encoder ID indicating that encoder 1310 should take over NC decoding. This saves signaling and allows the original encoder to try sending the TB again. If encoder 1310 did not have the TB in its buffer, encoder 1310 now has the TB.

[0224] Network entity 1306 may send a SL resource grant 1334 to UE 1302 for transmitting SL TB 1322. SL resource grant 1334 may enable UE 1302 to transmit SL TB 1322 to UE 1304 and encoder 1308 in the first zone. UE 1302 may transmit SL TB 1322. UE 1304 may receive SL TB 1322, which may be within range of UE 1302 when it moves to a different zone. Encoder 1308 may receive SL TB 1322. Encoder 1308 may forward SL TB 1322 along with any other TBs received by encoder 1308 to allow encoder 1310 to encode its own NC TB. If encoder 1310 receives SL TB 1323, then at 1325, encoder 1310 may encode SL TB 1322 instead of encoder 1308. At 1324, in response to receiving SL TB 1322 and / or SL TB 1323, encoder 1308 may encode the received SLTB along with other TBs received by UEs in the zone of encoder 1308. SL NC TB 1326, SL NC TB 1330, or SL NC TB 1332 may be Figure 8C The format of SL NC TB 840.

[0225] Encoder 1308 may send SL NC TB 1326 to UE 1304. However, when UE 1304 moves from one zone to another, UE 1304 may not receive SL NC TB 1326. Encoder 1308 may send SL NC TB 1326 to encoder 1310. The encoder may then buffer the TB for transmission to UE 1304 when UE 1304 moves into the encoder's zone.

[0226] Encoder 1310 may not have a TB in its buffer. This may occur if encoder 1308 sends SL NC TB 1326 before the encoder processes the handover at 1318. If encoder 1310 does not have a TB in its buffer, encoder 1310 may send an SL request 1328 to encoder 1308 to resend SL NC TB 1326. In response to SL request 1328, encoder 1308 may resend SL NC TB 1326 to encoder 1310 as SL NC TB 1330. When UE 1304 is moving into the zone of encoder 1310, encoder 1310 may send SL NC TB 1332 to UE 1304. In one aspect, the encoder 1310 may wait for a time delay before sending the SL NC TB 1332 based on the predicted speed of the UE 1304 to ensure that the UE 1304 is in the zone before the encoder 1310 sends the SL NC TB 1332 .

[0227] The transmission of the SL NC TB 1326 from the encoder 1308 and the transmission of the SL NC TB 1332 from the encoder 1310 may be position-based, distance-based, and / or reference signal received power (RSRP)-based. For example, while the UE 1304 is moving from the region of the encoder 1308 to the region of the encoder 1310, the encoder 1308 may use a distance or timing threshold to determine when to start or stop transmitting the SL NC TB 1326 to the UE 1304. In one aspect, if the encoder 1308 determines that the UE 1304 is within a threshold distance from the encoder 1308, the encoder may transmit the SL NC TB 1326 until the encoder 1308 determines that the position of the UE 1304 meets or exceeds the threshold distance from the encoder 1308. In another aspect, the encoder 1308 may be configured to send the SL NC TB 1326 at a first time (or after a threshold time period has elapsed) and may be configured to stop sending the SL NC TB 1326 at a second time (or after a threshold time period has elapsed). In another aspect, if the encoder 1308 determines that the UE 1304 has an RSRP value that meets or exceeds a threshold, the encoder may send the SL NC TB 1326 until the encoder 1308 determines that the UE 1304 has an RSRP value that meets or is less than the threshold. Such a value may be calculated by the encoder 1308 or provided by the network entity 1306.

[0228] Similarly, in one aspect, while the UE 1304 is moving from the region of the encoder 1308 to the region of the encoder 1310, the encoder 1308 may use a distance or timing threshold to determine when to begin sending the SL NC TB 1332 to the UE 1304. In one aspect, if the encoder 1310 determines that the distance of the UE 1304 from the encoder 1308 meets or exceeds the threshold distance, the encoder 1310 may begin sending the SL NC TB 1332 to the UE 1304. In another aspect, if the encoder 1310 determines that the distance of the UE 1304 from the encoder 1310 meets or is less than the threshold distance, the encoder 1310 may begin sending the SL NC TB 1332 to the UE 1304. In another aspect, the encoder 1310 may be configured to send the SL NC TB 1332 at a specified time (or after a threshold time period has elapsed). On the other hand, if the encoder 1310 determines that the UE 1304 has an RSRP value that meets or exceeds a threshold, the encoder 1310 may send a SL NC TB 1332 to the UE 1304. Such a value may be calculated by the encoder 1308 or provided by the network entity 1306.

[0229] Figure 141400 is a flow chart of a method for wireless communication at a first device. The first device may be a UE (e.g., UE 104, 350, 502, 504, 506, 508, 602, 604, 606, 608, 702, 704, 706, 708, 902, 904, 1002, 1004, 1006, 1102, 1104, 1202, 1204, 1206, 1302, 1304, apparatus 2204). The first device may be an encoder (e.g., encoder 152, 507, 707, 908, 1007, 1027, 1108, 1110, 1207, 1227, 1108, 1110). At 1402, the first device may communicate a SL TB for an NC with a second device. At least one of the first device or the second device may include a UE. For example, 1402 can be Figure 11 1402 may be performed by UE 1102 that sends SL TB 1122 to UE 1104, to encoder 1108, and to encoder 1110. UE 1102 may be a UE. Figure 11 The encoder 1108 of the embodiment of the present invention is executed by transmitting the SL NC TB 1126 to the UE 1104. The UE 1104 may be a UE. 1402 may also be Figure 22 1402 may also be performed by component 198 of means 2204 in Figure 24 Component 197 of encoder 2450 is executed.

[0230] At 1404, the first device may send a first message to a network entity, the first message including first location information indicating movement of the UE from the first zone to the second zone. For example, 1404 may be performed by Figure 11 1404 may also be performed by encoder 1108 sending location information 1113 to network entity 1106. Location information 1113 may indicate movement of UE 1102 from the first area to the second area. Figure 22 1404 may also be performed by component 198 of means 2204 in Figure 24 Component 197 of encoder 2450 is executed.

[0231] Figure 151500 is a flow chart of a method for wireless communication at a first device. The first device may be a UE (e.g., UE 104, 350, 502, 504, 506, 508, 602, 604, 606, 608, 702, 704, 706, 708, 902, 904, 1002, 1004, 1006, 1102, 1104, 1202, 1204, 1206, 1302, 1304, apparatus 2204). The first device may be an encoder (e.g., encoder 152, 507, 707, 908, 1007, 1027, 1108, 1110, 1207, 1227, 1108, 1110). At 1502, the first device may communicate a SL TB for an NC with a second device. At least one of the first device or the second device may include a UE. For example, 1502 can be Figure 11 1502 may be executed by UE 1102 that sends SL TB 1122 to UE 1104, to encoder 1108, and to encoder 1110. UE 1102 may be a UE. Figure 11 The encoder 1108 of the embodiment of the present invention is executed by transmitting the SL NC TB 1126 to the UE 1104. The UE 1104 may be a UE. 1502 may also be performed by Figure 22 1502 may also be performed by component 198 of means 2204 in Figure 24 Component 197 of encoder 2450 is executed.

[0232] At 1504, the first device may send a first message to a network entity, the first message including first location information indicating movement of the UE from the first zone to the second zone. For example, 1504 may be performed by Figure 11 1504 may also be performed by encoder 1108 sending location information 1113 to network entity 1106. Location information 1113 may indicate movement of UE 1102 from the first zone to the second zone. Figure 22 1504 may also be performed by component 198 of means 2204 in Figure 24 Component 197 of encoder 2450 is executed.

[0233] At 1506, the first device may communicate at least one SL TB with each UE in the set of UEs. The set of UEs may include UEs. The first device may include a first encoder that encodes the TB. The second device may include a UE. For example, 1506 may be performed by an encoder 1108 that may communicate with each UE in the set of UEs, such as UE 1102 and UE 1104. Encoder 1108 may receive SL TB 1122 from UE 1102. Encoder 1108 may send SL NC TB to UE 1104. The set of UEs may include UE 1104. The first device may include encoder 1108. The second device may include UE 1104. 1506 may also be performed by Figure 24 Component 197 of encoder 2450 is executed.

[0234] At 1508, the first device may send location information associated with each UE in the set of UEs to the network entity. For example, 1508 may be performed by encoder 1108 that sends location information 1113 to network entity 1106. Location information 1113 may include location information associated with each of UE 1102 and UE 1104 in the set of UEs. 1508 may also be performed by Figure 24 Component 197 of encoder 2450 is executed.

[0235] At 1510, the first device may receive an NC handover request from a network entity. The first device may include a first encoder that encodes a TB, and the second device may include a UE. For example, 1510 may be performed by encoder 1108 that may receive a handover request 1117 from network entity 1106. The first device may include encoder 1108. The second device may include UE 1102. 1510 may also be performed by Figure 24 Component 197 of encoder 2450 is executed.

[0236] At 1512, the first device may send the SL TB to the second encoder of the second zone based on the NC handover request. For example, 1512 may be performed by encoder 1108 sending the SL TB 1122 to encoder 1110 based on the handover request 1117. 1512 may also be performed by Figure 24 Component 197 of encoder 2450 is executed.

[0237] Figure 161600 is a flow chart of a method for wireless communication at a network entity. The method may be performed by a network entity (e.g., base station 102, 310; network entity 509, 609, 709, 906, 1009, 1106, 1209, 1306, 2202, 2302). At 1602, the network entity may obtain a first message from a first device, the first message including first location information associated with a UE, the UE performing SL communication with a first encoder associated with a first region. For example, 1602 may be performed by Figure 11 The network entity 1106 may obtain the first message as location information 1112 from the UE 1102. The location information 1112 may include the location of the UE 1102 that is in SL communication with the encoder 1108 in the first zone. Figure 11 The network entity 1106 may obtain the first message as location information 1113 from the encoder 1108. The location information 1113 may include the location of the UE 1102 that is in SL communication with the encoder 1108 in the first zone. Figure 23 Component 199 in is executed.

[0238] At 1604, the network entity may initiate NC handover of the UE to the second encoder in the second zone in response to the first location information indicating movement of the UE from the first zone to the second zone. For example, 1604 may be initiated by Figure 11 The network entity 1106 may initiate NC handover of the UE 1102 from the encoder 1108 in the first zone to the encoder 1110 in the second zone in response to the location information 1112 and / or the location information 1113 indicating that the UE 1102 moves from the first zone to the second zone. 1604 may also be performed by Figure 23 Component 199 in is executed.

[0239] Figure 17 1700 is a flow chart of a method for wireless communication at a network entity. The method may be performed by a network entity (e.g., base station 102, 310; network entity 509, 609, 709, 906, 1009, 1106, 1209, 1306, 2202, 2302). At 1702, the network entity may obtain a first message from a first device, the first message including first location information associated with a UE, the UE performing SL communication with a first encoder associated with a first region. For example, 1702 may be performed by Figure 11 The network entity 1106 may obtain the first message as location information 1112 from the UE 1102. The location information 1112 may include the location of the UE 1102 that is in SL communication with the encoder 1108 in the first zone. Figure 11The network entity 1106 may obtain the first message as location information 1113 from the encoder 1108. The location information 1113 may include the location of the UE 1102 that is in SL communication with the encoder 1108 in the first zone. Figure 23 Component 199 in is executed.

[0240] At 1704, the network entity may initiate NC handover of the UE to the second encoder in the second zone in response to the first location information indicating movement of the UE from the first zone to the second zone. For example, 1704 may be initiated by Figure 11 The network entity 1106 may initiate NC handover of the UE 1102 from the encoder 1108 in the first zone to the encoder 1110 in the second zone in response to the location information 1112 and / or the location information 1113 indicating that the UE 1102 moves from the first zone to the second zone. 1704 may also be performed by Figure 23 Component 199 in is executed.

[0241] At 1706, the network entity may obtain a second message from the first encoder, the second message including location information associated with each UE in the set of UEs in SL communication with the first encoder. The set of UEs may include UEs. The first device may include the first encoder. For example, 1706 may be performed by Figure 11 The network entity 1106 in the embodiment may obtain the location information 1113 from the encoder 1108. The location information 1113 may be associated with each UE in the set of UEs that are in SL communication with the encoder 1108. The set of UEs may include UE 1102 and UE 1104. 1706 may also be performed by Figure 23 Component 199 in is executed.

[0242] At 1708, the network entity may obtain second location information associated with the first encoder from the first encoder. The first location information and the second location information associated with the first encoder may indicate movement of the UE from the first area to the second area. The first device may include the first encoder. For example, 1708 may be performed by Figure 11 The network entity 1106 in the embodiment may obtain the location information 1113 associated with the encoder 1108 from the encoder 1108. The location information 1113 may be used together with the previously transmitted location information 1113 (because the location information 1113 may be transmitted periodically), or together with the location information 1112 from the UE 1102 that may indicate the movement of the UE 1102 from the first area to the second area. 1708 may also be performed by Figure 23 Component 199 in is executed.

[0243] Figure 181800 is a flow chart of a method for wireless communication at a second encoder. The method may be performed by a second encoder (e.g., encoders 152, 507, 707, 908, 1027, 1310, 1227, 1310). At 1802, the second encoder may receive an NC handover request from a network entity. For example, Figure 13 The encoder 1310 in the embodiment may receive a handover request 1316 from the network entity 1306. The handover request 1316 may be a downlink transmission. Figure 5 Component 197 in is executed.

[0244] At 1804, the destination encoder may send a SL NC TB to the UE based on the NC handover request. For example, 1804 may be performed by Figure 13 The encoder 1310 may be executed by transmitting the SL NC TB 1332 to the UE 1304 based on the handover request 1316. Figure 5 Component 197 in is executed.

[0245] Figure 19 1900 is a flow chart of a method for wireless communication at a second encoder. The method may be performed by a second encoder (e.g., encoders 152, 507, 707, 908, 1027, 1310, 1227, 1310). At 1902, the second encoder may receive an NC handover request from a network entity. For example, Figure 13 The encoder 1310 in the embodiment may receive a handover request 1316 from the network entity 1306. The handover request 1316 may be a downlink transmission. Figure 5 Component 197 in is executed.

[0246] At 1904, the second encoder may send a SL NC TB to the UE based on the NC handover request. For example, 1904 may be performed by Figure 13 The encoder 1310 may be executed by transmitting the SL NC TB 1332 to the UE 1304 based on the handover request 1316. Figure 5 Component 197 in is executed.

[0247] At 1906, the second encoder may send an indication of acceptance of the NC handover request to the network entity. For example, 1906 may be performed by Figure 13 The encoder 1310 may send an indication of acceptance of the handover request 1316 to the network entity 1306 as a handover confirmation 1320. 1906 may also be performed by Figure 5 Component 197 in is executed.

[0248] At 1908, the second encoder may receive a grant for SL resources in at least one of time or frequency from a network entity. For example, 1908 may be performed by Figure 13 The encoder 1310 may receive a grant of SL resources in at least one of time or frequency from the network entity 1306 in the handover request 1316. 1908 may also be performed by Figure 5 Component 197 in is executed.

[0249] At 1910, the second encoder may use the SL resources to send the SL NC TB to the UE. For example, 1910 may be Figure 13 The encoder 1310 in the handover request 1316 may use the SL resources provided by the grant to send the SL NC TB 1332 to the UE 1304. 1910 may also be performed by Figure 5 Component 197 in is executed.

[0250] At 1912, the second encoder may send a request for SL NC TB to the first encoder as a response to the request. Figure 13 The encoder 1310 may send a request for SL NC TB to the encoder 1308 as an SL request 1328. The SL request 1328 may be a transmission of the handover request 1316. 1912 may also be performed by Figure 5 Component 197 in is executed.

[0251] At 1914, the second encoder may receive the SL NC TB from the first encoder in response to the sending of the request. For example, 1914 may be performed by Figure 13 The encoder 1310 may receive the SL NC TB 1330 from the encoder 1308 in response to sending the SL request 1328. 1914 may also be performed by Figure 5 Component 197 in is executed.

[0252] At 1916, the second encoder may receive the SL NC TB from the first encoder. For example, 1916 may be performed by Figure 13 The encoder 1310 may receive the SL NC TB 1326 from the encoder 1308. 1916 may also be performed by Figure 5 Component 197 in is executed.

[0253] At 1918, the second encoder may send a confirmation message to the network entity based on the NC handover request. For example, 1918 may be performed by Figure 13 The encoder 1310 may be executed by sending a handover confirmation 1321 to the network entity 1306 based on the handover request 1316. 1918 may also be performed by Figure 5 Component 197 in is executed.

[0254] At 1920, the second encoder may send a second confirmation message to the first encoder based on the NC handover request. The second confirmation message may include a PSCCH message or a PSFCH message. For example, 1920 may be Figure 13 The encoder 1310 may send a handover confirmation 1321 to the encoder 1308 based on the handover request 1316. The handover confirmation 1321 may include a PSCCH message or a PSFCH message. Figure 5 Component 197 in is executed.

[0255] Figure 20 2000 is a flow chart of a method for wireless communication at a network entity. The method may be performed by a network entity (e.g., base station 102, 310; network entity 509, 609, 709, 906, 1009, 1106, 1209, 1306, 2202, 2302). At 2002, the network entity may output a first NC handover request to a second encoder for communicating a SL TB between the second encoder and the UE. For example, 2002 may be performed by Figure 13 The network entity 1306 that can output the handover request 1316 for conveying the SL TB to the encoder 1310 and the UE 1304 is executed. Figure 23 Component 199 in is executed.

[0256] At 2004, the network entity may output a first grant for sending a SL NC TB using a first SL resource to a second encoder, or output a second grant for sending a SL TB using a second SL resource to a UE. Figure 13 The network entity 1306 may output a first grant for sending the SL NC TB 1332 using the first SL resource to the encoder 1310 in the handover request 1316. On the other hand, the network entity 1106 may send a second grant for sending the SL TB 1122 using the second SL resource to the UE 1102. Figure 23 Component 199 in is executed.

[0257] Figure 21 2100 is a flow chart of a method for wireless communication at a network entity. The method may be performed by a network entity (e.g., base station 102, 310; network entity 509, 609, 709, 906, 1009, 1106, 1209, 1306, 2202, 2302). At 2102, the network entity may output a first NC handover request to a second encoder for communicating a SL TB between the second encoder and the UE. For example, 2102 may be performed by Figure 13The network entity 1306 outputs a handover request 1316 for communicating the SL TB to the encoder 1310 and the UE 1304. 2102 may also be performed by Figure 23 Component 199 in is executed.

[0258] At 2104, the network entity may output a first grant for sending the SL NC TB using the first SL resource to the second encoder, or output a second grant for sending the SL TB using the second SL resource to the UE. For example, 2104 may be performed by Figure 13 The network entity 1306 may output a first grant for sending the SL NC TB 1332 using the first SL resource to the encoder 1310 in the handover request 1316. On the other hand, the network entity 1106 may send a second grant for sending the SL TB 1122 using the second SL resource to the UE 1102. 2104 may also be performed by Figure 23 Component 199 in is executed.

[0259] At 2106, the network entity may obtain an indication of acceptance of the first NC handover request from the second encoder or the UE. For example, 2106 may be performed by Figure 13 The network entity 1306 may obtain an indication of acceptance of the handover request 1316 from the encoder 1310 as a handover confirmation 1320. 2106 may also be performed by Figure 23 Component 199 in is executed.

[0260] At 2108, the network entity may output a first grant based on an indication of acceptance of the first NC handover request. For example, 2108 may be performed by Figure 13 The network entity 1306 may output the SL resource grant 1335 to the encoder 1310 based on the indication of the acceptance of the handover request 1316. 2108 may also be performed by Figure 23 Component 199 in is executed.

[0261] At 2110, the network entity may output a second NC handover request to the first encoder for sending SL NC TB to the first encoder. For example, 2110 may be performed by Figure 13 The network entity 1306 may output to the encoder 1308 the handover request 1317 for the encoder 1310 to send the SLNC TB 1326 to the encoder 1308. 2110 may also be performed by Figure 23 Component 199 in is executed.

[0262] At 2112, the network entity may output a third grant to the first encoder for sending the SL NC TB using the third SL resource. For example, 2112 may be performed by Figure 13The network entity 1306 may output to the encoder 1308 a grant for using SL resources to send SL NC TB to the encoder 1310. 2112 may also be performed by Figure 23 Component 199 in is executed.

[0263] At 2114, the network entity may obtain an acknowledgment message from the second encoder. For example, 2114 may be performed by Figure 13 The network entity 1306 that can obtain the handover confirmation 1320 from the encoder 1310 can also perform 2114 Figure 23 Component 199 in is executed.

[0264] At 2116, the network entity may output a second NC handover request to the second encoder based on at least one of the first indications of the rejection of the first NC handover request. Figure 13 The network entity 1306 may output the handover request 1316 to the encoder 1340 based on the indication of the rejection of the handover request 1338. 2116 may also be performed by Figure 23 Component 199 in is executed.

[0265] Figure 21 2100 is a flow chart of a method for performing wireless communication. The method may be performed by a base station (e.g., base station 102, 310; network entity 509, 609, 709, 906, 1009, 1106, 1209, 1306, 2202, 2302). At 2102, the network entity may output a first NC handover request to a second encoder for communicating a SL TB with a UE. For example, Figure 13 The network entity 1306 in the embodiment may output to the encoder 1310 a handover request 1316 for the encoder 1310 to send the SL NC TB 1326, 1330 or 1332 for NC to the UE 1304 or to receive these SL NC TBs from the UE. The handover request 1316 may be a downlink transmission. Figure 23 Component 199 in is executed.

[0266] At 2104, the network entity may output a first grant for sending the SL NC TB using the first SL resource to the second encoder, or output a second grant for sending the SL TB using the second SL resource to the UE. For example, 2104 may be performed by Figure 13 The network entity 1306 may output a first grant for using SL resources to send SL NC TB 1332 to the encoder 1310 in the handover request 1316. 2104 may also be performed by Figure 13The network entity 1306 may output to the UE 1302 a grant for sending the SL TB 1322 to the encoder 1310. 2104 may also be performed by Figure 23 Component 199 in is executed.

[0267] Figure 2222 is a diagram illustrating an example of a hardware implementation for an apparatus 2204. The apparatus 2204 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 2204 may include a cellular baseband processor 2224 (also referred to as a modem) coupled to one or more transceivers 2222 (e.g., a cellular RF transceiver). The cellular baseband processor 2224 may include on-chip memory 2224'. In some aspects, the apparatus 2204 may also include one or more subscriber identity module (SIM) cards 2220, and an application processor 2206 coupled to a secure digital (SD) card 2208 and a screen 2210. The application processor 2206 may include on-chip memory 2206'. In some aspects, the device 2204 may further include a Bluetooth module 2212, a WLAN module 2214, an SPS module 2216 (e.g., a GNSS module), one or more sensor modules 2218 (e.g., a barometric 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 2226, a power source 2230, and / or a camera 2232. The Bluetooth module 2212, the WLAN module 2214, and the SPS module 2216 may include an on-chip transceiver (TRX) (or, in some cases, only a receiver (RX)). The Bluetooth module 2212, the WLAN module 2214, and the SPS module 2216 may include their own dedicated antennas and / or utilize an antenna 2280 for communication. The cellular baseband processor 2224 communicates with the UE 104 and / or RUs associated with the network entity 2202 via the transceiver 2222 via one or more antennas 2280. The cellular baseband processor 2224 and the application processor 2206 may each include computer-readable media / memory 2224', 2206', respectively. The additional memory module 2226 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 2224', 2206', 2226 may be non-transitory. The cellular baseband processor 2224 and the application processor 2206 are each responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the cellular baseband processor 2224 / application processor 2206, this software enables the cellular baseband processor 2224 / application processor 2206 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 2224 / application processor 2206 when executing the software.The cellular baseband processor 2224 / application processor 2206 may be a component of the UE 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 2204 may be a processor chip (modem and / or application) and include only the cellular baseband processor 2224 and / or the application processor 2206, while in another configuration, the device 2204 may be the entire UE (e.g., see ). Figure 3 UE 350) and includes additional modules of device 2204.

[0268] As discussed above, component 198 is configured to communicate the SL TB with the second device for NC. At least one of the first device or the second device may include a UE. Communicating the SL TB with the device may include sending the SL TB to the device, or receiving the SL TB from the device. Component 198 may be configured to send a first message to a network entity, the first message including first location information indicating movement of the UE from a first area to a second area. Component 198 may be within the cellular baseband processor 2224, the application processor 2206, or within both the cellular baseband processor 2224 and the application processor 2206. Component 198 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, apparatus 2204 may include a variety of components configured for various functions. In one configuration, the apparatus 2204 (specifically, the cellular baseband processor 2224 and / or the application processor 2206) includes: a component for sending a SL TB for NC to a second device or receiving a SL TB for NC from the second device, respectively, wherein at least one of the first device and the second device includes a UE; a component for sending a first message to a network entity, the first message including a location indicating movement of the UE from a first transmission zone to a second transmission zone; a component for communicating the SL TB for NC with the second device; a component for sending a first message to the network entity, the first message including first location information indicating movement of the UE from the first zone to the second zone; a component for communicating at least one SL TB with each UE in a set of UEs; a component for sending location information associated with each UE in the set of UEs to the network entity; a component for sending a second location associated with the first encoder to the network entity; a component for receiving an NC handover request from the network entity; a component for sending a SL TB to a second encoder in the second zone based on the NC handover request; and a component for communicating the SL TB for NC with the second device. At least one of the first device or the second device may include: a UE; a component for sending a first message to a network entity, the first message including first location information indicating movement of the UE from a first zone to a second zone; a component for communicating an SL TB for NC by communicating at least one SL TB with each UE in a set of UEs; a component for sending a first message including first location information by sending location information associated with each UE in the set of UEs to the network entity; a component for sending second location information associated with a first encoder to the network entity; a component for receiving an NC handover request from the network entity; or a component for sending an SL TB to a second encoder in the second zone based on the NC handover request. The component may be component 198 of apparatus 2204 configured to perform the functions recited by the component.As described above, the device 2204 may include the Tx processor 368, the Rx processor 356, and the controller / processor 359. Thus, in one configuration, the components may be the Tx processor 368, the Rx processor 356, and the controller / processor 359 configured to perform the functions recited by the components.

[0269] Figure 23 Diagram 2300 illustrates an example hardware implementation for a network entity 2302. Network entity 2302 may be a base station (BS), a component of a BS, or may implement BS functionality. Network entity 2302 may include at least one of a CU 2310, a DU 2330, or a RU 2340. For example, depending on the layer functionality handled by component 199, network entity 2302 may include a CU 2310; both the CU 2310 and the DU 2330; each of the CU 2310, the DU 2330, and the RU 2340; the DU 2330; both the DU 2330 and the RU 2340; or the RU 2340. CU 2310 may include a CU processor 2312. CU processor 2312 may include on-chip memory 2312′. In some aspects, CU 2310 may also include an additional memory module 2314 and a communication interface 2318. The CU 2310 communicates with the DU 2330 via a midhaul link, such as an F1 interface. The DU 2330 may include a DU processor 2332. The DU processor 2332 may include on-chip memory 2332′. In some aspects, the DU 2330 may also include an additional memory module 2334 and a communication interface 2338. The DU 2330 communicates with the RU 2340 via a fronthaul link. The RU 2340 may include a RU processor 2342. The RU processor 2342 may include on-chip memory 2342′. In some aspects, the RU 2340 may also include an additional memory module 2344, one or more transceivers 2346, an antenna 2380, and a communication interface 2348. The RU 2340 communicates with the UE 104. The on-chip memories 2312′, 2332′, 2342′ and the additional memory modules 2314, 2334, 2344 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of processors 2312, 2332, and 2342 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software 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.

[0270] As discussed above, component 199 is configured to obtain a first message from a first device, the first message including first location information associated with a UE, the UE engaging in SL communication with a first encoder associated with a first zone. Component 199 may be configured to initiate NC handover of the UE to a second encoder in the second zone in response to the first location information indicating movement of the UE from the first zone to the second zone. Component 199 may be configured to output a first NC handover request to the second encoder for communicating a SL TB with the UE. Component 199 may be configured to output a first grant to the second encoder for transmitting a SL NCTB using first SL resources, or to the UE for transmitting a SL TB using second SL resources. Component 199 may be within one or more processors of one or more of CU 2310, DU 2330, and RU 2340. Component 199 may be one or more hardware components specifically configured to perform the described processes / algorithms, implemented by one or more processors configured to perform the described processes / algorithms, stored on a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 2302 may include various components configured for various functions. In one configuration, the network entity 2302 includes means for obtaining a first message from a first device, the first message including a location of a UE in SL communication with a first encoder in a first transmission zone; means for initializing an NC handover of the UE to a second encoder in a second transmission zone in response to the location indicating movement of the UE from the first transmission zone to the second transmission zone; means for obtaining a location set from the first encoder, the location set including location information of each UE in a set of UEs in SL communication with the first encoder, wherein the set of UEs includes the UE; means for obtaining location information of the first encoder from the first encoder, wherein the location of the first encoder and the first message indicate movement of the UE from the first transmission zone to the second transmission zone; means for outputting, to a destination encoder, a first NC handover request for the destination encoder to send an SL TB for NC to the UE or to receive an SL TB for NC from the UE, respectively; means for outputting, to one of the destination encoder or the UE, a first grant for sending an SL NC TB using SL resources; means for outputting, to a source encoder, a second NC handover request for the source encoder to send an SL NC TB; and means for outputting, to the source encoder, a second NC handover request for sending an SL NC TB using second SL resources. means for obtaining an indication of an acceptance of the first NC handover request from a destination encoder or a UE, wherein outputting the grant for sending the SL NC TB using SL resources is in response to obtaining the indication of the acceptance of the first NC handover request; means for obtaining an acknowledgment message from the destination encoder;a means for outputting, to a second destination encoder, a second NC handover request for the second destination encoder to send an SL TB for NC to a UE or to receive an SL TB for NC from the UE, respectively, in response to receiving at least one of a first indication of a rejection of the first NC handover request, a second indication of no buffering of the SL NC TB, or a third indication of failed reception of the SL NC TB; a means for obtaining, from a first device, a first message including first location information associated with a UE, the UE performing SL communication with a first encoder associated with a first zone; a means for initializing NC handover of the UE to a second encoder in the second zone in response to the first location information indicating movement of the UE from the first zone to the second zone; a means for obtaining, from the first encoder, a second message including location information associated with each UE in a set of UEs performing SL communication with the first encoder; a means for obtaining, from the first encoder, second location information associated with the first encoder; a means for outputting, to the second encoder, the first NC handover request for the second encoder to communicate the SLTB with the UE; and a means for outputting, to the second encoder, a signal for transmitting the SL TB using the first SL resource. TB, or outputs to the UE a second grant for sending an SL TB using a second SL resource; and outputs to the first encoder a second NC handover request for sending an SL NC TB to the first encoder. The method may include: outputting a third grant for sending a SL NC TB using a third SL resource to a first encoder; obtaining an indication of acceptance of a first NC handover request from a second encoder or a UE; outputting a first grant for sending a SL NC TB using a first SL resource by outputting the first grant based on the indication of acceptance of the first NC handover request; obtaining an acknowledgment message from the second encoder; obtaining an acknowledgment message from the second encoder; obtaining a first message from the first device, the first message including first location information associated with a UE that is in SL communication with a first encoder associated with a first zone; initiating NC handover of the UE to a second encoder in the second zone in response to the first location information indicating movement of the UE from the first zone to the second zone; obtaining a second message from the first encoder, the second message including location information associated with each UE in a set of UEs in SL communication with the first encoder; obtaining second location information associated with the first encoder from the first encoder; and outputting an acknowledgment message for the second encoder to communicate SL TBs with the UE to the second encoder. a component for outputting a first NC handover request for a TB; a component for outputting a first grant for sending an SL NC TB using a first SL resource to a second encoder, or a component for outputting a second grant for sending an SL TB using a second SL resource to a UE;Components for outputting a second NC handover request for transmitting a SL NC TB to the first encoder; components for outputting a third grant for transmitting the SL NC TB using a third SL resource to the first encoder; components for outputting a second NC handover request for transmitting the SL NC TB to the first encoder; components for outputting a third grant for transmitting the SL NC TB using a third SL resource to the first encoder; components for obtaining an indication of acceptance of the first NC handover request from the second encoder; components for outputting a first grant for transmitting the SL NC TB using the first SL resource by outputting a first grant based on the indication of acceptance of the first NC handover request; components for obtaining a confirmation message from the second encoder; or components for outputting a second NC handover request to the second encoder based on the first indication of rejection of the first NC handover request. Components may be components 199 of the network entity 2302 configured to perform the functions recited by the components. As described above, the network entity 2302 may include a Tx processor 316, an Rx processor 370, and a controller / processor 375. Thus, in one configuration, the components may be the Tx processor 316, the Rx processor 370, and the controller / processor 375 configured to perform the functions recited by the components.

[0271] As discussed above, Figure 5Component 197 in the embodiment is configured to receive an NC handover request from a network entity. Component 197 may also be configured to send a SL NC TB to the UE based on the NC handover request. Component 197 may be within a processor. Component 197 may be one or more hardware components specifically configured to perform the described procedures / algorithms, implemented by one or more processors configured to perform the described procedures / algorithms, stored on a computer-readable medium for implementation by one or more processors, or some combination thereof. Encoder 507 may include multiple components configured for various functions.In one configuration, the encoder 507 includes: means for sending or receiving a SL TB for NC with a UE; means for sending a first message to a network entity, the first message including a location indicating movement of the UE from a first transmission zone to a second transmission zone; means for sending or receiving at least one SL transmission with each UE in a set of UEs, wherein the UE set includes the UE; means for sending a location set to the network entity, the location set including location information of each UE in the set of UEs; means for receiving an NC handover request from the network entity; means for sending an SL TB for NC to a second encoder of the second transmission zone based on the NC handover request; means for receiving the NC handover request from the network entity; means for sending an SL NCTB to the UE based on the NC handover request; means for sending an indication of acceptance of the NC handover request to the network entity; means for receiving a grant of SL resources in at least one of time or frequency from the network entity in response to the indication of acceptance, wherein sending the SL NC TB with the UE includes sending the SL NC TB with the UE using the SL resources; and means for sending the SL NC TB to the second encoder. TB; a component for receiving a SL NC TB from a second encoder in response to the request; a component for sending an acknowledgment message to a network entity in response to the NC handover request; a component for sending a second acknowledgment message to the second encoder in response to the NC handover request, wherein the second acknowledgment message includes a PSCCH message or a PSFCH message; a component for receiving a SL NC TB from the second encoder; a component for receiving an NC handover request from the network entity; a component for sending a SL NC TB to the UE based on the NC handover request; a component for receiving the NC handover request by receiving at least one of a DCI, a MAC-CE or an RRC including the NC handover request; a component for sending an indication of acceptance of the NC handover request to the network entity; a component for receiving a grant of SL resources in at least one of time or frequency from the network entity; a component for sending the SL NC TB to the UE based on the NC handover request by using the SL resources; a component for sending a request for the SL NC TB to the first encoder; a component for receiving the SL from the first encoder in response to sending the request NC TB component; component for sending a confirmation message to the network entity based on the NC handover request; or component for sending a second confirmation message to the first encoder based on the NC handover request. The component can be a component 197 of the encoder 507 configured to perform the functions recorded by the component.

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

[0273] 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, references to elements in the singular form do not mean "one and only one", but "one or more". Terms such as "if", "when..." and "at..." do not imply a direct temporal relationship or reaction. That is, these phrases, such as "when...", do not mean immediate action in response to the occurrence of an action or during the occurrence of an action, but only mean that if the conditions are met, the action will occur without the need for specific or immediate time constraints for the action to occur. 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 and may include multiple A’s, multiple B’s, or multiple C’s. 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, B, and C, where any such combination may include 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 a first device receives data from or sends data to a 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 this disclosure that are known or later become known to those 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 expressly stated in the claims. Words such as "module," "mechanism," "element," and "device" are not substituted for the word "component." Therefore, no claim element will be understood to be part-plus-function unless the element is expressly stated using the phrase "component for..."

[0274] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0275] A device configured to "output" data (such as sending a signal or message) can, for example, send the data using a transceiver, or can transmit the data to the device that sent the data. A device configured to "obtain" data (such as sending a signal or message) can, for example, receive the data using a transceiver, or can obtain the data from the device that received the data.

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

[0277] Aspect 1 is a method of wireless communication at a first device, comprising transmitting a SL TB for NC to a second device or receiving the SL TB for NC from the second device, respectively. At least one of the first device and the second device may include a UE. The method may further include transmitting a first message to a network entity, the first message including a location indicating movement of the UE from a first transmission zone to a second transmission zone.

[0278] Aspect 2 is the method according to aspect 1, wherein the first device can include the UE.The second device can include a first encoder of the first transmission zone.

[0279] Aspect 3 is a method according to aspect 2, wherein the first message can include a BSR indicating the location of the UE.

[0280] Aspect 4 is a method according to any one of aspects 1 to 3, wherein the uplink transmission can include a UEID, a zone ID or a GNSS position of the UE.

[0281] Aspect 5 is the method according to aspect 1, wherein the first device can include a first encoder that performs network decoding on the TB. The second device can include the UE.

[0282] Aspect 6 is a method according to aspect 5, further comprising sending at least one SL transmission to each UE in a set of UEs or receiving at least one SL transmission from each UE in the set of UEs. The set of UEs may include the UEs. The method may further comprise sending a location set to the network entity, the location set including the location of each UE in the set of UEs.

[0283] Aspect 7 is a method according to any one of aspects 5 to 6, further comprising sending the location of the first encoder to the network entity.

[0284] Aspect 8 is a method according to any one of aspects 5 to 7, further comprising receiving an NC handover request n from the network entity. The method may further comprise transmitting the SL TB for NC to the second encoder of the second transmission zone based on the NC handover request n.

[0285] Aspect 9 is a method of wireless communication at a network entity, comprising obtaining an uplink transmission from a first device, the uplink transmission including a location of a UE in SL communication with a first encoder in a first transmission zone. The method may further include initiating an NC handover of the UE to a second encoder in a second transmission zone in response to the location indicating movement of the UE from the first transmission zone to the second transmission zone.

[0286] Aspect 10 is the method according to aspect 9, wherein the first device can include the UE.

[0287] Aspect 11 is a method according to aspect 10, wherein the uplink transmission can include a BSR having the location.

[0288] Aspect 12 is a method according to any one of aspects 9 to 11, wherein the uplink transmission can include a UE ID, a zone ID or a GNSS position of the UE.

[0289] Aspect 13 is a method according to any one of aspects 9 or 12, wherein the first device can include the first encoder.

[0290] Aspect 14 is a method according to aspect 13, further comprising obtaining a position set from the first encoder, the position set having position information of each UE in a set of UEs that perform SL communication with the first encoder. The UE set may include the UE.

[0291] Aspect 15 is a method according to any one of aspects 13 to 14, further comprising obtaining position information of the first encoder from the first encoder. The position of the first encoder and the uplink transmission can indicate the movement of the UE from the first transmission zone to the second transmission zone.

[0292] Aspect 16 is a method for wireless communication at a destination encoder. Network coding for a UE can be handed over to the destination encoder. The method can include receiving an NC handover request n from a network entity. The method can also include sending a SL NC TB to the UE based on the NC handover request.

[0293] Aspect 17 is a method according to aspect 16, wherein the NC handover request can include DCI transmission, MAC-CE transmission, or RRC transmission.

[0294] Aspect 18 is a method according to any one of Aspects 16 to 17, wherein the NC handover request may include at least one of the following: (a) a first indication to the destination encoder, (b) a second indication to the source encoder, (c) a third indication for the source encoder to send the SL NC TB to the destination encoder, or (d) a fourth indication for the source encoder to send the SL NC TB to the UE.

[0295] Aspect 19 is a method according to any one of aspects 16 to 18, wherein the NC handover request can include a first indication for the source encoder to send the SL NC TB to the destination encoder, and the SL NC TB includes a second indication sent by the NC.

[0296] Aspect 20 is a method according to any one of aspects 16 to 19, wherein the NC handover request can include a grant of SL resources in at least one of time or frequency. Sending the SL NC TB with the UE can include using the SL resources to send the SL NC TB with the UE.

[0297] Aspect 21 is a method according to any one of aspects 16 to 20, further comprising sending an indication of acceptance of the NC handover request to the network entity. The method may also include receiving a grant of SL resources in at least one of time or frequency from the network entity. The grant of the SL resources may be received in response to the indication of the acceptance. Sending the SL NC TB with the UE may include using the SL resources to send the SL NC TB with the UE.

[0298] Aspect 22 is a method according to any one of aspects 16 to 21, wherein the NC handover request can include at least one of unicast transmission, multicast transmission, or broadcast transmission.

[0299] Aspect 23 is a method according to any one of aspects 16 to 22, further comprising sending a request for the SLNC TB to a second encoder. The method can further comprise receiving the SLNC TB from the second encoder in response to the request.

[0300] Aspect 24 is a method according to any one of aspects 16 to 23, further comprising sending a confirmation message to the network entity in response to the NC handover request.

[0301] Aspect 25 is the method according to aspect 24, wherein the confirmation message can include a UCI format.

[0302] Aspect 26 is a method according to Aspect 25, wherein the confirmation message may include at least one of the following: (a) a first indication of acceptance of the NC handover request, (b) a second indication of rejection of the NC handover request, (c) a third indication of buffering of the SL NC TB, (d) a fourth indication of unbufferedness of the SL NC TB, (e) a fifth indication of successful reception of the SL NC TB, or (f) a sixth indication of failed reception of the SL NC TB.

[0303] Aspect 27 is a method according to any one of aspects 24 to 26, further comprising sending a second confirmation message to the source encoder in response to the NC handover request.

[0304] Aspect 28 is a method according to aspect 27, wherein the second confirmation message can include a PSCCH message or a PSFCH message.

[0305] Aspect 29 is the method according to any one of aspects 24 to 28, further comprising receiving the SLNC TB from a source encoder.

[0306] Aspect 30 is a method according to any one of aspects 16 to 29, wherein the SL NC TB can include a header having at least one of: an indication of an NC handover request, or an ID of the destination encoder.

[0307] Aspect 31 is a method of wireless communication at a network entity, comprising outputting a first NC handover request to a destination encoder for the destination encoder to send a SL TB for NC to a UE or to receive the SL TB for NC from the UE, respectively. The method may also include outputting a first grant to one of the destination encoder or the UE to use SL resources to send the SL NC TB.

[0308] Aspect 32 is a method according to aspect 31, further comprising outputting a second NC handover request to a source encoder for the source encoder to transmit the SL NC TB. The method may further comprise outputting a second grant to the source encoder for transmitting the SL NC TB using a second SL resource.

[0309] Aspect 33 is a method according to aspect 32, wherein the first NC handover request can include a first unicast transmission.The second NC handover request can include a second unicast transmission.

[0310] Aspect 34 is a method according to aspect 32, wherein the first NC handover request and the second NC handover request can constitute a multicast transmission or a broadcast transmission.

[0311] Aspect 35 is a method according to any one of aspects 31 to 34, wherein the first NC handover request can include DCI transmission, MAC-CE transmission, or RRC transmission.

[0312] Aspect 36 is a method according to any one of Aspects 31 to 35, wherein the first NC handover request may include at least one of the following: (a) a first indication to the destination encoder, (b) a second indication to the source encoder, (c) a third indication for the source encoder to send the SL NC TB to the destination encoder, or (d) a fourth indication for the source encoder to send the SL NC TB to the UE.

[0313] Aspect 37 is a method according to any one of aspects 31 to 36, wherein the first NC handover request can include a first indication for the source encoder to send the SL NC TB to the destination encoder, and the SL NC TB includes a second indication sent by the NC.

[0314] Aspect 38 is a method according to any one of aspects 31 to 37, wherein the first NC handover request can include the grant to send the SL NC TB using the SL resources in at least one of time or frequency.

[0315] Aspect 39 is a method according to any one of aspects 31 to 38, further comprising obtaining an indication of acceptance of the first NC handover request from the destination encoder or the UE. Outputting the grant for using the SL resources to send the SL NC TB can be in response to obtaining the indication of acceptance of the first NC handover request.

[0316] Aspect 40 is a method according to any one of aspects 31 to 39, further comprising obtaining a confirmation message from the destination encoder.

[0317] Aspect 41 is a method according to aspect 40, wherein the confirmation message can include a UCI format.

[0318] Aspect 42 is a method according to aspect 41, wherein the confirmation message may include at least one of the following: (a) a first indication of acceptance of the NC handover request, (b) a second indication of rejection of the NC handover request, (c) a third indication of buffering of the SL NC TB, (d) a fourth indication of unbufferedness of the SL NC TB, (e) a fifth indication of successful reception of the SL NC TB, or (f) a sixth indication of failed reception of the SL NC TB.

[0319] Aspect 43 is a method according to any one of Aspects 40 to 42, further comprising outputting to a second destination encoder a second NC handover request for the second destination encoder to send the SL TB for NC to the UE or receive the SL TB for NC from the UE, respectively, in response to receiving at least one of the following: (a) a first indication of rejection of the first NC handover request, (b) a second indication of no buffering of the SL NC TB, or (c) a third indication of failed reception of the SL NCTB.

[0320] Aspect 44 is a method of wireless communication at a first device, wherein the method may include communicating a SL TB with a second device for NC. At least one of the first device or the second device may include a UE. The method may also include sending a first message to a network entity, the first message including first location information indicating movement of the UE from a first area to a second area.

[0321] Aspect 45 is a method according to aspect 44, wherein the first device comprises the UE, and the second device comprises a first encoder associated with the first zone.

[0322] Aspect 46 is a method according to aspect 45, wherein the first message includes a BSR, the BSR including the first location information associated with the UE.

[0323] Aspect 47 is a method according to any one of aspects 44 to 46, wherein the first message includes a UE ID, a zone ID, or a geographic location associated with the UE.

[0324] Aspect 48 is a method according to aspect 44, wherein the first device comprises a first encoder that encodes the TB, and the second device comprises the UE.

[0325] Aspect 49 is a method according to aspect 48, wherein communicating the SL TB for NC can include communicating at least one SL TB with each UE in a set of UEs. Sending the first message including the first location information can include sending location information associated with each UE in the set of UEs to the network entity.

[0326] Aspect 50 is a method according to any one of aspects 44 to 49, wherein the method may include sending second location information associated with the first encoder to the network entity.

[0327] Aspect 51 is a method according to any one of aspects 44 to 50, wherein the method may include receiving an NC handover request from the network entity. The method may include sending the SL TB to the second encoder of the second zone based on the NC handover request.

[0328] Aspect 52 is a method of wireless communication at a network entity, wherein the method may include obtaining a first message from a first device, the first message including first location information associated with a UE, the UE in SL communication with a first encoder associated with a first zone. The method may include initiating an NC handover of the UE to a second encoder in the second zone in response to the first location information indicating movement of the UE from the first zone to the second zone.

[0329] Aspect 53 is a method according to aspect 52, wherein the first device comprises the UE.

[0330] Aspect 54 is a method according to aspect 53, wherein the first message includes a BSR, and the BSR includes the first location information.

[0331] Aspect 55 is a method according to any one of aspects 53 to 54, wherein the first message includes a UE ID, a zone ID, or a geographic location associated with the UE.

[0332] Aspect 56 is a method according to any one of aspects 52 to 55, wherein the first device includes the first encoder.

[0333] Aspect 57 is a method according to aspect 56, wherein the method may include obtaining a second message from the first encoder, the second message including location information associated with each UE in a set of UEs in SL communication with the first encoder. The set of UEs may include the UE.

[0334] Aspect 58 is a method according to any one of aspects 52 to 57, wherein the method may include obtaining, from the first encoder, second position information associated with the first encoder. The first position information and the second position information associated with the first encoder may indicate the movement of the UE from the first zone to the second zone.

[0335] Aspect 59 is a method of wireless communication at a second encoder, wherein the method can include receiving an NC handover request from a network entity.The method can include sending a SL NC TB to a UE based on the NC handover request.

[0336] Aspect 60 is a method according to aspect 59, wherein receiving the NC handover request can include receiving at least one of a DCI, a MAC-CE, or an RRC including the NC handover request.

[0337] Aspect 61 is a method according to any one of Aspects 59 to 60, wherein the NC handover request may include at least one of the following: a first indication to the second encoder, a second indication to the first encoder, a third indication for the first encoder to send the SL NC TB to the second encoder, or a fourth indication for the first encoder to send the SL NC TB to the UE.

[0338] Aspect 62 is a method according to any one of aspects 59 to 61, wherein the NC handover request can include a first indication for the first encoder to send the SL NC TB to the second encoder, and the SL NC TB can include a second indication sent by the NC.

[0339] Aspect 63 is a method according to any one of aspects 59 to 62, wherein the NC handover request can include a grant of SL resources in at least one of time or frequency. Sending the SLNC TB to the UE based on the NC handover request can include using the SL resources to send the SLNC TB to the UE.

[0340] Aspect 64 is a method according to any one of aspects 59 to 63, wherein the method may include sending an indication of acceptance of the NC handover request to the network entity. The method may include receiving a grant of SL resources in at least one of time or frequency from the network entity. Sending the SL NC TB to the UE based on the NC handover request may include sending the SL NC TB to the UE using the SL resources.

[0341] Aspect 65 is a method according to any one of aspects 59 to 64, wherein at least one of a unicast transmission, a multicast transmission, or a broadcast transmission can include the NC handover request.

[0342] Aspect 66 is a method according to any one of aspects 59 to 65, wherein the method may include sending a request for the SL NC TB to a first encoder. The method may include receiving the SL NC TB from the first encoder in response to sending the request.

[0343] Aspect 67 is a method according to any one of aspects 59 to 66, wherein the method can include sending a confirmation message to the network entity based on the NC handover request.

[0344] Aspect 68 is a method according to aspect 67, wherein the confirmation message may include UCI, and the confirmation may include (a) a first indication of acceptance of the NC handover request, (b) a second indication of rejection of the NC handover request, (c) a third indication of buffering of the SL NC TB, (d) a fourth indication of unbufferedness of the SL NC TB, (e) a fifth indication of successful reception of the SL NC TB, or (f) a sixth indication of failed reception of the SL NC TB.

[0345] Aspect 69 is a method according to any one of aspects 67 to 68, wherein the method can include sending a second confirmation message to the first encoder based on the NC handover request. The second confirmation message can include a PSCCH message or a PSFCH message.

[0346] Aspect 70 is a method according to any one of aspects 67 to 69, wherein the method may include receiving the SL NC TB from a first encoder.

[0347] Aspect 71 is a method according to aspect 70, wherein the SL NC TB can include a header having at least one of: an indication of the NC handover request, or an ID of the second encoder.

[0348] Aspect 72 is a method of wireless communication at a network entity, wherein the method may include outputting a first NC handover request to a second encoder for the second encoder to communicate a SL TB with a UE. The method may include outputting a first grant to the second encoder to send the SL NC TB using a first SL resource, or outputting a second grant to the UE to send the SL TB using a second SL resource.

[0349] Aspect 73 is a method according to aspect 72, wherein the method may include outputting a second NC handover request to a first encoder for transmitting the SL NC TB to the first encoder. The method may include outputting a third grant to the first encoder for transmitting the SL NC TB using a third SL resource.

[0350] Aspect 74 is a method according to any one of aspects 72 to 73, wherein the method may include outputting a second NC handover request to a first encoder for transmitting the SL NC TB to the first encoder. The method may include outputting a third grant to the first encoder for transmitting the SL NC TB using a third SL resource.

[0351] Aspect 75 is a method according to aspect 74, wherein the first unicast transmission can include the first NC handover request.The second unicast transmission can include the second NC handover request.

[0352] Aspect 76 is a method according to any one of aspects 74 to 75, wherein the multicast transmission or the broadcast transmission can include the first NC handover request and the second NC handover request.

[0353] Aspect 77 is a method according to any one of aspects 72 to 76, wherein at least one of DCI, MAC-CE, or RRC can include the first NC handover request.

[0354] Aspect 78 is a method according to any one of Aspects 72 to 77, wherein the first NC handover request may include at least one of the following: a first indication to the second encoder, a second indication to the first encoder, a third indication for the first encoder to send the SL NC TB to the second encoder, or a fourth indication for the first encoder to send the SL NC TB to the UE.

[0355] Aspect 79 is a method according to any one of aspects 72 to 78, wherein the first NC handover request can include a first indication for the first encoder to send the SL NC TB to the second encoder, and the SL NC TB can include a second indication sent by the NC.

[0356] Aspect 80 is a method according to any one of aspects 72 to 79, wherein the first NC handover request can include the first grant for sending the first SL NC TB using the first SL resource in at least one of time or frequency.

[0357] Aspect 81 is a method according to any one of aspects 72 to 80, wherein the method may include obtaining an indication of acceptance of the first NC handover request from the second encoder. Outputting the first grant for sending the SL NC TB using the first SL resource may include outputting the first grant based on the indication of acceptance of the first NC handover request.

[0358] Aspect 82 is a method according to any one of aspects 72 to 81, wherein the method can include obtaining an acknowledgement message from the second encoder.

[0359] Aspect 83 is a method according to aspect 82, wherein the confirmation message can include UCI. The confirmation message can include at least one of the following: (a) a first indication of acceptance of the NC handover request, (b) a second indication of rejection of the NC handover request, (c) a third indication of buffering of the SL NC TB, (d) a fourth indication of no buffering of the SL NC TB, (e) a fifth indication of successful reception of the SL NC TB, or (f) a sixth indication of failed reception of the SL NC TB.

[0360] Aspect 84 is a method according to any one of aspects 82 to 83, wherein the method can include outputting a second NC handover request to a second encoder based on a first indication of a rejection of the first NC handover request.

[0361] Aspect 85 is an apparatus for wireless communication, comprising means for performing the method according to any one of aspects 1 to 15.

[0362] Aspect 86 is an apparatus for wireless communication, comprising a memory; and at least one processor coupled to the memory and configured to perform the method according to any one of aspects 1 to 15.

[0363] In aspect 87, the apparatus according to aspect 85 or 86 further comprises at least one antenna.

[0364] Aspect 88 is a non-transitory computer-readable storage medium storing computer-executable code, which, when executed by a processor, causes the processor to perform the method according to any one of aspects 1 to 15.

[0365] Aspect 89 is an apparatus for wireless communication, comprising means for performing the method according to any one of aspects 16 to 30.

[0366] Aspect 90 is an apparatus for wireless communication, comprising a memory; and at least one processor coupled to the memory and configured to perform the method according to any one of aspects 16 to 30.

[0367] In aspect 91, the apparatus according to aspect 89 or 90 further comprises at least one antenna.

[0368] Aspect 92 is a non-transitory computer-readable storage medium storing computer-executable code, which, when executed by a processor, causes the processor to perform the method according to any one of aspects 16 to 30.

[0369] Aspect 93 is an apparatus for wireless communication, comprising means for performing the method according to any one of aspects 31 to 43.

[0370] Aspect 94 is an apparatus for wireless communication, comprising a memory; and at least one processor coupled to the memory and configured to perform the method of any one of aspects 31 to 43.

[0371] In aspect 95, the apparatus according to aspect 93 or 94 further comprises at least one antenna.

[0372] Aspect 96 is a non-transitory computer-readable storage medium storing computer-executable code, which, when executed by a processor, causes the processor to perform the method according to any one of aspects 31 to 43.

[0373] Aspect 97 is an apparatus for wireless communication, comprising means for performing the method according to any one of aspects 44 to 51.

[0374] Aspect 98 is an apparatus for wireless communication, comprising a memory; and at least one processor coupled to the memory and configured to perform the method of any one of aspects 44 to 51.

[0375] In aspect 99, the apparatus according to aspect 97 or 98 further comprises at least one antenna.

[0376] Aspect 100 is a non-transitory computer-readable storage medium storing computer-executable code, which, when executed by a processor, causes the processor to perform the method according to any one of aspects 44 to 51.

[0377] Aspect 101 is an apparatus for wireless communication, comprising means for performing the method according to any one of aspects 52 to 58.

[0378] Aspect 102 is an apparatus for wireless communication, comprising a memory; and at least one processor coupled to the memory and configured to perform the method of any one of aspects 52 to 58.

[0379] In aspect 103, the apparatus according to aspect 101 or 102 further comprises at least one antenna.

[0380] Aspect 104 is a non-transitory computer-readable storage medium storing computer-executable code, which, when executed by a processor, causes the processor to perform the method according to any one of aspects 52 to 58.

[0381] Aspect 105 is an apparatus for wireless communication, comprising means for performing the method according to any one of aspects 59 to 71.

[0382] Aspect 106 is an apparatus for wireless communication, comprising a memory; and at least one processor coupled to the memory and configured to perform the method of any one of aspects 59 to 71.

[0383] In aspect 107, the apparatus according to aspect 105 or 106 further comprises at least one antenna.

[0384] Aspect 108 is a non-transitory computer-readable storage medium storing computer-executable code, which, when executed by a processor, causes the processor to perform the method according to any one of aspects 59 to 71.

[0385] Aspect 109 is an apparatus for wireless communication, comprising means for performing the method according to any one of aspects 72 to 84.

[0386] Aspect 110 is an apparatus for wireless communication, comprising a memory; and at least one processor coupled to the memory and configured to perform the method of any one of aspects 72 to 84.

[0387] In aspect 111, the apparatus according to aspect 109 or 110 further comprises at least one antenna.

[0388] Aspect 112 is a non-transitory computer-readable storage medium storing computer-executable code, which, when executed by a processor, causes the processor to perform the method according to any one of aspects 72 to 84.

Claims

1. An apparatus for wireless communication at a first device, the apparatus comprising: Memory; and at least one processor, the at least one processor coupled to the memory, the at least one processor configured to: communicating a sidelink transport block (TB) for network coding with a second device, wherein at least one of the first device or the second device comprises a user equipment (UE); and A first message is sent to a network entity, the first message including first location information indicating movement of the UE from a first zone to a second zone. 2 . The apparatus of claim 1 , wherein the first device comprises the UE, and the second device comprises a first encoder associated with the first zone.

3. The apparatus of claim 2, wherein the first message comprises a buffer status report (BSR) comprising the first location information associated with the UE.

4. The apparatus of claim 1 , further comprising a transceiver coupled to the at least one processor, wherein the at least one processor is further configured to send the first message using the transceiver, wherein the first message comprises a UE identifier (ID), a zone ID, or a geographic location associated with the UE. 5 . The apparatus of claim 1 , wherein the first device comprises a first encoder that encodes the TB, and the second device comprises the UE.

6. The device according to claim 5, wherein: To communicate the sidelink TB for the network decoding, the at least one processor is further configured to communicate at least one sidelink TB with each UE in a set of UEs, wherein the set of UEs includes the UE; and To send the first message including the first location information, the at least one processor is further configured to send location information associated with each UE in the set of UEs to the network entity.

7. The apparatus of claim 5, wherein the at least one processor is further configured to send second location information associated with the first encoder to the network entity.

8. The apparatus of claim 5, wherein the at least one processor is further configured to: receiving a network decoding handover request from the network entity; and The sidelink TB is sent to a second encoder of the second zone based on the network coding handover request.

9. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and at least one processor, the at least one processor coupled to the memory, the at least one processor configured to: obtaining a first message from a first device, the first message including first location information associated with a UE, the UE being in sidelink communication with a first encoder associated with a first zone; and In response to the first location information indicating movement of the UE from the first region to the second region, a network coding handover of the UE to a second encoder in the second region is initialized.

10. The apparatus of claim 9, wherein the first device comprises the UE.

11. The apparatus of claim 10, wherein the first message comprises a buffer status report (BSR), the buffer status report (BSR) comprising the first location information.

12. The apparatus of claim 9, further comprising a transceiver coupled to the at least one processor, wherein the at least one processor is further configured to use the transceiver to obtain the first message, and wherein the first message comprises a UE identifier (ID), a zone ID, or a geographic location associated with the UE.

13. The apparatus of claim 9, wherein the first device comprises the first encoder.

14. The apparatus of claim 13, wherein the at least one processor is further configured to: A second message is obtained from the first encoder, the second message comprising location information associated with each UE in a set of UEs communicating with the first encoder via a sidelink, wherein the set of UEs includes the UE.

15. The apparatus of claim 13, wherein the at least one processor is further configured to: Second location information associated with the first encoder is obtained from the first encoder, wherein the first location information and the second location information associated with the first encoder indicate the movement of the UE from the first region to the second region.

16. An apparatus for wireless communication at a second encoder, the apparatus comprising: Memory; and at least one processor, the at least one processor coupled to the memory, the at least one processor configured to: receiving a network decoding handover request from a network entity; and A sidelink network coded transport block (TB) is sent to a user equipment (UE) based on the network coded handover request.

17. The apparatus of claim 16, further comprising a transceiver coupled to the at least one processor, wherein to receive the network decoding handover request, the at least one processor is further configured to use the transceiver to receive at least one of the following including the network decoding handover request: downlink control information (DCI), medium access control (MAC) control element (MAC-CE), or radio resource control (RRC).

18. An apparatus according to claim 16, wherein the network decoding handover request comprises at least one of the following: a first indication to the second encoder, a second indication to the first encoder, a third indication for the first encoder to send the sidelink network decoding TB to the second encoder, or a fourth indication for the first encoder to send the sidelink network decoding TB to the UE.

19. The apparatus of claim 16, wherein the network decoding handover request comprises a first indication for a first encoder to send the sidelink network decoding TB to the second encoder, and the sidelink network decoding TB comprises a second indication for network decoding to send.

20. The apparatus of claim 16, wherein the network decoding handover request comprises a grant of side link resources in at least one of time or frequency, wherein in order to send the side link network decoding TB to the UE based on the network decoding handover request, the at least one processor is further configured to send the side link network decoding TB to the UE using the side link resources.

21. The apparatus of claim 16, wherein the at least one processor is further configured to: sending an indication of acceptance of the network coding handover request to the network entity; and A grant of sidelink resources in at least one of time or frequency is received from the network entity, wherein in order to send the sidelink network decoding TB, the at least one processor is also configured to use the sidelink resources to send the sidelink network decoding TB to the UE.

22. The apparatus of claim 16, wherein at least one of a unicast transmission, a multicast transmission, or a broadcast transmission includes the network decoding handover request.

23. The apparatus of claim 16, wherein the at least one processor is further configured to: Sending a request to the first encoder for the sidelink network decoding TB as sending the request; and The sidelink network decoding TB is received from the first encoder in response to the sending of the request.

24. The apparatus of claim 16, wherein the at least one processor is further configured to: A confirmation message is sent to the network entity based on the network decoding the handover request.

25. The apparatus of claim 24, wherein the confirmation message comprises uplink control information (UCI) and comprises at least one of: a first indication of acceptance of a handover request to the network decoding, a second indication of a rejection of the network decoding handover request, a third indication of a buffer of said sidelink network decoding TBs, a fourth indication of unbuffered decoding of the sidelink network TB, a fifth indication of successful receipt of the sidelink network decoding TB, or A sixth indication of failed reception of the sidelink network decoding TB.

26. The apparatus of claim 24, wherein the at least one processor is further configured to: A second confirmation message is sent to the first encoder based on the network decoding the handover request, wherein the second confirmation message includes a physical sidelink control channel (PSCCH) message or a physical sidelink feedback channel (PSFCH) message.

27. The apparatus of claim 16, wherein the at least one processor is further configured to: The sidelink network decoding TB is received from the first encoder.

28. The apparatus of claim 27, wherein the sidelink network coding (TB) comprises a header having at least one of: an indication of the network coding handover request, or an identifier (ID) of the second encoder.

29. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and at least one processor, the at least one processor coupled to the memory, the at least one processor configured to: outputting to a second encoder a first network decoding handover request for communicating a sidelink transport block (TB) between the second encoder and a user equipment (UE); as well as A first grant for sending a sidelink network decoding TB using a first sidelink resource is output to the second encoder, or a second grant for sending the sidelink TB using a second sidelink resource is output to the UE.

30. The apparatus of claim 29, wherein the at least one processor is further configured to: Outputting to the first encoder a second network decoding handover request for sending the side link network decoding TB to the first encoder; and A third grant for sending the sidelink network decoding TB using a third sidelink resource is output to the first encoder.

31. The apparatus of claim 30, wherein a first unicast transmission comprises the first network-decoded handover request, and wherein a second unicast transmission comprises the second network-decoded handover request.

32. The apparatus of claim 30, wherein the multicast transmission or the broadcast transmission includes the first network decoding handover request and the second network decoding handover request.

33. The apparatus of claim 29, further comprising a transceiver coupled to the at least one processor, wherein to output the first network decoding handover request, the at least one processor is further configured to use the transceiver to send the first network decoding handover request, wherein at least one of downlink control information (DCI), medium access control (MAC) control element (MAC-CE), or radio resource control (RRC) includes the first network decoding handover request.

34. An apparatus according to claim 29, wherein the first network decoding handover request includes at least one of the following: a first indication to the second encoder, a second indication to the first encoder, a third indication for the first encoder to send the sidelink network decoding TB to the second encoder, or a fourth indication for the first encoder to send the sidelink network decoding TB to the UE.

35. The apparatus of claim 29, wherein the first network decoding handover request comprises a first indication for a first encoder to send the sidelink network decoding TB to the second encoder, and the sidelink network decoding TB comprises a second indication for network decoding to send.

36. The apparatus of claim 29, wherein the first network coding handover request comprises the first grant to send the sidelink network coding TB using the first sidelink resource in at least one of time or frequency.

37. The apparatus of claim 29, wherein the at least one processor is further configured to: and obtaining, from the second encoder, an indication of an acceptance of the first network decoding handover request, wherein in order to output the first grant for sending the sidelink network decoding TB using the first side link resources, the at least one processor is further configured to output the first grant based on the indication of the acceptance of the first network decoding handover request.

38. The apparatus of claim 29, wherein the at least one processor is further configured to: Obtain an acknowledgement message from the second encoder.

39. The apparatus of claim 38, wherein the confirmation message comprises uplink control information (UCI) and comprises at least one of: a first indication of acceptance of the handover request decoded by the first network, a second indication of a rejection of the handover request decoded by the first network, a third indication of a buffer of said sidelink network decoding TBs, a fourth indication of unbuffered decoding of the sidelink network TB, a fifth indication of successful receipt of the sidelink network decoding TB, or A sixth indication of failed reception of the sidelink network decoding TB.

40. The apparatus of claim 38, wherein the at least one processor is further configured to: The second network decoding handover request is output to a second encoder based on a first indication of a rejection of the first network decoding handover request.

Images