Transmit (TX) carrier selection for new air interface (NR) sidelink operation

Abstract

Various embodiments herein relate to identifying a transmit carrier for a new air interface (NR) sidelink (SL) transmission. In particular, embodiments may involve identifying a plurality of potential transmit carriers, and then ranking the carriers. The ordering may be performed based at least in part on channel busy rate (CBR) values associated with respective ones of the plurality of potential transmit carriers. Other embodiments may be described and / or claimed.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 395,574, filed on August 5, 2022. Technical Field

[0003] Various embodiments may generally relate to the field of wireless communications.For example, some embodiments may relate to carrier selection for sidelink operation. Background Art

[0004] Various embodiments may generally relate to the field of wireless communications. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] The embodiments will be easily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, similar reference numerals represent similar structural elements. The embodiments are illustrated in the figures of the accompanying drawings by way of example and not by way of limitation.

[0006] Figure 1 An example of a layer 2 structure of a new radio (NR) side link (SL) configured with carrier aggregation (CA) according to various embodiments is shown.

[0007] Figure 2 A flow chart depicting an example process for transmit (TX) carrier reselection is shown in accordance with various embodiments.

[0008] Figure 3 A network according to various embodiments is shown.

[0009] Figure 4 A wireless network 400 according to various embodiments is schematically illustrated.

[0010] Figure 5 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (eg, a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some example embodiments.

[0011] Figure 6 A network according to various embodiments is shown.

[0012] Figure 7 Example procedures are depicted for practicing one or more of the various embodiments discussed herein.

[0013] Figure 8 Alternative example processes are depicted for practicing one or more of the various embodiments discussed herein. DETAILED DESCRIPTION

[0014] The following detailed description refers to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details, such as specific structures, architectures, interfaces, technologies, etc., are described for the purpose of explanation rather than limitation, so as to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to those skilled in the art who benefit from the present disclosure that various aspects of various embodiments can be practiced in other examples that depart from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted to avoid unnecessary details obscuring the description of various embodiments. For the purpose of this document, the phrases "A or B" and "A / B" mean (A), (B), or (A and B).

[0015] In order to support advanced sidelink (SL) vehicle-to-everything (V2X) use cases, it may be desirable to determine a set of relevant component carriers (CCs) for SL transmissions. This determination may be based on consideration of different factors. Embodiments herein relate to one or more of such factors, and the manner in which these factors affect the determination of CCs for transmission may be discussed. Embodiments may also relate to a framework that utilizes them to allow the AS layer to select a suitable set of CCs for transmission.

[0016] More specifically, embodiments herein may relate to an overall protocol stack for supporting CA in NR SL. Embodiments may also relate to selecting component carriers for transmitting NR SL V2X messages. Embodiments may also relate to developing mechanisms for incorporating these concepts as part of the TX carrier selection process for the NR sidelink.

[0017] In general, as the connected world evolves, the use cases for the NR sidelink have changed from catering only to traditional V2X applications. There is a growing interest in the industry to also support commercial and public safety use cases throughout the world, which may have different use case requirements compared to typical V2X use cases. Specifically, for applications involving a high degree of automation (e.g., self-driving vehicles or other similar applications), the need for increased data rates and higher reliability may be more pressing.

[0018] A specific example is the exchange of sensor data between neighboring vehicles, which, when coupled with the large number of different sensors installed in today's vehicles, may mean that data rate requirements are growing larger than typically supported by the 3rd Generation Partnership Project (3GPP) Release 17 (Rel-17) NR SL specification. Similarly, to support accurate positioning via SL, error rate requirements may be much more stringent than before. Such increased error rate requirements may be supported by enhancements to the SL design (e.g., which may be standardized in the 3GPP Release 18 (Rel-18) specification).

[0019] To meet these use case requirements, CA can be used. By allowing transmission on different PC5 carriers, CA can increase the achievable data rate (by transmitting different packets simultaneously on different carriers), increase reliability (by transmitting duplicate packets simultaneously on different carriers), and / or increase the overall capacity of the system.

[0020] Using CA may require solving various issues for the NR side link. Generally, the quality of service (QoS) design in the NR side link has abandoned the legacy per-packet priority (PPPP) and per-packet reliability (PPPR) and moved towards flow-based QoS. Flow-based QoS can be based on standardized PC5 5Qis (PQI) and associated QoS parameter sets. This can allow a much more flexible mapping of V2X service types directly to PC5 QoS parameters, and the access stratum (AS) layer can be responsible for mapping the PC5 QoS profile directly to the radio bearer, rather than associating each individual packet based on its associated priority (e.g., PPPP and / or PPPR). Therefore, it may be expected to perform carrier selection from the perspective of the TX user equipment (UE) based on this updated NR side link with flow-based QoS design.

[0021] Level 2 hierarchy of NR SL with CA configuration

[0022] exist Figure 1 An example general structure for supporting carrier aggregation on the NR side link is depicted in FIG. Figure 1 The example of differs from the legacy Rel-17 SL structure at least due to the inclusion of a separate Hybrid Automatic Repeat Request (HARQ) entity per sidelink carrier, where aggregation occurs at the Medium Access Control (MAC) layer.

[0023] Another aspect to consider is enhancements to UE procedures and signaling to support carrier aggregation for the NR sidelink. However, similar to the case of the Long Term Evolution (LTE) sidelink, it may be desirable to clarify whether there are any differences in UE behavior between network (NW) scheduled operations (Mode 1) and autonomous resource selection (Mode 2). Similar to LTE, the process of carrier and resource selection may typically be entirely under the control of a base station (e.g., a gNodeB ("gNB")), and therefore there is no need to specify a process for selecting a selected carrier. In contrast, for Mode 2, because it is left to the UE itself to select a specific carrier for SL transmission, the embodiments of this document may be described with respect to the Mode 2 case.

[0024] In the following discussion, we consider a different set of factors for the TX UE to consider when selecting a given sidelink carrier for sidelink transmission:

[0025] -QoS Priority

[0026] One factor that can be used to determine whether a UE is allowed to use a specific carrier for SL transmission can be similar to the factors used in legacy LTE designs. In LTE, the UE can be allowed / not allowed to use a specific carrier through a mapping in the SL-CBR-PPPP-TxConfigList (see, for example, 3GPP Technical Specification (TS) 36.331). Specifically, the UE can be configured (via network signaling and / or pre-configuration) with a mapping between physical side link shared channel (PSSCH) TX parameters, channel busy rate (CBR) ranges, and / or PPPP priority ranges. The mapping can be done via an index, and the network can ensure that specific carriers are allowed / not allowed, or that specific carriers are prioritized over other carriers based on the configured range by using a specific configuration. For the NR side link, the principle can be similar to the legacy method described above. However, in NR SL, instead of using PPPP mapping to sl-Priority, the logical channel (LCH) priority configured based on the radio resource control (RRC) PC5 QoS information for a given bearer can be utilized within the SL-CBR-PriorityTxConfigList information element (IE) (see, for example, 3GPP TS 38.331).

[0027] -Sidelink CBR

[0028] In the case of the legacy LTE sidelink, congestion on the channel (which may be described by or related to the CBR) may be a parameter used to determine whether the UE is allowed to consider that particular carrier as available for transmission. Thus, if multiple sidelink carriers are available for transmission, a Tx carrier (re)selection process that considers multiple carriers may be used for the NR sidelink. In some embodiments, each carrier may be associated with an associated list of CBR thresholds for maintaining or reselecting the carrier and SL LCH priorities to which the CBR thresholds are applied. At a high level, when the UE considers each carrier configured by upper layers (e.g., RRC), it may determine whether to maintain use of the carrier or to reselect based on the priority of the logical channel on which data needs to be sent and the CBR threshold.

[0029] An example of an IE for a CBR threshold and associated LCH priority is depicted below. In this embodiment, the "priority" depicted below may refer to the priority of a logical channel defined in 3GPP TS 38.321, rather than PPPP.

[0030] Sidelink Frequency Selection Configuration Message

[0031]

[0032]

[0033] -Sidelink HARQ feedback information

[0034] If hybrid automatic repeat request (HARQ) feedback is configured for one, multiple, or all carriers in SL CA, information about the frequency of negative acknowledgements (NACKs) or other metrics derived from the HARQ feedback may be included in the SL CA carrier selection process. Options for how this information may be used or employed may include one or more of the following:

[0035] • NACK feedback rate per carrier: The UE collects its NACK feedback rate for transmissions occurring on different carriers.

[0036] ● Percentage of NACK: The UE collects the percentage of NACK feedback among all HARQ feedback received on different carriers.

[0037] ● NACK feedback rate received for its own transmission: The UE collects the NACK feedback rate received for its own transmission for different carriers.

[0038] • Percentage of NACKs for own transmissions: The UE collects the percentage of NACK feedbacks received for its own transmissions for different carriers.

[0039] It should be understood that the above metrics may not be mutually exclusive, and more than one metric may be used in combination with other metrics for carrier selection. To employ the above metrics, the UE may determine the NACK feedback rate by cumulatively counting / collecting acknowledgement (ACK) / NACK feedback over time (e.g., cumulative or "long-term" statistics), or by considering an observation period whose length may be either fixed or (pre-)configured (e.g., "short-term" statistics).

[0040] In any case, the rate of NACKs received on a given carrier in the carrier selection process may be used by assigning different priorities to carriers based on the corresponding HARQ feedback rates.

[0041] - Sidelink CQI information

[0042] 3GPP Release 16 (Rel. 16) specifications introduce the ability to request channel state information (CSI) feedback from other UEs for unicast connections. Therefore, channel quality indicators (CQIs) of different carriers that are only relevant to unicast connections to other UEs can be solicited. If the goal is to establish a high data rate connection to another UE, it may be desirable to also consider channels at different component carriers (CCs) for this UE. Therefore, during the carrier selection process, the UE may be able to assign different priorities to candidate carriers based on the CQI information received on the unicast link.

[0043] -Carrier frequency considerations (including ITS, FR2, and unlicensed bands)

[0044] Another factor to consider in the selection of the sidelink carrier may be a factor such as the carrier frequency or some other distinguishable characteristic about the carrier itself. Legacy LTE V2X may have been restricted to Intelligent Transport System (ITS) carriers on frequency range 1 (FR1). However, for NR sidelink operation, frequency range 2 (FR2) as well as unlicensed bands may be used. Therefore, it is generally the carrier aggregation process, and in particular carrier selection, that may take into account whether the selected carrier is for operation on FR1, FR2, or an unlicensed band. In some embodiments, this information may be inferred based in part on upper layer / application layer information and / or network configuration. From a configuration perspective, each carrier configured to a given UE may additionally have this information indicated together to allow the UE to select (or not select) a given carrier (as part of the TX carrier (re)selection process).

[0045] As used herein, the terms frequency range 1 (which may be abbreviated as "FR-1", "FR1", etc.) and / or frequency range 2 (which may be abbreviated as "FR-2", "FR2", etc.) may refer to a frequency bandwidth defined by the Third Generation Partnership Project (3GPP), for example, in Technical Specification (TS) 38.104, whether previously defined, defined at the time of filing this document, or defined at some future time. In some specific embodiments, frequency range 1 may refer to a frequency bandwidth between approximately 410 megahertz (MHz) and approximately 7125 MHz. In other specific embodiments, frequency range 1 may refer to a frequency bandwidth less than or equal to approximately 6000 MHz. Similarly, in specific embodiments, frequency range 2 may refer to a bandwidth between approximately 24250 MHz and approximately 71000 MHz. In some embodiments, a bandwidth between approximately 24250 MHz and approximately 52600 MHz may be referred to as frequency range 2-1 (which may be abbreviated as "FR2-1", "FR 2-1", etc.). The bandwidth between approximately 52,600 MHz and approximately 71,000 MHz may be referred to as frequency range 2-2 (which may be abbreviated as “FR2-2”, “FR 2-2”, etc.).

[0046] -Service Type

[0047] Another factor that may be considered is the specific service / service type set for which the sidelink packets are generated for transmission. Based on the mapping between specific service types and the set of carrier frequencies / CCs visible to the AS layer, the UE can determine whether a specific CC is allowed for V2X transmission. In some embodiments, such mapping may depend on non-radio related regulatory aspects that the UE can be expected to always comply with. Therefore, in some embodiments, this factor may be considered as a binary (e.g., yes / no) decision (i.e., based on whether the initiating service type is allowed, a specific carrier is either considered for transmission or excluded). This criterion may be implemented as a separate filtering step in the AS layer, or more likely included as part of the configuration from RRC and / or upper layers. An example of this consideration is shown in Figure 2 and described in further detail below.

[0048] -Synchronization reference priority:

[0049] During the carrier selection process, the priority of the synchronization reference may itself be considered. The process of synchronization in the NR sidelink may be similar to the legacy LTE V2X design. Therefore, it may be assumed that if there are multiple (pre-)configured sidelink carriers, if multiple synchronization carriers are available among multiple SL carriers, the UE may be configured to prioritize between them based on the configured synchronization priority.

[0050] Based on the above factors, in an embodiment, the configuration for each sidelink carrier may allow the UE to select and / or prioritize the sidelink carrier during the TX carrier selection process. An example of such a configuration is depicted below, where the network may optionally configure one or more of the following example parameters to allow the UE to prioritize or de-prioritize the selection of a carrier. During the carrier (re)selection process, the UE is only allowed to select a carrier if it meets the criteria set as part of the configuration (e.g., HARQ feedback rate, CQI, type of carrier, etc.).

[0051] Sidelink Carrier Frequency Configuration Priority Message

[0052]

[0053]

[0054] Overall mechanism for carrier selection

[0055] In this case, an example mechanism for UE operation can be found in Figure 2For each applicable carrier associated with a sidelink logical channel that needs to send data, if the CBR on the carrier is below an appropriate threshold, the UE may consider that carrier as a viable candidate for transmission (depending on whether that carrier was previously selected). Once there is a set of such candidate carriers to choose from, there are different options in terms of the selection of the carrier:

[0056] 1. The UE may rank and select the candidate carriers based solely on their priority in terms of measured CBR level, starting with the lowest first.

[0057] 2. The UE may consider a combination of one or more of the CBR level and other factors discussed above (e.g., carrier frequency, authorized vs. unauthorized, etc.) to rank and select carriers for transmission. The criteria and associated configurations to be considered in this case may be provided by the network or preconfigured to the UE.

[0058] 3. The UE may randomly select carriers from the candidate settings based on its capabilities, up to the maximum number of carriers.

[0059] Impact on the listening and resource selection process

[0060] Once a carrier is selected, the same carrier may be used for all medium access control (MAC) protocol data units (PDUs) of the same sidelink process, at least until resource reselection is triggered for the same sidelink process. The selected carrier that may be used for TX and / or reception (RX) of CA may be semi-statically indicated to the UE via higher layers.

[0061] This candidate CC set may be used during the listening and resource selection process, which may be modified to allow CA based on one or more of the following options:

[0062] • The Rel.16 sensing and resource selection process may be reused and applied independently on each CC or each group of CCs. In this case, the resources may be aggregated on a carrier based on whether they meet the selection criteria per CC or per group of CCs.

[0063] ● The Rel.16 listening and resource selection process can be applied jointly on all candidate CCs. In this case,

[0064] o The sensing may be performed over the entire bandwidth (BW) including all candidate CCs, and the sensing threshold may be scaled by a factor proportional to the number of CCs measured jointly; and / or

[0065] o Resources may be aggregated on a carrier based on whether they meet the selection criteria on all candidate CCs.

[0066] • During the sensing and resource selection process, the UE may sense each CC independently on all candidate CCs. However, the UE may select resources to be used jointly on all candidate CCs.

[0067] It should be understood that in some embodiments, the above options may not be mutually exclusive and more than one option may be adopted and used based on (pre-)configuration and / or capabilities of the UE.

[0068] Systems and implementation

[0069] Figure 3-6 Various systems, devices, and components are shown in which aspects of the disclosed embodiments may be implemented.

[0070] Figure 3 A network 300 according to various embodiments is shown. The network 300 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems. However, example embodiments are not limited thereto, and the described embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems, etc.

[0071] The network 300 may include a UE 302, which may include any mobile or non-mobile computing device designed to communicate with the RAN 304 via an air connection. The UE 302 may be communicatively coupled to the RAN 304 via a Uu interface. The UE 302 may be, but is not limited to, a smartphone, a tablet computer, a wearable computer device, a desktop computer, a laptop computer, an in-vehicle infotainment device, an in-vehicle entertainment device, an instrument cluster, a head-mounted display device, an on-board diagnostic device, a dashboard mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked appliance, a machine type communication device, an M2M or D2D device, an IoT device, etc.

[0072] In some embodiments, the network 300 may include multiple UEs directly coupled to each other via a sidelink interface. The UE may be an M2M / D2D device that communicates using a physical sidelink channel (e.g., but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.).

[0073] In some embodiments, UE 302 may additionally communicate with AP 306 via an over-the-air connection. AP 306 may manage WLAN connections, which may be used to offload some / all network traffic from RAN 304. The connection between UE 302 and AP 306 may conform to any IEEE 802.11 protocol, wherein AP 306 may be a Wireless Fidelity Router. In some embodiments, UE 302, RAN 304, and AP 306 may utilize cellular-WLAN aggregation (eg, LWA / LWIP). Cellular-WLAN aggregation may involve UE 302 being configured by RAN 304 to utilize both cellular radio resources and WLAN resources.

[0074] RAN 304 may include one or more access nodes, such as AN 308. AN 308 may terminate the air interface protocol for UE 302 by providing access layer protocols, including RRC, PDCP, RLC, MAC, and L1 protocols. In this way, AN 308 may implement data / voice connections between CN 320 and UE 302. In some embodiments, AN 308 may be implemented in a discrete device, or as one or more software entities running on a server computer as part of a virtual network (which may be referred to as a CRAN or a virtual baseband unit pool), for example. AN 308 is referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN 308 may be a macro cell base station, or a low power base station for providing a femto cell, a pico cell, or other similar cells with a smaller coverage area, a smaller user capacity, or a higher bandwidth than a macro cell.

[0075] In an embodiment where the RAN 304 includes multiple ANs, they may be coupled to each other via an X2 interface (if the RAN 304 is an LTE RAN) or an Xn interface (if the RAN 304 is a 5G RAN). The X2 / Xn interface (which may be separated into a control / user plane interface in some embodiments) may allow the ANs to transfer information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0076] The ANs of the RAN 304 may each manage one or more cells, cell groups, component carriers, etc., to provide an air interface for network access to the UE 302. The UE 302 may be simultaneously connected to multiple cells provided by the same or different ANs of the RAN 304. For example, the UE 302 and the RAN 304 may use carrier aggregation to allow the UE 302 to connect to multiple component carriers, each corresponding to a Pcell or an Scell. In a dual connectivity scenario, the first AN may be a primary node providing an MCG, and the second AN may be a secondary node providing an SCG. The first / second AN may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0077] RAN 304 may provide an air interface on a licensed spectrum or an unlicensed spectrum. To operate in an unlicensed spectrum, a node may use LAA, eLAA, and / or feLAA mechanisms with PCell / Scell ​​based on CA technology. Before accessing the unlicensed spectrum, a node may perform a medium / carrier sensing operation based on, for example, a listen-before-talk (LBT) protocol.

