Resource conflict indication for sidelink positioning across one or more network entities

Abstract

The UE determines a conflict in sidelink resources for transmission by more than one user equipment and transmits an indication of the determined conflict to a network entity. A network entity receives an indication of conflicts in sidelink resources for transmission by more than one user equipment and allocates new sidelink resources to a UE connected to the network entity and being one of the more than one user equipment. The location management function receives, from the UE, an indication of a collision in sidelink resources sent by more than one user equipment, the indication indicating that the UE (s) use the sidelink resources and have a collision. The LMF sends an indication of a conflict in the sidelink resource to a network entity that assigns the sidelink resource.

Description

CLAIM OF PRIORITY / CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Application No. 63 / 466,046, filed May 12, 2023, the entire contents of which are incorporated herein by reference. TECHNICAL FIELD

[0002] Examples of embodiments herein relate generally to sidelink communications, and more specifically, to collisions in resources for sidelink positioning. BACKGROUND

[0003] Sidelink (SL) communications allow for direct communication between two user equipment (UEs), which are wireless devices and typically mobile devices in a wireless network, without going through a base station. That is, the communication occurs directly between the two UEs.

[0004] In order for UEs to communicate via sidelink, resources must be assigned to the UEs. Some of these resources are used for reference signals, such as, for example, SL positioning reference signals (PRS), although SL resources are also used for SL / D2D (device-to-device) / ProSe (Proximity Services) discovery, data communication, sensing, and associated control signaling, etc. At times, the same or similar resources can be assigned to different UEs for SL communication with other UEs, and these resources can cause collisions. SUMMARY

[0005] This section is intended to include examples and is not intended to be limiting.

[0006] In an example embodiment, a method is disclosed that includes determining, at a user equipment, a collision in sidelink resources for transmission by more than one user equipment, and transmitting, by the user equipment, an indication of the determined collision to a network entity.

[0007] An additional example embodiment includes a computer program comprising instructions for carrying out the method of the preceding paragraph when the computer program is run on an apparatus. According to this paragraph, the computer program is a computer program product comprising a computer-readable medium bearing instructions embodied in said medium for use with the apparatus. Another example is a computer program according to this paragraph, wherein the program is directly loadable into the internal memory of the apparatus.

[0008] An example apparatus includes one or more processors and one or more memories storing instructions that, when executed by the one or more processors, cause the apparatus to at least perform: determining, at a user equipment, a collision in sidelink resources for transmission by more than one user equipment, and transmitting, by the user equipment, an indication of the determined collision to a network entity.

[0009] An example computer program product comprises a computer readable storage medium bearing instructions which, when executed by an apparatus, cause the apparatus to at least perform the following: determining, at a user equipment, a collision in sidelink resources for transmission by more than one user equipment; and transmitting, by the user equipment to a network entity, an indication of the determined collision.

[0010] In another example embodiment, an apparatus comprises means for performing the following: determining, at a user equipment, a collision in sidelink resources for transmission by more than one user equipment; and transmitting, by the user equipment to a network entity, an indication of the determined collision.

[0011] In an example embodiment, a method is disclosed comprising: receiving, by a network entity, an indication of a collision in sidelink resources for transmission by more than one user equipment; and allocating, by the network entity to a user equipment connected to the network entity and being one of the more than one user equipment, a new sidelink resource.

[0012] An additional example embodiment comprises a computer program comprising instructions for performing the method of the preceding paragraph when the computer program is run on an apparatus. According to the present paragraph, the computer program is a computer program product comprising a computer-readable medium bearing instructions embodied in the medium for use with the apparatus. Another example is the computer program according to the present paragraph, wherein the program is directly loadable into the internal memory of the apparatus.

[0013] An example apparatus comprises one or more processors and one or more memories storing instructions which, when executed by the one or more processors, cause the apparatus to at least perform the following: receiving, by a network entity, an indication of a collision in sidelink resources for transmission by more than one user equipment; and allocating, by the network entity to a user equipment connected to the network entity and being one of the more than one user equipment, a new sidelink resource.

[0014] An example computer program product comprises a computer readable storage medium bearing instructions which, when executed by an apparatus, cause the apparatus to at least perform the following: receiving, by a network entity, an indication of a collision in sidelink resources for transmission by more than one user equipment; and allocating, by the network entity to a user equipment connected to the network entity and being one of the more than one user equipment, a new sidelink resource.

[0015] In another example embodiment, an apparatus comprises means for performing the following: receiving, by a network entity, an indication of a collision in sidelink resources for transmission by more than one user equipment; and allocating, by the network entity to a user equipment connected to the network entity and being one of the more than one user equipment, a new sidelink resource.

[0016] In an example embodiment, a method is disclosed that includes receiving, by a location management function and from a user equipment, an indication of a collision in sidelink resources transmitted by more than one user equipment, the indication indicating that a user equipment uses a sidelink resource and has a collision; and sending, by the location management function, an indication of the collision in the sidelink resources to a network entity that assigned the sidelink resources.

[0017] An additional example embodiment includes a computer program comprising instructions for carrying out the method of the preceding paragraph when the computer program is run on an apparatus. According to the present paragraph, the computer program is a computer program product comprising a computer-readable medium bearing instructions embodied in said medium for use with the apparatus. Another example is the computer program according to the present paragraph, wherein the program is directly loadable into the internal memory of the apparatus.

[0018] An example apparatus comprises one or more processors and one or more memories storing instructions that, when executed by the one or more processors, cause the apparatus to at least perform: receiving, by a location management function and from a user equipment, an indication of a collision in sidelink resources transmitted by more than one user equipment, the indication indicating that a user equipment uses a sidelink resource and has a collision; and sending, by the location management function, an indication of the collision in the sidelink resources to a network entity that assigned the sidelink resources.

[0019] An example computer program product comprises a computer-readable storage medium bearing instructions that, when executed by an apparatus, cause the apparatus to at least perform: receiving, by a location management function and from a user equipment, an indication of a collision in sidelink resources transmitted by more than one user equipment, the indication indicating that a user equipment uses a sidelink resource and has a collision; and sending, by the location management function, an indication of the collision in the sidelink resources to a network entity that assigned the sidelink resources.

[0020] In another example embodiment, an apparatus comprises means for performing: receiving, by a location management function and from a user equipment, an indication of a collision in sidelink resources transmitted by more than one user equipment, the indication indicating that a user equipment uses a sidelink resource and has a collision; and sending, by the location management function, an indication of the collision in the sidelink resources to a network entity that assigned the sidelink resources. BRIEF DESCRIPTION OF DRAWINGS

[0021] In the drawings:

[0022] Figure 1A is a block diagram of one possible and non-limiting example system in which example embodiments can be practiced;

[0023] Figure 1B is an example of a block diagram of an apparatus suitable for implementing any of the nodes in Figure 1A ;

[0024] Figure 2 An illustration of a SL positioning scenario is provided;

[0025] Figure 3 A scenario for describing issues in SL positioning is illustrated;

[0026] Figure 4 A signaling diagram for describing issues in resource allocation in SL positioning is illustrated;

[0027] FIG. 5 (split into Figure 5A and Figure 5B ) illustrates a signaling diagram for SL resource allocation involving resource conflict indication for one or more network entities such as gNBs; and

