CN119896014A - Systems, methods, and apparatus for multi-slot, continuous, unlicensed side link transmission - Google Patents

Abstract

Techniques for enabling indication, selection, allocation, and use of Side Link (SL) resources for side link SL communication (SL-U communication) using unlicensed radio spectrum and multiple contiguous time slots. One or more of these techniques may be applicable to scenarios in which SL resources are allocated by a base station and/or scenarios in which SL resources are allocated by a User Equipment (UE). The SL resources may include frequency domain, time domain, number of consecutive time slots, etc., may be selected from a SL-U resource pool, and may be indicated using Downlink Control Information (DCI) and/or side-link control information (SCI). The techniques may include using additional or higher layer parameters such as candidate SL resource slots, subchannels, data priority values, reference Signal Received Power (RSRP), etc. to allocate SL-U resources. The technique may involve scenarios in which the allocated SL resources collide or overlap with a Channel Occupancy Time (COT).

Description

Systems, methods, and apparatus for multi-slot, continuous, unlicensed side link transmission

Technical Field

The present disclosure relates to wireless communication networks and mobile device capabilities.

Background

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) technologies, sixth generation (6G) technologies, and so on. Such techniques may include solutions for enabling User Equipment (UEs) to communicate directly with each other.

Drawings

The present disclosure will be readily understood and effected by the detailed description and the accompanying drawings. Like reference numerals may designate like features and structural elements. The figures and corresponding descriptions are provided as non-limiting examples of aspects, implementations, etc. of the present disclosure, and references to "an" or "one" aspect, implementations, etc. may not necessarily refer to the same aspect, implementation, etc., and may mean at least one, one or more, etc.

FIG. 1 is a diagram of an example overview according to one or more implementations described herein.

FIG. 2 is a diagram of an example network according to one or more implementations described herein.

Fig. 3 is a diagram of an example process for multi-contiguous slot Side Link (SL) communication (SL-U communication) in an unlicensed spectrum in a mode 1 resource allocation scenario, according to one or more implementations described herein.

Fig. 4-5 are diagrams of examples of multi-contiguous slot SL-U communications according to one or more implementations described herein.

Fig. 6 is an illustration of an example process for multi-contiguous slot SL-U communication in a mode 2 resource allocation scenario according to one or more implementations described herein.

Fig. 7-8 are diagrams of examples of transmit times for multi-contiguous slot SL-U communications according to one or more implementations described herein.

Fig. 9 is an illustration of an example process for determining a transmit time for a multi-contiguous slot SL-U communication, according to one or more implementations described herein.

Fig. 10 is a diagram of an example of hybrid automatic repeat request (HARQ) transmission for multi-contiguous slot SL-U communications in accordance with one or more implementations described herein.

Fig. 11-13 are diagrams of examples of allocating resources for multi-contiguous slot SL-U communications with slot collisions according to one or more implementations described herein.

Fig. 14 is an illustration of an example process for allocating or determining SL-U resources for multi-contiguous slot SL-U communications, according to one or more implementations described herein.

Fig. 15-17 are diagrams of examples of Channel Occupancy Time (COT) for multi-contiguous slot SL communication in an unlicensed spectrum according to one or more implementations described herein.

Fig. 18 is a diagram of an example of components of an apparatus according to one or more implementations described herein.

Fig. 19 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 methods discussed herein, according to one or more implementations described herein.

Detailed Description

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

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 in accordance with one or more communication standards, such as a 2 nd generation (2G) communication standard, a3 rd generation (3G) communication standard, a 4 th generation (4G) communication standard (e.g., long Term Evolution (LTE)), and/or a 5 th generation (5G) communication standard (e.g., new Radio (NR)) of the 3 rd generation partnership project (3 GPP). A UE may refer to a smart phone, a tablet computer, a wearable wireless device, a vehicle capable of wireless communication, and/or another type of widely wireless-capable device.

The UEs may communicate directly with each other using one or more types of communication techniques. Examples of such technologies may include proximity services (ProSe) or device-to-device (D2D) communications, vehicle-to-everything (V2X) communications, side Link (SL) communications, and so forth. As described herein, SL communication may include scenarios in which a UE operates to discover, establish a connection with, and communicate directly with one or more other UEs. SL communication using unlicensed-radio spectrum may be referred to as SL-U communication.

SL transmissions may use Time Division Duplexing (TDD) (e.g., half-duplexing) on dedicated or shared carriers along with conventional Uu transmissions between the base station and the UE. A pool of transmission resources (also referred to as a resource pool, SL resource pool, etc.) may be used to manage resource allocation and interference between conflicting transmissions. The resource pool may include a set of time-frequency resources from which resources for SL transmissions may be selected. And the UE may be configured with multiple transmit and receive resource pools.

Additionally, the UE may use different modes of operation for SL resource allocation and communication. And (5) a base station. Mode 1 may be used when the UE is within the coverage area of a base station. In mode 1, scheduling and resource assignment may be performed by the base station (e.g., via DCI) (and may be based on Dynamic Grant (DG) or Configuration Grant (CG)). Mode 2 may be used when the UE is outside the coverage area of the base station. In mode 2, the UE may select SL resources itself (e.g., without a base station). Thus, the UE may use a sensing-based resource allocation, which may include performing a Listen Before Talk (LBT) procedure before selecting SL resources for use and sending SL Control Information (SCI) to other UEs to indicate the use and reservation of the SL resources. In some implementations, the UE may also use a Channel Occupancy Time (COT) to indicate how long certain resources (e.g., channels) are to be used. SCI may be sent via unicast, multicast and/or broadcast and may indicate to the recipient UE which SL resources are scheduled for use. The SCI may indicate reserved SL resources for both a first transmission of a Transport Block (TB) of data and a retransmission of the TB to improve reliability (e.g., if the initial transmission fails).

Currently available techniques for SL communication may be limited to SL-U transmissions involving only one slot. In other words, the UE may not be configured to, for example, select and reserve a plurality of consecutive slots for initial SL-U communications (e.g., SL access procedure). Thus, when an initial SL-U transmission involves, for example, multiple slots, the UE may have to perform multiple LBT procedures to complete the initial transmission. Additionally, currently available techniques may use Time Resource Indicator Values (TRIVs) and Frequency Resource Indicator Values (FRIV) to indicate SL resources. TRIV and FRIV may be communicated by the base station using DCI and/or communicated between UEs via SCI. However, since the currently available technology is designed for single slot SL communication, the current technology cannot achieve indicating and reserving resources for multi-slot SL communication. Furthermore, the currently available techniques fail to address scenarios in which the COT asserted by the UE involves some SL resources that are not within the SL resource pool.

The techniques described herein provide solutions for enabling indication, selection, allocation and use of SL resources for SL-U communications involving multiple consecutive slots. One or more of these techniques may be applicable to scenarios in which SL resources are allocated by a base station and/or scenarios in which SL resources are allocated by a UE (e.g., without base station participation). The SL-U resources may be defined in the frequency domain, the time domain, a plurality of consecutive time slots, etc., may be selected from a pool of SL-U resources, and may be indicated using DCI and/or SCI. One or more of the techniques described herein may additionally or alternatively include using additional or higher layer parameters, such as candidate SL resource slots, subchannels, data priorities, reference Signal Received Power (RSRP), and the like, to allocate SL-U resources. One or more of the techniques described herein may additionally or alternatively relate to a scenario in which one or more time slots of an allocated SL-U resource collide or overlap with a COT.

FIG. 1 is a diagram of an example 100 overview in accordance with one or more implementations described herein. As shown, example 100 may include UE 110-1, UE 110-2, and base station 120. UEs 110-1 and 110-2 may be configured to communicate with each other via multiple consecutive slot SL-U transmissions. As depicted, a multi-contiguous slot SL-U transmission may include two or more unlicensed spectrum SL communications (e.g., initial Tx and re-Tx), where each transmission spans multiple contiguous slots. Each transmission may correspond to a different frequency and the time slots within a transmission may correspond to the same frequency or different frequencies.

When UEs 110-1 and 110-2 are within the coverage area of base station 120, a mode 1 resource allocation approach may be implemented in which SL resources are allocated by base station 120 via DCI. When UEs 110-1 and 110-2 are not within the coverage area of base station 120, a mode 2 resource allocation approach may be implemented in which SL resources are allocated by UEs 110-1 and 110-2. The multi-contiguous slot SL-U resources may be determined based on the number of contiguous slots per transmission, the SL-U resource pool, the resource selection window, RSRP measurements, whether the expected resource slots have been reserved, data priority, etc. UEs 110-1 and 110-2 may use SCI to inform each other about the reservation of SL resources and to determine timing and other aspects of certain transmissions. Multiple consecutive slot SL-U transmissions may be used to transmit a single TB or multiple TBs, and a SL hybrid automatic repeat request (HARQ) procedure, retransmission, and SL HARQ reporting to base station 120 may also be enabled for multiple consecutive slot SL-U transmissions. Examples and details of these and other features are described below with reference to the following figures.

Fig. 2 is an example network 200 in accordance with one or more implementations described herein. Example network 200 may include UEs 210-1, UEs 210-2, etc. (collectively referred to as "UEs 210" and individually referred to as "UEs 210"), a Radio Access Network (RAN) 220, a Core Network (CN) 230, an application server 240, and an external network 250.

The systems and devices of the example network 200 may operate in accordance with one or more communication standards, such as the 3 rd generation partnership project (3 GPP) 2 nd generation (2G), 3 rd generation (3G), 4 th generation (4G) (e.g., long Term Evolution (LTE)) and/or 5 th generation (5G) (e.g., new Radio (NR)) communication standards. Additionally or alternatively, one or more of the systems and devices of the example network 200 may operate in accordance with other communication standards and protocols discussed herein, including future versions or generations of 3GPP standards (e.g., sixth generation (6G) standards, seventh generation (7G) standards, etc.), institute of Electrical and Electronics Engineers (IEEE) standards (e.g., wireless Metropolitan Area Network (WMAN), worldwide Interoperability for Microwave Access (WiMAX), etc.), and so forth.

As shown, the UE 210 may include a smart phone (e.g., a handheld touch screen mobile computing device capable of connecting to one or more wireless communication networks). Additionally or alternatively, the UE 210 may include other types of mobile or non-mobile computing devices capable of wireless communication, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handheld telephones, and the like. In some implementations, the UE 210 may include an internet of things (IoT) device (or IoT UE) that may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. Additionally or alternatively, the IoT UEs 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 MTC servers or other devices via a Public Land Mobile Network (PLMN)), proximity services (ProSe) or device-to-device (D2D) communication, sensor networks, ioT networks, and so forth. 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 (which may include uniquely identifiable embedded computing devices within the internet infrastructure) interconnected with a transient connection. In some scenarios, ioT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connection of IoT networks.

The UE 210 may communicate with and establish a connection with one or more other UEs 210 via one or more wireless channels 212, 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 implementations, the UEs 210 may be configured to discover each other, negotiate radio resources between each other, and establish connections between each other without intervention or communication involving the RAN node 222 or another type of network node. In some implementations, discovery, authentication, resource negotiation, registration, etc. may involve communication with RAN node 222 or another type of network node.

