Copying sidelink transmissions for sidelink carrier aggregation

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a first user equipment (UE) may transmit a replicated transmission of a sidelink transmission on a plurality of component carriers to a second UE based at least in part on a broadcast type associated with the sidelink transmission and one or more indications received from an upper layer of the first UE, wherein the replicated transmission is associated with the plurality of component carriers associated with a Layer 2 (L2) destination identifier (ID) of the sidelink transmission. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Patent Application No. 17 / 805,433, filed on June 3, 2022, entitled “DUPLICATING SIDELINK TRANSMISSIONS FOR SIDELINK CARRIER AGGREGATION” and assigned to the assignee of this application. The disclosure of the prior application is considered a part of and incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for replicating sidelink transmissions for sidelink carrier aggregation. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as a user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, among other examples).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] In some specific implementations, an apparatus for wireless communication at a first user equipment (UE) includes: a memory; and one or more processors coupled to the memory and configured to: send a sidelink transmission of a replicated transmission on multiple component carriers to a second UE based at least in part on a broadcast type associated with the sidelink transmission and one or more indications received from an upper layer of the first UE, wherein the replicated transmission is associated with the multiple component carriers associated with a layer 2 (L2) destination identifier (ID) of the sidelink transmission.

[0008] In some specific implementations, an apparatus for wireless communication at a second UE includes: a memory; and one or more processors, the one or more processors coupled to the memory and configured to: receive a duplicate transmission of a sidelink transmission on multiple component carriers from a first UE based at least in part on: a broadcast type associated with the sidelink transmission, and one or more indications received from an upper layer of the second UE, and the one or more indications support sidelink carrier aggregation, wherein the duplicate transmission is associated with the multiple component carriers associated with the L2 destination ID of the sidelink transmission.

[0009] In some specific embodiments, a method of wireless communication performed by a first UE includes sending a sidelink transmission to a second UE based at least in part on a broadcast type associated with the sidelink transmission and one or more indications received from an upper layer of the first UE, wherein the replicated transmission is associated with the multiple component carriers associated with an L2 destination ID of the sidelink transmission.

[0010] In some specific embodiments, a method of wireless communication performed by a second UE includes receiving a replicated transmission of a sidelink transmission on multiple component carriers from a first UE based at least in part on: a broadcast type associated with the sidelink transmission, and one or more indications received from upper layers of the second UE, and the one or more indications support sidelink carrier aggregation, wherein the replicated transmission is associated with the multiple component carriers associated with an L2 destination ID of the sidelink transmission.

[0011] In some specific implementations, a non-transitory computer-readable medium storing an instruction set for wireless communication includes one or more instructions that, when executed by one or more processors of a first UE, cause the first UE to: send a sidelink transmission of a replicated transmission on multiple component carriers to a second UE based at least in part on a broadcast type associated with the sidelink transmission and one or more indications received from an upper layer of the first UE, wherein the replicated transmission is associated with the multiple component carriers associated with an L2 destination ID of the sidelink transmission.

[0012] In some specific implementations, a non-transitory computer-readable medium storing an instruction set for wireless communication includes one or more instructions that, when executed by one or more processors of a second UE, cause the second UE to: receive a replicated transmission of a sidelink transmission on multiple component carriers from a first UE based at least in part on: a broadcast type associated with the sidelink transmission, and one or more indications received from upper layers of the second UE, and the one or more indications support sidelink carrier aggregation, wherein the replicated transmission is associated with the multiple component carriers associated with an L2 destination ID of the sidelink transmission.

[0013] In some specific embodiments, a first device for wireless communication includes a component for sending a sidelink transmission to a second device based at least in part on a broadcast type associated with the sidelink transmission and one or more indications received from an upper layer of the first device, wherein the duplicate transmission is associated with the multiple component carriers associated with an L2 destination ID of the sidelink transmission.

[0014] In some specific embodiments, a second device for wireless communication includes a component for receiving a duplicate transmission of a sidelink transmission on multiple component carriers from a first device based at least in part on: a broadcast type associated with the sidelink transmission, and one or more indications received from an upper layer of the second device, and the one or more indications support sidelink carrier aggregation, wherein the duplicate transmission is associated with multiple component carriers associated with an L2 destination ID of the sidelink transmission.

[0015] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0016] The features and technical advantages of the examples according to the present disclosure have been outlined quite extensively above in order to better understand the subsequent specific embodiments. Additional features and advantages will be described below. The disclosed concepts and specific examples can be easily used as a basis for modifying or designing other structures for the same purpose of achieving the present disclosure. Such equivalent constructions do not depart from the scope of protection of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of sidelink carrier aggregation according to the present disclosure.

[0023] Figures 5 to 7 is a diagram illustrating an example associated with duplicating sidelink transmissions for sidelink carrier aggregation according to the present disclosure.

[0024] Figures 8 to 9 is a diagram illustrating example procedures associated with duplicating sidelink transmissions for sidelink carrier aggregation in accordance with the present disclosure.

[0025] Figure 10 to Figure 11 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0026] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method that is practiced using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0027] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a 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.

[0028] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0029] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), one user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0030] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. For example, the network node 110 may include an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network.

[0031] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0032] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with the network node 110). In some aspects, the term "base station" or "network node" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

[0033] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communication between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0034] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0035] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0036] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station and / or a subscriber unit. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node and / or any other suitable device configured to communicate via a wireless or wired medium.

[0037] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, a processor component and a memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0038] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0039] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using network node 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0040] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

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

[0042] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0043] In some aspects, a first UE (e.g., UE 120a) may include a communication manager 140. As described in greater detail elsewhere herein, the communication manager 140 may transmit a duplicate transmission of a sidelink transmission on multiple component carriers to a second UE based at least in part on a playout type associated with the sidelink transmission and one or more indications received from upper layers of the first UE, wherein the duplicate transmission is associated with multiple component carriers associated with a layer 2 (L2) destination identifier (ID) of the sidelink transmission. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0044] In some aspects, the second UE (e.g., UE 120e) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive a duplicate transmission of a sidelink transmission on multiple component carriers from the first UE based at least in part on: a playout type associated with the sidelink transmission, and one or more indications received from upper layers of the second UE, and the one or more indications support sidelink carrier aggregation, wherein the duplicate transmission is associated with multiple component carriers associated with an L2 destination ID of the sidelink transmission. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0045] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 Different than described.

[0046] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a user equipment (UE) 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0047] At the network node 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0048] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0049] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0050] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0051] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 5 to 11 ) or any aspect of any of the methods described herein.

[0052] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions described herein (e.g., reference 20). Figures 5 to 11 ) or any aspect of any of the methods described herein.

[0053] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 8 The process of 800 Fig. 9 900 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 8 The process of 800 Fig. 9 The operations of process 900 and / or other processes described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0054] In some aspects, a first UE (e.g., UE 120a) includes means for transmitting a sidelink transmission to a second UE based at least in part on a playout type associated with the sidelink transmission and one or more indications received from upper layers of the first UE, wherein the replicated transmission is associated with the multiple component carriers associated with the L2 destination ID of the sidelink transmission. Means for performing operations described herein for the first UE may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0055] In some aspects, a second UE (e.g., UE 120e) includes means for receiving a replicated transmission of a sidelink transmission on multiple component carriers from a first UE based at least in part on a playout type associated with the sidelink transmission and one or more indications received from upper layers of the second UE, and the one or more indications support sidelink carrier aggregation, wherein the replicated transmission is associated with multiple component carriers associated with an L2 destination ID of the sidelink transmission. Means for performing operations described herein for the second UE may include, for example, one or more of the communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0056] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0057] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Different than described.