[0028] Figure 6 Possible options for warning by a UE to other entities of a conflict in SL resources so that the conflict is resolved are described. DETAILED DESCRIPTION

[0029] In the following, at the end of the DETAILED DESCRIPTION section, abbreviations that can be found in the specification and / or the attached drawings are defined.

[0030] The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any implementation described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other implementations. All of the implementations described in this detailed description are exemplary implementations provided to enable persons skilled in the art to make or use the application, and not as limitations on the scope of the application defined by the claims.

[0031] When more than one appendage reference numeral, word or abbreviation is used with the “ / ” in this description and generally as used in this description, the “ / ” can be interpreted to mean “or,” “and,” or “both.” As used in this document, “at least one of <list of two or more elements>” and “one or more of <list of two or more elements>” and similar phrases, where the list of two or more elements is connected by “and” or “or,” means any one of the listed elements alone, or any two or more of the listed elements in combination.

[0032] As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including,” when used herein, specify the presence of stated features, elements, and / or components, but do not preclude the presence or addition of one or more other features, elements, components, and / or groups thereof.

[0033] Any flow diagram (see, e.g., FIG. 4) or signaling diagram (such as FIG. 5) herein is regarded as a logical flow diagram, as opposed to a programmatic or algorithmic flow diagram, and illustrates the operational Figure 6 ) of exemplary methods, results of execution of computer program instructions embodied on a computer readable memory, functions performed by logic implemented in hardware, and / or inter-connection of components for performing functions in accordance with exemplary embodiments. Block diagrams (such as Figure 1A and Figure 1B ) also illustrate the operational of exemplary methods, results of execution of computer program instructions embodied on a computer readable memory, functions performed by logic implemented in hardware, and / or inter-connection of components for performing functions in accordance with exemplary embodiments.

[0034] Exemplary embodiments herein describe resource collision indication techniques for sidelink positioning across one or more network entities, such as, for example, gNBs. Additional description of these techniques is presented after describing a system in which exemplary embodiments can be used.

[0035] Turning to Figure 1A , this figure shows a block diagram of one possible and non-limiting exemplary system in which exemplary embodiments can be practiced. A number of nodes are shown: a user equipment (UE) 110; a base station 170; and a core network entity (or entities) 190.

[0036] In Figure 1A , a user equipment (UE) 110, as one of the nodes, is in wireless communication with a wireless network 100 via a wireless link 111. The UE 110 is a typically mobile, wireless device that is able to access the wireless network. The UE 110 is illustrated as having one or more antennas 128. The ellipsis 101 indicates that there can be multiple UEs 110.

[0037] A base station 170 that is one of the other nodes in the node but part of the wireless network 100 provides access to the wireless network 100 for wireless devices such as UEs 110. The base station 170 is illustrated as having one or more antennas 158. There are many options for the base station 170. In general, the base station 170 is a RAN node, and in particular can be a gNB, which is the primary term used herein. That is, the base station 170 will be referred to as a gNB 170. However, there are many options for the base station, including an eNB, or options outside of cellular systems.

[0038] There are multiple configurations for the base station 170. One such configuration is a “stand-alone” configuration that includes all circuitry as part of a single unit and access the antennas 158. More commonly today, the circuitry is split into one or more remote nodes 150 (accessing the antennas 158) and a central node 160. For example, for 5G (also referred to as NR), a gNB can include a distributed unit (DU) or a DU and a radio unit (RU) as the remote nodes, and include a central unit (CU) as the central node 160. For LTE, a base station 170 can include an eNB with a remote radio head as the remote node 150 and a baseband unit (BBU) as the central node 160. The remote node(s) 150 are coupled to the central node 160 via one or more links 171. There can be multiple remote nodes 150 for a single central node 160, and this is indicated by the ellipsis 102 indicating multiple remote nodes and the ellipsis 103 indicating additional links 171. The remote nodes 150 are remote in the sense that they are contained in a different physical cabinet than the physical cabinet that contains the corresponding central node 160. The link(s) 171 can be implemented using fiber optics, wireless technology, or any other technology for communicating data.

[0039] Two or more base stations 170 communicate using, for example, links 176. The link(s) 176 can be wired or wireless or both, and can implement, for example, the Xn interface for 5G, the X2 interface for LTE, or other suitable interfaces for other standards.