[0078] In the V2X scenario, the UE 302 or AN 308 may be or act as an RSU, which may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable AN or a fixed (or relatively fixed) UE. An RSU implemented in or by the following items: for a UE, it may be referred to as a "UE-type RSU"; for an eNB, it may be referred to as an "eNB-type RSU"; for a gNB, it may be referred to as a "gNB-type RSU"; etc. In one example, the RSU is a computing device coupled to a radio frequency circuit located on the roadside that provides connection support to passing vehicle UEs. The RSU may also include internal data storage circuits for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may provide very low latency communications required for high-speed events (e.g., collision avoidance, traffic warnings, etc.). Additionally or alternatively, the RSU may provide other cellular / WLAN communication services. The components of the RSU may be housed in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller for providing a wired connection (e.g., Ethernet) to a traffic signal controller or backhaul network.

[0079] In some embodiments, the RAN 304 may be an LTE RAN 310 with an eNB (e.g., eNB 312). The LTE RAN 310 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL ​​and SC-FDMA waveform for UL; Turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurement, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate on a sub-6 GHz frequency band.

[0080] In some embodiments, the RAN 304 may be a NG-RAN 314 having a gNB (e.g., gNB 316) or an ng-eNB (e.g., ng-eNB 318). The gNB 316 may be connected to a 5G-enabled UE using a 5GNR interface. The gNB 316 may be connected to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 318 may also be connected to the 5G core via an NG interface, but may be connected to the UE via an LTE air interface. The gNB 316 and the ng-eNB 318 may be connected to each other via an Xn interface.

[0081] In some embodiments, the NG interface can be divided into two parts: an NG user plane (NG-U) interface, which carries service data between the nodes of the NG-RAN 314 and the UPF 348 (e.g., the N3 interface); and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN 314 and the AMF 344 (e.g., the N2 interface).

[0082] NG-RAN 314 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polarization codes, Repetition codes, Simplex codes and Reed-Muller codes for control, and LDPC for data. Similar to the LTE air interface, the 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS. The 5G-NR air interface may not use CRS, but may use PBCHDMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signals for time tracking. The 5G-NR air interface may operate on a FR1 band including a sub-6 GHz band or a FR2 band including a band from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB, which is an area of ​​a downlink resource grid including PSS / SSS / PBCH.

[0083] In some embodiments, the 5G-NR air interface may utilize BWP for various purposes. For example, BWP may be used for dynamic adaptation of SCS. For example, UE 302 may be configured with multiple BWPs, each of which is configured with a different SCS. When a BWP change is indicated to UE 302, the transmitted SCS also changes. Another use case example of BWP is related to power saving. Specifically, UE 302 may be configured with multiple BWPs having different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. A BWP containing a smaller number of PRBs may be used for data transmission with a small traffic load while allowing power saving at UE 302 and in some cases at gNB 316. A BWP containing a larger number of PRBs may be used in scenarios with higher traffic loads.

[0084] RAN 304 is communicatively coupled to CN 320, which includes network elements to provide various functions to support data and telecommunication services to customers / subscribers (e.g., users of UE 302). The components of CN 320 may be implemented in one physical node or in separate physical nodes. In some embodiments, NFV may be used to virtualize any or all functions provided by the network elements of CN 320 onto physical computing / storage resources in servers, switches, etc. A logical instantiation of CN 320 may be referred to as a network slice, and a logical instantiation of a portion of CN 320 may be referred to as a network sub-slice.

[0085] In some embodiments, CN 320 may be LTE CN 322 (which may also be referred to as EPC). LTE CN 322 may include MME 324, SGW 326, SGSN 328, HSS 330, PGW 332, and PCRF 334, which are coupled to each other via interfaces (or "reference points") as shown. The functions of the elements of LTE CN 322 may be briefly described as follows.

[0086] The MME 324 may implement mobility management functions to track the current location of the UE 302 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, and the like.

[0087] The SGW 326 may terminate the S1 interface towards the RAN and route data packets between the RAN and the LTE CN 322. The SGW 326 may be a local mobility anchor for handovers between RAN nodes and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include legal interception, billing, and some policy enforcement.

