Carrier aggregation for sidelink communications

By configuring side link carrier frequency and cross-carrier scheduling in side link communication, the problem of low UE resource allocation efficiency is solved, the efficiency and data rate of side link communication are improved, and it is suitable for a variety of application scenarios.

CN118985170APending Publication Date: 2024-11-19LENOVO (SINGAPORE) PTE LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380033290.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-11
Filing Date
2023-04-04
Publication Date
2024-11-19

AI Technical Summary

Technical Problem

In side link communication, it is difficult for user equipment (UE) to independently determine and configure carrier frequency, resulting in low resource allocation efficiency and unable to quickly obtain resources for side link communication.

Method used

By determining and configuring the side link carrier frequency between the UE and the base station, using cell-specific and UE-specific signaling, the carrier frequency is configured based on ascending order of ARFCN, and cross-carrier scheduling and HARQ reporting are realized through the association of the serving cell with the carrier frequency. , to provide performance indication of side link CA.

Benefits of technology

It realizes that UE quickly and efficiently obtains side link CA resources, improves the efficiency and data rate of side link communication, and is suitable for commercial and intelligent transportation applications.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118985170A_ABST
    Figure CN118985170A_ABST
Patent Text Reader

Abstract

Aspects of the present disclosure relate to implementation of CA for sidelink communications. Techniques for determining and configuring sidelink carrier frequencies for cross-carrier scheduling for sidelink CA communications are described. For example, cell-specific and / or UE-specific scheduling of carrier frequencies for CA may be implemented. Implementations also enable sidelink HARQ reporting to a wireless network to provide an indication of sidelink CA performance.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Related Applications

[0002] This application claims priority to U.S. patent application serial number 63 / 329,754, filed on April 11, 2022, entitled “CARRIER AGGREGATION FOR SIDELINK COMMUNICATION,” and U.S. patent application serial number 63 / 329,761, filed on April 11, 2022, entitled “CARRIER AGGREGATION FOR SIDELINK COMMUNICATION,” the disclosures of which are incorporated herein by reference in their entirety. Technical Field

[0003] The present disclosure relates to wireless communications, and more particularly to sidelink communications. Background Art

[0004] A wireless communication system may include one or more network communication devices, such as a base station, which may be further referred to as an eNodeB (eNB), a next generation NodeB (gNB) or other suitable terms. Each network communication device, such as a base station, may support wireless communication of one or more user communication devices, which may be further referred to as a user equipment (UE) or other suitable terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system, such as time resources (e.g., symbols, time slots, sub-time slots, mini-time slots, aggregated time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers). In addition, a wireless communication system may support wireless communication across various radio access technologies (RATs), including third generation (3G) RATs, fourth generation (4G) RATs, fifth generation (5G) RATs, and other suitable RATs other than 5G. In some cases, a wireless communication system may be a non-terrestrial network (NTN), which may support various communication devices for wireless communication in the NTN. For example, the NTN may include network entities on non-ground vehicles, such as satellites, unmanned aerial vehicles (UAVs), and high altitude platform systems (HAPS), as well as network entities on the ground, such as gateway entities capable of transmitting and receiving over long distances.

[0005] In addition to wireless communication using network infrastructure, UEs may also utilize sidelink communication for direct device-to-device communication. For example, sidelink communication enables UEs to exchange wireless signals directly between devices, such as independently of network infrastructure components, such as base stations. Summary of the invention

[0006] Implementations of carrier aggregation (CA) for sidelink communications are described, such as in connection with methods, apparatus, and systems supporting CA for sidelink communications. For example, aspects of the present disclosure are directed to a manner for determining and configuring a sidelink carrier frequency for cross-carrier scheduling for sidelink CA communications. For example, cell-specific and / or UE-specific scheduling of carrier frequencies for CA can be implemented. Implementations also enable reporting to a wireless network sidelink hybrid automatic repeat request (HARQ) to provide an indication of sidelink CA performance.

[0007] Therefore, by enabling UEs to exchange CA capability information (e.g., primary carrier frequency and secondary carrier frequency) for sidelink communication, the described technology enables the UE to quickly and efficiently obtain resources for sidelink CA and participate in CA for sidelink communication using the allocated resources.

[0008] Some implementations of the methods and apparatus described herein may include wireless communication at a device (e.g., a UE), and the device determines, at a first UE, a sidelink carrier frequency that can be used to implement CA for sidelink communication; identifies at least one primary sidelink carrier frequency and at least one secondary sidelink carrier frequency from the sidelink carrier frequencies; and sends data to a second UE using the at least one primary sidelink carrier frequency and the at least one secondary sidelink carrier frequency.

[0009] In some implementations of the methods and apparatus described herein, a sidelink carrier frequency is identified based on one or more of cell-specific signaling received from a network node, UE-specific signaling received from a network node, or a pre-configuration of the UE; the sidelink carrier frequencies are configured in ascending order of absolute radio frequency channel numbers (ARFCNs); and further comprises receiving from the network node a mapping of one or more of the sidelink carrier frequencies to one or more service types operable for receiving sidelink communications, wherein the mapping is based at least in part on priority information of the service type; and further comprises determining the sidelink carrier frequency based on an association of a serving cell of the UE with the sidelink carrier frequency; wherein the association of the serving cell of the UE with the sidelink carrier frequency is the same as the association of a primary cell of the UE with the sidelink carrier frequency; and further comprises: receiving signaling comprising: one or more sidelink carrier frequencies associated with one or more synchronization signal blocks (SSBs); and receiving one or more SSBs via the one or more sidelink carrier frequencies for synchronization of at least one primary sidelink carrier frequency and at least one secondary sidelink carrier frequency.

[0010] In some implementations of the methods and apparatus described herein, the one or more sidelink carrier frequencies associated with one or more SSBs include: at least one primary sidelink carrier frequency; wherein the sidelink carrier frequency is identified based on UE-specific signaling received from a network node, and wherein the UE-specific signaling, and wherein the UE-specific signaling includes one or more of the following: configuration for one or more sidelink synchronization carrier frequencies; one or more priority values ​​for the sidelink carrier frequencies; or mapping information for mapping the sidelink carrier frequencies to the sidelink synchronization carrier frequencies; further comprising determining, based on a signal transmission from a second UE, a sidelink carrier frequency that can be used to implement CA for sidelink communication; and further comprising sending Broadcast, which broadcast identifier can be used to implement one or more of the side link carrier frequencies of CA for side link communication; also includes: generating HARQ feedback based on transmission through at least one primary side link carrier frequency and at least one secondary side link carrier frequency; and sending the side link HARQ to the network node; also includes sending the side link HARQ together with the downlink HARQ to the network node; also includes sending the side link HARQ via the physical uplink control channel (PUCCH) field in the downlink control information (DCI); also includes sending the side link HARQ based on the ascending order of at least one primary side link carrier frequency and at least one secondary side link carrier frequency in the side link carrier frequency index.

[0011] Some implementations of the methods and apparatus described herein may include wireless communication at a device (e.g., a UE), and the device receiving cross-carrier scheduling information, the cross-carrier scheduling information including a scheduling physical downlink control channel (PDCCH) carrying scheduling for DCI received on a first carrier frequency having a first subcarrier spacing, and a physical sidelink shared channel (PSSCH) carrying scheduling for sidelink transmission to a second UE on a second carrier frequency having a second subcarrier spacing; and receiving the PSSCH based on whether the first subcarrier spacing is greater than or less than the second subcarrier spacing.

[0012] In some implementations of the methods and apparatus described herein, the first subcarrier spacing and the second subcarrier spacing include orthogonal frequency division multiplexing (OFDM) spacings of a first carrier frequency and a second carrier frequency, respectively; wherein when the first subcarrier spacing is smaller than the second subcarrier spacing, if the first symbol in the PSSCH allocation defined by the time slot field in the DCI and the first symbol of the time slot for PSSCH transmission start at least N PDCCH symbols after the end of the PDCCH scheduling of the PSSCH, the UE receives the PSSCH; further comprising determining, independently of the reception timing difference between the scheduling cell and the second carrier frequency, whether the first symbol in the PSSCH allocation defined by the time slot field in the DCI and the first symbol of the time slot for PSSCH transmission start at least N PDCCH symbols after the end of the PDCCH scheduling of the PSSCH; wherein the N PDCCH symbols are pre-configured in a table; wherein the time slot field includes a time slot offset between the DCI and the start of a sidelink transmission; wherein the time slot offset in the time slot field includes a time slot offset representing a reference subcarrier spacing of one or more of the scheduling cells or sidelink carriers.