[0040] The wireless network 100 can include one or more core network entities 190, which are illustrated as a third node, that can include core network functionality and provide connectivity to a data network 191, such as a telephone network and / or a data communications network (e.g., the Internet), via one or more links 181. Such core network functionality for 5G can include Access and Mobility Management Function(s) ((AMF(s)) and / or User Plane Function(s) ((UPF(s)) and / or Session Management Function(s) ((SMF(s)) and / or Location Management Function(s) ((LMF(s)). Such core network functionality for LTE can include MME (Mobility Management Entity) functionality and / or SGW (Serving Gateway) functionality. These are merely exemplary functionality that can be supported by the one or more core network entities 190, and note that both 5G and LTE functionality can be supported. The RAN nodes 170 are coupled to the one or more core network entities 190 via links 131. The links 131 can be implemented, for example, as an NG interface for 5G, or an SI interface for LTE, or other suitable interface for other standards.

[0041] Note that the description herein indicates that a "cell" performs functions, but it should be clear that the base station forming the cell will perform the functions. The cell constitutes a part of the base station. That is, there can be multiple cells per base station. For example, for a single carrier frequency and associated bandwidth, there can be three cells each covering one third of a 360 degree region so that the coverage area of a single base station covers approximately an elliptical or circular shape. Further, each cell can correspond to a single carrier, and a base station can use multiple carriers. Thus, if there are three 120 degree cells per carrier and there are two carriers, then a base station has a total of 6 cells.

[0042] In general, the various embodiments of the user equipment 110 can include, but are not limited to, cellular telephones such as smart phones, mobile phones, handsets, voice over Internet Protocol (VoIP) phones, and / or wireless local loop phones, tablets, portable computers, vehicles or in-vehicle equipment for wireless V2X (vehicle-to-anything) communication, image capture devices such as digital cameras, gaming devices, music storage and playback appliances, Internet appliances (including Internet of Things (IoT) devices), IoT devices with sensors and / or actuators for automated application such as home or industrial automation, portable units or terminals that incorporate combinations of such functions, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), Universal Serial Bus (USB) dongles, smart devices, wireless customer-premises equipment (CPE), loT devices, watches or other wearable devices, head-mounted displays (HMD), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or

[0043] Turning to Figure 1B , this figure is an example of a block diagram of an apparatus 180 suitable for implementing any of the nodes in Figure 1A . The apparatus 180 includes circuitry including one or more processors 120, one or more memories 125, one or more transceivers 130, one or more network (N / W) interfaces (I / F) 155, and user interface (UI) circuitry and elements 157 interconnected through one or more buses 127. As this is an example covering all of the nodes in Figure 1A , some of the nodes can not have all of the circuitry. For example, the base station 170 can not have the UI circuitry and elements 157. All of the nodes can have additional circuitry not described here. Figure 1B This is presented by way of example only.

[0044] Each of the one or more transceivers 130 includes a receiver (Rx) 132 and a transmitter (Tx) 133. The one or more buses 127 can be address buses, data buses, and / or control buses, and can include any interconnection mechanism, such as a mother board or a series of lines on an integrated circuit, optical fiber or other optical communication equipment, and the like. The one or more transceivers 130 are connected to one or more antennas 105, which can be one of the antennas 128 (from the UE 110) or the antennas 158 (from the base station 170), and can communicate using the wireless link 111.

[0045] The one or more memories 125 include computer program code 123. The apparatus 180 includes a module 140, which includes one or both of portions 140-1 and / or 140-2, which can be implemented in a variety of ways. The module 140 can be implemented in hardware as module 140-1, such as being implemented as part of the one or more processors 120. The module 140-1 can also be implemented as an integrated circuit or through other hardware, such as a programmable gate array. In another example, the module 140 can be implemented as a control module 140-2, which is implemented as computer program code (with corresponding instructions) 123 and executed by the one or more processors 120. For example, the one or more memories 125 store instructions that, when executed by the one or more processors 120, cause the apparatus 180 to perform one or more of the operations as described herein. Moreover, the one or more processors 120, the one or more memories 125, and example algorithms (e.g., as flowcharts and / or signaling diagrams) encoded as instructions, programs, or code, are means for causing performance of operations described herein.

[0046] The network interface(s) (N / W I / F(s)) 155 are wired interfaces that communicate using link(s) 156, which can be optical fiber or other wired interface. The link(s) 156 can be the link(s) 131 and / or 176 from Figure 1A The link(s) 131 and / or 176 from Figure 1A The link(s) 131 and / or 176 from

[0047] The apparatus 180 can or can not include UI circuitry and elements 157. These can include a display such as a touchscreen, a speaker, or interface elements such as for a headset. For example, a UE 110 that is a smartphone will typically include at least a touchscreen and a speaker. The UI circuitry and elements 157 can also include circuitry for communicating with external UI elements (not shown) such as displays, keyboards, mice, headsets, etc.

[0048] The computer-readable memory 125 can be of any type suitable to the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, firmware, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The computer-readable memory 125 can be means for performing the storage function. The processor 120 can be of any type suitable to the local technical environment, and can include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multi-core processor architectures, as non-limiting examples. The processor 120 can be means for performing the functions of controlling the apparatus 180, as well as other functions as described herein.

[0049] Having thus introduced one suitable but non-limiting technical context for practicing example embodiments, example embodiments will now be described in more detail.

[0050] Examples herein relate to SL positioning. SL positioning is based on positioning reference signal, SL-PRS, transmissions between an anchor UE and a target UE to enable positioning of the target UE within the precision delay and accuracy requirements of the corresponding SL positioning session. Figure 2 A SL positioning scenario is illustrated in which a target UE 110-2 is performing a SL positioning session, i.e., exchanging SL-PRS with two anchor UEs 110-1 and 110-3, to determine a position 245 of the target UE 110-2. In this example, the reference 240 has both a label as an indication of the position 245 as well as a question mark indicating that the position 245 is not yet known.

[0051] With respect to resource allocation for SL PRS transmissions, schemes 1 and 2 are introduced, which are based on NR SL mode 1 (network controlled) and mode 2 (UE autonomous) resource allocation, respectively.

[0052] In scheme 1 SL-PRS resource allocation, a gNB allocates resources for SL PRS transmissions in the form of dynamic or configured grants.

[0053] SL PRS transmissions can occur in SL resource pools, which can be dedicated to SL positioning or shared with SL communications, referred to as dedicated and shared pools, respectively.

[0054] SL positioning typically involves multiple UEs transmitting SL PRS, especially to estimate the absolute position of a target UE. The multiple UEs transmitting SL PRS can be served by different gNBs, or even some of them can be out-of-coverage (OOC), meaning that these OOC UEs are not served by any gNB at this moment and can use the scheme 2 resource allocation.

[0055] If the resource pools used for SL positioning across UEs in-coverage of different gNBs and OOC UEs overlap in the time and / or frequency domain(s), this can lead to a conflict in SL resource allocation when each gNB applies scheme 1. There is currently no mechanism for a gNB to be aware of the SL resource allocation of another gNB, and therefore, the SL resources allocated by a gNB to the UEs it serves can collide with the SL resources allocated to other UEs served by a different gNB.

[0056] Examples of the problem are illustrated with the scenario in Figure 3 and the associated signaling diagram in Figure 4 , where UEs participating in SL positioning transmit SL-PRS to each other. In Figure 3 , gNB-1 170-1 forms cell 320-1, gNB-2 170-2 forms cell 320-2, and gNB-3 170-3 forms cell 320-3. There are multiple UEs 110. UE-1 110-1 (in cell 320-1) performs SL PRS transmissions 210-1 with UE-3 110-3 (in cell 320-3), SL-PRS transmissions 210-2 with UE-2 110-2 (in cell 320-2), and SL-PRS transmissions 210-3 with UE-4 110-4, which is OOC 330.

[0057] In Figure 4 , UE-4 uses scheme 2 resource allocation, see block 410. UE-3 and gNB 3 use scheme 1 resource allocation, as shown in block 420, which involves a SL scheduling request (SR) from UE-3 to gNB 3 and a SL scheduling assignment (SA) from gNB-3 to UE-3. Similarly, UE-2 and gNB 2 use scheme 1 resource allocation, as shown in block 430, and UE-1 and gNB 1 use scheme 1 resource allocation, as shown in block 440, both of which involve SR and SA signaling. Multiple SL PRS are indicated: 450, 455, 460, and 465.

[0058] More specifically and with reference to Figure 3 and Figure 4 In-coverage UEs-1, UE-2 and UE-3 use resource allocation scheme 1 (see blocks 420, 430 and 440 in Figure 4 However, they are each served by different gNBs 170, and OOC UE4 uses resource allocation scheme 2. Given that the resource pools configured for these UEs overlap, they can obtain conflicting resource grants, e.g., using the same time / frequency / code resource(s). This would result in unsuccessful SL PRS reception at the UEs, either due to half-duplex issues (UE cannot transmit and receive at the same time) or due to interference.

[0059] See blocks 415 (which indicates that resources in scheme 2 can collide with scheme 1 RAs for in-coverage) and 425, 435 and 445 (which indicates that the SAs of scheme 1 RAs for UEs 1, 2 and 3 can collide with the SA of OOC 330 or each other). These issues can result in unsuccessful SL PRS reception due to resource collision, as shown in blocks 470, 475, 480 and 485.

[0060] Thus, with dedicated resource pools for SL positioning, the issues would involve the UEs performing SL positioning, while interference or half-duplex issues that can arise from conflicting resource usage can easily degrade the quality of service for SL positioning. With shared resource pools between SL positioning and SL communications (where collisions in resource allocation can also degrade the quality of SL communications), the situation can become even worse when the UEs sharing the resources are served by different gNBs.

[0061] Regarding resource pools, a SL resource pool is a (pre)configured set of time / frequency resources where UEs transmit using scheduled resources (e.g., subchannels, REs, slots / symbols, etc.) within the resource pool. By (pre)configuration, UEs can be configured to transmit / receive using the same SL resource pool (or overlapping resource pools), respectively. Thus, collisions can occur at the granularity of time / frequency resources, rather than the entire resource pool. For this case, UEs can not even need to know the resource pool IDs of each other, but only detect collisions in time / frequency resources.

[0062] The examples herein propose methods to address the resource collisions that can arise in SL positioning when the UEs participating in SL positioning (which use overlapping SL resource pools in time / frequency / code domain) are served by different cells or are out of coverage.

[0063] A potential resource conflict can be determined, e.g., in case of a configured grant with resources that periodically repeat over time, where although a first instance of resources allocated by different gNBs do not collide, this can create a potential conflict (i.e. in the future). The UE can determine such a potential conflict, e.g., using data in SCI from other SL UEs that indicate resources on which SL transmissions will be made. Thus, by using SCI, the UE can determine whether two UEs will collide. With respect to a collision, the collision can have already occurred when the collision is determined, or it can be expected to occur (e.g., based on received control information or past collisions of resources) and thus be a potential collision. Thus, the term “collision” herein is used to encompass both past occurring collisions and potential collisions.

[0064] In an example method, it is assumed that the UEs are served by different gNBs with scheme 1 resource allocation, or utilize scheme 2 resource allocation if they are out of network coverage, as Figure 3 shown.

[0065] Upon detecting a resource collision of SL PRS transmissions between two UEs, referred to as colliding UEs, the UE indicates this resource collision (has occurred or is expected to occur) to its own serving gNB, to the serving gNB(s) of the colliding UE(s) via, e.g., SDT, or to the LMF, which will in turn inform the serving gNB(s) of the colliding UE(s) involved in the resource allocation. As known, small data transmission (SDT) is a procedure that allows data and / or signaling transmission when the UE remains in RRC_INACTIVE state (i.e. without the need to transition to RRC_CONNECTED state). Note that using SDT is just one example of possible connection mechanisms, and other examples are possible. Optionally, the UE can also indicate any (non-)preferred resources recommended for new resource allocation. Note that one of the colliding UEs can be the indicating UE itself.

[0066] The informed gNBs in turn determine new resources that will avoid the indicated collision and allocate the new resources to the UE(s) they are serving for reliable SL PRS transmission.

[0067] This idea can be applied to both dynamic scheduling and configured grant in scheme 1. Furthermore, the indication of resource collision can be used as a trigger for further inter-gNB resource coordination mechanisms (e.g. per vendor / operator implementation), if any.

[0068] An example implementation of this solution is illustrated in FIG. 5. FIG. 5 is divided into Figure 5A and Figure 5Band signaling diagrams for SL resource allocation involving resource conflict indication to one or more network entities such as gNBs are illustrated. Note that there are multiple options provided to the UE and Figure 5 selects certain options and also exhibits these options in signaling form. The following describes Figure 6 Possible options for warning of conflicts by the UE to other entities are described.

[0069] According to Figure 5, as shown in block 505, Scheme 2 resource allocation is being used. There are multiple UEs 110-1, 110-2, 110-3, and 110-4 and these UEs are capable of performing sidelink transmissions. In block 510, there is a Scheme 1 resource allocation used between UE-3 110-3 and gNB 3 170-3, which includes a SL Scheduling Request (SR) from UE-3 to gNB 3 and then a SL Scheduling Assignment (SA) from gNB 3 to UE-3. The resources in the SA of block 510 are in conflict (or can be in conflict) with one or more of the resources of UE-1, UE-2, or UE-4, as shown in block 515. In block 520, there is a Scheme 1 resource allocation used between UE-2 110-2 and gNB 2 170-2, which includes a SL SR from UE-2 to gNB 2 and then a SL SA from gNB 2 to UE-2. The resources in the SA of block 520 are in conflict (or can be in conflict) with one or more of the resources of UE-1, UE-3, or UE-4, as shown in block 521. In block 525, there is a Scheme 1 resource allocation used between UE-1 110-1 and gNB 1 170-1, which includes a SL SR from UE-1 to gNB 1 and then a SL SA from gNB 1 to UE-1. The resources in the SA of block 525 are in conflict (or can be in conflict) with one or more of the resources of UE-2, UE-3, or UE-4, as shown in block 530.

[0070] Signaling 535-4, 535-3, and 535-2 have SL PRS associated with SCI-4, SCI-3, and SCI-2 sent from UE-4, UE-3, and UE-2, respectively, to UE-1.

[0071] In this example, UE-1 detects a resource collision between UEs transmitting SL PRS. See block 540, where UE-1 determines the colliding SL PRS resources by decoding SCI-4, SCI-3, and SCI-2, which indicate the corresponding resources that will be used for SL transmission. If these resources (e.g., any of these resources) also collide with its own SL PRS transmission resources, UE-1 informs its own serving gNB of the collision, and gNB1 in turn allocates new resources to UE-1. This occurs in block 550, where UE-1 indicates (signaling 553) the collision of SL resources to gNB1, gNB1 allocates new SL resources for PRS Tx in block 554, and gNB1 responds with SL scheduling reassignment (with new resources) in signaling 555. Alternatively or additionally, UE-1 can inform other gNB(s) that assigned the colliding resources. Alternatively or additionally, UE-1 can inform a core network entity, such as, for example, LMF 190, of the collision, and LMF 190 informs gNB1 and / or other gNB(s) to allocate new resources.

[0072] Note that a “collision” can be an exact match in time / frequency / code resources. However, when resources partially or fully overlap, the reception quality can be degraded. Moreover, when using adjacent resources, power spillage can occur between the allocated resources due to, for example, Doppler effects. Thus, while a collision can be an exact match between resources, a collision can also be used for overlapping or adjacent resources. Note also that a potential collision can be between the UE itself and another UE (e.g., between UE1 and UE2), but also between two other UEs detected by the first UE (i.e., UE1 detects a collision between UE2 and UE3).

[0073] In an example embodiment, for a collision between other UEs detected by UE-1, such as, for example, a collision between UE-2, UE-3, and / or UE-4, in a first alternative (Alt. 1) 560, UE-1 indicates the collision to LMF 190. See signaling 562. Note that this example is used to illustrate that there can be multiple collisions with resources of UE-1. Figure 6with more detail. Note that the LMF 190 is an example, and the examples are not limited to LMF. The LMF can be generic and is intended to include any core network entity that performs positioning functions for UEs. In this example, the LMF 190 determines the gNBs corresponding to the indicated UEs in block 565, and the LMF 190 notifies each UE’s corresponding serving gNB of the conflict. In signaling 566, the LMF indicates to gNB-3 170-3 the conflict in SL resources for UE-3, and in signaling 568, the LMF indicates to gNB-2 170-2 the conflict in SL resources for UE-2. Each gNB in turn allocates (block 569) new resources for its corresponding UE’s SL PRS transmissions.

[0074] In another alternative (Alt. 2) 570, UE-1 informs via, for example, SDT, other gNBs that have allocated conflicting resources, which in turn allocate new resources to their UEs. That is, in signaling 573, UE-1 indicates to gNB-3 170-3 via SDT the conflict in SL resources for UE-3, and in signaling 575, UE-1 indicates to gNB-3 170-2 via SDT the conflict in SL resources for UE-2. In block 569, the corresponding gNBs allocate new SL resources for PRS transmissions (Tx) for their corresponding UEs.

[0075] Note that in some example embodiments, for conflicts between other UEs detected by UE-1, such as, for example, between UE-2, UE-3, and / or UE-4, UE-1 can inform its own gNB-1 (directly or via LMF), and gNB-1 can coordinate with other gNBs for resource allocation.

[0076] In signaling 580, gNB-3 sends an SL schedule reassignment to its UE-3. In signaling 585, gNB-2 sends an SL schedule reassignment to its UE-2.

[0077] In addition to the conflict indication, UE-1 can also provide suggestions regarding resource allocation by indicating (non-)preferred resource sets to the gNBs for their new resource allocation (see block 587). This can occur in signaling 553, 573, and / or 575.

[0078] In embodiments, the conflict indication can include one or more of the following (see block 590):

[0079] 1) ID of the UE(s) and / or SL resources that are conflicting;

[0080] 2) Explicit indication of the time / frequency / code resources in conflict (e.g., including SL PRS sequence number), such as RE offset, symbol, slot, subchannel, etc., and ID of SL resource pool, bandwidth part, frequency band, or carrier;

[0081] 3) Implicit indication of the resources in conflict, e.g., if there is a pre- mapping between SCI / control information / PSCCH and SL PRS / PSSCH resources, the UE can just indicate the SCI resource / content; and / or

[0082] 4) Session ID or message sequence ID of SL positioning.