The UEs 210 may communicate with each other using one or more wireless channels 212. As described herein, UE 210-1 may communicate with RAN node 222 to request SL resources. The RAN node 222 may respond to the request by providing a Dynamic Grant (DG) or a Configuration Grant (CG) for SL resources to the UE 210. DG may relate to authorization based on an authorization request from UE 210. CG may involve resource authorization without an authorization request and may be based on the type of service provided (e.g., services with strict timing or latency requirements). The UE 210 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 210 based on the SL resources. The UE 210 may communicate with the RAN node 222 using a licensed frequency band and with another UE 210 using an unlicensed frequency band.

UE 210 may communicate with and establish a connection (e.g., communicatively couple) with RAN 220, which may involve one or more wireless channels 214-1 and 214-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 multi-receive and transmit (Rx/Tx) capable UEs may use resources provided by different network nodes (e.g., 222-1 and 222-2) that may connect via non-ideal backhaul (e.g., where one network node provides NR access and another 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 another node may act as a Secondary Node (SN). The MN and SN may be connected via a network interface, and at least the MN may be connected to the CN 230. Additionally, at least one of the MN or SN can operate over shared spectrum channel access and functions specified for the UE 210 can be utilized for integrated access and backhaul mobile terminals (IAB-MTs). Similar to the UE 210, the iab-MT may access the network using one network node or using two different nodes with an enhanced dual connectivity (EN-DC) architecture or a new radio dual connectivity (NR-DC) architecture, etc. In some implementations, a base station (as described herein) may be an example of network node 222.

As described herein, UE 210 and/or base station 222 may transmit, receive, process, and/or store one or more configurations, instructions, and/or other types of information (e.g., multi-contiguous slot SL-U Tx information) to enable selection, indication, allocation, and use of SL resources for SL-U communications involving multiple contiguous slots. SL resources may be allocated by the base station and/or the UE (e.g., without base station involvement). The SL resources may include a frequency domain, a time domain, a plurality of consecutive time slots, etc., may be selected from a SL resource pool, and may be indicated using DCI and/or SCI. Allocating SL resources may include using additional or higher layer parameters such as candidate SL resource slots, subchannels, data priority values, RSRP, etc. Additionally, in scenarios where the allocated SL resources collide or overlap with COTs, the use of SL resources and/or COTs for SL-U communications may be modified.

As shown, the UE 210 may additionally or alternatively connect to an Access Point (AP) 216 via a connection interface 218, which may include an air interface that enables the UE 210 to communicatively couple with the AP 216. The AP 216 may include a Wireless Local Area Network (WLAN), a WLAN node, a WLAN endpoint, and the like. Connection 216 may comprise a local wireless connection, such as a connection consistent with any IEEE 702.11 protocol, and AP 216 may comprise wireless fidelityA router or other AP. Although not explicitly depicted in fig. 2, the AP 216 may be connected to another network (e.g., the internet) without being connected to the RAN 220 or the CN 230. In some scenarios, UE 210, RAN 220, and AP 216 may be configured to utilize LTE-WLAN aggregation (LWA) technology or LTE/WLAN radio level technology integrated with IPsec tunneling (LWIP). LWA may involve configuring, by the RAN 220, the UE 210 in an rrc_connected state to utilize radio resources of LTE and WLAN. LWIP may involve UE 210 using WLAN radio resources (e.g., connection interface 218) to authenticate and encrypt packets (e.g., internet Protocol (IP) packets) communicated via connection interface 218 via IPsec protocol tunneling. IPsec tunneling may involve encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

RAN 220 may include one or more RAN nodes 222-1 and 222-2 (which are collectively referred to as RAN nodes 222 and individually referred to as RAN nodes 222) that enable establishment of channels 214-1 and 214-2 between UE 210 and RAN 220. The RAN node 222 may comprise a network access point configured to provide radio baseband functionality for data and/or voice connectivity between a user and a network based on one or more of the communication techniques 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., enhanced node B, eNodeB, eNB, 4G base station, etc.), a next generation base station (e.g., 5G base station, NR base station, next generation eNB (gNB), etc.). The RAN node 222 may include a roadside unit (RSU), a transmitting-receiving point (TRxP or TRP), and one or more other types of ground stations (e.g., ground access points). In some scenarios, the RAN node 222 may be a dedicated physical device such as a macrocell base station and/or a Low Power (LP) base station for providing femtocells, picocells, etc. with smaller coverage areas, smaller user capacities, or higher bandwidths than macrocells.

Some or all of RAN nodes 222, or portions thereof, 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 pool of virtual baseband units (vBBUP). In these implementations, CRAN or vBBUP may implement RAN functionality splits, such as Packet Data Convergence Protocol (PDCP) splits, where Radio Resource Control (RRC) and PDCP layers may be operated by CRAN/vBBUP and other layer 2 (L2) protocol entities may be operated by separate RAN nodes 222, medium Access Control (MAC)/Physical (PHY) layer splits, where RRC, PDCP, radio Link Control (RLC) and MAC layers may be operated by CRAN/vBBUP and PHY layers may be operated by separate RAN nodes 222, or "lower PHY" splits, where RRC, PDCP, RLC, MAC layers and upper portions of PHY layers may be operated by CRAN/vBBUP and lower portions of PHY layers may be operated by separate RAN nodes 222. The virtualization framework may allow idle processor cores of RAN node 222 to make or execute other virtualized applications.

In some implementations, the individual RAN node 222 may represent an individual gNB Distributed Unit (DU) connected to a gNB Control Unit (CU) via an individual F1 or other interface. In such implementations, the gNB-DU may include one or more remote radio heads or Radio Frequency (RF) front end modules (RFEM), and the gNB-CU may operate in a similar manner as CRAN/vBBUP by a server (not shown) located in the RAN 220 or by a server pool (e.g., a set of servers configured to share resources). Additionally or alternatively, one or more of the RAN nodes 222 may be a next generation eNB (i.e., a gNB) that may provide evolved universal terrestrial radio access (E-UTRA) user plane and control plane protocol termination to the UE 210 and may connect to a 5G core network (5 GC) 230 through an NG interface.

Any of the RAN nodes 222 may be the end point of the air interface protocol and may be the first point of contact for the UE 210. In some implementations, any of the RAN nodes 222 may perform various logical functions of the RAN 220 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. UE 210 may be configured to communicate with each other or any of RAN nodes 222 over a multicarrier communication channel using Orthogonal Frequency Division Multiplexing (OFDM) communication signals in accordance with 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 Side Link (SL) communications), although the scope of such implementations is not limited in this respect. The OFDM signal may comprise a plurality of orthogonal subcarriers.

In some implementations, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 222 to the UE 210, 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 of the downlink in each time slot. For OFDM systems, such time-frequency plane representation is common practice, which makes radio resource allocation intuitive. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in the radio frame. The smallest time-frequency unit in the resource grid is denoted as a resource element. Each resource grid includes resource blocks that describe the mapping of certain physical channels to resource elements. Each resource block may include a set of Resource Elements (REs), which may represent a minimum amount of resources currently allocable in the frequency domain. Such resource blocks are used to convey a number of different physical downlink channels.

Further, the RAN node 222 may be configured to wirelessly communicate with the UE 210 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 about 400MHz to about 3.8GHz, while the unlicensed band or spectrum may include the 5GHz band. In additional or alternative examples, the unlicensed spectrum may include a 5GHz unlicensed band, a 6GHz band, a 60GHz millimeter wave band, and so on.

The licensed spectrum may correspond to channels or bands selected, reserved, adjusted, etc., for certain types of wireless activity (e.g., wireless telecommunications network activity), while the unlicensed spectrum may correspond to one or more bands that are not restricted for certain types of wireless activity. 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., government agency, regulatory agency, etc.), or frequency allocations determined by a private sector organization involved in developing wireless communication standards and protocols, or the like.

To operate in unlicensed spectrum, UE 210 and RAN node 222 may operate using independent unlicensed operation, licensed Assisted Access (LAA), eLAA, and/or feLAA mechanisms. In these implementations, the UE 210 and the RAN node 222 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 transmission in the unlicensed spectrum. The medium/carrier sensing operation may be performed according to a Listen Before Talk (LBT) protocol.

LAA mechanisms may be built on Carrier Aggregation (CA) technology of LTE-Advanced systems. In CA, each aggregated carrier is referred to as a Component Carrier (CC). In some cases, each CC may have a different bandwidth than 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. The CA also includes individual serving cells to provide individual CCs. The coverage of the serving cell may be different, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell or PCell may provide Primary Component Carriers (PCC) for both UL and DL and handle RRC and non-access stratum (NAS) related activities. Other serving cells are referred to as scells, and each SCell may provide a single Secondary Component Carrier (SCC) for both UL and DL. SCCs may be added and removed as needed, while changing PCC may require UE 210 to undergo handover. In LAA, eLAA, and feLAA, some or all of the scells may operate in unlicensed spectrum (referred to as "LAA SCell"), and the LAA SCell is assisted by a PCell operating in licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive a UL grant on the configured LAA SCell indicating a different Physical Uplink Shared Channel (PUSCH) starting location within the same subframe. To operate in the unlicensed spectrum, the UE 210 and the RAN node 222 may also operate using independent unlicensed operation, where the UE may be configured with PCell in addition to any scells in the unlicensed spectrum.

PDSCH may carry user data and higher layer signaling to UE 210. The Physical Downlink Control Channel (PDCCH) may carry information on a transport format and resource allocation related to the PDSCH channel, etc. The PDCCH may also inform the UE 210 about transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel. In general, downlink scheduling (assignment of control and shared channel resource blocks to UEs 210-2 within a cell) may be performed on any one of the RAN nodes 222 based on channel quality information fed back from any one of the UEs 210. The downlink resource allocation information may be sent on a PDCCH for (e.g., assigned to) each of the UEs 210.

The PDCCH conveys control information using Control Channel Elements (CCEs), 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 an OFDM symbol. The PDCCH complex-valued symbols may first be organized into quadruples before being mapped to resource elements, which may then be arranged for rate matching, e.g., using a sub-block interleaver. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements, respectively, 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 the channel conditions, the PDCCH may be transmitted using one or more CCEs. There may be four or more different PDCCH formats with different numbers of CCEs (e.g., aggregation level, l=1, 2, 4, 8, or 16) defined in LTE.

Some implementations may use concepts for resource allocation for control channel information, which concepts are extensions of the concepts described above. 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 transmit the EPDCCH. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements, respectively, referred to as EREGs. In some cases, ECCEs may have other amounts of EREGs.

RAN nodes 222 may be configured to communicate with each other via interface 223. In implementations where the system is an LTE system, the interface 223 may be an X2 interface. In an NR system, the interface 223 may be an Xn interface. In some implementations, such as a Standalone (SA) implementation, the interface 223 may be an Xn interface. In some implementations, such as a non-standalone (NSA) implementation, interface 223 may represent an X2 interface and an XN interface. The X2 interface may be defined between two or more RAN nodes 222 (e.g., two or more enbs/gnbs or a combination thereof) connected to an Evolved Packet Core (EPC) or CN 230, or between two enbs connected to the EPC. In some 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 transferred over the X2 interface and may be used to convey information regarding the delivery of user data between enbs or gnbs. For example, X2-U may provide specific sequence number information regarding user data transferred from a master eNB (MeNB) to a secondary eNB (SeNB), information regarding successful in-sequence delivery of PDCP Packet Data Units (PDUs) from the SeNB to the UE 210 for the user data, information of PDCP PDUs not delivered to the UE 210, information regarding a current minimum expected buffer size at the SeNB for transmitting user data to the UE, and so forth. X2-C may provide LTE access mobility functionality (e.g., including context transfer from source eNB to target eNB, user plane transmission control, etc.), load management functionality, and inter-cell interference coordination functionality.

