Service-to-frequency mapping for sidelink carrier aggregation

Abstract

The invention relates to service-to-frequency mapping for sidelink carrier aggregation. According to aspects of the present disclosure, a user equipment (UE) may receive a configuration for mapping a PC5 quality of service (QoS) flow to a frequency. The UE may also receive a sidelink logical channel configuration message indicating that sidelink data associated with the logical channel may be mapped to one or more sidelink carriers on the list of allowed sidelink carriers. Thus, the UE may transmit the sidelink data associated with the logical channel via at least one sidelink carrier based, at least in part, on mapping the logical channel to the at least one sidelink carrier on the list of allowed sidelink carriers according to the configuration for mapping and the sidelink logical channel configuration message.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 531,350, filed on August 8, 2023, which is incorporated herein by reference in its entirety. Background Art

[0003] Wireless communication networks provide integrated communication platforms and telecommunication services to wireless user devices. Example telecommunication services include telephone, data (e.g., voice, audio and / or video data), messaging and / or other services. Wireless communication networks have wireless access nodes that exchange wireless signals with wireless user devices using wireless network protocols (such as protocols described in various telecommunication standards promulgated by the Third Generation Partnership Project (3GPP)). Example wireless communication networks include time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal frequency division multiple access (OFDMA) networks, long term evolution (LTE) and fifth generation new radio (5G NR). Wireless communication networks use technologies such as OFDM, multiple input multiple output (MIMO), advanced channel coding, massive MIMO, beamforming and / or other features to facilitate mobile broadband services. Summary of the invention

[0004] Various aspects of the specific implementation relate to a method performed by a user equipment (UE), the method comprising: determining that a PC5 quality of service (QoS) flow is added or modified; providing a new or updated set of QoS flow-to-frequency mappings from a vehicle-to-everything (V2X) layer to an access layer; and in an access layer (AS) layer, deriving a mapping from a target layer 2 identifier (L2ID) to a frequency mapping based on the received QoS flow-to-frequency mapping.

[0005] In some implementations, the QoS flow-to-frequency mapping includes a new service-to-frequency mapping.

[0006] In some implementations, the QoS flow-to-frequency mapping includes a new service-to-L2 ID mapping.

[0007] In some implementations, the V2X layer provides a complete set of all service-to-frequency mappings.

[0008] In some implementations, the V2X layer provides a complete set of service-to-frequency mappings in an initial link, and provides changes to the set of service-to-frequency mappings when it is determined that a PC5 QoS flow has been added or modified.

[0009] In some implementations, the AS layer synthesizes the QoS flow to carrier mapping.

[0010] In some implementations, the AS layer generates a subset of carriers among all QoS flows that are designated as allowed sidelink carriers based on the intersection between the carriers mapped to all QoS flows received from the V2X layer.

[0011] Some implementations include informing another UE of the set of allowed sidelink carriers via PC5 radio resource control (RRC) messaging.

[0012] In some implementations, the UE is in a connected state and notifies the connected gNB of the allowed sidelink carriers via an RRC message including sidelink user information (SUI).

[0013] In some implementations, the allowed sidelink carriers are a null set and the UE is in an idle / inactive state, and the UE requests to enter a connected state to notify the gNB of the null set via the SUI.

[0014] Aspects of particular implementations relate to an apparatus, such as a UE, having one or more baseband processors configured to perform a method having any of the above method steps.

[0015] Various aspects of the specific implementation relate to a method performed by a UE, the method comprising: receiving a list of allowed frequencies in a sidelink logical channel configuration message or other RRC configuration message for a logical channel; receiving a list of frequencies associated with a sidelink radio bearer (SLRB) index in an RRC sidelink reconfiguration message; in a medium access control (MAC) layer, mapping the logical channel to an allowed frequency in the list of allowed frequencies associated with the SLRB index; and sending data to the UE using sidelink resources including at least one frequency mapped to the logical channel.

[0016] Some implementations include identifying overlapping frequencies between frequencies in the allowed frequency list and a frequency list associated with the SLRB.

[0017] Some specific implementations include: identifying a set of available SLRBs from a higher layer mapping of QoS flows to frequencies; determining different lists of allowed frequencies based on the set of available SLRBs; and mapping logical channels to allowed frequencies from the different lists of allowed frequencies.

[0018] In some implementations, the UE is in idle / inactive / OOC mode.

[0019] In some embodiments, the UE is in connected mode and the method: identifies a set of available SLRBs from a higher layer mapping of QoS flows to frequencies; notifies a network entity to which the UE is connected of the received QoS flow to frequency mapping; and receives a logical channel prioritization (LCP) restriction from the network entity in an RRC message including a second sidelink logical channel configuration message.

[0020] In some implementations, the second sidelink logical channel configuration message includes a new list of allowed frequencies for the logical channel.

[0021] Some implementations may include mapping the unknown QoS flow to a SLRB index associated with a logical channel having a frequency list aligned with a mapped frequency of the UE.

[0022] In some implementations, the UE is in a connected state, and the method includes notifying a connected network entity of a mapping of an unknown QoS flow to a selected SLRB index.

[0023] In some embodiments, no existing SLRB has an associated logical channel with a frequency list aligned with a UE mapped frequency, and the method includes: adding the mapped frequency to the logical channel prioritization restriction of the default SLRB; and mapping the unknown QoS flow to the default SLRB.

[0024] In some embodiments, no existing SLRB has an associated logical channel having a frequency list aligned with a mapping frequency of the UE, and the method includes, if the UE is in a connected state, notifying a network entity connected to the UE of a failure to map an unknown QoS flow to a default SLRB.

[0025] In some specific implementations, the UE is in a connected state, and the method also includes notifying a connected network entity of a received QoS flow-to-frequency mapping received from the V2X layer using sidelink user information (SUI).

[0026] In some specific implementations, the method includes: receiving a new QoS flow to frequency mapping from a V2X layer; determining an existing side link radio bearer (SLRB) to frequency mapping; remapping the new QoS flow to the existing SLRB; and sending data to another UE using the new QoS flow to SLRB mapping.

[0027] In some implementations, the UE cannot change one or more frequencies mapped to an existing SLRB based on logical channel prioritization restrictions of the associated logical channels.

[0028] In some implementations, the UE uses RRC or SIB or other reconfiguration messaging to rewrite the Service Data Adaptation Protocol (SDAP) configuration in the Uu link.

[0029] Some implementations include: reporting the new QoS flow-to-frequency mapping to a connected network entity via a Sidelink User Information (SUI) message; and receiving a reconfiguration of the QoS flow-to-SLRB mapping from the connected network entity.

[0030] Some specific implementations include notifying the connected network entity through a SUI message that the UE cannot change the frequency set to which the SLRB is mapped due to logical channel prioritization restrictions associated with the logical channel.

[0031] In some specific implementations, the UE is in a connected state, and the method also includes notifying the connected network entity of the received QoS flow-to-frequency mapping received from the V2X layer via the SUI.

[0032] Aspects of the embodiments are directed to a UE comprising one or more baseband processors and a memory encoded with instructions that, when executed by the one or more baseband processors, cause the one or more baseband processors to perform the operations of any of the foregoing method steps.

[0033] Aspects of the embodiments relate to a system comprising one or more processors and one or more storage devices on which instructions are stored that, when executed by the one or more processors, are operable to cause the one or more processors to perform the operations of any of the above paragraphs.

[0034] Aspects of the embodiments are directed to apparatuses configured to perform one or more operations described in this Specification.

[0035] The details of one or more embodiments of these systems and methods are set forth in the following drawings and description. Other features, objects, and advantages of these systems and methods will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 An example communication system supporting sidelink communications according to some implementations is illustrated.

[0037] FIG. 2A to FIG. 2C is a diagram illustrating an example carrier aggregation (CA) scheme for sidelink communications according to some implementations.

[0038] Figure 3A is a schematic diagram illustrating LTE sidelink carrier selection and scheduling operations for V2X communication.

[0039] Figure 3B It is a schematic diagram illustrating the NR sidelink single-carrier transmission scheme.

[0040] Figure 4 is a signaling diagram illustrating sidelink communication between two UEs.

[0041] Figure 5 An SDAP header for sidelink unicast communication over the PC5 interface is illustrated.

[0042] Figure 6 The mapping between QoS flows, logical channels and L2 IDs is illustrated.

[0043] Figure 7 is an example process flow diagram illustrating a link-level frequency mapping scheme according to some specific implementations.

[0044] Figure 8 is an example process flow diagram illustrating another link-level frequency mapping scheme according to some implementations.

[0045] Fig. 9 The mapping between QoS flows, logical channels and L2 IDs according to some specific implementations is illustrated.

[0046] FIG. 10A to FIG. 10B is a flow chart illustrating an example process for configuring a set of allowed sidelink carriers according to some implementations.

[0047] FIG. 11A to FIG. 11B is a diagram illustrating a service-to-frequency mapping scheme for LTE and NR sidelink according to some specific implementations.

[0048] Fig.12 is a process flow diagram illustrating a method of logical channel level frequency selection according to some specific implementations.