[0083] In embodiments, the resource assignment can include a dynamic scheduling grant (i.e., a set of resources assigned and activated for a single transmission), or a configured grant (e.g., a Type 1 or Type 2 configured grant as in SL communications), i.e., a set of configured resources that are repeated in time and activated / deactivated by additional signaling (e.g., via low or high layer signals).

[0084] Turning to Figure 6 , this figure describes possible options for a UE to alert other entities of a conflict in SL resources. Block 605 is used to help define terminology used. Assume there is a set of UEs capable of performing SL transmissions (one UE performing the method and other UEs in the set), and a corresponding set of gNBs. That is, there is the UE and other UEs in the set, and a corresponding gNB for the UE and other gNBs for the other UEs.

[0085] In block 610, the UE 110 determines that there is a conflict in SL (e.g., PRS) resources for transmission by one or more user equipment. Note that the UE can just need to determine that its own transmission (e.g., itself) can be in conflict. Consider the case where UE-1 determines using SCI-2 (see Figure 5A ) that there is a conflict in resources assigned to UE-1 and UE-2. Thus, UE-1 can perform block 550 to have only its own resources assigned so that its transmission no longer causes a conflict with UE-2. Note also that if both UE-1 and UE-2 are assigned the same resources, this means that a conflict is expected to occur, even if the conflict has not actually occurred yet (e.g., both UE-1 and UE-2 happen to transmit at different times). Of course, the conflict can have occurred previously as well, e.g., UE-1 transmitted but did not receive a response, and UE-1 can consider the conflict in known resources as a problem. These examples are handled by block 611.