As shown, the RAN 220 may be connected (e.g., communicatively coupled) to the CN 230. The CN 230 may include a plurality of network elements 232 configured to provide various data and telecommunications services to clients/subscribers (e.g., users of the UE 210) connected to the CN 230 via the RAN 220. In some implementations, the CN 230 may include an Evolved Packet Core (EPC), a 5G CN, and/or one or more additional or alternative types of CNs. The components of the CN 230 may be implemented in one physical node or in a separate physical node, 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-described network node roles or functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). The logical instance of CN 230 may be referred to as a network slice, and the logical instance of a portion of CN 230 may be referred to as a network sub-slice. Network Function Virtualization (NFV) architecture and infrastructure may be used to virtualize one or more network functions onto physical resources including industry standard server hardware, storage hardware, or a combination of switches (alternatively performed by proprietary hardware). In other words, NFV systems may be used to perform virtual or reconfigurable implementations of one or more EPC components/functions.

As shown, CN 230, application server 240, and external network 250 may be connected to each other via interfaces 234, 236, and 238, which may include IP network interfaces. The application server 240 may include one or more server devices or network elements (e.g., virtual Network Functions (VNFs)) that provide applications (e.g., universal mobile telecommunications system packet service (UMTS PS) domain, LTE-PS data services, etc.) that use IP bearer resources with the CM 230. The application server 240 may additionally or alternatively be configured to support one or more communication services of the UE 210 (e.g., voice over IP (VoIP session, push-to-talk (PTT) session, group communication session, social networking service, etc.) via the CN 230. Similarly, the external network 250 may include one or more of a variety of networks, including the internet, thereby providing network access to a variety of additional services, information, interconnectivity, and other network features for the mobile communication network and the UE 210.

Fig. 3 is an illustration of an example process 300 for multi-contiguous slot SL-U communication in a mode 1 resource allocation scenario according to one or more implementations described herein. Process 300 may be implemented by UE 210-1, UE 210-2, and base station 222. In some implementations, some or all of process 300 may be performed by one or more other systems or devices (including one or more of the devices of fig. 2). Additionally, process 300 may include one or more fewer, additional, differently ordered and/or arranged operations than those shown in fig. 3, including other processes and/or operations discussed herein. For example, process 300 may include operations preceding, performed in parallel with, and/or following one or more of the depicted operations. Further, some or all of the operations of process 300 may be performed independently, serially, simultaneously, etc., with respect to one or more of the other operations of process 300. Thus, the techniques described herein are not limited to the number, order, arrangement, timing, etc. of operations or processes depicted in fig. 3. A description of the process 300 is provided below with periodic reference to fig. 4-5.

As shown, process 300 may include base station 222 determining SL-U resources for a plurality of consecutive time slots (block 310). Examples of SL-U resources for multiple consecutive slots may include frequency resources, time resources, channel information, subchannel information, the number of consecutive slots per SL communication, and so forth. Base station 222 may determine SL-U resources in conjunction with a Dynamic Grant (DG) scenario or a Configuration Grant (CG) scenario. The SL-U resources may include a particular set of SL-U resources that the UE 210-1 will use for SL-U communications or a SL-U resource pool from which the UE 210-1 may select for SL-U communications. Additionally or alternatively, the base station 222 may determine the SL-U resources based on one or more conditions, parameters, or factors, such as a preconfigured SL-U resource pool stored in a local memory or storage device of the base station 222, data priority corresponding to the SL communication, UE capability information, etc.

Process 300 may include communicating SL-U resources having a plurality of consecutive time slots to UE 210-1 (block 320). For example, base station 222 may communicate DCI to UE 210-1 via a PDCCH. The DCI may include one or more TRIVs, FRIVs, and may be provided as DCI format 3_0 information. In some scenarios, a single TRIV and FRIV pair may be provided for the entire multi-slot transmission. In some scenarios, TRIV and FRIV pairs may be provided per slot of a multi-slot transmission. In yet other scenarios, a TRIV and FRIV pair may be provided for a first slot of a multi-slot transmission and a frequency offset may be provided for each subsequent slot of the multi-slot transmission.

As shown, the base station 222 may also communicate SL-U resource information to one or more other UEs 210, such as UE 210-2. In such implementations, other UEs 210 may use the SL-U resource information to perform one or more of the operations depicted in fig. 3 as being performed by UE 210-1. In such a scenario, a UE in communication with UE 210-2 may in turn perform one or more of the operations depicted in fig. 3 as being performed by UE 210-2.

Process 300 may include selecting a SL-U resource having a plurality of consecutive slots (block 330). For example, the UE 210-2 may select SL-U resources having multiple consecutive slots. UE 210-1 may do so based on SL-U resource information received from base station 222. In some implementations, selecting SL-U resources may include UE 210-2 using a particular set of SL-U resources indicated by base station 222. Selecting the SL-U resources may additionally or alternatively include UE 210-2 selecting a particular set of SL-U resources from a pool of SL-U resources indicated by base station 222. The resources selected by the UE 210-1 may be part of a DG or CG scenario. In some implementations, when a SL-U resource having multiple consecutive slots is based on quality of service (QoS) or priority of data to be transmitted, UE 210 may select a SL-U resource having multiple consecutive slots (as opposed to a SL-U resource of one slot at a time). In such a scenario, all data to be transmitted in a multi-slot continuous transmission may have the same QoS or data priority, e.g., to simplify the resource selection procedure.

Fig. 4-5 are diagrams of examples 400 and 500 of multi-contiguous slot SL-U communications according to one or more implementations described herein. As shown in fig. 4, the multi-contiguous slot SL communication may include an initial set of contiguous Tx slots and a subsequent set of contiguous Tx slots (e.g., a set of retransmission (Re-Tx) slots). The number of consecutive slots (a) may be the same for each set of consecutive slots. The maximum number of timeslots that can be applied in a multi-contiguous timeslot transmission may be preconfigured per resource pool. Additionally, a value of 1 may be supported or implemented (e.g., by default) when multiple consecutive slot transmissions are not applied or indicated.

In example 400, A is equal to 3, however, in other implementations, A may be another number greater or less than 3. Similarly, while example 500 includes two consecutive sets of Tx slots, another number of sets with consecutive Tx slots may be implemented. The initial set of consecutive Tx slots and the subsequent set of consecutive Tx slots may share the same base sequence or pattern (e.g., multiple consecutive Tx slots using the same frequency), but belong to different frequencies, channels, and/or sub-channels. In some implementations, the initial set of consecutive Tx slots and the subsequent set of consecutive Tx slots may be separated in the time domain by a gap, which may be equal to one slot or another number of designated slots.

As shown in fig. 5, the consecutive slot SL communication may include an initial set of consecutive Tx slots and a subsequent set of consecutive Tx slots (e.g., a retransmission (Re-Tx) slot set). The number of consecutive slots (a) may be the same for each set of consecutive slots. In example 500, A is equal to 3, however, in other implementations, A may be another number greater or less than 3. Similarly, while example 500 includes two consecutive sets of Tx slots, another number of sets with consecutive Tx slots may be implemented.

The time slots within each set of consecutive Tx time slots may correspond to different frequencies or sub-channels that may collectively form a total frequency pattern for the set of consecutive Tx time slots. Additionally, each set of consecutive Tx slots may include the same number of slots with a corresponding frequency pattern, however, the frequency pattern of one set of consecutive Tx slots may be offset from the frequency pattern of another set of consecutive Tx slots. In some implementations, the initial set of consecutive Tx slots and the subsequent set of consecutive Tx slots may be separated in the time domain by a gap, which may be equal to one slot or another number of designated slots. Thus, one or more of the techniques described herein may be applied to a set of consecutive Tx slots that may vary in terms of mode, number of consecutive slots, frequency mode, and number of consecutive Tx slot sets.

Referring to fig. 3, process 300 may include UE 210-1 indicating to UE 210-2 a SL-U resource having a plurality of consecutive slots (block 340). In some implementations, the UE 210-1 may provide this information via a Physical SL Control Channel (PSCCH) carrying the SCI (e.g., a first stage SCI). The SCI may indicate one or more TRIVs, FRIVs, the number of slots per SL-U transmission set, frequency offset of slots within SL-U transmissions, frequency offset between SL-U transmissions, time or slot gaps between SL-U transmission sets, the number of SL-U transmissions (e.g., initial transmission plus one or more possible retransmissions), COT, etc. In some scenarios, an indication of a single TRIV and FRIV pair may be sent for an entire multislot. In some scenarios, each slot, which may be transmitted in multiple slots, indicates a TRIV and FRIV pair. In yet other scenarios, the first slot of the multi-slot transmission may be indicative of a TRIV and FRIV pair, and a frequency offset may be provided for each subsequent slot of the multi-slot transmission.

The process 300 may also include the UE 210-1 providing data to the UE 210-2 using SL-U resources having a plurality of consecutive slots (block 340). The UE 210-1 may do so via a Physical SL Shared Channel (PSSCH) during the corresponding COT. In some implementations, each successive slot of the SL-U transmission may be used for a single TB. In other implementations, consecutive slots of a SL-U transmission may be used for different TB. As shown, the process 300 may include the UE 210-2 providing HARQ feedback to the UE 210-1 via a Physical SL Feedback Channel (PSFCH) (block 350) and the UE 210-1 responding to one or more retransmissions of data using SL-U resources having multiple consecutive slots (block 360). Additionally or alternatively, the process 300 may include the UE 210-1 generating a SL-HARQ report for SL-U communication between the UE 210-1 and the UE 210-2 and providing the SL-HARQ report to the base station 222 via the PUCCH (block 370).

Fig. 6 is an illustration of an example process 600 for multi-contiguous slot SL-U communication in a mode 2 resource allocation scenario according to one or more implementations described herein. Process 600 may be implemented by UE 210-1 and UE 210-2. In some implementations, some or all of process 600 may be performed by one or more other systems or devices (including one or more of the devices of fig. 2). Additionally, process 600 may include one or more fewer, additional, differently ordered and/or arranged operations than those shown in fig. 6, including other processes and/or operations discussed herein. For example, process 600 may include operations preceding, performed in parallel with, and/or following one or more of the depicted operations. Further, some or all of the operations of process 600 may be performed independently, serially, simultaneously, etc., with respect to one or more of the other operations of process 600. Thus, the techniques described herein are not limited to the number, order, arrangement, timing, etc. of operations or processes depicted in fig. 6.

As shown, process 600 may include UE 210-1 determining and selecting SL-U resources for a plurality of consecutive slots (block 610). Examples of SL-U resources for multiple consecutive slots may include frequency resources, time resources, channel information, subchannel information, the number of consecutive slots per SL communication, the number of SL-U transmissions (e.g., initial transmission and one or more retransmissions), and so forth. UE 210-1 may determine the SL-U resources based on a pool of resources designated for SL-U communications. Additionally or alternatively, the UE 210-1 may determine the SL-U resources based on one or more parameters, conditions, or procedures, such as Reference Signal Received Power (RSRP) measurements, COT, data priority, qoS requirements, LBT procedures, UE capability information, and the like.

Process 600 may include UE 210-1 indicating SL-U resources having a plurality of consecutive slots to UE 210-2 (block 620). In some implementations, the UE 210-1 may provide this information via the PSCCH carrying the SCI. The SCI may comprise a level 1 SCI. The SCI may indicate one or more TRIVs, FRIVs, the number of slots per SL-U transmission set, frequency offset of slots within SL-U transmissions, frequency offset between SL-U transmissions, time or slot gaps between SL-U transmission sets, the number of SL-U transmissions (e.g., initial transmission plus one or more possible retransmissions), COT, etc. In some scenarios, an indication of a single TRIV and FRIV pair may be sent for an entire multislot. In some scenarios, each slot, which may be transmitted in multiple slots, indicates a TRIV and FRIV pair. In yet other scenarios, the first slot of the multi-slot transmission may be indicative of a TRIV and FRIV pair, and a frequency offset may be provided for each subsequent slot of the multi-slot transmission. Additional examples of information that UE 210-1 may provide to UE 210-2 to facilitate multi-contiguous slot SL communication may be discussed with reference to one or more other examples provided herein.

Process 600 may also include UE 210-1 providing data to UE 210-2 using SL-U resources having a plurality of consecutive slots (block 630). The UE 210-1 may do so via a Physical SL Shared Channel (PSSCH) during the corresponding COT. In some implementations, each successive slot of the SL-U transmission may be used for a single TB. In other implementations, consecutive slots of a SL-U transmission may be used for different TB. As shown, process 600 may include UE 210-2 providing HARQ feedback to UE 210-1 via a Physical SL Feedback Channel (PSFCH) (block 640) and UE 210-1 responding to one or more retransmissions of data using SL-U resources having multiple consecutive slots (block 650). Additionally or alternatively, process 300 may include UE 210-1 generating a SL-HARQ report for SL-U communication between UE 210-1 and UE 210-2 and providing the SL-HARQ report to base station 222 via a PUCCH.

Fig. 7-8 are diagrams of examples 700 and 800 of transmit times for multi-contiguous slot SL-U communications according to one or more implementations described herein. As shown, example 700 represents frequency along the vertical axis and time along the horizontal axis. Example 700 also depicts several multi-contiguous slot SL-U communications for an initial Tx and two retransmissions (retransmission Tx 1 and retransmission Tx 2). Each SL-U communication includes two time slots (a=2) at different times and frequencies, including an initial Tx time slot set, re Tx set. As shown, re-Tx 1 begins after a first amount of time (T ₁) and Re-Tx 2 begins after a second amount of time (T ₂), where T ₁ and T ₂ are measured from the first time slot of the initial Tx to the first time slot of the corresponding Tx. In contrast, as shown in example 800, T ₁ and T ₂ may alternatively be measured according to another time (such as from the last time slot of the initial Tx to the first time slot of the corresponding Tx). T ₁ and T ₂ may be measured in terms of the number of time slots.

In some implementations, the base station 222 and/or the UE 210 may calculate or determine a transmission time (e.g., T ₁、T₂, etc.) to enable multi-contiguous slot SL-U communications. For example, base station 222 and/or UE 210 may determine a maximum number (N) of time slots that may be reserved (per reservation) for SL-U communications. N may be the maximum number of transmissions (e.g., initial transmission plus retransmission) that may be reserved for a TB. N may be determined based on locally stored or (pre) configured data and/or communication standards. N may be a value corresponding to the sl-MaxNumPerReserve Information Element (IE) and/or another parameter. Additionally, N may be used to determine the transmit times of multi-contiguous slot SL-U transmissions (e.g., re-Tx 1 and re-Tx 2).

For example, referring to fig. 7, when n=3, the time (e.g., T ₁) between the initial Tx and the first subsequent Tx (e.g., re-Tx 1) may be represented as [ a,32-2*A ], and the time (e.g., T ₂) between the initial Tx and the second subsequent Tx (e.g., re-Tx 2) may be represented as [ T ₁ +a,32-a ].32 may be constants defined by locally stored configuration data. The value of a may be the maximum number of time slots for a single transmission (e.g., initial Tx or re-Tx) and may be defined by locally stored configuration data. Alternatively, the value of a may be the actual number of timeslots transmitted, which may be indicated in the SCI (e.g., level 1 SCI). In a similar example, but n=2, the time (e.g., T ₁) between the initial Tx and the subsequent Tx (e.g., re-Tx) may be denoted as [ a,32-a ].

For example, referring to fig. 8, when n=3, the time (e.g., T ₁) between the initial Tx and the first subsequent Tx (e.g., re-Tx 1) may be represented as [1,32-2*A ], and the time (e.g., T ₂) between the initial Tx and the second subsequent Tx (e.g., re-Tx 2) may be represented as [ T ₁ +a,32-a ].1 may illustrate the time measured from the last slot of the initial Tx. 32 may be constants defined by locally stored configuration data. The value of a may be the maximum number of time slots for a single transmission (e.g., initial Tx or re-Tx) and may be defined by locally stored configuration data. Alternatively, the value of a may be the actual number of timeslots transmitted, which may be indicated in the SCI (e.g., level 1 SCI). In a similar example, but n=2, the time (e.g., T ₁) between the initial Tx and the subsequent Tx (e.g., re-Tx) may be denoted as [1,32-a ]. The base station 222 and/or the UE 210 may use the transmit time (e.g., T ₁、T₂, etc.) to determine the TRIV value for the multi-contiguous slot SL-U communication.

Fig. 9 is an illustration of an example process 900 for determining a Time Resource Indicator Value (TRIV) for a multi-contiguous slot SL-U communication in accordance with one or more implementations described herein. The process 900 may be implemented by the UE 210 and may be applicable to a mode 1 resource selection scenario or a mode 2 resource selection scenario. In some implementations, some or all of process 900 may be performed by one or more other systems or devices (including one or more of the devices of fig. 2). Additionally, process 900 may include one or more fewer, additional, differently ordered and/or arranged operations than those shown in fig. 9, including other processes and/or operations discussed herein. Further, some or all of the operations of process 900 may be performed independently, serially, simultaneously, etc., with respect to one or more of the other operations of process 900. Thus, the techniques described herein are not limited to the number, order, arrangement, timing, etc. of operations or processes depicted in fig. 9.

As shown, process 900 may include determining a maximum number of slots for multi-contiguous slot SL-U communications (block 910). For example, the UE 210 may determine a maximum number of slots (e.g., a) for multi-contiguous slot SL-U communications based on a pre-configured or locally stored SL-U resource pool. The SL-U resource pool may include channels, sub-channels, frequencies, times, etc., including one or more combinations thereof, for SL-U communications.

Process 900 may also include receiving a SCI including a number of slots for multi-contiguous slot SL-U communications (block 920). For example, the UE 210 may receive an SCI (e.g., a level 1 SCI) from another UE 210. The SCI may be a level 2 SCI. UE 210 may determine a transmission time or TRIV for an initial transmission (e.g., an initial Tx), a number of transmissions (e.g., N) for TB or multi-contiguous slot SL-U communications, and/or one or more other types of information based on the SCI.

Process 900 may include determining a transmit time for a multi-contiguous slot SL-U communication (block 930). For example, the UE 210 may determine a transmission time for one or more transmissions of a multi-contiguous slot SL-U communication. As described above, for example, the UE 210 may determine the time difference, range, or number of time slots (e.g., T ₁、T₂, etc.) between the initial Tx and the subsequent Tx (re-Tx 1, re-Tx 2, etc.). In some implementations, the time difference, range, or number of time slots may be measured from the first time slot of the initial Tx or the last time slot of the initial Tx. Additionally, the UE 210 may do so based on one or more parameters, such as a maximum number of consecutive slots per transmission, a number of transmissions, a time of a first or last slot of an initial transmission, and so forth. Thus, one or more of the techniques described herein may enable UE 210 to determine a transmission time or slot for multiple SL-U transmissions based on a preconfigured maximum number of consecutive slots per Tx and corresponding SCI.

Fig. 10 is a diagram of an example of hybrid automatic repeat request (HARQ) transmission for multi-contiguous slot SL-U communications in accordance with one or more implementations described herein. As shown, example 1000 represents frequency along the vertical axis and time along the horizontal axis. Example 1000 also includes several signal and information features that may correspond to information transmitted and received by UE 210, which may correspond to a mode 1 resource allocation scenario. Additionally, the placement, size, orientation, and/or relative positioning of one or more features of example 1000 are provided as non-limiting examples intended to convey concepts of one or more of the techniques described herein.

As shown, the UE 210 may receive DCI format 3_0 information from the base station 222 regarding SL-U communications with one or more other UEs 210. Based on the DCI, information and instructions stored locally by the UE 210, and/or one or more procedures performed by the UE 210 (e.g., LBT procedure), the UE 210 may select SL-U resources for multi-contiguous slot SL-U communications. Depending on the selected resources, the UE 210 may communicate an initial SL transmission comprising two consecutive slots via the PSSCH.

The DCI format 3_0 information received from the base station 222 may also include or specify SL HARQ reporting resources, which may include a frequency domain, a time domain, a plurality of consecutive slots, a plurality of repetitions, etc. for receiving SL HARQ feedback. UE 210 may communicate information describing some or all of the SL HARQ reporting resources via the PSCCH and/or SCI. The UE 210 may receive SL-U feedback information (e.g., SL HARQ information) via PSFCH, and based on the SL-U feedback information, the UE 210 may retransmit some or all of the initial transmissions according to the selected resources. Similar to the initial transmission, the retransmission may involve two consecutive slots of the PSSCH. And in turn, UE 210 may receive SL-U feedback information (e.g., HARQ information) via PSFCH related to the retransmission. As shown, the UE 210 may receive SL HARQ information via PSFCH in a resource whose pattern coincides with a plurality of consecutive slots of the first transmission.

In some implementations, DCI format 3_0 information received from base station 222 may include instructions and/or information regarding providing SL-HARQ reports to base station 222. In some implementations, some or all of these instructions may be included in the PSFCH to HARQ feedback timing indicator field of DCI format 3_0. This information may specify time, time slots, and/or other resources for communicating the SL-HARQ report to the base station 222. In some implementations, the timing information or indicator may be based on PSFCH events or occasions, such as the last PSCCH/PSSCH resource of the last slot of a multi-contiguous slot SL-U communication. For example, as depicted, DCI format 3_0 information may cause UE 210 to provide a SL-HARQ report to base station 222 upon expiration of a HARQ feedback timing indicator from PSFCH of last PSFCH resource measurements associated with multi-contiguous slot SL-U communications.

Fig. 11-13 are diagrams of examples 1100, 1200, and 1300 of allocating resources for multi-contiguous slot SL-U communications with slot collisions according to one or more implementations described herein. Examples 1100, 1200, and 1300 represent frequency along the vertical axis and time along the horizontal axis, as well as various multi-contiguous time slot transmissions (e.g., initial Tx, re-Tx 1, and re-Tx 2). As shown, the SL-U resources used for multi-contiguous slot transmission may overlap or otherwise collide with resources (e.g., slots) that are not within the preconfigured SL-U resource pool. In a resource pool configuration, a bitmap may be used to indicate which time resources (e.g., slots) are within the resource pool. Some of the slots, such as slots designated for SL system synchronization block (S-SSB) transmission or slots otherwise reserved, may be outside of the resource pool. Thus, during a resource selection or allocation process, base station 222 and/or UE 210 may determine whether the selection of SL-U resources for multi-contiguous slot transmission conflicts with an assigned or reserved slot. For example, base station 222 and/or UE 210 may use the bitmap to determine whether a set of slots to be allocated for SL-U communications is indicated as contiguous in a corresponding slot bitmap. And in the event that a collision is detected (e.g., the bitmap indicates that the selected slots are not in fact contiguous), the base station 222 and/or the UE 210 may determine whether and/or how to count a number of contiguous slots on slots that are not in the resource pool.

In some scenarios, the base station 222 and/or the UE 210 may allocate SL resources such that the set of multiple consecutive time slots continues after the conflicting time slots outside of the resource pool. In some implementations, the duration of the conflicting time slots outside of the resource pool can be factored into (e.g., as part of) the total multislot duration. In other words, the collision slots may be counted as one of the consecutive slots by a specified number of consecutive slots. For example, as shown in FIG. 12, the initial Tx, re-Tx 1 and re-Tx 2 may each include two consecutive SL-U slots, even if one slot of re-Tx 1 collides with a reserved slot.

In other scenarios, the base station 222 and/or the UE 210 may allocate SL resources such that the duration of the time slots outside of the resource pool may not be accounted for in the total multislot duration. In such implementations, additional slots may be added before and/or after the reserved slots, thereby maintaining the total number of consecutive slots (e.g., a) without counting the reserved slots. For example, as shown in FIG. 13, while the initial Tx and re-Tx 2 may each include two consecutive SL-U slots, re-Tx 1 collides with a slot that is not in the resource pool. Thus, additional slots may be added after the reserved slots such that re-Tx 1 includes the same number of resource pool slots as the initial Tx and re-Tx 2.

In yet other scenarios, the base station 222 and/or the UE 210 may allocate SL resources such that multiple slots per transmission may be stopped or interrupted at reserved slots outside of the resource pool. For example, as shown in FIG. 13, while the initial Tx and re-Tx 2 may each include two consecutive SL-U slots, re-Tx1 collides with a slot that is not in the resource pool. Thus, the time slot allocated to re-Tx1 may stop after the first time slot of re-Tx 1. In some implementations, slots determined to be conflicting or outside the resource pool may be limited to S-SSBs or other reserved slots for SL transmissions only. Additionally or alternatively, one or more of examples 1100, 1200, and 1300 may apply depending on whether a single TB is transmitted in a multi-slot continuous transmission or multiple TBs are transmitted in a multi-slot continuous transmission. For example, when a single TB is transmitted, base station 222 and/or UE 210 may apply example 1200, while when multiple TBs are transmitted in a multi-contiguous slot SL transmission, the base station and/or UE may apply example 1100. Thus, in determining that the multiple contiguous time slot selection and allocation conflicts with reserved time slots or includes time slots that are not within the SL resource pool, the base station 222 and/or the UE 210 may be configured to determine one or more qualities, conditions, or characteristics related to the multiple contiguous time slot SL transmissions and apply the SL resource allocation policy associated with those qualities, conditions, or characteristics.

Fig. 14 is an illustration of an example process 1400 for allocating or determining SL-U resources for multi-contiguous slot SL-U communications in accordance with one or more implementations described herein. Process 1400 may be implemented by UE 210 and may be applicable to a mode 2 resource selection scenario. In some implementations, some or all of process 1400 may be performed by one or more other systems or devices (including one or more of the devices of fig. 2). Additionally, process 1400 may include one or more fewer, additional, differently ordered and/or arranged operations than those shown in fig. 14, including other processes and/or operations discussed herein. Further, some or all of the operations of process 1400 may be performed independently, serially, simultaneously, etc., with respect to one or more of the other operations of process 1400. Thus, the techniques described herein are not limited to the number, order, arrangement, timing, etc. of operations depicted in fig. 14.

As shown, process 1400 may include determining candidate a-slot resources and resource selection windows for a multi-contiguous slot SL-U transmission (R _x,y) (block 1410). For example, UE 210 may receive higher layer signaling indicating SL resource selection involving the indicated number (a) of consecutive slots ("a-slot" or "a-slot resources") and subchannels (L _subCH) in each slot. A priority value or QoS may also be indicated. When multiple timeslots are used to transmit different TBs with different data priorities, then the priority (prio _TX) applied to the transmission of multiple consecutive timeslots SL-U is the lowest of these data priorities (the lower priority value indicating the higher actual data priority).

The UE 210 may determine candidate a-slot resources for a multi-contiguous slot SL-U transmission (R _x,y). Here, x may be a subchannel index (e.g., a frequency resource index), and y may be a slot index (e.g., a time resource index). The multi-contiguous slot SL-U transmission (R _x,y) may be defined or determined as a set of contiguous subchannels (L _subCH), where subchannel x+j is in slot t ^′ _y+k; where j=0, & gt, L _subCH -1;k =0, & gt, a-1. The UE 210 may also determine a resource selection window, which may be defined as an interval [ n+t ₁,n+T₂ ], where n may be the time (or slot index) when the resource selection procedure is triggered, and n+t ₁ may be the beginning slot of the resource selection window, and n+t ₂ may be the ending slot of the resource selection window. The total number of candidate slots (a) may be denoted as M _total.

Process 1400 may include determining a sensing window (block 1420). For example, UE 410 may determine a sensing window for evaluating candidate resources (e.g., slots and subchannels) for a multi-contiguous slot SL-U transmission (R _x,y). The sensing window may be defined or represented as an interval n-T ₀,n-T_proc0].T₀ may be the sensing window size, and T _proc0 may be the processing time of the sensing result. Process 1400 may include UE 210 determining or obtaining an RSRP threshold (block 1430). In some implementations, the UE 210 may determine the RSRP threshold based on locally stored configuration data and/or the RSRP threshold may be a default threshold. In some implementations, the UE 210 may additionally or alternatively determine the RSRP threshold based on higher layer signaling. In some implementations, the RSRP threshold may be based on a QoS or priority value associated with data to be transmitted by the UE 210. In such implementations, the RSRP threshold may be greater for data associated with higher priority or QoS. The RSRP threshold may additionally or alternatively be determined based on one or more other types of information, such as signal-to-noise ratio (SNR), block error rate (BLER), etc. As described below, the RSRP threshold may include an RSRP value or level that may be used to estimate a collision or contention slot reservation (e.g., a single slot reservation from other UEs 210).

