Sidelink carrier aggregation

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may send, to a network node, a first indication of at least one of whether sidelink carrier aggregation or a first one or more component carriers associated with sidelink communication is supported, the first indication associated with the sidelink communication. The UE may receive, based on transmitting the indication, a second indication from the network node that a transmission associated with the sidelink communication will be repeated for a plurality of component carriers. The UE may transmit the sidelink communication via each of a plurality of component carriers based on the second indication, the plurality of component carriers including at least one component carrier of the first one or more component carriers. Numerous other aspects are provided.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. patent application No. 17 / 810,810, filed on July 5, 2022, entitled “SIDELINK CARRIER AGGREGATION,” which is hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and particularly to techniques and apparatus 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 or transmit power). 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] The above 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 or global level. The 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 better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink, using CP-OFDM 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 to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful.

[0006] Carrier aggregation is a technology that enables two or more component carriers (CCs, sometimes referred to as carriers) to be combined (e.g., combined into a single channel) for a single user equipment (UE) to enhance data capacity. In some examples, the UE may be configured to perform carrier aggregation for sidelink communications. In some examples, the UE may perform carrier aggregation for sidelink communications in sidelink mode 1 (e.g., where scheduling and resource allocation are performed by a network node). Configuration parameters for sidelink communications over a PC5 interface may be based at least in part on mapping rules. The mapping rules may involve mappings between one or more service identifiers (e.g., service types) and layer 2 (L2) destination identifiers for broadcast or multicast communications, or mappings between one or more service identifiers and sidelink frequencies associated with a geographic area. Thus, an L2 destination identifier for multicast or broadcast communications may be associated with multiple services (e.g., multiple sidelink service types), each of which may be mapped to a different frequency carrier in a geographic area. For example, some services associated with the L2 destination identifier may support legacy UEs (e.g., UEs operating in accordance with Release 16 or 17 of the 3GPP technical specifications) that do not support sidelink carrier aggregation, and other services associated with the L2 destination identifier may support new UEs (e.g., UEs operating in accordance with Release 18 or higher of the 3GPP technical specifications) that support sidelink carrier aggregation.

[0007] For a multicast or broadcast communication associated with an L2 destination identifier, packets sent on a component carrier selected for or by a UE supporting sidelink carrier aggregation may not be received by a UE that does not support sidelink carrier aggregation when the selected carrier is not used or supported by a UE that does not support sidelink carrier aggregation. As another example, some UEs may be associated with reduced capabilities. For example, due to reduced or limited capabilities of some UEs, these UEs may not be able to support all frequency carriers associated with a given L2 destination identifier. Therefore, if the selected carrier for the transmission of a multicast or broadcast communication associated with an L2 destination identifier is not supported by a UE with reduced capabilities, the UE with reduced capabilities may not be able to receive the multicast or broadcast communication.

[0008] In other words, a first UE that supports sidelink carrier aggregation may be scheduled to use one or more component carriers in a component carrier set to send a multicast or broadcast communication associated with an L2 destination identifier. A second UE that does not support sidelink carrier aggregation may be configured to use a single component carrier (e.g., the single component carrier is included in the component carrier set) to receive sidelink communications. However, if the network node or the first UE does not select a single component carrier for the transmission of the groupcast or broadcast communication, the second UE may not receive the groupcast or broadcast communication. Because the first UE or the network node may not be aware of the second UE's capabilities related to sidelink carrier aggregation, the first UE or the network node may not select a component carrier used by the second UE. Therefore, backward compatibility issues may arise for sidelink carrier aggregation. Summary of the invention

[0009] Some aspects described herein relate to a UE for wireless communication. The user equipment may include at least one memory and at least one processor, the at least one processor being communicatively coupled to the at least one memory. The at least one processor may be configured to cause the UE to send a first indication of at least one of the following to a network node: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with the sidelink communication, the first indication being associated with the sidelink communication. The at least one processor may be configured to cause the UE to receive, based on sending the indication, a second indication from the network node that the transmission associated with the sidelink communication will be repeated for multiple component carriers. The at least one processor may be configured to cause the UE to send the sidelink communication via each of a plurality of component carriers based on the second indication, the plurality of component carriers including at least one of the first one or more component carriers.

[0010] Some aspects described herein relate to a network node for wireless communication. The network node may include at least one memory and at least one processor, the at least one processor being communicatively coupled to the at least one memory. The at least one processor may be configured to cause the network node to receive one or more indications of at least one of the following: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with a sidelink communication, the one or more indications being associated with the sidelink communication and one or more UEs. The at least one processor may be configured to cause the network node to send a communication to a UE in the one or more UEs, the communication indicating that the transmission associated with the sidelink communication will be repeated for multiple component carriers, the multiple component carriers including at least one component carrier in the first one or more component carriers.

[0011] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include: sending a first indication to a network node of at least one of: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with a sidelink communication, the first indication being associated with the sidelink communication. The method may include: based on sending the indication, receiving a second indication from the network node that the transmission associated with the sidelink communication will be repeated for multiple component carriers. The method may include: based on the second indication, sending the sidelink communication via each of a plurality of component carriers, the plurality of component carriers including at least one of the first one or more component carriers.

[0012] Some aspects described herein relate to a method of wireless communications performed by a network node. The method may include receiving one or more indications of at least one of: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with a sidelink communication, the one or more indications being associated with the sidelink communication and one or more UEs. The method may include sending a communication to a UE of the one or more UEs, the communication indicating that the transmission associated with the sidelink communication is to be repeated for a plurality of component carriers, the plurality of component carriers including at least one component carrier of the first one or more component carriers.

[0013] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to send a first indication of at least one of the following to a network node: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with the sidelink communication, the first indication being associated with the sidelink communication. The instruction set, when executed by one or more processors of the UE, may cause the UE, based on sending the indication, to receive from the network node a second indication that the transmission associated with the sidelink communication will be repeated for multiple component carriers. The instruction set, when executed by one or more processors of the UE, may cause the UE, based on the second indication, to send the sidelink communication via each of a plurality of component carriers, the plurality of component carriers including at least one of the first one or more component carriers.

[0014] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to receive one or more indications of at least one of the following: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with a sidelink communication, the one or more indications being associated with the sidelink communication and one or more UEs. The instruction set, when executed by one or more processors of the network node, may cause the network node to send a communication to a UE in the one or more UEs, the communication indicating that the transmission associated with the sidelink communication is to be repeated for multiple component carriers, the multiple component carriers including at least one component carrier in the first one or more component carriers.

[0015] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a first indication to a network node of at least one of whether sidelink carrier aggregation is supported or a first one or more component carriers associated with the sidelink communication, the first indication being associated with the sidelink communication. The apparatus may include means for receiving, based on sending the indication, from the network node a second indication that transmission associated with the sidelink communication will be repeated for multiple component carriers. The apparatus may include means for sending the sidelink communication via each of a plurality of component carriers, including at least one of the first one or more component carriers, based on the second indication.

[0016] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving one or more indications of at least one of: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with a sidelink communication, the one or more indications being associated with the sidelink communication and one or more UEs. The apparatus may include means for sending a communication to a UE of the one or more UEs, the communication indicating that the transmission associated with the sidelink communication is to be repeated for a plurality of component carriers, the plurality of component carriers including at least one component carrier of the first one or more component carriers.

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

[0018] The foregoing has broadly outlined the features and technical advantages of examples according to the present disclosure in an effort to make the following specific embodiments better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples can be easily used as the basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages will be better understood according to the following description. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to fully understand the above 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 some typical aspects of the present disclosure and should not be considered to limit its scope, as the description may allow for other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

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

[0021] Figure 2 is a diagram illustrating an example network node communicating with a user equipment (UE) in a wireless network according to the present disclosure.

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

[0023] Figure 4 is a diagram illustrating an example of side link communication according to the present disclosure.

[0024] Figure 5 is a diagram illustrating an example of side link communication and access link communication according to the present disclosure.

[0025] Figure 6 is a diagram illustrating an example of carrier aggregation according to the present disclosure.

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

[0027] Figure 8 is a diagram of an example associated with sidelink carrier aggregation according to the present disclosure.

[0028] Fig. 9 is a diagram illustrating an example associated with repeating sidelink transmission for sidelink carrier aggregation according to the present disclosure.

[0029] Fig.10 is a diagram illustrating an example associated with repeating sidelink transmission for sidelink carrier aggregation according to the present disclosure.

[0030] Fig.11 is a flow chart illustrating an example process associated with sidelink carrier aggregation, for example, performed by a UE according to the present disclosure.

[0031] Fig.12 is a flow chart illustrating an example process associated with sidelink carrier aggregation, for example, performed by a network node, according to the present disclosure.

[0032] Fig.13 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0033] Fig.14 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0034] 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 interpreted as being limited to any specific structure or function given 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 will be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, the aspect of any amount 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 devices or methods implemented using other structures, functionality, or structures and functionality in addition to or different from the various aspects of the disclosure set forth herein. Any aspect of the present disclosure disclosed herein may be embodied by one or more elements of a claim.

[0035] 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, or algorithms (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination of hardware and software. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0036] Various aspects generally relate to sidelink carrier aggregation. Some aspects more specifically relate to a user equipment (UE) sending an indication to a network node of at least one of: 1) whether sidelink carrier aggregation is supported (e.g., for sidelink communications or for sidelink services or service types); or 2) one or more component carriers associated with sidelink communications (e.g., one or more component carriers supported by the UE). As used herein, "sidelink communications" may refer to one or more sidelink packets or information associated with a given layer 2 (L2) destination identifier.

[0037] The sidelink communication may be repeated based at least in part on a broadcast type (e.g., broadcast or multicast) and one or more indications obtained by the UE from an upper layer (e.g., an application layer). One or more indications from the upper layer may indicate whether each service type supports or does not support sidelink carrier aggregation for an L2 destination identifier associated with the sidelink communication. For example, the upper layer may indicate to the access stratum (AS) layer multiple transmission (Tx) profiles associated with the L2 destination identifier (e.g., each transmission profile indicates at least one of the following: 1) whether sidelink carrier aggregation is supported, or 2) one or more associated component carriers for sidelink communication). Alternatively, the upper layer may indicate to the AS layer only one Tx profile associated with the L2 destination identifier (again, for example, indicating at least one of the following: 1) whether sidelink carrier aggregation is supported, or 2) one or more associated component carriers for sidelink communication). The UE may send an indication to the network node based at least in part on one or more indications obtained from the upper layer (e.g., to indicate 1) whether sidelink carrier aggregation is supported; or 2) one or more component carriers associated with the sidelink communication).

[0038] In some aspects, to support backward compatibility for a sidelink carrier aggregation feature (e.g., which may be supported by some UEs and not by other UEs), sidelink communications may be repeated on multiple component carriers. Knowledge of the UE's capabilities for sidelink carrier aggregation or knowledge of one or more component carriers supported by the UE for sidelink communications may enable a network node (e.g., for sidelink mode 1 scheduling) to determine whether to repeat sidelink communications (e.g., associated with a given L2 destination identifier) ​​on multiple component carriers. For example, the network node may determine that the sidelink communications are to be repeated on multiple component carriers based at least in part on the mutual exclusion of a first one or more component carriers (e.g., supported by a first UE or a first service type associated with the sidelink communications) and a second one or more component carriers (e.g., supported by a second UE or a second service type associated with the sidelink communications) (e.g., based on the first one or more component carriers and the second one or more component carriers not including a common component carrier). In some aspects, the network node may send an indication to the first UE that a transmission associated with the sidelink communications is to be repeated on multiple component carriers. In some examples, the indication may include an indication of multiple component carriers, including at least one of the first one or more component carriers, and the sidelink communication is to be repeated on the multiple component carriers. In some examples, the first UE may then send the sidelink communication via each of the multiple component carriers.

[0039] Certain aspects of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques may be used to achieve backward compatibility for sidelink communications associated with carrier aggregation. For example, a UE may send a sidelink communication, where the sidelink communication is repeated on multiple component carriers. The multiple component carriers may be selected (e.g., selected by a network node) to ensure that the multiple component carriers include at least one component carrier that is supported by a UE in the wireless network that does not support sidelink carrier aggregation or is supported by a UE with limited capabilities related to the component carriers supported by the UE. Therefore, the likelihood that a sidelink communication sent by a UE that supports sidelink carrier aggregation is received by a UE that does not support sidelink carrier aggregation or is associated with a reduction in capability for a supported component carrier may increase.

[0040] Figure 11 is a diagram illustrating an example of a wireless network according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network 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 (NN) 110a, network node 110b, network node 110c, and network node 110d), one UE 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The network node 110 is an entity 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 RAN node (e.g., within a single device or unit). For 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)).

[0041] 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 a 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, or one or more DUs. For example, the network node 110 may include an NR network node, an LTE network node, 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 interfaces, midhaul interfaces, or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0042] Each network node 110 may provide communication coverage for a particular geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​a network node 110 or a network node subsystem serving the coverage area, depending on the context in which the term is used.

[0043] The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several thousand meters) 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 residence) 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. A network node 110 for a femto cell may be referred to as a femto network node or a home network node.

[0044] 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, or relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, or different effects on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 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 to 2 watts). Figure 1 In 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).

[0045] 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.

[0046] 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. 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 a CU or a core network device, or the network controller 130 may include a CU or a core network device.