[0049] Fig.13A is a process flow diagram illustrating QoS flow level frequency selection according to some specific implementations.

[0050] Fig. 13B is a process flow diagram illustrating an example method for configuring unicast sidelink communications according to some implementations.

[0051] FIG. 14A to FIG. 14B is a flow chart illustrating an example method for reporting LCP restriction updates to a network according to some implementations.

[0052] Fig.15 An example UE according to some implementations is illustrated.

[0053] Fig.16 Example access nodes according to some implementations are illustrated.

[0054] Like reference numerals indicate like features. DETAILED DESCRIPTION

[0055] Quality of Service (QoS) refers to the performance characteristics of a network or service as perceived by the end user. In 5G cellular systems, QoS includes a variety of factors, including service reliability, availability, latency, throughput, and traffic prioritization. QoS is a flow-based policy applied to each data flow from the radio physical (PHY) layer to the core network. In sidelink deployments, QoS flows are mapped to logical channels also known as sidelink radio bearers (SLRBs). These logical channels are then mapped to sidelink carriers (e.g., frequencies) that deliver the associated data over the wireless medium. The mapping between QoS flows, logical channels, and sidelink carriers is visible to lower layers (such as the PHY layer).

[0056] However, for MAC layer operation, the mapping between QoS flows and sidelink carriers may be inaccessible because the MAC layer is not configured to read the Service Data Adaptation Protocol (SDAP) header of the Protocol Data Unit (PDU), which includes this information. Therefore, the visibility of the MAC layer may be limited to logical channel operations. This may be problematic because other layers may restrict which QoS flows can be delivered or mapped to specific sidelink carriers. For example, the V2X layer and / or the Access Stratum (AS) layer may have a list of allowed sidelink carriers to which a given QoS flow can be mapped. Therefore, existing frequency mapping techniques may not be able to guarantee that the appropriate sidelink carrier is always used to deliver the QoS flow.

[0057] The present disclosure describes a signaling mechanism that ensures that QoS flows are mapped only to allowed sidelink carriers. According to one or more aspects of the present disclosure, a first UE receives a sidelink logical channel configuration message, for example, an information element (IE) called SL-LogicalChannelConfig, which indicates that sidelink data associated with a logical channel can be mapped to one or more sidelink carriers on a list of allowed sidelink carriers. The first UE determines the appropriate QoS flow to frequency mapping based on the sidelink logical channel configuration message. Accordingly, the first UE sends sidelink data to a second UE via at least one sidelink carrier on the list of allowed sidelink carriers.

[0058] The first UE may also send an RRC sidelink reconfiguration message (e.g., RRCReconfigurationSidelink) indicating a sidelink carrier to be released, modified, or added for unicast sidelink communications between the first UE and the second UE. In some implementations, the RRC sidelink reconfiguration message also indicates one or more QoS flows to be mapped to (or released from) the configured sidelink data radio bearer (DRB). Thus, the second UE may update the QoS flow to frequency mapping based on the RRC sidelink reconfiguration message. Among other advantages, the techniques described herein improve the reliability and consistency of a QoS flow mapping scheme for NR sidelink CA.

[0059] More specifically, the present disclosure describes frequency selection techniques referred to as link-level frequency selection, logical channel-level frequency selection, and QoS flow-level frequency selection. A communication system may be configured to use one or more of these frequency selection techniques.

[0060] In some specific implementations, link-level frequency selection implements a service-to-frequency mapping technique for LTE sidelink CA and NR multicast / broadcast CA. In this technique, whenever a PC5 QoS flow is added or modified, the V2X layer provides a new set of carriers for the sidelink unicast link so that the mapping is dynamically updated by the V2X layer to the AS layer. At the same time, the AS layer synthesizes the QoS flow to carrier mapping, the SDAP configuration (e.g., QoS flow indicator [QFI] to SLRB mapping), and the SLRB list to determine the set of allowed sidelink carriers. The TX UE (e.g., UE 105-1) notifies the RX UE (e.g., UE 105-2) of these allowed sidelink carriers via PC5 RRC, and if the TX UE is in a connected state, the same information may be optionally notified to the network (e.g., base station 110-1).

[0061] In some implementations, logical channel level frequency selection uses the concept of QoS flow to frequency mapping. For example, there may be new logical channel prioritization (LCP) restrictions on the set of carriers authorized by the sidelink (e.g., only some logical channels may be selected for a given carrier). The technology involves limiting which carrier(s) may be mapped to a specific sidelink DRB. The TXUE notifies the RX UE of the restricted carrier set for the sidelink DRB via PC5 RRC. In some examples, an unknown QoS flow cannot be mapped to a default SLRB because the default SLRB may not satisfy the frequency mapping constraints.

[0062] In some implementations, QoS flow level frequency selection updates the QoS flow to SLRB mapping according to the QoS flow to frequency mapping information provided by the V2X layer. In some examples, the TX UE is allowed to autonomously update the QoS flow to sidelink DRB mapping. Additionally or alternatively, the TX UE may report the mapping information to the network (via the SUI) and wait for the network to reconfigure the QoS flow to SLRB mapping.

[0063] Figure 1 An example communication system 100 supporting sidelink communication according to some specific implementations is illustrated. Note that Figure 1 The system is just one example of a possible system, and features of the present disclosure may be implemented in other wireless communication systems.

[0064] The following description is provided for an example communication system operating in conjunction with a fifth generation (5G) network provided by the 3GPP technical specifications. However, the example implementation is not limited in this regard, and the described examples may be applied to other networks that may benefit from the principles described herein, such as 3GPP Long Term Evolution (LTE) networks, Wi-Fi networks, etc. In addition, other types of communication standards are also possible, including future 3GPP systems (e.g., sixth generation (6G)), etc. Although various aspects may be described herein using terms typically associated with 5G NR, various aspects of the present disclosure may be applied to other systems, such as systems after 5G (e.g., 6G).

[0065] The frequency bands for 5G NR can be divided into two different frequency ranges. Frequency Range 1 (FR1) may include frequency bands operating at frequencies below 6 GHz, some of which may be used by previous standards and may potentially be expanded to cover new spectrum products from 410 MHz to 7125 MHz. Frequency Range 2 (FR2) may include frequency bands from 24.25 GHz to 52.6 GHz. Frequency bands in the millimeter wave (mmWave) range of FR2 may have a smaller range but potentially higher available bandwidth than frequency bands in FR1.

[0066] As shown, the communication system 100 includes a plurality of user equipments. More specifically, the communication system 100 includes two UEs 105 (UE 105-1 and UE 105-2 are collectively referred to as "UE 105" or "UEs 105"), two base stations 110 (base stations 110-1 and base stations 110-2 are collectively referred to as "base stations 110" or "base stations 110"), two cells 115 (cells 115-1 and cells 115-2 are collectively referred to as "cells 115" or "cells 115"), and one or more servers 135 in a core network (CN) 140 connected to the Internet 145.

[0067] In some implementations, UE 105 may communicate directly with base station 110 via links 120 (links 120-1 and 120-2 are collectively referred to as "a link 120" or "links 120"), which utilize a direct interface with the base station (referred to as a "Uu interface"). Each of links 120 may represent one or more channels. Links 120 are illustrated as air interfaces for achieving communication coupling and may conform to a cellular communication protocol, such as a 5G protocol, a NR protocol, an NR-based unlicensed spectrum access (NR-U) protocol, and / or any of the other communication protocols discussed herein.

[0068] As shown, some user equipments may be able to communicate directly with each other, for example, without intermediate infrastructure equipment (such as base station 110-1). In this example, UE 105-1 may communicate directly with UE 105-2. Similarly, UE 105-2 may communicate directly with UE 105-1. This peer-to-peer communication may utilize a "side link" interface such as a PC5 interface. In some specific implementations, the PC5 interface supports direct cellular communication between user equipments (e.g., between UE 105), while the Uu interface supports cellular communication with infrastructure equipment (such as a base station). For example, UE 105 may use the PC5 interface for radio resource control (RRC) signaling exchange (also referred to as PC5-RRC signaling) between UEs. The PC5 / Uu interface is used only as an example, and PC5 as used herein may represent various other possible wireless communication technologies that allow direct side link communication between user equipments, while Uu may represent cellular communication performed between user equipments and infrastructure equipment (such as a base station).

[0069] In some implementations, UE 105 may be configured with parameters for communicating via the Uu interface and / or the sidelink interface. In some examples, UE 105 may be "pre-configured with" some parameters. In these examples, the parameters may be hardwired into UE 105 or coded into the specification. Additionally and / or alternatively, UE 105 may receive the parameters from one or more of base stations 110.

[0070] In order to transmit / receive data to / from one or more base stations 110 or UE 105, UE 105 may include a transmitter / receiver (or alternatively, a transceiver), a memory, one or more processors, and / or other similar components that enable UE 105 to operate according to one or more wireless communication protocols and / or one or more cellular communication protocols. UE 105 may have one or more antenna elements that enable UE 105 to maintain multiple links 120 and / or side links 125 to transmit / receive data to / from multiple base stations 110 and / or multiple UE 105. For example, as Figure 1 As shown, UE 105 - 1 may be connected to base station 110 - 1 via link 120 and simultaneously connected to UE 105 - 2 via side link 125 .

