Systems, methods, and devices for unlicensed sidelink priority to access level mapping

Abstract

The techniques described herein provide a solution for implementing sidelink (SL) unlicensed band or spectrum (SL-U) communications with quality and priority standards. A PC5 Quality of Service (QoS) identifier (PQI) value may be configured and used to indicate QoS associated with SL-U communications (e.g., channels, data streams, etc. Similarly, a Layer 1 (L1) priority indicator may be configured and used to indicate a priority of an SL-U transmission or an SL channel. The PQI and / or L1 priority indicator may be mapped to a channel access priority level (CAPC) value, and the PQI, L1 priority and / or CAPC value may indicate a SL COT sharing, a maximum COT, a timing interval for COT sharing, a listen before talk (LBT) configuration, traffic and channel priority, etc.

Description

Technical Field

[0001] The present disclosure relates to wireless communication networks and mobile device capabilities. Background Art

[0002] Wireless communication networks and wireless communication services are becoming increasingly dynamic, complex, and ubiquitous. For example, some wireless communication networks may be developed to implement fifth generation (5G) or new radio (NR) technology, sixth generation (6G) technology, etc. Such technologies may include solutions for enabling user equipment (UE) to communicate directly with each other. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] The present disclosure will be easily understood and implemented through the specific embodiments and the accompanying drawings. The same figure numerals may designate the same features and structural elements. The accompanying drawings and corresponding descriptions are provided as non-limiting examples of aspects, specific implementations, etc. of the present disclosure, and reference to "one" or "an" aspect, specific implementation, etc. may not necessarily refer to the same aspect, specific implementation, etc., and may mean at least one, one or more, etc.

[0004] Figure 1 is a diagram of an example network according to one or more implementations described herein.

[0005] Figure 2 is a diagram of an example process for determining and using a channel access priority level (CAPC) for an unlicensed side link (SL-U) according to one or more implementations described herein.

[0006] Figure 3 is a diagram of an example of mapping between PC5 Quality of Service (QoS) identifiers (PQIs) and Layer 1 (L1) priorities for a SL-U according to one or more implementations described herein.

[0007] Figure 4 is a diagram of an example of a hybrid approach to L1 priority signaling in Stage 1 SL Control Information (SCI) according to one or more implementations described herein.

[0008] Figure 5 is a diagram of an example for determining CAPC based on L1 priority according to one or more implementations described herein.

[0009] Figure 6 is a diagram of an example for determining CAPC by mapping PQI to 5QI based on QoS characteristics according to one or more implementations described herein.

[0010] Figure 7is a diagram of an example for determining CAPC by mapping PQI to a packet delay budget (PDB) according to one or more implementations described herein.

[0011] Figure 8 is a diagram of an example for determining CAPC by mapping L1 priority to PDB according to one or more implementations described herein.

[0012] Fig. 9 is a diagram of an example for determining a CAPC by mapping an L1 priority to a CAPC according to one or more implementations described herein.

[0013] Fig.10 is a diagram of an example for determining CAPC and maximum channel occupancy time (MCOT) for SL-U COT sharing based on L1 priority according to one or more implementations described herein.

[0014] Fig.11 is a diagram of an example for using CAPC during a SL-U COT sharing scenario according to one or more implementations described herein.

[0015] Fig.12 is a diagram of an example for using L1 priority during a SL-U COT sharing scenario according to one or more implementations described herein.

[0016] Fig.13 is a diagram of an example for using SL-U signals / channels per CAPC according to one or more implementations described herein.

[0017] Fig.14 is a diagram of an example process for determining physical channel priorities for sending SL-U communications according to one or more implementations described herein.

[0018] Fig.15 is a diagram of an example of a physical channel priority process associated with L1 according to one or more implementations described herein.

[0019] Fig.16 is a diagram of an example of a control plane protocol stack according to one or more implementations described herein.

[0020] Fig.17 is a block diagram illustrating components capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein in accordance with one or more specific implementations described herein. DETAILED DESCRIPTION

[0021] The following detailed description refers to the accompanying drawings. The same reference numerals in different drawings may identify the same or similar features, elements, operations, etc. In addition, the present disclosure is not limited to the following description, as other specific implementations may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure.

[0022] A wireless network may include user equipment (UE) capable of communicating with base stations, wireless routers, satellites, and other network nodes. Such devices may operate according to one or more communication standards, such as the 2nd generation (2G) communication standard of the 3rd generation partnership project (3GPP), the 3rd generation (3G) communication standard, the 4th generation (4G) communication standard (e.g., Long Term Evolution (LTE)), and / or the 5th generation (5G) communication standard (e.g., New Radio (NR)). UE may refer to a smart phone, a tablet device, a wearable wireless device, a vehicle capable of wireless communication, and / or another type of device with wireless capabilities.

[0023] UEs may communicate directly with each other using one or more types of communication technologies. Examples of such technologies may include proximity services (ProSe) or device-to-device (D2D) communications, vehicle-to-everything (V2X) communications, sidelink (SL) communications, etc. As described herein, SL communications may include scenarios in which a UE operates to directly discover one or more other UEs, establish connections with the one or more other UEs, and communicate. SL communications using unlicensed wireless spectrum may be referred to as SL-U communications.

[0024] SL-U communication may be performed using one or more wireless resources (e.g., channels, signals, carriers, etc.). These resources may be negotiated between the UEs themselves or may be based on a dynamic grant (DG) or a configured grant (CG) provided by the network to the UE (e.g., scheduled by a base station). Due to the shared nature of the unlicensed spectrum (e.g., shared with various operators, radio access technologies, users), the use of wireless resources in SL-U communication may involve various techniques to resolve channel access conflicts, such as channel occupation time (COT), intervals between signals in COT sharing scenarios, listen before talk (LBT) techniques, etc. However, currently available SL-U technologies fail to provide appropriate solutions for SL-U communication, for example, fail to provide a solution that balances the quality and priority of transmissions on unlicensed wireless resources (e.g., channels, signals, etc.). For example, although the communication standards between the UE and the base station (e.g., Uu interface) may include features such as quality of service (QoS), 5G QoS identifier (5QI), channel access priority level (CAPC), etc., such standards fail to provide solutions for the quality and priority used for SL-U communication.

[0025] The technology described herein provides a solution for implementing SL-U communication with quality and priority requirements. The technology described herein enables the determination and use of a PQI value for SL-U communication, which may generally refer to the QoS associated with the SL-U communication (e.g., channel, data stream, etc.). Similarly, a layer 1 (L1) priority level or indicator may be determined and used to indicate the priority of the SL-U transmission or channel. The PQI and / or L1 priority level may be mapped or otherwise used to determine a CAPC value, and the PQI, L1 priority level and / or CAPC value may be used by the UE to determine the priority for SL-U signals, channels, or other types of communications. In some specific implementations, the PQI, L1 priority and / or CAPC value may also or alternatively be used to determine SL COT sharing, maximum COT (MCOT), timing intervals for COT sharing, LBT processes, data service priorities, etc. Additional features and details of these technologies are described below with reference to the following figures.

[0026] Generally speaking, the PC5 QoS identifier (PQI) is a metric used for sidelink QoS control in the core network and radio components. Standardized PQIs for V2X services and proximity services are available in 3GPP specifications. The Service Data Adaptation Protocol (SDAP) can map the PQI of each stream to different SL radio bearers, which can carry different SL services. L1 priority can be signaled in L1 SL control information (SCI) (e.g., physical (PHY) layer) and can be used as a QoS mapping indicator for CAPC and other features of SL-U communication. For example, L1 priority can facilitate appropriate priority and resource allocation for data services, which can vary from more time-sensitive (e.g., voice calls, streaming video, etc.) to less time-sensitive (e.g., best effort or background services). L1 priority can also be used for physical layer SL communications (e.g., via the PC5 interface between UEs). L1 priority can be used for resource selection, priority preemption, and reassessment. L1 priority can also be used to determine the number of transport block (TB) retransmissions of the CG, the priority of physical SL feedback channel (PSFCH) transmissions, the priority of physical uplink control channel (PUCCH) transmissions carrying SL hybrid automatic repeat request (HARQ) report information, and the priority of SL-U transmissions.

[0027] CAPC may define different levels of transmission based on the priority of transmission for channel access. CAPC levels may be associated with communication conditions or parameters, which may include the maximum number of transmission attempts for the priority level, the minimum contention window size for the priority level, the maximum contention window size for the priority level, the MCOT for the priority level, etc. CAPCs with smaller numbers or values ​​(compared to CAPCs with larger numbers) may enable a UE to have a higher chance of obtaining a specific channel because (for example) the contention window (CW) may have a shorter duration. For example, using CAPC priority 1 is more likely to occupy a specific channel than CAPC priority 3. However, using a CAPC with a smaller number may result in the UE needing to give another UE the opportunity to use the channel after using the channel for a shorter period of time.