[0088] SGSN 328 can track the location of UE 302 and perform security functions and access control. In addition, SGSN 328 can perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection specified by MME 324; MME selection for handover; etc. The S3 reference point between MME 324 and SGSN 328 can realize user and bearer information exchange for 3GPP indirect access mobility in idle / active state.

[0089] HSS 330 may include a database for network users, including subscription related information, to support network entities in handling communication sessions. HSS 330 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc. The S6a reference point between HSS 330 and MME 324 may enable the transfer of subscription and authentication data for authenticating / authorizing users to access LTE CN 320.

[0090] The PGW 332 may terminate the SGi interface towards a data network (DN) 336, which may include an application / content server 338. The PGW 332 may route data packets between the LTE CN 322 and the data network 336. The PGW 332 may be coupled to the SGW 326 via an S5 reference point to facilitate user plane tunnels and tunnel management. The PGW 332 may also include a node (e.g., PCEF) for policy enforcement and charging data collection. In addition, the SGi reference point between the PGW 332 and the data network 336 may be an operator external public, private PDN, or an operator internal packet data network (e.g., for provisioning IMS services). The PGW 332 may be coupled to the PCRF 334 via a Gx reference point.

[0091] PCRF 334 is the policy and charging control element of LTE CN 322. PCRF 334 may be communicatively coupled to app / content server 338 to determine appropriate QoS and charging parameters for service flows. PCRF 332 may distribute the associated rules to PCEF with appropriate TFT and QCI (via Gx reference point).

[0092] In some embodiments, CN 320 may be 5GC 340. 5GC 340 may include AUSF 342, AMF 344, SMF 346, UPF 348, NSSF 350, NEF 352, NRF 354, PCF 356, UDM 358, and AF 360, which are coupled to each other through interfaces (or "reference points") as shown. The functions of the elements of 5GC 340 may be briefly described as follows.

[0093] AUSF 342 can store data for authentication of UE 302 and handle authentication related functions. AUSF 342 can facilitate a common authentication framework for various access types. In addition to communicating with other elements of 5GC 340 through reference points as shown, AUSF 342 can also expose interfaces based on Nausf services.

[0094] AMF 344 may allow other functions of 5GC 340 to communicate with UE 302 and RAN 304 and subscribe to notifications about mobility events for UE 302. AMF 344 may be responsible for registration management (e.g., for registering UE 302), connection management, reachability management, mobility management, legal interception of AMF-related events, and access authentication and authorization. AMF 344 may provide transport for SM messages between UE 302 and SMF 346 and act as a transparent proxy for routing SM messages. AMF 344 may also provide transport for SMS messages between UE 302 and SMSF. AMF 344 may interact with AUSF 342 and UE 302 to perform various security anchoring and context management functions. In addition, AMF 344 may be a termination point for the RAN CP interface, which may include or be an N2 reference point between RAN 304 and AMF 344; and AMF 344 may be a termination point for NAS (N1) signaling and perform NAS encryption and integrity protection. AMF 344 may also support NAS signaling with UE 302 through the N3 IWF interface.

[0095] SMF 346 may be responsible for SM (e.g., session establishment, tunnel management between UPF 348 and AN 308); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring traffic steering at UPF 348 to route traffic to the correct destination; terminating interfaces toward policy control functions; controlling a portion of policy enforcement, billing, and QoS; legal interception (for SM events and interfaces to LI systems); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent to AN 308 via AMF 344 over N2; and determining the SSC mode for a session. SM may refer to the management of a PDU session, and a PDU session or "session" may refer to a PDU connection service that provides or enables the exchange of PDUs between UE 302 and data network 336.

[0096] The UPF 348 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 336, and a branch point to support multi-homed PDU sessions. The UPF 348 may also perform packet routing and forwarding, perform packet inspection, implement the user plane portion of policy rules, legal intercept packets (UP collection), perform service usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink service verification (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 348 may include an uplink classifier to support routing of service flows to the data network.

[0097] NSSF 350 may select a set of network slice instances to serve UE 302. NSSF 350 may also determine the allowed NSSAI and the mapping to the subscribed S-NSSAI (if necessary). NSSF 350 may also determine the AMF set or list of candidate AMFs to be used to serve UE 302 based on appropriate configuration and possibly by querying NRF 354. The selection of a set of network slice instances for UE 302 may be triggered by the AMF 344 registered by UE 302 through interaction with NSSF 350, which may result in a change of AMF. NSSF 350 may interact with AMF 344 via the N22 reference point; and may communicate with another NSSF in the visited network via the N31 reference point (not shown). In addition, NSSF 350 may expose an interface based on Nnssf services.

[0098] NEF 352 can securely open the services and capabilities provided by 3GPP network functions to third parties, internal opening / reopening, AF (e.g., AF360), edge computing or fog computing systems, etc. In such an embodiment, NEF 352 can authenticate, authorize or restrict AF. NEF 352 can also convert information exchanged with AF 360 and information exchanged with internal network functions. For example, NEF 352 can convert between AF service identifiers and internal 5GC information. NEF 352 can also receive information from other NFs based on the capabilities opened by other NFs. The information can be stored at NEF 352 as structured data, or stored at a data storage NF using a standardized interface. The stored information can then be reopened by NEF 352 to other NFs and AFs, or used for other purposes (e.g., analysis). In addition, NEF 352 can display interfaces based on Nnef services.

[0099] NRF 354 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information of discovered NF instances to NF instances. NRF 354 also maintains information of available NF instances and the services they support. As used herein, the terms "instantiate", "instantiation", etc. may refer to the creation of an instance, while "instance" may refer to the specific appearance of an object, which may occur, for example, during program code execution. In addition, NRF 354 may expose an interface based on Nnrf services.

[0100] PCF 356 can provide policy rules to control plane functions to implement them, and can also support a unified policy framework to manage network behavior. PCF 356 can also implement a front end to access subscription information related to policy decisions in the UDR of UDM 358. In addition to communicating with functions through reference points as shown in the figure, PCF 356 also exposes an interface based on Npcf services.

[0101] UDM 358 can process subscription-related information to support the processing of communication sessions by network entities, and can store subscription data of UE 302. For example, subscription data can be transferred via the N8 reference point between UDM 358 and AMF 344. UDM 358 can include two parts: application front end and UDR. UDR can store subscription data and policy data for UDM 358 and PCF 356, and / or structured data for openness and application data for NEF 352 (including PFD for application detection, application request information for multiple UE 302). Nudr service-based interfaces can be displayed by UDR to allow UDM 358, PCF 356 and NEF 352 to access a specific set of stored data, as well as read, update (e.g., add, modify), delete and subscribe to notifications of changes in relevant data in UDR. UDM may include UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. Several different front ends can serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identity processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs through reference points as shown, the UDM 358 can also expose Nudm service-based interfaces.

[0102] AF 360 can provide application impact on service routing, provide access to NEF, and interact with the policy framework for policy control.

[0103] In some embodiments, 5GC 340 can enable edge computing by selecting an operator / third-party service to be geographically close to the point where UE 302 attaches to the network. This can reduce latency and load on the network. In order to provide edge computing implementation, 5GC 340 can select UPF 348 close to UE 302 and perform service guidance from UPF 348 to data network 336 via N6 interface. This can be based on UE subscription data, UE location and information provided by AF 360. In this way, AF 360 can affect UPF (re)selection and service routing. Based on operator deployment, when AF 360 is considered a trusted entity, the network operator can allow AF 360 to interact directly with relevant NFs. In addition, AF 360 can expose an interface based on Naf services.

[0104] The data network 336 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers (including, for example, application / content server 338).

[0105] Figure 4 Schematically illustrated is a wireless network 400 in accordance with various embodiments. The wireless network 400 may include a UE 402 in wireless communication with an AN 404. The UE 402 and AN 404 may be similar to, and substantially interchangeable with, similarly named components described elsewhere herein.

[0106] UE 402 may be communicatively coupled to AN 404 via connection 406. Connection 406 is shown as an air interface that enables the communicative coupling and may conform to a cellular communication protocol, such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6 GHz frequencies.

[0107] UE 402 may include a host platform 408 coupled to a modem platform 410. Host platform 408 may include application processing circuitry 412, which may be coupled to protocol processing circuitry 414 of modem platform 410. Application processing circuitry 412 may run various applications for outgoing / incoming application data of UE 402. Application processing circuitry 412 may also implement one or more layer operations to send / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and Internet (e.g., IP) operations.

[0108] Protocol processing circuitry 414 may implement one or more layer operations to facilitate sending or receiving data over connection 406. The layer operations implemented by protocol processing circuitry 414 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0109] The modem platform 410 may also include digital baseband circuitry 416, which may implement one or more layer operations that are "lower" layer operations in the network protocol stack that are performed by the protocol processing circuitry 414. These operations may include, for example, PHY operations, including one or more of the following: HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding (which may include one or more of space-time, space-frequency, or space coding), reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions.

[0110] The modem platform 410 may also include transmit circuitry 418, receive circuitry 420, RF circuitry 422, and an RF front end (RFFE) 424, which may include or be connected to one or more antenna panels 426. In short, the transmit circuitry 418 may include digital-to-analog converters, mixers, intermediate frequency (IF) components, etc.; the receive circuitry 420 may include analog-to-digital converters, mixers, IF components, etc.; the RF circuitry 422 may include low noise amplifiers, power amplifiers, power tracking components, etc.; the RFFE 424 may include filters (e.g., surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 418, receive circuitry 420, RF circuitry 422, RFFE 424, and antenna panels 426 (generally referred to as "transmit / receive components") may be specific to the details of a particular implementation, such as whether the communication is TDM or FDM, at mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be provided in the same or different chips / modules, etc.

[0111] In some embodiments, the protocol processing circuitry 414 may include one or more instances of control circuitry (not shown) for providing control functionality for the transmit / receive components.

[0112] UE reception may be established by and via antenna panel 426, RFFE 424, RF circuitry 422, receive circuitry 420, digital baseband circuitry 416, and protocol processing circuitry 414. In some embodiments, antenna panel 426 may receive transmissions from AN 404 via receive beamformed signals received by multiple antennas / antenna elements of one or more antenna panels 426.

[0113] UE transmission may be established by and via protocol processing circuitry 414, digital baseband circuitry 416, transmit circuitry 418, RF circuitry 422, RFFE 424, and antenna panel 426. In some embodiments, the transmit component of UE 404 may apply spatial filtering to the data to be transmitted to form transmit beams emitted by antenna elements of antenna panel 426.

[0114] Similar to UE 402, AN 404 may include a host platform 428 coupled to a modem platform 430. Host platform 428 may include application processing circuitry 432 coupled to protocol processing circuitry 434 of modem platform 430. The modem platform may also include digital baseband circuitry 436, transmit circuitry 438, receive circuitry 440, RF circuitry 442, RFFE circuitry 444, and antenna panel 446. The components of AN 404 may be similar to and substantially interchangeable with similarly named components of UE 402. In addition to performing data transmission / reception as described above, the components of AN 408 may also perform various logical functions, including, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0115] Figure 5 is a block diagram illustrating components according to some example embodiments that are capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein. Specifically, Figure 5 A graphical representation of hardware resources 500 is shown, including one or more processors (or processor cores) 510, one or more memory / storage devices 520, and one or more communication resources 530, each of which may be communicatively coupled via a bus 540 or other interface circuitry. For embodiments utilizing node virtualization (e.g., NFV), a hypervisor 502 may be executed to provide an execution environment for one or more network slices / subslices to utilize the hardware resources 500.

[0116] Processor 510 may include, for example, processor 512 and processor 514. Processor 510 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP (e.g., a baseband processor), an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0117] The memory / storage device 520 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 520 may include, but is not limited to, any type of volatile, non-volatile, or semi-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, etc.