Process 1400 may include setting the initial candidate set (S _A) to all candidate a-slot resources of the candidate a-slot resources in the resource selection window (block 1440). For example, the UE 210 may determine or define a theoretical maximum of a-slot resources in a resource selection window for multi-contiguous slot SL-U transmissions. The theoretical maximum of a-slot resources may be referred to as an initial candidate set (S _A).

Process 1400 may include excluding candidate a-slot resources that overlap with the unmonitored slot (block 1450). For example, the UE 210 may analyze the initial candidate set (S _A) to determine whether any of the candidate a-slot resources of the initial candidate set (S _A) overlap with slots that the UE 210 has not monitored with the supported periodic extensions. For example, assume that the resource pool supports a resource reservation periodicity of 50 ms. If UE 210-1 does not monitor the SL channel at slot 0 (i.e., UE 210-1 does not decode the SCI transmitted at slot 0), then UE 210-1 may not know whether the resources in slots 50, 100, 150,. This is because it is possible for UE 210-2 to transmit in slot 0 and to reserve resources in slots 50, 100, 150, etc. If, for example, slots 50, 100, and 150 are within the resource selection window of UE 210-1, then UE 210-1 may not select the resources of slots 50, 100, and 150 because UE 210-1 does not monitor slot 0. When the UE 210 determines that the candidate a-slot resources overlap with the unmonitored slots, the UE 210 may remove the candidate a-slot resources from the initial candidate set (S _A).

