Systems, methods, and apparatus for sidelink DCI 300 for resource selection mode 1

Abstract

The techniques described herein provide a solution for enabling sidelink (SL) unlicensed band or spectrum (SL-U) communication via a downlink control information (DCI) 30 for resource selection mode 1. The SL DCI 300 may include frequency resource assignment information, time resource assignment information, clear channel assessment (CCA) type information, time slot information, and cyclic prefix (CP) extension information, etc. A partial bandwidth (BW) or a full BW may be allocated to a user equipment (UE) and may be scheduled using multiple transition time intervals (multiple TTIs). Multiple SL transmission start locations may be used and they may be contiguous or non-contiguous. The bidirectional SL DCI 300 may also be transmitted to a plurality of UEs.

Description

Technical Field

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

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

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

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

[0005] Figure 2 is a diagram of an example process for sidelink (SL) downlink (DL) control information (DCI) 3_0 for resource selection mode 1 according to one or more implementations described herein.

[0006] Figure 3 is an illustration of an example data structure for SL DCI 3_0 for resource selection mode 1 according to one or more implementations described herein.

[0007] Figure 4 is a diagram of an example of DCI 3_0 based SL communication for partial bandwidth (PBW) and full bandwidth (FBW) scenarios according to one or more implementations described herein.

[0008] Figure 5 is a diagram of an example of DCI 3_0 based SL communication with multi-transmission time interval (multi-TTI) scheduling according to one or more implementations described herein.

[0009] Figure 6 is a diagram of an example of DCI 3_0 based SL communication with multiple starting positions according to one or more implementations described herein.

[0010] Figure 7is a diagram of an example of SL communication based on bidirectional DCI 3_0 according to one or more specific implementations described herein.

[0011] Figure 8 is a diagram of an example of a control plane protocol stack according to one or more implementations described herein.

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

[0013] Fig.10 is an illustration of an example process for using SL DCI 3_0 according to one or more implementations described herein.

[0014] Fig.11 is a diagram of an example process for providing SL DCI 3_0 according to one or more implementations described herein. DETAILED DESCRIPTION

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

[0016] A telecommunications network may include user equipment (UE) that is capable of communicating with base stations and other network nodes. The UE and the base station may implement various technologies for establishing and maintaining connections. In some implementations, the UE may be able to communicate and connect directly to each other. Direct communication between UEs may be referred to as device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, side link (SL) communication, etc. The UE may use one or more wireless frequency bands to communicate with different wireless devices. For example, the UE may use a licensed frequency band to communicate with a base station and use an unlicensed frequency band to communicate with other UEs. The UE may participate in a resource selection procedure (e.g., SL resource selection) to enable direct communication with other UEs.

[0017] As described herein, SL resource selection may include Mode 1 SL resource selection and Mode 2 SL resource selection. Mode 1 SL resource selection may include dynamic grant (DG) and configuration grant (CG) of SL resources managed by a base station or other network device. DG may involve grant based on a grant request from UE 110. CG may involve resource grant without a grant request and may be based on the type of service provided (e.g., a service with strict timing or delay requirements). In a Mode 1 SL resource selection scenario, the network dynamically allocates SL resources to the UE for SL communication. In addition, Mode 1 SL resource selection may include Type 1 CG or Type 2 CG. Type 1 CG may include a base station using radio resource control (RRC) signaling to indicate one or more wireless carriers or channels, the periodicity of the allocated resources, the offset, start and length of the resources (e.g., symbols), the number of repetitions, the transmission power level, etc. Type 2 CG may include a base station providing a more limited amount of CG information (e.g., periodicity and number of repetitions) via RRC and providing additional SL CG information via downlink (DL) control information (DCI). The CG may include a DCI with a SL radio network temporary identifier (SL-RNTI), a SL configuration scheduling (CS) RNTI (SL-CS-RNTI), etc. Compared with the network-managed SL resource selection of Mode 1, Mode 2 SL resource selection may include resource selection that is primarily performed by the UE. For example, in Mode 2 SL resource selection, the base station may provide a potential SL resource pool to the UE, but the UE may perform sensing (e.g., availability detection), selection, and reservation of SL resources.

[0018] However, currently available SL resource selection or allocation techniques fail to provide a complete or adequate solution for SL resource selection and reservation to enable sidelink operation in unlicensed bands. For example, currently available techniques fail to provide an adequate solution for mode 1 SL resource selection or allocation via DCI. For example, currently available techniques fail to provide a solution for disabling SL frequency domain and time domain resources in unlicensed bands, time slot information, clear channel assessment (CCA) type, cyclic prefix (CP) extension, and multiple transmission time interval (multi-TTI) scheduling.

[0019] The techniques described herein provide a better and more complete solution for SL resource selection in an unlicensed spectrum. For example, a base station may send a UE SL DCI 3_0 for resource selection mode 1. The SL DCI 3_0 may include frequency resource assignment information, time resource assignment information, CCA type information, time gap information, and CP extension information. The frequency resource assignment information may indicate whether a partial BW or a full BW is allocated to the UE 110, and whether the assigned frequency resources are interleaved waveform resources or continuous waveform resources. The time resource assignment information may include the type of CCA to be performed by the UE, the time gap between the reception of the SL DCI 3_0 and the first SL transmission, and whether CP extension is to be used during SL communication (e.g., between the completion of the CCA procedure and the first SL transmission or to ensure that the gap between SL transmissions for a shared COT scenario is observed).

[0020] SL DCI 3_0 may also include multi-TTI scheduling information, which may include continuous SL transmission or non-continuous SL transmission. In such a scenario, SL DCI 3_0 may also include HARQ information for one or more of the multi-TTI SL transmissions. In some specific implementations, SL DCI 3_0 may include multiple starting positions for SL transmission. The starting position may start at a time slot boundary or halfway between time slot boundaries, and may depend on whether a partial BW or a full BW is allocated to the UE. In some specific implementations, SL DCI 3_0 may include a bidirectional SL DCI 3_0 transmitted by a base station to multiple UEs. The UE may receive the bidirectional SL DCI 3_0 so as to be within the coverage area of ​​the base station and / or within a logical group of UEs determined by the base station.

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