[0013] In some implementations of the methods and apparatus described herein, the time gap field includes a difference in parameter sets between a scheduling cell and a sidelink carrier; wherein when a first subcarrier spacing is greater than a second subcarrier spacing, if a first symbol in a PSSCH allocation defined by a time gap field in a DCI starts no earlier than at least N PDCCH symbols after the end of a PDCCH scheduling of the PSSCH, the UE receives the PSSCH; further comprising determining, independently of a reception timing difference between the scheduling cell and a second carrier frequency, whether a first symbol in a PSSCH allocation defined by a time gap field in a DCI starts no earlier than at least N PDCCH symbols after the end of a PDCCH scheduling of the PSSCH; wherein the N PDCCH symbols are pre-configured in a table; wherein the time gap field includes a time gap offset between the DCI and the start of a sidelink transmission; wherein the time gap offset in the time gap field includes a time gap offset representing a reference subcarrier spacing of one or more of the scheduling cell or the sidelink carrier; wherein the time gap field includes a difference in parameter sets between the scheduling cell and the sidelink carrier.

[0014] Some implementations of the methods and apparatus described herein may include wireless communication at a device (e.g., a base station), and the device generating a notification of sidelink carrier frequencies that can be used to implement CA for sidelink communication, the notification indicating at least one primary sidelink carrier frequency and at least one secondary sidelink carrier frequency; and sending the notification to a UE.

[0015] In some implementations of the methods and apparatus described herein, the device generates a notification as one or more of cell-specific signaling or UE-specific signaling; wherein the notification identifies the sidelink carrier frequency based on an index value of the sidelink carrier frequency in an index of the sidelink carrier frequency; wherein the notification identifies the sidelink carrier frequency based on a corresponding absolute radio frequency channel number (ARFCN) of the sidelink carrier frequency; wherein the notification identifies the corresponding priority of one or more of the sidelink carrier frequencies; further comprising generating a definition of one or more serving cells of a network node that schedules the sidelink carrier frequency by generating an association between the one or more serving cells and the sidelink carrier frequency; wherein the definition of the one or more serving cells is the same as the definition of a primary cell of the network node; further comprising generating a mapping table that associates the serving cells of the network node with the associated sidelink carrier frequency, and wherein the mapping table associates each A service cell is defined as a service cell that uses DCI to schedule the corresponding sidelink carrier frequency; wherein the sidelink carrier frequency includes one or more sidelink carrier frequencies that can be used to send or receive a sidelink synchronization signal block (SSB); wherein the notification indicates that the SSB sent in the sidelink carrier frequency can be used for synchronization of multiple sidelink carrier frequencies, and at least one of the sidelink carrier frequencies is not available for sending or receiving SSB; wherein the notification includes an indication of the priority of one or more sidelink carrier frequencies that can be used to send or receive SSB; and also includes selecting one or more of the sidelink carrier frequencies that can be used to send or receive SSB based on one or more of the frequencies or coverage ranges of one or more of the sidelink carrier frequencies; wherein at least one of the one or more sidelink carrier frequencies that can be used to send or receive SSB includes at least one primary sidelink carrier frequency.

[0016] In some implementations of the methods and apparatus described herein, a device generates a notification as UE-specific signaling to include a DCI, the DCI including one or more of a serving cell identifier mapped to a sidelink carrier frequency or a serving cell identifier of a serving cell that schedules the sidelink carrier frequency; and further includes generating the notification as UE-specific signaling, the UE-specific signaling indicating one or more of a synchronized sidelink carrier frequency, a priority of the synchronized sidelink carrier frequency, or a mapping between the sidelink carrier frequency and the synchronized carrier frequency; wherein to generate the notification of the sidelink carrier frequency, the device: configures a physical downlink control channel (PDCCH) in the serving cell to schedule a sidelink transmission in the sidelink carrier frequency; and configures the PDCCH CH includes a separate control resource set (CORESET), a search space and a monitoring opportunity to schedule DCI for each of the sidelink carrier frequencies; generates DCI that can be used to report HARQ feedback; sends the DCI to the UE; and receives sidelink HARQ feedback from the UE based on the UE's transmission through at least one primary sidelink carrier frequency and at least one secondary sidelink carrier frequency; wherein based on the absence of a PUCCH cell indicator in the DCI, the HARQ feedback can be filled into the DCI; wherein the PUCCH cell designated for downlink HARQ reporting is implemented for sending sidelink HARQ feedback; wherein the service cell designated for monitoring the DCI is implemented for sending sidelink HARQ feedback.

[0017] Some implementations of the methods and apparatus described herein may include wireless communications at a device (e.g., a base station), and the device configuring cross-carrier scheduling information, the cross-carrier scheduling information including a physical downlink control channel (PDCCH) for scheduling sidelink transmissions of multiple sidelink carrier frequencies; and sending the cross-carrier scheduling information to a UE.

[0018] In some implementations of the methods and apparatus described herein, to configure cross-carrier scheduling information, the device configures a PDCCH in a serving cell to schedule sidelink transmissions in a sidelink carrier frequency; and configures the PDCCH to include a separate control resource set (CORESET), a search space, and a monitoring opportunity to schedule DCI for each of the sidelink carrier frequencies. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Various aspects of the CA for sidelink communication of the present disclosure are described with reference to the following drawings. The same reference numerals may be used throughout to reference similar features and components shown in the figures.

[0020] Figure 1 An example of a wireless communication system supporting CA for sidelink communications according to aspects of the present disclosure is shown.

[0021] Figure 2An example of a block diagram of a device (eg, UE) supporting CA for sidelink communications according to aspects of the present disclosure is shown.

[0022] Figure 3 An example of a block diagram of a device (eg, a base station) supporting CA for sidelink communications according to aspects of the present disclosure is shown.

[0023] Figures 4 to 12 A flow chart of a method of supporting CA for sidelink communications according to aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0024] Implementations of CA for sidelink communications are described, such as related to methods, apparatus, and systems supporting CA for sidelink communications. For example, aspects of the present disclosure are directed to ways to determine and configure sidelink carrier frequencies for cross-carrier scheduling for sidelink CA communications. For example, cell-specific and / or UE-specific scheduling of carrier frequencies for CA can be implemented. Implementations also enable reporting to a wireless network sidelink HARQ to provide an indication of sidelink CA performance.

[0025] Therefore, by enabling UEs to exchange CA capability information (e.g., primary carrier frequency and secondary carrier frequency) for sidelink communication, the described technology enables the UE to quickly and efficiently obtain resources for sidelink CA and participate in CA for sidelink communication using the allocated resources.

[0026] Aspects of the present disclosure are described in the context of wireless communication systems.Aspects of the present disclosure are further illustrated and described with reference to device diagrams and flow charts related to CA for sidelink communications.

[0027] Figure 1 An example of a wireless communication system 100 that supports CA for sidelink communication according to aspects of the present disclosure is shown. The wireless communication system 100 may include one or more base stations 102, one or more UEs 104, and a core network 106. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network. The wireless communication system 100 may support radio access technologies other than 5G. In addition, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0028] One or more base stations 102 may be dispersed throughout a geographic area to form a wireless communication system 100. One or more base stations 102 described herein may be or include or may be referred to as a base transceiver station, access point, NodeB, eNodeB (eNB), next generation NodeB (gNB), radio head (RH), relay node, integrated access and backhaul (IAB) node or other suitable terms. The base station 102 and the UE 104 may communicate via a communication link 108, which may be a wireless or wired connection. For example, the base station 102 and the UE 104 may perform wireless communication via an NRUu interface.

[0029] The base station 102 may provide a geographic coverage area 110 for which the base station 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area. For example, the base station 102 and the UE 104 may support wireless communications of signals associated with services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, the base station 102 may be mobile, such as when implemented as a gNB on a satellite or other non-terrestrial station (NTS) associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 110 associated with the same or different radio access technologies may overlap, and different geographic coverage areas 110 may be associated with different base stations 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0030] One or more UEs 104 may be dispersed in a geographic area or coverage area 110 of the wireless communication system 100. UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, a customer premises equipment (CPE), a subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. In addition, or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, among other examples. In some implementations, UE 104 may be stationary in the wireless communication system 100. In other implementations, UE 104 may be mobile in the wireless communication system 100, such as a ground station in motion (ESIM).

[0031] One or more UEs 104 may be devices in different forms or with different capabilities. Figure 1 Some examples of UE 104 are shown in FIG. UE 104 may be able to communicate with various types of devices, such as base stations 102, other UE 104, or network devices (e.g., core network 106, relay devices, gateway devices, integrated access and backhaul (IAB) nodes, location servers implementing location management functions (LMF), or other network devices). In addition, or alternatively, UE 104 may support communication with other base stations 102 or UE 104, which may act as relays in the wireless communication system 100.

[0032] The UE 104 may also support wireless communication directly with other UEs 104 via a communication link 112. For example, the UE 104 may support wireless communication directly with another UE 104 via a device-to-device (D2D) communication link. In some implementations such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 112 may be referred to as a side link. For example, the UE 104 may support wireless communication directly with another UE 104 via a PC5 interface.