[0118] The communication resources 530 may include an interconnect or network interface controller, component, or other suitable device to communicate with one or more peripheral devices 504 or one or more databases 506 or other network elements via the network 508. For example, the communication resources 530 may include a wired communication component (e.g., for coupling via USB, Ethernet, etc.), a cellular communication component, an NFC component, (or ) components, components and other communication components.

[0119] The instructions 550 may include software, programs, applications, applet, apps, or other executable code for causing at least any processor 510 to perform any one or more of the methods discussed herein. The instructions 550 may reside in whole or in part in at least one of the processor 510 (e.g., in a cache memory of the processor), the memory / storage device 520, or any suitable combination thereof. In addition, any portion of the instructions 550 may be transmitted to the hardware resources 500 from any combination of the peripheral device 504 or the database 506. Therefore, the memory of the processor 510, the memory / storage device 520, the peripheral device 504, and the database 506 are examples of computer-readable and machine-readable media.

[0120] Figure 6 A network 600 according to various embodiments is shown. The network 600 may be operated in a manner that complies with the 3GPP technical specification or a technical report for a 6G system. In some embodiments, the network 600 may be operated simultaneously with the network 300. For example, in some embodiments, the network 600 may share one or more frequency or bandwidth resources with the network 300. As a specific example, a UE (e.g., UE 602) may be configured to operate in both the network 600 and the network 300. This configuration may be based on the UE including a circuit configured to communicate with the frequency and bandwidth resources of both the networks 300 and 600. Typically, several elements of the network 600 may share one or more characteristics with elements of the network 300. For brevity and clarity, these elements are not repeated in the description of the network 600.

[0121] The network 600 may include a UE 602, which may include any mobile or non-mobile computing device designed to communicate with the RAN 608 via an over-the-air connection. The UE 602 may be similar to, for example, the UE 302. The UE 602 may include, but is not limited to, a smartphone, a tablet computer, a wearable computer device, a desktop computer, a laptop computer, an in-vehicle infotainment, an in-vehicle entertainment device, an instrument cluster, a head-mounted display device, an on-board diagnostic device, a dashboard mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a connected appliance, a machine type communication device, an M2M or D2D device, an IoT device, etc.

