Lateral link positioning with multiple resource pools

By dynamically requesting and retaining resource pool resources of other terminal devices, resource coordination among multiple resource pools in the 5G network is achieved, solving the problems of side link positioning accuracy and delay requirements, and improving positioning efficiency and accuracy.

CN119096501APending Publication Date: 2024-12-06NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280095376.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-04-29
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In 5G networks, the accuracy and delay requirements for side link positioning are high, but the bandwidth limitation of the side link resource pool in the prior art leads to limited positioning accuracy and cannot effectively achieve high-precision positioning.

Method used

By allowing the terminal device to dynamically request and retain resource pool resources of other terminal devices, the coordination of multiple resource pools or bandwidth parts is achieved, and it is used to send side link positioning reference signals to avoid the need to configure and monitor resource pools separately.

Benefits of technology

It realizes high-precision side link positioning without complex network coordination, improves positioning accuracy and efficiency, and reduces energy consumption and resource waste.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096501A_ABST
    Figure CN119096501A_ABST
Patent Text Reader

Abstract

The invention in particular relates to a first terminal device configured for sidelink communication in a first sidelink resource pool, the first terminal device comprising means for:-receiving resource pool information relating to a second sidelink resource pool configured for a second terminal device; -sending a request to the second terminal device via sidelink communication to reserve resources in the second sidelink resource pool for transmission of sidelink positioning reference signals by the first terminal device; receiving a response to the request from the second terminal device via the sidelink communication; and-based on the response, transmitting a sidelink positioning reference signal using a resource in the first sidelink resource pool and a resource in the second sidelink resource pool.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to, but is not limited to, communication networks defined by 3GPP standards, such as the 5G standard, also known as New Radio NR. The present disclosure relates specifically to sidelink positioning, and more specifically to sidelink positioning via sidelink positioning reference signals. Background Art

[0002] The present disclosure relates to sidelink positioning, such as discussed in technical report [1]. Compared to existing positioning methods over the Uu interface, sidelink (SL) positioning has the advantage of operating outside (or part of) network coverage, except in coverage conditions where network-based positioning is not applicable or cannot meet positioning QoS requirements (e.g. due to fewer available anchor nodes), or when the user equipment (UE) is out of GNSS coverage (e.g. in a tunnel). SL positioning will be an enabler for many use cases, as described in [2], most notably public safety and road safety, as well as many vehicular applications (including traffic efficiency, coordinated driving and autonomous driving), and industrial applications.

[0003] In order to perform positioning on the SL radio interface, the UE needs to send / receive certain reference signals for positioning, which are called SL Positioning Reference Signals (SL PRS). The UE makes certain measurements on these reference signals (e.g., time of arrival, angle of arrival, etc.), which are then used to calculate the UE's position estimate.

[0004] Currently, SL utilizes certain parts of dedicated or shared frequency bands, the so-called bandwidth parts (BWP). Within the BWP, SL transmission and reception is performed through a resource pool (pre-)configured by the network. Figure 1 As shown in the exemplary time-frequency diagram of , SLBWP uses a certain portion of the total carrier bandwidth. In SL BWP, the resource pool is reserved for SL communication during the resource pool period. The resource pool sequentially spans L frequency subchannels, each frequency subchannel has M sub The UE is a UE that uses a physical resource block (PRB) and a certain number of time slots. The configured resource pools use a single digital technology. Although SL resource pools are configured separately for SL transmission and reception, different resource pools may overlap in time and / or frequency. According to the current specification, a UE is only allowed to use the resource pool for which it is (pre)configured for transmission and reception.

[0005] According to the current 3GPP specifications (mainly TS 38.331), the sidelink UE uses a specific bandwidth part "sl-BWP" (maxNrofSL-BWPs-r16=4) configured by the network, with a specific digital technology. The sl-BWP contains one or more resource pools, which can generally have different sizes, i.e., different numbers of frequency subchannels and time slots. Typically, the network can (pre)configure the resource pools to make them completely orthogonal, or at least partially or even completely overlapping. Each resource pool is (pre)configured for a group of UEs for transmission (Tx) or reception (Rx) or both over the SL interface.

[0006] Figure 2 An example is given in . UE1 is configured with the same pool for SL transmission (Tx1) and reception (Rx1). The same is true for UE3 (Tx3 and Rx3). On the other hand, UE2 is configured with different pools for transmission (Tx2) and reception (Rx2). It receives through a larger Rx resource pool, which also overlaps with the transmission and reception pools of other UE1 and UE3.

[0007] SL UEs are only allowed to transmit and receive on (multiple) Tx / Rx SL resource pools specifically configured for them. According to Section 5.8.7 of TS38.331, the sidelink UE determines the configured SL resource pool to transmit / receive in the following order: First, if possible, it uses the Tx / Rx pool indicated in the RRC reconfiguration message (sent via dedicated signaling). Otherwise, if possible, the UE uses the Tx / Rx pool indicated in SIB12 (sent via broadcast). Otherwise, the UE uses the Tx / Rx pool indicated in SL-PreconfigurationNR (preconfigured in the UE).

[0008] When in mode 2 (autonomous resource allocation mode), the UE shall perform sensing on all resource pools that can be used for transmission of sidelink control information and corresponding sidelink data. As described above, the resource pool is indicated by pre-configuration, SIB12, or RRCreconfiguration. Summary of the invention

[0009] However, there is a problem that in 5G and other networks, applications have very high requirements for sidelink positioning, mainly in terms of accuracy and latency (see, for example, [1]).

[0010] To achieve high-precision positioning (e.g., see the basic Cramer-Rao bound), positioning reference signals (measured in terms of time / angle / phase to estimate UE position) should be sent / received over a relatively large bandwidth, ideally on the order of 10s or even 100s of MHz. However, the resource pools configured for SL transmission and reception typically have a small bandwidth that is insufficient for any meaningful positioning. The current Rel-16 resource pool configuration for the NR sidelink limits the maximum number of PRBs to a maximum of 275, which corresponds to a total allowed frequency bandwidth of 49.5 MHz.

[0011] Furthermore, the portion of bandwidth allocated to SL is much smaller compared to the uplink / downlink (UL / DL) Uu bands, e.g., 30MHz of the 5.9GHz ITS (Intelligent Transportation System) band is dedicated to vehicular SL communications. Therefore, while UL / DL-based positioning can theoretically benefit from several hundred MHz of available bandwidth, practical limitations on the sidelink resource pool size as well as the SL bandwidth portion greatly restrict the available transmission of the wideband reference signals required for precise positioning over the SL interface. The problem, therefore, is that the bandwidth or resources available for SL positioning is limited, thereby limiting the achievable positioning accuracy.

[0012] In NR sidelink Rel-16 and Rel-17, sidelink resource reservation is performed through Sidelink Control Information (SCI). SCI is carried by the Physical Sidelink Control Channel (PSCCH) and is split into first-level SCI and second-level SCI. The SCI configuration for NR sidelink is specified in 3GPP 38.212 Section 8.4. The first-level SCI contains resource reservations / allocations (frequency granularity in subchannels, time granularity in time slots) for up to three future sidelink transmission opportunities.

[0013] The problem is that in Rel-16 and Rel-17, there is a unique 1:1 (i.e., bijective) mapping between SCI and (multiple) sidelink resource reservations. In other words, in NR sidelink Rel-16 and Rel-17, multiple SCIs cannot be aggregated for the same reservation, i.e., for each sidelink resource reservation, there is only one SCI. Therefore, for a single SCI framework for NR sidelink Rel-16 / Rel-17, wideband resource reservation across multiple resource pools (adjacent, partially or fully overlapping) to maximize sidelink bandwidth (e.g., for the purpose of Rel-18 NR sidelink positioning) cannot be achieved.

[0014] There are some techniques that can exploit wider frequency bandwidth or available resources in the network for communication purposes, such as carrier aggregation (see, for example, [4] and [5]). However, such techniques involve centralized coordination of the network, use of only UL / DL frequency bands, or in the case of SL, carrier aggregation solutions have so far been targeted only for SL communications. For example, specific radio link measurements, RRC management on a single carrier component, asymmetric scheduling and duplication of the HARQ sublayer are required, for example, to overcome issues around different coverage of individual carrier components.

[0015] Therefore, certain embodiments of the present disclosure may have the effect of providing improved sidelink positioning. More specifically, certain embodiments may enable high-precision positioning in SL scenarios by utilizing all available sidelink resources in the network (but not necessarily (pre)configured to individual UEs). In addition, certain embodiments of the present disclosure may have the effect of allowing aggregation of multiple resources for SL positioning while avoiding complex arrangements. More specifically, certain embodiments of the present disclosure may have the effect of providing a simple and efficient method to allow a UE to utilize multiple resource pools or bandwidth portions for SL positioning with minimal or no network coordination, i.e., providing a distributed solution while maintaining inherent reliability.

[0016] According to a first exemplary aspect, a first terminal device configured for sidelink communication in a first sidelink resource pool is disclosed. The first terminal device may include a component for: receiving resource pool information related to a second sidelink resource pool configured for a second terminal device. The first terminal device may also include a component for: sending a request to the second terminal device via the sidelink communication to reserve resources in the second sidelink resource pool for transmission of a sidelink positioning reference signal by the first terminal device. The first terminal device may also include a component for: receiving a response to the request from the second terminal device via the sidelink communication. The first terminal device may also include a component for: based on the response, using resources in the first sidelink resource pool and resources in the second sidelink resource pool to send a sidelink positioning reference signal.