[0086] In block 625, the UE 110 determines whether there is a conflict of its own allocated resources by gNB 1 with another (in coverage, IC) UE (UE-X) served by gNB X or an OOC UE. If yes (block 625 = yes), there are three possible options that the UE can implement. There is option 1, block 630, where the UE indicates the conflict to its own gNB (e.g., using block 550 of Figure 5). In option 2, block 635, the UE indicates the conflict to the LMF 190 (e.g., using block 560 of Figure 5), so the LMF can alert other gNB X, and possibly also gNB 1, or just gNB 1. The notified gNBs allocate new resources to their UEs. In option 3, block 640, the UE indicates the conflict to gNB 1 and gNB X (e.g., via blocks 550 and 570 of Figure 5), so these gNBs allocate new resources. Note that for OOC, the options can be more limited, as there is no gNB for the OOC UE. The options include block 630 (where the UE indicates the conflict to its own gNB) or block 635 (where the UE indicates the conflict to the LMF, and the LMF indicates the conflict to the gNB for the UE).

[0087] If block 625 is no, this means (block 650) that there is a conflict in resources between two other UEs, such as UE 2 and UE 3. Again, there are three options. In option 1, block 655, the UE indicates the conflict to the LMF (e.g., see block 560) (so the LMF can alert one or both of the other gNBs for the two UEs). In option 2, block 660, the UE indicates (block 570) the conflict to one or both of the other gNBs (serving the other UEs), so these gNBs allocate new resources. It should be noted that options 1 and 2 can be used to resolve conflicting resources between OOC UE 4 and IC UEs 2 / 3. In option 3, block 665, the UE indicates (block 550) the conflict to the gNB of the UE.

[0088] Additional embodiments are possible. Consider these examples.

[0089] 1. The proposed resource allocation method is not only applicable to SL PRS transmission, but also to any transmission that typically uses SL resources, such as SL / D2D / ProSe discovery, data communication, sensing, and associated control signaling, etc.

[0090] 2. Instead of specific time / frequency / code resources for each UE’s SL PRS transmission, a gNB can allocate a pool (or a subset thereof) of resources for the group of UEs. The allocated resources can be scheduled by one UE for other UEs, or utilized in a distributed manner among the UEs, e.g., with a mode 2 / scheme 2 type of resource allocation mechanism.

[0091] 3. The characteristics of SL PRS transmissions for which resources are to be allocated, such as their bandwidth, periodicity, etc., can be determined by the LMF or a UE (e.g., a server UE, a client UE, or a target UE), which can depend on the positioning QoS requirements.

[0092] 4. Note that the UE-to-LMF signaling can be implemented via LPP or SLPP, and the gNB-to-LMF signaling can be implemented via NRPPa. The UE-to-gNB signaling can use UL control information (e.g., MAC-CE), or RRC signaling, or higher layers.

[0093] 5. The UE indicating the conflict can identify the serving gNB of the conflicting UE based on the cell ID indicated by the conflicting UE (e.g., in a SL discovery message sent by the UE). Alternatively, the UE can use SDT to indicate the resource conflict to one, multiple, or all gNBs that the UE can hear, with the indication containing the conflicting UE ID, etc., as listed above.

[0094] Without in any way limiting the scope, interpretation, or application of the claims appearing below, a technical effect and / or advantage of one or more of the example embodiments disclosed herein is that, by identifying conflicts, more reliable and efficient allocation of SL resources is facilitated, which in turn can result in better QoS, e.g., accuracy and latency of SL positioning, or better reliability of SL communications / any SL transmissions.

[0095] The following are additional examples.

[0096] Example 1. A method comprising: determining, at a user equipment, a conflict in sidelink resources for transmission by more than one user equipment; and sending, by the user equipment, an indication of the determined conflict to a network entity.

[0097] Example 2. The method of example 1, wherein the determined conflict in sidelink resources has previously occurred or is expected to occur.

[0098] Example 3. The method of example 2, wherein the user equipment is one of the more than one user equipment capable of transmitting in the sidelink resources, and the determined conflict exists in one or more of time resources, frequency resources, or code resources of sidelink resources allocated to the user equipment or other user equipment of the more than one user equipment.

[0099] Example 4. The method of any one of examples 1-3, wherein sending the indication of the determined conflict comprises sending the indication of the determined conflict to a network entity that assigned resources for sidelink transmission to the user equipment.

[0100] Example 5. The method of any one of examples 1-4, wherein the user device is one of more than one user device capable of transmitting in the sidelink resources, and wherein transmitting the indication of the determined conflict comprises transmitting the indication of the determined conflict to one or more other network entities that assigned resources for sidelink transmissions to one or more other user devices of the more than one user devices.

[0101] Example 6. The method of example 5, wherein the transmitting the indication comprises transmitting the indication of the determined conflict using small data transmissions between the user device and the one or more other network entities.