[0028] Figure 1 1 is an example network 100 according to one or more implementations described herein. Example network 100 may include UE 110-1, UE 110-2, etc. (collectively referred to as "UE 110" and individually referred to as "UE 110"), a radio access network (RAN) 120, a core network (CN) 130, an application server 140, and an external network 150.

[0029] The systems and devices of the example network 100 may operate in accordance with one or more communication standards, such as the 2nd generation (2G) communication standard of the 3rd Generation Partnership Project (3GPP), the 3rd generation (3G) communication standard, the 4th generation (4G) (e.g., Long Term Evolution (LTE)) communication standard, and / or the 5th generation (5G) (e.g., New Radio (NR)) communication standard. Additionally or alternatively, one or more of the systems and devices of the example network 100 may operate in accordance with other communication standards and protocols discussed herein, including future versions or generations of 3GPP standards (e.g., the 6th generation (6G) standard, the 7th generation (7G) standard, etc.), Institute of Electrical and Electronics Engineers (IEEE) standards (e.g., Wireless Metropolitan Area Network (WMAN), Worldwide Interoperability for Microwave Access (WiMAX), etc.), and more.

[0030] As shown, UE 110 may include a smart phone (e.g., a handheld touch screen mobile computing device that can be connected to one or more wireless communication networks). Additionally or alternatively, UE 110 may include other types of mobile or non-mobile computing devices capable of wireless communication, such as a personal data assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handheld terminal, etc. In some specific implementations, UE 110 may include an Internet of Things (IoT) device (or IoT UE), which may include a network access layer designed for low-power IoT applications that utilize transient UE connections. Additionally or alternatively, IoT UE may utilize one or more types of technologies such as machine-to-machine (M2M) communication or machine-type communication (MTC) (e.g., to exchange data with an MTC server or other device via a public land mobile network (PLMN)), proximity services (ProSe) or device-to-device (D2D) communication, sensor networks, IoT networks, and more. Depending on the scenario, the M2M or MTC exchange of data may be a machine-initiated exchange, and the IoT network may include IoT UEs interconnected with transient connections (which may include uniquely identifiable embedded computing devices within the Internet infrastructure). In some scenarios, the IoT UE may execute background applications (eg, keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0031] UE 110 may communicate and establish a connection with one or more other UEs 110 via one or more wireless channels 112, each of which may include a physical communication interface / layer. The connection may include an M2M connection, an MTC connection, a D2D connection, a SL connection, etc. The connection may involve a PC5 interface. In some specific implementations, UE 110 may be configured to discover each other, negotiate wireless resources between each other, and establish a connection between each other without involving intervention or communication with a RAN node 122 or another type of network node. In some specific implementations, discovery, authentication, resource negotiation, registration, etc. may involve communication with a RAN node 122 or another type of network node.

[0032] UEs 110 may communicate with each other using one or more wireless channels 112. As described herein, UE 110-1 may communicate with RAN node 122 to request SL resources. RAN node 122 may respond to the request by providing a dynamic grant (DG) or a configuration grant (CG) regarding SL resources to UE 110. DG may involve a grant based on a grant request from UE 110. CG may involve a grant of resources without a grant request and may be based on the type of service provided (e.g., a service with strict timing or latency requirements). UE 110 may perform a clear channel assessment (CCA) procedure based on the DG or CG, select SL resources based on the CCA procedure and the DG or CG; and communicate with another UE 110 based on the SL resources. UE 110 may communicate with RAN node 122 using a licensed band and communicate with another UE 110 using an unlicensed band.

[0033] UE 110 may communicate and establish a connection (e.g., communicatively coupled) with RAN 120, which may involve one or more radio channels 114-1 and 114-2, each of which may include a physical communication interface / layer. In some implementations, the UE may be configured with dual connectivity (DC) as a multi-radio access technology (multi-RAT) or multi-radio dual connectivity (MR-DC), where UEs capable of multiple reception and transmission (Rx / Tx) may use resources provided by different network nodes (e.g., 122-1 and 122-2), which may be connected via a non-ideal backhaul (e.g., where one of the network nodes provides NR access and the other network node provides E-UTRA for LTE or NR access for 5G). In such a scenario, one network node may act as a master node (MN) and the other node may act as a secondary node (SN). The MN and the SN may be connected via a network interface, and at least the MN may be connected to CN 130. In addition, at least one of the MN or the SN may operate with shared spectrum channel access, and the functionality specified for the UE 110 may be used for an integrated access and backhaul mobile terminal (IAB-MT). Similar to the UE 110, the IAB-MT may access the network using one network node or using two different nodes with an enhanced dual connectivity (EN-DC) architecture, a new radio dual connectivity (NR-DC) architecture, etc. In some implementations, a base station (as described herein) may be an example of a network node 122.

[0034] As described herein, UE 110 may receive and store one or more configurations, instructions, and / or other information for implementing SL-U communications with quality and priority criteria. A PQI may be determined and used to indicate a QoS associated with a SL-U communication (e.g., a channel, a data stream, etc.). Similarly, an L1 priority value may be determined and used to indicate a priority of a SL-U transmission, a SL-U channel, SL-U data, etc. The PQI and / or L1 priority value may be mapped to a CAPC value, and the PQI, L1 priority, and / or CAPC may indicate a SL channel occupancy time (COT) sharing, a maximum (MCOT), a timing interval for COT sharing, an LBT configuration, traffic and channel priority, etc.

[0035] As shown, UE 110 may also or alternatively be connected to access point (AP) 116 via connection interface 118, which may include an air interface that enables UE 110 to communicatively couple with AP 116. AP 116 may include a wireless local area network (WLAN), a WLAN node, a WLAN termination point, etc. Connection 116 may include a local wireless connection, such as a connection consistent with any IEEE 702.11 protocol, and AP 116 may include a wireless fidelity router or other AP. Figure 1 1, but AP 116 may be connected to another network (e.g., the Internet) without being connected to RAN 120 or CN 130. In some scenarios, UE 110, RAN 120, and AP 116 may be configured to utilize LTE-WLAN aggregation (LWA) technology or LTE WLAN radio level technology integrated with IPsec tunneling (LWIP). LWA may involve UE 110 in RRC_CONNECTED state being configured by RAN 120 to utilize radio resources of LTE and WLAN. LWIP may involve UE 110 using WLAN radio resources (e.g., connection interface 118) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., Internet Protocol (IP) packets) communicated through connection interface 118. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0036] The RAN 120 may include one or more RAN nodes 122-1 and 122-2 (collectively, RAN nodes 122, and individually, RAN nodes 122) that enable establishment of channels 114-1 and 114-2 between the UE 110 and the RAN 120. The RAN node 122 may include a network access point configured to provide a radio baseband function for data and / or voice connections between a user and a network based on one or more of the communication technologies described herein (e.g., 2G, 3G, 4G, 5G, WiFi, etc.). Thus, as an example, the RAN node may be an E-UTRAN Node B (e.g., an enhanced Node B, eNodeB, eNB, 4G base station, etc.), a next generation base station (e.g., a 5G base station, an NR base station, a next generation eNB (gNB), etc.). The RAN node 122 may include a roadside unit (RSU), a transmit receive point (TRxP or TRP), and one or more other types of ground stations (e.g., a ground access point). In some scenarios, the RAN node 122 may be a dedicated physical device such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell, etc. having a smaller coverage area, smaller user capacity, or higher bandwidth than a macrocell.

[0037] Some or all or portions of the RAN nodes 122 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 centralized RAN (CRAN) and / or a virtual baseband unit pool (vBBUP). In these specific implementations, the CRAN or vBBUP may implement a RAN functional split, such as a packet data convergence protocol (PDCP) split, where the radio resource control (RRC) and PDCP layers may be operated by the CRAN / vBBUP, and other layer 2 (L2) protocol entities may be operated by individual RAN nodes 122; a medium access control (MAC) / physical (PHY) layer split, where the RRC, PDCP, radio link control (RLC), and MAC layers may be operated by the CRAN / vBBUP, and the PHY layer may be operated by individual RAN nodes 122; or a "lower PHY" split, where the RRC, PDCP, RLC, MAC layer, and upper portions of the PHY layer may be operated by the CRAN / vBBUP, and the lower portions of the PHY layer may be operated by individual RAN nodes 122. The virtualization framework may allow idle processor cores of the RAN node 122 to perform or execute other virtualized applications.