[0017] According to a second exemplary aspect, a second terminal device configured for sidelink communication in a second sidelink resource pool is disclosed. The second terminal device may include a component for receiving a request from a first terminal device configured for sidelink communication in a first sidelink resource pool via sidelink communication, the request being used to reserve resources in the second sidelink resource pool for transmission of a sidelink positioning reference signal by the first terminal device. The second terminal device may also include a component for sending a response to the request to the first terminal device via the sidelink communication. The second terminal device may also include a component for reserving resources in the second sidelink resource pool in response to the request for transmission of a sidelink positioning reference signal by the first terminal device.

[0018] According to a third exemplary aspect, a network entity is disclosed, which includes a component for: sending or causing sending resource pool information related to a sidelink resource pool to a first terminal device, the sidelink resource pool being configured for one or more other terminal devices, and the one or more terminal devices being served by corresponding other base stations.

[0019] According to each of the exemplary aspects, a corresponding method is also disclosed.

[0020] Therefore, according to a first exemplary aspect, there is a method performed by a first terminal device, the first terminal device being configured for sidelink communication in a first sidelink resource pool. The method may include: receiving resource pool information related to a second sidelink resource pool configured for a second terminal device. The method may also include: sending a request to the second terminal device via the sidelink communication to reserve resources in the second sidelink resource pool for transmission of a sidelink positioning reference signal by the first terminal device. The method may also include: receiving a response to the request from the second terminal device via the sidelink communication. The method may also include: based on the response, using resources in the first sidelink resource pool and resources in the second sidelink resource pool to send a sidelink positioning reference signal.

[0021] According to a second exemplary aspect, a method performed by a second terminal device is disclosed, the second terminal device being configured for sidelink communication in a second sidelink resource pool. The method may include: receiving a request via the sidelink communication from a first terminal device configured for sidelink communication in a first sidelink resource pool, the request being used to reserve resources in the second sidelink resource pool for transmission of a sidelink positioning reference signal by the first terminal device. The method may also include: sending a response to the request to the first terminal device via the sidelink communication. The method may also include: reserving resources in the second sidelink resource pool for transmission of a sidelink positioning reference signal by the first terminal device in response to the request.

[0022] According to a third exemplary aspect, a method performed by a network entity is disclosed, the method comprising: sending or causing sending resource pool information related to a sidelink resource pool to a first terminal device, the sidelink resource pool being configured for one or more other terminal devices, and the one or more other terminal devices being served by corresponding other base stations.

[0023] Any of the disclosed devices (terminal devices, network entities) may be a fixed device or a mobile device. The terminal device may specifically be a user device, such as a mobile device, such as a smartphone, a tablet, a wearable device, a smart watch, a low-power device, an IoT device, an IIoT device, a vehicle, a truck, a drone, an airplane, etc. The terminal device (e.g., a first terminal device) may specifically be able to communicate (send and receive signals and / or data to / from) one or more other terminal devices (e.g., one or more second terminal devices) and / or a network device (such as a base station of a communication network). In general, the terminal device may also be any device capable of communicating with a communication network and / or another terminal device.

[0024] A network device may be understood as a wireless communication station installed at a fixed or mobile location, and may specifically be or include an entity of a radio access network of a communication system. For example, a network device may be a base station of any generation of communication networks (e.g., gNB, eNodeB, NodeB, BTS, etc.) of the 3GPP standard, including the base station, or a part of the base station. Typically, a network device may be or include a hardware or software component that implements a specific function. For example, in one example, a network device may be a location management function LMF. In one example, a network device may be an entity defined by a 3GPP 5G or NR standard (also referred to as a gNB). Therefore, although a network device may be understood as being implemented in a single device or module or being a single device or module, a network device may also be implemented across multiple devices or modules or include multiple devices or modules. Therefore, a network device may be specifically implemented in a fixed device or may be a fixed device. Multiple network devices of an exemplary aspect may specifically establish a communication system or network, which may specifically be a new radio (NR) or a 5G system (5GS) or any other mobile communication system defined by a past or future standard (particularly a subsequent standard of this 3GPP standard). The network devices of the example aspects may be capable of communicating directly and / or indirectly with the example terminal devices.

[0025] The components or functions of any one of the disclosed devices or apparatuses (i.e., any one of the terminal equipment and the network equipment) can be implemented in hardware and / or software. They may include one or more modules or units that provide corresponding functions. For example, they may include at least one processor for executing computer program code to perform the required functions, at least one memory for storing program code, or both. Alternatively, they may include, for example, a circuit system designed to implement the required functions, such as a circuit system implemented in a chipset or chip, such as an integrated circuit. Typically, the device may include, for example, one or more processing components or processors.

[0026] Therefore, according to the corresponding exemplary aspects of the present disclosure, in each case, a corresponding apparatus (i.e., a terminal device and a network device) is also disclosed, which comprises at least one processor and at least one memory comprising computer program code, and the at least one memory and the computer program code are configured to, together with the at least one processor, enable the apparatus to at least perform the method according to the corresponding aspect of the present disclosure.

[0027] However, any of the exemplary aspects disclosed above can generally be performed by an apparatus, which can be a module or component for a device, such as a chip. The disclosed apparatus can include the disclosed components, such as a part, a processor, a memory, or can also include one or more additional components.

[0028] According to exemplary aspects of the present disclosure, in each case, a computer program is also disclosed, which, when executed by a processor of a device, causes the above-mentioned device to perform the method according to the corresponding aspect.

[0029] In each case, the computer program may be stored on a computer-readable storage medium, in particular a tangible and / or non-transitory medium. The computer-readable storage medium may be, for example, a disk or a memory or the like. The computer program may be stored in a computer-readable storage medium in the form of instructions encoding the computer-readable storage medium. The computer-readable storage medium may be used to participate in the operation of a device, such as an internal or external memory, such as a read-only memory (ROM) or a hard disk of a computer, or to distribute the program, such as an optical disk.

[0030] The first terminal device and the second terminal device may be at a distance from each other, so that direct communication can be performed via a sidelink, i.e., without a base station. The first terminal device and the second terminal device may be served by the same or different cells and / or base stations, or may be outside the coverage (i.e., temporarily not served by any base station). It should be noted that, although the example embodiments provided herein are described for the second terminal device, the first terminal device may of course perform sidelink communication with various other terminal devices, which may refer to multiple second terminal devices, or second terminal devices, third terminal devices, fourth terminal devices, etc. Therefore, the first terminal device may then perform the above actions for multiple second terminal devices. For example, the first terminal device may receive resource pool information related to multiple second sidelink resource pools configured for the corresponding multiple second terminal devices, and send corresponding requests to each or at least some of the multiple second terminal devices. Then, the first terminal device may also receive corresponding responses from one or more of the multiple second terminal devices. For example, one or more second terminal devices may be able to reserve resources according to the request, while one or more second terminal devices may not be able to reserve resources according to the request. Based on these one or more responses, a sidelink positioning reference signal may then be sent using resources in the first sidelink resource pool and resources in one or more of the corresponding second resource pools.

[0031] The above aspects can achieve high-precision positioning in SL scenarios by utilizing more sidelink resources in the network (but not necessarily (pre)configured to a single UE). Therefore, bandwidth extension can be achieved, and specifically, the terminal device can send a broadband reference signal (broadband SL PRS) for sidelink positioning, which not only spans the first sidelink resource pool of the first terminal device, but also spans one or more other sidelink resource pools of one or more second terminal devices. Therefore, inter-pool coordination of resource allocation for broadband SL PRS transmission is achieved.

[0032] This provides two advantages. By dynamically requesting and reserving resources from the allocated resource pool of the terminal device, it is possible to avoid configuring a separate or dedicated SL resource pool just for SL PRS transmission. Since SL PRS transmissions usually occur only occasionally, such a separate SL resource pool results in a waste of (semi-)statically reserved resources in this separately configured resource pool. In addition, it is possible to avoid the terminal device having to constantly monitor all configured SL resource pools in the network in order to send broadband SL PRS signals across multiple resource pools. Such monitoring would result in a large amount of energy consumption, or would simply be impossible for certain types of terminal devices, such as terminal devices with reduced SL and / or battery capacity.

[0033] As will be explained in more detail below, the resource pool information may be specifically obtained from the network, such as via dedicated signaling (e.g., via a DL RRC reconfiguration message). In this way, the network may inform the first terminal device of the sidelink resource pool configured for other second sidelink terminal devices (which may be served by respective other base stations) so as to allow the first terminal device to utilize the sidelink resources of the second terminal device to send a broadband reference signal for sidelink positioning. Otherwise, the terminal device would not be able to know the pool configuration of other terminal devices. In contrast, the proposed method allows for inter-resource pool and intra-resource pool coordination for resource reservation and allocation.

[0034] To this end, as described in relation to the third exemplary aspect, a network entity may be provided for sending resource pool information to the first terminal device, the resource pool information being related to the sidelink resource pool configured for one or more other terminal devices (not in the same sidelink resource pool as the first terminal device). In one example, the network entity may be or include a centralized network controller that collects and / or distributes resource pool information related to the sidelink resource pool managed by a plurality of serving base stations. Alternatively, the network entity may be or include a base station that is configured to coordinate with one or more other base stations about the sidelink resource pool, which is configured or will be configured by the corresponding base station. Therefore, the base station may not only provide information about its first sidelink resource pool to the first terminal device, but may also provide information about one or more second sidelink resource pools of the corresponding one or more second terminal devices (which may be served by another base station) to the first terminal device. For example, base stations may inform each other of the resources they have configured for the corresponding sidelink resource pool.