[0071] In some implementations, one or more SLRBs can be established on the sidelink 125. The SLRBs can include signaling radio bearers (SL-SRBs) and / or data radio bearers (SL-DRBs).

[0072] The PC5 interface may alternatively be referred to as a sidelink interface and may include one or more logical channels, including but not limited to a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), a physical sidelink broadcast channel (PSBCH), a physical sidelink feedback channel (PSFCH) and / or any other similar communication channel. The PSFCH carries feedback related to the success or failure reception of the sidelink transmission. The PSSCH may be scheduled by the sidelink control information (SCI) carried in the sidelink PSCCH. In some examples, the sidelink interface may operate on an unlicensed spectrum (e.g., in an unlicensed 5 GHz (GHz) and 6 GHz band) or a (licensed) shared spectrum.

[0073] In one example, the sidelink interface implements V2X communication. V2X communication may, for example, follow the 3GPP Cellular V2X (C-V2X) specification, or follow one or more other or subsequent standards, whereby vehicles and other devices and network entities can communicate. V2X communication may utilize both long-range (e.g., cellular) communication and short-range to medium-range (e.g., non-cellular) communication. V2X communication with cellular capabilities may be referred to as cellular V2X (C-V2X) communication. C-V2X systems may use various cellular radio access technologies (RATs), such as 4G LTE or 5G NR RAT (or RATs after 5G, e.g., 6G RAT). Certain LTE standards available in V2X systems may be referred to as LTE-vehicle (LTE-V) standards. As used herein in the context of a V2X system, and as defined above, the term "user equipment" may generally refer to a device associated with a mobile participant or traffic participant in a V2X system, e.g., a mobile (capable of moving) communication device, such as a vehicle, a pedestrian user equipment (PUE) device, and a roadside unit (RSU).

[0074] In some implementations, the UEs 105 may be physical hardware devices that can run one or more applications, can access network services via one or more radio links 120 with corresponding base stations 110 (also referred to as "serving" base stations), and can communicate with each other via side links 125. The links 120 may allow the UEs 105 to send and receive data from the base stations 110 providing the links 120. The side links 125 may allow the UEs 105 to send and receive data with each other. The side links 125 between the UEs 105 may include one or more channels for transmitting information from the UE 105-1 to the UE 105-2 (or vice versa) and / or between the UE 105 and a UE-type RSU (or vice versa).

[0075] In some implementations, base stations 110 can communicate with each other over a backhaul connection 130, and can communicate with one or more servers 135 within CN 140 over another backhaul connection 133. The backhaul connection can be a wired and / or wireless connection.

[0076] In some implementations, UE 105 is configured to use a resource pool for sidelink communication. The sidelink resource pool defines the time-frequency resources used for sidelink communication and can be divided into multiple time slots, frequency channels, and frequency subchannels. In some examples, UE 105 is synchronized and performs sidelink transmission aligned with time slot boundaries. It is expected that the UE selects several time slots and subchannels for the transmission of a transport block. In some examples, the UE can use different subchannels to send a transport block across multiple time slots within its own resource selection window.

[0077] In some implementations, the base station 110 may configure a special exception resource pool for the UE 105. The special exception resource pool includes resources that the UE 105 can use in special exception situations such as radio link failure (RLF). The special exception resource pool may include resources selected based on random resource allocation.

[0078] In some implementations, a UE that is initiating communication with another UE is referred to as a transmitting UE (TX UE), and a UE that receives the communication is referred to as a receiving UE (RX UE). For example, UE 105-1 may be a TX UE, and UE 105-2 may be a RX UE. Figure 1 It is illustrated that a single TX UE communicates with a single RX UE, but the TX UE may communicate with more than one RX UE via a side link.

[0079] In some implementations, a TX UE initiating sidelink communication may determine available resources (e.g., sidelink resources) and may select a subset of these resources to communicate with the RX UE based on a resource allocation scheme. Example resource allocation schemes include a Mode 1 resource allocation scheme and a Mode 2 resource allocation scheme. In a Mode 1 resource allocation scheme (referred to as "Mode 1"), resources are allocated by a network node to UEs within coverage. In a Mode 2 resource allocation scheme (referred to as "Mode 2"), the TX UE selects sidelink resources (e.g., sidelink transmit resources).

[0080] In some implementations, the communication system 100 supports different broadcast types, including unicast, broadcast, and groupcast (or multicast) communications. Unicast refers to direct communication between two UEs. Broadcast refers to communication broadcasted by a single UE to multiple other UEs. Groupcast refers to communication transmitted from a single UE to a set of UEs that meet a certain condition (e.g., as members of a specific group).