[0047] In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile network nodes 110 (e.g., mobile network nodes). In some examples, the network nodes 110 may be interconnected with each other or to one or more other network nodes 110 or network nodes (not shown) in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections or virtual networks).

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

[0049] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be fixed or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, or a subscriber unit. UE 120 may 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 device, 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, 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, or any other suitable device configured to communicate via a wireless medium.

[0050] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, 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, 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 or a memory component. In some examples, the processor component and the 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, or electrically coupled.

[0051] In general, any amount of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific radio access technology (RAT) and may operate on one or more frequencies. RAT may also be referred to as a radio technology or air interface. Frequency may also be referred to as a carrier or frequency channel. 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.

[0052] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with each other). 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), or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by network node 110.

[0053] In some aspects, actions described herein as being performed by network node 110 may be performed by multiple different network nodes. For example, a configuration action may be performed by a first network node (e.g., CU or DU), and a radio communication action may be performed by a second network node (e.g., DU or RU).

[0054] Devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, or channels by frequency or wavelength. For example, 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). Although a portion of FR1 is 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 arise in conjunction with FR2, which is often (interchangeably) referred to as the “millimeter wave” band in various documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0055] 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 or FR2 characteristics, and thus the features of FR1 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.

[0056] Considering the above examples, unless otherwise specifically stated, if the term "below 6 GHz" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a, FR4-1, 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, or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0057] In some aspects, UE 120 may include communication manager 140. As described in more detail elsewhere herein, communication manager 140 may send to a network node a first indication of at least one of: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with a sidelink communication, the first indication being associated with the sidelink communication; based on sending the first indication, receiving from the network node a second indication that transmission associated with the sidelink communication is to be repeated for a plurality of component carriers; and based on the second indication, sending the sidelink communication via each of a plurality of component carriers, the plurality of component carriers including at least one of the first one or more component carriers. Additionally or alternatively, communication manager 140 may perform one or more other operations described herein.

[0058] In some aspects, the network node 110 may include a communication manager 150. As described in greater detail elsewhere herein, the communication manager 150 may receive one or more indications of at least one of: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with a sidelink communication, the one or more indications associated with the sidelink communication and one or more UEs; and send a communication to a UE of the one or more UEs, the communication indicating that the transmission associated with the sidelink communication is to be repeated for multiple component carriers, the multiple component carriers including at least one component carrier of the first one or more component carriers. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0059] Figure 2 is a diagram illustrating an example network node communicating with a UE in a wireless network according to the present disclosure. The network node may correspond to Figure 1 Similarly, the UE may correspond to a network node 110. Figure 1 UE 120. Network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T ≥ 1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R ≥ 1). Figure 2 The network node 110 depicted in FIG. 1 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 radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0060] 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 (CQIs) 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 may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, 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, 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, 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).

[0061] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 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, 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 to 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, 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.

[0062] 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.

[0063] One or more antennas (e.g., antennas 234a to 234t or antennas 252a to 252r) may include or may be included in one or more antenna panels, one or more antenna groups, one or more antenna element sets, or one or more antenna arrays, etc. An antenna panel, antenna group, antenna element set, or antenna array may include one or more antenna elements (in a single housing or multiple housings), a coplanar antenna element set, a non-coplanar antenna element set, or coupled to one or more transmit or receive components (such as Figure 2 One or more antenna elements of one or more components).

[0064] 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, 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, or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform aspects of any of the methods described herein.

[0065] At the network node 110, uplink signals from the UE 120 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 via the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and provide 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 or uplink communication. 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 an antenna 234, a modem 232, a MIMO detector 236, a receive processor 238, a transmit processor 220, or a TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein.

[0066] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or Figure 2Any other component of the network node 110 may perform one or more techniques associated with sidelink carrier aggregation, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or Figure 2 Any other component of the Fig.11 Process 1100, Fig.12 1200 or 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 or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 or UE 120 (e.g., directly, or after compilation, conversion, or interpretation), may cause one or more processors, UE 120, or network node 110 to perform or direct, for example, Fig.11 Process 1100, Fig.12 The operations of process 1200 or other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, or interpreting instructions, etc.

[0067] In some aspects, the UE 120 includes: means for sending a first indication to a network node of at least one of: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with the sidelink communication, the first indication being associated with the sidelink communication; means for receiving from the network node, based on sending the first indication, a second indication that the transmission associated with the sidelink communication will be repeated for a plurality of component carriers; or means for transmitting the sidelink communication via each of a plurality of component carriers, including at least one of the first one or more component carriers, based on the second indication. Means for the UE 120 to perform operations described herein may include, for example, one or more of the following: 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.

[0068] In some aspects, the network node 110 includes: means for receiving one or more indications of at least one of: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with a sidelink communication, the one or more indications being associated with the sidelink communication and one or more UEs; or means for sending a communication to a UE of the one or more UEs, the communication indicating that the transmission associated with the sidelink communication is to be repeated for multiple component carriers, the multiple component carriers including at least one of the first one or more component carriers. In some aspects, the means for the network node 110 to perform operations described herein may include, for example, one or more of the following: the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0069] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways using various components or constituent parts. 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 base station, 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).

[0070] 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 the CU, DU, and 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.

[0071] 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.

[0072] 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.

[0073] 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 transmit 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 the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, and the wireless interface being configured to receive signals or transmit signals to one or more of the other units via a wireless transmission medium, or both.

[0074] In some examples, 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 divided 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.

[0075] 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 examples, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional partition such as that defined by 3GPP. In some examples, 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 examples, 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.

[0076] 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 based on functional partitioning (e.g., functional partitioning defined by 3GPP) such as lower layer functional partitioning, or low PHY layer functions such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. 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 plane 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.

[0077] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 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.

[0078] 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-RT RIC 315 may be coupled to or communicate 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.

[0079] 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).

[0080] Figure 4 4 is a diagram illustrating an example of side link communication 400 according to the present disclosure. Figure 4 As shown, the first UE 405-1 can communicate with the second UE 405-2 (and one or more other UEs 405) via one or more side link channels 410. UEs 405-1 and 405-2 can communicate using one or more side link channels 410 for P2P communication, D2D communication, V2X communication (e.g., which may include V2V communication, V2I communication, or V2P communication) or mesh networking. In some examples, UE 405 (e.g., UE 405-1 or UE 405-2) may correspond to one or more other UEs described elsewhere herein, such as UE120. In some examples, one or more side link channels 410 may use a PC5 interface, or may operate in a high frequency band (e.g., a 5.9 GHz band). Additionally or alternatively, UE 405 may use global navigation satellite system (GNSS) timing to synchronize the timing of a transmit time interval (TTI) (e.g., a frame, subframe, time slot, or symbol).

[0081] like Figure 4 As further shown in FIG. 1 , the one or more sidelink channels 410 may include a physical sidelink control channel (PSCCH) 415, a physical sidelink shared channel (PSSCH) 420, or a physical sidelink feedback channel (PSFCH) 425. The PSCCH 415 may be used to communicate control information, similar to a physical downlink control channel (PDCCH) or a physical uplink control channel (PUCCH) used for cellular communication with the network node 110 via an access link or access channel. The PSSCH 420 may be used to communicate data, similar to a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) used for cellular communication with the network node 110 via an access link or access channel. For example, the PSCCH 415 may carry sidelink control information (SCI) 430, which may indicate various control information for sidelink communication, such as one or more resources (e.g., time resources, frequency resources, or space resources), wherein a transport block (TB) 435 may be carried on the PSSCH 420. The TB 435 may include data. The PSFCH 425 may be used to communicate sidelink feedback 440, such as hybrid automatic repeat request (HARQ) feedback (eg, acknowledgement (ACK) or negative acknowledgement (NACK) (ACK / NACK) information), transmit power control (TPC), or scheduling request (SR).

[0082] Although shown on PSCCH 415, in some examples, SCI 430 may include multiple communications in different phases, such as a first phase SCI (SCI-1) and a second phase SCI (SCI-2). SCI-1 may be sent on PSCCH 415. SCI-2 may be sent on PSSCH 420. SCI-1 may include, for example, an indication of one or more resources (e.g., time resources, frequency resources, or space resources) reserved for PSSCH 420, information for decoding sidelink communications on PSSCH, a quality of service (QoS) priority value, a resource reservation period, a PSSCH DMRS mode, an SCI format for SCI-2, a beta offset for SCI-2, the number of PSSCH DMRS ports, or an MCS. SCI-2 may include information associated with data transmission on PSSCH 420, such as a HARQ process ID, a new data indicator (NDI), a source identifier, a destination identifier, or a channel state information (CSI) report trigger.

[0083] In some examples, one or more sidelink channels 410 may use a resource pool. For example, a scheduling assignment (e.g., included in SCI 430) may be sent in a subchannel using specific resource blocks (RBs) across time. In some examples, data transmissions associated with the scheduling assignment (e.g., on PSSCH 420) may occupy adjacent RBs in the same time slot as the scheduling assignment (e.g., using frequency division multiplexing).

[0084] In some examples, UE 405 may operate using a sidelink transmission mode (e.g., Mode 1) in which resource selection or scheduling is performed by network node 110 (e.g., base station, CU, or DU). For example, UE 405 may receive a grant (e.g., in downlink control information (DCI) or in an RRC message, such as for a configured grant) from network node 110 (e.g., directly or via one or more network nodes) for sidelink channel access or scheduling. In some examples, UE 405 may operate using a transmission mode (e.g., Mode 2) in which resource selection or scheduling is performed by UE 405 (e.g., instead of network node 110). In some examples, UE 405 may perform resource selection or scheduling by sensing channel availability for transmission. For example, UE 405 may measure RSSI parameters associated with various side link channels (e.g., sidelink-RSSI (S-RSSI) parameters), may measure RSRP parameters associated with various side link channels (e.g., PSSCH-RSRP parameters), or may measure RSRQ parameters associated with various side link channels (e.g., PSSCH-RSRQ parameters), and may select a channel for sending side link communications based at least in part on the measurements.

[0085] Additionally or alternatively, the UE 405 may perform resource selection or scheduling using the SCI 430 received in the PSCCH 415, which may indicate occupied resources or channel parameters. Additionally or alternatively, the UE 405 may perform resource selection or scheduling by determining a channel busy ratio (CBR) associated with various sidelink channels, which may be used for rate control (e.g., by indicating a maximum number of resource blocks that the UE 405 may use for a particular set of subframes).

[0086] In a transmission mode in which resource selection or scheduling is performed by the UE 405, the UE 405 may generate sidelink grants and may transmit these grants in the SCI 430. The sidelink grant may indicate, for example, one or more parameters (e.g., transmission parameters) to be used for an upcoming sidelink transmission, such as one or more resource blocks (e.g., for TB 435) to be used for an upcoming sidelink transmission on the PSSCH 420, one or more subframes to be used for an upcoming sidelink transmission, or an MCS to be used for an upcoming sidelink transmission. In some examples, the UE 405 may generate a sidelink grant indicating one or more parameters for semi-persistent scheduling (SPS), such as the periodicity of the sidelink transmission. Additionally or alternatively, the UE 405 may generate a sidelink grant for event-driven scheduling, such as for an on-demand sidelink message.

[0087] Figure 5 is a diagram illustrating an example of side link communication and access link communication 500 according to the present disclosure. Figure 5 As shown, the transmitter (Tx) / receiver (Rx) UE 505 and the Rx / Tx UE 510 can communicate with each other via a side link, as described above in conjunction with Figure 4 as described.

[0088] As further shown, in some sidelink modes, the network node 110 may communicate (e.g., directly or via one or more network nodes), such as via a first access link, with a Tx / Rx UE 505. Additionally or alternatively, in some sidelink modes, the network node 110 may communicate (e.g., directly or via one or more network nodes), such as via a first access link, with an Rx / Tx UE 510. The Tx / Rx UE 505 or Rx / Tx UE 510 may correspond to one or more UEs described elsewhere herein, such as Figure 1 120. Thus, a direct link between UEs 120 (e.g., via a PC5 interface) may be referred to as a side link, and a direct link between network node 110 and UE 120 (e.g., via a Uu interface) may be referred to as an access link. Side link communications may be sent via a side link, and access link communications may be sent via an access link. Access link communications may be downlink communications (from network node 110 to UE 120) or uplink communications (from UE 120 to network node 110).

[0089] Figure 66 is a diagram illustrating an example of carrier aggregation 600 according to the present disclosure. Carrier aggregation is a technique that enables two or more component carriers (CCs, sometimes referred to as carriers) to be combined (e.g., combined into a single channel) for a single UE 120 to enhance data capacity. As shown, carriers may be combined in the same or different frequency bands. Additionally or alternatively, contiguous or non-contiguous carriers may be combined. The network node 110 may configure carrier aggregation for the UE 120, such as in an RRC message, a DCI, or another signaling message.

[0090] In some examples, carrier aggregation may be configured in intra-band contiguous mode 605, where the aggregated carriers are contiguous with each other and in the same frequency band. In some examples, carrier aggregation may be configured in intra-band discontiguous mode 610, where the aggregated carriers are discontiguous with each other and in the same frequency band. In some examples, carrier aggregation may be configured in inter-band discontiguous mode 615, where the aggregated carriers are discontiguous with each other and in different frequency bands.