[0022] The systems and devices of the example network 100 may operate in accordance with one or more communication standards, such as the second generation (2G), third generation (3G), fourth generation (4G) (e.g., long term evolution (LTE)), and / or fifth generation (5G) (e.g., new radio (NR)) communication standards of the 3rd Generation Partnership Project (3GPP). Additionally or alternatively, one or more of the systems and devices of the example network 100 may operate in accordance with other communication standards and protocols discussed herein, including future versions or generations of 3GPP standards (e.g., sixth generation (6G) standards, seventh generation (7G) standards, etc.), Institute of Electrical and Electronics Engineers (IEEE) standards (e.g., wireless metropolitan area networks (WMANs), Worldwide Interoperability for Microwave Access (WiMAX), etc.), and more.

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

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

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

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

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

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

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

[0030] Some or all or portions of the RAN nodes 122 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a centralized RAN (CRAN) and / or a virtual baseband unit pool (vBBUP). In these specific implementations, the CRAN or vBBUP may implement a RAN functional split, such as a packet data convergence protocol (PDCP) split, where the radio resource control (RRC) and PDCP layers may be operated by the CRAN / vBBUP, and other layer 2 (L2) protocol entities may be operated by individual RAN nodes 122; a medium access control (MAC) / physical (PHY) layer split, where the RRC, PDCP, radio link control (RLC), and MAC layers may be operated by the CRAN / vBBUP, and the PHY layer may be operated by individual RAN nodes 122; or a "lower PHY" split, where the RRC, PDCP, RLC, MAC layer, and upper portions of the PHY layer may be operated by the CRAN / vBBUP, and the lower portions of the PHY layer may be operated by individual RAN nodes 122. The virtualization framework may allow idle processor cores of the RAN node 122 to perform or execute other virtualized applications.

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

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

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

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

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

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

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

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

[0039] In some specific implementations, the UE 110 and stores one or more configurations, instructions and / or other information for the SL DCI 3_0 for resource selection mode 1. SL DCI 3_0SL DCI 3_0 information may be received from the base station 122 and used to communicate on SL unlicensed resources, select resources for transmission via the interface 112, etc. The SL DCI 3_0 may include frequency resource assignment information, time resource assignment information, CCA type information, time gap information, and CP extension information. The frequency resource assignment information may indicate whether a partial BW or a full BW is allocated to the UE 110, and whether the assigned frequency resources are interleaved waveform resources or continuous waveform resources. The time resource assignment information may include the type of CCA to be performed by the UE, the time gap between the reception of the SL DCI 3_0 and the first SL transmission, and whether CP extension is to be used during SL communication (e.g., between the completion of the CCA procedure and the first SL transmission or to ensure that the gap between SL transmissions for a shared COT scenario is observed).

[0040] SL DCI 3_0 may also include multi-TTI scheduling information, which may include continuous SL transmission or non-continuous SL transmission. In such a scenario, SL DCI 3_0 may also include HARQ information for one or more of the multi-TTI SL transmissions. In some specific implementations, SL DCI 3_0 may include multiple starting positions for SL transmission. The starting position may start at a time slot boundary, halfway between time slot boundaries, and may depend on whether a partial BW or a full BW is allocated to the UE. In some specific implementations, SL DCI 3_0 may include a bidirectional SL DCI 3_0 transmitted by a base station to multiple UEs. The UE may receive the bidirectional SL DCI 3_0 so as to be within the coverage area of ​​the base station and / or within a logical group of UEs determined by the base station.

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

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

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

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

[0045] Figure 22 is a diagram of an example process 200 for SL DCI 3_0 for resource selection mode 1 according to one or more implementations described herein. Process 200 may be implemented by UE 110-1, UE 110-2, and base station 122. In some implementations, some or all of process 200 may be performed by one or more other systems or devices, including Figure 1 In addition, process 200 may include: Figure 2 One or more fewer, additional, differently ordered, and / or arranged operations than those shown. In some implementations, some or all of the operations of process 200 may be performed independently, sequentially, simultaneously, etc., with one or more of the other operations of process 200. Thus, the techniques described herein are not limited to Figure 2 The number, sequence, arrangement, timing, etc. of the operations or processes depicted in the .

[0046] As shown, process 200 may include base station 122 providing SL DCI3_0 information for resource selection mode 1 to UE 110-1 (at 2.1). Mode 1 SL resource selection may include dynamic scheduling and CG of SL resources managed by the base station or other network devices. In the Mode 1 scenario, the network dynamically allocates SL resources to the UE for SL communication. In addition, Mode 1 SL resource selection may include Type 1 CG or Type 2 CG. Type 1 CG may include the base station using RRC signaling to indicate one or more wireless carriers or channels, the periodicity of the allocated resources, the offset, start and length of the resources (e.g., symbols), the number of repetitions, the transmission power level, etc. Type 2 CG may include the base station providing a more limited amount of CG information (e.g., periodicity and number of repetitions) via RRC and providing additional SL CG information via DCI. Type 1 CG may be cell-specific or UE-specific and is configured via RRC configuration of the useInterlacePSFCH-PSSCH value in the SLBWP configuration information element (IE).

[0047] In some implementations, base station 122 may send SL DCI 3_0 information in response to receiving UE capability information and / or a request for SL resources from UE 110-1. As described herein, SL DCI 3_0 may include frequency domain resource indication, time slot information, CCA type, and / or cyclic prefix (CP) extension. Figure 3 Examples of these are discussed in more detail.

[0048] UE 110-1 may receive SL DCI 3_0 information and select SL resources based on the SL DCI 3_0 information (at 2.2). As described herein, this may include processing the SL DCI 3_0 information, performing a CCA procedure prohibited by the SL DCI 3_0 information, and transmitting one or more signals to UE 110-2 using the assigned SL frequency domain resources. In some specific implementations, the SL DCI3_0 information may also or alternatively indicate or otherwise enable multi-transmission time interval (multi-TTI) scheduling, time domain resources for HARQ procedures, one or more transmission start positions, etc.