[0058] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0059] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0060] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0061] Figure 3 3 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0062] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of these units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, and the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, or to do both.

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

[0064] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to a functional split (such as a functional split defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0065] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc., based at least in part on functional splitting (e.g., functional splitting defined by 3GPP) (such as lower layer functional splitting). In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0066] The SMO framework 305 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

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

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

[0069] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 Different than described.

[0070] NR sidelink carrier aggregation operation may be designed to support various features, such as sidelink carrier (re)selection, synchronization of aggregated carriers, handling of limited capacity, power control and / or packet duplication for simultaneous sidelink transmissions. NR sidelink carrier aggregation operation may support various features based at least in part on LTE sidelink carrier aggregation operation. NR sidelink carrier aggregation operation may be limited to FR1 licensed spectrum and intelligent transmission system (ITS) bands within FR1 licensed spectrum. NR sidelink carrier aggregation operation may be backward compatible so that when sidelink HARQ is enabled in the sidelink control information (SCI), Release 16 / 17 UEs may be able to receive Release 18 sidelink broadcast / multicast transmissions by carrier aggregation of carriers on which Release 16 / 17 UEs receive a physical sidelink control channel (PSCCH) or a physical sidelink shared channel (PSSCH) and send corresponding sidelink HARQ feedback.

[0071] Carrier aggregation on the PC5 interface can be implemented to LTE V2X. One independent HARQ entity per carrier can be used for V2X sidelink communications. Each transport block and corresponding potential HARQ retransmission can be mapped to a single carrier. Multiple transport blocks can be sent in parallel on different carriers to obtain throughput gains. Sidelink carrier aggregation in resource allocation mode 3 using dynamic grants may include a carrier indication field (CIF) in the downlink control information (DCI) from the network node. Sidelink carrier aggregation in resource allocation mode 4 may use a sensing process to independently select resources on each involved carrier. The same carrier can be used for all transport blocks of the same sidelink process, at least until the process triggers resource reselection.

[0072] Figure 4is a diagram illustrating an example 400 of sidelink carrier aggregation according to the present disclosure.

[0073] like Figure 4 As shown, the sidelink shared channel (SL-SCH) for transmission (Tx) may be associated with multiple carriers (e.g., carrier 1 to carrier M). The MAC layer may be associated with HARQ processing, multiplexing, and scheduling and priority handling. The RLC layer may be associated with segmentation. The PDCP layer may be associated with security and robust header compression (ROHC). The SL-SCH for reception (Rx) may be associated with multiple carriers (e.g., carrier 1 to carrier N). The MAC layer may be associated with HARQ processing, packet filtering, and demultiplexing. The RLC layer may be associated with reorganization. The PDCP layer may be associated with security and ROHC. A sidelink broadcast channel (SL-BCH or SBCCH) for Tx and Rx may be defined. The sidelink discovery channel (SL-DCH) for Tx and Rx may be associated with HARQ processing. In addition, implementing sidelink carrier aggregation may involve establishing radio bearers, logical channels, and transport channels.

[0074] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 Different than described.

[0075] Configuration parameters for V2X communications on the NR PC5 may be based at least in part on mapping rules. The mapping rules may involve mappings between one or more V2X service identifiers and a broadcast or multicast L2 destination ID. The mapping rules may involve mappings between one or more V2X service identifiers and a V2X NR frequency having an associated geographic area. Thus, an L2 destination ID for multicast or broadcast may be associated with multiple V2X services, which may be mapped to different frequency carriers in a geographic area. For example, some services associated to the L2 destination ID may support legacy V2X UEs (e.g., Release 16 / 17 UEs) that do not support sidelink carrier aggregation, and other services associated to the L2 destination ID may support new V2X UEs (e.g., Release 18 or later UEs) that support sidelink carrier aggregation.

[0076] For multicast or broadcast associated to an L2 destination ID, when the selected carrier is not a carrier for a UE that does not support sidelink carrier aggregation, packets sent on a carrier selected for or by a UE that supports sidelink carrier aggregation may not be received by the UE that does not support sidelink carrier aggregation. Therefore, backward compatibility issues may arise for sidelink carrier aggregation.

[0077] In various aspects of the techniques and apparatus described herein, a first UE (e.g., a Tx UE) may transmit a duplicate transmission of a sidelink transmission on multiple component carriers to a second UE (e.g., an Rx UE) supporting sidelink carrier aggregation based at least in part on a playout type associated with the sidelink transmission and one or more indications received from an upper layer of the first UE. The duplicate transmission may be associated with multiple component carriers associated with an L2 destination ID of the sidelink transmission. The first UE may receive HARQ feedback (if enabled) based at least in part on the duplicate transmission of the sidelink transmission from the second UE.

[0078] In some aspects, to support backward compatibility, the sidelink transmission may be replicated on multiple component carriers (e.g., all component carriers) associated to the L2 destination ID. The sidelink transmission may be replicated based at least in part on the broadcast type (e.g., broadcast or multicast) and one or more indications from the upper layer. One or more indications (e.g., Tx profiles) from the upper layer may indicate support or non-support of sidelink carrier aggregation for the L2 destination ID for multicast or broadcast. The upper layer may indicate multiple Tx profiles (e.g., all Tx profiles) associated to the L2 destination ID to the access stratum (AS) layer. Alternatively, the upper layer may indicate only one Tx profile associated to the L2 destination ID to the AS layer. When at least one indication from the upper layer indicates that sidelink carrier aggregation is not supported, the sidelink transmission may be replicated on multiple component carriers associated to the L2 destination ID.

[0079] As an example, a Tx profile associated to a V2X or Proximity Service (ProSe) service identifier may indicate support or non-support of sidelink carrier aggregation at an upper layer, and the upper layer may pass all Tx profiles associated to a multicast or broadcast L2 destination ID to the AS layer. In this case, the L2 destination ID may be associated with one or more Tx profiles from the upper layer, each of which may indicate support or non-support of sidelink carrier aggregation.

[0080] As another example, each of the one or more Tx profiles associated to one or more V2X or ProSe service identifiers may support or not support sidelink carrier aggregation at the upper layer, and the upper layer may pass down only one Tx profile associated to the L2 destination ID for multicast or broadcast to the AS layer based at least in part on whether all Tx profiles support sidelink carrier aggregation (e.g., when all Tx profiles at the upper layer support sidelink carrier aggregation, the Tx profile passed down to the AS layer indicates support for sidelink carrier aggregation, or when one or more Tx profiles at the upper layer do not support sidelink carrier aggregation, the Tx profile passed down to the AS layer indicates support for sidelink carrier aggregation). In this case, the L2 destination ID may be associated with one Tx profile from the upper layer, where the Tx profile may indicate support or not support for sidelink carrier aggregation.

[0081] In some aspects, a MAC PDU duplication sidelink may be sent based at least in part on a configuration to implement duplication via a MAC protocol data unit (PDU). A first UE (e.g., a Tx UE) may duplicate a MAC PDU (e.g., a transport block) on multiple component carriers associated with an L2 destination ID based at least in part on a playout type and an indication from an upper layer (e.g., a Tx profile), and the first UE may insert a duplication indication in a MAC header or a subheader. A second UE (e.g., an Rx UE) may remove the duplicated MAC PDU based at least in part on the duplication indication.

[0082] In some aspects, the sidelink transmission may be duplicated at the PDCP layer based at least in part on a configuration to implement duplication at the PDCP layer. A first UE (e.g., a Tx UE) may duplicate a PDCP packet on a plurality of component carriers associated to an L2 destination ID based at least in part on a playout type and an indication from an upper layer (e.g., a Tx profile), and the first UE may insert a duplication indication in a PDCP header. A second UE (e.g., an Rx UE) may remove the duplicated PDCP packet based at least in part on the duplication indication.