[0122] Although in Figure 6 Although not specifically shown in FIG. 6 , in some embodiments, the network 600 may include multiple UEs directly coupled to each other via a sidelink interface. The UE may be an M2M / D2D device that communicates using a physical sidelink channel (e.g., but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.). Similarly, although in Figure 6 6, but UE 602 can communicate with AP (e.g., Figure 3 Additionally, although in Figure 6 Although not specifically shown, in some embodiments, the RAN 608 may include one or more ANs (e.g., Figure 3 The RAN 608 and / or the AN of the RAN 608 may be referred to as a base station (BS), a RAN node, or by some other terminology or name.

[0123] UE 602 and RAN 608 may be configured to communicate via an air interface that may be referred to as a sixth generation (6G) air interface. The 6G air interface may include one or more features (e.g., communication in terahertz (THz) or sub-THz bandwidth, or joint communication and listening). As used herein, the term "joint communication and listening" may refer to a system that allows wireless communication and radar-based listening via various types of multiplexing. As used herein, THz or sub-THz bandwidth may refer to communications in a frequency range of 80 GHz and above. This frequency range may be additionally or alternatively referred to as a "millimeter wave" or "mmWave" frequency range.

[0124] The RAN 608 may enable communication between the UE 602 and a 6G core network (CN) 610. Specifically, the RAN 608 may facilitate the transmission and reception of data between the UE 602 and the 6G CN 610. The 6G CN 610 may include various functions (e.g., NSSF 350, NEF 352, NRF 354, PCF 356, UDM 358, AF 360, SMF 346, and AUSF 342). The 6GCN 610 may also include a UPF 348 and a DN 336, such as Figure 6 shown.

[0125] Additionally, the RAN 608 may include various additional functions in addition to or in place of the functions of a legacy cellular network (e.g., a 4G or 5G network). Two such functions may include a compute control function (Comp CF) 624 and a compute service function (Comp SF) 636. The Comp CF 624 and the Comp SF 636 may be parts or functions of a compute service plane. The Comp CF 624 may be a control plane function that provides functions such as management of the Comp SF 636, computing task context generation and management (e.g., create, read, modify, delete), interacting with the underlying computing infrastructure for computing resource management, and the like. The Comp SF 636 may be a user plane function that acts as a gateway to interface computing service users (e.g., UE 602) and computing nodes behind the Comp SF instance. Some functions of the Comp SF 636 may include: parsing computing service data received from users to compute tasks that can be performed by computing nodes; maintaining a service mesh entry gateway or service API gateway; service and billing policy enforcement; performance monitoring and telemetry collection, and the like. In some embodiments, a Comp SF 636 instance may act as a user plane gateway for a cluster of compute nodes. A Comp CF 624 instance may control one or more Comp SF 636 instances.

[0126] Two other such functions may include a communication control function (Comm CF) 628 and a communication service function (CommSF) 638, which may be part of the communication service plane. Comm CF 628 may be a control plane function for managing Comm SF 638, communication session creation / configuration / release, and managing communication session contexts. Comm SF 638 may be a user plane function for data transmission. Comm CF 628 and Comm SF 638 may be viewed as related to Figure 3The upgrade of SMF 346 and UPF 348 described in the 5G system in FIG. The upgrade provided by Comm CF 628 and Comm SF 638 can realize service-aware transmission. For legacy (e.g., 4G or 5G) data transmission, SMF 346 and UPF 348 can still be used.

[0127] Two other such functions may include a data control function (Data CF) 622 and a data service function (DataSF) 632, which may be part of a data service plane. The Data CF 622 may be a control plane function and provide functions such as Data SF 632 management, data service creation / configuration / release, data service context management, etc. The Data SF 632 may be a user plane function and act as a gateway between data service users (e.g., various functions of the UE 602 and 6G CN 610) and data service endpoints behind the gateway. Specific functions may include: parsing data service user data and forwarding to corresponding data service endpoints, generating billing data, and reporting data service status.

[0128] Another such function may be a service orchestration and linking function (SOCF) 620, which may discover, orchestrate, and link communication / computing / data services provided by functions in the network. Upon receiving a service request from a user, SOCF 620 may interact with one or more of Comp CF 624, Comm CF 628, and Data CF 622 to identify Comp SF 636, Comm SF 638, and Data SF 632 instances, configure service resources, and generate a service chain, which may contain multiple Comp SF 636, Comm SF 638, and Data SF 632 instances and their associated computing endpoints. Workload processing and data movement may then be performed within the generated service chain. SOCF 620 may also be responsible for maintaining, updating, and releasing the created service chain.

[0129] Another such function may be a service registration function (SRF) 614, which may act as a registry for system services provided in the user plane, such as services provided by service endpoints behind the Comp SF 636 and Data SF 632 gateways and services provided by the UE 602. The SRF 614 may be viewed as a peer to the NRF 354, which may act as a registry for network functions.

[0130] Other such functions may include the evolved service communication proxy (eSCP) and the service infrastructure control function (SICF) 626, which can provide service communication infrastructure for control plane services and user plane services. The eSCP may be related to the service communication proxy (SCP) of 5G, where the user plane service communication proxy capability is added. Therefore, the eSCP is represented as two parts: eCSP-C 612 and eSCP-U 634, for control plane service communication proxy and user plane service communication proxy, respectively. The SICF 626 can control and configure the eCSP instance in terms of service business routing policies, access rules, load balancing configuration, performance monitoring.

[0131] Another such function is AMF 644. AMF 644 may be similar to 344, but with additional functionality. Specifically, AMF 644 may include potential functional re-splitting (e.g., moving message forwarding functionality from AMF 644 to RAN 608).

[0132] Another such function is the service orchestration exposure function (SOEF) 618. The SOEF may be configured to expose service orchestration and link services to external users (eg, applications).

[0133] The UE 602 may include an additional function called a compute client service function (comp CSF) 604. The Comp CSF 604 may have both control plane functions and user plane functions, and may interact with corresponding network-side functions (e.g., SOCF 620, Comp CF 624, Comp SF 636, Data CF 622, and / or Data SF 632) for service discovery, request / response, computing task workload exchange, etc. The Comp CSF 604 may also work with the network-side functions to decide whether computing tasks should be run on elements of the UE 602, RAN 608, and / or 6G CN 610.

[0134] UE 602 and / or Comp CSF 604 may include a service mesh proxy 606. Service mesh proxy 606 may act as a proxy for service-to-service communications in the user plane. Capabilities of service mesh proxy 606 may include one or more of addressing, security, load balancing, and the like.

[0135] Example Process

[0136] In some embodiments, Figure 3-6 The electronic device, network, system, chip or component of some other figures of this document or its part or implementation may be configured to perform one or more processes, techniques or methods or parts thereof as described herein. Figure 7 Such a process is depicted in . For example, the process may include: at 701, for each carrier in a group of carriers, determining whether SL communication is allowed to obtain a group of SL allowed carriers from the group of carriers; at 702, sorting the group of SL allowed carriers based at least in part on a channel busy rate (CBR) to provide the group of SL allowed carriers as a group of sorted SL allowed carriers; and at 703, selecting one or more of the SL allowed carriers based on the sorting of the group of sorted SL allowed carriers.

[0137] exist Figure 8 Another such process is depicted in . Figure 8 The process may include or involve a method performed by a user equipment (UE), one or more elements of the UE, and / or one or more electronic devices including and / or implementing the UE. The process may include: at 801, identifying multiple transmission carriers for new radio (NR) side link (SL) transmission; at 802, identifying corresponding channel busy rate (CBR) values ​​associated with the corresponding multiple transmission carriers; at 803, identifying a transmission carrier subset from the multiple transmission carriers based on a comparison of the corresponding CBR values ​​with a CBR threshold; at 804, selecting a transmission carrier based on the corresponding CBR values ​​of the transmission carrier subset; and at 805, performing or facilitating the performance of NR SL transmission on the selected transmission carrier.

[0138] For one or more embodiments, at least one component described in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes and / or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the preceding figures may be configured to operate according to one or more examples described below. As another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the preceding figures may be configured to operate according to one or more examples described below in the example section.

[0139] Example

[0140] Example 1 may include: a method for selecting multiple TX carriers for NR sidelink transmission to support high data rate use cases.

[0141] Example 2 may include a method as described in Example 1 and / or some other examples herein, wherein each sidelink carrier is associated with a separate SL HARQ entity, wherein aggregation occurs at the MAC layer.

[0142] Example 3 may include a method as described in Example 1 and / or some other examples herein, wherein when selecting a candidate carrier for transmission, the TX UE in Mode 2 specifically considers any combination of the following set of factors:

[0143] a. QoS priority for sidelink data, where the UE is configured with SL-LCH priority and ranges for CBR and PSSH TX parameters to explicitly allow / disallow specific carrier transmissions

[0144] b. Sidelink CBR, where each SL carrier is assigned a specific SL LCH priority and CBR threshold for keeping or reselecting that carrier

[0145] c. Sidelink HARQ feedback information, where the UE collects statistics related to SL HARQ feedback on a given carrier to prioritize for SL transmission

[0146] d. Sidelink CQI information, where the channel quality of each carrier is used to prioritize different carriers for sidelink transmission

[0147] e. Carrier frequency criteria, where the frequency band and licensed / unlicensed band information of the carrier are used to sort and prioritize different carriers

[0148] f. Service type and its mapping to specific carrier frequencies, which can explicitly allow / disable specific carriers for data services for a given SL service

[0149] g. synchronization priority for candidate carriers, which is used to assign priority to the selected carrier,

[0150] for transmission.

[0151] Example 4 may include: a method as described in Example 1 and / or some other examples herein, wherein the overall carrier selection process may select candidate carriers in order of priority or in a random manner based on the above factors until the maximum number of carriers allowed and / or its capabilities are reached.

[0152] Example 5 may include a method as described in Example 4 and / or some other examples herein, wherein resource listening and resource (re)selection may be applied in any of the following ways:

[0153] a. The Rel.16 listening and resource selection process can be reused and applied independently on each CC or each group of CCs.

[0154] b. The Rel.16 listening and resource selection process may be applied jointly on all candidate CCs.

[0155] c. The UE may listen to each CC independently on all candidate CCs. However, the UE may select resources to be used jointly on all candidate CCs.

[0156] Example 6 may include: a method for new radio (NR) sidelink (SL) communication, comprising: for each carrier in a group of carriers, determining whether SL communication is allowed to obtain a group of SL allowed carriers from the group of carriers; sorting the group of SL allowed carriers based at least in part on contention-based random access (CBR) to provide the group of SL allowed carriers as a group of sorted SL allowed carriers; and selecting one or more of the SL allowed carriers based on the sorting of the group of sorted SL allowed carriers.

[0157] Example 7 may include: a method as described in Example 6 and / or some other examples herein, wherein each carrier in the set of carriers is associated with a separate SL hybrid automatic repeat request (HARQ) entity, wherein aggregation is performed in the MAC layer.

[0158] Example 8 may include: a method as described in Example 6 and / or some other examples herein, wherein sorting the set of SL allowed carriers is also based on one or more of a combination of quality of service (QoS) priority of SL data, SL CBR, SL HARQ feedback information, SL channel quality indicator (CQI) information, carrier frequency criteria, and synchronization priority.

[0159] Example 9 may include: a method to be performed by a user equipment (UE), one or more elements of the UE, and / or one or more electronic devices that include and / or implement the UE, wherein the method includes: identifying multiple transmission carriers for new radio (NR) side link (SL) transmission; identifying corresponding channel busy rate (CBR) values ​​associated with the corresponding multiple transmission carriers; based on a comparison of the corresponding CBR values ​​with a CBR threshold, identifying a subset of transmission carriers among the multiple transmission carriers; based on the corresponding CBR values ​​of the subset of transmission carriers, selecting a transmission carrier; and performing or facilitating the performance of NR SL transmission on the selected transmission carrier.

[0160] Example 10 may include: the subject matter as described in Example 9 and / or some other examples herein, wherein the method further comprises: before identifying the subset of transmitting carriers, removing transmitting carriers of the service type that are not mapped to the NR SL transmission from the multiple transmitting carriers.

[0161] Example 11 may include: the subject matter described in any one of Examples 9-10 and / or some other examples in this document, wherein the method further includes: sorting the transmitting carriers in the transmitting carrier subset based on the corresponding CBR values ​​of the transmitting carrier subset; and selecting the transmitting carrier based on the sorting of the transmitting carriers.

[0162] Example 12 may include the subject matter of any of Examples 9-11 and / or some other examples herein, wherein selecting the transmission carrier is further based on respective quality of service (QoS) parameters of respective transmission carriers in the subset of transmission carriers.

[0163] Example 13 may include: the subject matter as described in Example 12 and / or some other examples herein, wherein the corresponding QoS parameters are related to a QoS priority parameter, a SL hybrid automatic repeat request (HARQ) parameter, a SL channel quality indicator (CQI) parameter, a carrier frequency parameter, a service type parameter, or a synchronization priority parameter.

[0164] Example 14 may include: the subject matter described in any of Examples 9-13 and / or some other examples herein, further comprising: identifying that the CBR of the selected transmitting carrier has changed relative to the threshold; and based on identifying that the CBR of the selected transmitting carrier has changed, selecting a different transmitting carrier in the transmitting carrier subset for NR SL transmission.

[0165] Example 15 may include the subject matter of any of Examples 9-14 and / or some other examples herein, wherein the threshold is related to a logical channel (LCH) priority.

[0166] Example Z01 may include an apparatus comprising means for performing one or more elements of a method described in or related to any of Examples 1-15, or any other method or process described herein.

[0167] Example Z02 may include one or more non-transitory computer-readable media, including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of Examples 1-15, or any other method or process described herein.

[0168] Example Z03 may include an apparatus comprising logic, modules, or circuits for performing one or more elements of a method described in or related to any of Examples 1-15, or any other method or process described herein.

[0169] Example Z04 may include methods, techniques, or processes as described in or related to any of Examples 1-15, or portions or sections thereof.

[0170] Example Z05 may include a device comprising: one or more processors and one or more computer-readable media, the media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in or related to any one or portion of Examples 1-15.

[0171] Example Z06 may include signals as described in or related to any of Examples 1-15, or portions or sections thereof.

[0172] Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of Examples 1-15 or a portion or section thereof or otherwise described in the present disclosure.

[0173] Example Z08 may include a signal encoded with data as described in or related to any of Examples 1-15, or a portion or section thereof, or otherwise described in this disclosure.

[0174] Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of Examples 1-15 or a portion or section thereof or otherwise described in the present disclosure.

[0175] Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors causes the one or more processors to perform a method, technique, or process described in or related to any one or a portion thereof of Examples 1-15.

[0176] Example Z11 may include a computer program including instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process described in or related to any one of Examples 1-15 or a portion thereof.

[0177] Example Z12 may include a signal in a wireless network as shown and described herein.

[0178] Example Z13 may include a method of communicating in a wireless network as shown and described herein.

[0179] Example Z14 may include a system for providing wireless communications as shown and described herein.

[0180] Example Z15 may include an apparatus for providing wireless communications as shown and described herein.

[0181] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be obtained from the practice of the various embodiments.

[0182] abbreviation

[0183] Unless otherwise used herein, the terms, definitions and abbreviations may be consistent with those defined in 3GPP TR 21.905v16.0.0 (2019-06). For the purposes of this document, the following abbreviations may apply to the examples and embodiments discussed herein.

[0184] 3GPP Third Generation Partnership Project

[0185] 4G Fourth Generation

[0186] 5G Fifth Generation

[0187] 5GC 5G Core Network

[0188] AC Application Client

[0189] ACR Application Context Relocation

[0190] ACK

[0191] ACID Application Client Identity

[0192] ADRF Analytics Data Repository Capabilities

[0193] AF Application Function

[0194] AM Confirmation Mode

[0195] AMBR Aggregate Maximum Bit Rate

[0196] AMF Access and Mobility Management Function

[0197] AN Access Network

[0198] AnLF Analysis Logic Function

[0199] ANR Automatic Neighbor Relation

[0200] AOA Angle of Arrival

[0201] AP application protocol, antenna port, access point

[0202] API Application Programming Interface

[0203] APN Access Point Name

[0204] ARP Allocation and Retention Priority

[0205] ARQ Automatic Repeat Request

[0206] AS Access Layer

[0207] ASP Application Service Provider

[0208] ASN.1 Abstract Syntax Notation 1

[0209] AUSF authentication server function

[0210] AWGN Additive White Gaussian Noise

[0211] BAP Backhaul Adaptation Protocol

[0212] BCH Broadcast Channel

[0213] BER Bit Error Rate

[0214] BFD Beam Fault Detection

[0215] BLER Block Error Rate

[0216] BPSK Binary Phase Shift Keying

[0217] BRAS Broadband Remote Access Server

[0218] BSS Business Support System

[0219] BS Base Station

[0220] BSR Buffer Status Report

[0221] BW Bandwidth

[0222] BWP Fractional Bandwidth

[0223] C-RNTI Cell Radio Network Temporary Identity

[0224] CA Carrier Aggregation, Certification Authority

[0225] CAPEX Capital Expenditure

[0226] CBD Candidate Beam Detection

[0227] CBRA Contention-based random access

[0228] CC component carrier, country code, secret checksum

[0229] CCA Clear Channel Assessment

[0230] CCE Control Channel Element

[0231] CCCH Common Control Channel

[0232] CE Coverage Enhancement

[0233] CDM Content Distribution Network

[0234] CDMA Code Division Multiple Access

[0235] CDR Charging Data Request

[0236] CDR charging data response

[0237] CFRA Contention-free random access

[0238] CG Cell Group

[0239] CGF Billing Gateway Function

[0240] CHF billing function

[0241] CI Community Identity

[0242] CID Cell ID (eg, positioning method)

[0243] CIM Common Information Model

[0244] CIR Carrier to Interference Ratio

[0245] CK Key

[0246] CM connection management, conditional enforcement

[0247] CMAS Commercial Mobile Alert Service

[0248] CMD command

[0249] CMS Cloud Management System

[0250] CO Conditional Options

[0251] CoMP Coordinated Multipoint

[0252] CORESET Control Resource Set

[0253] COTS Commercial Off-the-Shelf

[0254] CP Control Plane, Cyclic Prefix, Attachment Point

[0255] CPD Connection Point Descriptor

[0256] CPE Customer Premises Equipment

[0257] CPICH Common Pilot Channel

[0258] CQI Channel Quality Indicator

[0259] CPU CSI processing unit, central processing unit

[0260] C / R Command / Response field, bit

[0261] CRAN Cloud Radio Access Network, Cloud RAN

[0262] CRB Common Resource Block

[0263] CRC Cyclic Redundancy Check

[0264] CRI Channel State Information Resource Indicator, CSI-RS Resource Indicator

[0265] C-RNTI Cell RNTI

[0266] CS Circuit Switched

[0267] CSCF Call Session Control Function

[0268] CSAR Cloud Service Archive

[0269] CSI Channel State Information

[0270] CSI-IM CSI interference measurement

[0271] CSI-RS CSI reference signal

[0272] CSI-RSRP CSI reference signal received power

[0273] CSI-RSRQ CSI reference signal reception quality

[0274] CSI-SINR CSI signal to interference and noise ratio

[0275] CSMA Carrier Sense Multiple Access

[0276] CSMA / CA CSMA with Collision Avoidance

[0277] CSS Common Search Space, Cell Specific Search Space

[0278] CTF Billing Trigger Function

[0279] CTS Clear to Send

[0280] CW codeword

[0281] CWS Contention Window Size

[0282] D2D Device to Device

[0283] DC dual connection, direct current

[0284] DCI Downlink Control Information

[0285] DF deployment style

[0286] DL Downlink

[0287] DMTF Distributed Management Task Force

[0288] DPDK Data Plane Development Kit

[0289] DM-RS DMRS demodulation reference signal

[0290] DN Data Network

[0291] DNN data network name

[0292] DNAI Data Network Access Identifier

[0293] DRB Data Radio Bearer

[0294] DRS Discovery Reference Signal

[0295] DRX Discontinuous Reception

[0296] DSL Domain Specific Language, Digital Subscriber Line

[0297] DSLAM DSL Access Multiplexer

[0298] DwPTS Downlink Pilot Time Slot

[0299] E-LAN ​​Ethernet Local Area Network

[0300] E2E End to End

[0301] EAS Edge Application Server

[0302] ECCA Extended Clear Channel Assessment, Extended CCA

[0303] ECCE Enhanced Control Channel Element, Enhanced CCE

[0304] ED Energy Detection

[0305] EDGE Enhanced Data Rates for GSM Evolution (GSM Evolution)

[0306] EAS Edge Application Server

[0307] EASID Edge Application Server Identifier

[0308] ECS Edge Configuration Server

[0309] ECSP Edge Computing Service Provider

[0310] EDN Edge Data Network

[0311] EEC Edge Enabler Client

[0312] EECID Edge Enabler Client Identifier

[0313] EES Edge Enabler Server

[0314] EESID Edge Enabler Server ID

[0315] EHE Edge Hosting Environment

[0316] EGMF Open Control Management Function

[0317] EGPRS Enhanced GPRS

[0318] EIR Equipment Identity Register

[0319] eLAA Enhanced Authorization Assisted Access, Enhanced LAA

[0320] EM Component Manager

[0321] eMBB Enhanced Mobile Broadband

[0322] EMS Component Management System

[0323] eNB Evolved NodeB, E-UTRAN Node B

[0324] EN-DC E-UTRA-NR Dual Connectivity

[0325] EPC Evolved Packet Core

[0326] EPDCCH Enhanced PDCCH, Enhanced Physical Downlink Control Channel

[0327] EPRE Energy Element per Resource

[0328] EPS Evolved Packet System

[0329] EREG Enhanced REG, Enhanced Resource Element Group

[0330] ETSI European Telecommunications Standards Institute

[0331] ETWS Earthquake and Tsunami Early Warning System

[0332] eUICC embedded UICC, embedded universal integrated circuit card

[0333] E-UTRA Evolved UTRA

[0334] E-UTRAN Evolved UTRAN

[0335] EV2X Enhanced V2X

[0336] F1AP F1 Application Protocol

[0337] F1-C F1 control plane interface

[0338] F1-U F1 User Plane Interface

[0339] FACCH Fast Associated Control Channel

[0340] FACCH / F Fast Associated Control Channel / Full Rate

[0341] FACCH / H Fast Associated Control Channel / Half Rate

[0342] FACH Forward Access Channel

[0343] FAUSCH Fast Uplink Signalling Channel

[0344] FB Function Block

[0345] FBI Feedback

[0346] FCC Federal Communications Commission

[0347] FCCH Frequency Correction Channel

[0348] FDD Frequency Division Duplex

[0349] FDM Frequency Division Multiplexing

[0350] FDMA Frequency Division Multiple Access

[0351] FE Front End

[0352] FEC Forward Error Correction

[0353] FFS Further Research

[0354] FFT Fast Fourier Transform

[0355] feLAA further enhances authorized assisted access and LAA

[0356] FN Frame Number

[0357] FPGA Field Programmable Gate Array

[0358] FR Frequency Range

[0359] FQDN Fully Qualified Domain Name

[0360] G-RNTI GERAN Radio Network Temporary Identity

[0361] GERAN GSM EDGE RAN, GSM EDGE radio access network

[0362] GGSN Gateway GPRS Support Node

[0363] GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (English: Global Navigation Satellite System)

[0364] gNB Next Generation NodeB

[0365] gNB-CU gNB centralized unit, next generation NodeB centralized unit

[0366] gNB-DU gNB distributed unit, next generation NodeB distributed unit

[0367] GNSS Global Navigation Satellite System

[0368] GPRS General Packet Radio Service

[0369] GPSI General Public Subscription Identifier

[0370] GSM Global System for Mobile Communications, Groupe Special Mobile

[0371] GTP GPRS Tunneling Protocol

[0372] GTP-U GPRS User Plane Tunneling Protocol

[0373] GTS (related to WUS) sleep entry signal

[0374] GUMMEI Globally Unique MME Identifier

[0375] GUTI Globally Unique Temporary UE Identity

[0376] HARQ Hybrid ARQ, Hybrid Automatic Repeat Request

[0377] HANDO switch

[0378] HFN Superframe Number

[0379] HHO Hard Handover

[0380] HLR Home Location Register

[0381] HN Home Network

[0382] HO Switchover

[0383] HPLMN Home Public Land Mobile Network

[0384] HSDPA High Speed ​​Downlink Packet Access

[0385] HSN Hopping Sequence Number

[0386] HSPA High Speed ​​Packet Access

[0387] HSS Home Subscriber Server

[0388] HSUPA High Speed ​​Uplink Packet Access

[0389] HTTP Hypertext Transfer Protocol

[0390] HTTPS Hypertext Transfer Protocol Secure (https is http / 1.1 over SSL, i.e., port 443)

[0391] I-Block Information Block

[0392] ICCID Integrated Circuit Card Identifier

[0393] IAB Integration Access and Postbacks

[0394] ICIC Inter-cell Interference Coordination

[0395] ID Identity, identifier

[0396] IDFT Inverse Discrete Fourier Transform

[0397] IE Cell

[0398] IBE In-Band Emission

[0399] IEEE Institute of Electrical and Electronics Engineers

[0400] IEI Information Element Identifier

[0401] IEIDL Information element identifier data length

[0402] IETF Internet Engineering Task Force

[0403] IF Infrastructure

[0404] IIOT Industrial Internet of Things

[0405] IM Interference Measurement, Intermodulation, IP Multimedia

[0406] IMC IMS credentials

[0407] IMEI International Mobile Equipment Identity

[0408] IMGI International Mobile Group Identity

[0409] IMPI IP Multimedia Private Identity

[0410] IMPU IP Multimedia Public Identity

[0411] IMS IP Multimedia Subsystem

[0412] IMSI International Mobile Subscriber Identity

[0413] IoT

[0414] IP Internet Protocol

[0415] Ipsec IP security, Internet Protocol security

[0416] IP-CAN IP-Connect Access Network

[0417] IP-M IP Multicast

[0418] IPv4 Internet Protocol version 4

[0419] IPv6 Internet Protocol version 6

[0420] IR Infrared

[0421] IS Synchronization

[0422] IRP Integration Reference Point

[0423] ISDN Integrated Services Digital Network

[0424] ISIM IM Service Identity Module

[0425] ISO International Organization for Standardization

[0426] ISP Internet Service Provider

[0427] IWF interworking function

[0428] I-WLAN Intercommunication WLAN

[0429] Convolutional code constraint length, USIM individual key

[0430] kB kilobyte (1000 bytes)

[0431] kbps kilobits per second

[0432] Kc key

[0433] Ki Individual subscriber authentication key

[0434] KPI Key Performance Indicator

[0435] KQI Key Quality Indicator

[0436] KSI Key Set Identifier

[0437] ksps kilosymbols per second

[0438] KVM Kernel Virtual Machine

[0439] L1 Layer 1 (physical layer)

[0440] L1-RSRP Layer 1 reference signal received power

[0441] L2 Layer 2 (Data Link Layer)

[0442] L3 Layer 3 (Network Layer)

[0443] LAA Authorized Assisted Access

[0444] LAN Local Area Network

[0445] LADN Local Area Data Network

[0446] LBT Listen before you speak

[0447] LCM Lifecycle Management

[0448] LCR Low Chip Rate

[0449] LCS Location Services

[0450] LCID Logical Channel ID

[0451] LI layer indicator

[0452] LLC Logical Link Control, Lower Layer Compatibility

[0453] LMF Location Management Function

[0454] LOS Line of Sight

[0455] LPLMN Local PLMN

[0456] LPP LTE Positioning Protocol

[0457] LSB Least Significant Bit

[0458] LTE Long Term Evolution

[0459] LWA LTE-WLAN Aggregation

[0460] LWIP LTE / WLAN wireless level integration with IPsec tunneling

[0461] LTE Long Term Evolution

[0462] M2M Machine to Machine

[0463] MAC Medium Access Control (Protocol Layer Context)

[0464] MAC Message Authentication Code (Security / Cryptography Context)

[0465] MAC-A MAC for authentication and key agreement (TSG T WG3 context)

[0466] MAC-I MAC for data integrity of signalling messages (TSG T WG3 context)

[0467] MANO Management and Orchestration

[0468] MBMS Multimedia Broadcast and Multicast Service

[0469] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network

[0470] MCC Mobile Country Code

[0471] MCG Master Cell Group

[0472] MCOT Maximum Channel Occupancy Time

[0473] MCS Modulation Coding Scheme

[0474] MDAF Management Data Analysis Function

[0475] MDAS Management Data Analysis Service

[0476] MDT Minimized Drive Test

[0477] ME Mobile Devices

[0478] MeNB Master eNB

[0479] MER False Message Rate

[0480] MGL Measurement Gap Length

[0481] MGRP measurement gap repetition period

[0482] MIB Master Information Block, Management Information Base

[0483] MIMO Multiple Input Multiple Output

[0484] MLC Mobile Location Center

[0485] MM Mobility Management

[0486] MME Mobility Management Entity

[0487] MN Master Node

[0488] MNO Mobile Network Operator

[0489] MO Measurement object, mobile calling

[0490] MPBCH MTC Physical Broadcast Channel

[0491] MPDCCH MTC Physical Downlink Control Channel

[0492] MPDSCH MTC Physical Downlink Shared Channel

[0493] MPRACH MTC Physical Random Access Channel

[0494] MPUSCH MTC Physical Uplink Shared Channel

[0495] MPLS Multiprotocol Label Switching

[0496] MS Mobile Station

[0497] MSB Most Significant Bit

[0498] MSC Mobile Switching Center

[0499] MSI minimum system information, MCH scheduling information

[0500] MSID Mobile Station Identifier

[0501] MSIN Mobile Station Identification Number

[0502] MSISDN Mobile Subscriber ISDN Number

[0503] MT mobile called, mobile terminal

[0504] MTC Machine Type Communication

[0505] MTLF model training logic function

[0506] mMTC Massive MTC, Massive Machine Type Communication

[0507] MU-MIMO Multi-User MIMO

[0508] MWUS MTC wake-up signal, MTC WUS

[0509] NACK Negative Acknowledgement

[0510] NAI Network Access Identifier

[0511] NAS Non-Access Stratum, Non-Access Layer

[0512] NCT Network Connection Topology

[0513] NC-JT Non-coherent joint transmission

[0514] NEC Network Capability Openness

[0515] NE-DC NR-E-UTRA dual connectivity

[0516] NEF Network Exposure Function

[0517] NF Network Function

[0518] NFP Network Forwarding Path

[0519] NFPD Network Forwarding Path Descriptor

[0520] NFV Network Function Virtualization

[0521] NFVI NFV Infrastructure

[0522] NFVO NFV Orchestrator

[0523] NG Next generation, next generation

[0524] NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity

[0525] NM Network Manager

[0526] NMS Network Management System

[0527] N-PoP Network Point of Presence

[0528] NMIB, N-MIB Narrowband MIB

[0529] NPBCH Narrowband Physical Broadcast Channel

[0530] NPDCCH Narrowband Physical Downlink Control Channel

[0531] NPDSCH Narrowband Physical Downlink Shared Channel

[0532] NPRACH Narrowband Physical Random Access Channel

[0533] NPUSCH Narrowband Physical Uplink Shared Channel

[0534] NPSS Narrowband Primary Synchronization Signal

[0535] NSSS Narrowband Secondary Synchronization Signal

[0536] NR New Air Interface, Neighbor Relationship

[0537] NRF NF Repository Functionality

[0538] NRS Narrowband Reference Signal

[0539] NS Network Services

[0540] NSA Non-standalone operation mode

[0541] NSD Network Service Descriptor

[0542] NSR Network Service Record

[0543] NSSAI Network Slice Selection Assistance Information

[0544] S-NNSAI Single NSSAI

[0545] NSSF network slice selection function

[0546] NW Network

[0547] NWDAF network data analysis function

[0548] NWUS Narrowband wake-up signal, narrowband WUS

[0549] NZP Non Zero Power

[0550] O&M

[0551] ODU2 Optical Channel Data Unit - Type 2

[0552] OFDM Orthogonal Frequency Division Multiplexing

[0553] OFDMA Orthogonal Frequency Division Multiple Access

[0554] OOB Out of Band

[0555] OOS Out of Sync

[0556] OPEX Operating Expenses

[0557] OSI Other System Information

[0558] OSS Operation Support System

[0559] OTA (Over the Air)

[0560] PAPR Peak to Average Power Ratio

[0561] PAR Peak to Average Ratio

[0562] PBCH Physical Broadcast Channel

[0563] PC Power Control, Personal Computer

[0564] PCC Primary Component Carrier, Primary CC

[0565] P-CSCF Proxy CSCF

[0566] PCell Primary Cell

[0567] PCI Physical Cell ID, Physical Cell Identity

[0568] PCEF Policy and Charging Enforcement Function

[0569] PCF Policy Control Function

[0570] PCRF Policy Control and Charging Rules Function

[0571] PDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol Layer

[0572] PDCCH Physical Downlink Control Channel

[0573] PDCP Packet Data Convergence Protocol

[0574] PDN Packet Data Network, Public Data Network

[0575] PDSCH Physical Downlink Shared Channel

[0576] PDU Protocol Data Unit

[0577] PEI Persistent Equipment Identifier

[0578] PFD Packet Flow Description

[0579] P-GW PDN Gateway

[0580] PHICH Physical Hybrid ARQ Indicator Channel

[0581] PHY Physical Layer

[0582] PLMN Public Land Mobile Network

[0583] PIN Personal Identification Number

[0584] PM performance measurement

[0585] PMI Precoding matrix indicator

[0586] PNF Physical Network Function

[0587] PNFD Physical Network Functional Descriptor

[0588] PNFR Physical Network Function Record

[0589] POC PTT over Cellular

[0590] PP, PTP point to point

[0591] PPP Point-to-Point Protocol

[0592] PRACH Physical RACH

[0593] PRB Physical Resource Block

[0594] PRG Physical Resource Group

[0595] ProSe Proximity Services, Proximity-Based Services

[0596] PRS Positioning Reference Signal

[0597] PRR Packet Receive Radio

[0598] PS Packet Service

[0599] PSBCH Physical Sidelink Broadcast Channel

[0600] PSDCH Physical Sidelink Downlink Channel

[0601] PSCCH Physical Sidelink Control Channel

[0602] PSSCH Physical Sidelink Shared Channel

[0603] PSFCH Physical Sidelink Feedback Channel

[0604] PSCell Primary SCell

[0605] PSS Primary Synchronization Signal

[0606] PSTN Public Switched Telephone Network

[0607] PT-RS Phase Tracking Reference Signal

[0608] PTT Push to Talk

[0609] PUCCH Physical Uplink Control Channel

[0610] PUSCH Physical Uplink Shared Channel

[0611] QAM Quadrature Amplitude Modulation

[0612] QCI QoS Class Identifier

[0613] QCL Quasi-Co-location

[0614] QFI QoS flow ID, QoS flow identifier

[0615] QoS Quality of Service

[0616] QPSK Quadrature (Quaternary) Phase Shift Keying

[0617] QZSS Quasi-Zenith Satellite System

[0618] RA-RNTI Random Access RNTI

[0619] RAB Radio Access Bearer, Random Access Burst

[0620] RACH Random Access Channel

[0621] RADIUS Remote Authentication Dial-In User Service

[0622] RAN Radio Access Network

[0623] RAND Random number (for authentication)

[0624] RAR Random Access Response

[0625] RAT Radio Access Technology

[0626] RAU Routing Area Update

[0627] RB Resource Block, Radio Bearer

[0628] RBG Resource Block Group

[0629] REG Resource Element Group

[0630] Rel version

[0631] REQ Request

[0632] RF

[0633] RI Rank Indicator

[0634] RIV Resource Indicator Value

[0635] RL Wireless Link

[0636] RLC Radio Link Control, Radio Link Control Layer

[0637] RLC AM RLC Acknowledgement Mode

[0638] RLC UM RLC Unacknowledged Mode

[0639] RLF Radio Link Failure

[0640] RLM Radio Link Monitoring

[0641] RLM-RS Reference signal for RLM

[0642] RM Registration Management

[0643] RMC Reference Measurement Channel

[0644] RMSI Remaining MSI, Remaining Minimum System Information

[0645] RN Relay Node

[0646] RNC Radio Network Controller

[0647] RNL Radio Network Layer

[0648] RNTI Radio Network Temporary Identifier

[0649] ROHC Robust Header Compression

[0650] RRC Radio Resource Control, Radio Resource Control Layer

[0651] RRM Radio Resource Management

[0652] RS reference signal

[0653] RSRP Reference Signal Received Power

[0654] RSRQ Reference Signal Received Quality

[0655] RSSI Received Signal Strength Indicator

[0656] RSU Roadside Unit

[0657] RSTD Reference Signal Time Difference

[0658] RTP Real Time Protocol

[0659] RTS Ready to send

[0660] RTT Round Trip Time

[0661] Rx receive, receive, receiver

[0662] S1AP S1 Application Protocol

[0663] S1-MME is used for S1 control plane

[0664] S1-U S1 for user plane

[0665] S-CSCF Serving CSCF

[0666] S-GW Service Gateway

[0667] S-RNTI SRNC Radio Network Temporary Identity

[0668] S-TMSI SAE temporary mobile station identifier

[0669] SA Standalone Operation Mode

[0670] SAE system architecture evolution

[0671] SAP Service Access Point

[0672] SAPD Service Access Point Descriptor

[0673] SAPI Service Access Point Identifier

[0674] SCC Secondary Component Carrier, Secondary CC

[0675] SCell Secondary Cell

[0676] SCEF service capability exposure function

[0677] SC-FDMA Single Carrier Frequency Division Multiple Access

[0678] SCG Secondary Cell Group

[0679] SCM Security Context Management

[0680] SCS subcarrier spacing

[0681] SCTP Stream Control Transmission Protocol

[0682] SDAP Service Data Adaptation Protocol, Service Data Adaptation Protocol Layer

[0683] SDL Supplemental Downlink

[0684] SDNF Structured Data Storage Network Function

[0685] SDP Session Description Protocol

[0686] SDSF structured data storage function

[0687] SDT Small Data Transfer

[0688] SDU Service Data Unit

[0689] SEAF Security Anchoring Function

[0690] SeNB Secondary eNB

[0691] SEPP Security Edge Protection Proxy

[0692] SFI Slot Format Indicator

[0693] SFTD Space Frequency Time Diversity, SFN and Frame Timing Difference

[0694] SFN System Frame Number

[0695] SgNB

[0696] SGSN Serving GPRS Support Node

[0697] S-GW Service Gateway

[0698] SI System Information

[0699] SI-RNTI System Information RNTI

[0700] SIB System Information Block

[0701] SIM Subscriber Identity Module

[0702] SIP Session Initiation Protocol

[0703] SiP System in Package

[0704] SL Side Link

[0705] SLA Service Level Agreement

[0706] SM Session Management

[0707] SMF session management functions

[0708] SMS Short Message Service

[0709] SMSF SMS Function

[0710] SMTC SSB-based measurement timing configuration

[0711] SN Secondary Node, Serial Number

[0712] SoC System on Chip

[0713] SON Self-Organizing Network

[0714] SpCell Special Cell

[0715] SP-CSI-RNTI Semi-persistent CSI RNTI

[0716] SPS Semi-Persistent Scheduling

[0717] SQN Serial Number

[0718] SR Scheduling Request

[0719] SRB Signalling Radio Bearer

[0720] SRS Sounding Reference Signal

[0721] SS Sync Signal

[0722] SSB Synchronous Signal Block

[0723] SSID Service Set Identifier

[0724] SS / PBCH block

[0725] SSBRI SS / PBCH block resource indicator, synchronization signal block resource indicator

[0726] SSC Session and Service Continuity

[0727] SS-RSRP Reference signal received power based on synchronization signal

[0728] SS-RSRQ Reference signal reception quality based on synchronization signal

[0729] SS-SINR Signal-to-interference-noise ratio based on synchronization signal

[0730] SSS Secondary synchronization signal

[0731] SSSG Search Space Group

[0732] SSSIF Search Space Set Indicator

[0733] SST Slice / Service Type

[0734] SU-MIMO Single User MIMO

[0735] SUL Supplementary Uplink

[0736] TA Timing Advance, Tracking Area

[0737] TAC Tracking Area Code

[0738] TAG Timing Advance Group

[0739] TAI Tracking Area Identity

[0740] TAU Tracking Area Updates

[0741] TB Transfer Block

[0742] TBS Transport Block Size

[0743] TBD

[0744] TCI Transmission Configuration Indicator

[0745] TCP transport communication protocol

[0746] TDD Time Division Duplex

[0747] TDM Time Division Multiplexing

[0748] TDMA Time Division Multiple Access

[0749] TE Terminal Equipment

[0750] TEID Tunnel Endpoint Identifier

[0751] TFT Business Flow Template

[0752] TMSI Temporary Mobile Subscriber Identity

[0753] TNL Transport Network Layer

[0754] TPC Transmit Power Control

[0755] TPMI Transmit Precoding Matrix Indicator

[0756] TR Technical Report

[0757] TRP, TRxP transmit and receive points

[0758] TRS Tracking Reference Signal

[0759] TRx Transceiver

[0760] TS Technical Specifications, Technical Standards

[0761] TTI Transmission Time Interval

[0762] Tx transmission, sending, transmitter

[0763] U-RNTI UTRAN Radio Network Temporary Identity

[0764] UART Universal Asynchronous Receiver and Transmitter

[0765] UCI Uplink Control Information

[0766] UE User Equipment

[0767] UDM Unified Data Management

[0768] UDP User Datagram Protocol

[0769] UDSF Unstructured Data Storage Network Function

[0770] UICC Universal Integrated Circuit Card

[0771] UL Uplink

[0772] UM Unconfirmed Mode

[0773] UML Unified Modeling Language

[0774] UMTS Universal Mobile Telecommunications System

[0775] UP User Plane

[0776] UPF User Plane Function

[0777] URI Uniform Resource Identifier

[0778] URL Uniform Resource Locator

[0779] URLLC Ultra-Reliable and Low Latency

[0780] USB Universal Serial Bus

[0781] USIM Universal Subscriber Identity Module

[0782] USS UE-specific search space

[0783] UTRA UMTS Terrestrial Radio Access

[0784] UTRAN Universal Terrestrial Radio Access Network

[0785] UwPTS Uplink Pilot Time Slot

[0786] V2I Vehicle to Infrastructure

[0787] V2P Vehicle to Pedestrian

[0788] V2V Vehicle to Vehicle

[0789] V2X Vehicle to Everything

[0790] VIM Virtualization Infrastructure Manager

[0791] VL Virtual Link

[0792] VLAN Virtual LAN, Virtual Local Area Network

[0793] VM Virtual Machine

[0794] VNF Virtualized Network Function

[0795] VNFFG VNF forwarding graph

[0796] VNFFGD VNF Forwarding Graph Descriptor

[0797] VNFM VNF Manager

[0798] VoIP Voice over IP, Voice over Internet Protocol

[0799] VPLMN Visited Public Land Mobile Network

[0800] VPN Virtual Private Network

[0801] VRB Virtual Resource Block

[0802] WiMAX Worldwide Interoperability for Microwave Access

[0803] WLAN Wireless Local Area Network

[0804] WMAN Wireless Metropolitan Area Network

[0805] WPAN Wireless Personal Area Network

[0806] X2-C X2-Control Plane

[0807] X2-U X2-User Plane

[0808] XML Extensible Markup Language

[0809] XRES Expected User Response

[0810] XOR

[0811] ZC Zadoff-Chu

[0812] ZP Zero Power

[0813] the term

[0814] For the purposes of this document, the following terms and definitions apply to the examples and embodiments discussed herein.

[0815] The term "application" may refer to a complete and deployable package or environment for implementing a certain function in an operating environment. The term "AI / ML application" may refer to an application that contains some AI / ML models and application-level descriptions.

[0816] The term "circuit" as used herein refers to, is part of, or includes the following hardware components that are configured to provide the described functions: for example, electronic circuits, logic circuits, processors (shared, dedicated, or group) and / or memories (shared, dedicated, or group), application specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high capacity PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuit" may also refer to a combination of one or more hardware elements and program code (or a combination of circuits and program code used in an electrical or electronic system), the hardware elements being used to perform the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0817] The term "processor circuit" used herein refers to a circuit that can sequentially and automatically perform a series of arithmetic or logical operations, or record, store and / or transmit digital data, is a part of it, or includes them. The processing circuit may include one or more processing cores for executing instructions and one or more memory structures for storing program and data information. The term "processor circuit" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer executable instructions (e.g., program code, software module and / or functional process). The processing circuit may include more hardware accelerators, which may be microprocessors, programmable processing devices, etc. One or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms "application circuit" and / or "baseband circuit" may be considered synonymous with "processor circuit" and may be referred to as "processor circuit".

[0818] As used herein, the term "interface circuit" refers to, is a part of, or includes circuitry that enables information to be exchanged between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0819] The term "user equipment" or "UE" as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous with, and may be referred to as, a client, a mobile station, a mobile device, a mobile terminal, a user terminal, a mobile unit, a mobile station, a mobile user, a subscriber, a user, a remote station, an access agent, a user agent, a receiver, a radio device, a reconfigurable radio device, a reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0820] The term "network element" as used herein refers to a physical or virtualized device and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered a synonym for and / or referred to as: networked computer, networking hardware, network device, network node, router, switch, hub, bridge, radio network controller, RAN equipment, RAN node, gateway, server, virtualized VNF, NFVI, etc.