Process 1400 may include excluding candidate a-slot resources that overlap with any single-slot resources reserved by other UEs 210 with RSRP and priority values that meet a certain threshold (block 1460). For example, the UE 210 may analyze the initial candidate set (S _A) to determine whether any of the remaining candidate a-slot resources of the initial candidate set (S _A) overlap with the single-slot resources reserved by another UE 210. Upon detecting such a scenario, the UE 210 may determine an RSRP and a priority value associated with another UE 210 and/or a single slot reservation, and may compare the RSRP and priority value to certain criteria. For example, the UE 210 may compare the RSRP to the RSRP threshold discussed above. As another example, the UE 210 may compare the priority value with the priority value of the upcoming multi-contiguous slot SL-U transmission. In another example, the UE 210 may compare the priority value to a preconfigured priority value threshold for single slot reservation. When the UE 210 determines that the RSRP and priority values meet certain criteria, the UE 210 may remove candidate a-slot resources that overlap with the single-slot reservation. Otherwise, the UE 210 may leave the candidate a slot resources within the initial candidate set (S _A).

Process 1400 may include determining whether the initial candidate set (S _A) is less than X M _total (block 1470). Here, X may be 20%, 30%, or 50% in a single slot SL transmission scenario, and may be different in a multiple consecutive slot SL transmission scenario. For example, the UE 210 may determine whether the candidate a slot resources remaining in the initial candidate set (S _A) are less than a threshold defined by x×m _total. When the initial candidate set (S _A) is not less than X M _total, the process 1400 may proceed by the UE 210 increasing the RSRP threshold by a preconfigured amount (block 1480) and returning to setting the initial candidate set (S _A) as all of the candidate a-slot resources in the resource selection window (block 1440). When the initial candidate set (S _A) is not less than X M _total, the procedure 1400 may proceed by the UE 210 reporting to higher layer procedures and signaling candidate a slot resources remaining in the initial candidate set (S _A). Doing so may, for example, enable UE 210 to allocate SL-U resources suitable for performing multi-contiguous slot SL-U communications.

Fig. 15-17 are diagrams of examples 1500, 1600, and 1700 of COT for multi-contiguous slot SL communication in unlicensed spectrum according to one or more implementations described herein. Examples 1500, 1600, and 1700 represent frequency along the vertical axis and time along the horizontal axis, as well as overall COT spanning time slots outside the SL-U resource pool.

As described herein, a bitmap may be used to indicate which time resources (e.g., slots) are within a resource pool for SL-U communications. Some of the slots (such as slots designated for S-SSB transmissions or slots otherwise reserved) may be outside of the resource pool. Thus, during a resource selection or allocation process, base station 222 and/or UE 210 may determine whether the selection of SL-U resources for multi-contiguous slot transmission conflicts with an assigned or reserved slot. For example, base station 222 and/or UE 210 may use the bitmap to determine whether a set of slots to be allocated for SL-U communications is indicated as contiguous in a corresponding slot bitmap. And in the event that a collision is detected (e.g., the bitmap indicates that the selected slots are not in fact contiguous), the base station 222 and/or the UE 210 may apply the corresponding COTs in one or more ways.