[0102] Example 7. The method of any one of examples 1-6, wherein transmitting the indication of the determined conflict further comprises providing, by the user device, a recommendation regarding resource allocation by indicating to one or more network entities that assign resources for sidelink transmissions to one or more user devices for their new resource allocation, one or both of a preferred set of sidelink resources or a non-preferred set of sidelink resources.

[0103] Example 8. The method of any one of examples 1-7, wherein transmitting the indication of the determined conflict comprises transmitting the indication of the determined conflict to a core network entity.

[0104] Example 9. The method of any one of examples 1-8, wherein the user device is one of the more than one user devices capable of transmitting in the sidelink resources, and wherein determining the conflict further comprises determining the conflict by decoding sidelink control information received from other user devices of the more than one user devices.

[0105] Example 10. The method of any one of examples 1-9, wherein the indication of the determined conflict comprises one or more of: an identification of the user device of the more than one user devices, an identification of sidelink resources, or both the identification of the user device of the more than one user devices and the identification of sidelink resources that are conflicting; an explicit indication of time / frequency / code resources that are conflicting, and an identification of a corresponding sidelink resource pool, bandwidth part, frequency band, or carrier; an implicit indication of sidelink resources that are conflicting; or a session identification or a message sequence identification of a sidelink positioning.

[0106] Example 11. The method of any one of examples 1-10, wherein the sidelink resources are used for sidelink positioning reference signal transmissions.

[0107] Example 12. A method comprising: receiving, by a network entity, an indication of a collision in sidelink resources transmitted by more than one user equipment; and allocating, by the network entity, new sidelink resources to a user equipment connected to the network entity and that is one of the more than one user equipment.

[0108] Example 13. The method of example 12, wherein receiving the indication comprises receiving the indication from the user equipment connected to the network entity.

[0109] Example 14. The method of example 12, wherein receiving the indication comprises receiving the indication from a user equipment not served by the network entity, and the indication of the collision indicates that there is a collision in sidelink resources allocated to user equipment connected to the network entity.

[0110] Example 15. The method of example 14, wherein receiving the indication comprises receiving the indication of the collision using a small data transmission from the user equipment.

[0111] Example 16. The method of example 12, wherein receiving the indication comprises receiving the indication from a location management function, and the indication of the collision indicates that there is a collision in sidelink resources allocated to user equipment connected to the network entity.

[0112] Example 17. A method comprising: receiving, by a location management function and from a user equipment, an indication of a collision in sidelink resources transmitted by more than one user equipment, the indication indicating that a user equipment used the sidelink resources and had the collision; and sending, by the location management function, an indication of the collision in the sidelink resources to a network entity that assigned the sidelink resources.

[0113] Example 18. The method of example 17, further comprising determining which network entities correspond to the indicated user equipment, and the sending uses the determined network entities.

[0114] Example 19. A computer program comprising instructions for carrying out the method of any one of claims 1 to 18 when said computer program is run on an apparatus.

[0115] Example 20. The computer program of example 19, wherein the computer program is a computer program product comprising a computer-readable medium bearing instructions embodied therein for use with the apparatus.

[0116] Example 21. The computer program of example 19, wherein the computer program can be directly loadable into the internal memory of the apparatus.

[0117] Example 22. An apparatus comprising means for: determining, at a user equipment, a determined collision in sidelink resources for transmission by more than one user equipment; and transmitting, by the user equipment, an indication of the determined collision to a network entity.

[0118] Example 23. The apparatus of Example 22, wherein the determined collision in sidelink resources has previously occurred or is expected to occur.

[0119] Example 24. The apparatus of Example 23, wherein the user equipment is one of the more than one user equipment capable of transmitting in the sidelink resources, and the determined collision exists in one or more of time resources, frequency resources, or code resources of sidelink resources allocated to the user equipment or other user equipment of the more than one user equipment.

[0120] Example 25. The apparatus of any of Examples 22-24, wherein transmitting the indication of the determined collision comprises transmitting the indication of the determined collision to a network entity that assigned resources for sidelink transmission to the user equipment.

[0121] Example 26. The apparatus of any of Examples 22-25, wherein the user equipment is one of the more than one user equipment capable of transmitting in the sidelink resources, and wherein transmitting the indication of the determined collision comprises transmitting the indication of the determined collision to one or more other network entities that assigned resources for sidelink transmission to one or more other user equipment of the more than one user equipment.

[0122] Example 27. The apparatus of Example 26, wherein the transmitting the indication comprises transmitting the indication of the determined collision using small data transmission between the user equipment and the one or more other network entities.

[0123] Example 28. The apparatus of any of Examples 22-27, wherein transmitting the indication of the determined collision further comprises providing, by the user equipment, a recommendation regarding resource allocation by indicating one or both of a preferred set of sidelink resources or a non-preferred set of sidelink resources to one or more network entities that assign resources for sidelink transmission to one or more user equipment for their new resource allocation.

[0124] Example 29. The apparatus of any of Examples 22-28, wherein transmitting the indication of the determined collision comprises transmitting the indication of the determined collision to a core network entity.

[0125] Example 30. The apparatus of any one of Examples 22 to 29, wherein the user device is one of more than one user device capable of transmitting in the sidelink resources, and wherein determining the conflict further comprises determining the conflict by decoding sidelink control information received from other user devices of the more than one user device.

[0126] Example 31. The apparatus of any one of Examples 22 to 30, wherein the determined indication of the conflict comprises one or more of: an identification of the user device of the more than one user device, an identification of a sidelink resource, or both the identification of the user device of the more than one user device and the identification of a sidelink resource that is conflicting; an explicit indication of time / frequency / code resources that are conflicting, and an identification of a corresponding sidelink resource pool, bandwidth part, frequency band, or carrier; an implicit indication of a sidelink resource that is conflicting; or a session identification or message sequence identification of a sidelink positioning.

[0127] Example 32. The apparatus of any one of Examples 22 to 31, wherein the sidelink resources are used for sidelink positioning reference signal transmissions.

[0128] Example 33. An apparatus comprising means for: receiving, by a network entity, an indication of a conflict in sidelink resources transmitted by more than one user device; and allocating, by the network entity, new sidelink resources to a user device connected to the network entity and that is one of the more than one user device.

[0129] Example 34. The apparatus of Example 33, wherein receiving the indication comprises receiving the indication from the user device connected to the network entity.

[0130] Example 35. The apparatus of Example 33, wherein receiving the indication comprises receiving the indication from a user device that is not served by the network entity, and the indication of the conflict indicates that there is a conflict in sidelink resources allocated to user devices connected to the network entity.

[0131] Example 36. The apparatus of Example 35, wherein receiving the indication comprises receiving the indication of the conflict using a small data transmission from the user device.

[0132] Example 37. The apparatus of Example 33, wherein receiving the indication comprises receiving the indication from a location management function, and the indication of the conflict indicates that there is a conflict in sidelink resources allocated to user devices connected to the network entity.

[0133] Example 38. An apparatus comprising means for performing: receiving, by a location management function and from a user equipment, an indication of a collision in sidelink resources transmitted by more than one user equipment, the indication indicating a user equipment using the sidelink resources and having the collision; and sending, by the location management function, an indication of the collision in the sidelink resources to a network entity that assigned the sidelink resources.