[0033] The base station 102 may support communication with the core network 106 or with another base station 102 or both. For example, the base station 102 may interface with the core network 106 via one or more backhaul links 114 (e.g., via S1, N2, or other network interfaces). The base stations 102 may communicate with each other via the backhaul links 114 (e.g., via X2, Xn, or another network interface). In some implementations, the base stations 102 may communicate with each other directly (e.g., between the base stations 102). In some other implementations, the base stations 102 may communicate with each other indirectly (e.g., via the core network 106). In some implementations, one or more base stations 102 may include subcomponents, such as access network entities, which may be examples of access node controllers (ANCs). The ANC may communicate with one or more UEs 104 via one or more other access network transmission entities, which may be referred to as remote radio heads, smart radio heads, gateways, transmission-reception points (TRPs), and other network nodes and / or entities.

[0034] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and user plane entities that route or interconnect packets to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of one or more UEs 104 served by one or more base stations 102 associated with the core network 106.

[0035] Depending on the implementation, one or more of the UE 104 and the base station 102 may be operable to implement various aspects of CA for sidelink communications as described herein. For example, the UE 104 exchanges capability notifications 116 that identify different sidelink capabilities of the UE 104. In addition, the UE 104 transmits the capability notifications 116 to the base station 102 to communicate the sidelink capabilities of the UE 104 to the base station 102 and the wireless communication system 100. Thus, based on the sidelink capabilities of the UE 104, the UE 104 sends data to each other as part of the sidelink communications 118. The sidelink communications 118 may include various types of data, such as voice data, video data, application data, coordination data, etc.

[0036] In at least some implementations, to enable sidelink communication 118, base station 102 communicates resource allocation 120 data to UE 104. For example, resource allocation 120 includes resources that UE 104 may use to participate in sidelink communication 118. Detailed examples of different capabilities and resources related to sidelink communication are detailed throughout this disclosure.

[0037] In some wireless communication systems, sidelink communications have been developed in the RAN to support V2X applications. Although the NR sidelink was initially developed for V2X applications, there is a growing interest in extending the applicability of the NR sidelink to different use cases, such as public safety, commercial use, etc. For commercial sidelink applications, two goals have been identified:

[0038] -Increased sidelink data rate

[0039] - Support for new carrier frequencies for sidelink

[0040] Increased sidelink data rates are driven by applications such as sharing sensor information (e.g. video) between vehicles with a high degree of driving automation. The increased data rates can be achieved with support for sidelink CA and sidelink over unlicensed spectrum. CA is a technique where multiple frequency portions (component carriers) are assigned to the same UE. By increasing the number of component carriers towards a user, the maximum possible data rate per UE can be increased. Due to better resource utilization, the system data rate of the cell is also increased.

[0041] In addition, by enhancing FR2 sidelink operation, increased data rates can be supported more efficiently over FR2. While support for new carrier frequencies and larger bandwidths will also allow for increased data rates, the primary benefit will come from making the sidelink more applicable to a wider range of applications. More specifically, with support for unlicensed spectrum and enhancements to Frequency Range 2 (FR2), the sidelink can be implemented in commercial devices, as utilization of the Intelligent Transportation System (ITS) bands is limited to ITS safety-related applications.

[0042] Some other goals for extending the applicability of sidelink in 5G NR include specifying mechanisms to support NR sidelink CA operation based on LTE sidelink CA operation [e.g. RAN2, RAN1, RAN4], and supporting LTE sidelink CA features for NR such as sidelink carrier (re)selection, synchronization of aggregated carriers, handling limited capabilities, power control for simultaneous sidelink TX, packet duplication, etc.

[0043] In addition, in some wireless communication systems, the UE can receive sidelink broadcast / multicast transmissions using CA of the carrier on which it receives PSCCH / PSSCH and sends corresponding sidelink HARQ feedback, such as when SL-HARQ is enabled in SCI.

[0044] One of the biggest hurdles in configuring sidelink CA is that, unlike RAN nodes in Uu, sidelink UE devices may not be aware of the CA capabilities of their peer / group member UEs. In Uu, the network knows the UE capabilities as it can query the UEs for capabilities or receive them from the AMF, but in sidelink operation, UEs may not be aware of each other's aggregate capabilities, especially for multicast and broadcast based SL communications, e.g., due to the lack of signaling connection establishment at least at the PC5 level. Furthermore, for unicast SL communications, UE capabilities can only be shared if a PC5 RRC connection has been established between peer UEs.

[0045] And further, in some wireless communication systems, in the sidelink, the capabilities of a UE may remain "floating" because its activity keeps changing because the peer UEs and groups and group memberships with which it is linked, connected and / or communicating may change dynamically. This is due, for example, to the dynamic nature of the sidelink communications. As an example, a vehicle may need to communicate with a particular number of vehicles at one point in time for a lane change, and with a different number of vehicles at a later point in time for a perspective application. Therefore, the present disclosure provides a method for allocating resources for sidelink CA and for implementing HARQ feedback for sidelink communications. Therefore, aspects of CA for sidelink communications solve problems with some wireless communication systems by enabling a UE to obtain resources for a CA sidelink and to participate in CA for sidelink communications using the allocated resources.

[0046] For example, implementations enable the use of cell-specific and UE-specific signaling to determine and configure the sidelink carrier frequency carrier index. In implementations, multiple sidelink carriers may be considered and the sidelink carrier index may be determined based on signaling of a sidelink carrier identifier (e.g., ARFCN) from the gNB to the UE and / or from the UE to the gNB of a sidelink carrier identifier and / or index value.

[0047] In an implementation, cell-specific signaling of the sidelink carrier index / identifier may be provided by cell broadcast signaling including the ARFCN. For example, the cell-specific signaling may indicate a primary sidelink carrier(s) and a secondary sidelink carrier(s). The sidelink carriers may be identified in ascending order of the ARFCNs of the sidelink carrier(s). In an example, mapping information of priorities and / or traffic profiles of V2X service types may be provided for the sidelink carrier(s) configuration. Additionally, the primary sidelink carrier(s) may be the default sidelink carrier(s) for sending and receiving discovery messages, such as for a UE with limited Tx / RxRF chains.

[0048] In implementation, the definition of the serving cell(s) for scheduling the sidelink carrier(s) may be provided by generating an association between the serving cell(s) of the gNB and the serving cell(s) of the corresponding sidelink carrier(s). For example, the serving cell(s) for scheduling the sidelink carrier(s) may be the same as the definition of the primary cell(s) (e.g., PCell).

[0049] In an additional or alternative implementation, a mapping table of sidelink carrier frequencies may be created by associating a serving cell of a gNB with serving cells of multiple sidelink carriers, and DCI signaling may be used to define a serving cell as a scheduling cell with a corresponding sidelink carrier. In an implementation, a sidelink carrier for receiving sidelink SSB transmission and reception may also be signaled. For example, a sidelink SSB transmitted in a sidelink carrier may be used for synchronization of multiple sidelink carriers, and some sidelink carriers may not be used for sidelink SSB transmission and / or reception, such as sidelink carriers that were not previously notified to the UE. Multiple priorities for synchronization carriers and association of synchronization carriers with sidelink carriers may be provided to the UE. In at least one implementation, synchronization carrier selection may be based on corresponding sidelink frequencies and coverage.

[0050] In an implementation, a configuration is provided for DCI scheduling of PSSCH transmissions across multiple sidelink carriers. For example, the DCI is used to schedule multiple sidelink carriers, and some sidelink carriers may not have the same parameter set as the Uu carrier. For example, as described previously, a DCI (e.g., DCI format 3_0) that may be sent by a serving cell and that schedules sidelink transmissions in multiple sidelink carriers may include a sidelink carrier index identifier and / or an identifier that associates a sidelink grant with a sidelink grant for a corresponding sidelink carrier. In addition, the sidelink carriers may have different parameter sets and / or subcarrier spacings.

[0051] In implementation, a separate control resource set (CORESET), search space, and / or monitoring opportunity may be configured in a serving cell as part of cross-carrier scheduling of corresponding sidelink transmissions to multiple sidelink carriers. In scenarios with restrictions on blind decoding of DCIs from overlapping control channel elements (CCEs) from CORESETs and / or search spaces, the UE may decode the scheduling grant in a priority order corresponding to the priority of the sidelink carriers.

[0052] In implementation, a cross-carrier scheduled PDCCH carrying a scheduling DCI is received on one carrier with one orthogonal frequency division multiplexing (OFDM) subcarrier spacing (μPDCCH), while a PSSCH scheduled to a peer UE is received on another carrier with another OFDM subcarrier spacing (μPSSCH). In this scenario when μPDCCH < μPSSCH, the UE may receive the scheduled PSSCH when the first symbol in the PSSCH allocation defined by the time gap field in the DCI and the first symbol of the time slot for the PSSCH transmission start at least Npssch PDCCH symbols after the end of the PDCCH scheduling of the PSSCH. Depending on the implementation, this determination does not take into account the impact of the receive timing difference between the scheduling cell and the sidelink carrier. In addition, the Npssch PDCCH symbols may be pre-configured in the table.

[0053] In the scenario of μPDCCH>μPSSCH, the UE may receive the scheduled PSSCH when the first symbol in the PSSCH allocation defined by the Time Slot field in the DCI starts no earlier than at least Npssch PDCCH symbols after the end of the PDCCH scheduling of the PSSCH. Depending on the implementation, this determination does not take into account the impact of the receive timing difference between the scheduling cell and the sidelink carrier.