As shown in examples 1500 and 1600, in some implementations, the COT spanning the slots outside of the SL-U resource pool may begin before and continue or resume after the slots. As shown in fig. 15, in some implementations, the duration of the COT may be consistent with the original, default, or typical duration of the COT. That is, the collision slots may not affect the overall or total COT duration, or may be factored into the overall or total COT duration. In contrast, and as depicted in fig. 16, the overall or total COT duration may be modified (e.g., extended) based on time slots outside of the resource pool of resources corresponding to the COT. That is, slots outside of the reference pool may effectively extend the overall or total DOT duration based on the number of slots outside of the reference pool. In other implementations, the COT may be shortened or terminated in time slots outside of the resource pool corresponding to the resources of the overall or total COT. As shown in example 1700 of fig. 1, the initial COT may not extend beyond the intervening set of time slots outside of the given resource pool.

Fig. 18 is a diagram of an example of components of an apparatus according to one or more implementations described herein. In some implementations, the device 1800 may include application circuitry 1802, baseband circuitry 1804, RF circuitry 1806, front-end module (FEM) circuitry 1808, one or more antennas 1810, and Power Management Circuitry (PMC) 1812 coupled together at least as shown. The illustrated components of device 1800 may be included in a UE or RAN node. In some implementations, the device 1800 may include fewer elements (e.g., the RAN node may not utilize the application circuit 1802, but rather include a processor/controller to process IP data received from a CN or Evolved Packet Core (EPC)). In some implementations, the device 1800 may include additional elements such as memory/storage, a display, a camera, sensors (including one or more temperature sensors, such as a single temperature sensor, multiple temperature sensors at different locations in the device 1800, etc.), or input/output (I/O) interfaces. In other implementations, the components described below may be included in more than one device (e.g., the circuitry may be included separately in more than one device for cloud-RAN (C-RAN) implementations).

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

The baseband circuitry 1804 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 1804 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuitry 1806 and generate baseband signals for the transmit signal path of the RF circuitry 1806. The baseband circuitry 1804 may interact with the application circuitry 1802 to generate and process baseband signals and to control the operation of the RF circuitry 1806. For example, in some implementations, the baseband circuitry 1804 may include a 3G baseband processor 1804A, a 4G baseband processor 1804B, a 5G baseband processor 1804C, or other baseband processor 1804D of other existing generations, generations under development or future generations to be developed (e.g., 5G, 6G, etc.). The baseband circuitry 1804 (e.g., one or more of the baseband processors 1804A-1804D) may handle various radio control functions that are capable of communicating with one or more radio networks via the RF circuitry 1806. In other implementations, some or all of the functionality of the baseband processors 1804A-1804D may be included in modules stored in the memory 1804G and executed via a Central Processing Unit (CPU) 1804E. Radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, and the like. In some implementations, the modulation/demodulation circuitry of the baseband circuitry 1804 may include Fast Fourier Transform (FFT), precoding, or cluster mapping/demapping functionality. In some implementations, the encoding/decoding circuitry of the baseband circuitry 1804 may include convolution, tail-biting convolution, turbo, viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Implementations of the modem and encoder/decoder functionality are not limited to these examples, and may include other suitable functionality in other aspects.

In some implementations, memory 1804G may receive and store one or more configurations, instructions, and/or other types of information to enable indication, selection, allocation, and use of SL resources for SL-U communications involving multiple consecutive slots. SL resources may be allocated by the base station and/or the UE (e.g., without base station involvement). The SL resources may include a frequency domain, a time domain, a plurality of consecutive time slots, etc., may be selected from a SL resource pool, and may be indicated using DCI and/or SCI. Allocating SL resources may include using additional or higher layer parameters such as candidate SL resource slots, subchannels, data priority values, RSRP, etc. Additionally, in scenarios where the allocated SL resources collide or overlap with COTs, the use of SL resources and/or COTs for SL-U communications may be modified.

In some implementations, the baseband circuitry 1804 may include one or more audio Digital Signal Processors (DSPs) 1804F. The audio DSP 1804F may include elements for compression/decompression and echo cancellation, and may include other suitable processing elements in other implementations. In some implementations, components of the baseband circuitry may be combined in a single chip, a single chipset, or disposed on the same circuit board as appropriate. In some implementations, some or all of the constituent components of the baseband circuitry 1804 and the application circuitry 1802 may be implemented together, such as, for example, on a system on a chip (SOC).

In some implementations, the baseband circuitry 1804 may provide communication compatible with one or more radio technologies. For example, in some implementations, the baseband circuitry 1804 may support communication with a NG-RAN, an Evolved Universal Terrestrial Radio Access Network (EUTRAN), or other Wireless Metropolitan Area Network (WMAN), a Wireless Local Area Network (WLAN), a Wireless Personal Area Network (WPAN), or the like. Implementations in which the baseband circuitry 1804 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

The RF circuitry 1806 may enable communication with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various implementations, the RF circuitry 1806 may include switches, filters, amplifiers, and the like to facilitate communication with a wireless network. The RF circuitry 1806 may include a receive signal path that may include circuitry to down-convert RF signals received from the FEM circuitry 1808 and provide baseband signals to the baseband circuitry 1804. The RF circuitry 1806 may also include a transmit signal path, which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1804 and provide RF output signals to the FEM circuitry 1808 for transmission.

In some implementations, the receive signal path of the RF circuit 1806 may include a mixer circuit 1806A, an amplifier circuit 1806B, and a filter circuit 1806C. In some implementations, the transmit signal path of the RF circuit 1806 may include a filter circuit 1806C and a mixer circuit 1806A. The RF circuit 1806 may also include a synthesizer circuit 1806D for synthesizing frequencies used by the mixer circuit 1806A of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 1806A of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 1808 based on the synthesized frequency provided by the synthesizer circuit 1806D. The amplifier circuit 1806B may be configured to amplify the down-converted signal, and the filter circuit 1806C 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 circuitry 1804 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 1806A of the receive signal path may include a passive mixer, although the scope of the implementations is not limited in this respect.

In some embodiments, the mixer circuit 1806A of the transmit signal path may be configured to upconvert the input baseband signal based on a synthesized frequency provided by the synthesizer circuit 1806D to generate an RF output signal for the FEM circuit 1808. The baseband signal may be provided by baseband circuitry 1804 and may be filtered by filter circuitry 1806C.

In some implementations, the mixer circuit 1806A of the receive signal path and the mixer circuit 1806A 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 1806A of the receive signal path and the mixer circuit 1806A 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 1806A and mixer circuit 1406A of the receive signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some implementations, the mixer circuit 1806A of the receive signal path and the mixer circuit 1806A of the transmit signal path may be configured for superheterodyne operation.

In some implementations, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the implementations 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, the RF circuitry 1806 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuitry 1804 may include a digital baseband interface to communicate with the RF circuitry 1806.

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

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

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

In some implementations, the frequency input may be provided by a Voltage Controlled Oscillator (VCO), but this is not required. The divider control input may be provided by baseband circuitry 1804 or application circuitry 1802 depending on the desired output frequency. In some implementations, the divider control input (e.g., N) can be determined from a look-up table based on the channel indicated by application circuit 1802.

The synthesizer circuit 1806D of the RF circuit 1806 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 the carry out) to provide a fractional divide ratio. In some example implementations, the DLL may include a cascaded, tunable, set of delay elements, phase detectors, charge pumps, and D-type flip-flops. In these implementations, the delay elements may be configured to divide the VCO period into Nd equal phase packets, 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 period.

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

The FEM circuitry 1808 may include a receive signal path that may include circuitry configured to operate on RF signals received from the one or more antennas 1810, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 1806 for further processing. The FEM circuitry 1808 may also include a transmit signal path, which may include circuitry configured to amplify a transmit signal provided by the RF circuitry 1806 for transmission through one or more of the one or more antennas 1810. In various implementations, amplification by the transmit or receive signal paths may be accomplished in the RF circuitry 1806 alone, in the FEM circuitry 1808 alone, or in both the RF circuitry 1806 and FEM circuitry 1808.

In some implementations, the FEM circuitry 1808 may include a TX/RX switch to switch between transmit mode operation and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to provide to the RF circuitry 1806). The transmit signal path of FEM circuitry 1808 may include a Power Amplifier (PA) to amplify the input RF signal (e.g., provided by RF circuitry 1806), and one or more filters to generate the RF signal for subsequent transmission (e.g., via one or more of the one or more antennas 1810).

In some implementations, the PMC 1812 may manage the power provided to the baseband circuitry 1804. In particular, the PMC 1812 may control power supply selection, voltage scaling, battery charging, or DC-DC conversion. When the device 1800 is capable of being battery powered, for example, when the device is included in a UE, the PMC 1812 may generally be included. The PMC 1812 may improve power conversion efficiency while providing desired implementation size and heat dissipation characteristics.

Although fig. 18 shows PMC 1812 coupled only to baseband circuitry 1804. However, in other implementations, the PMC 1812 may additionally or alternatively be coupled with other components (such as, but not limited to, the application circuit 1802, the RF circuit 1806, or the FEM 1808) and perform similar power management operations for these other components.

In some implementations, the PMC 1812 may control or otherwise be part of various power saving mechanisms of the device 1800. For example, if the device 1800 is in an RRC Connected state, where the device is still Connected to the RAN node, because it expects to receive traffic immediately, after a period of inactivity, the device may enter a state called discontinuous reception mode (DRX). During this state, the device 1800 may be powered down for a short interval, thereby saving power.

If there is no data traffic activity for an extended period of time, the device 1800 may transition to an rrc_idle state in which the device is disconnected from the network and no operations such as channel quality feedback, handover, etc. are performed. The device 1800 enters a very low power state and it performs paging where it wakes up again periodically to listen to the network and then powers down again. The device 1800 may not receive data in this state and may transition back to the RRC Connected state in order to receive data.

The additional power saving mode may cause the device to fail to use the network for more than a paging interval (ranging from seconds to hours). During this time, the device cannot connect to the network and may be completely powered off. Any data transmitted during this period causes significant delay and the delay is assumed to be acceptable.

The processor of the application circuit 1802 and the processor of the baseband circuit 1804 may be used to execute elements of one or more instances of a protocol stack. For example, the processor of baseband circuitry 1804 may be used alone or in combination to perform layer 3, layer 2, or layer 1 functionality, while the processor of baseband circuitry 1804 may utilize data (e.g., packet data) received from these layers and further perform layer 4 functionality (e.g., transmission Communication Protocol (TCP) and User Datagram Protocol (UDP) layers). As mentioned herein, layer 3 may include an RRC layer, 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 the UE/RAN node, as will be described in further detail below.

Fig. 19 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 methods discussed herein, according to some example implementations. In particular, fig. 19 shows a schematic diagram of a hardware resource 1900 that includes one or more processors (or processor cores) 1910, one or more memory/storage devices 1920, and one or more communication resources 1930, each of which can be communicatively coupled via a bus 1940. For implementations in which node virtualization (e.g., NFV) is utilized, a hypervisor may be executed to provide an execution environment for one or more network slices/sub-slices to utilize hardware resources 1900.