[0038] In some implementations, the separate RAN nodes 122 may represent separate gNB distributed units (DUs) connected to a gNB control unit (CU) via separate F1 or other interfaces. In such implementations, the gNB-DU may include one or more remote radio heads or radio frequency (RF) front end modules (RFEMs), and the gNB-CU may be operated by a server (not shown) located in the RAN 120 or by a server pool (e.g., a group of servers configured to share resources) in a manner similar to CRAN / vBBUP. Additionally or alternatively, one or more of the RAN nodes 122 may be next generation eNBs (i.e., gNBs) that may provide Evolved Universal Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations to the UE 110 and may be connected to the 5G core network (5GC) 130 via an NG interface.

[0039] Any of the RAN nodes 122 may serve as an endpoint for an air interface protocol and may be a first point of contact for the UE 110. In some implementations, any of the RAN nodes 122 may perform various logical functions of the RAN 120, including but not limited to functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling, and mobility management. The UE 110 may be configured to communicate with each other or any of the RAN nodes 122 over a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication techniques, such as but not limited to OFDMA communication techniques (e.g., for downlink communications) or single carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink (SL) communications), although the scope of such implementations may not be limited in this respect. An OFDM signal may include a plurality of orthogonal subcarriers.

[0040] In some implementations, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 122 to the UE 110, and uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid (e.g., a resource grid or a time-frequency resource grid) that represents the physical resources for the downlink in each time slot. Such a time-frequency plane representation is common for OFDM systems, which makes radio resource allocation intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block may include a set of resource elements (REs); in the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transport several different physical downlink channels.

[0041] In addition, the RAN nodes 122 may be configured to wirelessly communicate with the UE 110 and / or each other over a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed band"), an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed band"), or a combination thereof. For example, the licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, while the unlicensed spectrum may include a 5 GHz band. The licensed spectrum may correspond to channels or frequency bands that are selected, reserved, regulated, etc. for certain types of wireless activities (e.g., wireless telecommunications network activities), while the unlicensed spectrum may correspond to one or more frequency bands that are not restricted for certain types of wireless activities. Whether a particular frequency band corresponds to a licensed medium or an unlicensed medium may depend on one or more factors, such as frequency allocations determined by a public sector organization (e.g., a government agency, a regulatory agency, etc.) or by a private sector organization involved in developing wireless communication standards and protocols, etc.

[0042] To operate in the unlicensed spectrum, the UE 110 and the RAN node 122 may operate using standalone unlicensed operation, license assisted access (LAA), eLAA, and / or feLAA mechanisms. In these implementations, the UE 110 and the RAN node 122 may perform one or more known medium sensing operations or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

[0043] The LAA mechanism can be built on the carrier aggregation (CA) technology of the LTE-Advanced system. In CA, each aggregated carrier is called a component carrier (CC). In some cases, each CC may have a different bandwidth from other CCs. In a time division duplex (TDD) system, the number of CCs and the bandwidth of each CC may be the same for DL ​​and UL. CA also includes individual service cells to provide individual CCs. The coverage of the service cells may be different, for example, because CCs on different frequency bands will experience different path losses. The primary service cell or PCell can provide a primary component carrier (PCC) for both UL and DL, and can handle RRC and non-access stratum (NAS) related activities. Other service cells are called SCells, and each SCell can provide a single secondary component carrier (SCC) for both UL and DL. SCCs can be added and removed as needed, and changing PCCs may require UE 110 to undergo switching. In LAA, eLAA, and feLAA, some or all of the SCells may operate in an unlicensed spectrum (referred to as "LAA SCell"), and the LAA SCell is assisted by the PCell operating in the licensed spectrum. When the UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different physical uplink shared channel (PUSCH) starting positions within the same subframe. To operate in unlicensed spectrum, the UE 110 and the RAN node 122 may also operate using independent unlicensed operation, where the UE may be configured with a PCell in the unlicensed spectrum in addition to any SCells.

[0044] The PDSCH may carry user data and higher layer signaling to the UE 110. A physical downlink control channel (PDCCH) may carry, among other things, information about a transport format and resource allocation associated with the PDSCH channel. The PDCCH may also inform the UE 110 about transport formats, resource allocations, and hybrid automatic repeat request (HARQ) information associated with an uplink shared channel. Typically, downlink scheduling (e.g., allocating control and shared channel resource blocks to the UE 110-2 within the cell) may be performed on any of the RAN nodes 122 based on channel quality information fed back from any of the UEs 110. Downlink resource allocation information may be transmitted on the PDCCH for (e.g., allocated to) each of the UEs 110.

[0045] PDCCH uses control channel elements (CCE) to convey control information, where several CCEs (e.g., 6, etc.) may be composed of resource element groups (REGs), where REGs are defined as physical resource blocks (PRBs) in OFDM symbols. Before being mapped to resource elements, PDCCH complex-valued symbols may first be organized into quaternions, which may then be arranged, for example, using a sub-block interleaver for rate matching. One or more of these CCEs may be used to send each PDCCH, where each CCE may correspond to nine sets of four physical resource elements, referred to as REGs. Four quadrature phase shift keying (QPSK) symbols may be mapped to each REG. Depending on the size of the DCI and channel conditions, one or more CCEs may be used to send the PDCCH. Four or more different PDCCH formats may be defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, 8, or 16).

[0046] Some implementations may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some implementations may utilize an extended (E)-PDCCH that uses PDSCH resources for control information transmission. One or more ECCEs may be used to send EPDCCH. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements, referred to as EREGs. In some cases, an ECCE may have other numbers of EREGs.

[0047] The RAN nodes 122 may be configured to communicate with each other via an interface 123. In a specific implementation where the system is an LTE system, the interface 123 may be an X2 interface. In an NR system, the interface 123 may be an Xn interface. The X2 interface may be defined between two or more RAN nodes 122 (e.g., two or more eNBs / gNBs or a combination thereof) connected to an evolved packet core (EPC) or CN 130, and / or between two eNBs connected to the EPC. In some specific implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user data packets transmitted over the X2 interface, and may be used to convey information about the delivery of user data between eNBs or gNBs. For example, X2-U may provide specific sequence number information about user data transmitted from the master eNB (MeNB) to the secondary eNB (SeNB); information about successful in-sequence delivery of PDCP packet data units (PDUs) from the SeNB to the UE 110 for user data; information about PDCP PDUs that were not delivered to the UE 110; information about the current minimum expected buffer size at the SeNB for sending user data to the UE; etc. X2-C may provide intra-LTE access mobility functions (e.g., including context transfer from the source eNB to the target eNB, user plane transmission control, etc.), load management functions, and inter-cell interference coordination functions.