[0054] In implementation, the time slot field value m (e.g., of DCI format 3_0) provides index m+1 into the time slot offset table. The table is given by the higher layer parameter sl-DCI-ToSL-Trans, and the table value at index m+1 can be referred to as the time slot offset K_SL. The time slot of the first side link transmission scheduled by the DCI is the first SL time slot in the corresponding resource pool that starts no earlier than T_"DL"-T_"TA" / 2+K_SL×T_"slot", where T_"DL" is the start time of the downlink time slot carrying the corresponding DCI, T_"TA" is the timing advance value corresponding to the TAG of the service cell on which the DCI is received, K_SL is the time slot offset between the time slot of the DCI and the first side link transmission scheduled by the DCI, and T_slot is the side link time slot duration.

[0055] In implementation, when a PDCCH candidate is associated with a search space set configured with searchSpaceLinking, the PDCCH candidate that ends later in time among the two configured PDCCH candidates may be used for the purpose of determining Npssch. In implementation, the time gap field may contain a time slot offset between the received DCI and the start of the sidelink transmission, and in a cross-carrier scheduling scenario, the subcarrier spacing between the scheduling cell and the sidelink carrier is different. For example, the time slot offset in the time gap field may represent a time slot offset according to a reference subcarrier spacing, which may be that of the scheduling cell or of the sidelink carrier. Alternatively, or in addition, the time gap may also include a gap for the difference in parameter sets between the scheduling cell and the sidelink carrier.

[0056] The implementation also enables sidelink HARQ reporting in PUCCH / PUSCH and multiplexing downlink HARQ and SL HARQ together. For example, a separate PUCCH cell indicator can be indicated in the DCI in addition to the PUCCH resource indicator used to report sidelink HARQ feedback to the gNB. For example, the absence of a PUCCH cell indicator in the DCI means that the PUCCH PCell can be used to transmit sidelink HARQ feedback to the gNB.

[0057] In an additional or alternative implementation, the PUCCH cell selected for downlink HARQ reporting can be used to report sidelink HARQ feedback, e.g., to a gNB. In an additional or alternative implementation, a serving cell configured to monitor DCI can be used to send the PUCCH. Furthermore, an ascending order of the sidelink carrier index can be used to report sidelink HARQ from multiple sidelink carriers, e.g., to a gNB.

[0058] Figure 2 An example of a block diagram 200 of a device 202 supporting CA for sidelink communications according to aspects of the present disclosure is shown. The device 202 may be an example of a UE 104 as described herein. The device 202 may support wireless communications and / or network signaling with one or more base stations 102, other UEs 104, network entities and devices, or any combination thereof. The device 202 may include components for bidirectional communications, including components for sending and receiving communications, such as a communication manager 204, a processor 206, a memory 208, a receiver 210, a transmitter 212, and an I / O controller 214. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0059] The communication manager 204, the receiver 210, the transmitter 212, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the present disclosure as described herein. For example, the communication manager 204, the receiver 210, the transmitter 212, or various combinations or components thereof, may support methods for performing one or more functions described herein.

[0060] In some implementations, the communication manager 204, the receiver 210, the transmitter 212, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise support means for performing the functions described in the present disclosure. In some implementations, the processor 206 and a memory 208 coupled to the processor 206 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory 208 by the processor 206).

[0061] Additionally or alternatively, in some implementations, the communication manager 204, the receiver 210, the transmitter 212, or various combinations or components thereof may be implemented in code executed by the processor 206 (e.g., as communication management software or firmware). If implemented in code executed by the processor 206, the functionality of the communication manager 204, the receiver 210, the transmitter 212, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., components configured or otherwise supported for performing the functionality described in the present disclosure).

[0062] In some implementations, the communication manager 204 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the receiver 210, the transmitter 212, or both. For example, the communication manager 204 may receive information from the receiver 210, send information to the transmitter 212, or be integrated with the receiver 210, the transmitter 212, or both to receive information, send information, or perform various other operations as described herein. Although the communication manager 204 is shown as a separate component, in some implementations, one or more functions described with reference to the communication manager 204 may be supported or performed by the processor 206, the memory 208, or any combination thereof. For example, the memory 208 may store code that may include instructions executable by the processor 206 to cause the device 202 to perform various aspects of the present disclosure as described herein, or the processor 206 and the memory 208 may be otherwise configured to perform or support such operations.

[0063] For example, the communications manager 204 may support wireless communications and / or network signaling at a device (eg, device 202, UE) according to examples as disclosed herein.

[0064] The communication manager 204 and / or other device components may be configured to or otherwise support an apparatus, such as a UE, comprising: a transceiver; a processor coupled to the transceiver, the processor and the transceiver being configured to cause the apparatus to: determine a side link carrier frequency that may be used to implement CA for side link communication; identify at least one primary side link carrier frequency and at least one secondary side link carrier frequency from the side link carrier frequencies; and send data to a second UE using the at least one primary side link carrier frequency and the at least one secondary side link carrier frequency.

[0065] In addition, the device (e.g., UE) includes any one of the following or a combination thereof: wherein the sidelink carrier frequency is identified based on one or more of cell-specific signaling received from a network node, UE-specific signaling received from a network node, or a pre-configuration of the UE; wherein the sidelink carrier frequencies are configured in ascending order of ARFCN; wherein the processor and the transceiver are configured to enable the first UE to: receive a mapping of one or more of the sidelink carrier frequencies to one or more service types operable for receiving sidelink communications from the network node, wherein the mapping is based at least in part on priority information of the service type; wherein the processor and the transceiver are configured to enable the first UE to: determine the sidelink carrier frequency based on an association of the UE's serving cell with the sidelink carrier frequency; wherein the association of the UE's serving cell with the sidelink carrier frequency is the same as the association of the UE's primary cell with the sidelink carrier frequency; wherein the processor and the transceiver are configured to enable the first UE to: receive signaling including one or more sidelink carrier frequencies associated with one or more SSBs; and receive one or more SSBs via the one or more sidelink carrier frequencies for synchronization of at least one primary sidelink carrier frequency and at least one secondary sidelink carrier frequency;

[0066] In addition, the device (e.g., UE) includes any one or a combination of the following: one or more sidelink carrier frequencies associated with one or more SSBs include: at least one primary sidelink carrier frequency; wherein the sidelink carrier frequency is identified based on UE-specific signaling received from a network node, and wherein the UE-specific signaling, and wherein the UE-specific signaling includes one or more of the following: configuration for one or more sidelink synchronization carrier frequencies; one or more priority values ​​for the sidelink carrier frequencies; or mapping information for mapping the sidelink carrier frequencies to the sidelink synchronization carrier frequencies; wherein the processor and the transceiver are configured to enable the first UE to: determine a sidelink carrier frequency that can be used to implement CA for sidelink communication based on a signal transmission from a second UE; wherein the processor and the transceiver are configured to enable the first UE to: send Broadcast, the broadcast identification can be used to implement CA for sidelink communication of one or more of the sidelink carrier frequencies; wherein the processor and the transceiver are configured to make the first UE: based on the transmission through at least one primary sidelink carrier frequency and at least one secondary sidelink carrier frequency generate HARQ feedback; and send the sidelink HARQ to the network node; the processor and the transceiver are configured to make the first UE: send the sidelink HARQ together with the downlink HARQ to the network node; wherein the processor and the transceiver are configured to make the first UE: send the sidelink HARQ via the PUCCH field in the DCI; wherein the processor and the transceiver are configured to make the first UE: send the sidelink HARQ based on the ascending order of at least one primary sidelink carrier frequency and at least one secondary sidelink carrier frequency in the sidelink carrier frequency index;

[0067] The communication manager 204 and / or other device components may be configured to or otherwise support components for wireless communication and / or network signaling at a UE, including determining, at a first UE, a sidelink carrier frequency that may be used to implement CA for sidelink communication; identifying at least one primary sidelink carrier frequency and at least one secondary sidelink carrier frequency from the sidelink carrier frequencies; and sending data to a second UE using the at least one primary sidelink carrier frequency and the at least one secondary sidelink carrier frequency.

[0068] In addition, wireless communication and / or network signaling at the UE includes any one or a combination of the following: wherein the sidelink carrier frequency is identified based on one or more of cell-specific signaling received from a network node, UE-specific signaling received from a network node, or a pre-configuration of the UE; wherein the sidelink carrier frequencies are configured in ascending order of ARFCN; further comprising receiving a mapping of one or more of the sidelink carrier frequencies from the network node to one or more service types operable for receiving sidelink communications, wherein the mapping is based at least in part on priority information of the service type; further comprising determining the sidelink carrier frequency based on an association between a serving cell of the UE and the sidelink carrier frequency; wherein the association between the serving cell of the UE and the sidelink carrier frequency is the same as the association between a primary cell of the UE and the sidelink carrier frequency; further comprising: receiving signaling including one or more sidelink carrier frequencies associated with one or more SSBs; and receiving one or more SSBs via one or more sidelink carrier frequencies for synchronization of at least one primary sidelink carrier frequency and at least one secondary sidelink carrier frequency.

