Sidelink reference signal for positioning

Abstract

The present application relates to apparatuses and components, systems, and methods including apparatuses for configuring and using reference signals for positioning in device-to-device communications, such as sidelink communications between two UEs. Configuration information may be generated for a device, and the configuration information may indicate sidelink resources in a resource pool configured as reference signals for positioning. In the time domain, the configuration may be at a slot level or a symbol level. The configured sidelink resources may be indexed in the time domain and the frequency domain. Control information may be transmitted to indicate a next transmission of a reference signal for positioning. The control information may implicitly or explicitly indicate a configured sidelink resource to be used in the next transmission.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 63 / 336,223, filed on April 28, 2022. The contents of that application are hereby incorporated by reference in their entirety for all purposes. Background Art

[0003] The fifth generation of mobile networks (5G) is a wireless standard that aims to improve data transmission speed, reliability, availability, etc. Although still under development, this standard includes many details related to the use of channels between devices, such as between base stations and user equipment (UE), or between UEs. In the latter case, the channel between UEs can be called a sidelink channel. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Figure 1 An example of a network environment according to some embodiments is shown.

[0005] Figure 2 An example of a resource pool that may be used for sidelink transmissions is shown according to some embodiments.

[0006] Figure 3 An example of a configuration of a sidelink reference signal for positioning (SL RSP) is shown according to some embodiments.

[0007] Figure 4 Another example of a configuration for a SL RSP according to some embodiments is shown.

[0008] Figure 5 Yet another example of a configuration for a SL RSP according to some embodiments is shown.

[0009] Figure 6 Yet another example of a configuration for a SL RSP according to some embodiments is shown.

[0010] Figure 7 Examples of resource indexing for SL RSP according to some embodiments are shown.

[0011] Figure 8 Another example of resource indexing for SL RSP according to some embodiments is shown.

[0012] Fig. 9 An example of resource allocation for SL RSP according to some embodiments is shown.

[0013] Fig.10 An example of a time gap between a sidelink transmission and an SL RSP transmission is shown according to some embodiments.

[0014] Fig.11 An example of an operational flow / algorithm structure for SL RSP transmission according to some embodiments is shown.

[0015] Fig.12 An example of an operational flow / algorithm structure for SL RSP reception according to some embodiments is shown.

[0016] Fig.13 An example of a receiving component according to some embodiments is shown.

[0017] Fig.14 Examples of UEs according to some embodiments are shown.

[0018] Fig.15 An example of a base station according to some embodiments is shown. DETAILED DESCRIPTION

[0019] The following specific embodiments relate to the accompanying drawings. The same figure numbers may be used to identify the same or similar elements in different drawings. In the following description, for the purpose of illustration and not limitation, specific details, such as specific structures, architectures, interfaces, technologies, etc., are set forth to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to those skilled in the art who benefit from the present disclosure that various aspects of various embodiments may be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted so that the descriptions of various embodiments are not obscured by unnecessary details. For the purposes of this document, the phrase "A or B" refers to (A), (B), or (A and B).

[0020] Generally speaking, in a device-to-device communication scheme, a first device can communicate with a second device. This type of communication can occur on a sidelink channel, which in 5G cellular networks is referred to as a physical sidelink shared channel (PSSCH) carrying data or a physical sidelink control channel (PSCCH) carrying control information. The first device can transmit a sidelink reference signal for positioning (abbreviated herein as "SL RSP", where "S" refers to sidelink and "RSP" refers to a reference signal for positioning). The second device can perform one or more measurements on the SL RSP to determine a location (e.g., the location of the second device or the location of the first device).

[0021] In order to implement device positioning using SL RSP transmission and measurement, the side link resources of the side link channel (e.g., PSSCH and / or PSCCH) may be initially configured to be available for SL RSP. Subsequently, side link control information (SCI) may be sent from the first device before the SL RSP is sent, so that the second device may receive the sent SL RSP using the configured side link resources.

[0022] In an example, sidelink resources are configured for the SL RSP (e.g., by the first device), where the resources may include time slots of the sidelink channel that may be used for the SL RSP and / or symbols within one or more of such time slots. In the frequency domain, the sidelink resources may occupy comb-shaped resource elements and may be distributed along the entire bandwidth of the sidelink channel or a portion of the bandwidth. The resource elements may be indexed by frequency first and then by time, or vice versa.

[0023] In an example, the SCI may explicitly indicate the side link resources allocated for the next SL RSP transmission. Alternatively, the SCI may explicitly indicate the PSSCH and / or PSCCH resources and implicitly indicate the side link resources for the next SL RSP transmission. The implicit indication may depend on the explicit indication of the PSSCH and / or PSCCH resources.

[0024] The following is a glossary of terms that may be used in this disclosure.

[0025] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or a memory (shared, dedicated, or group) configured to provide the described functions, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable system on chip (SoC)), a digital signal processor (DSP), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuit" may also refer to a combination of one or more hardware elements and a program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0026] As used herein, the term "processor circuit" refers to, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transferring digital data. The term "processor circuit" may refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions such as program code, software modules, and / or functional processes.

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

[0028] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can describe a remote user of network resources in a communication network. In addition, the term "user equipment" or "UE" may be considered synonymous and may be referred to as a client, device, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface. A UE may have the primary function of communicating with another UE or a network, and a UE may be integrated with other devices and / or systems (e.g., in a vehicle).

[0029] The term "base station" as used herein refers to a device with radio communication functionality, i.e., a device of a communication network (or more simply, a network), and can be configured as an access node in the communication network. Access of a UE to a communication network may be at least partially managed by a base station, whereby the UE connects to the base station to access the communication network. Depending on the radio access technology (RAT), a base station may be referred to as a gNodeB (gNB), an eNodeB (eNB), an access point, etc.

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

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

[0032] As used herein, the term "channel" refers to any tangible or intangible transmission medium for delivering data or data streams. The term "channel" may be synonymous or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" or any other similar term representing a path or medium through which data is delivered. In addition, as used herein, the term "link" refers to a connection made between two devices for sending and receiving information.

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

[0034] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0035] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, networking hardware, network equipment, network node, virtualized network function, etc.

[0036] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains the contents. An information element may include one or more additional information elements.

[0037] Figure 1 A network environment 100 is shown according to some embodiments. The network environment 100 may include a UE 104 and a gNB 108. The gNB 108 may be a base station that provides a wireless access cell, such as a third generation partnership project (3GPP) new radio (NR) cell through which the UE 104 can communicate with the gNB 108. The UE 104 and the gNB 108 may communicate over an air interface compatible with 3GPP technical specifications, such as those defining the fifth generation (5G) NR system standard.

[0038] The gNB 108 may send information (e.g., data and control signaling) in the downlink direction by mapping logical channels onto transport channels and mapping transport channels onto physical channels. Logical channels may transfer data between the radio link control (RLC) and MAC layers; transport channels may transfer data between the MAC and PHY layers; and physical channels may transfer information across the air interface. Physical channels may include a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH), and a physical downlink shared channel (PDSCH).

[0039] The PBCH may be used to broadcast system information that the UE 104 may use to initially access a serving cell. The PBCH may be sent in a synchronization signal (SS) / PBCH block along with a physical synchronization signal (PSS) and a secondary synchronization signal (SSS). The UE 104 may use the SS / PBCH block (SSB) during a cell search procedure (including cell selection and reselection) and for beam selection.

[0040] The PDSCH may be used to transfer end-user application data, Signaling Radio Bearer (SRB) messages, system information messages (in addition to, for example, the MIB), and paging messages.

[0041] The PDCCH may convey DCI used by the scheduler of the gNB 108 to allocate both uplink and downlink resources. The DCI may also be used to provide uplink power control commands, configure the slot format, or indicate that preemption has occurred.

[0042] The gNB 108 may also transmit various reference signals to the UE 104. The reference signals may include DMRS for the PBCH, PDCCH, and PDSCH. The UE 104 may compare the received version of the DMRS with the known DMRS sequence transmitted to estimate the impact of the propagation channel. The UE 104 may then apply the inverse channel of the propagation channel during the demodulation process of the corresponding physical channel transmission.

[0043] Reference signals may also include a channel state information reference signal (CSI-RS). CSI-RS may be a multi-purpose downlink transmission that may be used for CSI reporting, beam management, connected mode mobility, radio link failure detection, beam failure detection and recovery, and fine tuning of time and frequency synchronization.