[0091] In carrier aggregation on the Uu interface, the UE 120 may be configured with a primary carrier or primary cell (PCell) and one or more secondary carriers or secondary cells (SCells). In some examples, the primary carrier may carry control information (e.g., downlink control information or scheduling information) for scheduling data communications on one or more secondary carriers, which may be referred to as cross-carrier scheduling. In some examples, a carrier (e.g., a primary carrier or a secondary carrier) may carry control information for scheduling data communications on the carrier, which may be referred to as self-carrier scheduling or carrier self-scheduling or intra-carrier scheduling.

[0092] In some examples, UE 120 may be configured to perform carrier aggregation for sidelink communications. For example, UE 120 may send sidelink communications using a PCell and one or more SCells in a manner similar to that described above. In some examples, UE 120 may perform carrier aggregation for sidelink communications in sidelink mode 1 (e.g., where scheduling and resource allocation are performed by network node 110). Additionally or alternatively, UE 120 may perform carrier aggregation for sidelink communications in sidelink mode 2 (e.g., where scheduling and resource allocation are performed by UE 120).

[0093] Figure 7is a diagram illustrating an example of sidelink carrier aggregation 700 according to the present disclosure. Carrier aggregation on a PC5 interface (e.g., a sidelink interface) may be implemented to LTE V2X. An independent HARQ entity per carrier may be used for V2X sidelink communications. Each transport block and corresponding potential HARQ retransmission may be mapped to a single carrier. Multiple transport blocks may be sent in parallel on different carriers to obtain throughput gain. Sidelink carrier aggregation in resource allocation mode 3 using dynamic grant may include a carrier indication field (CIF) in the DCI from the network node 110 (e.g., a carrier index of a configured carrier list). Sidelink carrier aggregation in resource allocation mode 4 may use a sensing procedure to independently select resources on each involved carrier. The same carrier may be used for all transport blocks of the same sidelink process, at least until the process triggers resource reselection.

[0094] like Figure 7 As shown, a 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 processing. The RLC layer may be associated with segmentation. The PDCP layer may be associated with security and robust header compression (ROHC). The SL-SCH (Rx) for reception 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 a sidelink broadcast control channel (SBCCH) for Tx and Rx may be defined. A 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.

[0095] Configuration parameters for V2X communications over the NR PC5 interface may be based at least in part on mapping rules. The mapping rules may involve mappings between one or more V2X service identifiers (e.g., service types) and layer 2 (L2) destination identifiers for broadcast or multicast communications. The mapping rules may involve mappings between one or more V2X service identifiers or service types and V2X NR frequencies with associated geographic regions. Thus, an L2 destination identifier for multicast or broadcast communications may be associated with multiple V2X services (e.g., multiple sidelink service types), which may be mapped to the same or different frequency carriers in a geographic region. For example, some services associated with the L2 destination identifier may support legacy V2X UEs (e.g., UEs operating in accordance with Release 16 or 17 of the 3GPP technical specifications) that do not support sidelink carrier aggregation (e.g., support only one carrier), and other services associated with the L2 destination identifier may support new V2X UEs (e.g., UEs operating in accordance with Release 18 or higher of the 3GPP technical specifications) that support sidelink carrier aggregation (e.g., support more than one carrier).

[0096] For a multicast or broadcast communication associated with an L2 destination identifier, when the selected carrier is not a carrier for a UE that does not support sidelink carrier aggregation, packets sent on a component carrier selected, for example, by a network node or by a UE that supports sidelink carrier aggregation may not be received by the UE that does not support sidelink carrier aggregation. For another example, some UEs may be associated with reduced capabilities. For example, due to reduced or limited capabilities of some UEs, these UEs may not be able to support all frequency carriers associated with a given L2 destination identifier. Therefore, if the selected carrier for the transmission of a multicast or broadcast communication associated with the L2 destination identifier is not supported by the UE with reduced capabilities, the UE with reduced capabilities may not be able to receive the multicast or broadcast communication.

[0097] In other words, a first UE 120 that supports sidelink carrier aggregation may be configured to use one or more component carriers in a component carrier set to send a multicast or broadcast communication associated with an L2 destination identifier. A second UE 120 that does not support sidelink carrier aggregation may be configured to use a single component carrier (e.g., the single component carrier is included in the component carrier set) to receive sidelink communications. However, if the network node 110 or the first UE 120 does not select a single component carrier for sending a multicast or broadcast communication, the second UE 120 may not receive the multicast or broadcast communication. Therefore, backward compatibility issues may arise for sidelink carrier aggregation.

[0098] Various aspects generally relate to sidelink carrier aggregation. Some aspects more specifically relate to a UE sending an indication to a network node of at least one of: 1) whether sidelink carrier aggregation is supported (e.g., for sidelink communications or for sidelink services or service types); or 2) one or more component carriers associated with sidelink communications (e.g., one or more component carriers supported by the UE). As used herein, "sidelink communications" may refer to one or more sidelink packets or information associated with a given L2 destination identifier.

[0099] The sidelink communication may be repeated based at least in part on a broadcast type (e.g., broadcast or multicast) and one or more indications obtained by the UE from an upper layer (e.g., an application layer). One or more indications from the upper layer may indicate whether each service type supports or does not support sidelink carrier aggregation for an L2 destination identifier associated with the sidelink communication. For example, the upper layer may indicate to the access stratum (AS) layer multiple transmission (Tx) profiles associated with the L2 destination identifier (e.g., each transmission profile indicates at least one of the following: 1) whether sidelink carrier aggregation is supported, or 2) one or more associated component carriers for sidelink communication). Alternatively, the upper layer may indicate to the AS layer only one Tx profile associated with the L2 destination identifier (again, for example, indicating at least one of the following: 1) whether sidelink carrier aggregation is supported, or 2) one or more associated component carriers for sidelink communication). The UE may send an indication to the network node based at least in part on one or more indications obtained from the upper layer (e.g., to indicate 1) whether sidelink carrier aggregation is supported; or 2) one or more component carriers associated with the sidelink communication).

[0100] In some aspects, to support backward compatibility for a sidelink carrier aggregation feature (e.g., which may be supported by some UEs and not by other UEs), sidelink communications may be repeated on multiple component carriers. Knowledge of the UE's capabilities for sidelink carrier aggregation or knowledge of one or more component carriers supported by the UE for sidelink communications may enable a network node (e.g., for sidelink mode 1 scheduling) to determine whether to repeat sidelink communications (e.g., associated with a given L2 destination identifier) ​​on multiple component carriers. For example, the network node may determine that the sidelink communications are to be repeated on multiple component carriers based at least in part on the mutual exclusion of a first one or more component carriers (e.g., supported by a first UE or a first service type associated with the sidelink communications) and a second one or more component carriers (e.g., supported by a second UE or a second service type associated with the sidelink communications) (e.g., based on the first one or more component carriers and the second one or more component carriers not including a common component carrier). In some aspects, the network node may send an indication to the first UE that a transmission associated with the sidelink communications is to be repeated on multiple component carriers. In some examples, the indication may include an indication of multiple component carriers, including at least one of the first one or more component carriers, and the sidelink communication is to be repeated on the multiple component carriers. In some examples, the first UE may then send the sidelink communication via each of the multiple component carriers.

[0101] Certain aspects of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques may be used to achieve backward compatibility for sidelink communications associated with carrier aggregation. For example, a UE may send a sidelink communication, where the sidelink communication is repeated on multiple component carriers. The multiple component carriers may be selected (e.g., selected by a network node) to ensure that the multiple component carriers include at least one component carrier that is supported by a UE in the wireless network that does not support sidelink carrier aggregation or is supported by a UE with limited capabilities related to the component carriers supported by the UE. Therefore, the likelihood that a sidelink communication sent by a UE that supports sidelink carrier aggregation is received by a UE that does not support sidelink carrier aggregation or is associated with a reduction in capability for a supported component carrier may increase.