[0069] In addition, the wireless communication and / or network signaling at the UE includes any one or a combination of the following: wherein the one or more sidelink carrier frequencies associated with the one or more SSBs include: at least one primary sidelink carrier frequency; wherein the sidelink carrier frequency is identified based on UE-specific signaling received from the network node, and wherein the UE-specific signaling, and wherein the UE-specific signaling includes one or more of the following: configuration for one or more sidelink synchronization carrier frequencies; one or more priority values ​​of the sidelink carrier frequencies; or mapping information for mapping the sidelink carrier frequencies to the sidelink synchronization carrier frequencies; and also includes determining, based on signal transmission from a second UE, information that can be used to implement the sidelink communication. The method further comprises: transmitting a broadcast identifying one or more of the side link carrier frequencies that can be used to implement CA for side link communication; further comprises: generating HARQ feedback based on transmission through at least one primary side link carrier frequency and at least one secondary side link carrier frequency; and sending the side link HARQ to a network node; the method further comprises sending the side link HARQ together with the downlink HARQ to the network node; further comprises sending the side link HARQ via the PUCCH field in the DCI; further comprises sending the side link HARQ based on an ascending order of at least one primary side link carrier frequency and at least one secondary side link carrier frequency in a side link carrier frequency index.

[0070] The communication manager 204 and / or other device components may be configured to or otherwise support an apparatus, such as a UE, comprising: a transceiver; a processor coupled to the transceiver, the processor and the transceiver being configured such that the apparatus: receives cross-carrier scheduling information, the cross-carrier scheduling information comprising a scheduling physical downlink control channel (PDCCH) carrying scheduling for DCI received on a first carrier frequency having a first subcarrier spacing, and a PSSCH carrying scheduling for sidelink transmission to a second UE on a second carrier frequency having a second subcarrier spacing; and receives the PSSCH based on whether the first subcarrier spacing is greater than or less than the second subcarrier spacing.

[0071] In addition, the device (e.g., UE) includes any one of the following or a combination thereof: wherein the first subcarrier spacing and the second subcarrier spacing respectively include OFDM spacings of the first carrier frequency and the second carrier frequency; wherein when the first subcarrier spacing is smaller than the second subcarrier spacing, if the first symbol in the PSSCH allocation defined by the time slot field in the DCI, and the first symbol of the time slot for PSSCH transmission start at least N PDCCH symbols after the end of the PDCCH scheduling of the PSSCH, the UE receives the PSSCH; wherein the processor and the transceiver are configured to enable the first UE to: independently of the reception timing difference between the scheduling cell and the second carrier frequency, determine whether the first symbol in the PSSCH allocation defined by the time slot field in the DCI, and the first symbol of the time slot for PSSCH transmission start at least N PDCCH symbols after the end of the PDCCH scheduling of the PSSCH.

[0072] In addition, the device (e.g., UE) includes any one of the following or a combination thereof: wherein N PDCCH symbols are preconfigured in a table; wherein the time gap field includes a time gap offset between the DCI and the start of the sidelink transmission; wherein the time gap offset in the time gap field includes a time gap offset representing a reference subcarrier spacing of one or more of the scheduling cells or sidelink carriers; wherein the time gap field includes a difference in parameter sets between the scheduling cell and the sidelink carrier; wherein when the first subcarrier spacing is greater than the second subcarrier spacing, if the first symbol in the PSSCH allocation defined by the time gap field in the DCI starts no earlier than at least N PDCCH symbols after the end of the PDCCH scheduling of the PSSCH, the UE receives receiving PSSCH; wherein the processor and the transceiver are configured to enable the first UE to: determine whether the first symbol in the PSSCH allocation defined by the time gap field in the DCI starts no earlier than at least N PDCCH symbols after the end of the PDCCH scheduling of the PSSCH, independently of the reception timing difference between the scheduling cell and the second carrier frequency; wherein the N PDCCH symbols are preconfigured in a table; wherein the time gap field includes a time gap offset between the DCI and the start of the sidelink transmission; wherein the time gap offset in the time gap field includes a time gap offset representing a reference subcarrier spacing of one or more of the scheduling cell or the sidelink carrier; wherein the time gap field includes a difference in parameter sets between the scheduling cell and the sidelink carrier;

[0073] The communication manager 204 and / or other device components may be configured to or otherwise support components for wireless communication and / or network signaling at a UE, including receiving cross-carrier scheduling information, the cross-carrier scheduling information comprising a scheduling physical downlink control channel (PDCCH) carrying scheduling for DCI received on a first carrier frequency having a first subcarrier spacing, and a PSSCH carrying scheduling for sidelink transmissions to a second UE on a second carrier frequency having a second subcarrier spacing; and receiving the PSSCH based on whether the first subcarrier spacing is greater than or less than the second subcarrier spacing.

[0074] In addition, the wireless communication and / or network signaling at the UE includes any one or a combination of the following: wherein the first subcarrier spacing and the second subcarrier spacing respectively include OFDM spacings of the first carrier frequency and the second carrier frequency; wherein when the first subcarrier spacing is smaller than the second subcarrier spacing, if the first symbol in the PSSCH allocation defined by the time slot field in the DCI and the first symbol of the time slot for PSSCH transmission start at least N PDCCH symbols after the end of the PDCCH scheduling of the PSSCH, the UE receives the PSSCH; further comprising determining, independently of the reception timing difference between the scheduling cell and the second carrier frequency, whether the first symbol in the PSSCH allocation defined by the time slot field in the DCI and the first symbol of the time slot for PSSCH transmission start at least N PDCCH symbols after the end of the PDCCH scheduling of the PSSCH; wherein the N PDCCH symbols are pre-configured in a table; wherein the time slot field includes a time slot offset between the DCI and the start of the sidelink transmission; wherein the time slot offset in the time slot field includes a time slot offset representing a reference subcarrier spacing of one or more of the scheduling cells or sidelink carriers.

[0075] In addition, wireless communication and / or network signaling at the UE includes any one or a combination of the following: wherein the time gap field includes the difference in parameter sets between the scheduling cell and the sidelink carrier; wherein when the first subcarrier spacing is greater than the second subcarrier spacing, if the first symbol in the PSSCH allocation defined by the time gap field in the DCI starts no earlier than at least N PDCCH symbols after the end of the PDCCH scheduling of the PSSCH, the UE receives the PSSCH; also includes determining whether the first symbol in the PSSCH allocation defined by the time gap field in the DCI starts no earlier than at least N PDCCH symbols after the end of the PDCCH scheduling of the PSSCH, independent of the reception timing difference between the scheduling cell and the second carrier frequency; wherein the N PDCCH symbols are pre-configured in a table; wherein the time gap field includes a time slot offset between the DCI and the start of the sidelink transmission; wherein the time slot offset in the time gap field includes a time slot offset representing a reference subcarrier spacing of one or more of the scheduling cell or the sidelink carrier; wherein the time gap field includes the difference in parameter sets between the scheduling cell and the sidelink carrier.

[0076] The processor 206 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 206 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 206. The processor 206 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 208) to cause the device 202 to perform various functions of the present disclosure.

[0077] The memory 208 may include random access memory (RAM) and read-only memory (ROM). The memory 208 may store computer-readable, computer-executable code, which includes instructions that, when executed by the processor 206, cause the device 202 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some implementations, the code may not be directly executable by the processor 206, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, the memory 208 may include, among other things, a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0078] I / O controller 214 can manage input and output signals for device 202. I / O controller 214 can also manage peripheral devices that are not integrated into device 202. In some implementations, I / O controller 214 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 214 can use an operating system, such as or another known operating system. In some implementations, the I / O controller 214 may be implemented as part of a processor, such as the processor 206. In some implementations, a user may interact with the device 202 via the I / O controller 214 or via hardware components controlled by the I / O controller 214.

[0079] In some implementations, the device 202 may include a single antenna 216. However, in some other implementations, the device 202 may have more than one antenna 216, which may be capable of simultaneously sending or receiving multiple wireless transmissions. The receiver 210 and the transmitter 212 may communicate bidirectionally via one or more antennas 216, wired or wireless links, as described herein. For example, the receiver 210 and the transmitter 212 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver may also include a modem for modulating packets, providing the modulated packets to one or more antennas 216 for transmission, and demodulating packets received from one or more antennas 216.

[0080] Figure 3 An example of a block diagram 300 of a device 302 supporting CA for sidelink communications according to aspects of the present disclosure is shown. The device 302 may be an example of a base station 102, such as a gNB as described herein. The device 302 may support wireless communications and / or network signaling with one or more base stations 102, other UEs 104, core network devices and functions (e.g., core network 106), or any combination thereof. The device 302 may include components for bidirectional communications, including components for sending and receiving communications, such as a communication manager 304, a processor 306, a memory 308, a receiver 310, a transmitter 312, and an I / O controller 314. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0081] The communication manager 304, the receiver 310, the transmitter 312, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the present disclosure as described herein. For example, the communication manager 304, the receiver 310, the transmitter 312, or various combinations or components thereof, may support methods for performing one or more functions described herein.