[0081] Wireless communication systems, such as the communication system 100, use CA to increase the effective data rate of a particular device. CA is a communication scheme in which multiple carriers (e.g., frequency channels) are available for wireless communication between devices. CA involves using two or more component carriers (CCs) to communicate data between a transmitter (such as a TX UE) and a receiver (such as an RX UE). CA types include intra-band contiguous aggregation ( Figure 2A In-band non-contiguous aggregation ( Figure 2B shown) or inter-band aggregation ( Figure 2C shown).

[0082] FIG. 2A to FIG. 2Cis a schematic diagram illustrating an example CA scheme for sidelink communications. In the illustrated scheme, two frequency bands are shown: frequency band 202 (e.g., frequency band 1) and frequency band 210 (e.g., frequency band 2), each having multiple CCs. In the illustrated example, frequency band 202 includes CC 204, CC 206, and CC 208; frequency band 210 includes CC 212, CC 214, and CC 216. Although three CCs are shown, it should be understood that each frequency band may include any number of CCs. Figure 1 The plurality of CCs may be aggregated by one of the UEs 105 described herein. Each CC may have a predefined bandwidth depending on network configuration, current standards, or based on other settings.

[0083] Figure 2A An intra-band continuous CA scenario 200a is illustrated in which CCs of adjacent frequency channels are aggregated. Figure 2A As shown, adjacent CCs 206 and 208 are aggregated. In addition, in some examples, the CA scheme may identify a primary component carrier (PCC) and a secondary component carrier (SCC). Here, CC 206 is PCC 220a, and CC 208 is SCC 220b. In some examples, the network may designate a PCC to perform control signaling as well as data transmission. The SCC may be designated to perform data transmission, thereby increasing throughput. In some examples, the PCC may also be configured during connection and reconfigured during handover, while the SCC may be configured as needed.

[0084] like Figure 2B and Figure 2C As shown, CA can also be implemented using non-contiguous frequency channels. Figure 2B An intra-band non-continuous CA scenario 200b is illustrated. Figure 2B , CC 204 is designated as PCC 220a; and CC 208 is designated as SCC 220b, where CC 204 and CC 208 are in the same frequency band.

[0085] Figure 2C An inter-band CA scenario 200c is illustrated (inter-band CA is naturally discontinuous). Figure 2C In FIG. 2 , CC 206 is designated as PCC 220a and component carrier 216 is designated as SCC 220b, where CC 206 and CC 216 are in the same frequency band. By using inter-band, CA can be achieved using a frequency channel in a licensed band as one CC and a frequency channel in an unlicensed band as another CC.

[0086] Although the example provided FIG. 2A to FIG. 2CThe exemplary schemes illustrated and the associated descriptions are provided as one possible way to implement CA, but they are not intended to limit the present disclosure as a whole. Many alternatives and variations to its details are possible and should be considered within the scope of the present disclosure. For example, the CA scheme may be implemented in conjunction with other wireless communication technologies; carriers according to other LTE versions or other radio access technologies may be used; carriers with different channel widths may be used; different numbers of component carriers may be supported; and many other alternatives and variations to the illustrated schemes are also possible.

[0087] As discussed in more detail below, the present disclosure relates to NR sidelink CA, which can utilize some LTE sidelink CA operations. For example, the following LTE sidelink CA features can be supported for NR: sidelink carrier (re)selection, synchronization of aggregated carriers, power control for simultaneous sidelink TX, packet duplication, etc. The features described herein are applicable to intra-band CA for the ITS band in FR1 (band n47).

[0088] These features may be backward compatible in that UEs of different types / capabilities may receive sidelink broadcast / multicast transmissions utilizing CA for a carrier on which the UE receives PSCCH / PSSCH and sends corresponding sidelink HARQ feedback (when sidelink HARQ is enabled by SCI). In some examples, the described techniques are applicable to Mode 2 sidelink operation. For NR sidelink CA, the same subcarrier spacing (SCS) may be used between CA carriers to avoid resource selection and AGC issues. The time resources for PSFCH may be aligned between carriers used for CA.

[0089] SCI transmission, PSFCH transmission, RSRP feedback, CSI feedback and congestion control on PSCCH / PSSCH may be implemented as per-carrier operations. Sidelink resource indication may be per-resource pool and per-carrier (no cross-carrier scheduling in SCI). A UE may send sidelink HARQ feedback on the same carrier on which the UE receives the associated PSSCH.

[0090] NR sidelink CA can use LTE sidelink CA design for sidelink carrier (re)selection, synchronization of aggregated carriers, transmit power splitting for simultaneous sidelink transmissions, packet duplication, etc. NR sidelink CA band combinations can work for intra-band continuous CA. Sidelink NR CA is applicable to many V2X use cases.

[0091] Some aspects of the LTE sidelink may not be suitable for PCC / SCC configuration in NR sidelink CA. For example, in the LTE sidelink, there is no RRC connection in the PC5 interface, sidelink unicast is not supported, and HARQ feedback is not supported. In addition, the service-to-carrier mapping is provided by upper layers (such as the V2X layer) rather than configured by the AS layer. The upper layers may request the UE to use V2X communication over PC5 to transmit V2X messages for the V2X service identified by the V2X service identifier. The request from the upper layer includes: a V2X message; a V2X service identifier for the V2X service for the V2X message; the type of data in the V2X message (IP or non-IP); an indication of whether the V2X message contains non-IP data, the V2X message data family in the V2X message; the V2X message priority; and an optional ProSe per-packet reliability (PPPR) value.

[0092] When requesting from an upper layer to use V2X communication through PC5 to transmit a V2X message for a V2X service identified by a V2X service identifier, if the UE is configured with a V2X service identifier to V2X frequency mapping rule for V2X communication through PC5, and there are one or more V2X frequencies associated with the V2X service identifier of the V2X service for the V2X message in the current geographic area, then the one or more V2X frequencies associated with the V2X service identifier of the V2X service for the V2X message may be passed to the lower layer.

[0093] For NR sidelink, layer 2 ID to frequency mapping is allowed. However, NR SL can be a single carrier system.

[0094] Figure 3A is a schematic diagram illustrating LTE sidelink carrier selection and scheduling operations for V2X communication, and Figure 3B is a schematic diagram illustrating a single carrier transmission scheme for the NR side link. The broadcast / multicast signaling mechanism of the NR side link may be similar to LTE CA. For multicast / broadcast, as in LTE side link CA, the carrier available for sending data is configured by the V2X layer for the L2 target. However, for unicast, only the mapping between the service identifier for unicast and the initial L2 address is provided to the V2X layer. The service identifier is inaccessible to the AS layer, and the initial L2 ID used only in the direct communication request (DCR) can be replaced by the self-selected L2 ID during the PC5-S link establishment process. After the L2ID changes, the AS layer may not be able to obtain the mapping between the L2 ID and the frequency.

[0095] PC5 unicast allows the UE to add, modify, and remove V2X services (e.g., PC5 QoS flows) to the same L2 ID pair. However, since the service information may not be accessible to the AS layer, the UE may not be able to ensure that the modified V2X service is sent only on the corresponding frequency in the V2X layer.

[0096] By providing the frequency information together with the PC5-S message from the V2X layer to the AS layer, the AS layer can obtain the frequency information associated with the PC5-S message transmitted for PC5 unicast link establishment. Therefore, the UE can ensure that the modified V2X service is sent only on the corresponding frequency mapped in the V2X layer. The AS layer maintains the PC5 unicast link related context within the lifetime of the PC5 unicast link based on various information provided by the V2X layer (e.g., PC5 link identifier, source L2 ID, target L2 ID, etc.).

[0097] The V2X layer updates the AS layer about the PC5 QoS flow addition, modification and / or removal for the established PC5 unicast link. For PC5 QoS flow addition, the V2X layer provides the AS layer with one or more radio frequencies associated with the added PC5 QoS flow. The V2X layer may determine the radio frequency based on a mapping of V2X service types associated with the PC5 QoS flow to V2X frequencies using a relevant configuration (e.g., a mapping of V2X service types to V2X frequencies using a geographic area). The V2X layer ensures that V2X service types associated with different radio frequencies are classified into different PC5 QoS flows.

[0098] In the QoS model, the Service Data Adaptation Protocol (SDAP) is used to perform QoS flow to sidelink DRB mapping, but may not be used for QoS monitoring. The SDAP header is used only in sidelink unicast to indicate QoS flow remapping (end marker). One difference between the sidelink DRB model and the Uu DRB is that the logical channel ID (LCID) selection is performed by the UE, rather than configured by the NW. When the peer UE receives a SLRB configuration with a radio link control (RLC) acknowledgement mode (AM) / unacknowledgement mode (UM) for a specific LCID from the initiating UE via PC5 RRC, the peer UE autonomously assigns the LCID value to the configured SLRB. For the sidelink, 3 logical channel prioritization (LCP) restrictions are specified. These restrictions include: whether the configured grant type 1 can be used; the configured grant list allowed; and whether HARQ feedback is enabled or not, it is multiplexed with the logical channel.

[0099] Figure 4 is a signaling diagram illustrating sidelink communication between two UEs (UE1 and UE2). Figure 5 exemplifies the SDAP header for sidelink unicast communication over the PC5 interface. Figure 4 In the embodiment, UE1 and UE2 each include a Packet Data Convergence Protocol (PDCP) entity, which is responsible for: delivery of user plane data; delivery of control plane data; header compression; encryption; and integrity protection. UE2 may use sidelink resources to transmit an RLC scheduling request to UE1. UE1 may respond to UE2 with an RLC data PDU on the sidelink resources.

[0100] Figure 6 The mapping between QoS flows, logical channels (also called SLRBs) and L2 IDs is illustrated. Figure 6 As shown in , the QoS flow to carrier mapping is provided to the lower layers, and each QoS flow can be mapped to multiple sidelink carriers (e.g., f1, f2). However, for MAC layer operations, QoS flows are not visible, only logical channels are visible. The QoS flows to be used in one logical channel (e.g., a list of QFIs or QoS profiles) are configured in RRC signaling by the network or via pre-configuration. The MAC layer may not be able to determine which QoS flows are providing data to a given logical channel buffer, so the MAC layer entity may not be able to determine the allowed frequency subset to be used for a particular logical channel. This is because it is not assumed that the MAC layer entity reads the SDAP header ( Figure 5 An example SDAP header is shown in FIG.

[0101] As described in more detail below, aspects of the present disclosure may help ensure that a QoS flow is not delivered to a carrier that is not allowed by the V2X layer. In other words, for a PDU corresponding to a QoS flow: the selected carrier must be on the list of carriers allowed by the V2X layer for that QoS flow; and the selected carrier must be on the list of carriers allowed by the AS layer for sidelink CA operation. In some examples, a system information block (SIB) may provide a frequency list, but the PC5 RRC may not provide the frequency list.

[0102] For LTE sidelink LCP, the MAC entity performs the following LCP process for each SCI sent in the SC period or for each SCI corresponding to a new transmission in the V2X sidelink communication. The MAC entity allocates resources to the sidelink logical channel by the following operations. If the carrier is configured by the upper layer, the MAC entity only considers the sidelink logical channels allowed on the carrier where the SCI is sent for the V2X sidelink communication. Similarly, when (re)selecting a carrier, the MAC entity only considers the sidelink logical channels with priority whose associated threshCBR-FreqReselection is not lower than the channel busy rate (CBR) of the carrier. If duplication is activated, the MAC entity only considers one of the sidelink logical channels corresponding to the same PDCP entity.

[0103] First, the MAC entity selects a ProSe target that has a sidelink logical channel with the highest priority among the sidelink logical channels that have data available for transmission and have the same transmission format as the transmission format selected for the ProSe target. Sidelink logical channels belonging to the same ProSe target may have the same transmission format. For each MAC PDU associated with the SCI, the MAC entity allocates resources to the sidelink logical channel with the highest priority among the sidelink logical channels that belong to the selected ProSe target and have data available for transmission. If any resources remain, the sidelink logical channels belonging to the selected ProSe target are served in descending order of priority until the data for the sidelink logical channel or the sidelink grant is exhausted (whichever arrives first). Sidelink logical channels configured with equal priority are served identically.

[0104] Figure 7 700 is a process flow diagram illustrating a link level mapping scheme implemented by a UE according to some specific implementations. Figure 7 In the example of , the service-to-frequency mappings for LTE sidelink CA and NR multicast / broadcast CA are reused. At the beginning, the UE determines (702) that a PC5 QoS flow has been added or modified. Whenever a PC5 QoS flow is added or modified, the V2X layer may provide (704) a new / updated QoS flow-to-frequency mapping to the AS layer. The new / updated mapping includes a new service-to-frequency mapping and, optionally, a new service-to-L2 ID mapping. In some embodiments, a complete set of service-to-frequency mappings is provided (706). In other embodiments, a complete set of mappings is provided on the initial link, and increments (e.g., changes to the mapping) are provided once a PC5 QoS flow is added / modified.

[0105] In the AS layer, the UE derives 708 a mapping from the target L2 ID to frequency mapping based on the received mapping from service to target L2 ID and mapping from service to frequency. The UE may use 710 the mapped frequency carriers to communicate with another UE over a sidelink. Figure 7 The example shown in uses the principle of LTE single carrier CA, where different target L2 IDs are used to distinguish different services. In other examples, the service-to-frequency mapping for LTE sidelink CA and NR multicast / broadcast CA can be reused in conjunction with additional QoS flow-to-frequency mapping information provided by the V2X layer. The AS layer can synthesize the QoS flow-to-carrier mapping, SDAP configuration (e.g., QFI to SLRB mapping), and SLRB list to create a minimum set of allowed sidelink carriers.

[0106] Figure 8800 is a process flow diagram illustrating another link level mapping scheme implemented by a UE according to some specific implementations. At the beginning, the UE determines (802) that a PC5 QoS flow has been added or modified. The V2X layer provides (804) the QoS flow to carrier mapping to the AS layer. The mapping is provided in a semi-static manner. The AS layer assumes (806) that all those QoS flows are to be supported simultaneously. Then, the AS layer generates (808) a subset of carriers in all QoS flows (e.g., a list of allowed sidelink carriers). The subset of allowed carriers is the intersection of the set of mapped carriers for all possible QoS flows. The UE uses (810) the subset of allowed carriers to communicate with another UE via a sidelink.

[0107] Fig. 9 The mapping between QoS flows, logical channels and L2 IDs according to some specific implementations is illustrated. Fig. 9 Shows which carrier subsets are allowed for a particular QoS flow. For example, the V2X layer may indicate that QoS flow 1 may be mapped to carrier<f1,f2,f3,f4> , QoS flow 2 can be mapped to<f2,f3,f4> , QoS flow 3 can be mapped to<f3,f4> , and QoS flow 4 can be mapped to<f3,f4,f5> In this example, the allowed sidelink carriers are<f3,f4> ,because<f3,f4> Allowed for each of the four QoS flows. If there are no carriers in the intersection, the set of allowed sidelink carriers may be empty.

[0108] FIG. 10A to FIG. 10B is a flow chart illustrating an example process for configuring a set of allowed sidelink carriers according to some implementations. Fig. 10A The process described in can be implemented by a TX UE in a connected state, while Fig. 10B The process depicted in may be implemented by a TX UE in an idle / inactive state. In both scenarios, the TX UE may notify the RX UE of the allowed sidelink carriers via PC5RRC. If the TX UE is in a connected state, the TX UE may notify the network (e.g., gNB) of the allowed sidelink carriers via SUI. As discussed above, in some cases, the set of allowed carriers may be empty. If the TX UE is in an idle / inactive state and the set of allowed sidelink carriers is empty, the TX UE may request to enter a connected state to report the problem to the network via SUI.

[0109] Link-level frequency mapping technology ( Figure 71 L2 ID mapping.

[0110] FIG. 11A to FIG. 11B is a schematic diagram illustrating a logical channel level frequency mapping scheme for LTE sidelink and NR sidelink according to some specific implementations. Fig.12 is a process flow diagram illustrating a method of logical channel level frequency selection according to some implementations. In order to ensure that different services are transmitted in different frequencies with the same L2ID, a new LCP restriction on carrier sets may be introduced for logical channel level frequency mapping.

[0111] At the RRC level, a frequency list (e.g., AllowedFrequencies) may be included (1202) in the SL-LogicalChannelConfig for a particular logical channel. A frequency list associated with a given SLRB index may also be included (1204) in the RRCReconfigurationSidelink. In some examples, the TX UE may use (1206) a configuration different from that in the SL-LogicalChannelConfig because a new mapping of QoS flows to frequencies provided by the V2X layer may dynamically change the SLRB carrier set. In other examples, the TX UE uses the same configuration indicated by the SL-LogicalChannelConfig. The TX UE may notify the network of the received QoS flow to frequency mapping and wait for the network to reconfigure the LCP restrictions via the SL-LogicalChannelConfig. In some implementations, if the TX UE is in a connected state, the TX UE may use a different configuration. If the TX UE is in an idle / inactive / OOC state, the TX UE may use the same configuration indicated by the SL-LogicalChannelConfig.

[0112] In some embodiments, a new field may be added to the SL-LogicalChannelConfig to indicate the allowed frequency list. Additionally or alternatively, one or more fields may be added to the RRCReconfigurationSidelink IE to assist in adding, modifying, or releasing a sidelink carrier. If configured in the SL-LogicalChannelConfig or in the RRCReconfigurationSidelink (at the MAC layer), the TX UE maps (1208) the logical channel to the configured frequency list and uses (1210) these resources to communicate with the RX UE via the sidelink. An unknown QoS flow may not be mapped to the default SRLB because the associated logical channel of the default SRLB may use an unallowed carrier of the unknown QoS flow. It is possible that the associated logical channel does not configure an LCP restriction on the carrier, or that the unknown QoS flow does not allow the configured restriction on the carrier.

[0113] To address this issue, the TX UE may autonomously map the unknown QoS flow to a SLRB whose associated logical channel frequency list is aligned with the mapping frequency of the TX UE. If the TX UE is in a connected state, the TX UE may notify the network of the mapping of the unknown QoS flow to the selected SLRB. If no existing SLRB satisfies this condition, the TX UE may (i) add the mapped frequency to the LCP limit of the default SLRB and then map the unknown QoS flow to the default SLRB, or (ii) if the TX UE is in a connected state, notify the network of the failure to map the unknown QoS flow to the default SLRB.

[0114] Fig.13A is a process flow diagram illustrating a QoS flow level frequency selection process implemented by a TX UE according to some specific implementations. Upon receiving (1302) a new QoS flow to frequency mapping, the TX UE may not change the LCP restriction for some reason, but will rely on the remapping of the SLRB for the QoS flow of interest. In some specific implementations, the TX UE may autonomously update (1304) the QoS flow to SLRB mapping via RRCReconfigurationSidelink. Thus, the TX UE may communicate with the RX UE via the side link using the mapped carrier resources (1306). The TX UE may not change the carrier set of the mapped SLRB via the LCP restriction of the associated logical channel; however, the TX UE may remap the new QoS flow to an existing SLRB that meets the mapping frequency requirements. The TX UE may be able to rewrite the SDAP configuration in the Uu RRC or SIB or reconfiguration.

[0115] Alternatively, the TX UE may report the new QoS flow to frequency mapping to the network / gNB via the SUI and wait for network reconfiguration of the QoS flow to SLRB mapping. The TX UE may also inform the gNB that the TX UE cannot change the carrier set of the mapped SLRBs via the LCP restriction of the associated logical channel in the SUI. In this example, the TX UE may not be able to overwrite the SDAP configuration in the Uu RRC or SIB or reconfiguration.

[0116] Fig. 13B is a process flow diagram illustrating an example method for configuring unicast sidelink communications between a TX UE and an RX UE according to some implementations. Fig. 13B In an example, the TX UE and / or the RX UE may receive (1308) a configuration for mapping a PC5 QoS flow to a frequency. The TX UE may receive (1310) a sidelink logical channel configuration message (e.g., SL-LogicalChannelConfig) indicating that sidelink data associated with the logical channel may be mapped to one or more sidelink carriers on a list of allowed sidelink carriers. Based on mapping the logical channel to at least one sidelink carrier on the list of allowed sidelink carriers according to the sidelink logical channel configuration message, the TX UE may send (1312) sidelink data associated with the logical channel via the at least one sidelink carrier.

[0117] FIG. 14A to FIG. 14B is a flow chart illustrating an example method for reporting LCP restriction updates to a network according to some implementations. Fig.14A and Fig. 14B The operation is applicable to logical channel level frequency mapping (refer to Fig.12 13 ). Continuing with the above example, if the TX UE is in a connected state, the TX UE may notify the NW via the SUI of the QoS flow-to-carrier mapping received from the V2X layer.

[0118] For logical channel level mapping ( Fig.12), the TX UE receives the QoS flow to carrier mapping from the V2X layer. The TX UE reports the received mapping to the gNB using the SUI. The TX UE and the gNB / network may exchange RRCReconfiguration messages with updated LCP restrictions for the carrier set. The TX UE may exchange RRCReconfigurationSidelink messages with the RX UE to update the carrier set for a given SLRB. For QoS level mapping (Figure 13), the TX UE may receive QoS flow to carrier mapping information from the V2X layer. The TX UE reports the received mapping to the gNB using the SUI, but the TX UE may not be able to change carriers via LCP. The TX UE and the gNB may exchange RRCReconfiguration messages to update the SDAP configuration. The TX UE may exchange RRCReconfigurationSidelink messages with the RX UE to update the SDAP configuration.

[0119] In some implementations, the TX UE may obtain the link level frequency mapping ( Figure 8 ), but if the allowed carriers do not exist or are very few and the TX UE cannot meet the overall throughput requirements for the QoS flow, the TX UE may switch to logical channel level frequency mapping, as shown in reference Fig.12 Shown and described.

[0120] Fig.15 An example UE 1500 according to some implementations is illustrated. The UE 1500 may be similar to Figure 1 UE 105 and is substantially interchangeable therewith. UE 1500 may be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., a microphone, a pressure sensor, a thermometer, a motion sensor, an accelerometer, an inventory sensor, a voltage / current meter, etc.), a video device (e.g., a camera, a camcorder, etc.), a wearable device (e.g., a smart watch), a loose IoT device.

[0121] UE 1500 may include a processor 1502, RF interface circuitry 1504, memory / storage 1506, a user interface 1508, a sensor 1510, a driver circuit 1512, a power management integrated circuit (PMIC) 1514, one or more antennas 1516, and a battery 1518. The components of UE 1500 may be implemented as an integrated circuit (IC), a portion of an integrated circuit, a discrete electronic device or other module, logical component, hardware, software, firmware, or a combination thereof. Fig.15The block diagram of UE 1500 is intended to show a high-level view of some of the components of UE 1500. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0122] Components of UE 1500 may be coupled to various other components via one or more interconnects 1520, which may represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, optical connection, etc., which allows various circuit components (on a common or different chip or chipset) to interact with each other.

[0123] The processor 1502 may include processor circuits such as a baseband processor circuit (BB) 1522A, a central processor unit circuit (CPU) 1522B, and a graphics processor unit circuit (GPU) 1522C. The processor 1502 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program codes, software modules, or functional processes from the memory / storage device 1506) to cause the UE 1500 to perform operations as described herein.