The processor 1910 (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, a processor 1912 and a processor 1914.

Memory/storage 1920 may include main memory, disk memory, or any suitable combination thereof. The memory/storage 1920 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, and the like.

In some implementations, memory/storage 1920 may receive and store one or more configurations, instructions, and/or other types of information 1955 for enabling indication, selection, allocation, and use of SL resources for SL-U communications involving multiple consecutive slots. SL resources may be allocated by the base station and/or the UE (e.g., without base station involvement). The SL resources may include a frequency domain, a time domain, a plurality of consecutive time slots, etc., may be selected from a SL resource pool, and may be indicated using DCI and/or SCI. Allocating SL resources may include using additional or higher layer parameters such as candidate SL resource slots, subchannels, data priority values, RSRP, etc. Additionally, in scenarios where the allocated SL resources collide or overlap with COTs, the use of SL resources and/or COTs for SL-U communications may be modified.

Communication resources 1930 may include an interconnection or network interface component or other suitable device to communicate with one or more peripheral devices 1904 or one or more databases 1906 via network 1908. Communication resources 1930 may include, for example, wired communication components (e.g., for coupling via Universal Serial Bus (USB), cellular communication component, NFC component,The component(s) (e.g.,Low power consumption),Components and other communication components.

The instructions 1950 may include software, programs, applications, applets, application software, or other executable code for causing at least any one of the processors 1910 to perform any one or more of the method sets discussed herein. The instructions 1950 may reside, in whole or in part, within at least one of the processor 1910 (e.g., within a cache memory of the processor), the memory/storage 1920, or any suitable combination thereof. Further, any portion of instructions 1950 may be transferred from any combination of peripherals 1904 or databases 1906 to hardware resource 1900. Thus, the memory of the processor 1910, the memory/storage 1920, the peripheral devices 1904, and the database 1906 are examples of computer-readable and machine-readable media.

Embodiments herein may include subject matter, such as methods, at least one machine-readable medium comprising 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 the actions of a method or apparatus or system for concurrent communication using multiple communication techniques in accordance with the specific implementations and embodiments described.

In embodiment 1, which may also include one or more of the embodiments described herein, a UE may include a memory, and one or more processors configured to, when executing instructions stored in the memory, cause the UE to determine unlicensed spectrum side link (SL-U) resources for multi-contiguous slot SL-U communication with another UE, wherein the SL-U communication includes transmissions involving a plurality of contiguous slots, and transmit data to the other UE using the plurality of contiguous slots of the SL-U resources.

In embodiment 2, which may also include one or more of the embodiments described herein, the UE will determine the SL-U resources such that data transmitted by the multi-contiguous slot SL-U communication is transmitted in a consistent manner with a quality of service (QoS) associated with the data.

In embodiment 3, which may also include one or more of the embodiments described herein, wherein the UE is configured to send SL Control Information (SCI) to the other UE, the SCI is configured to indicate a Time Resource Indicator Value (TRIV) and a Frequency Resource Indicator Value (FRIV) of the multi-contiguous slot SL-U communication.

In embodiment 4 (which may also include one or more of the embodiments described herein), wherein the transmitting comprises an initial transmission having a plurality of consecutive time slots, each of the plurality of consecutive time slots corresponding to a first frequency.

In embodiment 5 (which may also include one or more of the embodiments described herein), the multi-contiguous slot SL-U communication further includes a first retransmission including a plurality of contiguous slots each corresponding to a second frequency.

In embodiment 6, which may also include one or more of the embodiments described herein, the UE is to receive hybrid automatic repeat request, SL, (HARQ) information corresponding to the initial transmission, wherein the SL HARQ information is received via a physical Side Link (SL) feedback channel (PSFCH) in a pattern of SL-U resources consistent with the plurality of consecutive slots of the first transmission.

In embodiment 7 (which may also include one or more of the embodiments described herein), the SL-U communication further includes a third retransmission comprising a plurality of consecutive time slots, wherein each time slot corresponds to a third frequency different from the first frequency and the second frequency.

In embodiment 8 (which may also include one or more of the embodiments described herein), the UE is to receive additional SL HARQ information corresponding to the one or more retransmissions, wherein the additional SL HARQ information is received via the PSFCH in a pattern of SL-U resources consistent with the plurality of consecutive slots of the one or more retransmissions.

In embodiment 9 (which may also include one or more of the embodiments described herein), the number of consecutive time slots of the initial transmission is equal to the number of consecutive time slots of each of the one or more second retransmissions.

In embodiment 10 (which may also include one or more of the embodiments described herein), the total number of transmissions (n) is 2, including the initial transmission and one retransmission, or 3, including the initial transmission and two retransmissions.

In embodiment 11 (which may also include one or more of the embodiments described herein), the transmitting comprises an initial transmitting having a plurality of consecutive time slots, wherein each time slot of the plurality of consecutive time slots corresponds to a different frequency of the frequency pattern.

In embodiment 12 (which may also include one or more of the embodiments described herein), the SL-U communication further includes one or more retransmissions having a plurality of consecutive time slots, wherein each time slot of the plurality of consecutive time slots corresponds to an offset frequency pattern shifted according to a frequency offset of the frequency pattern of the initial transmission.

In embodiment 13 (which may also include one or more of the embodiments described herein), the plurality of consecutive time slots of the initial transmission are all allocated for transmitting a single TB.

In embodiment 14 (which may also include one or more of the embodiments described herein), the plurality of consecutive time slots of the initial transmission are each allocated for transmitting a different TB.

In embodiment 15, which may also include one or more of the embodiments described herein, a base station may include a memory, and one or more processors configured to, when executing instructions stored in the memory, cause the base station to determine unlicensed spectrum side link (SL-U) resources for multi-contiguous slot SL-U communications between User Equipment (UEs), generate Downlink Control Information (DCI) indicating the SL-U resources, wherein the DCI includes an indication of frequency domain resources, time domain resources, and a number of slots for the multi-contiguous slot SL-U communications, and communicate the DCI to one or more of the UEs.

In embodiment 16 (which may also include one or more of the embodiments described herein), the DCI is provided as part of a mode 1 resource allocation procedure.

In embodiment 17 (which may also include one or more of the embodiments described herein), the DCI includes DCI format 3_0 information.

In embodiment 18, which may also include one or more of the embodiments described herein, the DCI format 3_0 information includes a Time Resource Indicator Value (TRIV) and a Frequency Resource Indicator Value (FRIV) of the multi-contiguous slot SL-U communication.

In embodiment 19 (which may also include one or more of the embodiments described herein), the DCI includes a single pair FRIV and TRIV fields when the frequency domain resource remaining is common to multiple slots in a multi-contiguous slot transmission.

In embodiment 20 (which may also include one or more of the embodiments described herein), the DCI includes a single pair FRIV and TRIV fields for a first slot of a multi-contiguous slot SL-U communication and a frequency offset associated with the first slot for each of the subsequent slots of the multi-contiguous slot SL-U communication.

In embodiment 21, which may also include one or more of the embodiments described herein, a UE may include a memory, and one or more processors configured to, when executing instructions stored in the memory, cause the UE to receive control information including unlicensed spectrum side link (SL-U) resources for communicating with another UE, determine SL-U resources for multi-contiguous slot SL-U communication based on the control information, the multi-contiguous slot SL-U communication including an initial multi-contiguous slot SL-U transmission, and communicate with the other UE via the multi-contiguous slot SL-U communication.

In embodiment 22 (which may also include one or more of the embodiments described herein), the control information includes frequency domain resources, time domain resources, channel Occupation Time (COT), number of consecutive slots per SL-U transmission (a), and maximum number of SL-U transmissions per multi-consecutive slot SL-U communication set (N).

In embodiment 23, which may also include one or more of the embodiments described herein, the control information includes at least one Time Resource Indicator Value (TRIV) and at least one Frequency Resource Indicator Value (FRIV).

In embodiment 24, which may also include one or more of the embodiments described herein, the control information includes Downlink Control Information (DCI) format 3_0 information received from the base station for resource allocation mode 1.

In embodiment 25, which may also include one or more of the embodiments described herein, the control information includes a level 1 SL Control Information (SCI) received from the other UE.

In embodiment 26, which may also include one or more of the embodiments described herein, the UE will determine a first time slot for multiple retransmissions based on the maximum number (N) of SL-U transmissions.

In embodiment 27, which may also include one or more of the embodiments described herein, the UE will determine a first time slot of a first retransmission of the continuous slot SL-U communication based on the maximum number of SL-U transmissions (N), a pre-configured constant (32), the number of continuous slots per SL-U transmission (a), and the first time slot of an initial transmission.

In embodiment 28 (which may also include one or more of the embodiments described herein), the UE will determine a first time slot of a second retransmission of the continuous slot SL-U communication based on a number of time slots (T ₁) from the first time slot of the initial transmission and the first time slot of the first retransmission, the maximum number of SL-U transmissions (N), the preconfigured constant (32), the number of consecutive time slots (a) of each SL-U transmission, and the first time slot of the initial transmission.

In embodiment 29 (which may also include one or more of the embodiments described herein), the UE will determine a first time slot of a first retransmission of the continuous slot SL-U communication based on the maximum number of SL-U transmissions (N), a pre-configured constant (32), the number of continuous slots per SL-U transmission (a), and a last time slot of an initial transmission.

In embodiment 30 (which may also include one or more of the embodiments described herein), the UE will determine a first time slot of a second retransmission of the continuous slot SL-U communication based on a number of time slots (T ₁) from the last time slot of the initial transmission and the first time slot of the first retransmission, the maximum number of SL-U transmissions (N), the preconfigured constant (32), the number of consecutive time slots (a) of each SL-U transmission, and the last time slot of the initial transmission.

In embodiment 31, which may also include one or more of the embodiments described herein, the UE will determine a transmission time of a SL hybrid automatic repeat request (HARQ) report based on a Physical SL Feedback Channel (PSFCH) to HARQ feedback timing indicator and a last PSFCH resource for the multi-contiguous slot SL-U communication.

In embodiment 32, which may also include one or more of the embodiments described herein, a UE may include a memory, and one or more processors configured to, when executing instructions stored in the memory, cause the UE to determine initial candidate multi-contiguous slot resources for unlicensed spectrum side link (SL-U) transmission within a resource selection window, remove multi-contiguous slot resources from the initial candidate multi-contiguous slot resources based on a Reference Signal Received Power (RSRP) threshold measured during a sensing window corresponding to the resource selection window, and report remaining multi-contiguous slot resources in the resource selection window for higher layer processing when a number of multi-contiguous slot resources transmitted by multi-contiguous slot SL is less than a number of multi-contiguous slot resources remaining in the resource selection window in the initial candidate multi-contiguous slot resources.

In embodiment 33 (which may also include one or more of the embodiments described herein), the UE will remove the multi-contiguous time slot resources from the initial candidate multi-contiguous time slot resources when the multi-contiguous time slot resources have not yet been monitored by the UE for supported periodic prolonged monitoring.

In embodiment 34 (which may also include one or more of the embodiments described herein), the UE will remove the multi-contiguous time slot resources from the initial candidate multi-contiguous time slot resources when the multi-contiguous time slot resources overlap with any single time slot resources reserved by another UE at an RSRP above the RSRP threshold.

In embodiment 35 (which may also include one or more of the embodiments described herein), the UE will remove the multi-contiguous time slot resources from the initial candidate multi-contiguous time slot resources when the multi-contiguous time slot resources overlap with any single time slot resources reserved by another UE associated with a priority value that meets certain criteria.

In embodiment 36 (which may also include one or more of the embodiments described herein), when the number of multi-contiguous time slot resources transmitted by multi-contiguous time slots SL is equal to or greater than the number of multi-contiguous time slot resources remaining in the resource selection window in the initial candidate multi-contiguous time slot resources, the RSRP threshold is increased and the number of multi-contiguous time slot resources remaining in the resource selection window in the initial candidate multi-contiguous time slot resources is determined based on the increased RSRP threshold.

In embodiment 37, which may also include one or more of the embodiments described herein, the total duration of Channel Occupancy Time (COT) for the multi-contiguous slot SL transmission is not modified by the SL-U resources reserved within the COT.

In embodiment 38, which may also include one or more of the embodiments described herein, the total duration of a Channel Occupancy Time (COT) for the multi-contiguous slot SL transmission is extended by the SL-U resources reserved within the COT.

In embodiment 39, which may also include one or more of the embodiments described herein, the total duration of Channel Occupancy (COT) for the multi-contiguous slot SL transmission is stopped by the SL-U resources reserved within the COT.

In embodiment 40, which may also include one or more of the embodiments described herein, a method performed by a UE may include one or more of the operations described herein, such as determining unlicensed spectrum side link (SL-U) resources for multi-contiguous slot SL-U communication with another UE, wherein the SL-U communication includes a transmission involving a plurality of contiguous slots, and transmitting data to the other UE using the multi-contiguous slots of the SL-U resources.

In embodiment 41, which may also include one or more of the embodiments described herein, a method performed by a base station may include one or more of the operations described herein, such as determining unlicensed spectrum side link (SL-U) resources for multi-contiguous slot SL-U communications between User Equipment (UEs), generating Downlink Control Information (DCI) indicating the SL-U resources, wherein the DCI includes an indication of frequency domain resources, time domain resources, and a number of slots for the multi-contiguous slot SL-U communications, and communicating the DCI to one or more of the UEs.

The above description of illustrated examples, implementations, aspects, etc. of the disclosed subject matter, including what is described in the abstract, is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. Although specific examples, implementations, aspects, and the like are described herein for illustrative purposes, various modifications are possible within the scope of such examples, implementations, aspects, etc., as those skilled in the relevant art may recognize.

In this regard, while the subject matter of the present disclosure has been described in connection 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 for performing the same, similar, alternative or alternative function of the same without deviating therefrom, where applicable. Accordingly, the disclosed subject matter should not be limited to any single example, implementation, or aspect described herein, but rather should be construed in breadth and scope in accordance with the following appended claims.

In particular regard to the various functions performed by the above described components or structures (assemblies, devices, circuits, systems, etc.), the terms (including a reference to a "means") used to describe such components are intended to correspond, unless otherwise indicated, to any component or structure which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations. In addition, while a particular feature may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given application.

As used herein, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise indicated or clear from the context, "X employs a or B" is intended to mean any of the natural inclusive permutations. 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" as used in this disclosure and the appended claims should generally be construed to mean "one or more" unless specified otherwise or clear from context to be directed to a singular form. Furthermore, to the extent that the terms "includes," including, "" has, "" with, "or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term" comprising. Additionally, where one or more numbered items (e.g., "first X," "second X," etc.) are discussed, typically 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.

It is well known that the use of personally identifiable information should follow privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled to minimize the risk of inadvertent or unauthorized access or use, and the nature of authorized use should be explicitly indicated to the user.

Claims (33)

1. A User Equipment (UE), the UE comprising:

Memory, and

One or more processors configured to, when executing the instructions stored in the memory, cause the UE to:

Determining unlicensed spectrum side link (SL-U) resources for multi-contiguous time slot SL-U communication with another UE, wherein the SL-U communication includes transmissions involving a plurality of contiguous time slots, and

The plurality of consecutive slots of the SL-U resource are used to transmit data to the other UE.

2. The UE of claim 1, wherein the UE is to determine the SL-U resources such that data sent by the multi-contiguous slot SL-U communication is sent in a consistent manner with a quality of service (QoS) associated with the data.

3. The UE of claim 1, wherein the UE is configured to send SL Control Information (SCI) to the other UE, the SCI being configured to indicate a Time Resource Indicator Value (TRIV) and a Frequency Resource Indicator Value (FRIV) of the multi-contiguous slot SL-U communication.

4. The UE of claim 1, wherein the transmission comprises an initial transmission having a plurality of consecutive time slots, each corresponding to a first frequency.

5. The UE of claim 4, wherein the multi-contiguous slot SL-U communication further comprises a first retransmission comprising a plurality of contiguous slots each corresponding to a second frequency.

6. The UE of claim 4, wherein the UE is to receive hybrid automatic repeat request, SL, (HARQ) information corresponding to the initial transmission, wherein the SL HARQ information is received via a physical Side Link (SL) feedback channel (PSFCH) in a pattern of SL-U resources consistent with the plurality of consecutive slots of the first transmission.

7. The UE of claim 4, wherein the SL-U communication further comprises a third retransmission comprising a plurality of consecutive time slots, wherein each time slot corresponds to a third frequency different from the first frequency and the second frequency.

8. The UE of claim 7, wherein the UE is to receive additional SL HARQ information corresponding to the one or more retransmissions, wherein the additional SL HARQ information is received via the PSFCH in a pattern of SL-U resources consistent with the plurality of consecutive slots of the one or more retransmissions.

9. The UE of claim 5, wherein the number of consecutive time slots of the initial transmission is equal to the number of consecutive time slots of each of the one or more second retransmissions.

10. The UE of claim 9, wherein the total number of transmissions (n) is:

2, including the initial transmission and one retransmission, or

3, Including the initial transmission and two retransmissions.

11. The UE of claim 1, wherein the transmission comprises an initial transmission having a plurality of consecutive time slots, wherein each time slot of the plurality of consecutive time slots corresponds to a different frequency of a frequency pattern.

12. The UE of claim 11, wherein the SL-U communication further comprises one or more retransmissions having a plurality of consecutive time slots, wherein each time slot of the plurality of consecutive time slots corresponds to an offset frequency pattern shifted according to a frequency offset of the frequency pattern of the initial transmission.

13. The UE of claim 1, wherein the plurality of consecutive time slots of an initial transmission are all allocated for transmitting a single TB.

14. The UE of claim 1, wherein the plurality of consecutive time slots of the initial transmission are each allocated for transmitting a different TB.

15. A base station, the base station comprising:

Memory, and

One or more processors configured to, when executing instructions stored in the memory, cause the base station to:

Determining unlicensed spectrum side link (SL-U) resources for multi-contiguous slot SL-U communications between User Equipments (UEs);

Generating Downlink Control Information (DCI) indicating the SL-U resources, wherein the DCI includes an indication of frequency domain resources, time domain resources, and a number of time slots for the multi-contiguous slot SL-U communication, and

The DCI is communicated to one or more of the UEs.

16. The base station of claim 15, wherein the DCI is provided as part of a mode 1 resource allocation procedure.

17. The base station of claim 15, wherein the DCI comprises DCI format 3_0 information.

18. The base station of claim 17, wherein the DCI format 3_0 information includes a Time Resource Indicator Value (TRIV) and a Frequency Resource Indicator Value (FRIV) of the multi-contiguous slot SL-U communication.

19. The base station of claim 18, wherein the DCI comprises a single pair FRIV and TRIV fields when frequency domain resource residuals are common for multiple slots in a multi-contiguous slot transmission.

20. The base station of claim 18, wherein the DCI includes a single pair FRIV and TRIV fields for a first slot of a multi-contiguous slot SL-U communication and a frequency offset associated with the first slot for each of the subsequent slots of the multi-contiguous slot SL-U communication.

21. A User Equipment (UE), the UE comprising:

Memory, and

One or more processors configured to, when executing the instructions stored in the memory, cause the UE to:

receiving control information, the control information including unlicensed spectrum side link (SL-U) resources for communicating with another UE;

Determining SL-U resources for a multi-contiguous slot SL-U communication based on the control information, the multi-contiguous slot SL-U communication including an initial multi-contiguous slot SL-U transmission, and

Communicate with the other UE via the multi-contiguous slot SL-U communication.

22. The UE of claim 21, wherein the control information includes frequency domain resources, time domain resources, channel Occupation Time (COT), a number of consecutive slots per SL-U transmission (a), and a maximum number of SL-U transmissions per multi-consecutive slot SL-U communication set (N).

23. The UE of claim 22, wherein the control information comprises at least one Time Resource Indicator Value (TRIV) and at least one Frequency Resource Indicator Value (FRIV).

24. The UE of claim 23, wherein the control information comprises Downlink Control Information (DCI) format 3_0 information for resource allocation mode 1 received from a base station.

25. The UE of claim 22, wherein the control information comprises a level 1 SL Control Information (SCI) received from the other UE.

26. The UE of claim 22, wherein the UE is to determine a first time slot for multiple retransmissions based on the maximum number (N) of SL-U transmissions.

27. The UE of claim 22, wherein the UE is to determine a first time slot of a first retransmission of the continuous slot SL-U communication based on the maximum number (N) of SL-U transmissions, a pre-configured constant (32), the number (a) of continuous slots per SL-U transmission, and the first time slot of an initial transmission.

28. The UE of claim 27, wherein the UE is to determine a first time slot of a second retransmission of the continuous slot SL-U communication based on a number of time slots (T ₁) from the first time slot of the initial transmission and the first time slot of the first retransmission, the maximum number of SL-U transmissions (N), the preconfigured constant (32), the number of consecutive time slots (a) per SL-U transmission, and the first time slot of the initial transmission.

29. The UE of claim 22, wherein the UE is to determine a first time slot of a first retransmission of the continuous slot SL-U communication based on the maximum number (N) of SL-U transmissions, a pre-configured constant (32), the number (a) of continuous slots per SL-U transmission, and a last time slot of an initial transmission.

30. The UE of claim 29, wherein the UE is to determine a first time slot of a second retransmission of the continuous slot SL-U communication based on a number of time slots (T ₁) from the last time slot of the initial transmission and the first time slot of the first retransmission, the maximum number of SL-U transmissions (N), the preconfigured constant (32), the number of consecutive time slots (a) per SL-U transmission, and a last time slot of the initial transmission.

31. The UE of claim 21, wherein the UE is to determine a transmission time of a SL hybrid automatic repeat request (HARQ) report based on a Physical SL Feedback Channel (PSFCH) to HARQ feedback timing indicator and a last PSFCH resource for the multi-contiguous slot SL-U communication.

32. A method performed by a User Equipment (UE), the method comprising:

Determining unlicensed spectrum side link (SL-U) resources for multi-contiguous time slot SL-U communication with another UE, wherein the SL-U communication includes transmissions involving a plurality of contiguous time slots, and

The plurality of consecutive slots of the SL-U resource are used to transmit data to the other UE.

33. The method of claim 32, further comprising determining the SL-U resources such that data transmitted by the multi-contiguous slot SL-U communication is transmitted in a consistent manner with a quality of service (QoS) associated with the data.