[0044] Reference signals and information from physical channels can be mapped to resources of a resource grid. For a given antenna port, subcarrier spacing configuration, and transmission direction (e.g., downlink or uplink), there is a resource grid. The basic unit of the NR downlink resource grid can be a resource element, which can be defined by one subcarrier in the frequency domain and one orthogonal frequency division multiplexing (OFDM) symbol in the time domain. Twelve consecutive subcarriers in the frequency domain can constitute a physical resource block (PRB). A resource element group (REG) can include one PRB in the frequency domain and one OFDM symbol in the time domain, such as twelve resource elements. A control channel element (CCE) can represent a resource group used to send a PDCCH. One CCE can be mapped to multiple REGs, for example, six REGs.

[0045] UE 104 may use physical uplink channels to send data and control information to gNB 108. Different types of physical uplink channels are possible, including, for example, a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH). Where PUCCH carries control information from UE 104 to gNB 108, such as uplink control information (UCI), while PUSCH carries data traffic (e.g., end-user application data) and may carry UCI.

[0046] The UE 104 and the gNB 108 may perform beam management operations to identify and maintain desired beams for transmission in the uplink and downlink directions. Beam management may be applied to both PDSCH and PDCCH in the downlink direction and PUSCH and PUCCH in the uplink direction.

[0047] In an example, communications with the gNB 108 and / or base stations may use channels on a frequency range 1 (FR1) band, a frequency range 2 (FR2) band, and / or a high frequency range (FRH) band. The FR1 band includes licensed bands and unlicensed bands. The NR unlicensed band (NR-U) includes spectrum shared with other types of radio access technologies (RATs) (e.g., LTE-LAA, WiFi, etc.). A listen-before-talk (LBT) procedure may be used to avoid or minimize collisions between different RATs in NR-U, whereby a device should apply a clear channel assessment (CCA) check before using a channel.

[0048] like Figure 1As further shown, the network environment 100 may also include another UE 106 to which the gNB 108 may be connected in a manner similar to the gNB 108-UE 104 connection. UE 104 may also be connected to UE 106 by using sidelink channels. These sidelink channels may include PSSCH and PSCCH. PSSCH may be similar to PDSCH and may carry data in a one-to-one or one-to-many scheme. In other words, UE 104 may be a transmitter device that sends data on PSSCH to one or more devices (including UE 106), or may be a receiver device in a set of devices that receives data on PSSCH from UE 106. PDSCH may be similar to PDCCH and may carry sidelink control information (SCI). SCI is similar to DCI and includes information about resource allocations for PSSCH.

[0049] In the case of use of a side link channel, a transmitter device may represent a UE that transmits an SCI to a receiver device, where the receiver device may represent another UE that receives the SCI. The transmitter device may also send an SL RSP, and the receiver device receives the SL RSP and performs measurements on it to determine the location of the receiver device or the transmitter device. For clarity of explanation, such transmitter devices and receiver devices are described herein as transmitter UEs (e.g., UE 104) and receiver UEs (e.g., UE 106), respectively. The transmitter device and the receiver device may be any type of device that is capable of supporting at least side link communications, and may include any one of mobile cellular devices, vehicle-to-everything (V2X) devices, public safety devices, commercial devices, Industrial Internet of Things (IIOT) devices, etc., or a combination thereof.

[0050] Figure 2 An example of a resource pool 200 that can be used for sidelink transmission according to some embodiments is shown. The resource pool 200, shown from the perspective of a transmitter device (e.g., UE 104), configures a resource pool for a receiver device (e.g., UE 106), wherein the resource pool 200 includes resource units that can be used to carry SL RSP. However, the resource pool 200 is equally applicable to receiver devices.

[0051] Generally speaking, a resource pool is a set of resources defined in the time and frequency domains. In the time domain, resources use multiple time slots. The time slots can be, but need not be, consecutive ( Figure 2Non-continuous time slots are shown). Each time slot may include multiple symbols (such symbols are further shown in the following figures). The time slot may be repeated according to a specific periodicity (e.g., 10, 240ms). The time slot may generally be referred to as a physical time slot, in which case the physical time slot includes a side link time slot and a non-side link time slot (e.g., a non-side link time slot is a time slot that does not belong to the resource pool 200). The time slots belonging to the resource pool 200 (e.g., the side link time slot) may be referred to as logical time slots. A bitmap may be used to indicate a logical time slot within a time period, and the applicability of the bitmap may be repeated according to the periodicity. The bitmap may have a length of ten bits, eleven bits, ..., one hundred and sixty bits, or at least some other length that depends on the number of time slots.

[0052] In the frequency domain, a resource uses multiple subchannels. Generally speaking, the subchannels are continuous. Each subchannel includes multiple subcarriers (for example, one hundred and twenty subcarriers, each subcarrier is 15kHz or larger).

[0053] like Figure 2 As shown, in both the time domain and the frequency domain, a resource corresponds to a resource unit (e.g., a time slot and a subchannel unit). A resource unit may include multiple resource elements, each of which corresponds to a single orthogonal frequency division multiplexing (OFDM) symbol in the time domain and a single subcarrier in the frequency domain.

[0054] The transmitter device may configure a resource pool 200 to the receiver device. Some of the configured resources may be used for PSSCH and / or PSCCH transmission. As used herein, a sidelink channel refers to either PSSCH and PSCCH or a combination thereof. PSSCH and / or PSCCH may be abbreviated as PSSCH / PSCCH or a sidelink channel herein. Some of the configured resources may also be used for sending SL RSP by the transmitter device and receiving SL RSP by the receiving device. SL RSP may be a reference signal transmitted by the transmitter device to the receiver device on a sidelink channel (e.g., by using relevant resources of the resource pool 200) for positioning purposes. Additionally or alternatively, SL RSP may be a reference signal transmitted from a receiver device on a sidelink channel to a transmitter device for positioning purposes (e.g., similar to a sounding reference signal (SRS) transmitted on a PUSCH or PUCCH).

[0055] Embodiments of the present disclosure relate to various techniques for configuring a resource pool 200 so that resources are available for SL RSP transmission, indexing such resources, and indicating resource allocation (e.g., via SCI). In one example, in the time domain, resources may be configured at a slot granularity level and / or at a symbol granularity level, where the resources may be PSSCH / PSCCH resources that have been repurposed or resources that may be available for a side link channel but are not yet included in the resource pool 200. In the frequency domain, resources using subchannels may use multiple subcarriers of a subchannel (e.g., in a comb-like manner) and may span the entire bandwidth or a portion of the bandwidth. Thus, the resource may include multiple resource elements (in the time domain and the frequency domain), and these resource elements may be indexed first by frequency and then by time, or first by time and then by frequency. The SCI may explicitly or implicitly indicate the resources of the resource pool 200 that are scheduled for SL RSP transmission. The following figures further describe these and other features.