[0035] By sending a request as described above, the terminal device can request other terminal devices in other resource pools, for example by sending SL control information (such as SCI, as will be described in more detail below), to reserve resources for the requesting UE to send broadband SLPRS transmissions. This is different from the known use of SCI, which is sent from the terminal device to reserve resources only for its own SL transmissions and only use its own SSL transmission resource pool for transmission. Therefore, the proposed SCI does not need to contain information about any reserved resources, but rather indicates a request for resource reservation for other UEs.

[0036] Accordingly, if available, the corresponding second terminal device can then reserve resources in its corresponding second sidelink resource pool. For example, the corresponding second terminal device can send control information in its resource pool (e.g., SCI) that is used to reserve resources for SL PRS transmission. This is also different from the known concept of sending SCI from a terminal device to reserve resources only for its own SL transmission. As will be described in more detail below, in particular, the transmission of control information by the second terminal device can enable a conventional terminal device using the same pool to avoid selecting resources that will be reserved for SL PRS transmission.

[0037] Then, the second terminal device in the corresponding second resource pool can respond to the requesting first terminal device. For example, in the case where resources are available at the corresponding second terminal device, the corresponding second terminal device can reserve resources in the corresponding second side link resource pool, and can send a positive response to indicate that the resources are reserved according to the request. For example, in the case where resources are not available at the corresponding second terminal device, the corresponding second terminal device may not reserve resources in the corresponding second side link resource pool, and can send a negative response. As will be explained in more detail below, for the response, the second terminal device can use the resources reserved by the requesting terminal device, which is in the resource pool of the requesting first terminal device. Contrary to the known concept, a terminal device can only reserve resources for its own SL transmission.

[0038] Based on the corresponding response from the corresponding second terminal device, the first terminal can determine the final resources that can be used to send the positioning reference signal. For example, the terminal device can staggeredly send multiple control information messages (such as SCI messages) across the frequency domain in the corresponding second resource pool (indicated by the corresponding second terminal device that resources are reserved for it) in order to perform broadband SL PRS transmission. Compared with the traditional 1-to-1 mapping between SCI and the relevant SL transmission, the proposed method allows the use of multiple control messages (such as SCI messages) to reserve and indicate resources for a single broadband SL PRS transmission across multiple SL resource pools. As will be explained in more detail below, different resource pools may be discontinuous, or there may be overlap between different resource pools in the time domain and / or frequency domain. In the latter case, the corresponding control message of the SL PRS can be sent on the first (lowest) subchannel of the overlapping part. If there is no overlap, SCI is sent for each pool, for example using the first subchannel.

[0039] Since the first terminal device has received the resource pool information related to the second sidelink resource pool, the request can be sent based on the received resource pool information. For example, the first terminal device may know the Rx resources of the second resource pool of the second terminal device, so that the first terminal device can send the request in such Rx resources of the second resource pool. In the case where there is an overlap between the resources of the first resource pool and the second resource pool (for example, between the TX resources of the first resource pool and the RX resources of the second resource pool), the first terminal device may preferably use such overlapping resources to send the request to the corresponding second terminal device.

[0040] For example, a request may be sent (and received) in a physical sidelink control channel PSCCH. In one example, a request may be sent (and received) in a control information message, such as a sidelink control information (SCI) message. In one example, an information field of a sidelink control information message may be provided for sending a request. This field may not have an associated data payload, so in this case, the first terminal device may not indicate any specific resources to be reserved or any resources to be used for a response by a second terminal device. In one example, a request is sent (and received) in a physical sidelink shared channel or in a data payload associated with a sidelink control information message. This allows the second terminal device to be indicated or provided with additional information, such as specific resources to be reserved or resources to be used for a response by a second terminal device. For example, a request may be sent (and received) in resources that overlap between a first sidelink resource pool and a second sidelink resource pool. Since the first terminal device has usually monitored this overlapping portion, this has the advantage of avoiding resource conflicts. Even in the absence of overlap, a request can still be sent (and received) in a second sidelink resource pool. For example, the first terminal device may randomly select a resource in the corresponding second sidelink resource pool.

[0041] In one example, the request includes information indicating the amount of resources requested to be reserved in the second side link resource pool. Additionally or alternatively, the request may include information indicating the (specific) resources requested to be reserved in the second side link resource pool. Additionally or alternatively, the request may include information indicating resources reserved by the first terminal device in the first side link resource pool for use by the second terminal device in responding to the request, which avoids resource conflicts for the response of the second terminal device. To this end, the first terminal device may announce the resources reserved for the response in the first pool, for example by sending a control message, such as an SCI message. The request may also include information indicating transmission parameters to be used by the second terminal device in responding to the request.

[0042] The first terminal device may include means for reserving resources in the first resource pool for use by the second terminal device in responding to the request. As described above, the first terminal device may, for example, notify the resources reserved for the response in the first pool by sending a control message, such as an SCI message. These reserved resources may then be indicated to the second terminal device, for example, by a request as described above.

[0043] The first terminal device includes a component for: determining, based on the response, resources for sending a sidelink positioning reference signal. For example, the first terminal device may determine an overlap or gap between different second sidelink resource pools, where resources have been reserved for SL PRS transmission. For example, the first terminal device may determine a final set of resources to be used for transmission of the SL PRS by the first device based on resources already reserved for SL PRS transmission. Based on this, the first terminal device may determine a control message to be used for sending the SL PRS.

[0044] The response may include information about resources in the second sidelink resource pool used for transmission of a sidelink positioning reference signal by the first terminal device.

[0045] For example, the response may indicate that a particular resource requested by the first terminal device is available, for example by means of an acknowledgement (ACK) message.Thus, the response may comprise an acknowledgement that the resources in the second sidelink resource pool requested by the first terminal device with the request are to be reserved.

[0046] For example, the response may indicate that a particular resource requested by the first terminal device is not available, for example by means of a negative acknowledgement (NACK) message.To this end, the response may comprise a negative acknowledgement of resources in the second sidelink resource pool requested by the first terminal device to be reserved using the request.

[0047] For example, the response may indicate specific resources that the second terminal has reserved, for example in the case where the first terminal device has not requested any specific resources, or in the case where the resources requested by the first terminal device are not available. To this end, the response may include: information indicating resources in the second sidelink resource pool reserved by the second terminal device for transmission of the sidelink positioning reference signal.

[0048] The response is not necessarily an explicit response, but may also be implicit or implied. For example, the second terminal may only send an (explicit) response, and the first terminal device may only expect an (explicit) response in the case of an acknowledgement. In the case where the first terminal device does not receive a response, this is interpreted as an implicit negative acknowledgement. Alternatively, the second terminal may only send an (explicit) response, and the first terminal device may only expect an (explicit) response in the case of a negative acknowledgement. In the case where the first terminal device does not receive a response, this is interpreted as an implicit acknowledgement. As can be seen in these scenarios, the second terminal device does not necessarily send a response to the request to the first terminal device, and the first terminal device does not necessarily receive a response to the request from the second terminal device.

[0049] Similar to the description above regarding the request, the response may be (sent and) received in resources that overlap between the first sidelink resource pool and the second sidelink resource pool, which avoids resource conflicts because the overlapping portions have already been monitored.

[0050] However, the response may typically be (sent and) received in (any non-overlapping) resources in the first sidelink resource pool, in particular in the absence of overlapping portions. For example, resources in the first sidelink resource pool may be reserved by the first terminal device for use by the second terminal device in responding to the request. For example, the response may be (sent and) received in resources or data payload of a physical sidelink feedback channel associated with a sidelink control information message used by the first terminal device to reserve resources in the first sidelink resource pool.

[0051] In one example, the response may be (sent and) received in a response message or data payload associated with a (new) sidelink control information message sent by the second terminal device. In one example, the sidelink control information message includes: information representing transmission parameters (e.g., related to time and / or frequency resources and / or modulation and coding scheme) used by the second terminal device for the response.

[0052] The response may be (sent and) received in resources in the second sidelink resource pool, in particular where the first terminal device does not indicate any resources reserved for the response (e.g., in the first resource pool). To this end, the first UE may begin monitoring the second sidelink resource pool. In one example, the response may be (sent) and received in resources of a physical sidelink feedback channel associated with a sidelink control information message that includes or is associated with a request sent by the first terminal device in the second sidelink resource pool.

[0053] In a further alternative, the response may be (sent and) received in a separate or new sidelink transmission.

[0054] The resource pool information may be received from the network (and sent by the network) via dedicated signaling, in particular via RRC signaling, for example in an RRC reconfiguration message. Alternatively, the resource pool information may be received and sent via a broadcast message, in particular using a system information block SIB, such as SIB12. The resource pool information may be sent to the first terminal device by the network on its own initiative or at the request of the first terminal device.

[0055] The first terminal device may comprise means for receiving information about overlaps between configured resource pools from the network. This information may be determined by the network and then sent to the first terminal device (and typically to all other terminal devices it serves). Thus, the network may comprise corresponding means for sending. Alternatively, the information about overlaps may also be determined by the first terminal device itself.