[0048] As shown, RAN 120 may be connected (e.g., communicatively coupled) to CN 130. CN 130 may include a plurality of network elements 132 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 110) connected to CN 130 via RAN 120. In some implementations, CN 130 may include an evolved packet core (EPC), a 5G CN, and / or one or more additional or alternative types of CNs. The components of CN 130 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some implementations, network function virtualization (NFV) may be used to virtualize any or all of the above-mentioned network node roles or functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 130 may be referred to as a network slice, and a logical instance of a portion of CN 130 may be referred to as a network sub-slice. Network Function Virtualization (NFV) architecture and infrastructure can be used to virtualize one or more network functions onto physical resources including a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system can be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0049] As shown, CN 130, application server 140 and external network 150 may be connected to each other via interfaces 134, 136 and 138, which may include IP network interfaces. Application server 140 may include one or more server devices or network elements (e.g., virtual network functions (VNFs) that provide applications that use IP bearer resources through CM 130 (e.g., Universal Mobile Telecommunications System Packet Service (UMTS PS) domain, LTE PS data service, etc.). Application server 140 may also or alternatively be configured to support one or more communication services (e.g., voice over IP (VoIP sessions, push-to-talk (PTT) sessions, group communication sessions, social networking services, etc.)) of UE 110 via CN 130. Similarly, external network 150 may include one or more of various networks, including the Internet, thereby providing network access to various additional services, information, interconnectivity and other network features to mobile communication networks and UE 110.

[0050] Figure 2 2 is a diagram of an example process 200 for determining and using a CAPC for SL-U communication according to one or more implementations described herein. Process 200 may be implemented by UE 110. In some implementations, some or all of process 200 may be implemented by one or more other systems or devices (including Figure 1 In addition, process 200 may include: Figure 2 One or more fewer, additional, differently ordered, and / or arranged operations than those shown. In some implementations, some or all of the operations of process 200 may be performed independently, sequentially, simultaneously, etc., with one or more of the other operations of process 200. Thus, the techniques described herein are not limited to Figure 2 The number, sequence, arrangement, timing, etc. of the operations or processes depicted in the description. Figures 3 to 13 Detailed Description Figure 2 .

[0051] As shown, process 200 may include determining a PQI and / or L1 priority indicator for SL-U communication with another UE 110 (box 210). For example, UE 110 may determine a PQI and / or L1 priority indicator for SL-U communication with another UE 110. As described below, the PQI and / or L1 priority indicator may be used to map (or determine) a corresponding CPAC. As described herein, the terms "mapping" and the like may refer to determining a type of data, information, value, etc. based on one or more types of data, information, value, etc. that are logically associated therewith (e.g., associated by machine-readable code, logical instructions, data structure association, etc.). In some specific implementations, the PQI for SL-U communication may be determined based on a mapping of QoS characteristics of the SL-U communication and a standardized 5QI for non-SL-U communication to QoS characteristics of a QoS characteristics table.

[0052] The PQI for unlicensed bands may be based on a standardized PQI for V2X and / or ProSe services. The standardized PQI for V2X and / or ProSe services may be designed for D2D communications (as opposed to SL-U communications) using licensed bands. Additionally or alternatively, the standardized PQI (e.g., a default priority) may be based on a priority value (e.g., L1 priority) represented by a 3-bit indicator in the SL-U signal, where "000" indicates priority level "0", "001" indicates priority level "1", and so on. The priority may be mapped to a standardized PQI to QoS system of NR PC5 for V2X or a priority value of a standardized ProSe per-packet priority (PPPP) for LTE PC5, each of which may include a table of relevant parameters such as PQI values, resource types, default priorities, packet delay budgets, packet error rates, default maximum data bursts, default averaging windows, and example service descriptions.

[0053] The QoS corresponding to the standardized PQI may be further mapped to a 5QI of a 5QI to QoS table for non-SL-U communications, and the 5QI may be mapped to a CAPC value. The standardized PQI for V2X and / or ProSe services may correspond to a CAPC value of 1, which may be the highest priority CAPC. In some implementations, the non-standardized PQI value may be configured by a SL service application (e.g., an application for SL-U communications). In some implementations, the PQI may be determined based on a different or additional standardized PQI table for general services (e.g., a standardized 5QI to QoS characteristic mapping table). The standardized 5QI to QoS characteristic mapping table may include parameters, which may include a 5QI value, resource type, default priority, packet delay budget, packet error rate, default maximum data burst, default averaging window, and an example service description.

[0054] The PQI may be mapped to a default L1 priority value. In some implementations, the mapping may be based on the standardized PPPP table for LTE PC5 discussed above (e.g., a standardized 5QI to QoS mapping table). The corresponding value of the L1 priority may be found within the standardized table itself and / or via reference to another table or data structure. For example, the L1 priority indicator may be the value of the default priority level of the corresponding PQI value of the 5QI to QoS mapping table. In some implementations, the non-standardized PQI to L1 priority mapping may be performed based on the SL service application used to create SL-U communications. In such a scenario, the SL service application may map the PQI to the L1 priority based on the QoS characteristics of the non-standardized PQI.

[0055] L1 signaling may include CAPC in L1 SL control information (SCI). Generally speaking, SCI transmission in SL communication may include a transport block with two-stage SCI, including a stage 1 SCI and a stage 2 SCI. The stage 1 SCI may be transmitted via a physical sidelink control channel (PSCCH). The stage 2 SCI and the transport block may share resources of a physical sidelink shared channel (PSSCH). Since the priorities of different services may be determined based on the CAPC priority, which may be signaled in the stage 1 SCI, the stage 1 SCI may not include a 3-bit indicator of the L1 priority for SL-U communication (e.g., where "000" indicates L1 priority "0", "001" indicates L1 priority "1", etc.). In some implementations, for example, if the SL signal synchronization block (S-SSB) for SL-U communication may be transmitted in an unlicensed band, the signaling of the CAPC instead of the L1 priority may be implicitly derived based on the operating band. In some implementations, RRC signaling may be used to indicate whether the L1 SCI is to include a 3-bit priority indicator.

[0056] Figure 3 3 is a diagram of an example 300 for mapping between PQI and L1 priority for SL-U communication according to one or more implementations described herein. As shown, in some implementations, L1 priority can be determined based on PQI. Additionally or alternatively, PQI can be determined based on L1 priority. Types of data, arrangements of data, and values ​​are provided as non-limiting examples of default mappings between PQI and L1 priority. In some implementations, the examples may include additional, alternative, different, or alternatively arranged or associated data.

[0057] Figure 4 4 is a diagram of an example 400 of a hybrid approach to L1 priority signaling in Phase 1 SCI according to one or more implementations described herein. As shown, the Phase 1 SCI may include a 2-bit CAPC indicator that may indicate a maximum COT (COT) and an access priority. When the 2-bit CAPC indicator indicates priority 1 CAPC, an additional 3 bits of the L1 priority may be used to indicate data priority. When the 2-bit CAPC indicator indicates priority 2, 3, or 4 CAPC, the L1 priority bit may be set to indicate priority 7 or 8, which is lower than the standard V2X data priority and the ProSe data priority. The type of data, the arrangement of the data, and the value are provided as non-limiting examples of a hybrid approach to L1 priority signaling in Phase 1 SCI. In some implementations, the examples may include additional, alternative, different, or alternatively arranged or associated data.

[0058] Figure 5 is a diagram of an example 500 for determining CAPC based on L1 priority according to one or more implementations described herein. As shown, L1 priority signaling in Phase 1 SCI may be configured by the network (e.g., base station 122) or the application layer (e.g., SL service application for SL-U communication). In such implementations, CAPC may be determined based on L1 priority. Thus, UE 110 may determine L1 priority based on network or application layer configuration, and may determine CAPC based on L1 priority. The types of data, the arrangement of data, and the values ​​are provided as non-limiting examples of determining CAPC based on L1 priority. In some implementations, the examples may include additional, alternative, different, or alternatively arranged or associated data.

[0059] refer to Figure 2, process 200 may include determining a CAPC for SL-U communication based on the PQI and / or layer 1 priority (block 220). For example, UE 110 may determine a CAPC for SL-U communication based on the PQI and / or layer 1 priority. In some implementations, the CAPC may be used to handle real-time and non-real-time communications (e.g., voice, video, best effort, and background processes, etc.). UE 110 may determine the CAPC by mapping the PQI to the CAPC. Additionally or alternatively, UE 110 may determine the CAPC by mapping the L1 priority to the CAPC. In some implementations, RRC signaling may be used to configure the mapping between the PQI and the CAPC.

[0060] Figure 6 600 is a diagram of an example for determining CAPC by mapping PQI to 5QI based on QoS characteristics according to one or more implementations described herein. In some implementations, UE 110 may determine CAPC based on PQI by mapping PQI to 5QI based on QoS characteristics. Examples of QoS characteristics that can be used to map PQI to 5QI for SL-U purposes may include resource type, packet delay budget, packet error rate, default maximum data burst, default averaging window, and example services, etc. A standardized 5QI table that relates 5QI to CAPC may then be used to determine an appropriate CAPC value for the PQI. The type of data, the arrangement of the data, and the value are provided as non-limiting examples of determining CAPC by mapping PQI to 5QI based on QoS characteristics. In some implementations, the examples may include additional, alternative, different, or alternatively arranged or associated data.

[0061] Figure 71 is a diagram of an example 700 for determining a CAPC by mapping a PQI to a packet delay budget (PDB) according to one or more implementations described herein. As shown, a table or data structure may associate a PQI, a PDB, and a CAPC, and may be used by a UE 110 to determine a CAPC based on a PQI. For example, a PQI of 3 may correspond to a PDB less than or equal to a first time (T1), which in turn may correspond to a CAPC value of 1. A PQI of 4 may correspond to a PDB greater than T1 and less than or equal to a second time (T2), which in turn may correspond to a CAPC value of 2. A PQI of 5 may correspond to a PDB greater than T2, which in turn may correspond to a CAPC value of 3. In some implementations, T1 may be 100 milliseconds (ms) and T2 may be 500 ms. In some implementations, T1 and / or T2 may be configured by RRC signaling. The types of data, the arrangement of data, and the values ​​are provided as non-limiting examples of determining a CAPC by mapping a PQI to a PDB. In some implementations, examples can include additional, alternative, different, or alternatively arranged or associated data.

[0062] Figure 8 1 is a diagram of an example 800 for determining CAPC by mapping L1 priority to PDB according to one or more implementations described herein. As shown, a table or data structure may associate L1 priority, PDB, and CAPC, and may be used by UE 110 to determine CAPC based on L1 priority. For example, L1 priority 1, 2, 3, or 4 may correspond to a PDB less than or equal to a first time (T1), which in turn may correspond to a CAPC value of 1. A PQI of 5, 6, or 7 may correspond to a PDB greater than T1 and less than or equal to a second time (T2), which in turn may correspond to a CAPC value of 2. A PQI of 8 may correspond to a PDB greater than T2, which in turn may correspond to a CAPC value of 3. In some implementations, T1 may be 100 milliseconds (ms) and T2 may be 500 ms. In some implementations, T1 and / or T2 may be configured by RRC signaling. The types of data, the arrangement of data, and the values ​​are provided as non-limiting examples of determining CAPC by mapping L1 priority to PDB. In some implementations, examples can include additional, alternative, different, or alternatively arranged or associated data.

[0063] Fig. 9900 is a diagram of an example for determining CAPC by mapping L1 priority to CAPC according to one or more implementations described herein. For example, RRC signaling may be used to provide a table or data structure that logically associates L1 priority with CAPC value to UE 110. UE 110 may use the table or data structure to determine an appropriate CAPC value based on the L1 priority. For example, as shown, L1 priorities 1, 2, 3, and 4 may correspond to CAPC value 1; L1 priorities 5, 6, and 7 may correspond to CAPC value 2; and L1 priority 8 may correspond to CAPC value 3. CAPC value 4 may be reserved for additional or alternative L1 priority values ​​(X). The types of data, the arrangement of data, and the values ​​are provided as non-limiting examples of determining CAPC by mapping L1 priority to CAPC. In some implementations, the examples may include additional, alternative, different, or alternatively arranged or associated data.

[0064] Fig.10 1 is a diagram of an example 1000 for determining CAPC and MCOT for SL-U COT sharing based on L1 priority according to one or more implementations described herein. For example, UE 110 may use one or more of the 3 bits used to indicate L1 priority to additionally or alternatively determine CAPC and MCOT for SL-U COT sharing. For example, as shown, L1 priorities 1, 2, 3, and 4 may correspond to CAPC values ​​1 and MOC A; L1 priorities 5, 6, and 7 may correspond to CAPC values ​​2 and MOCB; and L1 priority 8 may correspond to CAPC value 3 and MOC C. CAPC values ​​4 and MOC D may be reserved for additional or alternative L1 priority values ​​(X). The types of data, the arrangement of data, and the values ​​are provided as non-limiting examples of determining CAPC and MCOT for SL-U COT sharing based on L1 priority. In some implementations, the examples may include additional, alternative, different, or alternatively arranged or associated data.

[0065] Fig.111 is a diagram of an example 1100 for using CAPC during a SL-U COT sharing scenario according to one or more implementations described herein. As shown, UE 110 may communicate via SL-U COT sharing using the same CAPC or a higher level CAPC. For example, UE 110-1 may obtain a COT (and / or MCOT) based on a determined CAPC value of 2. UE 110-1 may have obtained a COT based on one or more of the L1 priority / CAPC techniques described herein, and UE 110-1 may signal or communicate with UE 110-2 using a CAPC value of 2 (at 11.1). UE 110-2 may receive a communication from UE 110-1 that may indicate a CAPC value of 2, and may respond via SL-U COT sharing using the same or higher CAPC (e.g., CAPC 1 or CAPC 2) (at 11.2).

[0066] Fig.12 1 is a diagram of an example 1200 for using L1 priority during SL-U COT sharing scenarios according to one or more implementations described herein. As shown, UE 110 may communicate via SL-U COT sharing using the same L1 priority or a higher L1 priority. For example, UE 110-1 may obtain a COT (and / or MCOT) based on a determined L1 priority value of 4. UE 110-1 may have obtained a COT based on one or more of the L1 priority / CAPC techniques described herein, and UE 110-1 may signal or communicate with UE 110-2 using the L1 priority value of 4 (at 12.1). UE 110-2 may receive a communication from UE 110-2 that may indicate an L1 priority value of 4, and may respond via SL-U COT sharing using the same or higher L1 priority (e.g., L1 priority 1, 2, 3, or 4) (at 12.2).

[0067] refer to Figure 2, process 200 may include sending SL-U communications based on the CAPC (block 230). For example, UE 110 may transmit SL-U communications based on the CAPC. The CAPC may have been determined based on the PQI and / or L1 priority. Although not shown, process 200 may also or alternatively include: a receiver (Rx) UE 110 receiving SL-U communications transmitted by Tx UE 110. Additionally or alternatively, the SL-U communications may include SL-U COT shared transmissions, and the Rx UE 110 may determine an appropriate CAPC and respond to the Tx UE 110 according to the SL-U COT shared transmission (e.g., after an appropriate interval, within a corresponding MCOT, etc.). In some specific implementations, the manner of transmitting, receiving, and responding to SL-U communications may be based at least in part on corresponding CAPC values ​​and CAPC categories (e.g., S-SSB signals, PSFCH, etc.).

[0068] Fig.13 1300 is a diagram of an example of a SL-U signal / channel per CAPC according to one or more specific implementations described herein. As shown, UE 110 may send an S-SSB signal in Category 2 (CAT-2) or after a LBT. CAT-2 LBT may include a scenario in which UE 110 performs LBT without a random backoff with a fixed length contention window. Additionally or alternatively, UE 110 may use PSFCH for transmission based on whether there is a shared COT and a corresponding interval length. For example, when communicating in a SL-U COT sharing scenario with an interval of less than 16μs, UE 110 may not perform an LBT process before using PSFCH.

[0069] When communicating in a SL-U COT sharing scenario with an interval of 16μs or 25μs (or an interval between 16μs and 25μs), the UE 110 may perform a CAT-2 (e.g., once) LBT procedure before using the PSFCH. When communicating without SL-U COT sharing, the UE 110 may use a priority 1 CAPC and perform a Category 1 (CAT-1) LBT before using the PSFCH. CAT-1 LBT may include a scenario where LBT is not used, so that in some exclusive cases, the UE 110 may be able to perform immediate transmission in an unlicensed band. Additionally or alternatively, the UE 110 may use a physical SL shared channel (PSSCH) and / or a physical SL control channel (PSCCH) for transmission based on a mapping between the QoS of the data to be communicated and the corresponding QoS of the corresponding CAPC. Additionally or alternatively, when UE 110 performs a Type 1 CCA procedure using a particular CAPC level, multiplexing and / or COT sharing on the PSSCH and / or PSCCH may be limited to data streams with higher or equal priority.

[0070] Fig.14 1 is a diagram of an example process 1400 for determining a physical channel priority for sending SL-U communications according to one or more implementations described herein. Process 1400 may be implemented by UE 110. In some implementations, some or all of process 1400 may be implemented by one or more other systems or devices (including Figure 1 In addition, process 1400 may include: Fig.14 The operations shown may be fewer, additional, differently ordered, and / or arranged than those shown. In some implementations, some or all of the operations of process 1400 may be performed independently, sequentially, simultaneously, etc., with one or more of the other operations of process 1400. Thus, the techniques described herein are not limited to Fig.14 The number, sequence, arrangement, timing, etc. of the operations or processes depicted in the .

[0071] As shown, process 1400 may include determining the priority of the current SL-U process (block 1410). For example, UE 110 may determine the priority of the current SL-U process being performed by UE 110. Examples of such processes may include transmitting or responding to an S-SSB signal, using PSFCH to provide feedback to a received SL transmission, or using PSSCH or PSCCH to communicate with another UE 110. UE 110 may determine the priority of the process by determining whether the L1 priority and / or PQI priority for the current SL-U process is known or exists. For example, a signal or message from Tx UE 110 may include L1 priority and / or PQI priority, and Rx UE 110 may determine the priority of responding to the signal or message based on the received L1 priority and / or PQI. Additionally or alternatively, UE 110 may determine the L1 priority and / or PQI priority of the process based on a previous RRC configuration associated with a particular process.

[0072] When L1 priority exists (block 1420 - yes), process 1400 may include applying the L1 priority to the current SL-U process or transmission (block 1430). For example, when the L1 priority is known, UE 110 may perform the current SL-U process according to the L1 priority. In some implementations, this may include performing one or more of the operations, processes, or procedures described herein involving L1 priority or L1 priority values. When L1 priority does not exist (block 1420 - no), process 1400 may include determining whether PQI priority exists (block 1440). For example, when priority does not exist, UE 110 may determine whether PQI priority exists.

[0073] When the PQI is present (block 1440 - yes), process 1400 may include applying the PQI to the current SL-U process or transmission (block 1450). For example, when the PQI for the current SL-U process is known, UE 110 may perform the current SL-U process based on the PQI. In some implementations, this may include performing one or more of the operations, processes, or procedures described herein involving one or more PQI values. When the PQI is not present (block 1440 - no), process 1400 may include applying the lowest L1 priority of the associated process to the current SL-U process or transmission (block 1460). For example, when the PQI for the current SL-U process is unknown, UE 110 may perform the current SL-U process based on the lowest L1 priority of the associated process.

[0074] Fig.151500 is a diagram of an example of a physical channel priority process related to L1 according to one or more specific implementations described herein. As shown, the physical channel priority process 1560 may include mode 2 resource selection 1510 for SL-U, TB retransmission 1520 for CG, multiple PSFCH feedback priorities 1530, and unlicensed PUCCH 1540 with SL HARQ report priority. One or more of the physical channel priority processes 1560 may be performed by UE 110 according to one or more of the techniques described herein. For example, with respect to mode 2 resource selection 1510 for SL-U, UE 110 may perform a type 1 CCA process based on the corresponding CAPC. Additionally or alternatively, when L1 priority exists or is configured, UE 110 may perform resource priority preemption and reassessment according to L1 priority. With respect to TB retransmission 1520 for CG, UE 110 may perform the number of retransmissions specified by the CG. In some implementations, UE 110 may be configured to perform the same number of TB retransmissions for all CGs, regardless of whether the CG specifies the number of TB retransmissions. In some implementations, UE 110 may perform TB retransmissions based on the corresponding CAPC value of each CG. Additionally or alternatively, UE 110 may perform TB retransmissions based on the corresponding L1 priority value of each CG.

[0075] With respect to multiple PSFCH feedback priorities 1530, the UE 110 may provide feedback based on a CAPC value associated with providing feedback (e.g., providing feedback information associated with a higher CAPC may take precedence over providing feedback information associated with a lower CAPC). Additionally or alternatively, the UE 110 may provide feedback based on an L1 priority value associated with providing feedback (e.g., providing feedback data associated with a higher L1 priority may take precedence over providing feedback data associated with a lower L1 priority). With respect to unlicensed PUCCH with SL HARQ report priority 1540, when the PUCCH is in an unlicensed band, the UE 110 may apply equal priority to each SL HARQ report. In some specific implementations, the SL HARQ report may alternatively be provided based on the corresponding CAPC (e.g., providing a SL HARQ report associated with a higher CAPC may take precedence over providing a SL HARQ report associated with a lower CAPC). In some implementations, SL HARQ reports may also or alternatively be provided based on corresponding L1 priority values ​​(eg, providing SL HARQ reports associated with higher L1 priority values ​​may take precedence over providing SL HARQ reports associated with lower L1 priority values).

[0076] Fig.161600 is a diagram of an example of components of a device according to one or more implementations described herein. In some implementations, the device 1600 may include application circuitry 1602, baseband circuitry 1604, RF circuitry 1606, front end module (FEM) circuitry 1608, one or more antennas 1610, and power management circuitry (PMC) 1612 (coupled together at least as shown). The components of the illustrated device 1600 may be included in a UE or a RAN node. In some implementations, the device 1600 may include fewer elements (e.g., the RAN node may not utilize application circuitry 1602, but may include a processor / controller to process IP data received from a CN or an evolved packet core (EPC)). In some implementations, the device 1600 may include additional elements, such as memory / storage, a display, a camera, a sensor (including one or more temperature sensors, such as a single temperature sensor, multiple temperature sensors at different locations in the device 1600, etc.), or an input / output (I / O) interface. In other implementations, the components described below may be included in more than one device (e.g., the circuitry may be separately included in more than one device for a Cloud-RAN (C-RAN) implementation).

[0077] The application circuit 1602 may include one or more application processors. For example, the application circuit 1602 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to or may include a memory / storage device and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the device 1600. In some specific implementations, the processor of the application circuit 1602 may process IP data packets received from the EPC.

[0078] The baseband circuit 1604 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 1604 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuit 1606 and generate baseband signals for the transmit signal path of the RF circuit 1606. The baseband circuit 1604 may interact with the application circuit 1602 to generate and process baseband signals and control the operation of the RF circuit 1606. For example, in some specific implementations, the baseband circuit 1604 may include a 3G baseband processor 1604A, a 4G baseband processor 1604B, a 5G baseband processor 1604C, or other baseband processors 1604D of other existing generations, being developed, or to be developed in the future (e.g., 5G, 6G, etc.). The baseband circuit 1604 (e.g., one or more of the baseband processors 1604A to 1604D) may handle various radio control functions that can communicate with one or more radio networks via the RF circuit 1606. In other implementations, some or all of the functions of the baseband processors 1604A to 1604D may be included in a module stored in the memory 1604G and executed via the central processing unit (CPU) 1604E. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some implementations, the modulation / demodulation circuitry of the baseband circuitry 1604 may include fast Fourier transform (FFT), pre-coding, or constellation mapping / demapping functions. In some implementations, the encoding / decoding circuitry of the baseband circuitry 1604 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples and may include other suitable functions in other aspects.

[0079] In some implementations, memory 1604G may receive and store one or more configurations, instructions, and / or other information for implementing SL-U communications with quality and priority criteria. A PQI may be determined and used to indicate a QoS associated with a SL-U communication (e.g., a channel, a data stream, etc.). Similarly, an L1 priority value may be determined and used to indicate a priority of a SL-U transmission, a SL-U channel, SL-U data, etc. The PQI and / or L1 priority value may be mapped to a CAPC value, and the PQI, L1 priority, and / or CAPC may indicate SL COT sharing, MCOT, a timing interval for COT sharing, a listen-before-talk (LBT) configuration, service and channel priorities, etc.

[0080] In some implementations, the baseband circuitry 1604 may include one or more audio digital signal processors (DSPs) 1604F. The audio DSP 1604F may include elements for compression / decompression and echo cancellation, and in other implementations may include other suitable processing elements. In some implementations, the components of the baseband circuitry may be appropriately combined in a single chip, a single chipset, or disposed on the same circuit board. In some implementations, some or all of the components of the baseband circuitry 1604 and the application circuitry 1602 may be implemented together, for example, on a system on a chip (SOC).

[0081] In some implementations, the baseband circuitry 1604 may provide communications compatible with one or more radio technologies. For example, in some implementations, the baseband circuitry 1604 may support communications with NG-RAN, Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN), etc. Implementations in which the baseband circuitry 1604 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0082] RF circuit 1606 may communicate with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various specific implementations, RF circuit 1606 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 1606 may include a receive signal path, which may include circuits that down-convert RF signals received from FEM circuit 1608 and provide baseband signals to baseband circuit 1604. RF circuit 1606 may also include a transmit signal path, which may include circuits that up-convert baseband signals provided by baseband circuit 1604 and provide RF output signals to FEM circuit 1608 for transmission.

[0083] In some implementations, the receive signal path of the RF circuit 1606 may include a mixer circuit 1606A, an amplifier circuit 1606B, and a filter circuit 1606C. In some implementations, the transmit signal path of the RF circuit 1606 may include a filter circuit 1606C and a mixer circuit 1606A. The RF circuit 1606 may also include a synthesizer circuit 1606D for synthesizing frequencies used by the mixer circuit 1606A of the receive signal path and the transmit signal path. In some implementations, the mixer circuit 1606A of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 1608 based on the synthesized frequency provided by the synthesizer circuit 1606D. Amplifier circuit 1606B may be configured to amplify the down-converted signal, and filter circuit 1606C may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit 1604 for further processing. In some implementations, the output baseband signal may be a zero frequency baseband signal, but this is not required. In some implementations, mixer circuit 1606A of the receive signal path may include a passive mixer, but the scope of the implementation is not limited in this regard.

[0084] In some implementations, the mixer circuit 1606A of the transmit signal path can be configured to up-convert an input baseband signal based on a synthesized frequency provided by the synthesizer circuit 1606D to generate an RF output signal for the FEM circuit 1608. The baseband signal can be provided by the baseband circuit 1604 and can be filtered by the filter circuit 1606C.

[0085] In some implementations, the mixer circuit 1606A of the receive signal path and the mixer circuit 1606A of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some implementations, the mixer circuit 1606A of the receive signal path and the mixer circuit 1606A of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some implementations, the mixer circuit 1606A of the receive signal path and the mixer circuit 1406A may be arranged for direct down-conversion and direct up-conversion, respectively. In some implementations, the mixer circuit 1606A of the receive signal path and the mixer circuit 1606A of the transmit signal path may be configured for superheterodyne operation.

[0086] In some implementations, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the implementation is not limited in this respect. In some alternative implementations, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative implementations, RF circuit 1606 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and baseband circuit 1604 may include a digital baseband interface to communicate with RF circuit 1606.

[0087] In some dual-mode implementations, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the implementations is not limited in this respect.

[0088] In some implementations, synthesizer circuit 1606D can be a fractional-N synthesizer or a fractional N / N+1 synthesizer, but the scope of the implementation is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 1606D can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0089] The synthesizer circuit 1606D can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by the mixer circuit 1606A of the RF circuit 1606. In some implementations, the synthesizer circuit 1606D can be a fractional-N / N+1 synthesizer.