[0082] In some implementations, the communication manager 304, the receiver 310, the transmitter 312, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise support means for performing the functions described in the present disclosure. In some implementations, the processor 306 and a memory 308 coupled to the processor 306 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory 308 by the processor 306).

[0083] Additionally or alternatively, in some implementations, the communication manager 304, the receiver 310, the transmitter 312, or various combinations or components thereof may be implemented in code executed by the processor 306 (e.g., as communication management software or firmware). If implemented in code executed by the processor 306, the functionality of the communication manager 304, the receiver 310, the transmitter 312, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., components configured or otherwise supported for performing the functions described in the present disclosure).

[0084] In some implementations, the communication manager 304 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the receiver 310, the transmitter 312, or both. For example, the communication manager 304 may receive information from the receiver 310, send information to the transmitter 312, or be integrated with the receiver 310, the transmitter 312, or both to receive information, send information, or perform various other operations as described herein. Although the communication manager 304 is shown as a separate component, in some implementations, one or more functions described with reference to the communication manager 304 may be supported or performed by the processor 306, the memory 308, or any combination thereof. For example, the memory 308 may store code that may include instructions executable by the processor 306 to cause the device 302 to perform various aspects of the present disclosure as described herein, or the processor 306 and the memory 308 may be otherwise configured to perform or support such operations.

[0085] For example, the communication manager 304 can support wireless communication and / or network signaling at a device (e.g., device 302, base station) according to examples as disclosed herein. The communication manager 304 and / or other device components can be configured as or otherwise support an apparatus such as a base station, which includes: a transceiver; a processor coupled to the transceiver, the processor and the transceiver configured to cause the apparatus to: generate a notification of a sidelink carrier frequency that can be used to implement CA for sidelink communication, the notification indicating at least one primary sidelink carrier frequency and at least one secondary sidelink carrier frequency; and send the notification to a UE.

[0086] In addition, the device (e.g., a base station) includes any one or a combination of the following: wherein the processor and the transceiver are configured to cause the network node to: generate a notification as one or more of cell-specific signaling or UE-specific signaling; wherein the notification identifies the sidelink carrier frequency based on an index value of the sidelink carrier frequency in an index of the sidelink carrier frequency; wherein the notification identifies the sidelink carrier frequency based on a corresponding absolute radio frequency channel number (ARFCN) of the sidelink carrier frequency; wherein the notification identifies the corresponding priority of one or more of the sidelink carrier frequencies; wherein the processor and the transceiver are configured to cause the network node to: generate a definition of one or more service cells of the network node that schedules the sidelink carrier frequency by generating an association between the one or more service cells and the sidelink carrier frequency; wherein the definition of the one or more service cells is the same as the definition of the primary cell of the network node; wherein the processor and the transceiver are configured to cause the network node to: generate a mapping table that associates the service cells of the network node with the associated The notification is associated with a sidelink carrier frequency, and wherein the mapping table defines each serving cell as a serving cell that uses the DCI to schedule the corresponding sidelink carrier frequency; wherein the sidelink carrier frequency includes one or more sidelink carrier frequencies that can be used to send or receive a sidelink synchronization signal block (SSB); wherein the notification indicates that the SSB sent in the sidelink carrier frequency can be used for synchronization of multiple sidelink carrier frequencies, and at least one of the sidelink carrier frequencies is not available for sending or receiving the SSB; wherein the notification includes an indication of the priority of the one or more sidelink carrier frequencies that can be used to send or receive the SSB; wherein the processor and the transceiver are configured to enable the network node to: select one or more of the sidelink carrier frequencies that can be used to send or receive the SSB based on one or more of the frequencies or coverage ranges of one or more of the sidelink carrier frequencies; wherein at least one of the one or more sidelink carrier frequencies that can be used to send or receive the SSB includes at least one primary sidelink carrier frequency;

[0087] In addition, the apparatus (e.g., a base station) includes any one or a combination of the following: wherein the processor and the transceiver are configured to cause the network node to: generate the notification as UE-specific signaling to include DCI, the DCI including one or more of a serving cell identifier mapped to the side link carrier frequency or a serving cell identifier of a serving cell that schedules the side link carrier frequency; wherein the processor and the transceiver are configured to cause the network node to: generate the notification as UE-specific signaling, the UE-specific signaling indicating one or more of a synchronization side link carrier frequency, a priority of the synchronization side link carrier frequency, or a mapping between the side link carrier frequency and the synchronization carrier frequency; wherein in order to generate the notification of the side link carrier frequency, the processor and the transceiver are configured to cause the network node to: configure a physical downlink control channel (PDCCH) in the serving cell to schedule the side link sidelink transmission in carrier frequencies; and configuring a PDCCH to include a separate control resource set (CORESET), a search space, and a monitoring opportunity to schedule DCI for each of the sidelink carrier frequencies; wherein the processor and the transceiver are configured to cause the network node to: generate DCI that can be used to report HARQ feedback; send the DCI to the UE; and receive sidelink HARQ feedback from the UE based on the UE's transmission over at least one primary sidelink carrier frequency and at least one secondary sidelink carrier frequency; wherein based on the absence of a PUCCH cell indicator in the DCI, the HARQ feedback can be filled into the DCI; wherein the PUCCH cell designated for downlink HARQ reporting is implemented for sending sidelink HARQ feedback; wherein the serving cell designated for monitoring the DCI is implemented for sending sidelink HARQ feedback;

[0088] The communication manager 304 and / or other device components may be configured to or otherwise support components for wireless communication and / or network signaling at a base station, including generating a notification of sidelink carrier frequencies that may be used to implement CA for sidelink communications, the notification indicating at least one primary sidelink carrier frequency and at least one secondary sidelink carrier frequency; and sending the notification to a UE.

[0089] In addition, the wireless communication at the base station includes any one or a combination of the following: also includes generating a notification as one or more of cell-specific signaling or UE-specific signaling; wherein the notification identifies the sidelink carrier frequency based on an index value of the sidelink carrier frequency in an index of the sidelink carrier frequency; wherein the notification identifies the sidelink carrier frequency based on a corresponding absolute radio frequency channel number (ARFCN) of the sidelink carrier frequency; wherein the notification identifies the corresponding priority of one or more of the sidelink carrier frequencies; also includes generating a definition of one or more service cells of a network node that schedules the sidelink carrier frequency by generating an association between the one or more service cells and the sidelink carrier frequency; wherein the definition of the one or more service cells is the same as the definition of a primary cell of the network node; also includes generating a mapping table that associates the service cells of the network node with the associated sidelink carrier frequency, and wherein the mapping The mapping table defines each service cell as a service cell that uses DCI to schedule a corresponding sidelink carrier frequency; wherein the sidelink carrier frequency includes one or more sidelink carrier frequencies that can be used to send or receive a sidelink synchronization signal block (SSB); wherein the notification indicates that the SSB sent in the sidelink carrier frequency can be used for synchronization of multiple sidelink carrier frequencies, and at least one of the sidelink carrier frequencies is not available for sending or receiving SSB; wherein the notification includes an indication of the priority of one or more sidelink carrier frequencies that can be used to send or receive SSB; and also includes selecting one or more of the sidelink carrier frequencies that can be used to send or receive SSB based on one or more of the frequencies or coverage ranges of one or more of the sidelink carrier frequencies; wherein at least one of the one or more sidelink carrier frequencies that can be used to send or receive SSB includes at least one primary sidelink carrier frequency.

[0090] In addition, the wireless communication at the base station includes any one of the following or a combination thereof: also includes generating the notification as UE-specific signaling, which includes a DCI, the DCI including one or more of a serving cell identifier mapped to the sidelink carrier frequency or a serving cell identifier of a serving cell that schedules the sidelink carrier frequency; also includes generating the notification as UE-specific signaling, the UE-specific signaling indicating one or more of a synchronized sidelink carrier frequency, a priority of the synchronized sidelink carrier frequency, or a mapping between the sidelink carrier frequency and the synchronized carrier frequency; wherein in order to generate the notification of the sidelink carrier frequency, the method also includes: configuring a physical downlink control channel (PDCCH) in the serving cell to schedule sidelink transmissions in the sidelink carrier frequency; and Configuring PDCCH to include a separate control resource set (CORESET), search space, and monitoring opportunity to schedule DCI for each of the sidelink carrier frequencies; also including generating DCI that can be used to report HARQ feedback; sending the DCI to the UE; and receiving sidelink HARQ feedback from the UE based on the UE's transmission through at least one primary sidelink carrier frequency and at least one secondary sidelink carrier frequency; wherein based on the absence of a PUCCH cell indicator in the DCI, the HARQ feedback can be filled into the DCI; wherein the PUCCH cell designated for downlink HARQ reporting is implemented for sending sidelink HARQ feedback; wherein the service cell designated for monitoring the DCI is implemented for sending sidelink HARQ feedback.