[0821] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Furthermore, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the terms "computer system" and / or "system" may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled to one another and configured to share computing and / or networking resources.

[0822] As used herein, the terms "appliance", "computer appliance", etc. refer to a computer device or computer system with program code (e.g., software or firmware) specifically designed to provide specific computing resources. A "virtual appliance" is a virtual machine image to be implemented by a device equipped with a hypervisor that virtualizes or emulates a computer appliance or is otherwise dedicated to providing specific computing resources.

[0823] The term "resource" as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and / or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time, a processor / CPU usage, a processor and accelerator load, a hardware time or usage, power, input / output operations, a port or network socket, a channel / link allocation, throughput, memory usage, storage, a network, a database and an application, a workload unit, etc. "Hardware resources" may refer to computing, storage and / or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage and / or network resources provided by a virtualized infrastructure to an application, device, system, etc. The term "network resources" or "communication resources" may refer to resources accessible to a computer device / system via a communication network. The term "system resources" may refer to any kind of shared entity that provides a service, and may include computing and / or network resources. System resources may be viewed as a set of coherent functions, network data objects, or services that may be accessed through a server, wherein these system resources reside on a single host or multiple hosts and may be clearly identifiable.

[0824] The term "channel" as used herein refers to any transmission medium, whether tangible or intangible, for transmitting data or data streams. The term "channel" may be synonymous with and / or equivalent to the following terms: "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" and / or any other similar term representing a path or medium through which data is transmitted. In addition, the term "link" as used herein refers to a connection between two devices over a RAT for sending and receiving information.