[0124] In some implementations, the baseband processor circuit 1522A may access a communication protocol stack 1524 in the memory / storage device 1506 to communicate over a 3GPP compatible network. In general, the baseband processor circuit 1522A may access the communication protocol stack to: perform user plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access layer. In some implementations, the PHY layer operations may be additionally / alternatively performed by components of the RF interface circuit 1504. The baseband processor circuit 1522A may generate or process a baseband signal or waveform that carries information in a 3GPP compatible network. In some implementations, the waveform for NR may be based on cyclic prefix orthogonal frequency division multiplexing (OFDM) "CP-OFDM" in the uplink or downlink, and discrete Fourier transform spread OFDM "DFT-S-OFDM" in the uplink.

[0125] The memory / storage 1506 may include one or more non-transitory computer-readable media including instructions (e.g., the communication protocol stack 1524) that may be executed by one or more of the processors 1502 to cause the UE 1500 to perform various operations described herein. The memory / storage 1506 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1500. In some implementations, some of the memory / storage 1506 may be located on the processor 1502 itself (e.g., L1 cache and L2 cache), while other memory / storage 1506 may be external to the processor 1502 but accessible via a memory interface. Memory / storage 1506 may include any suitable volatile or non-volatile memory, such as, but not limited to, 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, or any other type of memory device technology.