[0083] Figure 5 is a diagram illustrating an example 500 associated with duplicating sidelink transmissions for sidelink carrier aggregation according to the present disclosure. Figure 5 As shown, communication may occur between a network node (e.g., network node 110) or another UE (such as a special UE (e.g., a roadside unit (RSU), a group leader, a cluster head, a scheduling UE, or a Tx UE), a first UE (e.g., UE 120a), a second UE, and a third UE (e.g., UE 120e)). In some aspects, the network node, the special UE, the first UE, the second UE, and the third UE may be included in a wireless network (such as wireless network 100).

[0084] In some aspects, the first UE may be a Tx UE supporting sidelink carrier aggregation, the second UE may be a first Rx UE not supporting sidelink carrier aggregation, and the third UE may be a second Rx UE supporting sidelink carrier aggregation.

[0085] As shown by reference numeral 502, the first UE and / or the third UE may receive one or more indications from upper layers indicating support or non-support of sidelink carrier aggregation (e.g., "SL-CA" or "No-SL-CA") based at least in part on a service or service type associated to an L2 destination ID for multicast or broadcast (support or non-support of sidelink carrier aggregation). In some aspects, for an indication that sidelink carrier aggregation is not supported (e.g., an indication of "No-SL-CA"), one or more carriers may be indicated based at least in part on a mapping between supported carriers and services or service types that do not support sidelink carrier aggregation. In some aspects, for an indication that sidelink carrier aggregation is supported (e.g., an indication of "SL-CA"), multiple carriers may be indicated based at least in part on a mapping between supported component carriers and services or service types that support sidelink carrier aggregation.

[0086] As shown by reference numeral 504, the first UE may be preconfigured or configured with a sidelink component carrier list for sidelink transmission (e.g., for groupcast or broadcast) associated to an L2 destination ID by a network node or a special UE. The first UE may be preconfigured or configured with a sidelink component carrier list (e.g., sl-cc-list1) for sidelink transmission. The first UE may receive a configuration of a sidelink component carrier list configured for sidelink transmission associated with an L2 destination ID from a network node (e.g., via RRC configuration) or a special UE (e.g., via PC5 RRC configuration).

[0087] As shown by reference numeral 506, the second UE may be preconfigured or configured by the network node or the special UE with a sidelink component carrier list for sidelink transmissions associated to the L2 destination ID (e.g., for multicast or broadcast). The second UE may be preconfigured or configured with a sidelink component carrier list (e.g., sl-cc-list2) for sidelink transmissions that do not support sidelink carrier aggregation.

[0088] As indicated by reference numeral 508, the third UE may be preconfigured or configured by the network node or the special UE with a sidelink component carrier list for sidelink transmissions (e.g., for groupcast or broadcast) associated to the L2 destination ID. The third UE may be preconfigured or configured with a sidelink component carrier list (e.g., sl-cc-list3) for sidelink transmissions supporting sidelink carrier aggregation.

[0089] As indicated by reference numeral 510, the first UE may receive one or more indications from upper layers of the first UE for sidelink transmissions (e.g., for groupcast or broadcast) associated to an L2 destination ID. The one or more indications from the upper layers may indicate support or non-support of sidelink carrier aggregation for the L2 destination ID for sidelink transmissions (e.g., multicast or broadcast). An indication in the one or more indications may be based at least in part on a mapping to a sidelink service or service type (e.g., support or non-support of sidelink carrier aggregation) associated to the L2 destination ID. For example, an indication in the one or more indications may correspond to a Tx profile, wherein the Tx profile may be based at least in part on a mapping to a service or service type (e.g., a V2X or ProSe service identifier or service type) associated to the L2 destination ID.

[0090] As indicated by reference numeral 512, the first UE may determine to duplicate the sidelink transmission on multiple component carriers (e.g., multiple or all component carriers of sl-cc-list1) based at least in part on one or more indications received from an upper layer. For example, the multiple component carriers may be derived from a sidelink component carrier list (e.g., sl-cc-list1) such as received from a network node or a special UE (e.g., based at least in part on one or more sidelink component carriers mapped to one or more sidelink services or service types associated with an L2 destination ID and indicated from an upper layer). As another example, multiple component carriers may be indicated from a network node or a special UE (e.g., sl-cc-duplicate-list1 in addition to or as a subset of sl-cc-list1). The first UE may determine to duplicate the transmission on multiple component carriers based at least in part on one or more indications received from an upper layer. The first UE may determine to duplicate the sidelink transmission based at least in part on at least one indication from an upper layer indicating that sidelink carrier aggregation is not supported.

[0091] As indicated by reference numeral 514, the first UE may send a duplicate transmission of a sidelink transmission on multiple component carriers. The duplicate transmission may be associated with multiple component carriers, where the multiple component carriers may be associated with an L2 destination ID of the sidelink transmission. The first UE may send the duplicate transmission of the sidelink transmission based at least in part on a playout type (e.g., broadcast or multicast) associated with the sidelink transmission and based at least in part on one or more indications received from upper layers. In some aspects, the first UE may send the duplicate transmission of the sidelink transmission via a duplicate indication. The first UE may insert a duplicate indication into the duplicate transmission of the sidelink transmission, where the duplicate indication may indicate the presence of the duplicate transmission.

[0092] In some aspects, the duplicate transmission of the sidelink transmission may be based at least in part on a duplicated MAC PDU. The duplicated MAC PDU may be associated with multiple component carriers, which may be associated with an L2 destination ID. A duplication indication associated with the duplicate transmission may be included in a MAC header or subheader of the duplicate transmission. In some aspects, the duplicate transmission of the sidelink transmission may be based at least in part on a duplicated PDCP packet. The duplicated PDCP packet may be used for multiple logical channels mapped to multiple component carriers associated with an L2 destination ID. A duplication indication associated with the duplicate transmission may be included in a PDCP header of the duplicate transmission.

[0093] As indicated by reference numeral 516, the second UE may monitor sidelink transmissions on a sidelink component carrier associated with the second UE (e.g., sl-cc-list2 including component carrier i). The second UE may not support sidelink carrier aggregation and may receive sidelink transmissions on the component carrier (e.g., component carrier i). The second UE may decode packets received on the component carrier.

[0094] As indicated by reference numeral 518, the third UE may monitor a sidelink transmission on a sidelink component carrier associated with the third UE (e.g., sl-cc-list3 including component carrier 0 to component carrier m). The third UE may support sidelink aggregation and may receive a duplicate transmission of the sidelink transmission on multiple component carriers (e.g., component carrier 0 to component carrier m) from the first UE based at least in part on a playout type associated with the sidelink transmission, one or more indications received from an upper layer of the first UE, and / or the third UE's support for sidelink carrier aggregation. The third UE may determine that the received sidelink transmission is a duplicate transmission based at least in part on the duplication indication. The third UE may remove the duplicate transmission of the sidelink transmission based at least in part on the duplication indication, and the third UE may obtain the sidelink transmission (e.g., a single sidelink transmission).

[0095] As indicated by reference numeral 520, when the second UE fails to decode a sidelink transmission (eg, a packet received from the first UE), the second UE may send a negative acknowledgement (NACK) on a component carrier (eg, component carrier i).

[0096] As shown by reference numeral 522, when the third UE fails to decode all replicated transmissions (e.g., all copies of a packet) of the sidelink transmission received from the first UE, the third UE may send a NACK on a component carrier (e.g., component carrier j of component carrier 0 to component carrier m). The third UE may determine a component carrier for HARQ feedback and use the component carrier to send the NACK accordingly. The first UE may receive HARQ feedback indicating the NACK from the third UE, wherein the HARQ feedback (if enabled) may be based at least in part on the replicated transmissions of the sidelink transmission.