[0134] Example 39. The apparatus of Example 38, wherein the means are further configured to perform: determining which network entities correspond to the indicated user equipment, and the sending uses the determined network entities.

[0135] Example 40. The apparatus of any preceding apparatus example, wherein the means comprise: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the performance of the apparatus.

[0136] Example 41. An apparatus comprising: one or more processors; and one or more memories storing instructions that, when executed by the one or more processors, cause the apparatus to at least perform: determining, at a user equipment, a collision in sidelink resources transmitted by more than one user equipment; and sending, by the user equipment, an indication of the determined collision to a network entity.

[0137] Example 42. An apparatus comprising: one or more processors; and one or more memories storing instructions that, when executed by the one or more processors, cause the apparatus to at least perform: receiving, by a network entity, an indication of a collision in sidelink resources transmitted by more than one user equipment; and allocating, by the network entity, new sidelink resources to a user equipment connected to the network entity and that is one of the more than one user equipment.

[0138] Example 43. An apparatus comprising: one or more processors; and one or more memories storing instructions that, when executed by the one or more processors, cause the apparatus to at least perform: receiving, by a location management function and from a user equipment, an indication of a collision in sidelink resources transmitted by more than one user equipment, the indication indicating a user equipment using the sidelink resources and having the collision; and sending, by the location management function, an indication of the collision in the sidelink resources to a network entity that assigned the sidelink resources.

[0139] As used in this application, the term “circuitry” can refer to one or more or all of the following:

[0140] (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and

[0141] (b) combinations of hardware circuits and software, such as (as applicable): (i) combinations of analog and / or digital hardware circuit(s) with software / firmware

[0142] (c) to a combination of hardware circuits and software (or firmware), such as (as applicable): (i) a combination of hardware circuits and software (or firmware), which work together to

[0143] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation that includes one or more processors and / or

[0144] Embodiments herein can be implemented in software (executed by one or more processors), hardware (e.g., an application specific integrated circuit), or a combination of software and hardware. In an example embodiment, software (e.g., an application Figure 1B In the context of this document, a "computer-readable medium" can be any means that can contain, store, communicate, propagate or transport the program for use by or in connection with the instruction execution system, apparatus or device, such as a computer with one example of a computer described and depicted in FIG. 1. Computer readable medium can comprise a computer-readable storage medium (e.g., memory 125 or other device) that can be any media or means that can contain, store, and / or transfer programming for use by or in connection with an instruction execution system, apparatus, or device, such as a computer. Computer readable storage medium can comprise any medium that is capable of storing or transferring programming code that can be executed by an instruction execution system, apparatus, or device, such as a computer. Computer readable storage medium can not include propagated signals, and thus can be considered tangible. As used herein, the term "non-transitory" therefore merely indicates that the programming code does not reside or exist at a time of being transitory (i.e., in transit by, for example, a propagated signal). As used herein, the term "non-transitory" therefore does not eliminate software that can continue to exist on computer-readable storage medium after it is received or downloaded by a computer. Rather, the term "non-transitory" as used herein eliminates only propagated signals as the computer-readable medium.

[0145] If desired, the different functions discussed herein can be performed in a different order and / or concurrently with each other. Furthermore, if desired, one or more of the above-described functions can be optional or can be combined.

[0146] Although various aspects of the application are set out in the independent claims, other aspects of the application include other combinations of the features set out in the described embodiments and / or in the dependent claims with the features set out in the independent claims, and not just the combinations explicitly set out in the claims.

[0147] It is also noted herein that while the above describes example embodiments of the application, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications which can be made without departing from the scope of the present application as defined in the appended claims.

[0148] The following abbreviations which can be found in the specification and / or drawings, are defined as follows:

[0149] 5G Fifth Generation

[0150] AMF Access and Mobility Management Function

[0151] AS Access Stratum

[0152] BBU Base Band Unit

[0153] CU Central Unit

[0154] D2D Device to Device

[0155] DU Distributed Unit

[0156] eNB (or eNodeB) Evolved Node B (e.g., LTE base station)

[0157] gNB (or gNodeB) Base station for 5G / NR

[0158] IC In-Coverage

[0159] ID Identity

[0160] I / F Interface

[0161] LMF Location Management Function

[0162] LPP LTE Positioning Protocol

[0163] LTE Long Term Evolution

[0164] MAC-CE Medium Access Control - Control Element

[0165] MME Mobility Management Entity

[0166] NRPPa New Radio Positioning Protocol A (or Annex)

[0167] ng or NG Next Generation

[0168] ng-eNB or NG-eNB Next Generation eNB

[0169] NR New Radio

[0170] N / W or NW Network

[0171] OOC Out of Coverage

[0172] ProSe Proximity Service

[0173] PRS Positioning Reference Signal

[0174] PSCCH Physical Sidelink Control Channel

[0175] PSSCH Physical Sidelink Shared Channel

[0176] QoS Quality of Service

[0177] RA Resource Allocation

[0178] RAN Radio Access Network

[0179] RE Resource Element

[0180] Rel Release

[0181] RLC Radio Link Control

[0182] RP Resource Pool (for SL)

[0183] RRH Remote Radio Head

[0184] RRC Radio Resource Control

[0185] RU Radio Unit

[0186] Rx Receiver

[0187] SA Scheduling Assignment

[0188] SCI SL Control Information

[0189] SDT Small Data Transmission

[0190] SGW Serving Gateway

[0191] SL Sidelink

[0192] SLPP Sidelink Positioning Protocol (newly introduced in 3GPP TS 38.355)

[0193] SR scheduling request

[0194] SMF session management function

[0195] Tx transmitter

[0196] UE user equipment (e.g., a wireless, typically mobile device)

[0197] UI user interface

[0198] UPF user plane function

Claims

1. A method comprising: determining, at a user device, a collision in sidelink resources for transmission by more than one user device; and transmitting, by the user device, an indication of the determined collision to a network entity.

2. The method of claim 1, wherein the determined collision in sidelink resources has previously occurred or is expected to occur.

3. The method of claim 2, wherein the user device is one of the more than one user device capable of transmitting in the sidelink resources, and the determined collision exists in one or more of time resources, frequency resources, or code resources of sidelink resources allocated to the user device or other user devices of the more than one user device.

4. The method of any one of claims 1-3, wherein transmitting the indication of the determined collision comprises transmitting the indication of the determined collision to a network entity that assigned resources for sidelink transmission to the user device.

5. The method of any one of claims 1-4, wherein the user device is one of the more than one user device capable of transmitting in the sidelink resources, and wherein transmitting the indication of the determined collision comprises transmitting the indication of the determined collision to one or more other network entities that assigned resources for sidelink transmission to one or more other user devices of the more than one user device.

6. The method of claim 5, wherein the transmitting the indication comprises transmitting the indication of the determined collision using small data transmission between the user device and the one or more other network entities.

7. The method of any one of claims 1-6, wherein transmitting the indication of the determined collision further comprises providing, by the user device, a recommendation regarding resource allocation by indicating one or both of a preferred set of sidelink resources or a non-preferred set of sidelink resources to one or more network entities that assign resources for sidelink transmission to one or more user devices for their new resource allocation.

8. The method of any one of claims 1-7, wherein transmitting the indication of the determined collision comprises transmitting the indication of the determined collision to a core network entity.

9. The method of any one of claims 1-8, wherein the user device is one of the more than one user device capable of transmitting in the sidelink resources, and wherein determining the collision further comprises determining the collision by decoding sidelink control information received from other user devices of the more than one user device.

10. The method of any one of claims 1-9, wherein the indication of the determined collision comprises one or more of: an identification of the user device of the more than one user device, an identification of sidelink resources, or both the identification of the user device of the more than one user device and the identification of sidelink resources that are colliding; an explicit indication of time / frequency / code resources that are colliding, and an identification of a corresponding sidelink resource pool, bandwidth part, frequency band, or carrier; an implicit indication of conflicting sidelink resources; or a session identity or message sequence identity for sidelink positioning.

11. The method of any one of claims 1 to 10, wherein, the sidelink resources are used for sidelink positioning reference signal transmissions.

12. A method comprising: receiving, by a network entity, an indication of a conflict in sidelink resources transmitted by more than one user equipment; and allocating, by the network entity, new sidelink resources to a user equipment connected to the network entity and being one of the more than one user equipment.

13. The method of claim 12, wherein receiving the indication comprises receiving the indication from the user equipment connected to the network entity.

14. The method of claim 12, wherein receiving the indication comprises receiving the indication from a user equipment not served by the network entity, and the indication of the conflict indicates that there is a conflict in sidelink resources allocated to user equipment connected to the network entity.

15. The method of claim 14, wherein receiving the indication comprises receiving the indication of the conflict using a small data transmission from the user equipment.

16. The method of claim 12, wherein receiving the indication comprises receiving the indication from a location management function, and the indication of the conflict indicates that there is a conflict in sidelink resources allocated to user equipment connected to the network entity.

17. A method comprising: receiving, by a location management function and from a user equipment, an indication of a conflict in sidelink resources transmitted by more than one user equipment, the indication indicating that a user equipment used the sidelink resources and had the conflict; and sending, by the location management function, an indication of the conflict in the sidelink resources to a network entity that assigned the sidelink resources.

18. The method of claim 17, further comprising determining which network entities correspond to the indicated user equipment, and the sending uses the determined network entities.

19. A computer program comprising instructions for carrying out the method of any one of claims 1 to 18 when said computer program is run on an apparatus.

20. The computer program of claim 19, wherein the computer program is a computer program product comprising a computer-readable medium bearing instructions embodied therein for use with the apparatus.

21. The computer program of claim 19, wherein the computer program can be directly loadable into the internal memory of the apparatus.

22. An apparatus comprising means for performing: determining, at a user equipment, a conflict in sidelink resources transmitted by more than one user equipment; and sending, by the user equipment, an indication of the determined conflict to a network entity.

23. The apparatus of claim 22, wherein the determined conflict in sidelink resources has previously occurred or is expected to occur.

24. The apparatus of claim 23, wherein the user device is one of the more than one user devices capable of transmitting in the sidelink resources, and the determined collision exists in one or more of time resources, frequency resources, or code resources of sidelink resources allocated to the user device or other user devices of the more than one user devices.

25. The apparatus of any one of claims 22-24, wherein transmitting the indication of the determined collision comprises transmitting the indication of the determined collision to a network entity that assigned resources for sidelink transmissions for the user device.

26. The apparatus of any one of claims 22-25, wherein the user device is one of the more than one user devices capable of transmitting in the sidelink resources, and wherein transmitting the indication of the determined collision comprises transmitting the indication of the determined collision to one or more other network entities that assigned resources for sidelink transmissions for one or more other user devices of the more than one user devices.

27. The apparatus of claim 26, wherein the transmitting the indication comprises transmitting the indication of the determined collision using a small data transmission between the user device and the one or more other network entities.

28. The apparatus of any one of claims 22-27, wherein transmitting the indication of the determined collision further comprises providing a recommendation regarding resource allocation by the user device to one or more network entities that assigned resources for sidelink transmissions for one or more user devices for their new resource allocation by indicating one or both of a preferred set of sidelink resources or a non-preferred set of sidelink resources.

29. The apparatus of any one of claims 22-28, wherein transmitting the indication of the determined collision comprises transmitting the indication of the determined collision to a core network entity.

30. The apparatus of any one of claims 22-29, wherein, the user device is one of the more than one user devices capable of transmitting in the sidelink resources, and wherein determining the collision further comprises determining the collision by decoding sidelink control information received from other user devices of the more than one user devices.

31. The apparatus of any one of claims 22-30, wherein the indication of the determined collision comprises one or more of: an identification of the user device of the more than one user devices, an identification of sidelink resources, or both the identification of the user device of the more than one user devices and the identification of sidelink resources that are colliding; an explicit indication of time / frequency / code resources that are colliding, and an identification of a corresponding sidelink resource pool, bandwidth part, frequency band, or carrier; an implicit indication of sidelink resources that are colliding; or a session identification or a message sequence identification of a sidelink positioning.

32. The apparatus of any one of claims 22-31, wherein, the sidelink resources are used for sidelink positioning reference signal transmissions.

33. An apparatus comprising means for performing: receiving, by a network entity, an indication of a collision in sidelink resources for transmission by more than one user device; and allocating, by the network entity, new sidelink resources to a user device connected to the network entity and being one of the more than one user devices.

34. The apparatus of claim 33, wherein receiving the indication comprises receiving the indication from the user device connected to the network entity.

35. The apparatus of claim 33, wherein receiving the indication comprises receiving the indication from a user device not served by the network entity, and the indication of the conflict indicates a conflict in sidelink resources allocated to user devices connected to the network entity.

36. The apparatus of claim 35, wherein receiving the indication comprises receiving the indication of the conflict using a small data transmission from the user device.

37. The apparatus of claim 33, wherein receiving the indication comprises receiving the indication from a location management function, and the indication of the conflict indicates a conflict in sidelink resources allocated to user devices connected to the network entity.

38. An apparatus comprising means for performing: receiving, by a location management function and from a user device, an indication of a conflict in sidelink resources transmitted by more than one user device, the indication indicating a user device using the sidelink resources and having the conflict; and sending, by the location management function, an indication of the conflict in the sidelink resources to a network entity that assigned the sidelink resources.

39. The apparatus of claim 38, wherein the means are further configured to perform: determining which network entities correspond to the indicated user device, and the sending uses the determined network entities.

40. The apparatus of any preceding apparatus claim, wherein the means comprise: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform.

41. An apparatus comprising: one or more processors; and one or more memories storing instructions that, when executed by the one or more processors, cause the apparatus to perform at least: determining, at a user device, a conflict in sidelink resources transmitted by more than one user device; and sending, by the user device, an indication of the determined conflict to a network entity.

42. An apparatus comprising: one or more processors; and one or more memories storing instructions that, when executed by the one or more processors, cause the apparatus to perform at least: receiving, by a network entity, an indication of a conflict in sidelink resources transmitted by more than one user device; and allocating, by the network entity, new sidelink resources to a user device connected to the network entity and being one of the more than one user devices.

43. An apparatus comprising: one or more processors; and one or more memories storing instructions that, when executed by the one or more processors, cause the apparatus to perform at least: receiving, by a location management function and from a user equipment, an indication of a collision in sidelink resources transmitted by more than one user equipment, the indication indicating that a user equipment used the sidelink resources and has the collision; and sending, by the location management function, an indication of the collision in the sidelink resources to a network entity that assigned the sidelink resources.

Images