[0049] UE 110-1 may use the selected resources to communicate with UE 110-2 based on or in accordance with the SL DCI 3_0 information and the selected resources (at 2.3). UE 110-2 may receive the SL communication from UE 110-1 and respond in a manner that further enables SL communication between UEs 110. As shown, in some specific implementations, base station 122 may provide group DCI (e.g., SL DCI 3_0 information) to both UE 110-1 and UE 110-2. As described herein, the group DCI may enable UE 110-1 and UE 110-2 to each implement DCI information when communicating with each other (e.g., using a shared channel, similar timing information, similar HARQ procedures, etc.).

[0050] Figure 3 3_0 for resource selection mode according to one or more implementations described herein. The data structure 300 may include the type of information that may be included in the SL DCI 3_0 information 310, which may be provided by the base station 122 to one or more UEs 110. In addition, any of the data structures 300 may be stored and / or processed by the UE 110 to implement one or more of the SL communication techniques described herein. In some implementations, the data structure 300 may include information related to Figure 3 One or more fewer, additional, differently ordered, and / or arranged types of information than those shown.Thus, data structure 300 is provided as a non-limiting example of information that may be used to implement one or more of the techniques described herein.

[0051] As shown, the data structure 300 may include frequency domain resource indication information 310 (also referred to as frequency domain information). The frequency domain resource indication information 310 may include a bit field of one or more bits, which indicates one or more frequencies that the UE 110 can use for SL communication. In some specific implementations, the type or arrangement of the bit field may depend on the RRC configuration (e.g., whether the useInterlacePSFCH-PSSCH value of the SLBWP configuration IE is set to true or false). This information may be provided by the UE 110 to the base station 122 as part of the UE capability information or another type of information. Therefore, the frequency domain resource indication information 310 may include an indication of interlaced waveform frequency resources. In such a scenario, the bit field may include a DCI 0-0 bit field for an interlaced waveform or a DCI 0-1 bit field for an interlaced waveform. Additionally or alternatively, such as when the UE 110 is unable to use the interlaced waveform resources, the useInterlacePSFCH-PSSCH value is set to false, and the frequency domain resource indication information 310 may include an allocation of continuous waveform frequency resources.

[0052] The data structure 300 may also include CCA information 320. The CCA information 320 may include a type of CCA (e.g., type 1 CCA or type 2 CCA) to be performed by the UE 110 before using the selected resources for SL communication. In some implementations, the CCA type may be determined by the base station 122 in response to, for example, a request for SL resources and / or UE capability information transmitted to the base station 122 by the UE 110 before receiving the SL DCI 3_0 information 360. In some implementations, the SL DCI 3_0 information 360 indicating a type 1 CCA procedure (e.g., based on energy detection (ED)) may also include priority category information to be used by the UE 110 when selecting SL resources (e.g., frequency resources, timing resources, etc.). In such a scenario, the priority category information may have been determined by the base station 122 based on a SL scheduling request (SR) and / or a buffer status report (BSR) received from the UE 110. In some implementations, the SL DCI 3_0 information 360 can indicate a type 2 CCA procedure (eg, based on carrier sensing) when, for example, the scheduled SL transmission is within the COT of another UE 110 .

[0053] The data structure 300 may also include time gap information 330. The time gap information 330 may include an amount of time that the UE 110 is to wait before using the resources allocated by the SL DCI 3_0 information 360 for SL communication. In some implementations, the time gap information 330 may be determined by the base station 122 based on a request for SL resources (e.g., a SL scheduling request) and / or UE capability information from the UE 110. In some implementations, the time gap information 330 may be based on a minimum amount of time that the UE 110 may spend processing the SL DCI 3_0 information 360 and performing the CCA procedure indicated by the SL DCI 3_0 information 360.

[0054] The data structure 300 may also include CP extension information 340. The CP extension information 340 may include CP extensions used by the UE 110 for SL communications. In some implementations, the CP extension may be implemented when a Type 2 CCA is signaled to create a 16μs or 25μs gap between shared COT SL communications (e.g., after receiving a signal from the UE 110-1, the UE 110-2 may implement a CP extension to create a prohibited gap between shared COT SL communications). In some implementations, the CP extension may be used when a Type 1 CCA is signaled. In such scenarios, for PBW scenarios (e.g., scenarios in which the CG from the base station 122 involves a PBW), the CP extension may not be enabled. In contrast, for FBW scenarios (e.g., scenarios in which the CG from the base station 122 involves a FBW), the CP extension may be enabled.

[0055] Figure 4 4 is a diagram of an example 400 of DCI 3_0 based SL communication for PBW and FBW scenarios according to one or more implementations described herein. As shown, example 400 includes a transmit (Tx) UE timeline that includes several events and features (e.g., 410, 420, time gaps, SL Tx, etc.). The events and features of example 400 may represent processes, operations, data sets, etc. that may involve one or more devices described herein (such as UE 110 and / or base station 122). In some implementations, example 400 may include Figure 4 The example 400 may be one or more fewer, additional, differently ordered, or arranged events and features than those shown. For example, in some implementations, the events and features of the example 400 may be combined with, modified by, or replaced by one or more operations, processes, or data sets of one or more other example implementations described herein. Thus, the example 400 is provided as a non-limiting example that may be used to implement one or more of the techniques described herein.

[0056] As shown, example 400 may include a transmitting (Tx) UE 110 (not shown) receiving SL DCI 3_0 information (at 410). In some specific implementations, the SL DCI 3_0 information may include one or more SL frequency domain resources, CCA types, time gaps, and CP extensions allocated to the Tx UE 110. The SL frequency domain resources may include carriers, channels, frequency bands, etc. that the Tx UE 110 may use to communicate with the receiving (Rx) UE 110 (not shown). The CCA type may include the type of CCA (e.g., type 1 CCA or type 2 CCA) that the UE 110 is to perform before using the selected resources for SL communication. The time gap may include the amount of time that the Tx UE 110 may wait, measured from receiving the SL DCI 3_0 information, before participating in SL Tx. As described herein, the time gap may be the amount of time it takes for the UE 110-1 to process the SL DCI 3_0 information and perform the CCA procedure. CP extension may indicate whether UE 110 participating in SL communication should implement CP extension to help meet timing gaps in SL COT sharing scenarios.