[0126] RF interface circuit 1504 may include transceiver circuits and radio frequency front end modules (RFEMs) that allow UE 1500 to communicate with other devices over a radio access network. RF interface circuit 1504 may include various elements arranged in a transmit or receive path. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, control circuits, etc.

[0127] In the receive path, the RFEM may receive the radiated signal from the air interface via antenna 1516 and proceed to filter and amplify the signal (using a low noise amplifier). The signal may be provided to a transceiver's receiver, which down-converts the RF signal to a baseband signal, which is provided to a baseband processor of processor 1502.

[0128] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier before the signal is radiated across the air interface via the antenna 1516. In various specific implementations, the RF interface circuit 1504 may be configured to transmit / receive signals in a manner compatible with the NR access technology.

[0129] Antenna 1516 may include one or more antenna elements to convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. Antenna 1516 may have an antenna panel that is omnidirectional, directional, or a combination thereof to achieve beamforming and multi-input, multi-output communications. Antenna 1516 may include a microstrip antenna, a printed antenna manufactured on the surface of one or more printed circuit boards, a patch antenna, a phased array antenna, etc. Antenna 1516 may have one or more panels that are designed for a specific frequency band including a frequency band in FR1 or FR2.

[0130] The user interface 1508 includes various input / output (I / O) devices designed to enable the user to interact with the UE 1500. The user interface 1508 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual components for accepting input, and in particular includes one or more physical or virtual buttons (e.g., reset button), physical keyboards, keypads, mice, touch pads, touch screens, microphones, scanners, headphones, etc. The output device circuit includes any physical or virtual components for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuit may include any number or combination of audio or visual displays, in particular including one or more simple visual outputs / indicators (e.g., binary state indicators (such as light emitting diodes "LEDs") and multi-character visual outputs) or more complex outputs (such as display devices or touch screens (e.g., liquid crystal displays "LCDs", LED displays, quantum dot displays, projectors, etc.)), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the UE 1500.

[0131] Sensor 1510 may include a device, module, or subsystem whose purpose is to detect events or changes in its environment and to communicate information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit including an accelerometer, gyroscope, or magnetometer; a microelectromechanical system or nanoelectromechanical system including a three-axis accelerometer, three-axis gyroscope, or magnetometer; a liquid level sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; a microphone or other similar audio capture device; and the like.

[0132] The driver circuit 1512 may include software and hardware elements that operate to control a specific device embedded in, attached to, or otherwise communicatively coupled to the UE 1500. The driver circuit 1512 may include various drivers to allow other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE 1500. For example, the driver circuit 1512 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface, a sensor driver for obtaining sensor readings of the sensor 1510 and controlling and allowing access to the sensor 1510, a driver for obtaining an actuator position of an electromechanical component or controlling and allowing access to an electromechanical component, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0133] The PMIC 1514 may manage the power provided to various components of the UE 1500. Specifically, with respect to the processor 1502, the PMIC 1514 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0134] In some implementations, the PMIC 1514 may control or otherwise be part of various power saving mechanisms of the UE 1500. The battery 1518 may power the UE 1500, but in some examples, the UE 1500 may be mounted in a fixed location and may have a power source coupled to a power grid. The battery 1518 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in vehicle-based applications, the battery 1518 may be a typical lead-acid automotive battery.

[0135] Fig.16 An example access node 1600 (e.g., a base station or gNB) is illustrated according to some implementations. Access node 1600 may be similar to base station 110 and substantially interchangeable therewith. Access node 1600 may include a processor 1602, RF interface circuitry 1604, core network (CN) interface circuitry 1606, memory / storage circuitry 1608, and one or more antennas 1610.

[0136] The components of access node 1600 may be coupled to various other components via one or more interconnects 1612. Processor 1602, RF interface circuitry 1604, memory / storage circuitry 1608 (including communication protocol stack 1614), antenna 1610, and interconnects 1612 may be similar to those described with respect to Fig.15Like-named elements are shown and described.For example, processor 1602 may include processor circuits such as, for example, baseband processor circuit (BB) 1616A, central processor unit circuit (CPU) 1616B, and graphics processor unit circuit (GPU) 1616C.

[0137] The CN interface circuit 1606 may provide a connection to a core network (e.g., a 5GC using a 5th Generation Core Network (5GC) compatible network interface protocol such as a Carrier Ethernet protocol or some other suitable protocol). The network connection may be provided to / from the access node 1600 via optical fiber or wireless backhaul. The CN interface circuit 1606 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1606 may include multiple controllers for providing connections to other networks using the same or different protocols.

[0138] As used herein, the terms "access node", "access point", etc. may be described as equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP or TRP, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node", etc. may refer to an access node 1600 (e.g., a gNB) operating in an NR or 5G system, and the terms "E-UTRAN node", etc. may refer to an access node 1600 (e.g., an eNB) operating in an LTE or 4G system. According to various specific implementations, the access node 1600 may be implemented as one or more of a dedicated physical device such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell.

[0139] In some implementations, all or part of the access node 1600 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In a V2X scenario, the access node 1600 may be or act as a "roadside unit". The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communications. The RSU may be implemented in or by a suitable RAN node or a stationed (or relatively stationed) UE, where an RSU implemented in or by a UE may be referred to as a "UE-type RSU", an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU", an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU", and so on.

[0140] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". The statement that a component is configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. §112(f) interpretation of that component.

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

[0142] Embodiment 1 is a device comprising: one or more processors; and a memory storing instructions which, when executed by the one or more processors, cause the device to perform operations comprising: receiving a configuration for mapping a PC5 QoS flow to a frequency from an RF circuit; receiving a sidelink logical channel configuration message from the RF circuit, indicating that sidelink data associated with a logical channel can be mapped to one or more sidelink carriers on a list of allowed sidelink carriers; and instructing the RF circuit to send the sidelink data associated with the logical channel via the at least one sidelink carrier based at least in part on mapping the logical channel to at least one sidelink carrier on the list of allowed sidelink carriers according to the configuration for mapping and the sidelink logical channel configuration message.

[0143] Embodiment 2 is an apparatus according to embodiment 1, wherein the operation further includes: instructing the RF circuit to send an RRC side link reconfiguration message according to the side link logical channel configuration message, the RRC side link reconfiguration message indicating a side link carrier on the list of allowed side link carriers to be added or modified for unicast side link communication, wherein the side link data is sent via the side link carrier indicated by the RRC side link reconfiguration message.