[0825] As used herein, the terms "instantiate," "instantiation," and the like refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0826] The terms "coupled", "communicatively coupled" and their derivatives are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between elements that are considered to be coupled to each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements may be in contact with each other by means of communication, including by wired or other interconnection, by wireless communication channels or links, etc.

[0827] The term "cell" refers to a structural element containing one or more fields. The term "field" refers to the individual contents of a cell, or a data element containing the contents.

[0828] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[0829] The term "SSB" refers to a SS / PBCH block.

[0830] The term "primary cell" refers to an MCG cell operating on a primary frequency, in which the UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

[0831] The term "primary SCG cell", for DC operation, refers to the SCG cell in which the UE performs random access when performing the synchronization reconfiguration procedure.

[0832] The term "secondary cell", for a UE configured with CA, refers to a cell that provides additional radio resources over a special cell.

[0833] The term "secondary cell group", for a UE configured with DC, refers to a subset of serving cells including a PSCell and zero or more secondary cells.

[0834] The term "serving cell", for a UE in RRC_CONNECTED without CA / DC configuration, refers to a primary cell, of which there is only one serving cell.

[0835] The term "serving cell" or "serving cells", for a UE configured with CA / DC in RRC_CONNECTED, refers to a group of cells including a special cell and all secondary cells.