[0102] Figure 8 8 is a diagram of an example 800 associated with sidelink carrier aggregation according to the present disclosure. Figure 8As shown, one or more network nodes 110 (e.g., CU, DU, RU, or base station) may communicate with a first UE 120 and a second UE 120. In some aspects, the network node 110, the first UE 120, and the second UE 120 may be part of a wireless network (e.g., wireless network 100). The first UE 120 and the network node 110 may be in communication with each other. Figure 8 The wireless connection has been established before the operation shown. Similarly, the first UE 120 and the second UE 120 and the network node 110 may be connected to the wireless network at Figure 8 The first UE 120 and the second UE 120 may (for example, in combination with Figure 4 and Figure 5 The first UE 120 and the second UE 120 may communicate with each other using the sidelink in a manner similar to that described above. The first UE 120 and the second UE 120 may operate in sidelink mode 1 (eg, where the network node 110 performs scheduling and resource selection for sidelink communication).

[0103] As used herein, a network node 110 "sending" a communication to a UE 120 (e.g., a first UE 120 or a second UE 120) may refer to direct transmission (e.g., from the network node 110 to the UE 120) or indirect transmission via one or more other network nodes or devices. For example, if the network node 110 is a DU, indirect transmission to the UE 120 may include the DU sending the communication to the RU and the RU sending the communication to the UE 120. Similarly, a UE 120 (e.g., a first UE 120 or a second UE 120) "sending" a communication to the network node 110 may refer to direct transmission (e.g., from the UE 120 to the network node 110) or indirect transmission via one or more other network nodes or devices. For example, if the network node 110 is a DU, indirect transmission to the network node 110 may include the UE 120 sending the communication to the RU and the RU sending the communication to the DU. In some aspects, references herein to "network node 110" or "the network node 110" may refer to multiple network nodes.

[0104] The protocol stack may be implemented on a UE 120 (e.g., a first UE 120 or a second UE 120) or a network node 110. As used herein, a "layer" may refer to a protocol stack layer. On the user plane, the UE 120 and the network node 110 may include a corresponding PHY layer, a MAC layer, an RLC layer, a PDCP layer, and an SDAP layer. The user plane function may handle the transmission of user data between the UE 120 and the network node 110. On the control plane, the UE 120 and the network node 110 may include a corresponding RRC layer. In addition, the UE 120 may include a NAS layer that communicates with a non-access stratum (NAS) layer of an access and management mobility function (AMF). The control plane function may handle the transmission of control information between the UE 120 and the core network. Typically, if the first layer is farther from the PHY layer than the second layer, the first layer is referred to as being higher than the second layer. For example, the PHY layer may be referred to as the lowest layer, and the SDAP / PDCP / RLC / MAC layer may be referred to as being higher than the PHY layer and lower than the RRC layer. The application (APP) layer or service layer may be higher than the SDAP / PDCP / RLC / MAC layer. In some cases, an entity may handle the services and functions of a given layer (e.g., a PDCP entity may handle the services and functions of the PDCP layer), although the description herein mentions that these layers themselves handle these services and functions.

[0105] The RRC layer may handle communications related to configuring and operating the UE 120, such as: broadcasting of system information related to the AS and NAS; paging initiated by the 5G core network (5GC) or the next generation radio access network (NG-RAN); establishment, maintenance, and release of an RRC connection between the UE 120 and the NG-RAN, including the addition, modification, and release of carrier aggregation, and the addition, modification, and release of dual connectivity; security functions, including key management; establishment, configuration, maintenance, and release of signaling radio bearers (SRBs) and data radio bearers (DRBs); mobility functions (e.g., handover and context transfer, UE cell selection and reselection and control of cell selection and reselection, inter-RAT mobility); QoS management functions; UE measurement reporting and control of reporting; detection of and recovery from radio link failures; and NAS messaging between the NAS layer and lower layers of the UE 120. The RRC layer is often referred to as Layer 3 (L3).

[0106] The SDAP layer, the PDCP layer, the RLC layer, and the MAC layer may be collectively referred to as Layer 2 (L2). Therefore, in some cases, the SDAP, PDCP, RLC, and MAC layers are referred to as sublayers of Layer 2. The PDCP layer may provide data in the form of PDCP protocol data units (PDUs) to the RLC layer via an RLC channel. The RLC layer may handle the delivery of upper layer PDUs to the MAC layer or the PHY layer, sequence numbers independent of PDCP sequence numbers, error correction via automatic repeat request (ARQ), segmentation and re-segmentation, reassembly of service data units (SDUs), RLC SDU discard, and RLC reconstruction. The RLC layer may provide data mapped to logical channels to the MAC layer. The services and functions of the MAC layer include mapping between logical channels and transport channels (used by the PHY layer as described below), multiplexing of MAC SDUs belonging to one or different logical channels into / demultiplexing the MAC SDUs from the TB delivered to / from the physical layer on the transport channel, scheduling information reporting, error correction through HARQ, priority handling between UEs with the help of dynamic scheduling, priority handling between logical channels of a UE with the help of logical channel prioritization, and padding. The MAC layer can encapsulate data from logical channels into TBs and can provide TBs to the PHY layer on one or more transport channels. The PHY layer can handle various operations related to the transmission of data signals, such as combining Figure 2 The PHY layer is often referred to as Layer 1 (L1).

[0107] On the receiving side (e.g., if the UE 120 is receiving downlink communications or the network node 110 is receiving uplink communications), operations may be similar to those described for the transmitting side, but in the opposite direction. For example, the PHY layer may receive TBs and may provide TBs to the MAC layer on one or more transport channels. The MAC layer may map transport channels to logical channels and may provide data to the RLC layer via the logical channels. The RLC layer may map logical channels to RLC channels and may provide data to the PDCP layer via the RLC channels. The PDCP layer may map RLC channels to radio bearers and may provide data to the SDAP layer or the RRC / NAS layer via the radio bearers.

[0108] Data may be passed between layers in the form of PDUs and SDUs. An SDU is a unit of data that has been passed from a layer or sublayer to a lower layer. For example, a PDCP layer may receive a PDCP SDU. A given layer may then encapsulate the data unit into a PDU and may pass the PDU to a lower layer. For example, a PDCP layer may encapsulate a PDCP SDU into a PDCP PDU and may pass the PDCP PDU to an RLC layer. An RLC layer may receive a PDCP PDU as an RLC SDU, may encapsulate the RLC SDU into an RLC PDU, and so on. In effect, a PDU carries an SDU as a payload.

[0109] In a first operation 805, the first UE 120 may obtain information indicating at least one of the following from an upper layer associated with the first UE 120: whether sidelink carrier aggregation for sidelink communication (e.g., associated with a given L2 destination identifier) ​​is supported, or one or more component carriers associated with the sidelink communication. In some aspects, the first one or more component carriers may be associated with one or more sidelink service types (e.g., V2X service types). For example, the one or more indications may be passed from an upper layer (e.g., an application layer or a service layer) of the first UE 120 to a lower layer (e.g., an AS layer or a NAS layer).

[0110] For example, the first UE 120 may obtain, from an upper layer (e.g., an application layer or a service layer, such as a V2X service layer), one or more indications indicating at least one of the following: support or non-support of sidelink carrier aggregation (e.g., "SL-CA" or "No-SL-CA") or associated one or more component carriers, based at least in part on a service or service type associated with an L2 destination ID for multicast or broadcast (support or non-support of sidelink carrier aggregation). In some aspects, for an indication associated with an indication that sidelink carrier aggregation is not supported (e.g., an indication of "No-SL-CA"), one or more component 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 associated with 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.

[0111] In some aspects, the indication may include a list of (e.g., one or more) component carriers associated with the corresponding service or service type associated with the L2 destination identifier. For example, the indication from the upper layer may include one or more sidelink carriers for transmission (e.g., sl-txcc-list1) or one or more sidelink component carriers for reception (e.g., sl-rxcc-list1), where the one or more sidelink carriers for transmission may be the same as or different from the one or more sidelink component carriers for reception.

[0112] Additionally or alternatively, an indication or configuration obtained from an upper layer (e.g., such as pre-configured in an original equipment manufacturer (OEM) configuration or configured in a configuration received by the UE 120) may indicate UE capabilities associated with component carriers for an L2 destination identifier (e.g., for one or more or all sidelink services or sidelink service types) supported by the first UE 120. For example, the L2 destination identifier may be associated with a set of component carriers (e.g., the set of component carriers may be used to send or receive sidelink communications associated with the L2 destination identifier). The indication obtained from an upper layer (or indicated by a pre-configuration or configuration) may indicate a subset of component carriers in the set of component carriers supported by the first UE 120 for sidelink communications (e.g., broadcast or multicast) associated with the L2 destination identifier (e.g., for one or more or all sidelink services or sidelink service types). In some aspects, the first UE 120 may be pre-configured (e.g., by an OEM or service provider) or configured (e.g., by the network) or indicated (e.g., via system information (SI) of the network) with a list of sidelink component carriers for carrier aggregation.

[0113] In a second operation 810, the second UE 120 may obtain information indicating at least one of the following from an upper layer associated with the second UE 120: whether sidelink carrier aggregation for sidelink communication (e.g., associated with a given L2 destination identifier) ​​is supported, or one or more component carriers associated with the sidelink communication. For example, the second UE 120 may obtain one or more indications from the upper layer in a manner similar to that described above in conjunction with the first operation 805. For example, the second UE 120 may obtain a list of (e.g., one or more) component carriers that are associated with corresponding services or service types associated with the L2 destination identifier. For example, the indication from the upper layer may include one or more sidelink carriers for transmission (e.g., sl-txcc-list2) or one or more sidelink component carriers for reception (e.g., sl-rxcc-list2), wherein the one or more sidelink carriers for transmission may be the same as or different from the one or more sidelink component carriers for reception.

[0114] In a third operation 815, the network node 110 may send an indication of supporting sidelink carrier aggregation (CA) for the wireless network or that the network node 110 supports sidelink carrier aggregation (CA), and the first UE 120 and the second UE 120 may receive the indication. The indication of supporting sidelink carrier aggregation may be included in the sidelink common configuration. In some aspects, the network node 110 may send system information, and the first UE 120 and the second UE 120 may receive the system information, which indicates that sidelink carrier aggregation is supported. For example, the indication may be included in a system information block (SIB). The SIB may be associated with the sidelink common configuration. For example, the SIB may be SIB12 (e.g., as defined by 3GPP or otherwise determined). For example, the first UE 120 and the second UE 120 may monitor the SIB broadcasted by the network node 110. The SIB may include an indication of whether the network node 110 supports sidelink carrier aggregation. The indication of whether the network node 110 supports sidelink carrier aggregation may be an explicit indication or an implicit indication. In some aspects, the network (e.g., network node 110) may explicitly indicate whether sidelink carrier aggregation is supported (e.g., if carrier aggregation is not supported, a flag for sidelink carrier aggregation is set to a value of "0", or if carrier aggregation is supported, a flag for sidelink carrier aggregation is set to a value of "1"). In some aspects, the network (e.g., network node 110) may implicitly indicate whether sidelink carrier aggregation is supported (e.g., if more than one component carrier is indicated for sidelink communication, this may imply support for carrier aggregation).

[0115] In a fourth operation 820, the first UE 120 may send a first indication of at least one of the following: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with the sidelink communication, the first indication being associated with the sidelink communication, and the network node 110 may receive the first indication. For example, the first indication may be based on one or more indications obtained from the upper layer of the first UE 120 in the first operation 805. In some aspects, the first indication may be associated with an L2 destination identifier. For example, the sidelink communication may be a broadcast communication or a multicast communication associated with the L2 destination identifier. In some aspects, the first indication may be associated with or at least partially based on one or more sidelink service types. In some aspects, whether sidelink carrier aggregation is supported or the first one or more component carriers associated with the sidelink communication may be based at least in part on the capabilities of the first UE 120.

[0116] In some aspects, the first indication may be included in an uplink communication. For example, the uplink communication may be an RRC communication. In some aspects, the first indication may be included in a sidelink UE information communication. For example, when all indications from the upper layer indicate support for SL CA, the first UE 120 may send a sidelink UE information message indicating support for sidelink carrier aggregation (SL CA) (e.g., "SL-CA" or a bit indication sl-ca="1") to the network node 110. The sidelink UE information message may indicate an associated sidelink component carrier list (e.g., sl-rxcc-list1 for reception and sl-txcc-list1 for transmission, where sl-rxcc-list1 may be the same as or different from sl-txcc-list1). Alternatively, when at least one indication from an upper layer indicates that sidelink carrier aggregation is not supported or when there is no indication from an upper layer, the first UE 120 may send a sidelink UE information message indicating that sidelink carrier aggregation is not supported (e.g., "No-SL-CA" or a bit indication sl-ca="0") to the network node 110. The sidelink UE information message may indicate an associated sidelink component carrier (SL CC) list for an L2 destination identifier associated with a multicast or broadcast communication (e.g., sl-rxcc-list1 for reception and sl-txcc-list1 for transmission, where sl-rxcc-list1 may be the same as or different from sl-txcc-list1).

[0117] Similarly, in a fifth operation 825, the second UE 120 may send a first indication of at least one of whether sidelink carrier aggregation is supported or a first one or more component carriers associated with the sidelink communication, the first indication being associated with the sidelink communication, and the network node 110 may receive the first indication. For example, the first indication may be based on one or more indications obtained from the upper layer of the second UE 120 in the second operation 810. In some aspects, the first indication may be associated with an L2 destination identifier. For example, the sidelink communication may be a broadcast communication or a multicast communication associated with the L2 destination identifier. In some aspects, the first indication may be associated with or based at least in part on one or more sidelink service types.

[0118] In some aspects, the first indication may be included in an uplink communication. For example, the uplink communication may be an RRC communication. In some aspects, the first indication may be included in a sidelink UE information communication. For example, when all indications from the upper layer indicate support for sidelink carrier aggregation (SL CA), the second UE 120 may send a sidelink UE information message indicating support for SL CA (e.g., "SL-CA" or a bit indication sl-ca="1") to the network node 110. The sidelink UE information message may indicate an associated sidelink component carrier list (e.g., sl-rxcc-list2 for reception and sl-txcc-list2 for transmission, where sl-rxcc-list2 may be the same as or different from sl-txcc-list2). Alternatively, when at least one indication from an upper layer indicates that sidelink carrier aggregation is not supported or when there is no indication from an upper layer, the second UE 120 may send a sidelink UE information message indicating that sidelink carrier aggregation is not supported (e.g., "No-SL-CA" or a bit indication sl-ca="0") to the network node 110. The sidelink UE information message may indicate an associated sidelink component carrier (SL CC) list for an L2 destination identifier associated with a multicast or broadcast communication (e.g., sl-rxcc-list2 for reception and sl-txcc-list2 for transmission, where sl-rxcc-list2 may be the same as or different from sl-txcc-list2).

[0119] The network node 110 may receive indications from other UEs in a similar manner. In some aspects, the UE (e.g., the first UE 120 and the second UE 120) may send sidelink UE information based at least in part on the network node 110 (e.g., in the third operation 815) sending an indication that the network node 110 supports sidelink carrier aggregation, the sidelink UE information indicating information associated with the supported component carriers for sidelink carrier aggregation. For example, the first UE 120 (e.g., in the fourth operation 820) and the second UE 120 (e.g., in the fifth operation 825) may send sidelink UE information based at least in part on the network node 110 (e.g., in the third operation 815) sending an SIB indicating support for sidelink carrier aggregation, the sidelink UE information indicating information associated with sidelink carrier aggregation (e.g., support for carrier aggregation and associated component carriers).

[0120] In some aspects, the UE (e.g., the first UE 120 and the second UE 120) may send a sidelink buffer status report (SL-BSR) indicating information associated with supported component carriers for sidelink carrier aggregation based at least in part on the network node 110 (e.g., in the third operation 815) sending an indication that the network node 110 supports sidelink carrier aggregation. For example, the first UE 120 (e.g., in the fourth operation 820) and the second UE 120 (e.g., in the fifth operation 825) may send the SL-BSR indicating information associated with sidelink carrier aggregation (e.g., whether carrier aggregation and associated component carriers are supported) based at least in part on the network node 110 (e.g., in the third operation 815) sending an SIB indicating support for sidelink carrier aggregation.

[0121] In some aspects, a UE (e.g., a first UE 120 and a second UE 120) may send a sidelink buffer status report (SL-BSR) based at least in part on one or more indications from an upper layer for sidelink communications, the sidelink buffer status report (SL-BSR) indicating information associated with supported component carriers for sidelink carrier aggregation. For example, the first UE 120 (e.g., in the fourth operation 820) and the second UE 120 (e.g., in the fifth operation 825) may send a SL-BSR based at least in part on one or more indications from an upper layer for sidelink communications associated with data in a buffer (e.g., a logical channel associated with an L2 destination identifier, e.g., as indicated via a destination index), the SL-BSR indicating information associated with sidelink carrier aggregation (e.g., whether carrier aggregation and associated component carriers are supported).

[0122] In a sixth operation 830, the network node 110 may determine a list of sidelink component carriers and whether to enable repetition for sidelink communication (or for an L2 destination identifier). For example, the network node 110 may determine a list of sidelink component carriers and whether to enable repetition for sidelink communication (or for an L2 destination identifier) ​​based on an indication received from one or more UEs (such as an indication sent as described above in conjunction with the fourth operation 820 and the fifth operation 825). In other words, the network node 110 may determine whether one or more sidelink component carrier lists have transmission repetitions for an L2 destination ID associated with a multicast or broadcast based on a sidelink UE information message or a sidelink buffer status report message received by the network node 110.

[0123] For example, if all services or service types associated with a multicast or broadcast L2 destination ID identifier support sidelink carrier aggregation (e.g., as described above, "SL-CA" is indicated in the indication from the upper layer or the bit indication sl-ca = "1" and there is no UE capability restriction on the sidelink CC), the network node 110 may determine a list of one or more sidelink component carriers for sidelink carrier aggregation transmission associated with the L2 destination identifier without sending duplication. For another example, if at least one service or service type associated with the L2 destination identifier for multicast or broadcast does not support sidelink carrier aggregation (e.g., as described above, "No-SL-CA" is indicated in the indication from the upper layer or the bit indication sl-ca="0"), or if there are any UEs with UE capability restrictions on the sidelink component carriers, the network node 110 may determine one or more sidelink component carrier lists for sidelink carrier aggregation transmission associated with the L2 destination identifier, and there are transmission repetitions on the sidelink component carriers derived from the one or more sidelink component carrier lists to ensure that UEs that do not support sidelink carrier aggregation or UEs with limited UE capability on the sidelink component carriers can receive sidelink communication packets. In other words, if the first indication sent by the first UE 120 or the second UE 120 (e.g., in the fourth operation 820 or the fifth operation 825) includes an indication that sidelink carrier aggregation is not supported for one or more component carriers, the network node 110 may determine that packets associated with the sidelink communication will be repeated on multiple component carriers associated with the service or service type that does not support carrier aggregation.

[0124] For example, the network node 110 may receive an indication of supported component carriers for various sidelink service types or various UEs. For example, the first UE 120 may indicate a first set of component carriers supported for sidelink communication (e.g., for an L2 destination identifier) ​​based at least in part on capabilities associated with the first UE 120. Similarly, the second UE 120 may indicate a second set of component carriers supported for sidelink communication (e.g., for an L2 destination identifier) ​​based at least in part on capabilities associated with the second UE 120. For ease of explanation, assuming that the network node 110 receives only these two indications, if the first set of component carriers and the second set of component carriers include at least one common component carrier, the network node 110 may determine one or more sidelink component carrier lists for sidelink carrier aggregation transmissions associated with the L2 destination identifier without transmission duplication. In such examples, the one or more sidelink component carrier lists may include at least one common component carrier to ensure that packets associated with the sidelink communication can be received by all UEs (e.g., the first UE 120 and the second UE 120).

[0125] Alternatively, if the first component carrier set and the second component carrier set do not include at least one common component carrier (e.g., if the first component carrier set and the second component carrier set are mutually exclusive), the network node 110 may determine one or more sidelink component carrier lists for sidelink carrier aggregation transmissions associated with the L2 destination identifier, and there is transmission duplication. In such examples, packets associated with sidelink communications may be repeated on at least one component carrier in the first component carrier set and on at least one component carrier in the second component carrier set to ensure that packets associated with sidelink communications can be received by all UEs (e.g., the first UE 120 and the second UE 120).

[0126] In a seventh operation 835, the network node 110 may send configuration information for sidelink carrier aggregation, and the first UE 120 may receive the configuration information. In some aspects, the first UE 120 may receive the configuration information via one or more of RRC signaling, one or more MAC control elements (MAC-CE), or DCI, etc. For example, the network node 110 may send a dedicated sidelink configuration message (e.g., sidelink RRC configuration) for the first UE 120. In some aspects, the configuration information may indicate that transmissions associated with sidelink communications will be repeated for multiple component carriers. For example, the configuration information may indicate one or more sidelink component carrier lists (e.g., sl-rxcc-list3 and sl-txcc-list3) configured for the first UE 120. The one or more sidelink component carrier lists (e.g., sl-rxcc-list3 and sl-txcc-list3) may be based at least in part on component carriers indicated as supported by the first UE 120, such as in the fourth operation 820 (e.g., sl-rxcc-list1 and sl-txcc-list1).

[0127] Additionally, the configuration information may indicate whether to enable transmission repetition for sidelink communications (e.g., for L2 destination identifiers). For example, a radio resource control communication (e.g., including the configuration information) may indicate a plurality of component carriers (e.g., sl-rxcc-list3 and sl-txcc-list3) and may include an indication of a repetition type associated with the plurality of component carriers. The repetition type may include a MAC layer repetition (e.g., as combined with Fig. 9 ) or PDCP layer duplication (e.g., as described in more detail in conjunction with Fig.10 depicted and described in more detail).

[0128] In an eighth operation 840, the network node 110 may send configuration information for sidelink carrier aggregation, and the second UE 120 may receive the configuration information. For example, the second UE 120 may receive the configuration information for sidelink carrier aggregation in a manner similar to that described above in conjunction with the seventh operation 835. For example, the network node 110 may send a dedicated sidelink configuration message (e.g., a sidelink RRC configuration) for the second UE 120. In some aspects, the configuration information may indicate that transmissions associated with the sidelink communication will be repeated for multiple component carriers. For example, the configuration information may indicate one or more sidelink component carrier lists (e.g., sl-rxcc-list4 and sl-txcc-list4) configured for the second UE 120. The one or more sidelink component carrier lists (e.g., sl-rxcc-list4 and sl-txcc-list4) may be based at least in part on component carriers indicated as supported by the second UE 120, such as in the fifth operation 825 (e.g., sl-rxcc-list2 and sl-txcc-list2).

[0129] Additionally, the configuration information may indicate whether to enable transmission repetition for sidelink communications (e.g., for an L2 destination identifier). For example, a radio resource control communication (e.g., including the configuration information) may indicate multiple component carriers (e.g., sl-rxcc-list4 and sl-txcc-list4) and may include an indication of the repetition type associated with the multiple component carriers.

[0130] In some aspects, the network node 110 may send a MAC-CE communication, and the first or second UE 120 may receive the MAC-CE communication, to activate or deactivate repetition or a repetition type on multiple component carriers for sidelink carrier aggregation. For example, the network node 110 may send a MAC-CE to the first UE 120 or the second UE 120 to activate repetition of transmissions associated with sidelink communications for multiple component carriers. For example, based at least in part on the component carriers indicated as supported by the first or second UE 120, such as in the fourth operation 820 (e.g., sl-rxcc-list1 and sl-txcc-list1) or in the fifth operation 825 (e.g., sl-rxcc-list2 and sl-txcc-list2), the MAC-CE may activate one or more sidelink component carrier lists for repetition (e.g., sl-rxcc-list5 and sl-txcc-list5). For another example, the MAC-CE may activate a repetition type, such as a MAC layer repetition (e.g., as combined with Fig. 9 ) or PDCP layer duplication (e.g., as described in more detail in conjunction with Fig.10 depicted and described in more detail).

[0131] In a ninth operation 845, the first UE 120 may send a sidelink buffer status report, and the network node 110 may receive the sidelink buffer status report. The sidelink buffer status report may include one or more channel busy ratio measurements associated with each component carrier in a plurality of component carriers configured for the first UE 120 (e.g., in sl-rxcc-list3 and sl-txcc-list3). For example, the first UE 120 may perform the one or more channel busy ratio measurements. The first UE 120 may send a sidelink buffer status report including an indication of one or more channel busy ratio measurements of component carriers configured for sidelink carrier aggregation for the first UE 120 (e.g., in sl-rxcc-list3 and sl-txcc-list3).

[0132] Similarly, in the tenth operation 850, the second UE 120 may send a sidelink buffer status report, and the network node 110 may receive the sidelink buffer status report. The sidelink buffer status report may include one or more channel busy ratio measurements associated with each component carrier of a plurality of component carriers configured for the second UE 120 (e.g., in sl-rxcc-list4 and sl-txcc-list4). For example, the second UE 120 may perform the one or more channel busy ratio measurements. The second UE 120 may send a sidelink buffer status report, which includes an indication of one or more channel busy ratio measurements of component carriers configured for sidelink carrier aggregation for the second UE 120 (e.g., in sl-rxcc-list4 and sl-txcc-list4). In this way, the network node 110 may receive indications of various channel busy ratio measurements of component carriers configured for sidelink carrier aggregation associated with a given sidelink communication.

[0133] This may enable the network node 110 to make an improved determination associated with which component carrier(s) to use for transmission of a given sidelink communication. For example, the network node 110 may determine one or more component carriers on which to transmit transmissions of the sidelink communication based at least in part on a channel busy ratio measurement received by the network node 110. For example, the network node 110 may select one or more component carriers from sl-rxcc-list3, sl-txcc-list3, sl-rxcc-list4, or sl-txcc-list4 based on the channel busy ratio measurement received by the network node 110. For another example, the network node 110 may determine a plurality of component carriers on which to transmit transmission repetitions of the sidelink communication based at least in part on a channel busy ratio measurement received by the network node 110. For example, the network node 110 may select a plurality of component carriers from sl-rxcc-list3, sl-txcc-list3, sl-rxcc-list4, or sl-txcc-list4 based on the channel busy ratio measurement result received by the network node 110.

[0134] In an eleventh operation 855, the network node 110 may send a DCI indicating one or more component carriers for transmission of sidelink communication, and the first UE 120 may receive the DCI. For example, the DCI may indicate multiple component carriers, and a packet (e.g., a transport block) is to be repeated on each of the multiple component carriers (e.g., on multiple component carriers). In some aspects, the DCI may include a bitmap (e.g., sl-cc-bitmap). The bitmap may include a corresponding bit associated with each of the multiple component carriers configured for sidelink carrier aggregation by the first UE 120 (e.g., a corresponding bit for each component carrier included in sl-rxcc-list3 or sl-txcc-list3). For example, if seven component carriers are configured for sidelink carrier aggregation by the first UE 120, the bitmap may include seven bits.

[0135] For example, a value associated with a bit (e.g., "0" or "1") may indicate whether the first UE 120 will use the component carrier associated with the bit to send packets associated with the sidelink communication and the L2 destination identifier. For example, a value of "0" may indicate that the first UE 120 will not use the component carrier for transmission, while a value of "1" may indicate that the first UE 120 will use the component carrier for transmission. The mapping of bits to component carriers may be indicated in configuration information (e.g., received by the first UE 120 in the seventh operation 835). For example, a bitmap may include four bits corresponding to {CC1, CC2, CC3, CC4}. If the bitmap included in the DCI indicates a value of {0, 1, 0, 1}, the first UE 120 may identify that CC2 and CC4 will be used for transmission (e.g., packets will be repeated on each of CC2 and CC4) and CC1 and CC3 will not be used for transmission. The network node 110 may send scheduling information (e.g., DCI) to schedule transmission blocks on the sidelink for transmission, with transmission repetitions as indicated by the bitmap. As described elsewhere herein, the network node 110 (or another network node) may select a component carrier to be associated with the transmission repetition based at least in part on a channel busy ratio measurement received by the network node 110. For example, in the case of a component carrier list {CC1, CC2, CC3, CC4}, if transmission repetitions may be performed on CC1 and CC3 or CC1 and CC4, then CC1 and CC3 may be selected if the CBR measurement on CC3 is lower than the CBR measurement on CC4.

[0136] In the twelfth operation 860, the first UE 120 may send sidelink communications via each of the multiple component carriers as indicated in the DCI. In some aspects, the multiple component carriers may include at least one component carrier in one or more component carriers supported by the first UE 120 for sidelink carrier aggregation (e.g., sl-rxcc-list1 or sl-txcc-list1 or sl-rxcc-list3 or sl-txcc-list3). For example, the sidelink communication may be associated with a transport block at the MAC layer or a PDCP packet at the PDCP layer. In the twelfth operation 860, the first UE 120 may send a transport block at the MAC layer or a PDCP packet at the PDCP layer on each of the multiple component carriers (e.g., on each component carrier indicated by a bitmap included in the DCI). In some aspects, the repeated transmission of the sidelink transmission may be based at least in part on repeated MAC PDUs. The repeated MAC PDUs may be associated with multiple component carriers, which may be associated with an L2 destination identifier. The repeat indication associated with the repeated transmission may be included in the MAC header or subheader of the repeated transmission. Fig. 9MAC layer repetition is described in more detail below. In some aspects, the repeated transmission of the sidelink transmission may be based at least in part on the repeated PDCP packet. The repeated PDCP packet may be used for multiple logical channels that are mapped to multiple component carriers associated with the L2 destination identifier. A repetition indication associated with the repeated transmission may be included in the PDCP header of the repeated transmission. Fig.10 Let's describe PDCP layer repetition in more detail.

[0137] Fig. 9 is a diagram illustrating an example 900 associated with repeating a sidelink transmission for sidelink carrier aggregation according to the present disclosure. 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 repeated using a MAC PDU on multiple carriers (e.g., some or all carriers) associated with a multicast or broadcast L2 destination identifier. 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 identifier, and repeat a transport block (e.g., TB(x)) on the multiple carriers. The first UE may insert a repeat indication (e.g., MACduplicate=1) in a MAC header or subheader. Repeated transport blocks on multiple carriers may correspond to repeated sidelink transmissions. A second UE (e.g., a first Rx UE) that does not support sidelink carrier aggregation may receive the transport block (e.g., TB(x)) on a carrier associated with the second UE (e.g., carrier i). A third UE (e.g., a second Rx UE) supporting sidelink carrier aggregation may receive the transport block (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 duplication indication (e.g., MACduplicate=1).

[0138] like Fig. 9As shown in , at a first UE (e.g., a Tx UE, which may be associated with carriers 0 to m), the MAC layer may be involved in scheduling and priority processing, multiplexing, carrier selection, and HARQ processing. The multiplexing may produce a transport block (e.g., TB(x)), which may be repeated using a MAC PDU or a sub-PDU, which may produce a repeated transport block (e.g., TB(x) repeated using a HARQ entity associated with multiple carriers for repetition (e.g., some or all of carriers 0 to m)). For example, the repeated transport blocks 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 (e.g., a first Rx UE, which may be associated with carrier i) that does not support sidelink carrier aggregation 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, which 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 duplicate transport blocks based at least in part on a repetition indication inserted in a MAC header of the duplicate transport blocks, thereby producing a single transport block to which demultiplexing is applied.

[0139] In some aspects, the third UE may determine transmission repetitions based at least in part on a repetition indication in a MAC header or subheader, a logical channel identifier (LCID), and source identifiers and destination identifier pairs of repeated MAC PDUs or MAC sub-PDUs received from multiple carriers. The MAC entity may receive a first MAC PDU or sub-PDU including a repetition indication in a MAC header or subheader and a first logical channel identifier and a first source identifier and destination identifier pair from a first component carrier, and may receive a second MAC PDU or sub-PDU including a repetition indication in a MAC header or subheader and a second logical channel identifier and a second source identifier and destination identifier pair from a second component carrier. For example, if the MAC entity successfully decodes the first MAC PDU or sub-PDU, and if the first logical channel identifier is the same as the second logical identifier (e.g., the same logical channel instance of the corresponding MAC SDU or the type of the corresponding MAC CE within the scope of the source identifier and destination identifier pair), and if the first source identifier and destination identifier pair is the same as the second source identifier and destination identifier pair (e.g., sent from the same UE (source identifier) ​​for the same sidelink communication (destination identifier)), the MAC entity may deliver the MAC 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 first or second MAC PDU or sub-PDU on the first or second component carrier may refresh the buffer), and send an ACK on the first component carrier and / or the second component carrier or may not send any NACK. For example, if the MAC entity does not successfully decode the first MAC PDU or sub PDU and does not successfully decode the second MAC PDU or sub PDU, and if the first logical channel identifier is the same as the second logical identifier and if the first source identifier and destination identifier pair is the same as the second source identifier and destination identifier pair for the same sidelink communication (destination identifier), 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 or second MAC PDU or sub PDU on the first or second component carrier may refresh the buffer), and send an ACK on the first component carrier and / or the second component carrier or may not send any NACK (e.g., if HARQ feedback is enabled).For another example, if the MAC entity does not successfully decode both the first MAC PDU or sub-PDU and the second MAC PDU or sub-PDU, and if the first logical channel identifier is the same as the second logical identifier, and if the first source identifier and destination identifier pair is the same as the second source identifier and destination identifier pair for the same sidelink communication (destination identifier), the MAC entity may send a NACK on the first or second component carrier (e.g., if HARQ feedback is enabled) and / or send an ACK on another component carrier (e.g., the HARQ entity associated with the other component carrier may refresh the buffer), 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 PDUs or sub-PDUs (e.g., based at least in part on an RSRP or signal-to-interference-plus-noise ratio (SINR) measurement of the PSSCH carrying the first or second MAC PDU or sub-PDU).