[0090] In some implementations, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by the baseband circuit 1604 or the application circuit 1602 according to the desired output frequency. In some implementations, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuit 1602.

[0091] The synthesizer circuit 1606D of the RF circuit 1606 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some implementations, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some implementations, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry output) to provide a fractional division ratio. In some example implementations, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these implementations, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0092] In some implementations, the synthesizer circuit 1606D can be configured to generate a carrier frequency as an output frequency, while in other implementations, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and can be used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some implementations, the output frequency can be an LO frequency (fLO). In some implementations, the RF circuit 1606 can include an IQ / polarity converter.

[0093] FEM circuitry 1608 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 1610, amplify the receive signals, and provide an amplified version of the receive signals to RF circuitry 1606 for further processing. FEM circuitry 1608 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by RF circuitry 1606 for transmission via one or more of one or more antennas 1610. In various implementations, amplification by the transmit or receive signal path may be accomplished only in RF circuitry 1606, only in FEM circuitry 1608, or in both RF circuitry 1606 and FEM circuitry 1608.

[0094] In some implementations, the FEM circuit 1608 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 1606). The transmit signal path of the FEM circuit 1608 may include a power amplifier (PA) to amplify an input RF signal (e.g., provided by the RF circuit 1606); and one or more filters to generate an RF signal for subsequent transmission (e.g., through one or more of the one or more antennas 1610).