[0836] The term "special cell" refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term "special cell" refers to the Pcell.

[0837] The term "machine learning" or "ML" refers to the use of computer systems that implement algorithms and / or statistical models to perform specific tasks without explicit instructions, relying instead on patterns and reasoning. ML algorithms build or estimate mathematical models (called "ML models", etc.) based on sample data (called "training data", "model training information", etc.) to make predictions or decisions without being explicitly programmed to perform such tasks. In general, an ML algorithm is a computer program that learns from experience and some performance metrics about some tasks, and an ML model can be any object or data structure created after training an ML algorithm with one or more training data sets. After training, the ML model can be used to make predictions on new data sets. Although the term "ML algorithm" refers to a different concept from the term "ML model", for the purposes of this disclosure, these terms discussed herein can be used interchangeably.

[0838] The terms "machine learning model", "ML model", etc. may also refer to ML methods and concepts used by ML-assisted solutions. "ML-assisted solutions" are solutions that use ML algorithms to solve specific use cases during operation. ML models include supervised learning (e.g., linear regression, k-nearest neighbors (KNN), decision tree algorithms, support machine vectors, Bayesian algorithms, ensemble algorithms, etc.), unsupervised learning (e.g., K-means clustering, principal component analysis (PCA)), reinforcement learning (e.g., Q-learning, multi-armed bandit learning, deep RL, etc.), neural networks, etc. Depending on the implementation, a specific ML model may have many sub-models as components, and the ML model may train all sub-models together. During inference, separately trained ML models may also be linked together in an ML pipeline. "ML pipeline" is a set of functional, functional, or functional entities specific to ML-assisted solutions; an ML pipeline may include one or more data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and actors. "Actors" are entities that host ML-assisted solutions using the output of ML model inference. The term "ML training host" refers to an entity that hosts model training, such as a network function. The term "ML inference host" refers to the entity, such as a network function, that hosts the model during inference mode (which includes model execution and any online learning (if applicable)). The ML host informs the participants of the output of the ML algorithm, and the participants make decisions about actions ("actions" are performed by the participants based on the output of the ML-assisted solution). The term "model inference information" refers to the information used as input to the ML model for determining inferences; the data used to train the ML model and the data used to determine inferences may overlap, however, "training data" and "inference data" refer to different concepts.

Claims

1. A user equipment (UE), comprising: A memory for storing information related to a plurality of transmit carriers for New Radio (NR) Side Link (SL) transmission; and One or more processors are communicatively coupled to the memory, wherein the one or more processors are configured to: identifying corresponding channel busy rate (CBR) values ​​associated with the corresponding plurality of transmit carriers; identifying a subset of transmit carriers from the plurality of transmit carriers based on a comparison of the corresponding CBR values ​​with a CBR threshold; selecting a transmission carrier based on the corresponding CBR values ​​of the transmission carrier subset; and Facilitates NR SL transmission on selected transmit carriers.

2. The UE according to claim 1, wherein: The one or more processors are further configured to: Before identifying the transmission carrier subset, transmission carriers of the service type not mapped to the NR SL transmission are removed from the plurality of transmission carriers.

3. The UE according to claim 1, wherein: The one or more processors are further configured to: sorting the transmission carriers in the transmission carrier subset based on the corresponding CBR values ​​of the transmission carrier subset; and Based on the ranking of the transmit carriers, a transmit carrier is selected.

4. The UE according to any one of claims 1 to 3, wherein: The one or more processors are further configured to: The transmission carrier is also selected based on respective quality of service (QoS) parameters of respective transmission carriers in the subset of transmission carriers.

5. The UE according to claim 4, wherein: The corresponding QoS parameter is related to a QoS priority parameter, a SL hybrid automatic repeat request (HARQ) parameter, a SL channel quality indicator (CQI) parameter, a carrier frequency parameter, a service type parameter or a synchronization priority parameter.

6. The UE according to any one of claims 1 to 3, wherein: The one or more processors are further configured to: identifying that the CBR of the selected transmit carrier has changed relative to the threshold; and Based on identifying that the CBR of the selected transmission carrier has changed, a different transmission carrier in the subset of transmission carriers is selected for NR SL transmission.

7. The UE according to any one of claims 1 to 3, wherein: The threshold is related to the logical channel (LCH) priority.

8. One or more non-transitory computer readable media (NTCRMs) comprising instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: Identifying a plurality of transmit carriers for New Radio (NR) Side Link (SL) transmissions; identifying corresponding channel busy rate (CBR) values ​​associated with the corresponding plurality of transmit carriers; identifying a subset of transmit carriers from among the plurality of transmit carriers based on a comparison of the corresponding CBR values ​​with a CBR threshold; selecting a transmission carrier based on the corresponding CBR values ​​of the transmission carrier subset; and Facilitates NR SL transmission on selected transmit carriers.

9. One or more NTCRMs as claimed in claim 8, wherein: The instructions also provide for: Before identifying the transmission carrier subset, transmission carriers of the service type not mapped to the NR SL transmission are removed from the plurality of transmission carriers.

10. The one or more NTCRMs of claim 8, wherein: The instructions also provide for: sorting the transmission carriers of the transmission carrier subset based on the corresponding CBR values ​​of the transmission carrier subset; and Based on the ranking of the transmit carriers, a transmit carrier is selected.

11. One or more NTCRMs according to any one of claims 8 to 10, wherein: The instructions also provide for: The transmission carrier is also selected based on respective quality of service (QoS) parameters of respective transmission carriers in the subset of transmission carriers.

12. The one or more NTCRMs of claim 4, wherein: The corresponding QoS parameter is related to a QoS priority parameter, a SL hybrid automatic repeat request (HARQ) parameter, a SL channel quality indicator (CQI) parameter, a carrier frequency parameter, a service type parameter or a synchronization priority parameter.

13. One or more NTCRMs according to any one of claims 8 to 10, wherein: The instructions also provide for: identifying that the CBR of the selected transmit carrier has changed relative to the threshold; and Based on identifying that the CBR of the selected transmission carrier has changed, a different transmission carrier in the subset of transmission carriers is selected for NR SL transmission.

14. One or more NTCRMs according to any one of claims 8 to 10, wherein: The threshold is related to the logical channel (LCH) priority.

15. A user equipment (UE), comprising: A memory for storing information related to one or more carriers to be used for New Radio (NR) Side Link (SL) communications; and One or more processors are communicatively coupled to the memory, wherein the one or more processors are configured to: For each carrier in a set of carriers, determining whether SL communication is allowed to obtain a set of SL allowed carriers from the set of carriers; sorting the set of SL allowed carriers based at least in part on one or more channel busy rate (CBR) values ​​to provide the set of SL allowed carriers as a set of sorted SL allowed carriers; and Based on the ranking of the ranked set of SL allowed carriers, one or more of the set of SL allowed carriers are selected.

16. The UE according to claim 15, wherein: Respective carriers in the set of carriers are associated with separate SL Hybrid Automatic Repeat Request (HARQ) entities.

17. The UE according to claim 16, wherein: Aggregation associated with the individual SL HARQ entities is performed by a Medium Access Control (MAC) layer entity.

18. The UE according to claim 15, wherein: The one or more CBR values ​​include a plurality of CBR values ​​respectively associated with corresponding SL allowed carriers in the set of SL allowed carriers.

19. The UE according to any one of claims 15 to 18, wherein: The one or more processors are further configured to: The set of SL allowed carriers is ranked based at least in part on the one or more CBR values ​​and one or more quality of service (QoS) parameters.

20. The UE according to claim 19, wherein: The one or more QoS parameters include QoS priority of SL data, SL CBR, SL HARQ feedback information, SL channel quality indicator (CQI) information, carrier frequency criteria, or synchronization priority.

Images