[0140] In some aspects, the first UE may determine retransmissions on one or more component carriers based at least in part on received ACKs or non-received NACKs (e.g., if HARQ feedback is enabled). For example, for repeated transmissions, if one or more ACKs are received from all RX UEs (e.g., each Rx UE of the group responds with ACK / NACK for HARQ feedback) or no NACK is received (e.g., the Rx UE responds with only NACK for HARQ feedback), the MAC entity may determine that there is no retransmission on any component carrier (e.g., the HARQ entity associated with repeated transmissions 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 that received one or more NACKs, while other HARQ entities associated with a component carrier that received one or more ACKs or did not receive a NACK may flush the buffer with repeated TBs. 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 a timeout or after reaching the maximum retransmissions allowed (e.g., as configured) for retransmissions on any component carrier corresponding to the repeated transmissions.

[0141] Fig.101 is a diagram illustrating an example 1000 associated with repeating a sidelink transmission for sidelink carrier aggregation according to the present disclosure. In some aspects, the sidelink transmission may be repeated at the PDCP layer via a repeated 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 repeated logical channels are mapped to multiple carriers (e.g., some or all of carriers 0 to carrier m).

[0142] A first UE (e.g., a Tx UE) that supports sidelink carrier aggregation may repeat PDCP packets on repeated logical channels (e.g., sidelink control channels (SCCH) 0 to SCCH m, or sidelink service channels (STCH) 0 to STCHm) mapped to some or all carriers, 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. Repeated PDCP packets on repeated logical channels mapped to multiple carriers may correspond to repeated sidelink transmissions. 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) that supports sidelink carrier aggregation may receive PDCP packets on repeated logical channels mapped to multiple carriers (e.g., some or all of carriers 0 to carrier m), and the third UE may determine to perform duplication removal based at least in part on the duplication indication (e.g., PDCPduplicate=1 or PDCP SN).