[0056] The first terminal device may include a component for: receiving information from the network about whether the sidelink positioning reference signal transmission is allowed in resources outside the configured resource pool. Therefore, the network may include a corresponding component for sending the corresponding information. If transmission resources outside the configured resource pool are allowed, the first terminal device is able to send SL PRS substantially over the entire carrier bandwidth, even if the resource pool does not cover or does not cover the entire carrier bandwidth continuously. If transmission in resources outside the configured resource pool is not allowed, the first terminal device can still send discontinuous SL PRS in the case where the resource pool is not distributed continuously over the carrier bandwidth. If transmission in resources outside the configured resource pool is not allowed and the resource pool is not distributed over the carrier bandwidth (neither continuous nor discontinuous), broadband SL PRS transmission is not possible (at least no transmission covers substantially the entire carrier bandwidth).

[0057] In order to send a sidelink positioning reference signal, the first terminal device may send multiple control information messages, in particular a sidelink control information message. The control information message may indicate scheduling resources across multiple pools for sending SL PRS via a control message associated with a broadband SL PRS. For example, one control information message may be used for each sidelink resource pool. However, in the event of overlapping resource pools, a separate control information message may be sent in the overlapping resources, as described below. Although multiple control information messages may be sent in different frequency resources, they may also be sent in the same time resources.

[0058] If the first sidelink resource pool and the second sidelink resource pool overlap in the time domain and the frequency domain, the control information message of the sidelink positioning reference signal is sent in the resources overlapping between the first sidelink resource pool and the second sidelink resource pool. For example, the control information message can be sent in a predefined (e.g., first or lowest) subchannel of the overlapping resources of the resource pools.

[0059] The sidelink positioning reference signal may substantially cover the bandwidth of the first sidelink resource pool and the second sidelink resource pool. For example, the sidelink positioning reference signal may substantially cover the bandwidth of the first sidelink resource pool and the plurality of second sidelink resource pools. For example, the sidelink positioning reference signal may substantially cover the entire carrier bandwidth (e.g., continuous or discontinuous).

[0060] The sidelink positioning reference signal may cover resources in the frequency domain outside the first sidelink resource pool and the second sidelink resource pool. As described above, the network may provide information to the first terminal indicating that the sidelink position reference signal transmission is allowed in resources outside the configured resource pool. The first terminal device is then able to send the SL PRS substantially over the entire carrier bandwidth, even when the resource pool does not cover or does not cover the entire carrier bandwidth contiguously.

[0061] The resources in the second side link resource pool used for transmitting the side link positioning reference signal by the first terminal device can be reserved after the timer expires. The timer can be a random timer. The second terminal device can reserve the corresponding resources by sending a control information message (such as SCI) in its second resource pool. This allows other (traditional and non-traditional) terminal devices in the second resource pool to know that the second terminal device has reserved the corresponding resources. Specifically, the traditional terminal device can then avoid using the reserved resources. The other (non-traditional) terminal devices in the second side link resource pool will know that the second terminal device will respond to the request of the first terminal device, and they can avoid doing so. The other (non-traditional) terminal devices in the second side link resource pool can also confirm to the second terminal that they will not respond to the request.

[0062] It should be understood that the embodiments disclosed herein are presented by way of example only and not limitation.

[0063] Here, the disclosure of a method step should also be regarded as the disclosure of a component for performing the corresponding method step. Similarly, the disclosure of a component for performing a method step should also be regarded as the disclosure of the method step itself.

[0064] Other features of the present disclosure will become apparent from the following detailed description considered in conjunction with the accompanying drawings. It should be understood, however, that the drawings are for illustrative purposes only and not as a definition of the limitations of the present disclosure, for which reference should be made to the appended claims. It should be further understood that the drawings are not drawn to scale and that they are intended only to conceptually illustrate the structures and processes described herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] Figure 1 An exemplary embodiment of a sidelink resource pool is shown in a time-frequency diagram;

[0066] Figure 2 An exemplary arrangement of different sidelink resource pools is shown in the time-frequency diagram;

[0067] Figure 3 A schematic diagram is shown illustrating an example radio environment in which exemplary embodiments of the present disclosure may be performed;

[0068] Figure 4a , Figure 4b Sidelink resource pools for a first UE and a second UE are shown in a time-frequency diagram illustrating example embodiments of different aspects;

[0069] Figure 5a , Figure 5b Sidelink resource pools for a first UE, a second UE, and a third UE are shown in a time-frequency diagram illustrating example embodiments of different aspects;

[0070] Figure 6a , Figure 6b illustrates resource pools for continuous and discontinuous configurations in the time-frequency domain;

[0071] Figure 7 An exemplary decision tree for determining how to send a wideband SL PRS is shown;

[0072] Figure 8a , Figure 8b , Figure 8c An exemplary signaling flow diagram is shown;

[0073] Fig. 9 An exemplary signaling flow diagram is shown;

[0074] Fig.10 A schematic diagram is shown, which illustrates a block diagram of an exemplary embodiment of an apparatus according to the present disclosure;

[0075] Fig.11 A block diagram illustrating an exemplary embodiment of a base station; and

[0076] Fig.12 A schematic diagram illustrating an example of a tangible, non-transitory computer-readable storage medium. DETAILED DESCRIPTION

[0077] The following description is intended to deepen the understanding of the present disclosure, and should be understood as supplementary to and read together with the description of example embodiments of the present disclosure provided in the above Abstract section of this specification.

[0078] In the following, an example communication system in which the present disclosure may be applied is described. Although the specific radio system in the following example is a 5G system, this is only a non-limiting example.

[0079] Figure 3 A 5G communication network is shown, which introduces new radio technology and an architecture in which different sublayers of the RAN can be split into two logical entities in a communication network control element (such as a BS or gNB), referred to as a distributed unit (DU) and a central unit (CU). For example, a CU is a logical node that controls the operation of one or more DUs via a fronthaul interface (referred to as an F1 interface). A DU is a logical node that includes a subset of gNB functionality, depending on the functional split option.

[0080] like Figure 3 As shown in , as an example of a first terminal device of an exemplary aspect of the present disclosure, a first user equipment (UE) 310 is connected to cell 1 of a network device or base station (gNB 320) via a communication beam of cell 1. Figure 3 In the example shown in FIG, the gNB 330 is equipped with a CU 333 and two DUs 331 and 332 connected to the CU 333 via an F1 interface. Figure 3 As shown in the example in , the first UE 310 can be connected to multiple other cells. Naturally, in each cell, there can be multiple UEs, and these UEs are connected to the corresponding cells. Similar to cell 1, cell 2 and cell 3 are controlled by gNB 25 and 26, respectively, and each cell provides multiple beams 1 to 3, which can be used for beam diversity or beam hopping. Multiple second UEs 320, UE321, UE 322, UE 323 are shown as examples of second terminal devices according to different aspects of the present invention, and these second UEs can be connected to the same or different base stations. UE (such as the current UE 323) may also be outside the network coverage. However, the first UE 310 is still able to communicate directly with the second UE 320, UE 321, UE 322, UE 323 via sidelink communication without the need for a corresponding base station. As Figure 3As shown in , each base station or gNB of a cell is connected to the core network, such as 5GC, via a corresponding interface (indicated as NG interface). In addition, each gNB of the cell is connected to each other by means of a specific interface, which is called, for example, an Xn-C interface. Any of these network entities (such as gNB, gNB-DU, gNB-CU and / or 5GC) can be individually or collectively used as an example of a base station or a part thereof according to the present disclosure.

[0081] Now go to Figure 4a , Figure 4b , Figure 4a , Figure 4b The sidelink resource pools (hereinafter also referred to as resource pools or simply pools) of the first UE and the second UE are shown in the time-frequency diagram, and example embodiments of different aspects will be illustrated and described below.

[0082] As shown in the figure, two sidelink resource pools are configured for different UEs in the time-frequency diagram. The first sidelink resource pool Tx / Rx pool 1 401 is configured for the first (or requesting) UE, and the second sidelink resource pool Tx / Rx pool 2 402 is configured for the second (or responding) UE.

[0083] The network will indicate to the first UE (and typically to all UEs configured with corresponding sidelink resource pools) a list of resource pools configured for all UEs (eg, served by certain base stations and / or in certain areas).

[0084] A first UE configured with a first SL resource pool wants to send a broadband SL PRS. The first UE sends a request REQ 403 in a second sidelink resource pool 402 so that it is received by a second UE configured with a second SL resource pool 402 (and typically in multiple second resource pools different from the first pool, and therefore to multiple second UEs) in order to reserve resources in the corresponding second pool for sending the SL PRS.

[0085] In case there is an overlap in time / frequency between the first sidelink resource pool 401 and the second sidelink resource pool 402, the first UE may preferably use the overlapped portion to send the request to avoid any resource conflict, since the first UE already monitors this common portion of the resource pool. Figure 4a As shown in , the first UE sends a request in the second sidelink resource pool 402. However, the first UE does not necessarily monitor the second resource pool in advance to make a resource selection, but may randomly select a resource in the second pool.

[0086] As shown in Figure 4, the first UE sends the request by sending a control message (such as sidelink control information SCI). Here, the SCI itself contains a field indicating the request, which has no associated data payload and therefore does not indicate any reserved resources in the sending pool. However, in an alternative, the request can be indicated within the data payload associated with the SCI.