[0144] Embodiment 3 is an apparatus according to any one of embodiments 1 to 2, wherein the operation further includes: instructing the RF circuit to send an RRC side link reconfiguration message according to the side link logical channel configuration message, the RRC side link reconfiguration message indicating a side link carrier to be released from unicast side link communication, wherein sending the side link data via the at least one side link carrier on the list of allowed side link carriers is at least partially based on the RRC side link reconfiguration message.

[0145] Embodiment 4 is an apparatus according to any one of embodiments 1 to 3, wherein the operation further includes: instructing the RF circuit to send an RRC side link reconfiguration message according to the side link logical channel configuration message, the RRC side link reconfiguration message indicating one or more PC5 QoS flows to be mapped to a DRB configured for unicast side link communication, wherein the side link data is sent using the DRB mapped to the one or more QoS flows indicated by the RRC side link reconfiguration message.

[0146] Embodiment 5 is an apparatus according to any one of embodiments 1 to 4, wherein the operation further includes: instructing the RF circuit to send an RRC side link reconfiguration message based on the side link logical channel configuration message, the RRC side link reconfiguration message indicating one or more PC5 QoS flows to be released from a DRB configured for unicast side link communication, wherein instructing the RF circuit to send the side link data via the at least one side link carrier on the list of allowed side link carriers is at least partially based on the RRC side link reconfiguration message.

[0147] Embodiment 6 is an apparatus according to any one of embodiments 1 to 5, wherein the operation further includes: instructing the RF circuit to send an RRC side link reconfiguration message based on the side link logical channel configuration message, the RRC side link reconfiguration message including an identifier of the logical channel to which the at least one side link carrier is mapped, wherein instructing the RF circuit to send the side link data via the at least one side link carrier mapped to the logical channel is at least partially based on the RRC side link reconfiguration message.

[0148] Embodiment 7 is an apparatus according to any one of embodiments 1 to 6, wherein a field of the sidelink logical channel configuration message indicates the list of allowed sidelink carriers for the logical channel.

[0149] Embodiment 8 is an apparatus according to any one of embodiments 1 to 7, further comprising determining, based at least in part on the sidelink logical channel configuration message, that the at least one sidelink carrier is within a frequency subset associated with all PC5 QoS flows allowed to be mapped to the logical channel.

[0150] Embodiment 9 is an apparatus according to any one of embodiments 1 to 8, wherein the sidelink logical channel configuration message indicates that the sidelink data from the logical channel can be mapped to any configured sidelink carrier.

[0151] Embodiment 10 is a device according to any one of embodiments 1 to 9, further comprising, when the device is in a connected state, instructing the RF circuit to send a SUI message to a network entity, wherein the SUI message indicates the mapping between the PC5 QoS flow and the frequency.

[0152] Embodiment 11 is an apparatus according to any one of embodiments 1 to 10, wherein the sidelink logical channel configuration message reconfigures the PC5 QoS flow to SLRB mapping of the apparatus.

[0153] Embodiment 12 is a device according to any one of embodiments 1 to 11, further comprising instructing the RF circuit to send an indication that the device cannot change the carrier set to which the SLRB is mapped via the LCP restriction of the logical channel in the SUI message.

[0154] Embodiment 13 is an apparatus according to any one of embodiments 1 to 12, wherein the configuration for mapping PC5QoS flow to frequency is provided by a V2X layer of the apparatus.

[0155] Embodiment 14 is a device comprising: one or more processors; and a memory storing instructions which, when executed by the one or more processors, cause the device to perform operations comprising: receiving a configuration for mapping a PC5 QoS flow to a frequency from an RF circuit; instructing the RF circuit to send a sidelink logical channel configuration message indicating that sidelink data associated with a logical channel can be mapped to one or more sidelink carriers on a list of allowed sidelink carriers; and receiving the sidelink data associated with the logical channel from the RF circuit via the at least one sidelink carrier based at least in part on mapping the logical channel to at least one sidelink carrier on the list of allowed sidelink carriers according to the configuration for mapping and the sidelink logical channel configuration message.

[0156] Embodiment 15 is an apparatus according to embodiment 14, wherein the operation further includes: receiving an RRC side link reconfiguration message from the RF circuit, the RRC side link reconfiguration message indicating a side link carrier on the list of allowed side link carriers to be added or modified for unicast side link communication, wherein the side link data is received via the side link carrier indicated by the RRC side link reconfiguration message.

[0157] Embodiment 16 is an apparatus according to any one of embodiments 14 to 15, wherein the operation further includes: receiving an RRC side link reconfiguration message from the RF circuit, the RRC side link reconfiguration message indicating a side link carrier to be released from unicast side link communication, wherein receiving the side link data via the at least one side link carrier on the list of allowed side link carriers is at least partially based on the RRC side link reconfiguration message.

[0158] Embodiment 17 is an apparatus according to any one of embodiments 14 to 16, wherein the operation further includes: receiving an RRC side link reconfiguration message from the RF circuit, the RRC side link reconfiguration message indicating one or more PC5 QoS flows to be mapped to a DRB configured for unicast side link communication, wherein the side link data is received using the DRB mapped to the one or more PC5 QoS flows indicated by the RRC side link reconfiguration message.

[0159] Embodiment 18 is an apparatus according to any one of embodiments 14 to 17, wherein the operation further includes: receiving an RRC side link reconfiguration message from the RF circuit, the RRC side link reconfiguration message indicating one or more PC5 QoS flows to be released from a DRB configured for unicast side link communication, wherein receiving the side link data via the at least one side link carrier on the list of allowed side link carriers is at least partially based on the RRC side link reconfiguration message.

[0160] Embodiment 19 is an apparatus according to any one of embodiments 14 to 18, wherein the operation further includes: receiving an RRC side link reconfiguration message from the RF circuit, the RRC side link reconfiguration message including an identifier of the logical channel to which the at least one side link carrier is mapped, wherein receiving the side link data via the at least one side link carrier mapped to the logical channel is at least partially based on the RRC side link reconfiguration message.

[0161] Embodiment 20 is a method comprising: receiving a configuration for mapping a PC5 QoS flow to a frequency; receiving a sidelink logical channel configuration message indicating that sidelink data associated with a logical channel can be mapped to one or more sidelink carriers on a list of allowed sidelink carriers; and sending the sidelink data associated with the logical channel via the at least one sidelink carrier based at least in part on mapping the logical channel to at least one sidelink carrier on the list of allowed sidelink carriers according to the configuration for mapping and the sidelink logical channel configuration message.

[0162] Embodiment 21 includes a non-transitory computer storage medium encoded with instructions that, when executed by one or more processors, cause the one or more processors to perform one or more operations according to any one of Embodiments 1 to 20, or any other method or process described herein.

[0163] Embodiment 22 includes a device comprising logical components, modules and / or circuits (e.g., processing circuits and / or RF circuits) configured to perform one or more operations according to any of Embodiments 1 to 20, or any other method or process described herein.

[0164] Embodiment 23 includes a device comprising one or more processors (e.g., one or more baseband processors) configured to perform one or more operations according to any one of Embodiments 1 to 20, or any other method or process described herein.

[0165] Embodiment 24 includes a system configured to perform one or more operations according to any one of Embodiments 1 to 20, or any other method or process described herein.

[0166] Embodiment 25 includes a device configured to perform one or more operations according to any one of Embodiments 1 to 20, or any other method or process described herein.

[0167] Embodiment 26 includes a UE configured to perform one or more operations according to any one of Embodiments 1 to 20, or any other method or process described herein.

[0168] As described above, one aspect of the present technology may involve collecting and using data that can be obtained from specific and legitimate sources to allow interaction with a second device for data transfer. The present disclosure contemplates that, in some instances, the collected data may include personal information data that uniquely identifies or can be used to identify a specific person. Such personal information data may include demographic data, location-based data, online identifiers, phone numbers, email addresses, home addresses, data or records related to the user's health or fitness level (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other personal information.

[0169] The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit the user. For example, the personal information data can be used to provide a secure data transfer between a first device and a second device. The personal information data can also be used to identify an account associated with the user from a service provider to complete the data transfer.

[0170] The disclosure envisions that entities responsible for collecting, analyzing, disclosing, transmitting, storing or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, it is expected that such entities will implement and consistently apply privacy practices that are generally recognized as meeting or exceeding the industry or government requirements for maintaining user privacy. Such information about the use of personal data should be highlighted and easily accessible to users, and should be updated as the collection and / or use of data changes. The user's personal information should be collected only for legal use. In addition, such collection / sharing should only occur after receiving user consent or other legal grounds specified in applicable laws. Additionally, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data, and ensure that other entities with access to personal information data comply with their privacy policies and procedures. In addition, such entities can subject themselves to third-party assessments to prove that they comply with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted for specific types of personal information data collected and / or accessed, and applied to applicable laws and standards, including considerations that are exclusive to jurisdictions that can be used to impose higher standards. For example, in the US, collection of or access to certain health data may be governed by federal and / or state laws such as the Insurance Portability and Accountability Act (HIPAA), while health data in other countries may be subject to other regulations and policies and should be handled accordingly.