[0091] The communication manager 304 and / or other device components may be configured to or otherwise support an apparatus, such as a base station, comprising: a transceiver; a processor coupled to the transceiver, the processor and the transceiver being configured to cause the apparatus to: configure cross-carrier scheduling information, the cross-carrier scheduling information comprising a physical downlink control channel (PDCCH) for scheduling sidelink transmissions of multiple sidelink carrier frequencies; and send the cross-carrier scheduling information to a UE.

[0092] In addition, the device (e.g., a base station) includes any one or a combination of the following: configuring a PDCCH in a serving cell to schedule sidelink transmissions in a sidelink carrier frequency; and configuring the PDCCH to include a separate control resource set (CORESET), a search space, and a monitoring opportunity to schedule DCI for each of the sidelink carrier frequencies.

[0093] The communication manager 304 and / or other device components may be configured to or otherwise support components for wireless communication and / or network signaling at a base station, including configuring cross-carrier scheduling information, the cross-carrier scheduling information comprising a physical downlink control channel (PDCCH) for scheduling sidelink transmissions of multiple sidelink carrier frequencies; and sending the cross-carrier scheduling information to a UE.

[0094] In addition, the wireless communication at the base station includes any one or a combination of the following: wherein, in order to configure cross-carrier scheduling information, the method also includes: configuring the PDCCH in the serving cell to schedule sidelink transmissions in the sidelink carrier frequency; and configuring the PDCCH to include a separate control resource set (CORESET), search space, and monitoring opportunity to schedule DCI for each of the sidelink carrier frequencies.

[0095] The processor 306 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 306 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 306. The processor 306 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 308) to cause the device 302 to perform various functions of the present disclosure.

[0096] The memory 308 may include random access memory (RAM) and read-only memory (ROM). The memory 308 may store computer-readable, computer-executable code, which includes instructions that, when executed by the processor 306, cause the device 302 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some implementations, the code may not be directly executable by the processor 306, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, the memory 308 may include, among other things, a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0097] I / O controller 314 can manage input and output signals for device 302. I / O controller 314 can also manage peripheral devices that are not integrated into device 302. In some implementations, I / O controller 314 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 314 can use an operating system, such as or another known operating system. In some implementations, I / O controller 314 may be implemented as part of a processor, such as processor 306. In some implementations, a user may interact with device 302 via I / O controller 314 or via hardware components controlled by I / O controller 314.

[0098] In some implementations, the device 302 may include a single antenna 316. However, in some other implementations, the device 302 may have more than one antenna 316, which may be capable of simultaneously sending or receiving multiple wireless transmissions. The receiver 310 and the transmitter 312 may communicate bidirectionally via one or more antennas 316, wired or wireless links, as described herein. For example, the receiver 310 and the transmitter 312 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver may also include a modem for modulating packets, providing the modulated packets to one or more antennas 316 for transmission, and demodulating packets received from one or more antennas 316.

[0099] Figure 4 400 for supporting CA for sidelink communication according to aspects of the present disclosure. The operations of the method 400 may be performed by a device or a component thereof (such as a Figures 1 to 3 The described UE 104) is implemented and executed. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. In addition, or alternatively, the device can use dedicated hardware to perform aspects of the described functions.

[0100] At 402, the method may include determining, at a first UE, a sidelink carrier frequency that may be used to implement CA for sidelink communication. The operations of 402 may be performed according to examples as described herein. In some implementations, aspects of the operations of 402 may be performed as described in reference to Figure 1 The described device performs.

[0101] At 404, the method may include identifying at least one primary side link carrier frequency and at least one secondary side link carrier frequency from the side link carrier frequencies. The operations of 404 may be performed according to examples as described herein. In some implementations, aspects of the operations of 404 may be performed as described in reference to Figure 1 The described device performs.

[0102] At 406, the method may include sending data to a second UE using at least one primary sidelink carrier frequency and at least one secondary sidelink carrier frequency. The operations of 406 may be performed according to examples as described herein. In some implementations, aspects of the operations of 406 may be performed as described in reference to Figure 1 The described device performs.

[0103] Figure 5 1 is a flow chart of a method 500 for supporting CA for sidelink communication according to aspects of the present disclosure. The operations of the method 500 may be performed by a device or a component thereof (such as a device described in reference Figures 1 to 3The described UE 104) is implemented and executed. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. In addition, or alternatively, the device can use dedicated hardware to perform aspects of the described functions.

[0104] At 502, the method may include receiving signaling including one or more sidelink carrier frequencies associated with one or more SSBs. The operations of 502 may be performed according to examples as described herein. In some implementations, aspects of the operations of 502 may be performed as described in reference to Figure 1 The described device performs.

[0105] At 504, the method may include receiving one or more SSBs over one or more side link carrier frequencies for synchronization of at least one primary side link carrier frequency and at least one secondary side link carrier frequency. The operations of 504 may be performed according to examples as described herein. In some implementations, aspects of the operations of 504 may be performed as described in reference to Figure 1 The described device performs.

[0106] Figure 6 600 for supporting CA for sidelink communication according to aspects of the present disclosure. The operations of method 600 may be performed by a device or a component thereof (such as a device such as a device described in reference Figures 1 to 3 The described UE 104) is implemented and executed. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. In addition, or alternatively, the device can use dedicated hardware to perform aspects of the described functions.

[0107] At 602, the method may include generating HARQ feedback based on transmissions over at least one primary side link carrier frequency and at least one secondary side link carrier frequency. The operations of 602 may be performed according to examples as described herein. In some implementations, aspects of the operations of 602 may be performed as described in reference to Figure 1 The described device performs.

[0108] At 604, the method may include sending a sidelink HARQ to the network node. The operations of 604 may be performed according to examples as described herein. In some implementations, aspects of the operations of 604 may be performed as described in reference to Figure 1 The described device performs.

[0109] Figure 7 1 is a flow chart of a method 700 for supporting CA for sidelink communication according to aspects of the present disclosure. The operations of the method 700 may be performed by a device or a component thereof (such as a device described in reference Figures 1 to 3The described UE 104) is implemented and executed. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. In addition, or alternatively, the device can use dedicated hardware to perform aspects of the described functions.

[0110] At 702, the method may include receiving cross-carrier scheduling information, the cross-carrier scheduling information including a scheduling physical downlink control channel (PDCCH) carrying scheduling for DCI received on a first carrier frequency with a first subcarrier spacing, and a PSSCH carrying scheduling for sidelink transmission to a second UE on a second carrier frequency with a second subcarrier spacing. The operations of 702 may be performed according to examples as described herein. In some implementations, aspects of the operations of 702 may be performed as described in reference to Figure 1 The described device performs.

[0111] At 704, the method may include receiving the PSSCH based on whether the first subcarrier spacing is greater than or less than the second subcarrier spacing. The operations of 704 may be performed according to examples as described herein. In some implementations, aspects of the operations of 704 may be performed as described in reference to Figure 1 The described device performs.

[0112] Figure 8 800 for supporting CA for sidelink communications according to aspects of the present disclosure. The operations of the method 800 may be performed by a device or component thereof (such as a base station 102, for example, as described in reference Figures 1 to 3 The gNB described herein may be implemented and performed by a device. In some implementations, a device may execute a set of instructions to control functional elements of the device to perform the described functions. In addition, or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0113] At 802, the method may include generating a notification of sidelink carrier frequencies that may be used to implement CA for sidelink communications, the notification indicating at least one primary sidelink carrier frequency and at least one secondary sidelink carrier frequency. The operations of 802 may be performed according to examples as described herein. In some implementations, aspects of the operations of 802 may be performed as described in reference to Figure 1 The described device performs.

[0114] At 804, the method may include sending a notification to the UE. The operations of 804 may be performed according to examples as described herein. In some implementations, aspects of the operations of 804 may be performed as described in reference to Figure 1 The described device performs.

[0115] Fig. 91 is a flow chart of a method 900 for supporting CA for sidelink communication according to aspects of the present disclosure. The operations of the method 900 may be performed by a device or a component thereof (such as a base station 102, for example, as described in reference Figures 1 to 3 The gNB described herein may be implemented and performed by a device. In some implementations, a device may execute a set of instructions to control functional elements of the device to perform the described functions. In addition, or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0116] At 902, the method may include configuring a physical downlink control channel (PDCCH) in a serving cell to schedule a sidelink transmission in a sidelink carrier frequency. The operations of 902 may be performed according to examples as described herein. In some implementations, aspects of the operations of 902 may be performed as described in reference to Figure 1 The described device performs.

[0117] At 904, the method may include configuring the PDCCH to include a separate control resource set (CORESET), search space, and monitoring opportunity to schedule DCI for each of the sidelink carrier frequencies. The operations of 904 may be performed according to examples as described herein. In some implementations, aspects of the operations of 904 may be performed as described in reference to Figure 1 The described device performs.