[0057] The SL DCI 3_0 information may also indicate whether a partial bandwidth (BW, PBW, or BWP) or a full BW (FBW) is allocated for SL communication. As shown, when one or more partial BWs are allocated, the SL DCI 3_0 information may indicate the starting position for the partial BW. In such a scenario, the Tx UE 110 may be configured to enable frequency division multiplexing (FDM), and the Tx UE 110 may multiplex signals based on an interleaved signaling structure (e.g., where useInterlacePSFCH-PSSCH is set to "true"). In addition, the starting point configured for a resource pool or CG may be aligned to, for example, avoid one UE 1110 from transmitting earlier and block all other FDM transmissions of UE 110 using the same frequency resource pool. In some specific implementations, the aligned or unified starting position may be provided by the base station 122 via dynamic authorization.

[0058] When FBW is allocated, the SL DCI 3_0 information may indicate a set of starting positions (configured by the base station 122) from which the Tx UE 110 may randomly select. In such a scenario, when 20 megahertz (MHz) BW is allocated to the Tx UE 110, 10 and 5 interlaces for 15 and 30 kilohertz (kHz) subcarrier spacing (SCS) may be used, respectively. In addition, the Tx UE 110 may randomly select a position within the first symbol and use CP extension to fill the remaining half symbols. In some specific implementations, the above signaling may be configured via RRC signaling and / or via DCI 3_0 for Type 2 CG. The Tx UE 110 may randomly select a value from a set of configured starting points after Type 1 LBT is successful.

[0059] Figure 5 5 is a diagram of an example 500 of DCI 3_0 based SL communication with multi-TTI scheduling according to one or more implementations described herein. As shown, example 500 includes a Tx UE timeline, which includes several events and features (e.g., 510, 520, 530, time gaps, SL Tx, etc.). The events and features of example 500 may represent processes, operations, data sets, etc. that may involve one or more devices described herein (such as UE 110 and / or base station 122). In some implementations, example 500 may include Figure 5 The example 500 may be one or more fewer, additional, differently ordered, or arranged events and features than those shown. For example, in some implementations, the events and features of the example 500 may be combined with, modified by, or replaced by one or more operations, processes, or data sets of one or more other example implementations described herein. Thus, the example 500 is provided as a non-limiting example that may be used to implement one or more of the techniques described herein.