[0095] In some implementations, the PMC 1612 can manage the power provided to the baseband circuit 1604. Specifically, the PMC 1612 can control power selection, voltage scaling, battery charging, or DC-DC conversion. When the device 1600 is capable of being powered by a battery, for example, when the device is included in a UE, the PMC 1612 can generally be included. The PMC 1612 can improve power conversion efficiency while providing the desired implementation size and heat dissipation characteristics.

[0096] Although Fig.16The PMC 1612 is shown coupled only to the baseband circuit 1604. However, in other implementations, the PMC 1612 may be additionally or alternatively coupled to other components (such as, but not limited to, the application circuit 1602, the RF circuit 1606, or the FEM circuit 1608) and perform similar power management operations.

[0097] In some implementations, the PMC 1612 can control or otherwise be part of various power saving mechanisms of the device 1600. For example, if the device 1600 is in the RRC_Connected state, in which the device is still connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the device can enter a state known as discontinuous reception mode (DRX). During this state, the device 1600 can be powered off for short time intervals to save power.

[0098] If there is no data traffic activity for an extended period of time, the device 1600 may transition to the RRC_Idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 1600 enters a very low power state, and it performs paging, in which the device wakes up periodically again to listen to the network, and then powers down again. The device 1600 may not receive data in this state; in order to receive data, the device may transition back to the RRC_Connected state.