[0056] Figure 3 An example of a configuration 300 for SL RSP according to some embodiments is shown. In this illustration, a single subchannel is shown in the frequency domain and multiple time slots are shown in the time domain. The number of time slots is 10,240·2 μ , where "μ" is a parameter set. The same number "N" of available time slots for the sidelink channel repeats so that the resource pool can have a specific periodicity (in Figure 3 The time slots may be indexed using a system frame number (SFN) or a direct frame number (DFN), where the first time slot is indexed as "0" and the last time slot is indexed as "10,240·2 μ -1".

[0057] The resource pool includes different time slots, except for time slots that can be used for side link synchronization signal (SLSS) (shown by left-slanting dashed rectangles), time slots without enough uplink symbols (shown by vertical dashed rectangles), and reserved time slots (shown by solid dark rectangles). The number of SLSS time slots is The number of time slots without enough uplink symbols is N 非SL , and includes slots in which at least the Yth, (Y-1)th, ..., (Y+X-1)th symbols in the slot are not semi-statically used for the uplink, as indicated in TDD-UL-DL-ConfigCommon, where "X" is the configured number of symbols per sidelink slot and "Y" is the sidelink starting symbol index in the slot. The number of reserved slots is And such time slots are usually evenly distributed across each resource cycle.

[0058] The remaining time slots are time slots that can be used for the side link and are either included in the resource pool or excluded from the resource pool. The first bitmap (shown as a PSSCH / PSCCH bitmap) indicates whether such time slots are included in the resource pool or excluded from the resource pool. In particular, each bit in the bitmap corresponds to one of the time slots, and the bit value of the bit indicates inclusion (e.g., when the bit value is "1") or exclusion (e.g., when the bit value is "0"). Figure 3 In the illustration of , the first bitmap includes ten bits. The bit values ​​of the first six bits and the last three bits are set to "1", and the bit value of the seventh bit is set to "0". Thus, the bitmap indicates that the first six time slots and the last three time slots (their indexes are defined relative to the SFN or DFN rather than the bit position in the first bitmap) that can be used for the side link are included in the resource pool, while the seventh time slot is excluded from the resource pool. The time slots included in the resource pool and available for PSSCH / PSCCH are shown with blank rectangles.

[0059] In the example, configuration 300 is at the time slot level and indicates that resources that can be used for the side link but are excluded from the resource pool are now included in the resource pool for the purpose of SL RSP transmission. In other words, the resource is a dedicated time slot for SL RSP transmission. Multiple dedicated time slots can be allocated for SL RSP and can be configured separately from PSSCH / PSCCH resources (resources corresponding to blank rectangles). For example, configuration 300 may include first configuration information specific to PSSCH / PSCCH resources and second configuration information specific to SL RSP. The first configuration information may include a first bitmap, and the second configuration may include a second bitmap (shown as a positioning bitmap). The second bitmap includes a bit indicating whether a time slot that can be used for the side link is included in the resource pool for the purpose of SL RSP transmission. Assuming that the time slot can be dedicated to SL RSP transmission, the time slot will not be available for PSSCH / PSCCH resources. Thus, the bit values ​​of the second figure cannot conflict with the bit values ​​of the first bitmap. In particular, if the first bitmap indicates that the time slot is available for the side link (e.g., for PSSCH / PSCCH transmission) and is included in the resource pool (e.g., by using a bit value of "1" for the corresponding bit in the first bitmap), the second bitmap indicates that the time slot is not available for SL RSP transmission (e.g., by using a bit value of "0" for the corresponding bit in the second bitmap). In contrast, if the first bitmap indicates that the time slot is available for the side link (e.g., for PSSCH / PSCCH transmission) and is excluded from the resource pool (e.g., by using a bit value of "0" for the corresponding bit in the first bitmap), the second bitmap indicates that the time slot is (i) available for SL RSP transmission (e.g., by using a bit value of "1" for the corresponding bit in the second bitmap) and is therefore included in the resource pool, or (ii) not available for SL RSP transmission (e.g., by using a bit value of "0" for the corresponding bit in the second bitmap) and therefore remains excluded from the resource pool. However, when the first bitmap indicates that a time slot is included in the resource pool, the second bitmap may not indicate that the same time slot is available for the SLRSP (eg, both bitmaps set the bit values ​​of corresponding bits to the same bit value "1").

[0060] exist Figure 3 In the illustration of FIG. 1 , the first bitmap indicates that the seventh time slot available for the side link is excluded from the resource pool (e.g., the corresponding seventh bit has a value of "0"). In contrast, the second bitmap indicates that the seventh time slot is included in the resource pool for SL RSP transmission (e.g., the corresponding seventh bit has a value of "1"). The SL RSP time slot is shown with a horizontal dashed rectangle. In contrast, the first bitmap indicates that the remaining nine time slots available for the side link are included in the resource pool (e.g., the corresponding nine bits have a value of "1"), while the second bitmap indicates that these nine time slots will not be used in SL RSP transmission.

[0061] In the example where a dedicated time slot for SL RSP transmission is configured separately from PSSCH / PSCCH resources, configuration 300 includes a resource pool configuration "sl-ResourcePool". Furthermore, the resource pool configuration includes a first bitmap and a second bitmap as "sl-TimeResource" and "sl-TimeResourcePositioning", respectively. In the bitmap "sl-TimeResourcePositioning", a bit value of "0" indicates that the corresponding time slot is not used for sidelink reference signal usage for positioning, and a bit value of "1" indicates that the corresponding time slot is used for sidelink reference signal usage for positioning. The bitmap "sl-TimeResourcePositioning" may have the same length as the bitmap "sl-TimeResource", where a position with a value of "1" in "sl-TimeResourcePositioning" may correspond to a position with a value of "0" in "sl-TimeResource".

[0062] Figure 4 Another example of a configuration 400 for a SL RSP is shown according to some embodiments. Figure 4 The diagram shows the different time slots that can be included in or excluded from a resource pool. These types of time slots are similar to Figure 3 For the sake of brevity, the similarities are not repeated herein. However, the description of these time slots is equivalently applicable to Figure 4 .

[0063] While configuration 300 configures resources for SL RSP transmission separately from the configuration of PSSCH / PSCCH resources, here configuration 400 jointly configures resources for SL RSP transmission and PSSCH / PSCCH resources. For example, instead of using two separate bitmaps, a single bitmap (shown herein as a joint bitmap) is used. The bits of the bitmap may use ternary values ​​(instead of Figure 3 A binary value in ): a value of "0" indicates that the time slots available for the side link are excluded from the resource pool, a value of "1" indicates that the time slots available for the side link are included in the resource pool for PSSCH / PSCCH transmission, and a value of "2" indicates that the time slots available for the side link are included in the resource pool for SL RSP transmission.

[0064] exist Figure 4In the illustration of , the joint bitmap indicates that the first six time slots available for the side link and the last three time slots available for the side link are included in the resource pool as PSSCH / PSCCH time slots (e.g., the corresponding bits have a value of "1"). In addition, the joint bitmap indicates that the seventh time slot available for the side link is included in the resource pool as an SL RSP time slot (e.g., the corresponding bit has a value of "2").

[0065] In the example of a dedicated time slot for SL RSP transmission, the dedicated time slot is configured jointly with the PSSCH / PSCCH resource. In this example, configuration 400 includes a resource pool configuration "sl-ResourcePool". In turn, the resource pool configuration includes a bitmap "sl-TimeResource" modified from a bit string to a ternary string, where "0" indicates that the corresponding time slot is used by the side link, "1" indicates that the corresponding time slot is used for PSSCH / PSCCH, and "2" indicates that the corresponding time slot is used for a side link reference signal for positioning.

[0066] exist Figure 3 and Figure 4 In the , the slot level configuration is used to indicate that the slot is included in the resource pool for PSSCH / PSCCH and is dedicated to SL RSP transmission. There are other variations. For example, the slot level configuration can be used and can be separated from the resource pool for PSSCH / PSCCH. In particular, the slot can be dedicated to the side link reference signal for positioning. These dedicated slots are not included in the PSSCH / PSSCH resources (similar to reserved slots, SLSS slots, and slots without enough uplink symbols being excluded from the PSSCH / PSSCH resource pool). Instead, the dedicated slots can be configured with a fixed periodicity (e.g., a 160ms period), similar to the side link synchronization signal block (SL SSB). For example, "SL-RSP-TimeAllocation" can be configured similarly to the way "SL-SSB-TimeAllocation" is configured.

[0067] Figure 5 Another example of a configuration 500 for SL RSP according to some embodiments is shown. Here, configuration 500 indicates that the time slot is dedicated to the sidelink reference signal for positioning and is included in the PSSCH / PSCCH resources (similar to configuration 300 or 400). The time slot level configuration is Figure 5 However, within a dedicated time slot, configuration 500 also indicates symbols configured for sidelink reference signals. This symbol level configuration is shown on the lower right side of the figure.

[0068] Starting with the slot level configuration, nine slots per subchannel are shown, and three subchannels are also shown. The resources dedicated to SL RSP transmissions are shown with horizontal dashed rectangles, while the resources used for PSSCH / PSCCH are shown with blank rectangles. Some symbols of a slot with PSSCH / PSCCH resources may be used for a physical sidelink feedback channel (PSFCH). For example, the last two symbols in a slot with PSSCH / PSCCH include PSFCH symbols (shown with dark solid rectangles). The PSFCH symbols may be configured with a specific PSFCH periodicity (e.g., repeating every two slots). The SL RSP slots may also have a SL RSP periodicity (e.g., repeating every eight slots). An offset may also be configured for the SL RSP slots (although in Figure 5 In other words, in configuration 500, the periodicity and offset are configured for the SL RSP.

[0069] In an example, if a PSSCH / PSCCH slot includes at least one PSFCH symbol, the slot cannot be repurposed for use as a dedicated SL RSP slot. For example, if the SL RSP periodicity is eight slots, the PSFCH periodicity is two slots, and a zero offset is used, the SL RSP slot may overlap with a PSSCH / PSCCH slot that includes a PSFCH symbol. In this case, the PSSCH / PSCCH slot is not repurposed for SL RSP transmission. Alternatively, it is allowed to repurpose PSSCH / PSCCH symbols as SL RSP symbols, whereby PSFCH symbols are also repurposed for use as SL RSP symbols, or PSFCH symbols are not repurposed.

[0070] Referring now to the symbol level configuration, a slot dedicated to SL RSP (e.g., SL RSP slot) includes a number of OFDM symbols (e.g., fourteen). In the SL RSP slot, every "X" consecutive OFDM symbols define a symbol group and can be used for SL RSP. Figure 5In the illustration of , "X" is equal to two, but different numbers are possible. Each symbol group may be associated with a transmitter device-receiver device pair (e.g., different symbol groups may be used by different device pairs in a time division multiplexed manner). The same content may be repeated in an OFDM symbol group. The first OFDM symbol (or the first "Y" number of such symbols, where "Y" is strictly less than "X") may be used for automatic gain control (AGC). The remaining OFDM symbols in the OFDM symbol may be used for positioning purposes (e.g., as actual SL RSP symbols). The number "X" and / or the number "Y" may be predefined, or may be configured for each resource pool (e.g., indicated in the configuration information defining configuration 500). Thus, the SL RSP resources are arranged in OFDM symbol groups in the time domain, and each symbol group in the symbol group may be used for a device pair (although multiple symbol groups in the same SL RSP time slot may be used by the same device pair). A number "Z" of slot symbols may be used (in Figure 5 In the illustration of , "Z" is equal to one, shown with a grid-patterned rectangle), where "Z" gap symbols separate two symbol groups (e.g., positioned between the end of a first symbol group and the beginning of a second symbol group). Here, the value of "Z" may also be predefined, or configured for a resource pool. The "Z" gap symbols are used for transmit-receive transitions (e.g., for radio frequency RF circuits to transition between a transmit chain and a receive chain, or vice versa, similar to the use of measurement gaps). In some cases, some of the symbols within the SL RSP slot may remain unused (not used for SL RSP, or as gap symbols). These symbols are shown with solid dark rectangles patterned with blank dots (the last two right symbols in the slot shown). In the example, these unused symbols may, but need not, be repurposed for non-SL RSP use (e.g., as PSSCH / PSCCH symbols or PSFCH symbols). The configuration with an SL RSP slot may be repeated across other SL RSP slots (e.g., in Figure 5 In the diagram, the symbol configuration may be repeated every eight time slots).

[0071] Figure 6 Yet another example of a configuration 600 for SL RSP according to some embodiments is shown. Here, a dedicated slot included in the PSSCH / PSCCH resources is used for SL RSP. However, instead of using the entire dedicated slot, only a portion (e.g., multiple symbols) is used for SL RSP. Figure 6 The upper left side shows the slot level configuration, while Figure 6 The lower right side shows the symbol level configuration.

[0072] Starting with the slot level configuration, nine slots per subchannel are shown, and three subchannels are also shown. Resources dedicated to PSSCH / PSCCH are shown as blank rectangles. Some of these PSSCH / PSCCH resources are dedicated to SLRSP. In particular, each of such PSSCH / PSCCH resources includes a SL RSP symbol set. The SL RSP symbol may be configured with a specific SL RSP periodicity (e.g., repeated once every eight slots) and is shown with a horizontal dashed rectangle. Other PSSCH / PSCCHs in the PSSCH / PSCCH are also dedicated to PSFCH. In particular, each of such PSSCH / PSCCH resources includes a PSFCH symbol set. For example, the last two symbols in such PSSCH / PSCCH resources are used for PSFCH (shown with a solid dark rectangle). The PSFCH symbol may be configured with a specific PSFCH periodicity (e.g., repeated once every two slots). In addition to the SL RSP periodicity, configuration 600 may also include an offset for the SL RSP.

[0073] In the example, the first PSSCH / PSCCH time slot set includes SL RSP symbols, and the second PSSCH / PSCCH time slot set includes PSFCH symbols. In other words, SL RSP resources can be shared with PSFCH resources in a time division multiplexing manner (e.g., some PSSCH / PSCCH time slots correspond to PSFCH resources, while other PSSCH / PSCCH time slots correspond to SL RSP resources).

[0074] In addition, SL RSP resources can be shared with PSFCH resources in a frequency division multiplexing manner across different subchannels or different subcarriers within the same subchannel (e.g., depending on the subcarrier and / or subchannel, symbols with the same symbol index in the time domain can be used for SL RSP and PSFCH, so that these shared resources overlap in the time domain and are frequency division multiplexed in the frequency domain). For example, SL RSP may duplicate some resource blocks (RBs) that are not used by PSFCH.

[0075] In the example, if a PSSCH / PSCCH slot includes at least one PSFCH symbol, the slot cannot be repurposed to include an SL RSP symbol. For example, if the SL RSP periodicity is eight slots, the PSFCH periodicity is two slots, and a zero offset is used, the SL RSP symbol may overlap with the PSFCH symbol. In this case, the PSSCH / PSCCH slot containing the overlap may not be repurposed for SL RSP transmission (e.g., it will still be used for PSSH / PSCCH transmission and PSFCH transmission). Alternatively, it is allowed to repurpose the PSSCH / PSCCH symbol to an SL RSP symbol, whereby the PSFCH symbol is also repurposed to be used as an SL RSP symbol. In other cases (e.g., depending on the SL RSP periodicity and offset and the PSFCH periodicity), the PSSCH / PSCCH slot may include both the SL RSP symbol and the PSFCH symbol in a non-overlapping manner. In such cases, the SLRSP resources may be shared with the PSFCH resources in a time division multiplexing manner.

[0076] Referring now to the symbol level configuration, a PSSCH / PSCCH slot includes a number of OFDM symbols (e.g., fourteen). When the PSSCH / PSCCH slot does not contain a PSFCH symbol, it may contain "X" consecutive OFDM symbols that define a symbol group and may be used for SL RSP. Figure 5 In the illustration of , "X" is equal to two, and the two symbols are located near the end of the PSSCH / PSCCH slot (e.g., the last two symbols before the last symbol), although a different number of symbols is possible and / or a different location is possible. The first "Y" symbols of the symbol group (e.g., before Figure 6 The contents of the symbol are repeated across the symbols of the symbol group. Although a single symbol group is shown, multiple such symbol groups are possible, and if two such symbol groups are adjacent, they may be separated by "X" gap symbols. However, the PSSCH / PSCCH also includes multiple OFDM symbols used as part of the PSSCH / PSCCH resources. The PSSCH / PSCCH symbols and the SL RSP symbol groups are separated by "X" gap symbols. Figure 6 In the illustration of , "X" is equal to two, but different numbers are possible. The last "X" symbols of the PSSCH / PSCCH slot may also be gap symbols. The first symbol (or first "Z" symbols) of the PSSCH / PSCCH may be reserved (e.g., for AGC).

[0077] Figure 7An example of a resource index 700 for a SL RSP according to some embodiments is shown. As explained herein above, resources (referred to herein as SL RSP resources) may be configured for a SL RSP. In the time domain, a SL RSP resource may occupy an entire time slot or a specific symbol within the time slot. In the frequency domain, a SL RSP resource may occupy an entire subchannel or a specific set of subcarriers. Figure 7 An example is shown where the SL RSP occupies two symbols in the time domain, and the comb-like resource elements (REs) each correspond to a subcarrier, and the set of such REs spans the bandwidth allocated to the sidelink channel.

[0078] exist Figure 7 In the specific illustration of , five symbols within a time slot are shown in the time domain. In addition, twenty-four subcarriers within a subchannel (e.g., two resource blocks) are shown in frequency. Of course, different numbers of symbols and / or bandwidths are possible. Eight symbol groups are defined (shown by rectangles of different shades and their respective indices). Each symbol group includes two OFDM symbols and is assigned to a device pair. Two symbol groups using the same subcarrier are separated by a gap symbol (for time division multiplexing, where four symbol group sets are multiplexed in the time domain, each set containing two symbol groups). For frequency division multiplexing, a comb of four is used for each symbol group, where two symbol group sets are multiplexed in the frequency-time domain, each set containing four symbol groups.

[0079] Thus, in the time domain, each SL RSP may occupy one or more symbols ( Figure 7 For example, SL RSP "0" uses two OFDM symbols with indexes "0" and "0". Figure 7 Continuous OFDM symbols are shown in , but non-contiguous OFDM symbols are possible.

[0080] In the frequency domain, each SL RSP may occupy a comb RE in an OFDM symbol. For example, SL RSP "0" uses six comb REs per OFDM symbol (a total of twelve comb REs for its symbol group of two OFDM symbols), where comb equals four. Figure 7 In the diagram, each SL RSP occupies the entire bandwidth.

[0081] also, Figure 7 It is shown that the SL RSP resources are indexed by frequency first and then by time (for example, the resources of SL RSP "0" including two OFDM symbols forming an OFDM symbol group and including six comb REs per OFDM symbol are indexed by "0", while the resources of the next SL RSP "1" occupying the next set of REs and using the same symbol index are indexed by "1", etc.). However, the SL RSP resources may be indexed by time first and then by frequency.

[0082] Figure 8 Another example of a resource index 800 for a SL RSP according to some embodiments is shown. The resource index 800 is similar to Figure 7 700 of the resource index. For the sake of brevity, the similarities are not repeated herein. However, the description of the resource index is equivalently applicable to Figure 8 The difference is that in the frequency domain, each SL RSP occupies a portion of the bandwidth (eg, a portion of the bandwidth of the sidelink channel, such as half, a quarter, or some other portion).

[0083] exist Figure 8 In the specific illustration of , each SL RSP occupies half of the bandwidth. Thus, in the time domain, each SL RSP occupies two OFDM symbols. In the time domain, each SL RSP uses three comb REs per OFDM symbol (different from Figure 7 , where six REs are used per OFDM symbol), where the comb equals four. Thus, sixteen SL RSPs are indexed, each SL RSP using a symbol group of two OFDM symbols and three comb REs per OFDM symbol.

[0084] Fig. 9 An example of a resource allocation 900 for a SL RSP according to some embodiments is shown. As described herein above, SL RSP resources may be configured for a SL RSP and may be indexed by frequency first and then by time, or vice versa. Here, an SCI may be used to indicate the resource allocation 900 so that a device may send or receive a SL RSP using the SL RSP resource configuration and index.

[0085] In the example, the SCI indicates an implicit mapping between PSSCH / PSCCH resources and SL RSP resources. For example, the SCI may include a single bit field to indicate the transmission of the SL RSP on the associated configured SL RSP resources. The index of the SL RSP resource may depend on the index of the PSSCH / PSCCH. The index of the PSSCH / PSCCH (or the index of the PSSCH / PSCCH resource) may be implicitly indicated in the SCI (for example, the SCI indicates the position of the PSCCH / PSSCH in the time domain and the frequency domain, and the index of the PSSCH / PSCCH may be calculated from the time-frequency position). The index of the SL RSP resource can be derived from the indication. In this case, the SCI may also indicate whether the SL RSP transmission will occur. If so, the SL RSP resource index to be used corresponds to the PSCCH / PSSCH resource index. Otherwise, the SL RSP resource corresponding to the PSCCH / PSSCH resource index is not used.

[0086] In an example, the index of PSSCH / PSCCH may include a starting subchannel index and a time slot index. For example, the PSSCH / PSCCH resource is first based on the time index and then on the frequency index (e.g. Fig. 9 ), or first based on frequency index and then based on time index. Fig. 9 In the illustration of , the first starting PSSCH / PSCCH resource is indexed as "0" and corresponds to the first time slot and the first subchannel, the second PSSCH / PSCCH resource is indexed as "1" and corresponds to the same first time slot but to the second subchannel, and so on, until the fourth time slot which is indexed as "3" and corresponds to the same first time slot but to the last subchannel of the PSSCH / PSCCH. For the next second time slot, the pattern repeats, starting with the fifth PSSCH / PSCCH resource indexed as "4" and corresponding to the second time slot and the first subchannel, and so on, until the last PSSCH / PSCCH resource indexed as "7" and corresponding to the second time slot and the last subchannel.

[0087] In the example, the mapping between the SL RSP resource index and the PSSCH / PSCCH resource index is defined so that the two indices are the same. For example, if the SCI indicates that the PSSCH / PSCCH resource index is "0", the SL RSP resource index is also implicitly indicated as "0". In this example, the total number of SL RSP resources is And this number is equal to or greater than the total number of PSSCH / PSCCH resources in is the number of OFDM symbols used for SLRSP, is the SL RSP periodicity, and N 子信道 is the number of subchannels in the resource pool.

[0088] In another example, the mapping between the SL RSP resource index and the PSSCH / PSCCH resource index is defined so that the two indexes may be different. For example, if the SCI indicates that the PSSCH / PSCCH resource index is "1", the SL RSP resource index is implicitly indicated as "2". In this example, the SL RSP resource index may be an integer multiple of the PSSCH / PSCCH resource index (e.g., "index SlRSP =A. Index PSSCH / PSCCH ”, where A is an integer multiple). Therefore, the total number of SL RSP resources Equal to the total number of PSSCH / PSCCH resources ( N 子信道). In this example, the selection of which SL RSP resource to use may depend on a source identifier (e.g., an identifier of a transmitter device) and / or a destination identifier (e.g., an identifier of a receiver device) of the SCI in the PSSCH / PSCCH resource index.

[0089] To illustrate the use of implicit mapping, consider the following two device procedures. The first device procedure can be implemented by a receiver device. In this procedure, a receiver device (e.g., UE) receives a sidelink PSSCH / PSCCH transmission, where the SCI indicates a future transmission of an SLRSP. The receiver device determines the SL RSP index based on the time slot and starting subchannel index of the PSSCH / PSCCH. The receiver device then measures the SL RSP in the determined SL RSP resource.

[0090] The second device procedure may be implemented by a transmitter device. In the procedure, a transmitter device (e.g., UE) sends a sidelink PSSCH / PSCCH transmission, where the SCI indicates a future transmission of a SL RSP. The transmitter device determines the SL RSP index based on the time slot and starting subchannel index of the PSSCH / PSCCH. The transmitter device then sends the SLRSP in the determined SL RSP resource.

[0091] In yet another example, rather than using an implicit mapping, an explicit mapping may be used. Here, the SCI may explicitly indicate and / or reserve SL RSP resources by including a bit set that provides the indication (rather than simply indicating that the SL RSP is sent as in the case of an implicit mapping). For example, the SCI may include an SL RSP bit field, wherein the bits of the field are set to a bit value indicating the reservation of SL RSP resources with a particular index.

[0092] Fig.10 An example of a time gap 1000 between a sidelink transmission (shown as a transmission using PSSCH / PSCCH 1010) and a SL RSP transmission (shown as a transmission using SL RSP 1020) according to some embodiments is shown. In general, the sidelink transmission may include an SCI that implicitly or explicitly indicates a SL RSP resource for SL RSP 1020. The receiver device may require processing time to process the SCI and determine the SL RSP resource. Thus, the time gap 1000 may be used, and the time gap may be equal to or greater than the processing time. In this way, the receiver device may receive the SL RSP on the SL RSP resource after it has completed processing the SCI.

[0093] In an example, the receiver device may indicate to the transmitter device the processing time and / or the expected length of the time slot 1000. The indication may be part of the UE capability information. The transmitter device may then schedule the SL RSP resources to appear in the time domain only after the time slot 1000 from the transmission of the SCI. The parameters of the time slot 1000 may be predefined, or may be preconfigured, or may be configured by a resource pool. The parameters may include any or all of the start of the time slot 1000, the end of the time slot 1000, or the time length of the time slot 1000. The time length may be defined as an integer multiple of a time slot (e.g., one time slot, two time slots, etc.).

[0094] In another example, time slot 1000 may not be used. Instead, the SCI may be sent before the end of time slot 1000. In this case, the receiver device may not receive the SL RSP on the first SL RSP resource set. However, given the SL RSP periodicity, the receiver device may receive the SL RSP on the next SL RSP resource set that occurs after time slot 1000 in the time domain.

[0095] Fig.11 An example of an operational flow / algorithm structure 1100 for SL RSP transmission according to some embodiments is shown. The operational flow / algorithm structure 1100 may be implemented by a first device, which may be a transmitter device (such as UE 104 or 106) or a component thereof (e.g., processor 1404) in sidelink communication.

[0096] In the example, the operation flow / algorithm structure 1100 includes: at 1102, sending an SCI for sidelink transmission in a sidelink channel between the first device and the second device to the second device, wherein the SCI indicates that the sidelink transmission includes the transmission of an SLRSP, and wherein the sidelink channel includes a PSSCH or a PSCCH. For example, the SCI may indicate an index associated with the PSSCH and / or the PSCCH, and may include a single bit field indicating that the SL RSP is transmitted. In this illustration, the SL RSP resource is determined using an implicit mapping between an explicitly indicated index and an index of the SL RSP resource. The SL RSP resource is used for the transmission of the SL RSP. In another illustration, an explicit mapping is used instead of an implicit mapping. In this case, the SCI may include an SL RSP bit field that uses multiple bits to indicate the SL RSP resource. In both cases, before sending the SCI, the first device may have sent configuration information that configures the second device to use the SL RSP resource, and such resources may be indexed by frequency first and then by time, or vice versa.

[0097] In an example, the operation flow / algorithm structure 1100 includes determining sidelink resources to be used for transmission of the SL RSP at 1104. For example, the sidelink resources include SL RSP resources that meet the configuration information and may appear after a time gap from the transmission of the SCI in the time domain.

[0098] In an example, the operational flow / algorithm structure 1100 includes: at 1106, sending a SL RSP to a second device based on the sidelink resource. For example, the SL RSP resource carries content that can be used to measure the SL RSP. In the case where multiple OFDM symbols are used in the SL RSP resource, the content can be repeated across the OFDM symbols so that the first OFDM symbol (or a first set of such symbols) can be used for AGC and the remaining OFDM symbols can be used for SL RSP measurement.

[0099] Fig.12 An example of an operational flow / algorithm structure 1200 for SL RSP reception according to some embodiments is shown. The operational flow / algorithm structure 1200 may be implemented by a first device, which may be a receiver device (such as UE 104 or 106) or a component thereof (e.g., processor 1404) in sidelink communication.

[0100] In the example, the operation flow / algorithm structure 1200 includes: at 1202, receiving an SCI for a sidelink transmission in a sidelink channel between a first device and a second device from a second device, wherein the SCI indicates that the sidelink transmission includes the transmission of an SLRSP, and wherein the sidelink channel includes a PSSCH or a PSCCH. For example, the SCI may indicate an index associated with the PSSCH and / or the PSCCH, and may include a single bit field indicating that the SL RSP is transmitted. In this illustration, an implicit mapping between an explicitly indicated index and an index of the SL RSP resource is used to determine the SL RSP resource. The SL RSP resource is used for the transmission of the SL RSP. In another illustration, an explicit mapping is used instead of an implicit mapping. In this case, the SCI may include an SL RSP bit field that indicates the SL RSP resource using multiple bits. In both cases, before sending the SCI, the first device may have received configuration information that configures the first device to determine the SL RSP resources for SL RSP transmission, and such resources may be indexed by frequency first and then by time, or vice versa.

[0101] In an example, the operational flow / algorithm structure 1200 may include receiving a side link transmission from a second device at 1204. For example, the first device receives data on a PSSCH or receives control information on a PSCCH. In addition to receiving data and / or control information, the received side link transmission may also include the transmission of an SL RSP.

[0102] In an example, the operation flow / algorithm structure 1200 includes: at 1206, determining a side link resource for the transmission of the SL RSP. For example, the side link resource includes a SL RSP resource that satisfies the configuration information and may appear after a time gap from the transmission of the SCI in the time domain. The index of the SL RSP resource may be implicitly or explicitly determined from the SCI.

[0103] In an example, the operational flow / algorithm structure 1200 includes: At 1208, measurements are performed on the SL RSP based on the side link resources. For example, the measurements using the SL RSP resources are performed according to one or more positioning techniques. These techniques may include timing-based techniques, such as time of arrival (ToA), time difference of arrival (TDoA), or round trip time (RTT), and / or angle-based techniques, such as angle of arrival (AoA).

[0104] Fig.13 A receiving component 1300 of a UE 144 according to some embodiments is shown. The receiving component 1300 may include an antenna panel 1304 including a plurality of antenna elements. The panel 1304 is shown with four antenna elements, but other embodiments may include other numbers of antenna elements.

[0105] The antenna panel 1304 may be coupled to an analog beam forming (BF) component including a plurality of phase shifters 1308(1)-1308(4). The phase shifters 1308(1)-1308(4) may be coupled to a radio frequency (RF) chain 1312. The RF chain 1312 may amplify the received analog RF signal, down-convert the RF signal to baseband, and convert the analog baseband signal to a digital baseband signal that may be provided to a baseband processor for further processing.

[0106] In various embodiments, control circuitry, which may reside in a baseband processor, may provide BF weights (e.g., W1-W4) to phase shifters 1308(1)-1308(4), which may represent phase shift values ​​to provide receive beams at antenna panel 1304. These BF weights may be determined based on channel-based beamforming.

[0107] Fig.14 UE 1400 according to some embodiments is shown. UE 1400 may be similar to Figure 1UE 104 or 106 and is essentially interchangeable therewith.

[0108] Similar to what is described above with respect to UE 144, UE 1400 may be any mobile or non-mobile computing device, such as a mobile phone, computer, tablet, industrial wireless sensor (e.g., microphone, carbon dioxide sensor, pressure sensor, humidity sensor, thermometer, motion sensor, accelerometer, laser scanner, fluid level sensor, inventory sensor, voltage / current meter, actuator, etc.), video surveillance / monitoring equipment (e.g., camera, camcorder, etc.), wearable device, or loose IoT device. In some embodiments, the UE may be a reduced capacity UE or an NR-Light UE.

[0109] UE 1400 may include a processor 1404, an RF interface circuit 1408, a memory / storage device 1412, a user interface 1416, a sensor 1420, a driver circuit 1422, a power management integrated circuit (PMIC) 1424, and a battery 1428. The components of UE 1400 may be implemented as an integrated circuit (IC), a portion of an integrated circuit, a discrete electronic device or other module, logical component, hardware, software, firmware, or a combination thereof. Fig.14 The block diagram of UE 1400 is intended to show a high-level view of certain of the components of UE 1400. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

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

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

[0112] In some embodiments, the baseband processor circuit 1404A can access the communication protocol stack 1436 in the memory / storage device 1412 to communicate through a 3GPP compatible network. In general, the baseband processor circuit 1404A can access the communication protocol stack to: perform user plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access layer (NAS) layer. In some embodiments, the PHY layer operations can be additionally / alternatively performed by components of the RF interface circuit 1408.

[0113] The baseband processor circuit 1404A may generate or process baseband signals or waveforms that carry information in a 3GPP-compatible network. In some embodiments, the waveforms used for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0114] The baseband processor circuit 1404A may also access group information from the memory / storage 1412 to determine a search space group in which multiple repetitions of the PDCCH may be sent.

[0115] The memory / storage 1412 may include any type of volatile or non-volatile memory that may be distributed throughout the UE 1400. In some implementations, some of the memory / storage 1412 may be located on the processor 1404 itself (e.g., L1 cache and L2 cache), while other memory / storage 1412 is external to the processor 1404 but accessible via a memory interface. The memory / storage 1412 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0116] The RF interface circuit 1408 may include a transceiver circuit and a radio frequency front end module (RFEM), which allows the UE 1400 to communicate with other devices through a radio access network. The RF interface circuit 1408 may include various elements arranged in a transmit path or a receive path. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, control circuits, etc.

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

[0118] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier before the signal is radiated across the air interface via the antenna 1450.

[0119] In various embodiments, the RF interface circuit 1408 may be configured to send / receive signals in a manner compatible with NR access technology.

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

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

[0122] Sensors 1420 may include devices, modules, or subsystems that are designed to detect events or changes in their environment and communicate information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit including an accelerometer; a gyroscope; or a magnetometer; a micro-electromechanical system or nano-electromechanical system including: a three-axis accelerometer; a three-axis gyroscope; or a magnetometer; a level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; a microphone or other similar audio capture device; and the like.

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

[0124] The PMIC 1424 may manage the power provided to various components of the UE 1400. Specifically, with respect to the processor 1404, the PMIC 1424 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0125] In some embodiments, the PMIC 1424 may control or otherwise be part of various power saving mechanisms of the UE 1400. For example, if the platform UE is in the RRC_Connected state, in which the platform is still connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform may enter a state known as discontinuous reception mode (DRX). During this state, the UE 1400 may be powered off for short time intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the UE 1400 may transition to the RRC_Idle state, in which it is disconnected from the network and does not perform operations such as channel quality feedback, handovers, etc. The UE 1400 enters a very low power state and performs paging, in which it wakes up again periodically to listen to the network, and then powers off again. The UE 1400 may not receive data in this state; in order to receive data, the platform must transition back to the RRC_Connected state. Additional power saving modes may prevent the device from using the network for a time exceeding the paging interval (from a few seconds to a few hours). During this time, the device is completely unable to connect to the network and can be completely powered off. Any data transmitted during this time will incur significant latency, and it is assumed that latency is acceptable.

[0126] The battery 1428 can power the UE 1400, but in some examples, the UE 1400 can be installed and deployed in a fixed location and can have a power source coupled to the power grid. The battery 1428 can be a lithium-ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, the battery 1428 can be a typical lead-acid car battery.

[0127] Fig.15 FIG. 1 shows a gNB 1500 according to some embodiments. The gNB 1500 may be similar to Figure 1 The gNB 108 is similar to and essentially interchangeable with it.

[0128] gNB 1500 may include a processor 1504, RAN interface circuitry 1508, core network (CN) interface circuitry 1512, and memory / storage device circuitry 1516.

[0129] Components of gNB 1500 may be coupled to various other components via one or more interconnects 1528.

[0130] The processor 1504, RAN interface circuit 1508, memory / storage circuit 1516 (including communication protocol stack 1510), antenna 1550 and interconnect 1528 may be similar to those of reference Fig.14 Like named elements are shown and described.

[0131] The CN interface circuitry 1512 may provide connectivity to a core network, e.g., a fifth generation core network (5GC) using a 5GC-compatible network interface protocol such as a Carrier Ethernet protocol or some other suitable protocol. Network connectivity may be provided to / from the gNB 1500 via optical fiber or wireless backhaul. The CN interface circuitry 1512 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 1512 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0132] 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. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

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

[0134] Example

[0135] In the following sections, additional exemplary embodiments are provided.

[0136] Embodiment 1 includes a method implemented by a first device, the method comprising: sending sidelink control information (SCI) for a sidelink transmission in a sidelink channel between the first device and the second device to a second device, wherein the SCI indicates that the sidelink transmission includes the transmission of a sidelink reference signal for positioning (SL RSP), and wherein the sidelink channel includes a physical sidelink shared channel (PSSCH) or a physical sidelink control channel (PSCCH); determining a sidelink resource to be used for the transmission of the SLRSP; and sending the SL RSP to the second device based on the sidelink resource.

[0137] Embodiment 2 includes a method implemented by a first device, the method comprising: receiving sidelink control information (SCI) for a sidelink transmission in a sidelink channel between the first device and the second device from a second device, wherein the SCI indicates that the sidelink transmission includes a transmission of a sidelink reference signal for positioning (SL RSP), and wherein the sidelink channel includes a physical sidelink shared channel (PSSCH) or a physical sidelink control channel (PSCCH); receiving the sidelink transmission from the second device; determining a sidelink resource for the transmission of the SL RSP; and performing measurements on the SL RSP based on the sidelink resource.

[0138] Embodiment 3 includes a method according to any one of the aforementioned embodiments 1 to 2, wherein the SCI includes a bit field, the bit field includes multiple bits indicating the side link resources used for the SL RSP, and wherein the side link resources are determined based on the multiple bits.

[0139] Embodiment 4 includes a method according to any one of the aforementioned embodiments 1 to 2, wherein the SL RSP is sent after a time gap from the sending of the SCI, wherein the time gap is preconfigured, or is configured by a resource pool associated with the side link transmission, or is predefined.

[0140] Embodiment 5 includes a method according to any one of the aforementioned embodiments 1 to 2, wherein the SCI includes a bit field indicating a PSSCH resource or a PSCCH resource used for the side link transmission, and wherein the side link resource is determined based on the bit field.

[0141] Embodiment 6 includes a method according to any one of the aforementioned embodiments 1 to 2, wherein the method further includes: determining a first resource index of a PSSCH resource or a PSCCH resource sent by the side link based on the SCI; and determining a second resource index of the side link resource based on the first resource index, wherein the SL RSP is sent based on the second resource index.

[0142] Embodiment 7 includes the method according to embodiment 6, wherein the PSSCH resource or the PSCCH resource is first based on a time index and then based on a frequency index, or first based on a frequency index and then based on a time index.

[0143] Embodiment 8 includes the method according to embodiment 6, wherein the second resource index is the same as the first resource index.

[0144] Embodiment 9 includes the method according to embodiment 8, wherein the sidelink transmission uses a total number of SL RSP resources equal to or greater than a total number of PSSCH resources or PSCCH resources.

[0145] Embodiment 10 includes the method according to embodiment 6, wherein the second resource index is an integer multiple of the first resource index.

[0146] Embodiment 11 includes the method according to embodiment 10, wherein the sidelink transmission uses a total number of SL RSP resources equal to or greater than an integer multiple of the total number of PSSCH resources or PSCCH resources.

[0147] Embodiment 12 comprises a method according to any one of the preceding embodiments 1 to 10, wherein the side link resources comprise comb resource elements in an orthogonal frequency division multiplexing (OFDM) symbol.

[0148] Embodiment 13 includes a method according to any one of the preceding embodiments 1 to 10, wherein the side link resources include a plurality of resource elements distributed across a bandwidth associated with the side link transmission or a portion of the bandwidth.

[0149] Embodiment 14 includes a method according to any one of the preceding embodiments 1 to 10, wherein the side link resources include a plurality of orthogonal frequency division multiplexing (OFDM) symbols of the comb resource that are continuous or discontinuous in the time domain.

[0150] Embodiment 15 includes a method according to any one of the aforementioned embodiments 1 to 10, wherein the side link resource is first based on a time index and then on a frequency index, or first based on a frequency index and then on a time index.

[0151] Embodiment 16 includes a method according to any one of the aforementioned embodiments 1 to 15, wherein the method further includes: sending first configuration information to the second device, the first configuration information indicating a resource configuration that can be used for the SL RSP, wherein the first configuration information is separate from the second configuration information used for the PSSCH or the PSCCH.

[0152] Embodiment 17 includes a method according to embodiment 16, wherein the first configuration information includes a first bitmap indicating that a first time slot in the resource pool can be used for the SL RSP, wherein the second configuration information includes a second bitmap indicating that a second time slot in the resource pool can be used for PSSCH data or PSCCH control, and wherein the first bitmap and the second bitmap have the same size.

[0153] Embodiment 18 includes a method according to any one of the aforementioned embodiments 1 to 15, wherein the method further includes: sending configuration information to the second device, the configuration information jointly indicating resource configuration that can be used for the SL RSP and can be used for the PSSCH or the PSCCH.

[0154] Embodiment 19 includes the method according to embodiment 18, wherein the configuration information includes a bitmap indicating whether a time slot in a resource pool can be used for any one of the SL RSP, the PSSCH, or the PSCCH.

[0155] Embodiment 20 includes a method according to any one of the aforementioned embodiments 1 to 15, wherein the method further includes: sending configuration information to the second device, the configuration information indicating: in the resource pool, the time slot that can be used for the PSSCH or the PSCCH is dedicated to side link device-to-device positioning.

[0156] Embodiment 21 includes the method according to embodiment 20, wherein the time slot includes a first orthogonal frequency division multiplexing (OFDM) symbol that can be used for the SL RSP.

[0157] Embodiment 22 includes the method of embodiment 21, wherein the time slot includes a second OFDM symbol that can be used for automatic gain control (AGC), wherein the second OFDM symbol precedes the first OFDM symbol.

[0158] Embodiment 23 includes a method according to embodiment 20, wherein the time slot includes multiple orthogonal frequency division multiplexing (OFDM) symbol groups that can be used for sidelink device-to-device positioning, wherein each OFDM symbol group in the multiple OFDM symbol groups includes one or more OFDM symbols, and wherein at least two of the OFDM symbols are separated by one or more gap symbols in the time slot.

[0159] Embodiment 24 includes a method according to any one of the aforementioned embodiments 1 to 15, wherein the method further includes: sending configuration information to the second device, the configuration information indicating that: in the resource pool, the time slot includes a first orthogonal frequency division multiplexing (OFDM) symbol that can be used for the PSSCH or the PSCCH, and the second OFDM symbol can be used for the SL RSP.

[0160] Embodiment 25 includes the method of embodiment 24, wherein the time slot includes one or more time slot gaps separating the first OFDM symbol and the second OFDM symbol.

[0161] Embodiment 26 includes the method according to embodiment 24, wherein the configuration information indicates that the side link resource to be used for the transmission of the SL RSP is shared with another side link resource to be used for a physical side link feedback channel (PSFCH) in a frequency division multiplexing manner.

[0162] Embodiment 27 includes the method according to embodiment 24, wherein the configuration information indicates that the side link resource to be used for the transmission of the SL RSP is shared with another side link resource to be used for a physical side link feedback channel (PSFCH) in a time division multiplexed manner.

[0163] Embodiment 28 includes an apparatus comprising means for performing one or more elements of the method described in or related to any one of Embodiments 1-27.

[0164] Embodiment 29 includes one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of a device, cause the device to perform one or more elements of a method described in or related to any one of Embodiments 1 to 27.

[0165] Embodiment 30 includes an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any one of Embodiments 1-27.

[0166] Embodiment 31 includes a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of a method described in or related to any one of Embodiments 1 to 27.

[0167] Embodiment 32 includes a system comprising means for performing one or more elements of the method described in or related to any one of Embodiments 1-27.

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

[0169] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to include all such variations and modifications.

Claims

1. A method implemented by a first device, the method comprising: sending, to a second device, sidelink control information (SCI) for a sidelink transmission in a sidelink channel between the first device and the second device, wherein the SCI indicates that the sidelink transmission includes transmission of a sidelink reference signal for positioning (SL RSP), and wherein the sidelink channel includes a physical sidelink shared channel (PSSCH) or a physical sidelink control channel (PSCCH); determining sidelink resources to be used for said sending of said SL RSP; and The SL RSP is sent to the second device based on the side link resources.

2. The method of claim 1, wherein the SCI comprises a bit field including a plurality of bits indicating the side link resources for the SL RSP, and wherein the side link resources are determined based on the plurality of bits.

3. The method of claim 1, wherein the SL RSP is sent after a time gap from the sending of the SCI, wherein the time gap is preconfigured, or is configured by a resource pool associated with the side link transmission, or is predefined.

4. The method of claim 1, wherein the SCI comprises a bit field indicating a PSSCH resource or a PSCCH resource used for the sidelink transmission, and wherein the sidelink resource is determined based on the bit field.

5. The method according to claim 1, further comprising: Determine a first resource index of a PSSCH resource or a PSCCH resource sent by the side link based on the SCI; as well as A second resource index for the side link resource is determined based on the first resource index, wherein the SL RSP is sent based on the second resource index.

6. The method according to claim 5, wherein the PSSCH resource or the PSCCH resource is first based on a time index and then based on a frequency index, or first based on a frequency index and then based on a time index. The method of claim 5 , wherein the second resource index is the same as the first resource index.

8. The method according to claim 7, wherein the sidelink transmission uses a total number of SL RSP resources equal to or greater than a total number of PSSCH resources or PSCCH resources.

9. The method of claim 5, wherein the second resource index is an integer multiple of the first resource index.

10. The method according to claim 9, wherein the side link transmission uses a total number of SL RSP resources equal to or greater than an integer multiple of a total number of PSSCH resources or PSCCH resources.

11. A first device, comprising: one or more processors; and one or more memories storing instructions that, when executed by the one or more processors, configure the first device to: receiving, from a second device, sidelink control information (SCI) for a sidelink transmission in a sidelink channel between the first device and the second device, wherein the SCI indicates that the sidelink transmission includes transmission of a sidelink reference signal for positioning (SL RSP), and wherein the sidelink channel includes a physical sidelink shared channel (PSSCH) or a physical sidelink control channel (PSCCH); receiving the sidelink transmission from the second device; determining side link resources for said sending of said SL RSP; and Performing measurements on the SL RSP based on the sidelink resources.

12. The first device of claim 11, wherein the sidelink resources comprise comb-shaped resource elements in an orthogonal frequency division multiplexing (OFDM) symbol.

13. The first device of claim 11, wherein the sidelink resources comprise a plurality of resource elements distributed across a bandwidth associated with the sidelink transmission or a portion of the bandwidth.

14. The first device according to claim 11, wherein the side link resource comprises a plurality of orthogonal frequency division multiplexing (OFDM) symbols in which the comb resource is continuous or discontinuous in the time domain.

15. The first device according to claim 11, wherein the side link resource is based on a time index first and then a frequency index, or based on a frequency index first and then a time index.

16. One or more computer-readable storage media storing instructions that, when executed on a first device, cause the first device to perform operations comprising: sending, to a second device, sidelink control information (SCI) for a sidelink transmission in a sidelink channel between the first device and the second device, wherein the SCI indicates that the sidelink transmission includes transmission of a sidelink reference signal for positioning (SL RSP), and wherein the sidelink channel includes a physical sidelink shared channel (PSSCH) or a physical sidelink control channel (PSCCH); determining sidelink resources to be used for said sending of said SL RSP; and The SL RSP is sent to the second device based on the side link resources.

17. The one or more computer-readable storage media of claim 16, wherein the operations further comprise: First configuration information is sent to the second device, where the first configuration information indicates a resource configuration that can be used for the SL RSP, wherein the first configuration information is separate from second configuration information for the PSSCH or the PSCCH.

18. One or more computer-readable storage media according to claim 17, wherein the first configuration information includes a first bitmap, the first bitmap indicating that a first time slot in a resource pool can be used for the SL RSP, wherein the second configuration information includes a second bitmap, the second bitmap indicating that a second time slot in the resource pool can be used for PSSCH data or PSCCH control, and wherein the first bitmap and the second bitmap have the same size.

19. The one or more computer-readable storage media of claim 16, wherein the operations further comprise: Configuration information is sent to the second device, where the configuration information jointly indicates resource configuration that can be used for the SL RSP and that can be used for the PSSCH or the PSCCH.

20. The one or more computer-readable storage media of claim 19, wherein the configuration information comprises a bitmap indicating whether a time slot in a resource pool can be used for any of the SL RSP, the PSSCH, or the PSCCH.

21. The one or more computer-readable storage media of claim 16, wherein the operations further comprise: Configuration information is sent to the second device, the configuration information indicating that in a resource pool, a time slot that can be used for the PSSCH or the PSCCH is dedicated to sidelink device-to-device positioning.

22. The one or more computer-readable storage media of claim 21, wherein the time slot comprises a first orthogonal frequency division multiplexing (OFDM) symbol that can be used for the SL RSP.

23. The one or more computer-readable storage media of claim 22, wherein the time slot includes a second OFDM symbol that can be used for automatic gain control (AGC), wherein the second OFDM symbol precedes the first OFDM symbol.

24. One or more computer-readable storage media according to claim 21, wherein the time slot includes a plurality of orthogonal frequency division multiplexing (OFDM) symbol groups that can be used for sidelink device-to-device positioning, wherein each OFDM symbol group in the plurality of OFDM symbol groups includes one or more OFDM symbols, and wherein at least two of the OFDM symbols are separated by one or more gap symbols in the time slot.

25. The one or more computer-readable storage media of claim 16, wherein the operations further comprise: Configuration information is sent to the second device, the configuration information indicating that, in a resource pool, a time slot includes a first orthogonal frequency division multiplexing (OFDM) symbol that can be used for the PSSCH or the PSCCH, and a second OFDM symbol can be used for the SLRSP.

26. The one or more computer-readable storage media of claim 25, wherein the time slot comprises one or more time slot gaps separating the first OFDM symbol and the second OFDM symbol.

27. One or more computer-readable storage media according to claim 25, wherein the configuration information indicates that the sidelink resource to be used for the transmission of the SL RSP is shared with another sidelink resource to be used for a physical sidelink feedback channel (PSFCH) in a frequency division multiplexing manner.

28. One or more computer-readable storage media according to claim 25, wherein the configuration information indicates that the sidelink resource to be used for the transmission of the SL RSP is shared with another sidelink resource to be used for a physical sidelink feedback channel (PSFCH) in a time division multiplexed manner.

Images