[0060] As shown, example 500 may include that a Tx UE 110 (not shown) may receive SL DCI 3_0 information (at 510). In some implementations, the SL DCI 3_0 information may include multi-TTI information with corresponding time domain resource information and HARQ related information per TTI (such as HARQ process ID, redundancy version (RV), new data indicator (NDI), etc. The multi-TTI information with corresponding time domain resource information may indicate the transmission of the same data for multiple consecutive times and the corresponding time domain resources (at 530) to increase the possibility of successful data reception and decoding (e.g., TTI bundling of information via a physical SL control channel (PSCCH) and / or a physical SL shared channel (PSSCH)). In some implementations, only consecutive time domain resources may be used for multiple TTIs. In such implementations, when the access priority is signaled in the SL DCI 3_0 information, the allocated time domain resources may be within the MCOT. In some implementations, the allocated time domain resources may also or alternatively include non-contiguous time domain resources.

[0061] For each TTI, the HARQ related information may include a HARQ process ID, RV, NDI, etc., so that new data, redundant data, and HARQ process ID for each HARQ program can be identified. In this way, the example 500 may enable the Tx UE 110 (not shown) to transmit data to the Rx UE 110 (not shown) using multiple TTIs and corresponding HARQ processes (at 520). In some specific implementations, the original HARQ process number and / or the HARQ process ID may indicate the first TTI of the multi-TTI transmission. In some specific implementations, the HARQ ID from the second TTI can be derived from the first TTI by an increasing sequence count. In other specific implementations, the HARQ process ID for each TTI may be explicitly signaled. Additionally or alternatively, the HARQ process ID for the first TTI plus the number of TTIs per transport block (TB) may be signaled to support repetition-based transmission operations.

[0062] In some specific implementations, the SL DCI 3_0 information may also include one or more SL frequency domain resources, CCA types, time gaps, and CP extensions allocated to the Tx UE 110. The SL frequency domain resources may include carriers, channels, frequency bands, etc. that the Tx UE 110 can use to communicate with the Rx UE 110. The CCA type may include the type of CCA (e.g., type 1 CCA or type 2 CCA) that the UE 110 is to perform before using the selected resources for SL communication. The time gap may include the amount of time that the Tx UE 110 can wait measured from receiving the SL DCI3_0 information before participating in the SL Tx. As described herein, the time gap may be the amount of time it takes for the UE 110-1 to process the SL DCI 3_0 information and perform the CCA procedure. The CP extension may indicate whether the UE 110 participating in the SL communication should implement the CP extension to help meet the timing gap in the SL COT sharing scenario.

[0063] Figure 6 600 is a diagram of an example of DCI 3_0 based SL communication with multiple start positions according to one or more implementations described herein. As shown, example 600 includes a Tx UE timeline, which includes several events and features (e.g., 610, 620, time gaps, SL Tx, etc.). The events and features of example 600 may represent processes, operations, data sets, etc. that may involve one or more devices described herein (such as UE 110 and / or base station 122). In some implementations, example 600 may include Figure 6 The example 600 may include one or more fewer, additional, differently ordered, or arranged events and features than those shown. For example, in some implementations, the events and features of the example 600 may be combined with, modified by, or replaced by one or more operations, processes, or data sets of one or more other example implementations described herein. Thus, the example 600 is provided as a non-limiting example that may be used to implement one or more of the techniques described herein.

[0064] As shown, example 600 may include that a Tx UE 110 (not shown) may receive SL DCI 3_0 information (at 610). In some implementations, the SL DCI 3_0 information may include an indication of one or more starting positions and corresponding CP extensions for SL Tx. The starting position may include a starting position at a slot boundary (e.g., at the beginning of a slot) and / or a starting position at a half-slot boundary (e.g., halfway through a slot). In some implementations, the SL DCI 3_0 information indicating one or more starting positions may be the same as described above with reference to FIG. Figure 5The described multi-TTI implementations are used in combination. In such a scenario, each time slot may include multiple starting positions for PSCCH and / or PSSCH transmissions after a successful CCA procedure. In some implementations, the starting position may be based on whether a partial BW or a full BW has been allocated for SL Tx. Additionally or alternatively, CP extension may be used to fill any additional gaps between a successful CCA procedure and the starting position.

[0065] Additionally or alternatively, in a multi-TTI transmission scenario, when the CCA procedure is unsuccessful before the first TTI, the Tx UE 110 may perform (or continue to perform) another CCA procedure. If the CCA procedure is successful, the Tx UE 110 may use the second starting position for the second TTI. In such a scenario, the Tx UE 110 may discard the unsuccessful TTI (e.g., end at the same time slot used for dynamic scheduling). In some specific implementations, due to an unsuccessful CCA procedure, a full BW scenario with only multiple TTIs may be permitted to discard the successful TTI, and start multiple TTIs from the second TTI while ending at the same time slot. In a partial BW scenario, this may be limited to 1 time slot to avoid blocking or conflicting other UEs 110 that sense CCA success within multiple TTIs. In other specific implementations, multi-TTI SL grants may be used for both full BW and partial BW scenarios. In multi-TTI SL grant and partial BW scenarios, the last symbol of each TTI may not be transmitted to ensure that the FDM transmission can perform a successful CCA and transmit using other interlaces. In this way, example 600 may enable a Tx UE 110 (not shown) to transmit data to an Rx UE 110 (not shown) using multiple starting points (at 620).

[0066] In some specific implementations, the SL DCI 3_0 information may also include one or more SL frequency domain resources, CCA types, time gaps, and CP extensions allocated to the Tx UE 110. The SL frequency domain resources may include carriers, channels, frequency bands, etc. that the Tx UE 110 can use to communicate with the Rx UE 110. The CCA type may include the type of CCA (e.g., type 1 CCA or type 2 CCA) that the UE 110 is to perform before using the selected resources for SL communication. The time gap may include the amount of time that the Tx UE 110 can wait measured from receiving the SL DCI3_0 information before participating in the SL Tx. As described herein, the time gap may be the amount of time it takes for the UE 110-1 to process the SL DCI 3_0 information and perform the CCA procedure. The CP extension may indicate whether the UE 110 participating in the SL communication should implement the CP extension to help meet the timing gap in the SL COT sharing scenario.

[0067] Figure 70 is a diagram of an example 700 of SL communication based on bidirectional DCI 3_0 according to one or more implementations described herein. As shown, example 700 includes a Tx UE timeline, which includes several events and features (e.g., 710, 720, time gaps, SL Tx, SL Rx, etc.). The events and features of example 700 may represent processes, operations, data sets, etc. that may involve one or more devices described herein (such as UE 110 and / or base station 122). In some implementations, example 700 may include Figure 7 The example 700 may be one or more fewer, additional, differently ordered, or arranged events and features than those shown. For example, in some implementations, the events and features of the example 700 may be combined with, modified by, or replaced by one or more operations, processes, or data sets of one or more other example implementations described herein. Thus, the example 700 is provided as a non-limiting example that may be used to implement one or more of the techniques described herein.

[0068] As shown, example 700 may include that a Tx UE 110 (not shown) may receive SL DCI 3_0 information (at 710). In some implementations, the SL DCI 3_0 information may include group DCI for Tx and Rx UEs. For a unidirectional DG or CG (as described in the above example), a UE 110 that only receives a grant and DCI may perform a CCA procedure and initiate a COT sharing scenario with the SL Tx. In some implementations, a bidirectional DG or CG may be provided by each UE (at Figure 7 In such a scenario, two UEs 110 may receive SL DCI 3_0 information indicating the same SL resources for each UE 110. Both UEs 110 may perform a CCA procedure and start transmission when the CCA procedure is successful. Both UEs 110 may perform a Type 1 CCA. Since the time to complete a Type 1 CCA may be random, whichever UE 110 completes first may start transmission, and in this case, the other UE 110 may be the Rx UE 110 by default.

[0069] In some implementations, the base station 122 may send the same SL DCI 3_0 information to each UE 110 individually. In other implementations, the base station 122 may define a group or UEs 110 including Tx UEs and Rx UEs. Additionally or alternatively, the base station 122 may define SL DCI 3_0 information for the UEs 110 in the group. Thus, when the Tx UE 110 and the Rx UE 110 are within the coverage area of ​​the base station 122, each UE 110 may receive the same SL DCI 3_0 information as part of the UE group. In addition, as shown in FIG. Figure 7 As shown, after the time gap and successful CCA, Tx UE 110 and Rx UE 110 may initiate SL communication using the same resources according to the bidirectional SL DCI3_0 information (at 720). The corresponding bidirectional communication may include corresponding SL HARQ procedures between Tx UE 110 and Rx UE 110. In some specific implementations, when only one of Tx UE 110 or Rx UE 110 is within the coverage area of ​​base station 122, UE 110 receiving SL DCI 3_0 information may initiate unidirectional SL communication according to one or more of the other examples described herein (e.g., examples 400, 500, or 600).

[0070] In some specific implementations, the SL DCI 3_0 information may also include one or more SL frequency domain resources, CCA types, time gaps, and CP extensions allocated to the Tx UE 110. The SL frequency domain resources may include carriers, channels, frequency bands, etc. that the Tx UE 110 can use to communicate with the Rx UE 110. The CCA type may include the type of CCA (e.g., type 1 CCA or type 2 CCA) that the UE 110 is to perform before using the selected resources for SL communication. The time gap may include the amount of time that the Tx UE 110 can wait measured from receiving the SL DCI3_0 information before participating in the SL Tx. As described herein, the time gap may be the amount of time it takes for the UE 110-1 to process the SL DCI 3_0 information and perform the CCA procedure. The CP extension may indicate whether the UE 110 participating in the SL communication should implement the CP extension to help meet the timing gap in the SL COT sharing scenario.

[0071] Figure 8800 is a diagram of an example of components of a device according to one or more implementations described herein. In some implementations, the device 800 may include an application circuit 802, a baseband circuit 804, an RF circuit 806, a front-end module (FEM) circuit 808, one or more antennas 810, and a power management circuit (PMC) 812 (coupled together at least as shown). The components of the illustrated device 800 may be included in a UE or a RAN node. In some implementations, the device 800 may include fewer elements (e.g., the RAN node may not utilize the application circuit 802, but instead includes a processor / controller to process IP data received from the CN or the Evolved Packet Core (EPC)). In some implementations, the device 800 may include additional elements, such as, for example, a memory / storage device, a display, a camera, a sensor (including one or more temperature sensors, such as a single temperature sensor, multiple temperature sensors at different locations in the device 800, etc.) or an input / output (I / O) interface. In other implementations, the components described below may be included in more than one device (eg, the circuitry may be included solely in more than one device for a Cloud-RAN (C-RAN) implementation).

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

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

[0074] In some specific implementations, the memory 804G may receive and store one or more configurations, instructions, and / or other information for the SL DCI 3_0 for resource selection mode 1. The SL DCI 3_0 may include frequency resource assignment information, time resource assignment information, CCA type information, time gap information, and CP extension information. The frequency resource assignment information may indicate whether a partial BW or a full BW is allocated to the UE 110, and whether the assigned frequency resources are interleaved waveform resources or continuous waveform resources. The time resource assignment information may include the type of CCA to be performed by the UE, the time gap between the reception of the SL DCI 3_0 and the first SL transmission, and whether CP extension is to be used during SL communication (e.g., between the completion of the CCA procedure and the first SL transmission or to ensure that the gap between SL transmissions for a shared COT scenario is observed).

[0075] SL DCI 3_0 may also include multi-TTI scheduling information, which may include continuous SL transmission or non-continuous SL transmission. In such a scenario, SL DCI 3_0 may also include HARQ information for one or more of the multi-TTI SL transmissions. In some specific implementations, SL DCI 3_0 may include multiple starting positions for SL transmission. The starting position may start at a time slot boundary, halfway between time slot boundaries, and may depend on whether a partial BW or a full BW is allocated to the UE. In some specific implementations, SL DCI 3_0 may include a bidirectional SL DCI 3_0 transmitted by a base station to multiple UEs. The UE may receive the bidirectional SL DCI 3_0 so as to be within the coverage area of ​​the base station and / or within a logical group of UEs determined by the base station.

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

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

[0078] The RF circuit 806 may enable communication with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various specific implementations, the RF circuit 806 may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuit 806 may include a receive signal path, which may include circuits for down-converting RF signals received from the FEM circuit 808 and providing baseband signals to the baseband circuit 804. The RF circuit 806 may also include a transmit signal path, which may include circuits for up-converting baseband signals provided by the baseband circuit 804 and providing RF output signals to the FEM circuit 808 for transmission.

[0079] In some implementations, the receive signal path of the RF circuit 806 may include a mixer circuit 806A, an amplifier circuit 806B, and a filter circuit 806C. In some implementations, the transmit signal path of the RF circuit 806 may include a filter circuit 806C and a mixer circuit 806A. The RF circuit 806 may also include a synthesizer circuit 806D for synthesizing the frequencies used by the mixer circuit 806A of the receive signal path and the transmit signal path. In some implementations, the mixer circuit 806A of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 808 based on the synthesized frequency provided by the synthesizer circuit 806D. The amplifier circuit 806B may be configured to amplify the down-converted signal, and the filter circuit 806C 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 the baseband circuit 804 for further processing. In some implementations, the output baseband signal can be a zero frequency baseband signal, but this is not required.In some implementations, the mixer circuit 806A of the receive signal path can include a passive mixer, but the scope of the implementations is not limited in this respect.

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

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

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

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

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

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

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

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

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

[0089] The FEM circuitry 808 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 810, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 806 for further processing. The FEM circuitry 808 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 806 for transmission through one or more of the one or more antennas 810. In various implementations, amplification by the transmit signal path or the receive signal path may be performed only in the RF circuitry 806, only in the FEM circuitry 808, or in both the RF circuitry 806 and the FEM circuitry 808.

[0090] In some implementations, the FEM circuitry 808 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 a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuitry 806). The transmit signal path of the FEM circuitry 808 may include a power amplifier (PA) to amplify an input RF signal (e.g., provided by the RF circuitry 806); and one or more filters to generate an RF signal for subsequent transmission (e.g., via one or more of the one or more antennas 810).

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

[0092] and Figure 8The PMC 812 is shown coupled only to the baseband circuit 804. However, in other implementations, the PMC 812 may additionally or alternatively be coupled to other components (such as, but not limited to, the application circuit 802, the RF circuit 806, or the FEM 808) and perform similar power management operations for the other components.

[0093] In some implementations, the PMC 812 can control or otherwise be part of various power saving mechanisms of the device 800. For example, if the device 800 is in the RRC_Connected state, where the device is still connected to the RAN node because it expects to receive traffic immediately, then after a period of inactivity, the device can enter a state known as a discontinuous reception mode.

[0094] During this state, the device 800 may be powered off for short time intervals, thereby saving power.

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

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

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

[0098] Fig. 9 is a block diagram illustrating components that can read instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methods discussed herein, according to some example implementations. Specifically, Fig. 9 A diagrammatic representation of hardware resources 900 is shown, including one or more processors (or processor cores) 910, one or more memory / storage devices 920, and one or more communication resources 930, each of which may be communicatively coupled via a bus 940. For specific implementations where node virtualization (e.g., NFV) is utilized, a hypervisor 902 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 900.

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

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

[0101] In some specific implementations, the memory / storage device 920 may receive and store one or more configurations, instructions, and / or other information 955 for the SL DCI 3_0 for resource selection mode 1. The SL DCI 3_0 955 may include frequency resource assignment information, time resource assignment information, CCA type information, time gap information, and CP extension information. The frequency resource assignment information may indicate whether a partial BW or a full BW is allocated to the UE 110, and whether the assigned frequency resources are interleaved waveform resources or continuous waveform resources. The time resource assignment information may include the type of CCA to be performed by the UE, the time gap between the reception of the SL DCI 3_0 and the first SL transmission, and whether CP extension is to be used during SL communication (e.g., between the completion of the CCA procedure and the first SL transmission or to ensure that the gap between SL transmissions for a shared COT scenario is observed). The SL DCI 3_0 may also include multi-TTI scheduling information, which may include continuous SL transmission or non-continuous SL transmission. In such a scenario, the SL DCI 3_0 may also include HARQ information for one or more of the multi-TTI SL transmissions. In some implementations, the SL DCI 3_0 may include multiple starting positions for SL transmissions. The starting position may start at a time slot boundary, midway between time slot boundaries, and may depend on whether a partial BW or a full BW is allocated to the UE. In some implementations, the SL DCI 3_0 may include a bidirectional SL DCI 3_0 transmitted by the base station to multiple UEs. The UE may receive the bidirectional SL DCI 3_0 so as to be within the coverage area of ​​the base station and / or within a logical group of UEs determined by the base station.

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

[0103] The instructions 950 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 910 to perform any one or more of the methods discussed herein. The instructions 950 may reside completely or partially in at least one of the processors 910 (e.g., within a cache memory of the processor), the memory / storage device 920, or any suitable combination thereof. In addition, any portion of the instructions 950 may be transmitted to the hardware resources 900 from any combination of the peripheral device 904 or the database 906. Therefore, the memory of the processor 910, the memory / storage device 920, the peripheral device 904, and the database 906 are examples of computer-readable media and machine-readable media.

[0104] Fig.10 1000 is a diagram of an example process for using SL DCI 3_0 according to one or more implementations described herein. Process 1000 may be implemented by UE 110-1, UE 110-2, and base station 122. In some implementations, some or all of process 1000 may be implemented by one or more other systems or devices (including Figure 1 In addition, process 1000 may include: Fig.10 The operations shown may be fewer, additional, differently ordered, and / or arranged than those shown. In some implementations, some or all of the operations of process 1000 may be performed independently, sequentially, simultaneously, etc., with one or more of the other operations of process 1000. Thus, the techniques described herein are not limited to Fig.10 The number, sequence, arrangement, timing, etc. of the operations or processes depicted in the .

[0105] As shown, process 1000 may include receiving SL DCI 3_0 from base station 122 (block 1010). For example, UE 110 may receive SL DCI 3_0 information from base station 122. In some implementations, SL DCI 3_0 information may be received as part of DG. In other implementations, SL DCI 3_0 information may be received as part of CG. As described herein, SL DCI3_0 955 may include frequency resource assignment information, time resource assignment information, CCA type information, time slot information, CP extension information, etc.

[0106] Process 1000 may also include selecting SL resources based on SL DCI 3_0 (block 1020). For example, UE 110 may use SL DCI 3_0 information to select SL resources based on SL DCI 3_0 information. As described herein, this may include, for example, UE 110 processing received SL DCI 3_0 information to identify SL resources indicated by the SL DCI 3_0 information. SL resources may include frequency domain resources, time domain resources, performing a CCA procedure based on the SL DCI 3_0 information, etc.

[0107] Process 1000 may include communicating with another UE 110 based on the selected SL resources (block 1030). For example, UE 110 may transmit a SL signal to another UE 110 using resources (e.g., frequency domain resources, timing domain resources, etc.) selected based on the received SL DCI 3_0 information. In some implementations, the SL signal may be in an unlicensed spectrum, the UE 110 may transmit the signal in response to a successful CCA procedure, and the SL signal may initiate additional SL communication (e.g., SL COT sharing) between the UEs 110.

[0108] Fig.11 1100 is a diagram of an example process for providing SL DCI 3_0 according to one or more implementations described herein. Process 1100 may be implemented by UE 110-1, UE 110-2, and base station 122. In some implementations, part or all of process 1100 may be performed by one or more other systems or devices, including Figure 1 In addition, process 1100 may include one or more Fig.11 In some implementations, some or all of the operations of process 1100 may be performed independently, sequentially, simultaneously, etc., relative to one or more other operations of process 1100. Therefore, the techniques described herein are not limited to Fig.11 The number, sequence, arrangement, timing, etc. of the operations or processes shown.

[0109] As shown, process 1100 may include receiving a request for SL resources from UE 110 (block 1110). For example, base station 122 may receive a request for SL resources from UE 110. The request for SL resources may correspond to a request for frequency domain resources, timing domain resources, etc. in an unlicensed spectrum. In some implementations, the request may correspond to a DG scenario.

[0110] Process 1100 may include determining a SL DCI 3_0 for UE 110 (block 1120). For example, base station 122 may determine SL DCI 3_0 information for UE 110. In some implementations, such as a DG scenario, base station 122 may determine the SL DCI 3_0 information in response to receiving a grant request or another type of request for SL resources. In some implementations, such as a CG scenario, base station 122 may of course determine the SL DCI 3_0 information (e.g., as part of an attachment procedure or another process). In some implementations, the SL DCI 3_0 information may be cell-specific, UE-specific, or UE group-specific.

[0111] Process 1100 may include providing SL DCI 3_0 to the UE for SL communication (block 1130). For example, base station 122 may transmit SL DCI 3_0 information to UE 110. In some implementations, base station 122 may do so via a PDCCH to UE 110. In some implementations, RRC signaling may be used. As described herein, SL DCI 3_0 information may enable UE 110 to establish SL communication with another UE 110.

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

[0113] In embodiment 1, which may also include one or more of the embodiments described herein, a user equipment (UE) may include: a memory; and one or more processors, the one or more processors being configured to, when executing instructions stored in the memory, cause the UE to: receive downlink control information (DCI) from a base station for communicating with another UE via a side link (SL); select SL resources based on the DCI; and communicate with the other UE via the SL according to the SL resources. In embodiment 2, which may also include one or more of the embodiments described herein, the DCI is DCI 3_0 for mode 1 SL resource selection.

[0114] In embodiment 3, which may also include one or more of the embodiments described herein, the DCI includes: frequency domain resources; time domain resources; clear channel assessment (CCA) type; and cyclic prefix (CP) extension. In embodiment 4, which may also include one or more of the embodiments described herein, the DCI includes a type 1 CCA and a priority category based on a SL scheduling request (SR) and / or a buffer status report (BSR). In embodiment 5, which may also include one or more of the embodiments described herein, when a scheduled transmission based on the DCI is within a shared channel occupancy time (COT) allocated to different UEs, the DCI includes a type 2 CCA.

[0115] In embodiment 6, which may also include one or more of the embodiments described herein, the DCI includes a CP extension configured to enable SL communication involving gaps of a shared COT. In embodiment 7, which may also include one or more of the embodiments described herein, the DCI includes a CP extension based on whether the frequency domain resources of the DCI include a partial bandwidth (BW) or a full BW. In embodiment 8, which may also include one or more of the embodiments described herein, the frequency domain resources of the DCI include a partial BW and a starting position for SL transmission using the partial BW.

[0116] In embodiment 9, which may also include one or more of the embodiments described herein, the frequency domain resources of the DCI include a full BW and a set of starting positions for random selection for SL transmission using the full BW. In embodiment 10, which may also include one or more of the embodiments described herein, the DCI includes multi-transmission time interval (multi-TTI) scheduling for SL transmission. In embodiment 11, which may also include one or more of the embodiments described herein, the DCI includes a first hybrid automatic repeat request (HARQ) ID for a first TTI, and the UE will determine a subsequent HARD ID based on the HARQ ID for the first TTI.

[0117] In embodiment 12, which may also include one or more of the embodiments described herein, the DCI includes HARQ information for each of the SL transmissions scheduled for the multi-TTI. In embodiment 13, which may also include one or more of the embodiments described herein, the DCI includes multiple starting positions for the SL transmissions scheduled for the multi-TTI. In embodiment 14, which may also include one or more of the embodiments described herein, the UE is configured to transmit using a second starting position for the SL transmission when a CCA procedure is unsuccessful before a first starting position for the SL transmission.

[0118] In embodiment 15, which may also include one or more of the embodiments described herein, the DCI includes a bidirectional DCI involving the UE and the other UE, and the bidirectional DCI includes resource selection for the UE and the other UE. In embodiment 16, which may also include one or more of the embodiments described herein, the frequency domain resources of the DCI include interleaved waveform resources or continuous waveform resources. In embodiment 17, which may also include one or more of the embodiments described herein, a method performed by a user equipment (UE) may include: receiving downlink control information (DCI) for communicating with another UE via a side link (SL) from a base station; selecting SL resources based on the DCI; and communicating with the other UE via the SL according to the SL resources.

[0119] In embodiment 18, which may also include one or more of the embodiments described herein, a base station may include: a memory; and one or more processors, the one or more processors being configured to, when executing instructions stored in the memory, cause the base station to: determine downlink control information (DCI) for sidelink (SL) resource selection; and transmit the DCI to a UE. In embodiment 19, which may also include one or more of the embodiments described herein, a method performed by a base station may include: determining downlink control information (DCI) for sidelink (SL) resource selection; and transmitting the DCI to a UE.

[0120] The above description of illustrative 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, etc. are described herein for illustrative purposes, various modifications can be considered within the scope of such examples, implementations, aspects, etc., as can be appreciated by those skilled in the relevant art.

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

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

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

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

Claims

1. A user equipment (UE), comprising: Memory; as well as one or more processors, the one or more processors being configured to, when executing instructions stored in the memory, cause the UE to: receiving downlink control information (DCI) from a base station for communicating with another UE via a side link (SL); selecting a SL resource based on the DCI; and Communicate with the other UE via the SL according to the SL resources.

2. The UE according to claim 1, wherein the DCI is DCI 3_0 for mode 1SL resource selection.

3. The UE according to claim 1, wherein the DCI comprises: Frequency domain resources; Time domain resources; Clear Channel Assessment (CCA) type; as well as Cyclic Prefix (CP) extension.

4. The UE according to claim 1, wherein the DCI includes a type 1 CCA and a priority class based on a SL scheduling request (SR) and / or a buffer status report (BSR).

5. The UE of claim 1, wherein the DCI comprises a Type 2 CCA when a scheduled transmission based on the DCI is within a shared channel occupancy time (COT) allocated to a different UE. 6 . The UE of claim 1 , wherein the DCI includes a CP extension configured to enable SL communication involving gaps of a shared COT. 7 . The UE of claim 1 , wherein the DCI comprises a CP extension based on whether a frequency domain resource of the DCI comprises a partial bandwidth (BW) or a full BW.

8. The UE according to claim 1, wherein the frequency domain resources of the DCI include a portion of the BW and a starting position for using the portion of the BW for SL transmission. 9 . The UE according to claim 1 , wherein the frequency domain resources of the DCI include a full BW and a set of starting positions for random selection for SL transmission using the full BW.

10. The UE of claim 1, wherein the DCI includes a multi-transmission time interval (multi-TTI) schedule for SL transmission.

11. The UE of claim 11, wherein the DCI includes a first hybrid automatic repeat request (HARQ) ID for a first TTI, and the UE is to determine a subsequent HARQ ID based on the HARQ ID for the first TTI.

12. The UE according to claim 11, wherein the DCI includes HARQ information for each of the SL transmissions scheduled by the multi-TTI. 13 . The UE according to claim 11 , wherein the DCI includes a plurality of starting positions of the SL transmission for the multi-TTI scheduling.

14. The UE according to claim 13, wherein the UE is configured to transmit using a second starting position for the SL transmission when a CCA procedure is unsuccessful before the first starting position for the SL transmission. 15 . The UE according to claim 11 , wherein the DCI comprises a bidirectional DCI involving the UE and the another UE, the bidirectional DCI comprising resource selection for the UE and the another UE. 16 . The UE according to claim 1 , wherein the frequency domain resources of the DCI include interleaved waveform resources or continuous waveform resources.

17. A method performed by a user equipment (UE), comprising: receiving downlink control information (DCI) from a base station for communicating with another UE via a side link (SL); selecting a SL resource based on the DCI; as well as Communicate with the other UE via the SL according to the SL resources.

18. The method of claim 17, wherein the DCI comprises: Frequency domain resources; Time domain resources; Clear Channel Assessment (CCA) type; as well as Cyclic Prefix (CP) extension.

19. A base station, comprising: Memory; as well as one or more processors configured to, when executing instructions stored in the memory, cause the base station to: determining downlink control information (DCI) for sidelink (SL) resource selection; and The DCI is transmitted to the UE.

20. The base station according to claim 19, wherein the DCI comprises: Frequency domain resources; Time domain resources; Clear Channel Assessment (CCA) type; as well as Cyclic Prefix (CP) extension.

Images