[0143] like Fig.10As shown in , at a first UE (e.g., a Tx UE, which may be associated with carrier 0 to carrier m), the PDCP layer may repeat PDCP packets. PDCP packet repetition may be based at least in part on a QoS flow, which may be associated with a PC5 side link (PC5-S) or an RRC layer or an SDAP layer. The repeated PDCP packets may also undergo scheduling or priority processing, multiplexing, carrier selection, and HARQ processing. The repeated PDCP packets may generate multiple transport blocks (e.g., TB(0), ..., TB(i), ..., TB(m) as shown in the figure), which may correspond to multiple carriers (e.g., some or all of carriers from carrier 0 to carrier m). A second UE that does not support sidelink carrier aggregation (e.g., a first Rx UE, which may be associated with carrier i) may receive a PDCP packet on a logical channel mapped to a single carrier associated with the second UE (e.g., carrier i), 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, which may be associated with carriers 0 to m) may receive a PDCP packet on a repeated logical channel mapped to multiple carriers (e.g., some or all of carriers 0 to m), wherein the PDCP packet may be derived from a received transport block (e.g., TB(0) to TB(m)). Before obtaining the PDCP packet, the received transport block may be subjected to HARQ processing, packet filtering, and demultiplexing. The third UE may determine to remove the duplicate PDCP packets based at least in part on a duplication indication (e.g., PPDCPduplicate=1 or PDCP SN) inserted in a PDCP header of the duplicate PDCP packets, thereby generating a single PDCP packet.

[0144] In some aspects, the third UE may determine to transmit a repetition based at least in part on a repetition indication in a PDCP header of the repeated PDCP PDU. The PDCP entity may receive a first PDCP PDU from a first repeated logical channel via a first repeated RLC entity, and may receive a second PDCP PDU from a second repeated logical channel via a second repeated RLC entity. For example, if the PDCP entity successfully receives a first PDCP PDU with a repetition 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 in the control plane or SDAP in the user plane), discard the second PDCP PDU, and for an acknowledgement mode (AM) DRB, send a PDCP status report to the first UE with a bitmap field set to "1" for the first and / or second PDCP SDU. For example, if 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 an AM DRB, send a PDCP status report to the first UE with a bitmap field set to "1" for the first and / or second PDCP SDU. For another example, if 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 an AM DRB, may send a PDCP status report to the first UE with a bitmap field set to "0" for the first and / or second PDCP SDU, respectively.

[0145] 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 repetitions of retransmissions based at least in part on a PDCP status report received from the Rx UE, wherein each PDCP status report includes a bitmap "0" or "1" corresponding to a PDCP SDU that is repeatedly transmitted. For example, if the bitmap of the first PDCP SDU associated with the first repeated logical channel mapped to the first component carrier is "0" and / or if the bitmap of the second PDCP SDU associated with the second repeated logical channel mapped to the second component carrier is "0" (e.g., logical channel i and logical channel j are mapped to component carrier i and component carrier j, respectively), the PDCP entity may determine repetitions of retransmissions on the first repeated logical channel and the second repeated logical channel corresponding to the first component carrier and the second component carrier (e.g., logical channel i and logical channel j are mapped to component carrier i and component carrier j, respectively).

[0146] Fig.11 is a flow diagram illustrating an example process 1100 associated with sidelink carrier aggregation, performed, for example, by a UE, according to the present disclosure. Example process 1100 is an example in which a UE (eg, UE 120) performs operations associated with sidelink carrier aggregation.