[0099] An additional power saving mode can prevent a device from using the network for a period longer than the paging interval (which can range from a few seconds to several hours). During this period, the device cannot connect to the network and can be completely powered down. Any data transmitted during this period will incur significant latency, assuming that latency is acceptable.

[0100] The processor of the application circuit 1602 and the processor of the baseband circuit 1604 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 1604 can be used alone or in combination to perform the functions of layer 3, layer 2, or layer 1, and the processor of the baseband circuit 1604 can utilize data received from these layers (e.g., packet data) and further perform the functions of layer 4 (e.g., transmit communication protocol (TCP) and user datagram protocol (UDP) layer). As mentioned herein, layer 3 may include an RRC layer, which will be described in further detail below. As mentioned herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include a physical (PHY) layer of a UE / RAN node, which will be described in further detail below.

[0101] Fig.17is a block diagram illustrating components that can read instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methods discussed herein, according to some example implementations. Specifically, Fig.17 A schematic diagram of hardware resources 1700 is shown, which includes one or more processors (or processor cores) 1710, one or more memory / storage devices 1720, and one or more communication resources 1730, each of which can be communicatively coupled via a bus 1740.

[0102] Processor 1710 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) (such as a baseband processor), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 1712 and processor 1714.

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

[0104] In some implementations, the memory / storage device 1720 can receive and store one or more configurations, instructions, and / or other information 1755 for implementing SL-U communications with quality and priority criteria. A PQI can be determined and used to indicate a QoS associated with a SL-U communication (e.g., a channel, a data stream, etc.). Similarly, an L1 priority value can be determined and used to indicate a priority of a SL-U transmission, a SL-U channel, SL-U data, etc. The PQI and / or L1 priority value can be mapped to a CAPC value, and the PQI, L1 priority, and / or CAPC can indicate SL COT sharing, MCOT, timing intervals for COT sharing, listen-before-talk (LBT) configuration, service and channel priorities, etc.

[0105] The communication resources 1730 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 1704 or one or more databases 1706 via the network 1708. For example, the communication resources 1730 may include a wired communication component (e.g., for coupling via a universal serial bus (USB)), a cellular communication component, an NFC component, Parts (such as Low power consumption), components and other communication components.

[0106] The instructions 1750 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 1710 to perform any one or more of the methodologies discussed herein. The instructions 1750 may reside in whole or in part in at least one of the processor 1710 (e.g., in a cache memory of the processor), the memory / storage device 1720, or any suitable combination thereof. In addition, any portion of the instructions 1750 may be transmitted to the hardware resources 1700 from any combination of the peripheral device 1704 or the database 1706. Thus, the memory of the processor 1710, the memory / storage device 1720, the peripheral device 1704, and the database 1706 are examples of computer-readable and machine-readable media.

[0107] Embodiments herein may include subject matter, such as a method, components for performing actions or blocks of the method, and at least one machine-readable medium including executable instructions that, when executed by a machine (e.g., a processor with memory, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), cause the machine to perform actions of a method or apparatus or system for concurrent communication using multiple communication technologies according to the described specific implementations and embodiments.

[0108] In embodiment 1, the embodiment may also include one or more embodiments described herein, a user equipment (UE) may include: a memory; and one or more processors, the one or more processors being configured to, when executing instructions stored in the memory, cause the UE to: determine a PC5 quality of service (QoS) identifier (PQI) for unlicensed spectrum side link (SL-U) communication; determine a channel access priority class (CAPC) value based on the PQI for the SL-U communication; and send the SL-U communication based on the CAPC value. In embodiment 2, the embodiment may also include one or more embodiments described herein, the PQI for the SL-U communication is based on a standardized PQI for proximity services (ProSe) for licensed bands.

[0109] In embodiment 3, the embodiment may also include one or more of the embodiments described herein, wherein the PQI used for the SL-U communication is based on a standardized PQI for vehicle-to-everything (V2X) in a licensed band. In embodiment 4, the embodiment may also include one or more of the embodiments described herein, wherein the PQI used for the SL-U communication is based on a layer 1 (L1) priority value. In embodiment 5, the embodiment may also include one or more of the embodiments described herein, wherein the L1 priority value is signaled in a phase 1 side link (SL) control information (SCI).

[0110] In embodiment 6, the embodiment may also include one or more embodiments described herein, determining the CAPC value based on the QoS characteristics of the SL-U communication and the QoS characteristics of the standardized 5QI to QoS characteristics table for the licensed band. In embodiment 7, the embodiment may also include one or more embodiments described herein, determining the CAPC value based on the packet delay budget (PDB) associated with the PQI used for the SL-U communication. In embodiment 8, the embodiment may also include one or more embodiments described herein, the SL-U communication includes a SL signal synchronization block (S-SSB), and the UE will perform a type 2 listen-before-talk (LBT) procedure before sending the SL-U communication.

[0111] In embodiment 9, the embodiment may also include one or more embodiments of the embodiments described herein, wherein the SL-U communication includes physical SL feedback channel (PSFCH) communication and a shared channel occupancy time (COT) with a corresponding interval, and the UE will determine the LBT process based on the interval before sending the SL-U communication. In embodiment 10, the embodiment may also include one or more embodiments of the embodiments described herein, wherein the SL-U communication includes physical SL shared channel (PSSCH) communication or physical SL shared channel (PSCCH) communication, and the UE will use a CAPC level equal to or greater than the CAPC level of the corresponding SL-U communication. In embodiment 11, the embodiment may also include one or more embodiments of the embodiments described herein, wherein the PQI used for the SL-U communication is signaled by the core network or application layer.

[0112] In embodiment 12, the embodiment may also include one or more embodiments of the embodiments described herein, and a method performed by a user equipment (UE) may include: determining a PC5 quality of service (QoS) identifier (PQI) for unlicensed spectrum side link (SL-U) communication; determining a channel access priority level (CAPC) value based on the PQI for the SL-U communication; and sending the SL-U communication based on the CAPC value. In embodiment 13, the embodiment may also include one or more embodiments of the embodiments described herein, a user equipment (UE) may include: a memory; and one or more processors, the one or more processors being configured to, when executing instructions stored in the memory, cause the UE to: determine a layer 1 (L1) priority value for unlicensed spectrum side link (SL-U) communication; determine a channel access priority level (CAPC) value based on the L1 priority value for the SL-U communication; and send the SL-U communication based on the CAPC value.