[0097] As indicated by reference numeral 524, the first UE may retransmit a sidelink transmission to the second UE, a duplicate transmission on a component carrier (eg, component carrier i) associated with the component carrier on which the NACK was received from the second UE.

[0098] As indicated by reference numeral 526, the first UE may retransmit to the third UE a sidelink transmission of a duplicate transmission on a component carrier (e.g., component carrier j) associated with the component carrier on which the NACK was received from the third UE. The first UE may retransmit the sidelink transmission on a component carrier among the plurality of component carriers based at least in part on the HARQ feedback.

[0099] In some aspects, the second UE and the third UE may send a NACK to the first UE, and the first UE may retransmit a duplicate transmission of the sidelink transmission based at least in part on the groupcast in which HARQ feedback is enabled.

[0100] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 Different than described.

[0101] Figure 6 is a diagram illustrating an example 600 associated with duplicating sidelink transmissions for sidelink carrier aggregation in accordance with the present disclosure.

[0102] In some aspects, when at least one indication from an upper layer indicates that sidelink carrier aggregation is not supported, the sidelink transmission may be replicated via a MAC PDU on multiple carriers (e.g., some or all carriers) associated with a multicast or broadcast L2 destination ID. A first UE (e.g., a Tx UE) that supports sidelink carrier aggregation may select multiple carriers (e.g., some or all of carriers 0 to carrier m) associated with a multicast or broadcast L2 destination ID, and replicate a transport block (e.g., TB(x)) on the multiple carriers. The first UE may insert a duplication indication (e.g., MACduplicate=1) in a MAC header or subheader. The replicated transport blocks on multiple carriers may correspond to replicated sidelink transmissions. A second UE (e.g., a first Rx UE) that does not support sidelink carrier aggregation may receive a transport block (e.g., TB(x)) on a carrier (e.g., carrier i) associated with the second UE. A third UE (e.g., a second Rx UE) supporting sidelink carrier aggregation may receive transport blocks (e.g., TB(x)) on multiple carriers (e.g., carrier 0 to carrier m), and the third UE may determine to perform duplicate removal based at least in part on a duplicate indication (e.g., MACduplicate=1).

[0103] like Figure 6 As shown, at a first UE (e.g., a Tx UE that may be associated with carriers 0 to m), the MAC layer may be involved in scheduling and priority handling, multiplexing, carrier selection, and HARQ processing. Multiplexing may produce a transport block (e.g., TB(x)), which may be replicated via a MAC PDU or a sub-PDU, which may produce a replicated transport block (e.g., a replicated TB(x) having HARQ entities associated with multiple carriers (e.g., some or all of carriers 0 to m)) for replication. For example, the replicated transport block may include a first transport block associated with a sidelink shared channel (SL-SCH) on carrier 0, a second transport block associated with the SL-SCH on carrier i, and a third transport block associated with the SL-SCH on carrier m. A second UE that does not support sidelink carrier aggregation (e.g., a first Rx UE that may be associated with carrier i) may receive a transport block on a single carrier (e.g., carrier i) associated with the second UE. A third UE supporting sidelink carrier aggregation (e.g., a second Rx UE that may be associated with carriers 0 to carrier m) may receive transport blocks on multiple carriers (e.g., some or all of carriers 0 to carrier m). The third UE may determine to remove the duplicated transport blocks based at least in part on a duplication indication inserted in a MAC header of the duplicated transport blocks, thereby producing a single transport block to which demultiplexing is applied.

[0104] In some aspects, a third UE may determine to send a copy based at least in part on a copy indication in a MAC header or subheader, a logical channel identifier (LCID), and a pair of source identifiers and destination identifiers of duplicated MAC PDUs or MAC sub-PDUs received from multiple carriers. The MAC entity may receive a first MAC PDU or sub-PDU from a first component carrier, the first MAC PDU or sub-PDU including a copy indication in a MAC header or subheader and a first logical channel ID and a first pair of source ID and destination source ID, and may receive a second MAC PDU or sub-PDU from a second component carrier, the second MAC PDU or sub-PDU including a copy indication in a MAC header or subheader and a second logical channel ID and a second pair of source ID and destination source ID. For example, when the MAC entity successfully decodes the first MAC PDU or sub-PDU and when the first logical channel ID is the same as the second logical ID (e.g., the same logical channel instance) and when the first pair of source ID and destination ID is the same as the second pair of source ID and destination ID (e.g., sent from the same UE (source ID) for the same sidelink communication (destination ID)), the MAC entity may deliver the MAC service data unit (SDU) extracted from the first MAC PDU or sub-PDU to the upper layer (e.g., the RLC layer) and discard the second MAC PDU or sub-PDU (e.g., the HARQ entity associated with the second MAC PDU or sub-PDU on the second component carrier may refresh the buffer) and send an ACK on the first component carrier or may not send any NACK on the first component carrier and / or the second component carrier. For example, in a case where the MAC entity unsuccessfully decodes a first MAC PDU or sub PDU and successfully decodes a second MAC PDU or sub PDU and in a case where the first logical channel ID is the same as the second logical ID and in a case where the first pair of source ID and destination ID is the same as the second pair of source ID and destination ID for the same side link communication (destination ID), the MAC entity may deliver the MAC SDU extracted from the second MAC PDU or sub PDU to an upper layer (e.g., an RLC layer) and discard the first MAC PDU or sub PDU (e.g., the HARQ entity associated with the first MAC PDU or sub PDU on the first component carrier may refresh the buffer) and send an ACK on the second component carrier or may not send any NACK on the first component carrier and / or the second component carrier (e.g., if HARQ feedback is enabled).As another example, in a case where the MAC entity unsuccessfully decodes both a first MAC PDU or sub-PDU and a second MAC PDU or sub-PDU and when the first logical channel ID is the same as the second logical ID and when the first pair of source ID and destination ID is the same as the second pair of source ID and destination ID for the same sidelink communication (destination ID), the MAC entity may send a NACK on a first or second component carrier (e.g., when HARQ feedback is enabled), where the first or second component carrier may be randomly selected or may be selected based at least in part on measurements associated with the first and second MAC PDU or sub-PDU (e.g., based at least in part on RSRP or SINR measurements of the PSSCH carrying the first or second MAC PDU or sub-PDU).