[0087] The request message for resource reservation for SL PRS may indicate the amount of SL time / frequency resources to be reserved and / or the specific SL time / frequency resources to be reserved. Optionally, the request message may indicate the resources in the first sidelink resource pool reserved by the first UE (so that the second UE can respond to the request on these resources), and the transmission parameters (such as modulation and coding scheme MCS) used by the second UE to send its response in these resources. In this case, Figure 4a As shown in FIG. 4 , the first UE sends an SCI 404 in the first sidelink resource pool 401 to indicate reserved resources (which will be used by the second UE to respond) to avoid other UEs in the first pool 401 from selecting these resources.

[0088] The second UE receiving such a request then makes a resource reservation 405 in the second sidelink resource pool 402 for SL PRS transmission based on its sensing history. The second UE makes a resource reservation 405 by sending an SCI 406 in the second pool 402 after the expiration of a random timer. The SCI 406 has two purposes: it avoids legacy (and all other) UEs from selecting reserved resources for SL PRS, thereby avoiding resource conflicts. In addition, the SCI 406 lets other UEs in the second pool 402 know that it is responding to the first UE so that other UEs do not do the same thing in the second resource pool 402. Together with the random timer, this avoids multiple second UEs reserving resources for the same request. Other UEs in the second pool 402 can send an acknowledgement to the second UE to indicate that they will not respond to the request (e.g., via PSFCH resources associated with the SCI, as described below).

[0089] The second UE then sends a response RESP 407 to the first UE's request. Typically, the response message 407 may contain an ACK or NACK in the case where the first UE specifically requested resources, or it may contain a set of reserved resources in the second pool (e.g., in the case where the first UE did not request specific resources).

[0090] If there is an overlap in time and frequency between the first pool and the second pool, the second UE may use the overlapping portion to send the response 407 to avoid any resource conflict since it has been monitoring this common portion of the resource pools.

[0091] However, if Figure 4a As shown in , if there is no overlap and if the first UE has indicated that it reserves resources in the first pool 401 for the second UE to respond, the second UE sends a response 407 in the first pool 401. In case of an ACK / NACK type response, the second UE may use the PSFCH resources associated with the SCI 404 sent by the first UE in the first pool 401. Alternatively, the second UE may respond using a payload associated with this SCI 404. In case the second UE changes transmission parameters (e.g. an MCS value different from the MCS value indicated in the SCI 404 sent by the first UE for resource reservation in the first pool), the second UE sends a new SCI associated with the RESP message.

[0092] However, if the first UE does not indicate any reserved resources for the response, the second UE sends a response in the second pool based on sensing. In this case, the first UE starts monitoring the second resource pool 402 after sending a request 403 to receive a corresponding response. In the case of an ACK / NACK type response, the second UE can use the PSFCH resources in the second pool 403 associated with the SCI of the request message 403 sent by the first UE. Alternatively, the second UE can also create a new SL transmission to respond.

[0093] Now go to Figure 4b , based on the response 407 received from the second UE configured with the second resource pool (and generally any responses received from UEs configured with different resource pools), the first UE determines a final set of time / frequency resources in all pools for sending the broadband SL PRS and sends the SL PRS 410 on the determined set of resources.

[0094] To this end, the first UE sends a plurality of staggered SCIs 408, 409, thereby sending one SCI for each resource pool spanned by the wideband SL PRS. The staggered SCIs are placed at the same time instance but in different subchannels, so that the individual SCIs 408, 409 are always placed at the lowest (or any other predefined) subchannel of the resource pool, and / or at the lowest (or any other predefined) subchannel of any overlapping portion of the resource pool in case of resource overlap.

[0095] Now combine Figure 5a , Figure 5b Further exemplary embodiments are described.

[0096] The network configures multiple SL resource pools for different UEs. Preferably, the resource pools overlap in frequency and / or time, which enables efficient communication between UEs that originally belong to different resource pools.

[0097] exist Figure 5a , Figure 5b In the example shown in , the network configures three different sidelink resource pools Tx1 501, Tx2 502a, and Tx3 503 for SL transmission, and three different sidelink resource pools Rx1 501, Rx2 502b, and Rx3 503 for SL reception. The network configures Tx1 and Rx1 for the first UE (UE1), configures Tx2 and Rx2 for the second UE (UE2), and configures Tx3 and Rx3 for another second (or third) UE (UE3).

[0098] from Figure 5a , Figure 5b It can be seen that Rx2 overlaps with parts of Tx1 and Tx3, which enables UE2 to also monitor the transmissions of UE1 and UE3. Thus, in contrast to the example given in Figure 4, there are three UEs involving respective different resource pools, and the resource pools partially overlap.

[0099] First, the network indicates at least to the first UE1 all resource pools configured for the corresponding UE (but generally all resource pool configurations will be indicated to all UEs). This is different from the known method, in which the UE has no knowledge of the pool configuration of other UEs when sent via dedicated signaling. Such indication of resource pools can be sent to the UE via a broadcast message (such as using SIB12) or via dedicated signaling (e.g., RRCReconfiguration message) or proactively or at the UE's request (e.g., when the UE wants to send wideband SLPRS).

[0100] Optionally, the network may indicate the overlapping parts of the resource pools to the UE, for example via the SIB. Alternatively, the UE may determine that the resource pools overlap by analyzing the configuration received from the network.

[0101] To avoid the problem that different gNBs may configure resource pools in different ways, thereby avoiding communication and coordination between UEs configured by different gNBs, for example at the network edge, a centralized controller may be utilized to coordinate and / or configure resource pools for a group of gNBs, for example in a given area.

[0102] Such a centralized network controller (e.g., location management function LMF) can collect resource pool information belonging to different serving gNBs (e.g., via NRPPa or NGAP signaling). Alternatively, a controller (such as LMF) can also determine the SL resource pool configuration for a group of gNBs. Furthermore, in this case, the controller can notify the UE and gNB about the pool configuration. To notify the UE, in the case of LMF, the signaling can be carried out via LPP signaling, while in the case of another core network entity, the signaling can be carried out via NGAP+RRC signaling. To notify the gNB, the signaling can be carried out via NRPPa or NGAP protocol.

[0103] Alternatively or additionally, neighboring gNBs may coordinate with each other, e.g., via the Xn interface, to configure the same SL resource pool, or collect each other's resource pool information and share it with the UEs they serve. For example, a serving gNB announces a resource pool configured for a group of neighboring gNBs.

[0104] The network may also configure validity criteria associated with the resource pools, e.g., based on or pertaining to a certain area (e.g., a group of gNBs), time, distance, etc. This allows for common pool configuration, e.g., within a certain area, time, or distance, such that pool information received from one gNB is also valid in neighboring gNBs. In this way, UEs may seamlessly coordinate with each other for SL PRS transmissions, e.g., utilizing overlapping pools.

[0105] We now consider the case where a first UE1 wishes to optimally send a wideband SL PRS across multiple resource pools. Therefore, UE1 sends a request message REQ to other UEs in these pools, preferably by using overlapping parts of the resource pools.

[0106] More specifically, in Figure 5a In the example of , UE1 wants to send broadband SLPRS among multiple resource pools Rx1, Rx2, and Rx3. Figure 5a As shown, UE1 sends a request REQ message in these pools 502b, 503 (indicated by arrows 504, 505), but preferably uses the overlapping part of the resource pools to communicate with the UE. In this case, UE1 uses the overlapping part of Rx2 and Tx1 to send its request in this pool. If there is no overlapping part between the resource pools of the UE (for example, Figure 5a Between UE1 and UE3 in the pool), the request message is sent to the corresponding non-shared pool.

[0107] The request message may indicate a request for SL resource recommendation from other UEs, for example, by indicating the amount of resources required. Additionally or alternatively, the request message indicates a request for whether certain (certain) sidelink resources (e.g., subchannel X, time slot Y) are idle. Additionally or alternatively, the request message indicates the criticality level of the request by sending a bandwidth extension reason (e.g., a reason for sending a wideband SLPRS, such as due to high accuracy requirements). Additionally or alternatively, the request message indicates which or how many UEs in the corresponding pool can respond.

[0108] Consider the following two alternatives for UEs in other pools to respond to the request message.

[0109] In a first alternative, the requesting UE reserves SL resources in its own pool so that UEs in other pools can respond using these resources. In this case, the request message indicates the resource pool and the resources reserved for UEs in other pools to respond. For example, a request sent by the first UE1 indicates Tx1 / Rx1 and any resources reserved therein for UEs responding using other pools.

[0110] In a second alternative, the requesting UE does not reserve any SL resources in its first sidelink resource pool and starts monitoring the corresponding second pools after sending the request to obtain responses from the corresponding UEs configured with these second pools. For example, UE1 monitors resource pool Tx3, where UE3 will send its response.

[0111] For example, the network may configure and indicate to the UE which of the above alternatives are allowed. Alternatively, it may be left to the requesting UE to implement. For example, if indicated by the requesting UE, the UE may respond using the reserved resources in the pool of the requesting UE, otherwise the UE may respond using its own pool.

[0112] The UEs (UE2, UE3) in other pools reserve corresponding SL resources for the requesting UE (UE1) in their own (multiple) pools to send broadband SL PRS, and respond to the requesting UE with corresponding response messages RESP 506, RESP 507, which indicate the reserved resources or provide ACK / NACK for the resources requested by the requesting UE.

[0113] As indicated by arrows 508, 509, the corresponding responding UE also sends a legacy SL SCI in its own resource pool to let other UEs (including legacy UEs) know the resource reservation for SL PRS transmission, so as to avoid selecting these resources for their own SL transmission.