[0147] like Fig.11 As shown in , in some aspects, process 1100 may include: sending a first indication to a network node of at least one of: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with a sidelink communication, the first indication being associated with the sidelink communication (block 1110). For example, a UE (such as by using Fig.13 The communication manager 140 or the sending component 1304 depicted in the figure may send a first indication to the network node of at least one of the following: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with the sidelink communication, the first indication being associated with the sidelink communication, as described above.

[0148] like Fig.11 As further shown, in some aspects, process 1100 may include, based on sending the first indication, receiving from the network node a second indication that transmissions associated with the sidelink communication are to be repeated for a plurality of component carriers (block 1120). Fig.13 The communication manager 140 or receiving component 1302 depicted in FIG. 1 may receive a second indication from the network node that transmissions associated with the sidelink communication are to be repeated for multiple component carriers based on sending the first indication, as described above.

[0149] like Fig.11 As further shown, in some aspects, process 1100 may include, based on the second indication, sending the sidelink communication via each of a plurality of component carriers, the plurality of component carriers including at least one of the first one or more component carriers (block 1130). For example, a UE (such as by using Fig.13 The communication manager 140 or the sending component 1304 depicted in the figure may, based on the second indication, send the sidelink communication via each of a plurality of component carriers, the plurality of component carriers including at least one of the first one or more component carriers, as described above.

[0150] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below or in combination with one or more other processes described elsewhere herein.

[0151] In a first additional aspect, process 1100 includes obtaining, from an upper layer associated with the UE, information indicating at least one of: whether sidelink carrier aggregation is supported or the first one or more component carriers, wherein the first one or more component carriers are associated with one or more sidelink service types.

[0152] In a second additional aspect, alone or in combination with the first aspect, the sidelink communication is a broadcast communication or a multicast communication associated with a layer 2 destination identifier.

[0153] In a third additional aspect, alone or in combination with one or more of the first and second aspects, the first indication is included in a sidelink UE information communication.

[0154] In a fourth additional aspect, alone or in combination with one or more of the first to third aspects, whether sidelink carrier aggregation is supported or the first one or more component carriers associated with the sidelink communication are based at least in part on the capabilities of the UE.

[0155] In a fifth additional aspect, either alone or in combination with one or more of the first to fourth aspects, the first indication comprises an indication that sidelink carrier aggregation is not supported for a second one or more component carriers, and wherein receiving the second indication is at least partially based on not supporting sidelink carrier aggregation for the second one or more component carriers.

[0156] In a sixth additional aspect, either alone or in combination with one or more of the first to fifth aspects, the first indication is based at least in part on corresponding indications for a plurality of sidelink service types and corresponding component carriers associated with the plurality of sidelink service types.

[0157] In a seventh additional aspect, alone or in combination with one or more of the first to sixth aspects, process 1100 includes: receiving system information indicating support for sidelink carrier aggregation from the network node, wherein sending the first indication is at least partially based on receiving the system information.

[0158] In an eighth additional aspect, alone or in combination with one or more of the first to seventh aspects, the second indication is included in a radio resource control communication.

[0159] In a ninth additional aspect, alone or in combination with one or more of the first to eighth aspects, the radio resource control communication indicates the plurality of component carriers and includes an indication of a repetition type to be associated with the plurality of component carriers.

[0160] In a tenth additional aspect, either alone or in combination with one or more of the first to ninth aspects, the repetition type comprises a MAC layer repetition or a PDCP layer repetition.

[0161] In an eleventh additional aspect, alone or in combination with one or more of aspects one to ten, process 1100 comprises sending a side link buffer status report to the network node, wherein the side link buffer status report comprises one or more channel busy ratio measurements associated with each of the multiple component carriers.

[0162] In a twelfth additional aspect, alone or in combination with one or more of the first to eleventh aspects, the second indication is included in a DCI communication scheduling the sidelink communication.

[0163] In a thirteenth additional aspect, alone or in combination with one or more of the first to twelfth aspects, the DCI communication includes an indication of the multiple component carriers.

[0164] In a fourteenth additional aspect, either alone or in combination with one or more of the first to thirteenth aspects, the indication of the plurality of component carriers comprises a bitmap, and the bitmap comprises a respective bit associated with each of the plurality of component carriers.

[0165] In a fifteenth additional aspect, either alone or in combination with one or more of the first to fourteenth aspects, the sidelink communication is associated with a transport block or a PDCP packet, and sending the sidelink communication comprises sending the transport block or the PDCP packet on each of the multiple component carriers.

[0166] Although Fig.11 An example block diagram of process 1100 is shown, but in some aspects, the same Fig.11 The process 1100 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. Additionally or alternatively, two or more of the blocks in the process 1100 may be executed in parallel.

[0167] Fig.12 is a flow diagram illustrating an example process 1200 associated with sidelink carrier aggregation, performed, for example, by a network node, in accordance with the present disclosure. The example process 1200 is an example in which a network node (eg, network node 110) performs operations associated with sidelink carrier aggregation.

[0168] like Fig.12 As shown, in some aspects, process 1200 may include receiving one or more indications of at least one of: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with sidelink communication, the one or more indications associated with the sidelink communication and one or more UEs (block 1210). For example, a network node (such as by using Fig.14The communication manager 150 or receiving component 1402 depicted in the figure may receive one or more indications of at least one of the following: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with the sidelink communication, the one or more indications being associated with the sidelink communication and one or more UEs, as described above.

[0169] like Fig.12 As further shown, in some aspects, process 1200 may include sending a communication to a UE of the one or more UEs indicating that transmissions associated with the sidelink communication are to be repeated for a plurality of component carriers, the plurality of component carriers including at least one component carrier of the first one or more component carriers (block 1220). For example, a network node (such as by using Fig.14 The communication manager 150 or the sending component 1404 depicted in the figure may send a communication to a UE in the one or more UEs, indicating that the transmission associated with the sidelink communication will be repeated for multiple component carriers, including at least one component carrier in the first one or more component carriers, as described above.

[0170] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below or in combination with one or more other processes described elsewhere herein.

[0171] In a first additional aspect, the sidelink communication is a broadcast communication or a multicast communication associated with a layer 2 destination identifier.

[0172] In a second additional aspect, alone or in combination with the first aspect, the indication is included in a sidelink UE information communication.

[0173] In a third additional aspect, alone or in combination with one or more of the first and second aspects, the indication is based at least in part on capabilities of the one or more UEs.

[0174] In a fourth additional aspect, either alone or in combination with one or more of the first to third aspects, the indication includes an indication that sidelink carrier aggregation is not supported for a third one or more component carriers, and sending the communication is based at least in part on not supporting sidelink carrier aggregation for the third one or more component carriers, the communication indicating that the transmission associated with the sidelink communication will be repeated for the multiple component carriers.

[0175] In a fifth additional aspect, alone or in combination with one or more of the first to fourth aspects, process 1200 includes: sending system information indicating support for sidelink carrier aggregation, wherein receiving the indication is at least partially based on sending the system information.

[0176] In a sixth additional aspect, alone or in combination with one or more of the first to fifth aspects, the communication is included in a radio resource control communication.

[0177] In a seventh additional aspect, alone or in combination with one or more of the first to sixth aspects, the radio resource control communication indicates the plurality of component carriers and includes an indication of a repetition type to be associated with the plurality of component carriers.

[0178] In an eighth additional aspect, alone or in combination with one or more of the first to seventh aspects, the repetition type comprises a MAC layer repetition or a PDCP layer repetition.

[0179] In a ninth additional aspect, alone or in combination with one or more of aspects one to eight, process 1200 comprises: receiving a side link buffer status report comprising one or more channel busy ratio measurements associated with a corresponding component carrier among the plurality of component carriers; and sending a DCI communication that schedules the side link communication to be sent via a second one or more component carriers among the plurality of component carriers, wherein the second one or more component carriers are selected based at least in part on the one or more channel busy ratio measurements.

[0180] In a tenth additional aspect, either alone or in combination with one or more of the first to ninth aspects, the communication is included in a DCI communication that schedules the sidelink communication.

[0181] In an eleventh additional aspect, alone or in combination with one or more of the first to tenth aspects, the DCI communication includes an indication of a second one or more component carriers of the plurality of component carriers.

[0182] In a twelfth additional aspect, alone or in combination with one or more of the first to eleventh aspects, the indication comprises a bitmap, and the bitmap comprises a respective bit associated with each component carrier of the plurality of component carriers.

[0183] In a thirteenth additional aspect, alone or in combination with one or more of aspects one to twelfth, receiving the indication comprises receiving a first indication of the first one or more component carriers, and receiving a second indication that another UE among the one or more UEs supports a second one or more component carriers for the sidelink communication, and sending the communication is at least partially based on the mutual exclusion of the first one or more component carriers and the second one or more component carriers.

[0184] Although Fig.12 An example block diagram of process 1200 is shown, but in some aspects, the same Fig.12The process 1200 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. Additionally or alternatively, two or more of the blocks in the process 1200 may be executed in parallel.

[0185] Fig.13 1 is a diagram of an example apparatus 1300 for wireless communication according to the present disclosure. Apparatus 1300 may be a UE, or a UE may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302, a sending component 1304, and a communication manager 140, which may communicate with each other (e.g., via one or more buses). As shown, apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a network node, or another wireless communication device) using receiving component 1302 and sending component 1304.

[0186] In some aspects, the apparatus 1300 may be configured to perform Figures 8 to 10 Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as Fig.11 In some aspects, the apparatus 1300 may include the process 1100 described above in combination with Figure 2 One or more components of a UE are described.

[0187] The receiving component 1302 may receive communications from the device 1306, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1302 may provide the received communications to one or more other components of the device 1300, such as the communications manager 140. In some aspects, the receiving component 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) on the received communications and may provide the processed signals to one or more other components. In some aspects, the receiving component 1302 may include the above in combination with Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0188] The transmitting component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1306. In some aspects, the communication manager 140 may generate communications and may transmit the generated communications to the transmitting component 1304 for transmission to the device 1306. In some aspects, the transmitting component 1304 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 1306. In some aspects, the transmitting component 1304 may include the above in combination with Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.

[0189] The communication manager 140 may send to the network node or may cause the sending component 1304 to send to the network node a first indication of at least one of the following: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with the sidelink communication, the first indication being associated with the sidelink communication. The communication manager 140 may receive from the network node a second indication that the transmission associated with the sidelink communication will be repeated for multiple component carriers based on sending the first indication, or may cause the receiving component 1302 to receive from the network node the second indication based on sending the first indication. The communication manager 140 may send the sidelink communication via each of the multiple component carriers based on the second indication, the multiple component carriers including at least one of the first one or more component carriers, or may cause the sending component 1304 to send the sidelink communication via each of the multiple component carriers based on the second indication. In some aspects, the communication manager 140 may perform one or more operations described elsewhere herein as being performed by one or more components of the communication manager 140.

[0190] The communication manager 140 may include the above combined Figure 2 The controller / processor, memory, or combination thereof of the UE described herein. In some aspects, the communication manager 140 includes a component set, such as obtaining component 1308, or a combination thereof. Alternatively, the component set may be separate and distinct from the communication manager 140. In some aspects, one or more components in the component set may include the above-mentioned components. Figure 2The controller / processor, memory, or combination thereof of the described UE may be implemented therein. Additionally or alternatively, one or more components in the component set may be at least partially implemented as software stored in the memory. For example, a component (or a portion of a component) may be implemented as an instruction or code that is stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0191] The sending component 1304 may send to the network node a first indication of at least one of: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with the sidelink communication, the first indication being associated with the sidelink communication. The receiving component 1302 may receive from the network node a second indication that the transmission associated with the sidelink communication will be repeated for multiple component carriers based on sending the first indication. The sending component 1304 may send the sidelink communication via each of the multiple component carriers based on the second indication, the multiple component carriers including at least one of the first one or more component carriers.

[0192] The obtaining component 1308 may obtain information from upper layers associated with the UE indicating at least one of: whether sidelink carrier aggregation is supported or the first one or more component carriers, wherein the first one or more component carriers are associated with one or more sidelink service types.

[0193] The receiving component 1302 can receive system information from the network node indicating support for sidelink carrier aggregation, wherein sending the first indication is based at least in part on receiving the system information.

[0194] Transmitting component 1304 can transmit a sidelink buffer status report to the network node, wherein the sidelink buffer status report includes one or more channel busy ratio measurements associated with respective component carriers of the plurality of component carriers.

[0195] Fig.13 The number and arrangement of components shown in the figure are provided as examples. In practice, Fig.13 There may be additional components, fewer components, different components, or differently arranged components than those shown in FIG. Fig.13 Two or more components shown in may be implemented in a single component, or Fig.13 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.13 The assembly of (one or more) components shown in the executable is described as being composed of Fig.13 One or more functions performed by another set of components shown in .

[0196] Fig.14 1 is a diagram of an example apparatus 1400 for wireless communication according to the present disclosure. Apparatus 1400 may be a network node, or a network node may include apparatus 1400. In some aspects, apparatus 1400 includes a receiving component 1402, a sending component 1404, and a communication manager 150, which may communicate with each other (e.g., via one or more buses). As shown, apparatus 1400 may communicate with another apparatus 1406 (such as a UE, a network node, or another wireless communication device) using receiving component 1402 and sending component 1404.

[0197] In some aspects, the apparatus 1400 may be configured to perform Figures 8 to 10 Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as Fig.12 In some aspects, the apparatus 1400 may include the process 1200 described above in combination with Figure 2 One or more components of a described network node.

[0198] The receiving component 1402 may receive communications from the device 1406, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1402 may provide the received communications to one or more other components of the device 1400, such as the communications manager 150. In some aspects, the receiving component 1402 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) on the received communications and may provide the processed signals to one or more other components. In some aspects, the receiving component 1402 may include the above in combination with Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, receiving component 1402 may include or be included in an interface for communicating with another device (such as a network node).

[0199] The transmission component 1404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1406. In some aspects, the communication manager 150 may generate communications and may transmit the generated communications to the transmission component 1404 for transmission to the device 1406. In some aspects, the transmission component 1404 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 1406. In some aspects, the transmission component 1404 may include the above in combination with Figure 2One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmitting component 1404 may be co-located in a transceiver with the receiving component 1402. In some aspects, the transmitting component 1404 may include an interface for communicating with another device (such as a network node) or be included in the interface. In some aspects, the transmitting component 1404 or the receiving component 1402 may facilitate communication with one or more network nodes. For example, the transmitting component 1404 or the receiving component 1402 may not perform direct radio communication with the UE. In some other aspects, the transmitting component 1404 or the receiving component 1402 may perform direct radio communication with the UE.

[0200] The communication manager 150 may receive or may cause the receiving component 1402 to receive one or more indications of at least one of the following: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with the sidelink communication, the one or more indications being associated with the sidelink communication and one or more UEs. The communication manager 150 may send a communication to a UE in the one or more UEs, or may cause the sending component 1404 to send a communication to a UE in the one or more UEs, the communication indicating that the transmission associated with the sidelink communication will be repeated for multiple component carriers, the multiple component carriers including at least one component carrier in the first one or more component carriers. In some aspects, the communication manager 150 may perform one or more operations described elsewhere herein as being performed by one or more components of the communication manager 150.

[0201] The communication manager 150 may include the above combined Figure 2 The controller / processor, memory, scheduler, communication unit, or combination thereof of the network node described herein. In some aspects, the communication manager 150 includes a component set, such as determining component 1408, or a combination thereof. Alternatively, the component set may be separate and distinct from the communication manager 150. In some aspects, one or more components in the component set may include the components described above in conjunction with Figure 2 The controller / processor, memory, scheduler, communication unit, or combination thereof of the described network node may be implemented in or within. Additionally or alternatively, one or more components in the component set may be at least partially implemented as software stored in the memory. For example, a component (or a portion of a component) may be implemented as an instruction or code that is stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0202] The receiving component 1402 may receive one or more indications of at least one of: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with a sidelink communication, the one or more indications being associated with the sidelink communication and one or more UEs. The transmitting component 1404 may transmit a communication to a UE of the one or more UEs, the communication indicating that the transmission associated with the sidelink communication is to be repeated for a plurality of component carriers, the plurality of component carriers including at least one component carrier of the first one or more component carriers.

[0203] Determining component 1408 can determine where transmissions associated with the sidelink communication are to be repeated based on the one or more indications.

[0204] Transmitting component 1404 can transmit system information indicating support for the sidelink carrier aggregation, wherein receiving the indication is based at least in part on transmitting the system information.

[0205] Receiving component 1402 can receive a sidelink buffer status report, wherein the sidelink buffer status report includes one or more channel busy ratio measurements associated with respective component carriers of the plurality of component carriers.

[0206] Transmitting component 1404 can transmit a DCI communication scheduling a sidelink communication to be transmitted via a second one or more component carriers of the plurality of component carriers, wherein the second one or more component carriers are selected based at least in part on the one or more channel busy ratio measurements.

[0207] Fig.14 The number and arrangement of components shown in the figure are provided as examples. In practice, Fig.14 There may be additional components, fewer components, different components, or differently arranged components than those shown in FIG. Fig.14 Two or more components shown in may be implemented in a single component, or Fig.14 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.14 The assembly of (one or more) components shown in the executable is described as being composed of Fig.14 One or more functions performed by another set of components shown in .

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

[0209] Aspect 1: A method for wireless communication performed by a user equipment (UE), the method comprising: sending a first indication to a network node of at least one of the following: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with sidelink communication, the first indication being associated with the sidelink communication; based on sending the first indication, receiving a second indication from the network node that the transmission associated with the sidelink communication will be repeated for multiple component carriers; and based on the second indication, sending the sidelink communication via each of a plurality of component carriers, the plurality of component carriers including at least one of the first one or more component carriers.

[0210] Aspect 2: According to the method described in Aspect 1, the method also includes: obtaining information indicating at least one of the following items from an upper layer associated with the UE: whether sidelink carrier aggregation is supported or the first one or more component carriers, wherein the first one or more component carriers are associated with one or more sidelink service types.

[0211] Aspect 3: The method according to any one of aspects 1 to 2, wherein the sidelink communication is a broadcast communication or a multicast communication associated with a layer 2 destination identifier.

[0212] Aspect 4: A method according to any one of aspects 1 to 3, wherein the first indication is included in a sidelink UE information communication.

[0213] Aspect 5: The method according to any one of aspects 1 to 4, wherein whether sidelink carrier aggregation is supported or the first one or more component carriers associated with the sidelink communication are based at least in part on the capabilities of the UE.

[0214] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the first indication includes an indication that sidelink carrier aggregation is not supported for a second one or more component carriers, and wherein receiving the second indication is at least partially based on not supporting sidelink carrier aggregation for the second one or more component carriers.

[0215] Aspect 7: A method according to any one of aspects 1 to 6, wherein the first indication is based at least in part on respective indications for a plurality of sidelink service types and respective component carriers associated with the plurality of sidelink service types.

[0216] Aspect 8: According to any one of aspects 1 to 7, the method further comprises: receiving system information indicating support for sidelink carrier aggregation from the network node, wherein sending the first indication is at least partly based on receiving the system information.