[0105] In some aspects, the first UE may determine retransmissions on one or more component carriers based at least in part on receiving an ACK or not receiving a NACK (e.g., where HARQ feedback is enabled). For example, in the case where one or more ACKs are received from all RX UEs for a replicated transmission (e.g., each Rx UE in the group responds with an ACK / NACK for HARQ feedback) or no NACK is received (e.g., the Rx UE responds only with a NACK for HARQ feedback), the MAC entity may determine that there are no retransmissions on any component carrier (e.g., the HARQ entity associated with the replicated transmission on multiple component carriers may flush the buffer and indicate success (e.g., ACK) to the upper layer (if necessary). For example, the MAC entity may determine one or more retransmissions via a HARQ entity associated with a component carrier in which one or more NACKs are received, while other HARQ entities associated with a component carrier in which one or more ACKs are received or no NACKs are received may flush the buffer via a replicated TB. The MAC entity may indicate success (e.g., ACK) to the upper layer (e.g., RLC layer) after receiving one or more ACKs or no NACKs for all retransmissions on the component carriers, or may indicate failure (e.g., NACK) to the upper layer after timeout or reaching the maximum retransmissions allowed for retransmissions on any component carrier corresponding to the duplicated transmission (e.g., as configured).

[0106] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 Different than described.

[0107] Figure 7 is a diagram illustrating an example 700 associated with duplicating sidelink transmissions for sidelink carrier aggregation in accordance with the present disclosure.

[0108] In some aspects, a sidelink transmission may be duplicated at the PDCP layer via a duplicated RLC entity based at least in part on a broadcast type and at least one indication from an upper layer that sidelink carrier aggregation is not supported, wherein the duplicated logical channel is mapped to multiple carriers (e.g., some or all of carriers 0 to carrier m). A first UE (e.g., a Tx UE) that supports sidelink carrier aggregation may duplicate PDCP packets on duplicated logical channels mapped to some or all carriers (e.g., sidelink control channel (SCCH) 0 to SCCH m, or sidelink service channel (STCH) 0 to STCH m), and the first UE may insert a duplication indication (e.g., PDCPduplicate=1 or a PDCP sequence number (SN) without a "0" value) in the PDCP header. The duplicated PDCP packets on the duplicated logical channels mapped to multiple carriers may correspond to the duplicated sidelink transmission. A second UE (e.g., a first Rx UE) that does not support sidelink carrier aggregation may receive PDCP packets on a logical channel mapped to its carrier (e.g., carrier i). A third UE (e.g., a second Rx UE) supporting sidelink carrier aggregation may receive PDCP packets on duplicated logical channels mapped to multiple carriers (e.g., some or all of carrier 0 to carrier m), and the third UE may determine to perform duplicate removal based at least in part on a duplication indication (e.g., PDCPduplicate=1 or PDCPSN).

[0109] like Figure 7As shown, at a first UE (e.g., a Tx UE that may be associated with carrier 0 to carrier m), the PDCP layer may duplicate PDCP packets. PDCP packet duplication may be based at least in part on a quality of service (QoS) flow that may be associated with a PC5 side link (PC5-S) or RRC layer or a service data adaptation protocol (SDAP) layer. The duplicated PDCP packets may also undergo scheduling or priority handling, multiplexing, carrier selection, and HARQ processing. The duplicated PDCP packets may generate duplicated transport blocks (e.g., TB(0), ..., TB(i), ..., TB(m) as shown) that may correspond to multiple carriers (e.g., some or all of carriers 0 to carrier m). A second UE that does not support sidelink carrier aggregation (e.g., a first Rx UE that may be associated with carrier i) may receive a PDCP packet mapped to a logical channel of a single carrier (e.g., carrier i) associated with the second UE, wherein the PDCP packet may be derived from the received transport block (e.g., TB(i)). A third UE supporting sidelink carrier aggregation (e.g., a second Rx UE that may be associated with carriers 0 to carrier m) may receive PDCP packets on duplicated logical channels mapped to multiple carriers (e.g., some or all of carriers 0 to carrier m), wherein the PDCP packets may be derived from received transport blocks (e.g., TB(0) to TB(m)). Before obtaining the PDCP packets, the received transport blocks may be subjected to HARQ processing, packet filtering, and demultiplexing. The third UE may determine to remove the duplicated PDCP packets based at least in part on a duplication indication (e.g., PDCPduplicate=1 or PDCP SN) inserted in a PDCP header of the duplicated PDCP packets, thereby generating a single PDCP packet.

[0110] In some aspects, the third UE may determine to send a copy based at least in part on a copy indication in a PDCP header of the copied PDCP PDU. The PDCP entity may receive a first PDCP PDU from a first copied logical channel via a first copied RLC entity, and may receive a second PDCP PDU from a second copied logical channel via a second copied RLC entity. For example, in the event that the PDCP entity successfully receives a first PDCP PDU with a copy indication, the PDCP entity may deliver a PDCP SDU extracted from the first PDCP PDU to an upper layer (e.g., PC5-S or RRC for a control plane or SDAP for a user plane), discard the second PDCP PDU, and, for an acknowledged mode (AM) data radio bearer (DRB), send a PDCP status report to the first UE with a bitmap field set to '1' for the first PDCP SDU. For example, in the case where the PDCP entity does not successfully receive the first PDCP PDU and successfully receives the second PDCP PDU, the PDCP entity may deliver the PDCP SDU extracted from the second PDCP PDU to the upper layer, discard the first PDCP PDU, and, for the AM DRB, send a PDCP status report to the first UE with a bitmap field set to '1' for the second PDCP SDU. As another example, in the case where the PDCP entity does not successfully receive both the first PDCP PDU and the second PDCP PDU, the PDCP entity may not deliver any PDCP SDU to the upper layer, and, for the AM DRB, may send a PDCP status report to the first UE with a bitmap field set to '0' for the first and second PDCP SDUs, respectively.

[0111] In some aspects, for an AM DRB configured by an upper layer, the first UE may determine retransmissions on one or more component carriers based at least in part on a received PDCP status report. For example, the PDCP entity may determine duplication of retransmissions based at least in part on a PDCP status report received from an Rx UE, wherein each PDCP status report includes a bitmap "0" or "1" corresponding to a PDCP SDU that has been duplicated and sent. For example, where a bitmap "0" for a first PDCP SDU is associated with a first duplicated logical channel mapped to a first component carrier and a bitmap "0" for a second PDCP SDU is associated with a second duplicated logical channel mapped to a second component carrier (e.g., logical channel i and logical channel j mapped to component carrier i and component carrier j, respectively), the PDCP entity may determine duplication of retransmissions on a first duplicated logical channel and a second duplicated logical channel corresponding to the first component carrier and the second component carrier (e.g., logical channel i and logical channel j mapped to component carrier i and component carrier j, respectively).

[0112] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 Different than described.

[0113] In some aspects, the indication from the upper layer may indicate support or non-support of sidelink carrier aggregation. For example, in the case where one or more indications indicate support for sidelink carrier aggregation (e.g., indicating "SL-CA"), transmission duplication is not applied. The first UE may select any component carrier for sending TB (e.g., any component carrier of carrier 0 to carrier m), and the third UE may monitor all component carriers used for TB transmission (e.g., all carriers on sl-cc-list3). For example, in the case where at least one indication indicates that sidelink carrier aggregation is not supported (e.g., indicating "No-SL-CA"), the first UE or the third UE may determine transmission duplication on multiple carriers for sending TB (e.g., some or all of carrier 0 to carrier m), and the third UE may monitor multiple carriers for duplication or all component carriers for TB transmission. In some aspects, the multiple carriers may be determined by the first UE and / or the third UE at least in part based on one or more carriers indicated from an upper layer with an indication of "No-SL-CA" (e.g., carrier i associated to service i or service type i that does not support sidelink carrier aggregation and carrier j associated to service j or service type j that does not support sidelink carrier aggregation, where carrier i and carrier j are within an sl-cc-list including carrier 0 to carrier m (0≤i, j≤m)). In some aspects, the multiple carriers may be determined by the first UE and / or the third UE at least in part based on a sidelink component carrier list for duplication (e.g., sl-cc-duplicate-list) that is preconfigured or configured at least in part based on a mapping between supported component carriers and services or service types that do not support sidelink carrier aggregation.

[0114] Figure 8 is a diagram illustrating an example process 800 performed, for example, by a first UE in accordance with the present disclosure. Example process 800 is an example in which a first UE (eg, UE 120a) performs operations associated with duplicating sidelink transmissions for sidelink carrier aggregation.

[0115] like Figure 8 As shown, in some aspects, process 800 may include transmitting a replicated transmission of the sidelink transmission on multiple component carriers to a second UE based at least in part on a playout type associated with the sidelink transmission and one or more indications received from upper layers of the first UE, wherein the replicated transmission is associated with multiple component carriers associated with an L2 destination ID of the sidelink transmission (block 810). For example, a first UE (e.g., using Fig.10The communication manager 140 and / or the sending component 1004 depicted in FIG. 1 may send a duplicate transmission of the sidelink transmission on multiple component carriers to the second UE based at least in part on the playout type associated with the sidelink transmission and one or more indications received from the upper layer of the first UE, wherein the duplicate transmission is associated with the multiple component carriers associated with the L2 destination ID of the sidelink transmission, as described above. The second UE may correspond to a third UE, such as in conjunction with Figures 5 to 7 as described.

[0116] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0117] In a first aspect, the one or more indications from the upper layer indicate support or non-support of sidelink carrier aggregation for the L2 destination ID for the sidelink transmission.

[0118] In a second aspect, alone or in combination with the first aspect, the playout type is multicast or broadcast, and the L2 destination ID sent by the sidelink is of the multicast or the broadcast.

[0119] In a third aspect, alone or in combination with one or more of the first and second aspects, process 800 includes receiving, from a network node or a special UE, a configuration of a sidelink component carrier list for the sidelink transmission associated to the L2 destination ID, wherein the plurality of component carriers are derived from the sidelink component carrier list.

[0120] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 800 includes determining to replicate the sidelink transmission on the multiple component carriers based at least in part on at least one indication of the one or more indications from the upper layer indicating that sidelink carrier aggregation is not supported.

[0121] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 800 includes sending a copy indication indicating the existence of the copied transmission.

[0122] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the replicated transmission of the side link transmission is based at least in part on a replicated MAC PDU, wherein the replicated MAC PDU is associated with the multiple component carriers associated with the L2 destination ID, and a replication indication associated with the replicated transmission is in a MAC header of the replicated transmission.

[0123] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the replicated transmission of the sidelink transmission is based at least in part on a replicated PDCP packet, wherein the replicated PDCP packet is used for multiple logical channels mapped to the multiple component carriers associated with the L2 destination ID, and a replication indication associated with the replicated transmission is in a PDCP header of the replicated transmission.

[0124] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 800 includes: receiving HARQ feedback of the replicated transmission based at least in part on the sidelink transmission from the second UE; and retransmitting the sidelink transmission on a component carrier among the multiple component carriers to the second UE based at least in part on the HARQ feedback.

[0125] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, an indication of the one or more indications corresponds to a Tx profile, and the Tx profile is associated with a V2X or ProSe service identifier.

[0126] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 800. Additionally or alternatively, two or more blocks of the blocks of process 800 may be performed in parallel.

[0127] Fig. 9 900 is a diagram illustrating an example process 900 performed, for example, by a second UE according to the present disclosure. Example process 900 is an example in which a second UE (e.g., UE 120e) performs operations associated with duplicating sidelink transmissions for sidelink carrier aggregation. The second UE may correspond to a third UE, such as in conjunction with Figures 5 to 7 as described.

[0128] like Fig. 9 As shown in , in some aspects, process 900 may include receiving a replicated transmission of a sidelink transmission on multiple component carriers from a first UE based at least in part on: a playout type associated with the sidelink transmission, and one or more indications received from upper layers of a second UE, and the one or more indications support sidelink carrier aggregation, wherein the replicated transmission is associated with multiple component carriers associated with an L2 destination ID of the sidelink transmission (block 910). For example, the second UE (e.g., using Fig.11The communication manager 150 and / or receiving component 1102 depicted in the figure may receive a replicated transmission of a sidelink transmission on multiple component carriers from a first UE based at least in part on: a broadcast type associated with the sidelink transmission, and one or more indications received from upper layers of a second UE, and the one or more indications support sidelink carrier aggregation, wherein the replicated transmission is associated with multiple component carriers associated with an L2 destination ID of the sidelink transmission, as described above.

[0129] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0130] In a first aspect, process 900 includes receiving, with the duplicate transmission having the sidelink transmission, a duplicate indication indicating the presence of the duplicate transmission; and removing the duplicate transmission based at least in part on the duplicate indication.

[0131] In a second aspect, either alone or in combination with the first aspect, the replicated transmission of the sidelink transmission is based at least in part on a replicated MAC PDU, wherein the replicated MAC PDU is associated with the multiple component carriers associated with the L2 destination ID, and a replication indication associated with the replicated transmission is in a MAC header of the replicated transmission.

[0132] In a third aspect, either alone or in combination with one or more of the first and second aspects, the replicated transmission of the sidelink transmission is based at least in part on a replicated PDCP packet, wherein the replicated PDCP packet is used for multiple logical channels mapped to the multiple component carriers associated with the L2 destination ID, and a replication indication associated with the replicated transmission is in a PDCP header of the replicated transmission.

[0133] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 900 includes: sending HARQ feedback of the replicated transmission based at least in part on the sidelink transmission to the first UE; and receiving a retransmission of the sidelink transmission on a component carrier among the multiple component carriers from the first UE based at least in part on the HARQ feedback.

[0134] although Fig. 9 An example block diagram of process 900 is shown, but in some aspects, process 900 may include Fig. 9 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 900. Additionally or alternatively, two or more blocks of the blocks of process 900 may be performed in parallel.

[0135] Fig.101 is a diagram of an example apparatus 1000 for wireless communication according to the present disclosure. Apparatus 1000 may be a first UE, or the first UE may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using receiving component 1002 and transmitting component 1004. As further shown, apparatus 1000 may include a communication manager 140. Communication manager 140 may include determining component 1008, etc.

[0136] In some aspects, the apparatus 1000 may be configured to perform Figures 5 to 7 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 8 In some aspects, the apparatus 1000 and / or Fig.10 One or more of the components shown may include a combination of Figure 2 Additionally or alternatively, Fig.10 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0137] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1006. The receiving component 1002 may provide the received communications to one or more other components of the device 1000. In some aspects, the receiving component 1002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1000. In some aspects, the receiving component 1002 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described first UE.