[0113] In embodiment 14, the embodiment may also include one or more of the embodiments described herein, the L1 priority value is used to determine the CAPC based on a PC5 quality of service (QoS) identifier (PQI) for the SL-U communication. In embodiment 15, the embodiment may also include one or more of the embodiments described herein, providing the L1 priority value for the SL-U communication via phase 1 sidelink (SL) control information (SCI). In embodiment 16, the embodiment may also include one or more of the embodiments described herein, determining the CAPC value based on a 2-bit CAPC indicator in the phase 1 SCI.

[0114] In embodiment 17, the embodiment may also include one or more of the embodiments described herein, wherein the 2-bit CAPC indicator corresponds to a maximum channel occupancy time (MCOT). In embodiment 18, the embodiment may also include one or more of the embodiments described herein, wherein additional 3 bits of the SCI are used to indicate the L1 priority based on the CAPC value of the 2-bit CAPC indicator. In embodiment 19, the embodiment may also include one or more of the embodiments described herein, wherein the CAPC value is determined based on a packet delay budget (PDB) associated with the L1 priority.

[0115] In embodiment 20, the embodiment may also include one or more embodiments described herein, and the CAPC value is determined based on radio resource control (RRC) signaling by mapping the L1 priority to the CAPC value. In embodiment 21, the embodiment may also include one or more embodiments described herein, the SL-U communication corresponds to a shared SLCOT, and SL-U services of the same or higher priority CAPC use the shared SL COT. In embodiment 22, the embodiment may also include one or more embodiments described herein, the SL-U communication corresponds to a shared SL COT, and SL-U services of the same or higher priority L1 use the shared SL COT.

[0116] In embodiment 23, the embodiment may also include one or more embodiments described herein, and the UE will perform a type 1 clear channel assessment (CCA) procedure based on the CAPC. In embodiment 24, the embodiment may also include one or more embodiments described herein, and the number of transport block (TB) retransmissions for the SL-U communication is based on the CAPC value or the L1 priority value. In embodiment 25, the embodiment may also include one or more embodiments described herein, and a physical side link (SL) feedback channel is based on the CAPC value or the L1 priority value.

[0117] In embodiment 26, the embodiment may also include one or more embodiments described herein, and the physical uplink control channel (PUCCH) information carrying SL hybrid automatic repeat request (HARQ) report information is based on the CAPC value or the L1 priority value. In embodiment 27, the embodiment may also include one or more embodiments described herein, and a method performed by a user equipment (UE) may include: determining a layer 1 (L1) priority value for unlicensed spectrum side link (SL-U) communication; determining a channel access priority level (CAPC) value based on the L1 priority value for the SL-U communication; and sending the SL-U communication based on the CAPC value.

[0118] The above description of illustrative examples, implementations, aspects, etc. of the disclosed subject matter, including what is described in the abstract of the specification, is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. Although specific examples, implementations, aspects, etc. are described herein for illustrative purposes, various modifications can be considered within the scope of such examples, implementations, aspects, etc., as can be appreciated by those skilled in the relevant art.

[0119] In this regard, while the subject matter of the present disclosure has been described in conjunction with various examples, implementations, aspects, etc. and corresponding figures, it should be understood that other similar aspects may be used or modifications and additions may be made to the disclosed subject matter, where applicable, for performing the same, similar, alternative or alternative functions of the subject matter without departing from the disclosed subject matter. Therefore, the disclosed subject matter should not be limited to any single example, implementation, or aspect described herein, but should be interpreted in accordance with the breadth and scope of the following claims.

[0120] In particular, with respect to the various functions performed by the above-described components or structures (assemblies, devices, circuits, systems, etc.), unless otherwise specified, the terms used to describe such components (including references to "members") are intended to correspond to any component or structure that performs the specified function of the component (e.g., functionally equivalent), even if not structurally equivalent to the disclosed structure that performs the function in the exemplary implementations illustrated herein. In addition, although particular features have been disclosed with respect to only one of several implementations, for any given application, such features may be combined with one or more other features of other implementations, which may be desirable and advantageous.

[0121] As used herein, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clear from the context, "X employs A or B" is intended to mean any of the natural inclusive arrangements. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied in any of the foregoing cases. In addition, the articles "a" and "an" used in this application and the appended claims should generally be interpreted as meaning "one or more" unless otherwise specified or clear from the context to be directed to the singular form. In addition, to the extent that the terms "including", "comprising", "having", "having", "with", or variations thereof are used in the detailed description or claims, such terms are intended to be included in a manner similar to the term "comprising". In addition, where one or more numbered items (e.g., "first X", "second X", etc.) are discussed, generally, the one or more numbered items may be different or they may be the same, but in some cases, the context may indicate that they are different or that they are the same.

[0122] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and disposed of to minimize the risk of inadvertent or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: Memory; and one or more processors, wherein the one or more processors are configured to, when executing instructions stored in the memory, cause the UE to: Determine the PC5 Quality of Service (QoS) Identifier (PQI) for unlicensed spectrum sidelink (SL-U) communications; determining a channel access priority class (CAPC) value based on the PQI for the SL-U communication; as well as The SL-U communication is sent based on the CAPC value. 2 . The UE of claim 1 , wherein the PQI used for the SL-U communication is based on a standardized PQI for Proximity Services (ProSe) in a licensed band. 3 . The UE of claim 1 , wherein the PQI used for the SL-U communication is based on a standardized PQI for vehicle-to-everything (V2X) in a licensed band. 4 . The UE of claim 1 , wherein the PQI for the SL-U communication is based on a layer 1 (L1) priority value.

5. The UE of claim 4, wherein the L1 priority value is signaled in Phase 1 Sidelink (SL) Control Information (SCI).

6. The UE of claim 1, wherein the CAPC value is determined based on a QoS characteristic of the SL-U communication and a QoS characteristic of a standardized 5QI to QoS characteristic table for a licensed band.

7. The UE of claim 1, wherein the CAPC value is determined based on a packet delay budget (PDB) associated with the PQI for the SL-U communication.

8. The UE of claim 1, wherein the SL-U communication includes a SL signal synchronization block (S-SSB), and the UE is to perform a Type 2 Listen Before Talk (LBT) procedure before sending the SL-U communication.

9. The UE according to claim 1, wherein the SL-U communication includes a physical SL feedback channel (PSFCH) communication and a shared channel occupancy time (COT) with a corresponding interval, and the UE determines the LBT process based on the interval before sending the SL-U communication.

10. The UE of claim 1, wherein the SL-U communication comprises a physical SL shared channel (PSSCH) communication or a physical SL shared channel (PSCCH) communication, and the UE is to use a CAPC level equal to or greater than a CAPC level of the corresponding SL-U communication.

11. The UE of claim 1, wherein the PQI for the SL-U communication is signaled by a core network or an application layer.

12. A method performed by a user equipment (UE), the method comprising: Determine the PC5 Quality of Service (QoS) Identifier (PQI) for unlicensed spectrum sidelink (SL-U) communications; determining a channel access priority class (CAPC) value based on the PQI for the SL-U communication; as well as The SL-U communication is sent based on the CAPC value. 13 . The method of claim 11 , wherein the PQI for the SL-U communication is based on a standardized PQI for Proximity Services (ProSe) in a licensed band.

14. The method of claim 11, wherein the PQI used for the SL-U communication is based on a standardized PQI for vehicle-to-everything (V2X) in a licensed band.

15. The method of claim 11, wherein the PQI for the SL-U communication is based on a layer 1 (L1) priority value.

16. The method of claim 15, wherein the L1 priority value is signaled in Phase 1 Sidelink (SL) Control Information (SCI).

17. The method of claim 11, wherein the CAPC value is determined based on QoS characteristics of the SL-U communication and QoS characteristics of a standardized 5QI to QoS characteristics table for a licensed band.

18. A computer-readable medium, the computer-readable medium comprising: One or more instructions configured to cause one or more processors to: Determine the PC5 Quality of Service (QoS) Identifier (PQI) for unlicensed spectrum sidelink (SL-U) communications; determining a channel access priority class (CAPC) value based on the PQI for the SL-U communication; as well as The SL-U communication is sent based on the CAPC value.

19. The computer-readable medium of claim 18, wherein the PQI for the SL-U communication is based on a standardized PQI for Proximity Services (ProSe) in a licensed band.

20. The computer-readable medium of claim 18, wherein the PQI used for the SL-U communication is based on a standardized PQI for vehicle-to-everything (V2X) in a licensed band.

Images