[0217] Aspect 9: The method according to any one of aspects 1 to 8, wherein the second indication is included in a radio resource control communication.

[0218] Aspect 10: The method of aspect 9, wherein the radio resource control communication indicates the plurality of component carriers and includes an indication of a repetition type to be associated with the plurality of component carriers.

[0219] Aspect 11: The method according to aspect 10, wherein the repetition type comprises a medium access control (MAC) layer repetition or a packet data convergence protocol (PDCP) layer repetition.

[0220] Aspect 12: According to the method described in any one of Aspects 1 to 11, the method further includes: sending a side link buffer status report to the network node, wherein the side link buffer status report includes one or more channel busy ratio measurements associated with each component carrier among the multiple component carriers.

[0221] Aspect 13: A method according to any one of aspects 1 to 8 and 12, wherein the second indication is included in a downlink control information (DCI) communication scheduling the sidelink communication.

[0222] Aspect 14: The method according to aspect 13, wherein the DCI communication includes an indication of the plurality of component carriers.

[0223] Aspect 15: The method according to aspect 14, wherein the indication of the plurality of component carriers comprises a bitmap, and wherein the bitmap comprises a respective bit associated with each component carrier of the plurality of component carriers.

[0224] Aspect 16: A method according to any one of Aspects 1 to 15, wherein the sidelink communication is associated with a transport block or a packet data convergence protocol (PDCP) packet, and wherein sending the sidelink communication includes sending the transport block or the PDCP packet on each component carrier of the multiple component carriers.

[0225] Aspect 17: A method of wireless communication performed by a network node, the method comprising: receiving one or more indications of at least one of the following: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with a sidelink communication, the one or more indications being associated with the sidelink communication and one or more user equipment (UE); and sending communications to a UE among the one or more UEs, the communication indicating that the transmission associated with the sidelink communication will be repeated for multiple component carriers, the multiple component carriers including at least one of the first one or more component carriers.

[0226] Aspect 18: The method according to aspect 17, wherein the sidelink communication is a broadcast communication or a multicast communication associated with a layer 2 destination identifier.

[0227] Aspect 19: A method according to any one of Aspects 17 to 18, wherein the indication is included in a sidelink UE information communication.

[0228] Aspect 20: A method according to any one of aspects 17 to 19, wherein the indication is based at least in part on capabilities of the one or more UEs.

[0229] Aspect 21: According to the method described in any one of Aspects 17 to 20, the indication includes an indication that sidelink carrier aggregation is not supported for a third one or more component carriers, and wherein sending the communication is at least partially based on the fact that sidelink carrier aggregation is not supported for the third one or more component carriers, and the communication indicates that the sending associated with the sidelink communication will be repeated for the multiple component carriers.

[0230] Aspect 22: According to any one of aspects 17 to 21, the method further comprises: sending system information indicating support for sidelink carrier aggregation, wherein receiving the indication is at least partly based on sending the system information.

[0231] Aspect 23: The method according to any one of aspects 17 to 22, wherein the communication is included in a radio resource control communication.

[0232] Aspect 24: The method of aspect 23, wherein the radio resource control communication indicates the plurality of component carriers and includes an indication of a repetition type to be associated with the plurality of component carriers.

[0233] Aspect 25: The method according to aspect 24, wherein the repetition type comprises a medium access control (MAC) layer repetition or a packet data convergence protocol (PDCP) layer repetition.

[0234] Aspect 26: According to the method described in any one of Aspects 17 to 25, the method further includes: receiving a side link buffer status report, wherein the side link buffer status report includes one or more channel busy ratio measurements associated with each of the multiple component carriers; and sending downlink control information (DCI) communication for scheduling side link communications to be sent via a second one or more component carriers among the multiple component carriers, wherein the second one or more component carriers are selected at least in part based on the one or more channel busy ratio measurements.

[0235] Aspect 27: A method according to any one of aspects 17 to 22 and 26, wherein the communication is included in a downlink control information (DCI) communication that schedules the sidelink communication.

[0236] Aspect 28: The method according to aspect 27, wherein the DCI communication includes an indication of a second one or more component carriers of the plurality of component carriers.

[0237] Aspect 29: The method of aspect 28, wherein the indication comprises a bitmap, and wherein the bitmap comprises a respective bit associated with each component carrier of the plurality of component carriers.

[0238] Aspect 30: A method according to any one of Aspects 17 to 29, wherein receiving the indication includes: receiving a first indication of the first one or more component carriers; and receiving a second indication of a second one or more component carriers supported by another UE among the one or more UEs for the sidelink communication; and wherein sending the communication is at least partially based on the mutual exclusion of the first one or more component carriers and the second one or more component carriers.

[0239] Aspect 31: An apparatus for performing wireless communications at a device, the apparatus 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 16.

[0240] Aspect 32: 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 16.

[0241] Aspect 33: 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 16.

[0242] Aspect 34: 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 16.

[0243] Aspect 35: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, 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 16.

[0244] Aspect 36: An apparatus for performing wireless communications at a device, the apparatus 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 17 to 30.

[0245] Aspect 37: 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 17 to 30.

[0246] Aspect 38: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 17 to 30.

[0247] Aspect 39: 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 17 to 30.

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

[0249] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0250] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware or hardware and software. "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 programs, threads of execution, procedures or functions, etc., whether it is described in software, firmware, middleware, microcode, hardware description language or other terms. As used herein, "processor" is implemented with hardware or a combination of hardware and software. It will be obvious that the system or method described herein can be implemented in different forms of hardware or a combination of hardware and software. The actual dedicated control hardware or software code for implementing these systems or methods does not limit various aspects. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software codes, because those skilled in the art will understand that software and hardware can be designed to implement these systems or methods based at least in part on the description herein.

[0251] 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.

[0252] Although a specific combination of features is stated in the claims 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 not specifically described in the claims or 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 (which includes a single member). As an example, "at least one of the following: 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 (e.g., 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).

[0253] Any element, action or instruction used herein should not be interpreted as key or necessary, unless clearly stated so. In addition, as used herein, the articles "one" and "a kind of" are 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 with 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 want to refer to a project, then use the phrase "only one" or similar terms. In addition, as used herein, the terms "having", "containing", "comprising" and similar terms are intended to be open terms that do not limit the elements (for example, element "comprising" A can also contain B) that they modify. In addition, the phrase "based on" is intended to represent "based at least in part", unless otherwise clearly stated. Furthermore, as used herein, the term "or" when used consecutively is intended to be inclusive and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: at least one memory; and at least one processor, the at least one processor being communicatively coupled to the at least one memory, the at least one processor being configured to cause the UE to: sending, to a network node, a first indication of at least one of: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with sidelink communications, the first indication being associated with the sidelink communications; receiving, based on sending the first indication, from the network node a second indication that transmissions associated with the sidelink communication are to be repeated for a plurality of component carriers; as well as Based on the second indication, the sidelink communication is sent via each component carrier of a plurality of component carriers, the plurality of component carriers including at least one component carrier of the first one or more component carriers.

2. The UE according to claim 1, wherein the at least one processor is further configured to cause the UE to obtain information indicating at least one of the following from an upper layer associated with the UE: whether sidelink carrier aggregation is supported or the first one or more component carriers, wherein the first one or more component carriers are associated with one or more sidelink service types.

3. The UE of claim 1, wherein the sidelink communication is a broadcast communication or a multicast communication associated with a layer 2 destination identifier.

4. The UE of claim 1, wherein the first indication is included in a sidelink UE information communication.

5. The UE of claim 1, wherein whether sidelink carrier aggregation is supported or the first one or more component carriers associated with the sidelink communication is based at least in part on capabilities of the UE.

6. The UE of claim 1 , wherein the first indication comprises an indication that sidelink carrier aggregation is not supported for a second one or more component carriers, and wherein receiving the second indication is based at least in part on not supporting sidelink carrier aggregation for the second one or more component carriers.

7. The UE of claim 1, wherein the first indication is based at least in part on respective indications for a plurality of sidelink service types and respective component carriers associated with the plurality of sidelink service types.

8. The UE of claim 1, wherein the second indication is included in a radio resource control communication.

9. The UE of claim 8, wherein the radio resource control communication indicates the plurality of component carriers and includes an indication of a repetition type to be associated with the plurality of component carriers.

10. The UE of claim 1, wherein the at least one processor is further configured to cause the UE to send a sidelink buffer status report to the network node, wherein the sidelink buffer status report comprises one or more channel busy ratio measurements associated with each of the plurality of component carriers.

11. The UE of claim 1, wherein the second indication is included in a downlink control information (DCI) communication scheduling the sidelink communication.

12. The UE of claim 11, wherein the DCI communication comprises an indication of the plurality of component carriers, and wherein the indication of the plurality of component carriers comprises a bitmap, and wherein the bitmap comprises a respective bit associated with each of the plurality of component carriers.

13. A network node for wireless communication, the network node comprising: at least one memory; and at least one processor, the at least one processor being communicatively coupled to the at least one memory, the at least one processor being configured to cause the network node to: receiving one or more indications of at least one of: whether sidelink carrier aggregation or a first one or more component carriers associated with sidelink communications are supported, the one or more indications being associated with the sidelink communications and one or more user equipment (UEs); as well as A communication is transmitted for a UE of the one or more UEs, the communication indicating that transmissions associated with the sidelink communication are to be repeated for a plurality of component carriers including at least one of the first one or more component carriers.

14. The network node of claim 13, wherein the at least one processor is further configured to cause the network node to send system information indicating support for the sidelink carrier aggregation, wherein receiving the one or more indications is based at least in part on sending the system information.

15. The network node according to claim 13, wherein: In order for the network node to receive the one or more indications, the at least one processor is configured to cause the network node to: receiving a first indication of first one or more component carriers supported by the UE for sidelink communication; as well as receiving a second indication of second one or more component carriers supported by another UE of the one or more UEs for the sidelink communication; and Wherein sending the communication is based at least in part on the first one or more component carriers and the second one or more component carriers being mutually exclusive.

16. A method of wireless communication performed by a user equipment (UE), the method comprising: sending, to a network node, a first indication of at least one of: whether sidelink carrier aggregation is supported or a first one or more component carriers associated with sidelink communications, the first indication being associated with the sidelink communications; receiving, based on sending the first indication, from the network node a second indication that transmissions associated with the sidelink communication are to be repeated for a plurality of component carriers; as well as Based on the second indication, the sidelink communication is sent via each component carrier of a plurality of component carriers, the plurality of component carriers including at least one component carrier of the first one or more component carriers.

17. The method according to claim 16, further comprising: Information indicating at least one of whether sidelink carrier aggregation or the first one or more component carriers is supported is obtained from an upper layer associated with the UE, wherein the first one or more component carriers are associated with one or more sidelink service types.

18. The method of claim 16, wherein the sidelink communication is a broadcast communication or a multicast communication associated with a layer 2 destination identifier.

19. The method of claim 16, wherein the first indication is included in a sidelink UE information communication.

20. The method of claim 16, wherein whether sidelink carrier aggregation is supported or the first one or more component carriers associated with the sidelink communications is based at least in part on capabilities of the UE.

21. The method of claim 16, wherein the first indication comprises an indication that sidelink carrier aggregation is not supported for a second one or more component carriers, and wherein receiving the second indication is based at least in part on not supporting sidelink carrier aggregation for the second one or more component carriers.

22. The method of claim 16, wherein the first indication is based at least in part on respective indications for a plurality of sidelink service types and respective component carriers associated with the plurality of sidelink service types.

23. The method of claim 16, wherein the second indication is included in a radio resource control communication.

24. The method of claim 23, wherein the radio resource control communication indicates the plurality of component carriers and includes an indication of a repetition type to be associated with the plurality of component carriers.

25. The method according to claim 16, further comprising: A sidelink buffer status report is sent to the network node, wherein the sidelink buffer status report includes one or more channel busy ratio measurements associated with respective component carriers of the plurality of component carriers.

26. The method of claim 16, wherein the second indication is included in a downlink control information (DCI) communication scheduling the sidelink communication.

27. The method of claim 26, wherein the DCI communication comprises an indication of the plurality of component carriers, and wherein the indication of the plurality of component carriers comprises a bitmap, and wherein the bitmap comprises a respective bit associated with each of the plurality of component carriers.

28. A method of wireless communication performed by a network node, the method comprising: receiving one or more indications of at least one of: whether sidelink carrier aggregation or a first one or more component carriers associated with sidelink communications are supported, the one or more indications being associated with the sidelink communications and one or more user equipment (UEs); as well as A communication is transmitted to a UE of the one or more UEs, the communication indicating that transmissions associated with the sidelink communication are to be repeated for a plurality of component carriers including at least one of the first one or more component carriers.

29. The method according to claim 28, further comprising: System information indicating support for the sidelink carrier aggregation is transmitted, wherein receiving the one or more indications is based at least in part on transmitting the system information.

30. The method of claim 28, wherein receiving the one or more indications comprises: receiving a first indication of first one or more component carriers supported by the UE for sidelink communication; as well as receiving a second indication of second one or more component carriers supported by another UE of the one or more UEs for the sidelink communication; and Wherein sending the communication is based at least in part on the first one or more component carriers and the second one or more component carriers being mutually exclusive.

Images