[0138] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1006. In some aspects, one or more other components of the device 1000 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1006. In some aspects, the transmitting component 1004 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described first UE. In some aspects, the transmit component 1004 can be co-located with the receive component 1002 in a transceiver.

[0139] The transmitting component 1004 may transmit a replicated transmission of the sidelink transmission on multiple component carriers to the second UE based at least in part on the broadcast type associated with the sidelink transmission and one or more indications received from upper layers of the first UE, wherein the replicated transmission is associated with multiple component carriers associated with the L2 destination ID of the sidelink transmission.

[0140] The receiving component 1002 may receive a configuration of a sidelink component carrier list for sidelink transmission associated to an L2 destination ID from a network node or a special UE, wherein the plurality of component carriers are derived from the sidelink component carrier list. The determining component 1008 may determine to replicate the sidelink transmission on the plurality of component carriers based at least in part on at least one indication from one or more indications from an upper layer indicating that sidelink carrier aggregation is not supported. The receiving component 1002 may receive HARQ feedback based at least in part on the replicated transmission of the sidelink transmission from the second UE. The transmitting component 1004 may retransmit the sidelink transmission on a component carrier of the plurality of component carriers to the second UE based at least in part on the HARQ feedback.

[0141] Fig.10 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.10 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.10 Two or more components shown may be implemented in a single component, or Fig.10 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.10 The component set (one or more components) shown may be described as being executable by Fig.10 Another component shown may be a collection of components that perform one or more functions.

[0142] Fig.11 1 is a diagram of an example apparatus 1100 for wireless communication according to the present disclosure. Apparatus 1100 may be a second UE, or the second UE may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a sending component 1104, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using receiving component 1102 and sending component 1104. As further shown, apparatus 1100 may include a communication manager 150. Communication manager 150 may include removal component 1108, etc.