[0118] Fig.10 1 is a flow chart of a method 1000 for supporting CA for sidelink communication according to aspects of the present disclosure. The operations of the method 1000 may be performed by a device or a component thereof (such as a base station 102, for example, as described in reference Figures 1 to 3 The gNB described herein may be implemented and executed by a device. In some implementations, a device may execute a set of instructions to control functional elements of the device to perform the described functions. In addition, or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0119] At 1002, the method may include generating a DCI that can be used to report HARQ feedback. The operations of 1002 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1002 may be performed as described in reference to Figure 1 The described device performs.

[0120] At 1004, the method may include sending the DCI to the UE. The operations of 1004 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1004 may be performed as described in reference to Figure 1 The described device performs.

[0121] At 1006, the method may include receiving sidelink HARQ feedback from the UE based on the UE's transmissions over at least one primary sidelink carrier frequency and at least one secondary sidelink carrier frequency. The operations of 1006 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1006 may be performed as described in reference to Figure 1 The described device performs.

[0122] Fig.11 1 is a flowchart of a method 1100 for supporting CA for sidelink communication according to aspects of the present disclosure. The operations of the method 1100 may be performed by a device or a component thereof (such as a device such as a device described in reference Figures 1 to 3 The described base station 102, such as a gNB) is implemented and performed. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. In addition, or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0123] At 1102, the method may include configuring cross-carrier scheduling information, the cross-carrier scheduling information including a physical downlink control channel (PDCCH) for scheduling sidelink transmissions of multiple sidelink carrier frequencies. The operations of 1102 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1102 may be performed as described in reference to Figure 1 The described device performs.

[0124] At 1104, the method may include sending the cross-carrier scheduling information to the UE. The operations of 1104 may be performed according to the examples described herein. In some implementations, aspects of the operations of 1104 may be performed as described in reference to Figure 1 The described device performs.

[0125] Fig.12 1 is a flow chart of a method 1200 for supporting CA for sidelink communication according to aspects of the present disclosure. The operations of the method 1200 may be performed by a device or a component thereof (such as a base station 102, for example, as described in reference Figures 1 to 3 The gNB described herein may be implemented and performed by a device. In some implementations, a device may execute a set of instructions to control functional elements of the device to perform the described functions. In addition, or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0126] At 1202, the method may include configuring a PDCCH in a serving cell to schedule a sidelink transmission in a sidelink carrier frequency. The operations of 1202 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1202 may be performed as described in reference to Figure 1 The described device performs.

[0127] At 1204, the method may include configuring the PDCCH to include a separate control resource set (CORESET), search space, and monitoring opportunity to schedule DCI for each of the sidelink carrier frequencies. The operations of 1204 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1204 may be performed as described in reference to Figure 1 The described device performs.

[0128] It should be noted that the methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are possible. In addition, two or more aspects from the methods may be combined. The order in which the methods are described is not intended to be construed as limiting, and any number or combination of the described method operations may be performed in any order to perform the method or an alternative method.

[0129] The various illustrative blocks and components described in conjunction with the present disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.

[0130] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or sent via a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these. Features that implement the functions may also be physically located at various locations, including being distributed so that parts of the functions are implemented at different physical locations.

[0131] Computer-readable media include both non-transient computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. Non-transient storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. As an example and not limitation, non-transient computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage device, magnetic disk storage device or other magnetic storage device, or can be used to carry or store the required program code components in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Any other non-transient medium.

[0132] Any connection may be appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are all included in the definition of computer-readable media. Disks and optical disks as used herein include CDs, laser optical disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, wherein disks typically reproduce data magnetically, and optical disks reproduce data optically using lasers. The above combinations are also included in the scope of computer-readable media.

[0133] As used herein, including in the claims, "or" as used in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, for example, a list of at least one of A, B, or C means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Similarly, a list of one or more of A, B, or C means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on". In addition, as used herein, including in the claims, a "set" may include one or more elements.

[0134] The description set forth herein in conjunction with the accompanying drawings describes example configurations and does not represent all examples that can be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "in favor of other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0135] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first UE, comprising: Transceiver; as well as a processor coupled to the transceiver, the processor and the transceiver being configured to cause the first UE to: determining a sidelink carrier frequency that can be used to implement CA for sidelink communication; identifying at least one primary sidelink carrier frequency and at least one secondary sidelink carrier frequency from the sidelink carrier frequencies; as well as Data is sent to a second UE using the at least one primary sidelink carrier frequency and the at least one secondary sidelink carrier frequency.

2. The first UE of claim 1, wherein the sidelink carrier frequency is identified based on one or more of cell-specific signaling received from a network node, UE-specific signaling received from a network node, or a pre-configuration of the UE. 3 . The first UE according to claim 1 , wherein the sidelink carrier frequency is configured in ascending order of Absolute Radio Frequency Channel Number (ARFCN).

4. A first UE according to claim 1, wherein the processor and the transceiver are configured to enable the first UE to: receive from a network node a mapping of one or more of the sidelink carrier frequencies to one or more service types operable for receiving sidelink communications, wherein the mapping is based at least in part on priority information of the service type.

5. The first UE according to claim 1, wherein the processor and the transceiver are configured to enable the first UE to: determine the sidelink carrier frequency based on an association between a serving cell of the UE and the sidelink carrier frequency.

6. The first UE of claim 5, wherein the association of the serving cell of the UE with the sidelink carrier frequency is the same as an association of a primary cell of the UE with the sidelink carrier frequency.

7. The first UE according to claim 1, wherein the processor and the transceiver are configured to enable the first UE: Receive signaling, the signaling comprising: one or more sidelink carrier frequencies associated with one or more synchronization signal blocks (SSBs); as well as The one or more SSBs are received over the one or more sidelink carrier frequencies for synchronization of the at least one primary sidelink carrier frequency and the at least one secondary sidelink carrier frequency.

8. The first UE of claim 7, wherein the one or more sidelink carrier frequencies associated with the one or more SSBs include: The at least one primary sidelink carrier frequency.

9. The first UE of claim 1 , wherein the sidelink carrier frequency is identified based on UE-specific signaling received from a network node, and wherein the UE-specific signaling comprises one or more of: configuration for one or more sidelink synchronization carrier frequencies; one or more priority values ​​of the sidelink carrier frequency; or Mapping information for mapping the sidelink carrier frequency to the sidelink synchronization carrier frequency.

10. A first UE, comprising: Transceiver; as well as a processor coupled to the transceiver, the processor and the transceiver being configured to cause the first UE to: receiving cross-carrier scheduling information, the cross-carrier scheduling information comprising: a scheduling physical downlink control channel (PDCCH) carrying scheduling for downlink control information (DCI) received on a first carrier frequency with a first subcarrier spacing, and a physical sidelink shared channel (PSSCH) carrying scheduling for sidelink transmission to a second UE on a second carrier frequency with a second subcarrier spacing; and The PSSCH is received based on whether the first subcarrier spacing is greater than or less than the second subcarrier spacing.

11. The first UE according to claim 10, wherein the first subcarrier spacing and the second subcarrier spacing respectively comprise: An orthogonal frequency division multiplexing (OFDM) interval of the first carrier frequency and the second carrier frequency.

12. A first UE according to claim 10, wherein when the first subcarrier spacing is smaller than the second subcarrier spacing, if the first symbol in the PSSCH allocation defined by the time slot field in the DCI, and the first symbol of the time slot of the PSSCH transmission starts at least N of the PDCCH symbols after the end of the PDCCH scheduling of the PSSCH, the UE receives the PSSCH.

13. A first UE according to claim 12, wherein the processor and the transceiver are configured to enable the first UE to: independently of the reception timing difference between the scheduling cell and the second carrier frequency, determine whether the first symbol in the PSSCH allocation defined by the time gap field in the DCI, and the first symbol of the time slot of the PSSCH transmission start at least N PDCCH symbols after the end of the PDCCH scheduling of the PSSCH. The first UE according to claim 12 , wherein the N PDCCH symbols are preconfigured in a table.

15. The first UE of claim 12, wherein the time gap field comprises a time slot offset between the DCI and a start of the sidelink transmission.

16. A network node, comprising: Transceiver; as well as a processor coupled to the transceiver, the processor and the transceiver being configured to cause the network node to: generating a notification of sidelink carrier frequencies usable to implement CA for sidelink communications, the notification indicating at least one primary sidelink carrier frequency and at least one secondary sidelink carrier frequency; as well as The notification is sent to the UE.

17. The network node of claim 16, wherein the processor and the transceiver are configured to cause the network node to: generate the notification as one or more of cell-specific signaling or UE-specific signaling.

18. The network node of claim 16, wherein the notification identifies the sidelink carrier frequency based on an index value of the sidelink carrier frequency in an index of sidelink carrier frequencies.

19. The network node of claim 16, wherein the notification identifies the sidelink carrier frequency based on its corresponding Absolute Radio Frequency Channel Number (ARFCN).

20. The network node of claim 16, wherein the notification identifies a respective priority of one or more of the sidelink carrier frequencies.