[0114] In order to avoid all second UEs in a given resource pool responding at the same time, the second UE may start taking action after a random timer and then only send the above-mentioned SCI 508, SCI 509 to reserve resources. Once the above-mentioned SCI 508, SCI 509 are received, all other second UEs stop their actions. For example, the MAC CE may indicate that the SCI is intended to stop non-traditional actions of other UEs. Optionally, the other UEs to be stopped may also send ACK or NACK to the UE sending SCI 508, SCI 509 to indicate that they will not respond to the request either. The ACK or NACK may be sent using PSFCH resources associated with traditional SCI 508, SCI 509 sent by other UEs, or may be sent as a dedicated SL transmission.

[0115] As described above, if available, the respective second UEs (UE2, UE3) may use overlapping portions of the resource pool(s) to send the response messages RESP 506, 507 (eg Figure 5a Alternatively, they may respond using resources in the first resource pool reserved by the requesting UE (as in the case of alternative 1 above, such as Figure 5a As another alternative, the responding second UE may use its own pool (as in the case of alternative 2 above).

[0116] In the case of an ACK / NACK type response message, the UE may be silent in the case of an ACK response and only a NACK is sent. Therefore, in this scenario, the second UE may not send a response and the first UE may not receive a response, but the first UE still knows that the resources in the second sidelink resource pool are reserved and used for SL PRS transmission.

[0117] If the requesting UE is not aware of any other resource pools that other UEs are configured with (e.g. Figure 5a In the example, the first US (UE1) is unaware that UE3 is configured with a separate resource pool "Rx4", not shown in the figure), the responding UE may also indicate the resource pool configuration of the corresponding pool (for example, UE3 responds to UE1 that certain resources in Rx4 are idle, and provides the resource pool configuration of Rx4, such as indicating its subchannel and time slot configuration, and any other required resource pool information).

[0118] Based on the response message it receives ( Figure 5a506, 507), the first UE1 making the request determines the SL resources for sending the broadband SL PRS in the multiple pools. The first UE1 making the request indicates the scheduled SL resources across the multiple pools for sending the SL PRS (such as SCI) to other UEs via the control message 510 and the control message 511 associated with the broadband SL PRS (such as SCI). Figure 3 ).

[0119] Here, each SCI 510, SCI 511 is transmitted using the first (or any other predefined) subchannel of the overlapping part of two overlapping resource pools and / or the first (or any other predefined) subchannel of a (non-overlapping) resource pool.

[0120] UEs in different pools interested in receiving the SL PRS decode the control message and receive the relevant wideband SL PRS in multiple pools for positioning measurements.

[0121] In the following, further examples and embodiments are described, which may be combined with the exemplary embodiments and aspects described herein and which may be modified according to these examples and embodiments.

[0122] The request message REQ and the response message RESP may be sent in a broadcast manner so that all UEs in an area can receive the message.

[0123] Although the above mainly considers NR SL resource allocation mode 1, in one example, the request message can be sent based on NR SL resource configuration mode 2 (or LTE SL mode 4) including random resource selection or via another listen-before-talk process. In another example, the request message can be sent via another contention-based method, such as through random resource selection, so that the first UE making the request does not need to monitor multiple resource pools before its request (which may result in significant power consumption).

[0124] In one example, the UE may broadcast the request and / or control message of the first UE to account for the wider audibility of these messages. Specifically, the UE forwards the request UE1 request message or the SCI control message to other UEs in its vicinity, for example, via broadcast. This is to avoid any hidden node problems and to make different resource pools and / or neighboring different UEs aware of the request or transmission of SLPRS. In addition, this ensures that there will be no conflict with the resource aggregation requested by a relatively distant UE that cannot receive the REQ message in the first stage.

[0125] In one example, the request message indicates a priority of the request. The priority value may be accompanied and / or associated with a reason for sending such a request, for example, the reason indicating a need to request the UE to increase the bandwidth or resources used.

[0126] In one example, the ACK response is implicit, i.e., if the UE observes that the resources requested by the requesting UE are free, the UE does not send a response message, whereas in case of expected resource conflicts, they respond with a NACK message.

[0127] In one example, the resource pool may be (pre)configured continuously or discontinuously over time and / or frequency. Figure 6a In the example, the continuous configuration resource pools 601, 602, and 603 in the time-frequency domain are described. Figure 6b 6 is described for discontinuously configured resource pools 601, 603 in the time-frequency domain. In the case of discontinuous resource pools, the network can determine whether resources outside the configured pools (i.e., resources within the gaps between pools or above or below the pools) can be used to send wideband SLPRS. Therefore, the transmission of SL PRS can be continuous or discontinuous in the frequency domain, as shown in FIG6 for continuous wideband SL PRS 604 and discontinuous wideband SL PRS 605. Then, the configuration of SL PRS (e.g., the pattern of time / frequency resources) needs to match the allowed resource size and the gaps between RPs.

[0128] Based on the configuration of the available resource pool provided by the network, the first UE may follow a decision tree, such as Figure 7 to determine how to send broadband SL PRS and how to configure SL PRS mode and resources accordingly.

[0129] First, it may be determined whether the resource pool is substantially distributed over the carrier bandwidth or a certain frequency domain (action 701).

[0130] If the resource pool is basically distributed over the carrier bandwidth or a certain frequency domain (e.g. Figure 7 If the resource pools are configured or arranged continuously in the frequency domain, a continuous broadband SL PRS may be sent (action 705).

[0131] If the resource pools are configured or arranged discontinuously in the frequency domain, it may be considered whether the network allows the transmission of SL PRS outside the configured resource pools (action 704). If the network allows the transmission of SL PRS outside the configured resource pools, a continuous broadband SL PRS may be sent (action 705), e.g. Figure 6bIf the network does not allow the transmission of SL PRS outside the configured resource pool, a discontinuous broadband SL PRS may be sent (action 706), e.g. Figure 6b SL PRS 605 shown in Figure 6.

[0132] In the case where the resource pool is not substantially distributed over the carrier bandwidth or a certain frequency domain, it may also be considered whether the network allows the transmission of the SL PRS outside the configured resource pool (action 705). If the network allows the transmission of the SL PRS outside the configured resource pool, a continuous wideband SL PRS may be sent (action 705). If the network does not allow the transmission of the SL PRS outside the configured resource pool, a wideband SL PRS may not be sent (action 707) because the desired bandwidth or frequency domain may not be substantially covered continuously or discontinuously.

[0133] In some embodiments, a UE (rather than a resource pool) may send / receive SLPRS on a bandwidth portion, frequency band, or carrier, such as if they are configured with the same digital technology. Therefore, in the disclosed exemplary aspects and examples, the term "resource pool" may be replaced with the term "bandwidth portion", "frequency band", or "carrier".

[0134] Next, we will refer to Figure 8a , Figure 8b , Figure 8c ,as well as Fig. 9 The signaling flow chart illustrates the signaling process.

[0135] exist Figure 8a , Figure 8b , Figure 8c ,as well as Fig. 9 In the scenario, UE1_1 (as an example of a first terminal device) is served by gNB1, and UE2_1, UE2_2 (as examples of second terminal devices), and UE2_3 are served by gNB2. UE2_3 is a legacy UE that may not support the method described herein, i.e., it may not be able to participate in the inter-pool coordination of resource allocation for the described wideband SL PRS transmission.

[0136] Now go to Figure 8a , Figure 8b , Figure 8c , a central network coordination entity (LMF in this case) collects the resource pool configurations of the different gNBs it controls. In turn, this entity provides all resource pool configurations to the gNBs. The gNBs provide the same configuration information of all resource pools to all UEs they serve, such as via a broadcast message.

[0137] In more detail, configuration of SL resource pools is performed. To this end, UE1_1 is configured with a first resource pool Tx1 / Rx1 by gNB1 (action 801), and UE2_1, UE2_2 and UE2_3 (legacy UEs) are configured with a second resource pool Tx2 / Rx2 by gNB2 (actions 802, 803, 804). The LMF requests information about the corresponding SL resource pool configuration from gNB1 and gNB2 (action 805). gNB1 and gNB2 provide the requested information to the LMF (action 806). In turn, the LMF may provide each gNB with the configured SL resource pools of the corresponding other gNBs (action 807). Each gNB may then provide (e.g., broadcast) all SL resource pool configurations to the UEs served by the corresponding gNB (action 808).

[0138] UE1_1 then determines the wideband SL PRS to be transmitted and detects that (its own) resource pool Tx1 / Rx1 overlaps with the second resource pool Tx2 / Rx2 (action 809). UE1_1 then sends a request message in the second resource pool Rx2 to transmit the SLPRS (action 810). UE2_1 monitors the resource pool Rx2 and reserves resources in its own resource pool (Rx2 / Tx2) (action 811). Although UE2_2 also monitors the resource pool Rx2 and may have also received the request, the timer of UE2_1 has expired early. UE2_1 then sends an SCI indicating the SL PRS resources to be reserved in Tx2 / Rx2 to the other UEs served by gNB2 (i.e., UE2_2 and UE2_3) (action 812). UE2_2 sends a confirmation to UE2_1 to indicate or confirm that UE2_2 will not respond to the request (action 813). Therefore, upon sensing the SCI of UE2_1, UE2_2 will withdraw from responding to the request of UE1 (action 814). Since in action 812, the legacy UE2_3 also receives the SCI sent by UE2_1, it will also avoid selecting the resources indicated in the SCI (action 815).

[0139] UE2_1 then sends a response message in the resources associated with UE1_1 in the sidelink resource pool Rx1 (action 816). Alternatively, for the case where UE2_1 is not provided with any reserved resources in the resource pool Rx1, UE1_1 monitors the SL resource pool Tx2 of UE2_1 (action 817), and UE2_1 sends a response message in its own resource pool Tx2 (action 818).

[0140] UE1_1 monitors the resources in its own pool Tx1 / Rx1 (action 819), and sends SCI in Tx1 / Rx1 (action 820). UE1_1 also determines the resources in (multiple) other resource pools for sending SLPRS based on the received (multiple) response messages (action 821), and sends SCI in the determined resource pool (here Rx2) (action 822). Therefore, UE1_1 can send a wideband SL PRS (action 823). The wideband SL PRS will not only be received by the UEs in the first SL resource pool Tx1 / Rx1, but also by the devices (such as UE2_1, UE2_2) in the second SL resource pool Tx2 / Rx2. UE2_1 and UE2_2 can therefore perform positioning measurements on the SL PRS (action 824).

[0141] Now go to Fig. 9 , describes an alternative way to configure SL resource pools (with Figure 8a , Figure 8b , Figure 8c In this case, there is no central coordination entity and the gNBs coordinate with each other to obtain each other's resource pool configuration information. In turn, they share all collected resource pool information belonging to different gNBs with the UEs they serve, such as via broadcast messages.

[0142] That is, more specifically, UE1_1 is configured with a first resource pool Tx1 / Rx1 by gNB1 (action 901), and UE2_1, UE2_2 are configured with a second resource pool Tx2 / Rx2 by gNB2 (action 902). gNB1 requests information about the corresponding SL resource pool configuration from gNB2 (action 903). gNB2 provides the requested information to gNB1 (action 904). Similarly, gNB2 requests information about the corresponding SL resource pool configuration from gNB1 (action 905), and gNB1 provides the requested information to gNB2 (action 906). Each gNB can then provide (e.g., broadcast) all SL resource pool configurations to the UEs served by the corresponding gNB (actions 907, 908).

[0143] The remaining steps can be followed as Figure 8a , Figure 8b , Figure 8c Same as described.

[0144] Now go to Fig.10 , a block diagram of an exemplary embodiment of a first terminal device, or a second terminal device, or a UE 1000 according to the present disclosure is shown. For example, the UE 1000 may be a smart phone, a tablet computer, a laptop computer, a smart watch, a smart bracelet, an IoT device, or a vehicle or a part thereof.

[0145] UE 1000 includes a processor 1001. Processor 1001 may represent a single processor or two or more processors, which are at least partially coupled, for example, via a bus. Processor 1001 executes program code stored in program memory 1002 (for example, when executed on processor 1001, a mobile device 1000 connected to base station 1000 executes a program code according to one or more embodiments of the method or part thereof of the present disclosure), and is interfaced with main memory 1003. Program memory 1002 may also include an operating system for processor 1001. Some or all of memories 1002 and 1003 may also be included in processor 1001.

[0146] One or both of the processor's main memory and program memory (e.g., program memory 1002 and main memory 1003) may be fixedly connected to the processor (e.g., processor 1001), or at least partially removable from the processor, for example in the form of a memory card or memory stick.

[0147] The program memory (e.g., program memory 1002) may be, for example, a non-volatile memory. For example, it may be any of a flash memory (or a portion thereof), a ROM, a PROM, an EPROM, an MRAM, or a FeRAM (or a portion thereof), or a hard disk (or a portion thereof), to name a few examples. For example, the program memory may, for example, include a first memory portion that is fixedly mounted and a second memory portion that is removable, for example in the form of a removable SD memory card.

[0148] The main memory (e.g., main memory 1003) may be, for example, a volatile memory. For example, it may be a DRAM memory. For example, when executing an operating system, an application, a program, etc., it may be used as a working memory of the processor 1001.

[0149] The processor 1001 also controls a communication interface 1104 (e.g., a radio interface) configured to receive and / or send data and / or information. For example, the communication interface 1004 may be configured to send and / or receive radio signals from a radio node such as a base station, in particular as described herein. It should be understood that any computer program code-based processing required to receive and / or evaluate radio signals may be stored in the communication interface 1004's own memory and executed by the communication interface 1004's own processor, and / or it may be stored, for example, in the memory 1003 and executed, for example, by the processor 1001.

[0150] The communication interface 1004 may be specifically configured to communicate according to a cellular communication system (such as 2G / 3G / 4G / 5G or a next generation cellular communication system). The terminal device 1000 may communicate with a base station using the radio interface 1004 .

[0151] For example, the communication interface 1004 may also include a BLE and / or Bluetooth radio interface, including a BLE transmitter, receiver, or transceiver. For example, the radio interface 1104 may additionally or alternatively include a WLAN radio interface, including at least a WLAN transmitter, receiver, or transceiver.

[0152] Components 1002 to 1004 of terminal 1000 may be connected to processor 1001 , for example, by means of one or more serial and / or parallel buses.

[0153] It should be understood that the terminal device 1000 may include various other components. For example, the terminal device 1000 may optionally include a user interface (eg, a touch-sensitive display, a keyboard, a touchpad, a display, etc.).

[0154] Fig.11 1 is a block diagram of an exemplary embodiment of a network entity (such as a base station or gNB). For example, as described above, the network device 1100 can be configured to schedule and / or send signals to a UE.

[0155] The network device 1100 includes a processor 1101. The processor 1101 may represent a single processor, or two or more processors coupled at least in part via a bus, for example. The processor 1101 executes program codes stored in a program memory 1102 (e.g., program codes that cause the network device 1100 to execute alone or together with the terminal device 1000 embodiment or part thereof according to the present disclosure), and is connected to a main memory 1103 interface.

[0156] Program memory 1102 may also include an operating system for processor 1101. Some or all of memories 1102 and 1103 may also be included in processor 1101.

[0157] In addition, the processor 1101 controls a communication interface 1104, which is configured, for example, to communicate according to a cellular communication system (such as a 2G / 3G / 4G / 5G cellular communication system). The communication interface 1104 of the apparatus 1100 may be implemented, for example, by a radio head, and may be provided for communication between a network device and a terminal device.

[0158] Components 1102 to 1104 of device 1100 may be connected to processor 1101 , for example, by means of one or more serial and / or parallel buses.

[0159] It should be understood that the apparatus 1000, 1100 may include various other components.

[0160] Fig.12 is a schematic diagram of an example of a tangible, non-transitory computer-readable storage medium according to the present disclosure, which can be used to implement Fig.10 Memory 1002 or Fig.11 Memory 1102. To this end, Fig.12 Shown are a flash memory 1200 that can be, for example, soldered or glued to a printed circuit board, a solid-state drive 1201 including multiple memory chips (e.g., flash memory chips), a magnetic hard disk drive 1202, a secure digital (SD) card 1203, a universal serial bus (USB) memory stick 1204, an optical storage medium 1205 (such as a CD-ROM or DVD), and a magnetic storage medium 1206.

[0161] Any connections presented in the described embodiments should be understood in a manner that the components involved are coupled in operation. Therefore, the connection may be direct or indirect, there may be any number or combination of elements in between, and there may be only functional relationships between components.

[0162] Furthermore, as used herein, the term 'circuitry' refers to any of the following:

[0163] (a) Pure hardware circuit implementation (such as implementation in analog and / or digital circuit systems only)

[0164] (b) a combination of circuitry and software (and / or firmware), such as: (i) a combination of processor(s), or (ii) portions of processor(s) / software (including digital signal processor(s), software and memory(s) that work together to enable a device such as a mobile phone to perform various functions), and

[0165] (c) Circuitry that requires software or firmware to function (even if the software or firmware is not physically present), such as microprocessor(s) or portion(s) of microprocessor(s).

[0166] This definition of 'circuitry' applies to all uses of the term herein, including in any claims. As another example, as used herein, the term 'circuitry' also covers an implementation of merely a processor (or multiple processors) or portion of a processor and its accompanying software and / or firmware. For example, the term 'circuitry' also covers a baseband integrated circuit or an application processor integrated circuit for a mobile phone.

[0167] Any processor mentioned in this document (especially but not limited to Fig.10 and Fig.11The processors 1001 and 1101 in the embodiment may be any suitable type of processor. Any processor may include, but is not limited to, one or more microprocessors, one or more processors with accompanying (multiple) digital signal processors, one or more processors without accompanying (multiple) digital signal processors, one or more special-purpose computer chips, one or more field programmable gate arrays (FPGAs), one or more controllers, one or more application-specific integrated circuits (ASICS), or one or more computers. The relevant structure / hardware has been programmed to perform the functions described.

[0168] In addition, any of the actions or steps described or illustrated herein may be implemented using executable instructions in a general or special purpose processor and stored on a computer readable storage medium (e.g., disk, memory, etc.) for execution by such a processor. References to 'computer readable storage medium' should be understood to cover special purpose circuits such as FPGAs, ASICs, signal processing devices, and other devices.

[0169] In addition, any of the actions described or illustrated herein may be implemented using executable instructions in a general or special purpose processor and stored on a computer readable storage medium (e.g., disk, memory, etc.) for execution by such a processor. References to 'computer readable storage medium' should be understood to cover special purpose circuits such as FPGAs, ASICs, signal processing devices and other devices.

[0170] The wording "A, B, C or a combination thereof" or "at least one of A, B and C" may be understood as not being exhaustive and including at least the following: (i) A, or (ii) B, or (iii) C, or (iv) A and B, or (vi) B and C, or (vii) A, B and C.

[0171] It should be understood that the embodiments disclosed herein are exemplary only, and any feature presented for a specific exemplary embodiment may be used in any aspect of the present disclosure alone or in combination with any feature presented for the same or another specific exemplary embodiment and / or with any other features not mentioned. It should also be understood that any feature presented for an exemplary embodiment in a particular category may also be used in a corresponding manner in any other category of exemplary embodiments.

[0172] References

[0173] [1] 3GPP TR 38.845 V17.0.0, "Study on scenarios and requirements of in-coverage, partial coverage, and out-of-coverage NR positioning use cases (Release 17)", September 2021

[0174] [2] "System Architecture and Solution Development; High-Accuracy Positioning for C-V2X – 5G Automotive Association." [Online]. Available: https: / / 5gaa.org / news / system-architecture-and-solution-development-high-accuracy-positioning-for-c-v2x / . [Accessed: December 12, 2021]

[0175] [3] M.H.C. Garcia et al., "A Tutorial on 5G NR V2X Communications," in IEEE Communications Surveys & Tutorials, Vol. 23, No. 3, pp. 1972 - 2026, Q3 2021, doi: 10.1109 / COMST.2021.3057017.

[0176] [4] "Carrier Aggregation explained." [Online]. Available: https: / / www.3gpp.org / technologies / keywords-acronyms / 101-carrier-aggregation-explained.

[0177] [5] 3GPP TR 37.985 V16.0.0, "Overall description of Radio Access Network (RAN) aspects for Vehicle-to-everything (V2X) based on LTE and NR (Release 16)", June 2020. Note: In the translation of the access date in [3], since the original text has an incorrect date (November 12, 2021), it is corrected to December 12, 2021 for the correct English expression. If you have specific requirements not to correct the date error, you can adjust it back according to your needs.

Claims

1. A first terminal device, configured for sidelink communication in a first sidelink resource pool, the first terminal device comprising means for: - receiving resource pool information related to a second sidelink resource pool configured for a second terminal device; - sending a request to the second terminal device via a sidelink communication to reserve resources in the second sidelink resource pool for transmission of a sidelink positioning reference signal by the first terminal device; - receiving a response to the request from the second terminal device via a sidelink communication; and - Based on the response, sending a sidelink positioning reference signal using resources in the first sidelink resource pool and resources in the second sidelink resource pool. 2 . The first terminal device according to claim 1 , wherein the request is sent based on the received resource pool information.

3. The first terminal device according to any one of claims 1 to 2, wherein the request is sent in one or more of the following items: - Physical sidelink control channel; - control information messages; -Sidelink Control Information message; -Information field of the sidelink control information message; - Physical sidelink shared channel; - a data payload associated with a sidelink control information message; - overlapping resources between the first sidelink resource pool and the second sidelink resource pool; -The second sidelink resource pool.

4. The first terminal device according to any one of claims 1 to 3, wherein the request comprises one or more of the following items: - information indicating the amount of resources requested to be reserved in the second sidelink resource pool; - information indicating resources requested to be reserved in the second sidelink resource pool; - information indicating resources in the first sidelink resource pool reserved by the first terminal device for use by the second terminal device to respond to the request; and / or - Information representative of transmission parameters to be used by said second terminal device for responding to said request.

5. The first terminal device according to any one of claims 1 to 4, wherein the first terminal device comprises means for: - reserving resources in the first resource pool for use by the second terminal device in responding to the request.

6. The first terminal device according to any one of claims 1 to 5, wherein the first terminal device comprises means for: - Based on the response, determining resources for sending the sidelink positioning reference signal.

7. A first terminal device according to any one of claims 1 to 6, wherein the response comprises information about the following items: the resources in the second sidelink resource pool used for transmitting the sidelink positioning reference signal by the first terminal device.

8. The first terminal device according to claim 7, wherein the response comprises one of the following items: - confirmation of the resources in the second sidelink resource pool requested by the first terminal device to be reserved using the request; - a negative acknowledgement of the resources in the second sidelink resource pool requested by the first terminal device to be reserved by means of the request; -Information representing resources in the second sidelink resource pool reserved by the second terminal device for the transmission of the sidelink positioning reference signal.

9. The first terminal device according to claim 7 or 8, wherein the response is received in one of the following: - overlapping resources between the first sidelink resource pool and the second sidelink resource pool; - resources in the first sidelink resource pool; - resources reserved by the first terminal device in the first sidelink resource pool, the resources to be used by the second terminal device to respond to the request; - resources of a physical sidelink feedback channel associated with a sidelink control information message used by the first terminal device to reserve resources in the first sidelink resource pool; - a data payload associated with a sidelink control information message used by the first terminal device to reserve resources in the first sidelink resource pool; - a data payload associated with a sidelink control information message sent by the second terminal device, the sidelink control information message optionally comprising information indicative of transmission parameters used by the second terminal device for the response; - resources in the second sidelink resource pool; - resources of a physical sidelink feedback channel associated with a sidelink control information message comprising or associated with said request sent by said first terminal device in said second sidelink resource pool; - Separate sidelink transmission.

10. The first terminal device according to any one of claims 1 to 9, wherein the resource pool information is received from the network, in particular via one of the following: -RRC signalling; - broadcast a message; or -System Information Block SIB.

11. The first terminal device according to any one of claims 1 to 10, wherein the first terminal device comprises components for one or more of the following: - receiving information from the network about overlaps between configured resource pools; - receiving information from the network about whether sidelink positioning reference signal transmission is allowed in resources outside the configured resource pool.

12. The first terminal device according to any one of claims 1 to 11, wherein in order to send the sidelink positioning reference signal, one or more of the following items are sent by the first terminal device: - a plurality of control information messages, in particular sidelink control information messages; - multiple control information messages in the same time resource; and / or -Multiple control information messages in different frequency resources.

13. A first terminal device according to any one of claims 1 to 12, wherein when the first sidelink resource pool and the second sidelink resource pool overlap in time domain and frequency domain, a control information message for the sidelink positioning reference signal is sent in resources overlapping between the first sidelink resource pool and the second sidelink resource pool.

14. The first terminal device according to any one of claims 1 to 13, wherein the sidelink positioning reference signal substantially covers the bandwidth of the first sidelink resource pool and the second sidelink resource pool.

15. The first terminal device according to any one of claims 1 to 14, wherein the sidelink positioning reference signal covers resources in the frequency domain outside the first sidelink resource pool and the second sidelink resource pool.

16. A second terminal device configured for sidelink communication in a second sidelink resource pool, the second terminal device comprising means for: - receiving a request via sidelink communication from a first terminal device configured for sidelink communication in a first sidelink resource pool, the request being used to reserve resources in the second sidelink resource pool for transmission of a sidelink positioning reference signal by the first terminal device; - sending a response to the request to the first terminal device via a sidelink communication; as well as - In response to the request, reserving resources in the second sidelink resource pool for transmission of a sidelink positioning reference signal by the first terminal device.

17. The second terminal device according to claim 13 or 14, wherein the resources in the second sidelink resource pool used for transmitting the sidelink positioning reference signal by the first terminal device are reserved after the timer expires.

18. A network entity, the network entity comprising means for: - sending or causing sending of resource pool information related to a sidelink resource pool to the first terminal device, the sidelink resource pool being configured for one or more other terminal devices, the one or more other terminal devices being served by corresponding other base stations.

19. The network entity according to claim 18, wherein the network entity is: - a centralized network controller that collects and / or distributes resource pool information related to sidelink resource pools managed by a plurality of serving base stations; or - a base station configured to coordinate with one or more other base stations regarding the sidelink resource pool, which is configured or to be configured by the corresponding base station.

20. A method performed by a first terminal device, the first terminal device being configured for sidelink communication in a first sidelink resource pool, the method comprising: - receiving resource pool information related to a second sidelink resource pool configured for a second terminal device; - sending a request to the second terminal device via a sidelink communication to reserve resources in the second sidelink resource pool for transmission of a sidelink positioning reference signal by the first terminal device; - receiving a response to the request from the second terminal device via sidelink communication; as well as - Based on the response, sending a sidelink positioning reference signal using resources in the first sidelink resource pool and resources in the second sidelink resource pool.

21. A method performed by a second terminal device, the second terminal device being configured for sidelink communication in a second sidelink resource pool, the method comprising: - receiving a request via sidelink communication from a first terminal device configured for sidelink communication in a first sidelink resource pool, the request being used to reserve resources in the second sidelink resource pool for transmission of a sidelink positioning reference signal by the first terminal device; - sending a response to the request to the first terminal device via a sidelink communication; as well as - In response to the request, reserving resources in the second sidelink resource pool for transmission of a sidelink positioning reference signal by the first terminal device.

22. A method performed by a network entity, the method comprising: Resource pool information related to a sidelink resource pool is sent or caused to be sent to the first terminal device, the sidelink resource pool being configured for one or more other terminal devices, the one or more other terminal devices being served by corresponding other base stations.

23. Computer program code which, when executed by a processor of an apparatus, causes the apparatus to perform the method according to claim 21 or 22.

24. A computer storage medium comprising computer program code according to claim 23.