[0143] In some aspects, the apparatus 1100 may be configured to perform Figures 5 to 7 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Fig. 9 In some aspects, the apparatus 1100 and / or Fig.11 One or more of the components shown may include a combination of Figure 2 One or more components of the second UE. Additionally or alternatively, Fig.11 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0144] The receiving component 1102 may receive communications from the device 1106, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the second UE.

[0145] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1106. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1106. In some aspects, the transmitting component 1104 may include a combination of Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the second UE. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0146] Receiving component 1102 may receive a replicated transmission of a sidelink transmission on multiple component carriers from a first UE based at least in part on: a broadcast type associated with the sidelink transmission, and one or more indications received from upper layers of a second UE, and the one or more indications support sidelink carrier aggregation, wherein the replicated transmission is associated with multiple component carriers associated with an L2 destination ID of the sidelink transmission.

[0147] The receiving component 1102 may receive a duplication indication in the presence of a duplicate transmission of the sidelink transmission, the duplication indication indicating the presence of the duplicate transmission. The removing component 1108 may remove the duplicate transmission based at least in part on the duplication indication. The sending component 1104 may send HARQ feedback based at least in part on the duplicate transmission of the sidelink transmission to the first UE. The receiving component 1102 may receive a retransmission of the sidelink transmission on a component carrier of the plurality of component carriers from the first UE based at least in part on the HARQ feedback.

[0148] Fig.11 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.11 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.11 Two or more components shown may be implemented in a single component, or Fig.11 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.11 The component set (one or more components) shown may be described as being executable by Fig.11 Another component shown may be a collection of components that perform one or more functions.

[0149] The following provides an overview of some aspects of the disclosure:

[0150] Aspect 1: A method of wireless communication performed by a first user equipment (UE), comprising: sending a duplicate transmission of the sidelink transmission on multiple component carriers to a second UE based at least in part on a broadcast type associated with the sidelink transmission and one or more indications received from an upper layer of the first UE, wherein the duplicate transmission is associated with the multiple component carriers associated with a layer 2 (L2) destination identifier (ID) of the sidelink transmission.

[0151] Aspect 2: The method according to aspect 1, wherein the one or more indications from the upper layer indicate support or non-support of sidelink carrier aggregation for the L2 destination ID used for the sidelink transmission.

[0152] Aspect 3: The method according to any one of aspects 1 to 2, wherein the playout type is multicast or broadcast, and wherein the L2 destination ID sent by the sidelink is the multicast or the broadcast.

[0153] Aspect 4: The method according to any one of Aspects 1 to 3 further includes: receiving a configuration of a sidelink component carrier list for the sidelink transmission associated to the L2 destination ID from a network node or a special UE, wherein the multiple component carriers are derived from the sidelink component carrier list.

[0154] Aspect 5: The method according to any one of Aspects 1 to 4 further includes: determining to replicate the sidelink transmission on the multiple component carriers based at least in part on at least one indication among the one or more indications from the upper layer indicating that sidelink carrier aggregation is not supported.

[0155] Aspect 6: The method according to any one of aspects 1 to 5, wherein sending the duplicate transmission of the sidelink transmission includes sending a duplication indication indicating the presence of the duplicate transmission.

[0156] Aspect 7: A method according to any one of Aspects 1 to 6, wherein the replicated transmission of the sidelink transmission is at least partially based on a replicated medium access control (MAC) protocol data unit (PDU), wherein the replicated MAC PDU is associated with the multiple component carriers associated with the L2 destination ID, and wherein the replication indication associated with the replicated transmission is in the MAC header of the replicated transmission.

[0157] Aspect 8: A method according to any one of Aspects 1 to 7, wherein the replicated transmission of the sidelink transmission is at least partially based on a replicated Packet Data Convergence Protocol (PDCP) packet, wherein the replicated PDCP packet is used for multiple logical channels mapped to the multiple component carriers associated with the L2 destination ID, and wherein the replication indication associated with the replicated transmission is in the PDCP header of the replicated transmission.

[0158] Aspect 9: The method according to any one of Aspects 1 to 8 further includes: receiving hybrid automatic repeat request (HARQ) feedback of the copied transmission from the second UE based at least in part on the sidelink transmission; and retransmitting the sidelink transmission on a component carrier among the multiple component carriers to the second UE based at least in part on the HARQ feedback.

[0159] Aspect 10: The method according to any one of aspects 1 to 9, wherein an indication of the one or more indications corresponds to a transmission (Tx) profile, and wherein the Tx profile is associated with a connected vehicle or proximity service service identifier.

[0160] Aspect 11: A method of wireless communication performed by a second user equipment (UE), comprising: receiving a replicated transmission of a sidelink transmission on multiple component carriers from a first UE based at least in part on: a broadcast type associated with the sidelink transmission, and one or more indications received from an upper layer of the second UE, and the one or more indications support sidelink carrier aggregation, wherein the replicated transmission is associated with the multiple component carriers associated with a layer 2 (L2) destination identifier (ID) of the sidelink transmission.

[0161] Aspect 12: The method according to Aspect 11 also includes: receiving a duplication indication in the case of the duplicate transmission having the side link transmission, the duplication indication indicating the existence of the duplicate transmission; and removing the duplicate transmission based at least in part on the duplication indication.

[0162] Aspect 13: A method according to any one of Aspects 11 to 12, wherein the replicated transmission of the sidelink transmission is at least partially based on a replicated medium access control (MAC) protocol data unit (PDU), wherein the replicated MAC PDU is associated with the multiple component carriers associated with the L2 destination ID, and wherein the replication indication associated with the replicated transmission is in the MAC header of the replicated transmission.

[0163] Aspect 14: A method according to any one of Aspects 11 to 13, wherein the replicated transmission of the sidelink transmission is at least partially based on a replicated Packet Data Convergence Protocol (PDCP) packet, wherein the replicated PDCP packet is used for multiple logical channels mapped to the multiple component carriers associated with the L2 destination ID, and wherein the replication indication associated with the replicated transmission is in the PDCP header of the replicated transmission.

[0164] Aspect 15: The method according to any one of Aspects 11 to 14 further includes: sending a hybrid automatic repeat request (HARQ) feedback of the copied transmission sent by the sidelink to the first UE at least partially based on; and receiving a retransmission of the sidelink transmission on a component carrier among the multiple component carriers from the first UE at least partially based on the HARQ feedback.

[0165] Aspect 16: An apparatus for performing wireless communications at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 15.

[0166] Aspect 17: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 15.

[0167] Aspect 18: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 1 to 15.

[0168] Aspect 19: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 15.

[0169] Aspect 20: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 15.

[0170] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0171] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0172] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0173] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0174] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly stated. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. An apparatus for wireless communication at a first user equipment (UE), comprising: Memory; and one or more processors coupled to the memory and configured to: Sending a duplicate transmission of the sidelink transmission on multiple component carriers to a second UE based at least in part on a playout type associated with the sidelink transmission and one or more indications received from an upper layer of the first UE, wherein the duplicate transmission is associated with the multiple component carriers associated with a layer 2 (L2) destination identifier (ID) of the sidelink transmission.

2. The apparatus of claim 1, wherein the one or more indications from the upper layer indicate support or non-support of sidelink carrier aggregation for the L2 destination ID for the sidelink transmission.

3. The apparatus of claim 1, wherein the playout type is multicast or broadcast, and wherein the L2 destination ID sent by the sidelink is of the multicast or the broadcast.

4. The apparatus of claim 1 , wherein the one or more processors are further configured to: A configuration of a sidelink component carrier list configured for the sidelink transmission associated to the L2 destination ID is received from a network node or a special UE, wherein the plurality of component carriers are derived from the sidelink component carrier list.