[0171] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates hardware elements and / or software elements to prevent or block access to such personal information data. For example, the technology of the present invention may be configured to allow users to choose to participate in the "opt-in" or "opt-out" of collecting personal information data anytime, anywhere during or after the registration service. For example, a user may "opt-in" or "opt-out" of information associated with a user account stored on a user device and / or shared by a user device. In addition to providing "opt-in" and "opt-out" options, the present disclosure also contemplates providing notifications related to access or use of personal information. For example, a user may notify a user when downloading an application that their personal information data will be accessed, and then remind the user again before the personal information data is accessed by the application. In some instances, a user may be notified when a data transfer is initiated in which a device accesses information associated with a user's account and / or shares information associated with the user's account with another device.

[0172] In addition, it is the intention of the present disclosure that personal information data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Once the data is no longer needed, the risk can be minimized by limiting the collection of data and deleting the data. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be promoted when appropriate by removing identifiers, controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than at the address level), controlling how data is stored (e.g., aggregating data among users), and / or other methods such as differential privacy.

[0173] Thus, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may also be implemented without access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or a portion of such personal information data. For example, content may be selected and delivered to a user based on aggregated non-personal information data or an absolute minimum amount of personal information, such as content processed only on the user's device or other non-personal information that may be used for content delivery services.

Claims

1. A device, comprising: one or more processors; as well as a memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform operations including: receiving, from a radio frequency (RF) circuit, a configuration for mapping a PC5 quality of service (QoS) flow to a frequency; receiving a sidelink logical channel configuration message from the RF circuitry, the sidelink logical channel configuration message indicating that sidelink data associated with a logical channel can be mapped to one or more sidelink carriers on a list of allowed sidelink carriers; as well as and instructing the RF circuitry to send the sidelink data associated with the logical channel via the at least one sidelink carrier based at least in part on mapping the logical channel to at least one sidelink carrier on the list of allowed sidelink carriers in accordance with the configuration for mapping and the sidelink logical channel configuration message.

2. The apparatus according to claim 1, wherein the operation further comprises: instructing the RF circuit to send a radio resource control (RRC) sidelink reconfiguration message based on the sidelink logical channel configuration message, the radio resource control (RRC) sidelink reconfiguration message indicating a sidelink carrier on the list of allowed sidelink carriers to be added or modified for unicast sidelink communication, wherein the sidelink data is sent via the sidelink carrier indicated by the RRC sidelink reconfiguration message.

3. The apparatus according to claim 1, wherein the operation further comprises: The RF circuit is instructed to send a radio resource control (RRC) sidelink reconfiguration message based on the sidelink logical channel configuration message, the radio resource control (RRC) sidelink reconfiguration message indicating a sidelink carrier to be released from unicast sidelink communication, wherein the RF circuit is instructed to send the sidelink data via the at least one sidelink carrier on the list of allowed sidelink carriers is based at least in part on the RRC sidelink reconfiguration message.

4. The apparatus according to claim 1, wherein the operation further comprises: Instructing the RF circuit to send a radio resource control (RRC) sidelink reconfiguration message based on the sidelink logical channel configuration message, the radio resource control (RRC) sidelink reconfiguration message indicating one or more PC5 QoS flows to be mapped to a data radio bearer (DRB) configured for unicast sidelink communication, wherein the sidelink data is sent using the DRB mapped to the one or more PC5 QoS flows indicated by the RRC sidelink reconfiguration message.

5. The apparatus of claim 1, wherein the operations further comprise: Instructing the RF circuitry to send a radio resource control (RRC) sidelink reconfiguration message based on the sidelink logical channel configuration message, the radio resource control (RRC) sidelink reconfiguration message indicating one or more PC5 QoS flows to be released from a data radio bearer (DRB) configured for unicast sidelink communication, wherein instructing the RF circuitry to send the sidelink data via the at least one sidelink carrier on the list of allowed sidelink carriers is based at least in part on the RRC sidelink reconfiguration message.

6. The apparatus of claim 1, wherein the operations further comprise: instructing the RF circuit to send a radio resource control (RRC) sidelink reconfiguration message based on the sidelink logical channel configuration message, the radio resource control (RRC) sidelink reconfiguration message including an identifier of the logical channel to which the at least one sidelink carrier is mapped, wherein instructing the RF circuit to send the sidelink data via the at least one sidelink carrier mapped to the logical channel is based at least in part on the RRC sidelink reconfiguration message.

7. The apparatus of claim 1, wherein a field of the sidelink logical channel configuration message indicates the list of allowed sidelink carriers for the logical channel.

8. The apparatus of claim 1 , further comprising determining, based at least in part on the sidelink logical channel configuration message, that the at least one sidelink carrier is within a frequency subset associated with all PC5 QoS flows allowed to be mapped to the logical channel.

9. The apparatus of claim 1, wherein the sidelink logical channel configuration message indicates that the sidelink data from the logical channel can be mapped to any configured sidelink carrier.

10. The apparatus of claim 1, the operations further comprising, when the apparatus is in a connected state, instructing the RF circuit to send a Side Link User Information (SUI) message to a network entity, the SUI message indicating the mapping between PC5 QoS flows and frequencies.

11. The apparatus of claim 1, wherein the sidelink logical channel configuration message reconfigures a PC5 QoS flow to sidelink radio bearer (SLRB) mapping of the apparatus.

12. According to the device of claim 1, the operation also includes instructing the RF circuit to send an indication that the device cannot change the carrier set mapped side link radio bearer (SLRB) via a logical channel prioritization (LCP) restriction of the logical channel in a side link user information (SUI) message.

13. The apparatus of claim 1, wherein the configuration for mapping PC5 QoS flows to frequencies is provided by a vehicle-to-everything (V2X) layer of the apparatus.

14. A device, comprising: one or more processors; as well as a memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform operations including: receiving, from a radio frequency (RF) circuit, a configuration for mapping a PC5 quality of service (QoS) flow to a frequency; instructing the RF circuit to send a sidelink logical channel configuration message indicating that sidelink data associated with a logical channel can be mapped to one or more sidelink carriers on a list of allowed sidelink carriers; as well as The sidelink data associated with the logical channel is received from the RF circuit via the at least one sidelink carrier based at least in part on mapping the logical channel to at least one sidelink carrier on the list of allowed sidelink carriers in accordance with the configuration for mapping and the sidelink logical channel configuration message.

15. The apparatus of claim 14, wherein the operations further comprise: A radio resource control (RRC) sidelink reconfiguration message is received from the RF circuit, the radio resource control (RRC) sidelink reconfiguration message indicating a sidelink carrier on the list of allowed sidelink carriers to be added or modified for unicast sidelink communications, wherein the sidelink data is received via the sidelink carrier indicated by the RRC sidelink reconfiguration message.

16. The apparatus of claim 14, wherein the operations further comprise: A radio resource control (RRC) sidelink reconfiguration message is received from the RF circuit, the radio resource control (RRC) sidelink reconfiguration message indicating a sidelink carrier to be released from unicast sidelink communications, wherein receiving the sidelink data via the at least one sidelink carrier on the list of allowed sidelink carriers is based at least in part on the RRC sidelink reconfiguration message.

17. The apparatus of claim 14, wherein the operations further comprise: A radio resource control (RRC) sidelink reconfiguration message is received from the RF circuit, the radio resource control (RRC) sidelink reconfiguration message indicating one or more PC5 QoS flows to be mapped to a data radio bearer (DRB) configured for unicast sidelink communication, wherein the sidelink data is received using the DRB mapped to the one or more PC5 QoS flows indicated by the RRC sidelink reconfiguration message.

18. The apparatus of claim 14, wherein the operations further comprise: A radio resource control (RRC) sidelink reconfiguration message is received from the RF circuit, the radio resource control (RRC) sidelink reconfiguration message indicating one or more PC5 QoS flows to be released from a data radio bearer (DRB) configured for unicast sidelink communication, wherein receiving the sidelink data via the at least one sidelink carrier on the list of allowed sidelink carriers is based at least in part on the RRC sidelink reconfiguration message.

19. The apparatus of claim 14, wherein the operations further comprise: A radio resource control (RRC) sidelink reconfiguration message is received from the RF circuit, the radio resource control (RRC) sidelink reconfiguration message including an identifier of the logical channel to which the at least one sidelink carrier is mapped, wherein receiving the sidelink data via the at least one sidelink carrier mapped to the logical channel is based at least in part on the RRC sidelink reconfiguration message.

20. A method comprising: receiving a configuration for mapping PC5 quality of service (QoS) flows to frequencies; receiving a sidelink logical channel configuration message indicating that sidelink data associated with a logical channel can be mapped to one or more sidelink carriers on a list of allowed sidelink carriers; as well as The sidelink data associated with the logical channel is sent via the at least one sidelink carrier based at least in part on mapping the logical channel to at least one sidelink carrier on the list of allowed sidelink carriers in accordance with the configuration for mapping and the sidelink logical channel configuration message.

Images