5. The apparatus of claim 1 , wherein the one or more processors are further configured to: The determination to replicate the sidelink transmission on the plurality of component carriers is based at least in part on at least one indication of the one or more indications from the upper layer indicating that sidelink carrier aggregation is not supported.

6. The apparatus of claim 1, wherein, in order to transmit the duplicate transmission of the sidelink transmission, the one or more processors are configured to transmit a duplication indication indicating the presence of the duplicate transmission.

7. An apparatus according to claim 1, wherein the replicated transmission of the sidelink transmission is based at least in part on a replicated medium access control (MAC) protocol data unit (PDU), wherein the replicated MAC PDU is associated with the multiple component carriers associated with the L2 destination ID, and wherein the replication indication associated with the replicated transmission is in a MAC header of the replicated transmission.

8. An apparatus according to claim 1, wherein the replicated transmission of the sidelink transmission is based at least in part on a replicated Packet Data Convergence Protocol (PDCP) packet, wherein the replicated PDCP packet is used for multiple logical channels mapped to the multiple component carriers associated with the L2 destination ID, and wherein a replication indication associated with the replicated transmission is in a PDCP header of the replicated transmission.

9. The apparatus of claim 1, wherein the one or more processors are further configured to: receiving, from the second UE, hybrid automatic repeat request (HARQ) feedback based at least in part on the replicated transmission of the sidelink transmission; and The sidelink transmission on a component carrier of the plurality of component carriers is retransmitted to the second UE based at least in part on the HARQ feedback.

10. The apparatus of claim 1, wherein an indication of the one or more indications corresponds to a transmit (Tx) profile, and wherein the Tx profile is associated with a connected vehicle or proximity service service identifier.

11. An apparatus for wireless communication at a second user equipment (UE), comprising: Memory; and one or more processors coupled to the memory and configured to: Receiving a sidelink transmission from the first UE and transmitting a replicated transmission on the multiple component carriers based at least in part on: a playout type associated with the sidelink transmission, and One or more indications received from an upper layer of the second UE, and the one or more indications support sidelink carrier aggregation, The replicated transmission is associated with the plurality of component carriers associated with a layer 2 (L2) destination identifier (ID) of the sidelink transmission.

12. The apparatus of claim 11, wherein the one or more processors are further configured to: receiving, in the case of the duplicated transmission with the sidelink transmission, a duplication indication indicating the presence of the duplicated transmission; and The duplicated transmission is removed based at least in part on the duplicate indication.

13. An apparatus according to claim 11, wherein the duplicate transmission of the sidelink transmission is based at least in part on a duplicated medium access control (MAC) protocol data unit (PDU), wherein the duplicated MAC PDU is associated with the multiple component carriers associated with the L2 destination ID, and wherein the duplication indication associated with the duplicate transmission is in a MAC header of the duplicate transmission.

14. An apparatus according to claim 11, wherein the replicated transmission of the sidelink transmission is based at least in part on a replicated Packet Data Convergence Protocol (PDCP) packet, wherein the replicated PDCP packet is used for multiple logical channels mapped to the multiple component carriers associated with the L2 destination ID, and wherein the replication indication associated with the replicated transmission is in a PDCP header of the replicated transmission.

15. The apparatus of claim 11, wherein the one or more processors are further configured to: transmitting, to the first UE, hybrid automatic repeat request (HARQ) feedback based at least in part on the replicated transmission of the sidelink transmission; and A retransmission of the sidelink transmission on a component carrier of the plurality of component carriers is received from the first UE based at least in part on the HARQ feedback.

16. A method of wireless communication performed by a first user equipment (UE), comprising: Sending a duplicate transmission of the sidelink transmission on multiple component carriers to a second UE based at least in part on a playout type associated with the sidelink transmission and one or more indications received from an upper layer of the first UE, wherein the duplicate transmission is associated with the multiple component carriers associated with a layer 2 (L2) destination identifier (ID) of the sidelink transmission.

17. The method of claim 16, wherein the one or more indications from the upper layer indicate support or non-support of sidelink carrier aggregation for the L2 destination ID for the sidelink transmission.

18. The method of claim 16, wherein the playout type is multicast or broadcast, and wherein the L2 destination ID sent by the sidelink is of the multicast or the broadcast.

19. The method according to claim 16, further comprising: A configuration of a sidelink component carrier list configured for the sidelink transmission associated to the L2 destination ID is received from a network node or a special UE, wherein the plurality of component carriers are derived from the sidelink component carrier list.

20. The method of claim 16, further comprising: The determination to replicate the sidelink transmission on the plurality of component carriers is based at least in part on at least one indication of the one or more indications from the upper layer indicating that sidelink carrier aggregation is not supported.

21. The method of claim 16, wherein sending the duplicate transmission of the sidelink transmission comprises sending a duplication indication indicating the presence of the duplicate transmission.

22. The method of claim 16, wherein the replicated transmission of the sidelink transmission is based at least in part on a replicated medium access control (MAC) protocol data unit (PDU), wherein the replicated MAC PDU is associated with the multiple component carriers associated with the L2 destination ID, and wherein a replication indication associated with the replicated transmission is in a MAC header of the replicated transmission.

23. A method according to claim 16, wherein the replicated transmission of the sidelink transmission is at least partially based on a replicated Packet Data Convergence Protocol (PDCP) packet, wherein the replicated PDCP packet is used for multiple logical channels mapped to the multiple component carriers associated with the L2 destination ID, and wherein the replication indication associated with the replicated transmission is in the PDCP header of the replicated transmission.

24. The method of claim 16, further comprising: receiving, from the second UE, hybrid automatic repeat request (HARQ) feedback based at least in part on the replicated transmission of the sidelink transmission; as well as The sidelink transmission on a component carrier of the plurality of component carriers is retransmitted to the second UE based at least in part on the HARQ feedback.

25. The method of claim 16, wherein an indication of the one or more indications corresponds to a transmit (Tx) profile, and wherein the Tx profile is associated with a connected vehicle or proximity service service identifier.

26. A method of wireless communication performed by a second user equipment (UE), comprising: Receiving a sidelink transmission from the first UE and transmitting a replicated transmission on the multiple component carriers based at least in part on: a playout type associated with the sidelink transmission, One or more indications received from an upper layer of the second UE, and the one or more indications support sidelink carrier aggregation, The replicated transmission is associated with the plurality of component carriers associated with a layer 2 (L2) destination identifier (ID) of the sidelink transmission.

27. The method according to claim 26, further comprising: receiving, in the case of the duplicated transmission with the sidelink transmission, a duplication indication indicating the presence of the duplicated transmission; as well as The duplicated transmission is removed based at least in part on the duplicate indication.

28. A method according to claim 26, wherein the replicated transmission of the sidelink transmission is based at least in part on a replicated medium access control (MAC) protocol data unit (PDU), wherein the replicated MAC PDU is associated with the multiple component carriers associated with the L2 destination ID, and wherein the replication indication associated with the replicated transmission is in a MAC header of the replicated transmission.

29. A method according to claim 26, wherein the replicated transmission of the sidelink transmission is at least partially based on a replicated Packet Data Convergence Protocol (PDCP) packet, wherein the replicated PDCP packet is used for multiple logical channels mapped to the multiple component carriers associated with the L2 destination ID, and wherein the replication indication associated with the replicated transmission is in the PDCP header of the replicated transmission.

30. The method of claim 26, further comprising: sending, to the first UE, hybrid automatic repeat request (HARQ) feedback based at least in part on the replicated transmission of the sidelink transmission; as well as A retransmission of the sidelink transmission on a component carrier of the plurality of component carriers is received from the first UE based at least in part on the HARQ feedback.

Images