Method for network-centric resource allocation for sidelink positioning

Abstract

Method for network-centric resource allocation for sidelink positioning within a wireless communication system having at least one user equipment (UE), characterized in that the at least one user equipment (UE) initiates an indirect or / and direct resource allocation for a sidelink positioning procedure, and the positioning procedure itself is triggered by a user equipment (UE) or any other node.

Description

Technical Field

[0001] The present disclosure relates to a method for network-centric resource allocation for sidelink positioning, a protocol for network-centric resource allocation for SL positioning, and messages to be exchanged, including cases where one or more UEs do not belong to the same cell. Background Art

[0002] Wireless communication systems are widely used to provide various types of communication services, such as voice and data. Generally, wireless communication systems are multiple-access systems that support communication between multiple users by sharing available system resources (such as bandwidth and transmission power). Examples of multiple-access systems include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single-carrier frequency division multiple access (SC-FDMA), and multi-carrier frequency division multiple access (MC-FDMA).

[0003] Sidelink (SL) is a communication method that establishes a direct link between user equipment (UE), allowing voice or data to be exchanged directly between terminals without going through a base station (BS). SL is considered a solution to the burden on base stations caused by the rapid growth of data traffic.

[0004] V2X (Vehicle to Everything) refers to the communication technology used to exchange information with other vehicles, pedestrians, and infrastructure via wired or wireless communications. V2X can be categorized into four types: vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), and vehicle-to-pedestrian (V2P). V2X communication can be provided via the PC5 interface and / or the Uu interface.

[0005] As more and more communication devices require greater communication capacity to transmit and receive signals, there is a need to improve mobile broadband communications beyond traditional radio access technologies. Consequently, discussions are underway to develop communication systems that take into account reliability- and latency-sensitive services and users. The next-generation radio access technology, which incorporates enhanced mobile broadband communications, massive machine-type communications (MTC), and ultra-reliable low-latency communications (URLLC), can be referred to as new radio access technology (RAT) or new radio (NR). Even within NR, vehicle-to-everything (V2X) communications can be supported.

[0006] EP 4060923 A1 discloses a method and apparatus for transmitting a preconfigured positioning reference signal (PRS) for sidelink positioning. According to one aspect, a method for performing on-demand positioning by a positioning terminal in a New Radio Vehicle-to-Everything (NR-V2X) communication system includes the following steps: transmitting a request PRS via a sidelink channel; receiving a response PRS corresponding to the request PRS from a neighboring terminal via the sidelink channel; receiving a measurement result corresponding to the request PRS from the neighboring terminal; and performing positioning based on the response PRS and the measurement result, wherein the positioning terminal transmits resource allocation information for transmitting the response PRS corresponding to the request PRS to the neighboring terminal, and the measurement result can be received using resources used for V2X data transmission.

[0007] US 2016095092 A1 discloses a user equipment (UE), which includes a processing circuit for performing the following operations: connecting to a cellular network; detecting one or more additional UEs or connecting to the one or more additional UEs to form a direct connection with the one or more additional UEs; receiving information from the cellular network allocating a portion of radio spectrum resources as radio spectrum resources dedicated to exchanging signal location parameters, which signal location parameters relate to information related to UE location determination; receiving one or more of the signal location parameters via a direct connection with the one or more additional UEs and using the allocated portion of the radio spectrum resources; and determining the location of the UE based on one or more of the received signal location parameters.

[0008] EP 4072195 A1 discloses a method and apparatus according to various embodiments, for a first terminal to transmit a positioning reference signal (PRS) via a physical sidelink feedback channel (PSFCH) in a wireless communication system supporting sidelink communication. The method and apparatus include the following steps: allocating a first frequency resource region for the PRS within a resource region of the PSFCH so that the PRS is multiplexed with a feedback signal; transmitting allocation information regarding the first frequency resource region; and transmitting the PRS and the feedback signal via the PSFCH based on the allocation information, wherein the size of the first frequency resource region is determined based on the size of a preconfigured frequency resource for the feedback signal and a multiplexing type, and the allocation information includes information regarding the multiplexing type, the size of the first frequency resource region, and a starting frequency of the first frequency resource.

[0009] US 2022278797 A1 discloses a method for a first device to perform sidelink communication. The method may include: receiving a PSCCH from a second device; receiving a PSSCH related to the PSCCH from the second device; sending a SL PRS for sidelink positioning to the second device; determining a PSFCH resource for sending a PSFCH to the second device based on the PSCCH and the PSSCH; and sending the PSFCH to the second device based on the PSFCH resource, wherein a time interval for sending the SL PRS and a time interval for sending the PSFCH may overlap with each other.

[0010] US 2020374656 A1 discloses a transceiver for a wireless communication system, the transceiver being configured to: communicate with at least one other transceiver of the system using a sidelink resource pool of the system; transmit signals on resources of the resource pool that are periodically allocated to the transceiver with a period tperiodA of equal length; transmit a first signal on a first resource of the resources allocated to the transceiver and receive a second signal from another transceiver of the system on a second resource, the second signal being transmitted by the other transceiver in response to receiving the first signal, the second signal being sent by the other transceiver on the second resource using the period tperiodA based on which the resources are allocated to the transceiver; determine a distance to the other transceiver based on a time troundA between transmitting the first signal and receiving the second signal from the other transceiver and based on the period tperiodA based on which the resources are allocated to the transceiver.

[0011] WO 2022120817 A1 is a disclosure related to coordinated positioning via sidelink resources. A first terminal device sends a first message to a plurality of positioning terminal devices including a second terminal device. The first message indicates a sidelink resource for sending a reference signal from a plurality of positioning terminal devices to the first terminal device. After receiving the first message, the second terminal device determines a first sidelink resource for sending a first reference signal for positioning the first terminal device from the sidelink resources, and then sends the first reference signal to the first terminal device via the first sidelink resource. Through this solution, a sidelink-based positioning solution can be implemented. In particular, even in the case of partial coverage or out of coverage, that is, when at least some of the devices participating in the positioning process cannot access the network device, resource allocation for sending RS can be implemented.

[0012] WO 2022193314 A1 discloses a method and apparatus for sidelink (SL) positioning. According to an embodiment of the present application, a method may include: receiving configuration information for SL positioning, wherein the configuration information for SL positioning includes at least one of the following: configuration of at least one panel mode, wherein each panel mode of the at least one panel mode includes one or more panels; at least one resource allocation principle associated with the at least one panel mode; and at least one beam allocation principle associated with the at least one panel mode; and transmitting a SL positioning reference signal (SL-PRS) based on the received configuration information for SL positioning. Various embodiments of the present application can support more efficient multi-node UE positioning with low signaling overhead.

[0013] WO 2022184240 A1 discloses a user equipment for sidelink-based positioning, wherein the user equipment is configured to: obtain sidelink SL positioning resource information, wherein the sidelink positioning resource information indicates resource characteristics of a sidelink positioning reference signal SL-PRS, positioning assistance data AD or location information LI; and perform sidelink positioning based on the sidelink positioning resource information.

[0014] The positioning methods used for SL positioning are at least the following methods using the SL measurements identified as possible:

[0015] RTT-based solutions using SL

[0016] SL-AoA

[0017] SL-TDOA

[0018] The above identification does not necessarily mean that these methods are designated as independent methods, nor does it mean that a unified SL positioning method is specified.

[0019] Regarding SL positioning measurement report, it includes the following aspects.

[0020] The contents of the measurement report may include one or more SL positioning measurements, (multiple) timestamps associated with the SL positioning measurement, (multiple) quality metrics associated with the SL positioning measurement, and identification information for the SL positioning measurement.

[0021] The temporal behavior of the measurement report (e.g., one-shot, triggered, aperiodic, semi-continuous, periodic)

[0022] Consider whether SL positioning measurements can be reported as high-level and / or low-level reports.

[0023] At least the following schemes are known for resource allocation of SL PRS:

[0024] Solution 1: Network-centric operation (e.g., similar to the solution of legacy Mode 1), the network (e.g., gNB, LMF, gNB and LMF) allocates resources for SL PRS.

[0025] Solution 2: UE autonomous (eg, similar to the solution of legacy Mode 2), at least one of the UE(s) participating in the SL positioning operation allocates resources for the SL PRS.

[0026] Applicable to any network coverage area.

[0027] If necessary, potential mechanisms for SL PRS resource coordination among multiple transmitting UEs may be further considered, for example, solutions similar to Inter-UE Coordination (IUC).

[0028] Solution 1 SL PRS resource allocation is performed in the following manner: The sending UE receives SL PRS resource allocation signaling from the network. For the corresponding signaling, further consider one or both of the following options:

[0029] Option 1: Through LMF senior management

[0030] Option 2: Dynamic authorization by gNB or configuration via configuration authorization type 1 or type 2

[0031] Regarding SL positioning resource allocation, the SL PRS may be (pre-)configured with dedicated resource pool(s) and / or resource pool(s) shared with SL communication.

[0032] The following options are provided for time domain resource assignment and associated Tx UE behavior for SL PRS transmission:

[0033] Periodic SL PRS, where the SL PRS is sent periodically with a transmission period; any additional details (including whether higher layers can start / stop sending) can be further considered during the normative work.

[0034] Semi-persistent SL PRS, in which the SL PRS is sent periodically with a transmission cycle after activation until it is deactivated.

[0035] Aperiodic SL PRS is performed by sending an SL PRS at least once after a trigger or request (FFS). The applicability of the above options to SL PRS resource allocation schemes 1 and 2, respectively, can be further considered. The details of the Rx UE behavior can be discussed separately during normative work. Further consideration can be given to the mechanism(s) to be used for activation / deactivation / triggering. Resource allocation for SL positioning measurement reports is also known.

[0036] Some existing technologies have considered resource allocation issues for SL positioning; however, none of them considers the situation where UEs may belong to different cells. Summary of the Invention

[0037] This application provides a solution on how to implement network-centric resource allocation for SL positioning, and how to coordinate network-centric resource allocation when the participating UEs belong to different cells.

[0038] This problem is solved by the features of claims 1 to 25 .

[0039] A network-centric resource allocation method for sidelink positioning in a wireless communication system having at least one user equipment (UE), the method being characterized in that at least one or more user equipments (UEs) initiate indirect and / or direct resource allocation for a positioning procedure, and the positioning procedure itself being triggered by the UE or any other node.

[0040] In some embodiments of the method according to the first aspect, the method is characterized in that the UEs participating in the SL positioning belong to different serving cells in the wireless communication system.

[0041] In some embodiments of the method according to the first aspect, the method is characterized in that the user equipment UE performs indirect resource allocation, where one UE initiates positioning through its own serving cell or LMF and handles resource allocation for all UEs participating in SL positioning.

[0042] In some embodiments of the method according to the first aspect, the method is characterized in that SL positioning resource allocation is always routed through a UE within the coverage area, the requesting UE forwards the resource allocation to other UEs through the SL, and the requesting UE needs to forward the resource allocation to other UEs through the SL, and UEs outside the coverage area can participate in positioning.

[0043] In some embodiments of the method according to the first aspect, the method is characterized in that whenever a UE within the coverage area receives a trigger of any subset or all of the following items from its own upper layer or any other node in the network, the UE is triggered to perform resource allocation, wherein the trigger is the sending and / or reception of SL PRS, or the sending and / or reception of at least one SL positioning measurement report or signal, and / or data transmission related to the SL positioning operation.

[0044] In some embodiments of the method according to the first aspect, the method is characterized in that before or after triggering the positioning procedure and before making a resource allocation request, the UE in the coverage area requests and receives (multiple) UE IDs of all other (multiple) UEs participating in the positioning operation and (multiple) cell IDs of all other (multiple) UEs participating in the positioning operation from all other UEs participating in the positioning operation.

[0045] In some embodiments of the method according to the first aspect, the method is characterized in that the UE ID(s) of all other UE(s) participating in the positioning operation and the cell ID(s) of all other participating UE(s) are obtained by:

[0046] • Any data channels or control channels within the dedicated RP that the UE uses for positioning with other UE(s), and / or

[0047] • Any data channels or control channels within a shared RP that the UE uses with other UE(s) for communication and positioning, and / or

[0048] • Trigger any data channel or control channel within the SL communication RP(s) that the UE and other UE(s) are using.

[0049] In some embodiments of the method according to the first aspect, the method is characterized in that the data channel is a Physical Sidelink Shared Channel (PSSCH) and the control channel is a Physical Sidelink Control Channel (PSCCH).

[0050] In some embodiments of the method according to the first aspect, the method is characterized in that the triggering UE within the coverage area has obtained resource allocation through the gNB, the triggering UE within the coverage area identifies (multiple) UEs that do not belong to the same cell based on their (multiple) cell IDs, and then sends an SR to the serving cell (gNB) to authorize UL resources to send further information.

[0051] In some embodiments of the method according to the first aspect, the method is characterized in that the SR, the UE requests any one of the following: data and / or control channel resources on a dedicated RP for positioning, or data and / or control channel resources on a shared RP for positioning and communication, or data channel resources on an SL communication RP.

[0052] In some embodiments of the method according to the first aspect, the method is characterized in that the SR further indicates an amount of UL resources required for the UE to send further information, and as a response to the SR of the UE, the gNB allocates UL resources to the UE in order to send further information about the SR, and the UE sends at least the information to the gNB via the UL resources allocated to it, wherein the information includes the type of resources to be scheduled for each UE participating in the positioning procedure, the index of the RP requiring the resources, and the time characteristics / periodicity of the required resources and / or the type of positioning method.

[0053] In some embodiments of the method according to the first aspect, the method is characterized in that the UE requiring resources for SL positioning sends a request to the LMF, wherein the request may be sent using an existing LPP and the request includes:

[0054] • UE ID(s) and cell ID(s) of all participating UE(s);

[0055] •The number of UEs participating in the positioning process;

[0056] • Index of the RP that requires resources (if the UE uses multiple RPs);

[0057] • Type of resources required (e.g., SL-PRS resources, measurement reporting resources, etc.);

[0058] • Temporal characteristics / periodicity of the required resources (e.g., aperiodic / semi-persistent / periodic SL-PRS, multiple measurement reports in a predefined sequence, etc.).

[0059] In some embodiments of the method according to the first aspect, the method is characterized in that:

[0060] •The target UE sends an SR to the gNB; the gNB provides UL resources for the target UE to send a SL positioning resource allocation request; the target UE sends a resource allocation request to the anchor UE for SL PRS transmission; this includes the UEIDs of all (multiple) anchor UEs and the target UE and an indication of which (these) anchor UEs do not belong to the same cell as the target UE; the gNB sends a resource allocation grant for the target UE and the anchor UE.

[0061] • The target UE forwards the authorization to the anchor UE(s);

[0062] • All anchor UE(s) perform SL PRS transmission on the allocated resources, and the target UE performs SL RSTD measurements towards higher layers to calculate its own position.

[0063] In some embodiments of the method according to the first aspect, the method is characterized in that a UE within the coverage of which a higher layer triggers the positioning process sends an indication of initiating resource allocation to other participating UE(s); the indication involves at least the following information:

[0064] •The type of resources required;

[0065] •The temporal nature / periodicity of the resources required;

[0066] •Preferred time-frequency location of resources;

[0067] •The index of the RP that requires the resource.

[0068] In some embodiments of the method according to the first aspect, the method is characterized in that the following information can be sent via the following manner:

[0069] • trigger any control channel or data channel within the dedicated RP(s) that the UE uses for positioning together with other UE(s);

[0070] • any control channel or data channel within the shared RP(s) that the triggering UE uses for communication and positioning with other UE(s);

[0071] • Any data channel within the SL communication RP(s) that the triggering UE uses for communication with other UEs.

[0072] In some embodiments of the method according to the first aspect, the method is characterized in that, in response to the SR of each UE, the corresponding serving cell (gNB) allocates UL resources to each UE in order to send further information about the SR, and then the UE sends at least the following information to the gNB via the UL resources allocated to it:

[0073] •The type of resources required;

[0074] •The temporal nature / periodicity of the resources required;

[0075] •Preferred time-frequency location of resources;

[0076] •The index of the RP that requires the resource.

[0077] In some embodiments of the method according to the second aspect, the method is characterized in that a UE within the coverage area of ​​which the positioning process is triggered by its higher layer or the resource allocation is triggered sends an indication of initiating resource allocation to other (multiple) UEs participating in the SL positioning process, and then each participating UE that needs resources for SL positioning sends a request to the LMF, which request can be sent using the existing LPP.

[0078] In some embodiments of the method according to the second aspect, the method is characterized in that:

[0079] • The target UE sends a resource allocation initiation to other UEs participating in the positioning process;

[0080] • Each UE sends a SR to its respective gNB; the gNB provides UL resources to each UE to send a SL positioning resource allocation request; each UE sends a resource allocation request for SL PRS transmission; the gNB sends a resource allocation grant to each UE;

[0081] • All anchor UE(s) perform SL PRS transmission on the allocated resources, and the target UE performs SL RSTD measurements towards higher layers to calculate its own position.

[0082] In some embodiments of the method according to the third aspect, the method is characterized in that after the UE raises an SR for UL resources and the gNB grants UL resources for sending further information, the UE sends information on the granted UL resources regarding whether there are out-of-coverage UEs participating in positioning,

[0083] If there are out-of-coverage UEs participating, the gNB uses indirect resource allocation and sends these resources to the UE that sent the SR, which forwards them to all other UEs.

[0084] If there is no out-of-coverage UE participating, the gNB can decide whether to use direct resource allocation or indirect resource allocation based on latency requirements, available resources, etc.

[0085] If direct resource allocation is to be used, the gNB sends an indication to the UE that sent the SR to send an indication of autonomous resource allocation request to all participating UEs.

[0086] If indirect resource allocation is to be used, the gNB sends an indication to the UE that sent the SR to forward the resource allocation to the corresponding UE,

[0087] If resources are allocated by the LMF instead of the gNB, the LMF decides between direct resource allocation and indirect resource allocation and sends appropriate indications to the requesting UE.

[0088] According to a second aspect, the present disclosure relates to an apparatus for network-centric resource allocation for sidelink positioning, the apparatus comprising a wireless transceiver, a processor coupled to a memory having computer program instructions stored therein, the instructions being configured to implement the steps of the method according to the first, second and third aspects.

[0089] According to a third aspect, the present disclosure relates to an in-coverage user equipment comprising the apparatus according to the second aspect.

[0090] According to a fourth aspect, the present disclosure relates to a further user equipment comprising the apparatus according to the second aspect.

[0091] According to a fifth aspect, the present disclosure relates to a serving gNB comprising an apparatus according to the second aspect.

[0092] According to a sixth aspect, the present disclosure relates to a neighboring gNB comprising an apparatus according to the second aspect.

[0093] According to a sixth aspect, the present disclosure relates to a wireless communication system for network-centric resource allocation for sidelink positioning, wherein the wireless communication system includes a user equipment within the coverage range according to the third aspect, other user equipment according to the fourth aspect, a serving gNB according to the fifth aspect, and a neighboring gNB according to the sixth aspect, wherein the other user equipment, the serving gNB, and the neighboring gNB each include a processor coupled to a memory having computer program instructions stored therein, the instructions being configured to implement the steps of the methods according to the first, second, and third aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0094] Figure 1 The periodicity and frequency of resource allocation for SL communication are shown.

[0095] Figure 2 A dynamic SL grant DCI is shown.

[0096] Figure 3 The configuration SL authorization DCI is shown.

[0097] Figure 4 The UL scheduling process is shown.

[0098] Figure 5 The protocol layering of LMF to UE signaling is shown.

[0099] Figure 6 It shows LPP PDU transmission between LMF and UE (network triggered and UE triggered cases).

[0100] Figure 7 Shown

[0101] Figure 8 The protocol layering of LMF to NG-RAN signaling is shown.

[0102] Figure 9 The NRPPa PDU transmission for UE positioning between LMF and NG-RAN node is shown.

[0103] Figure 10 The NRPPa PDU transmission between LMF and NG-RAN for obtaining NG-RAN data is shown.

[0104] Figure 11 Two possible scenarios are shown: all UEs belong to the same cell or at least one anchor UE belongs to a different cell.

[0105] Figure 12 The indirect resource allocation (gNB) flow chart is shown.

[0106] Figure 13 The indirect resource allocation (gNB) flow chart for UEs within coverage is shown.

[0107] Figure 14 An embodiment of indirect resource allocation (gNB) is shown.

[0108] Figure 15 A flow chart of Direct Resource Allocation ((multiple) gNBs) is shown.

[0109] Figure 16 The flow chart of direct resource allocation (gNB) to UEs within coverage is shown.

[0110] Figure 17 The flow chart of direct resource allocation to other UEs (gNB) is shown.

[0111] Figure 18 An embodiment of direct resource allocation (gNB(s)) is shown. DETAILED DESCRIPTION

[0112] The detailed description set forth below with reference to the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein may be practiced. The detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In particular, although terminology from 3GPP 5G NR may be used in this disclosure to illustrate the embodiments herein, this should not be considered as limiting the scope of the invention.

[0113] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are also within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0114] Generally, all terms used herein should be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or a different meaning is implied from the context of its use. Unless otherwise expressly stated, all references to one / a kind / this element, device, part, mode, step, etc. should be openly interpreted as referring to at least one instance of an element, device, part, mode, step, etc. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as being after or before another step and / or it is implied that a step must be after or before another step. Where appropriate, any feature of any embodiment disclosed herein may be applicable to any other embodiment. Similarly, any advantage of any embodiment may be applicable to any other embodiment, and vice versa. Based on the following description, other purposes, features and advantages of the attached embodiments will become apparent.

[0115] In some embodiments, the more general term "network node" may be used, which may correspond to any type of radio network node or any network node that communicates with a UE (directly or via another node) and / or communicates with another network node. Examples of network nodes are NodeB, MeNB, ENB, a network node belonging to an MCG or SCG, a base station (BS), a multi-standard radio (MSR) radio node (such as an MSR BS, eNodeB, gNodeB), a network controller, a radio network controller (RNC), a base station controller (BSC), a relay, a donor node controlled relay, a base transceiver station (BTS), an access point (AP), a transmission point, a transmission node, an RRU, an RRH, a node in a distributed antenna system (DAS), a core network node (such as a mobile switching center (MSC), a mobility management entity (MME), etc.), operations and maintenance (O&M), an operations support system (OSS), a self-optimizing network (SON), a positioning node (such as an evolved serving mobile positioning center (E-SMLC)), minimization of drive tests (MDT), test equipment (physical node or software), etc.

[0116] In some embodiments, the non-limiting term user equipment (UE) or wireless device may be used, which may refer to any type of wireless device that communicates with a network node and / or another UE in a cellular or mobile communication system. Examples of UEs are target devices, device-to-device (D2D) UEs, machine-type UEs or UEs capable of machine-to-machine (M2M) communication, PDAs, PADs, tablet computers, mobile terminals, smartphones, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, M1 category UEs, M2 category UEs, ProSe UEs, V2V UEs, V2X UEs, and the like.

[0117] Furthermore, terms such as base station / gNodeB and UE should be considered non-restrictive and, in particular, do not imply a hierarchical relationship between the two. In general, a "gNodeB" can be considered device 1 and a "UE" can be considered device 2, with the two devices communicating with each other over a radio channel. In the following, a transmitter or receiver can be either a gNodeB (gNB) or a UE.

[0118] As will be appreciated by those skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Thus, the embodiments may take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects.

[0119] For example, the disclosed embodiments may be implemented as hardware circuits comprising custom very large scale integrated ("VLSI") circuits or gate arrays, off-the-shelf semiconductors (e.g., logic chips, transistors, or other discrete components). The disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, and the like. As another example, the disclosed embodiments may comprise one or more physical or logical blocks of executable code, which blocks may be organized, for example, as objects, procedures, or functions.

[0120] Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code (hereinafter referred to as code). The storage device may be tangible, non-transitory, and / or non-transmissive. The storage device may not embody signals. In certain embodiments, the storage device utilizes only signals to access the code.

[0121] Any combination of one or more computer-readable media may be utilized. The computer-readable medium may be a computer-readable storage medium. The computer-readable storage medium may be a storage device that stores code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0122] More specific examples of storage devices (a non-exhaustive list) would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, random access memory ("RAM"), read-only memory ("ROM"), erasable programmable read-only memory ("EPROM" or flash memory), a portable compact disk read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0123] The code for performing the operations of the embodiment can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and conventional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code can be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network ("LAN"), a wireless LAN ("WLAN"), or a wide area network ("WAN"), or can be connected to an external computer (e.g., via the Internet using an Internet Service Provider ("ISP")).

[0124] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details (e.g., examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc.) are provided to provide a thorough understanding of the embodiments. However, those skilled in the relevant art will recognize that the embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the embodiments. Reference throughout this specification to "one embodiment," "an embodiment," or similar language means that at least one embodiment includes the specific features, structures, or characteristics described in connection with that embodiment. Therefore, unless expressly stated otherwise, the phrases "one embodiment," "an embodiment," and similar language throughout this specification may, but do not necessarily, refer to the same embodiment, but rather to "one or more, but not all, embodiments." Unless expressly stated otherwise, the terms "including," "comprising," "having," and variations thereof mean "including, but not limited to." The enumerated listing of items does not imply that any or all of the items are mutually exclusive unless expressly specified otherwise.The terms "a" and "an" and "the" also mean "one or more" unless expressly specified otherwise.

[0125] Various aspects of the embodiments are described below with reference to schematic flow charts and / or schematic block diagrams of methods, apparatuses, systems, and program products according to the embodiments. It should be understood that each block of the schematic flow charts and / or schematic block diagrams, as well as combinations of blocks in the schematic flow charts and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to generate a machine, such that instructions executed by the processor of the computer or other programmable data processing device create means for implementing the functions / actions specified in the flow charts and / or block diagrams.

[0126] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other device to operate in a specific manner so that the instructions stored in the storage device produce an article of manufacture including instructions for implementing the functions / actions specified in the flowcharts and / or block diagrams.

[0127] The code may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, such that the code executed on the computer or other programmable apparatus provides a process for implementing the functions / actions specified in the flowcharts and / or block diagrams.

[0128] The flowcharts and / or blocks in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of devices, systems, methods, and program products according to various embodiments. In this regard, each block in the flowcharts and / or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing the specified logical function(s).

[0129] It should also be noted that in some alternative implementations, the functions indicated in the blocks may not occur in the order indicated in the figures. For example, two blocks shown in succession may actually be executed substantially in parallel, or the blocks may sometimes be executed in the reverse order depending on the functions involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks or portions thereof in the illustrated figures.

[0130] Although various arrow types and line types may be employed in the flowcharts and / or block diagrams, it should be understood that they do not limit the scope of the corresponding embodiments. In fact, some arrows or other connectors may be used only to indicate the logical flow of the depicted embodiments. For example, arrows may indicate waiting or monitoring cycles of unspecified duration between the enumerated steps of the depicted embodiments. It should also be noted that each block in the block diagrams and / or flowcharts and the combination of blocks in the block diagrams and / or flowcharts may be implemented by a dedicated hardware-based system or a combination of dedicated hardware and code that performs a specified function or action.

[0131] The description of an element in each figure may refer to an element in a subsequent figure. In all figures, the same reference numerals refer to the same elements, including alternative embodiments of the same elements.

[0132] The detailed description set forth below with reference to the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. For example, although 3GPP terminology from, for example, 5G NR may be used in this disclosure to illustrate embodiments herein, this should not be considered to limit the scope of this disclosure.

[0133] This disclosure relates to a wireless communication system, which may be, for example, a 5G NR wireless communication system. More specifically, the wireless communication system refers to a radio access network (RAN) of the wireless communication system, which is used to exchange data with a user equipment (UE) via radio signals. For example, the RAN may send data (downlink, DL) to the UE, such as data received from a core network (CN). The RAN may also receive data (uplink, UL) from the UE, which may be forwarded to the CN.

[0134] In the illustrated example, the RAN includes one base station (BS). Of course, the RAN may include more than one BS to increase the coverage of the wireless communication system. Depending on the implemented wireless communication standard(s), each of these BSs may be referred to as a NB, eNodeB (or eNB), gNodeB (or gNB, in the case of a 5G NR wireless communication system), access point, etc.

[0135] The UE is located within the coverage of the BS. The coverage of the BS corresponds to an area where the UE can decode the PDCCH transmitted by the BS.

[0136] An example of a wireless device suitable for implementing any of the methods discussed in this disclosure, performed at a UE, corresponds to an apparatus that provides a wireless connection to a wireless communication system's radio access network (RAN) and can be used to exchange data with the RAN. Such a wireless device may be included in a UE. A UE may be, for example, a cellular phone, a wireless modem, a wireless communication device, a handheld device, a laptop computer, etc. A UE may also be an Internet of Things (IoT) device, such as a wireless camera, a smart sensor, a smart meter, smart glasses, a vehicle (manned or unmanned), a Global Positioning System device, etc., or any other device that can run an application that requires exchanging data with a remote recipient via a wireless device.

[0137] The wireless device includes one or more processors and one or more memories. The one or more processors may include, for example, a central processing unit (CPU), a digital signal processor (DSP), a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc. The one or more memories may include any type of computer-readable volatile and non-volatile memory (magnetic hard disk, solid-state drive, optical disk, electronic memory, etc.). The one or more memories may store a computer program product in the form of a program code instruction set, which is executed by the one or more processors to implement all or part of the steps of the method for exchanging data performed on the UE side according to any of the embodiments disclosed herein.

[0138] The wireless device may also include a main radio (MR) unit. The MR unit corresponds to the wireless device's main wireless communication unit and is used to exchange data with the base station of the RAN using radio signals. The MR unit can implement one or more wireless communication protocols and can be, for example, a 3G, 4G, 5G, NR, WiFi, WiMax, or similar transceiver. In a preferred embodiment, the MR unit corresponds to a 5G NR wireless communication unit.

[0139] Figure 1 The period and frequency of resource allocation for SL communication are shown. Mode 1 resource allocation for SL communication is defined in TS 38.214 and TS 38.211. The gNB assigns and manages SL radio resources using the NR Uu interface. UEs must be within network coverage. SL radio resources can be allocated from a licensed carrier dedicated to SL communication or from a licensed carrier that shares resources between SL and UL communication. SL radio resources can be configured so that Mode 1 and Mode 2 use separate or shared resource pools. Mode 1 UEs notify Mode 2 UEs of the allocated resources for their future transmissions.

[0140] The grant types can be: Dynamic Grant (DG); Configured Grant (CG): periodic sidelink resources semi-statically configured by RRC.

[0141] Figure 2 A dynamic SL grant DCI is shown. Figure 3 The configuration SL authorization DCI is shown. Figure 2 and Figure 3 Mode 1 resource allocation for SL communication is shown (references: TS 38.214, TS 38.211). Dynamic SL grants (DCI) can provide resources for one or more transmissions of a TB. SL configuration grants: Type 1: configured once and immediately usable by the UE until released via RRC signaling; Type 2: configured once but unusable after the gNB sends a DCI indicating activation to the UE, and until another DCI indicates deactivation. Both resource types recur periodically, which the gNB expects to match the characteristics of V2X traffic. gNB scheduling activity is driven by the UE reporting its sidelink traffic characteristics to the gNB, or by requesting sidelink resource allocations from the gNB via a sidelink BSR procedure similar to the BSR procedure over Uu.

[0142] Figure 4 The UL scheduling process is shown in FIG. SL SR follows a similar process to UL SR, which is as follows:

[0143] Step 1: The UE sends an SR to request PUSCH resources for new transmission.

[0144] Step 2: The gNB receives the SR and knows that the UE has UL data to transmit, but the gNB does not know the amount of UL data in the UE's buffer. Therefore, the gNB usually first allocates PUSCH resources for the BSR to the UE.

[0145] Step 3: The UE sends a BSR on the PUSCH resources allocated to the UE and provides the UL data volume to the gNB.

[0146] Step 4: The gNB allocates PUSCH resources for UL data to the UE.

[0147] Step 5: The UE sends UL data on the PUSCH resources allocated to the UE.

[0148] The location management function manages the various location services supported for the target UE, including positioning the UE and delivering assistance data to the UE. The location management function can interact with the target UE's serving gNB to obtain the UE's location measurement. Furthermore, it can interact with the target UE to deliver assistance data when specific location services are requested, or to obtain a location estimate when a location estimate is requested, and can interact with multiple NG-RAN nodes to provide assistance data information for broadcast. The assistance data information for broadcast can optionally be segmented and / or encrypted by the LMF. The LMF can also interact with the AMF to provide encryption key data information to the AMF.

[0149] For positioning the target UE, the LMF decides which positioning method to use based on factors that may include the LCS client type, required QoS, UE positioning capabilities, gNB positioning capabilities, and so on. The LMF then invokes these positioning methods in the UE and serving gNB. These positioning methods may produce: a position estimate from UE-based positioning methods, and / or positioning measurement results from UE-assisted and network-based positioning methods. The LMF may combine all received results and determine a single position estimate for the target UE (hybrid positioning). Additional information such as the accuracy and speed of the position estimate may also be determined. The LMF may interact with the AMF to provide (updated) UE positioning capabilities to the AMF and receive stored UE positioning capabilities from the AM.

[0150] Figure 5 The figure shows the protocol layering of LMF to UE signaling. The LPP PDU is carried in the NAS PDU between the AMF and the UE.

[0151] Figure 6 and Figure 7 It shows the LPP PDU transmission between LMF and UE (network triggered and UE triggered cases).

[0152] Figure 8The protocol layering of LMF to NG-RAN signaling is shown.

[0153] Figure 9 The NRPPa PDU transmission for UE positioning between LMF and NG-RAN node is shown.

[0154] Figure 10 The NRPPa PDU transmission between LMF and NG-RAN for obtaining NG-RAN data is shown.

[0155] Figure 11 The present application provides two independent resource allocation methods for positioning similar to Mode 1:

[0156] 1. Indirect resource allocation: One of the UEs (e.g., the UE whose higher layer initiates positioning) handles resource allocation for all UEs participating in SL positioning through its own serving cell or LMF. SL positioning resource allocation is always routed through a UE within coverage. The requesting UE needs to forward the resource allocation to other UEs via SL. UEs outside of coverage can participate in positioning.

[0157] 2. Direct Resource Allocation: All UEs participating in positioning first coordinate their resource needs with each other and then individually request resources from their respective serving cells or LMFs. SL positioning resource allocation is requested individually by each UE. The triggering UE must send an indication to other UEs initiating resource allocation. UEs outside the coverage area cannot participate in positioning.

[0158] 3. Direct / indirect resource allocation based on indications provided by the originating UE

[0159] SL positioning resource allocation is requested by a UE within coverage, but is determined by its serving cell based on additional information provided by the UE. Depending on whether direct or indirect resource allocation is used, the triggering UE needs to forward the resource allocation to other UEs or send an indication to initiate resource allocation. UEs outside coverage can participate in positioning.

[0160] All methods can handle the situation where the UEs participating in SL positioning belong to different serving cells.

[0161] This concept applies to the case where one or more UEs within coverage initiate a resource allocation request as part of a positioning procedure; the positioning procedure itself can be triggered by the UE or any other node (e.g., gNB, LMF, etc.).

[0162] Resource allocation is triggered whenever a UE in coverage receives a trigger from its own higher layers or any other node in the network for any subset or all of the following:

[0163] Any transmission / reception of SL PRS, or any transmission / reception of SL Positioning Measurement Report(s), or any other signal / data transmission related to SL positioning operations.

[0164] Before or after triggering the positioning procedure and before making a resource allocation request, a UE in coverage requests and receives the following information from all other UEs participating in the positioning operation:

[0165] UE ID(s) of all other UE(s) participating in the positioning operation

[0166] The cell ID(s) of all other UE(s) participating in the positioning operation.

[0167] The above information can be obtained through the following methods:

[0168] Any data channel or control channel within a dedicated RP that the UE uses for positioning with other UE(s),

[0169] any data channel (e.g., PSSCH) or control channel (e.g., PSCCH) within a shared RP that the UE uses for communication and positioning with other UE(s),

[0170] Any data channel (eg, PSSCH) or control channel (eg, PSCCH) within the SL communication RP(s) that is used by both the triggering UE and other UE(s).

[0171] a. Resource allocation by gNB:

[0172] Once the triggering UE in coverage obtains the above information, it identifies the UE(s) that do not belong to the same cell based on their cell(s) IDs, and then sends an SR to its serving cell (gNB) to authorize UL resources to send further information.

[0173] In an SR, the UE requests any of the following:

[0174] Data and / or control channel resources on a dedicated RP for positioning, or data and / or control channel resources on a shared RP for positioning and communication, or data channel resources on an RP for SL communication.

[0175] The SR also indicates the amount of UL resources required by the UE to send further information. In response to the UE's SR, the gNB allocates UL resources to the UE to send further information related to the SR.

[0176] The UE sends at least the following information to the gNB via the UL resources allocated to it:

[0177] The type(s) of resource(s) to be scheduled for each UE participating in the positioning procedure (e.g., configured grant(s) or dynamic grants).

[0178] One of the following options:

[0179] Option 1: The number of UEs participating in the positioning process;

[0180] Option 2: The number of UEs participating in the positioning procedure in the same cell, and the UE ID(s) and cell ID(s) of those UE(s) that do not belong to the same cell;

[0181] The index of the RP that requires resources (if the UE uses multiple RPs);

[0182] Temporal characteristics / periodicity of the required resources (e.g., aperiodic / semi-persistent / periodic SL-PRS, several measurement reports in a predefined sequence, etc.).

[0183] Optionally, the information sent by the UE may further include:

[0184] The type of positioning method (e.g., RTT, SL-TDOA, SL-AoA, etc.).

[0185] After receiving the above information, the gNB allocates resources to all participating UEs as indicated by the UE sending the SR.

[0186] If one or more of the participating UEs (except the UE within the coverage of the sending SR) belongs to a different cell:

[0187] i. Option 1: The gNB sends at least the following to the UE sending the SR:

[0188] An indication to forward resource allocations to UE(s) in different cell(s).

[0189] The resource allocation of the UE within the coverage of the sending SR is sent to the UE within the coverage via RRC (for configurable grant) or DCI (for dynamic grant) or a combination of the two.

[0190] Optionally, the resource allocation sent by the gNB may also include:

[0191] Dynamic / configurable grant of SL resources for forwarding resource allocations to other UEs;

[0192] These dynamic / configurable grants are indications used to send resource allocation indications to other UE(s).

[0193] These SL resource allocations may be within a dedicated RP or within a shared RP used by the UE sending the SR for SL positioning.

[0194] If the gNB does not indicate a separate SL resource for forwarding resource allocation to other UEs, the UE forwards the resource allocation on any other available SL resource.

[0195] ii. Option 2: The gNB sends resource allocations to the other UE(s) via their respective serving gNBs using the X2 interface based on the cell ID(s) indicated by the UE sending the SR.

[0196] If all participating UEs belong to the same cell, the gNB sends the resource allocation of all UEs and an indication to forward the resource allocation to other UEs to the UE sending the SR, as described in option 1 in section i above.

[0197] Positioning resource allocation can be a configured grant or a dynamic grant like in SL communication; after receiving the resources, the participating UE(s) will perform the SL positioning process / calculation.

[0198] b. Resource allocation by LMF:

[0199] A UE that requires resources for SL positioning sends a request to the LMF; this can be sent using the existing LPP.

[0200] The request should contain at least the following information:

[0201] UE ID(s) and cell ID(s) of all participating UE(s);

[0202] The number of UEs participating in the positioning process;

[0203] The index of the RP that requires resources (if the UE uses multiple RPs);

[0204] The type of resources required (e.g., SL-PRS resources, measurement reporting resources, etc.);

[0205] Temporal characteristics / periodicity of the required resources (e.g., aperiodic / semi-persistent / periodic SL-PRS, multiple measurement reports in a predefined sequence, etc.).

[0206] Optionally, the request may also include:

[0207] The type of positioning method (e.g., RTT, SL-TDOA, SL-AoA, etc.).

[0208] The LMF allocates the requested resource allocation to the requesting UE by routing the resource allocation via the serving cell of the UE that sent the resource allocation request using NRPPa and LPP.

[0209] As described above, the resource allocation includes resources for all participating UEs and may also include SL resources used by the UE to forward the resource allocation to other UEs.

[0210] The resource allocation from the LMF may be received directly by the UE as an LPP message, or alternatively, the serving gNB may decode the message from the LMF and then provide the configuration grant / dynamic grant to the UE, as shown in Figure 12 and Figure 13 As shown, this may be a new behavior.

[0211] Figure 12 The indirect resource allocation (gNB) flow chart is shown.

[0212] Figure 13 The indirect resource allocation (gNB) flow chart for UEs within coverage is shown.

[0213] Figure 14 An embodiment of indirect resource allocation (gNB) is shown. This embodiment 1 describes indirect resource allocation (gNB): Considering that the operation of SL-TDOA is similar to DL-TDOA, multiple anchor nodes transmit SL PRSs to the target UE, and the target UE performs SL RSTD measurements. It is assumed that at least one anchor UE belongs to a different cell than the target UE. It is assumed that resource allocation is performed by the target UE's serving gNB. It is assumed that the target UE receives a trigger for SL-TDOA positioning from higher layers.

[0214] The steps according to the proposed method are as follows:

[0215] 1. The target UE sends an SR to the gNB. The gNB provides UL resources for the target UE to send a SL positioning resource allocation request. The target UE sends a resource allocation request to the anchor UE for SL PRS transmission. This includes the UE IDs of all (multiple) anchor UEs and the target UE, as well as an indication of which anchor UE(s) do not belong to the same cell as the target UE. The gNB sends a resource allocation grant to the target UE and the anchor UE.

[0216] 2. The target UE forwards the authorization to the anchor UE(s);

[0217] 3. All anchor UE(s) perform SL PRS transmission on the allocated resources, and the target UE performs SL RSTD measurements for higher layers to calculate its own position.

[0218] Figure 15 A flow chart of Direct Resource Allocation (gNB(s)) is shown. The flow chart illustrates the following:

[0219] a. Resource allocation by (multiple) gNBs:

[0220] The UE within the coverage of which the positioning process is triggered by its higher layer sends an indication of initiating resource allocation to the other participating UE(s); the indication involves at least the following information:

[0221] The type of resources required (e.g., SL-PRS resources, measurement reporting resources, etc.);

[0222] The temporal characteristics / periodicity of the required resources (e.g., aperiodic / semi-persistent / periodic SL-PRS, or several measurement reports in a predefined sequence, etc.);

[0223] The preferred time-frequency location of resources (to avoid resource allocation conflicts between (multiple) different gNBs);

[0224] The index of the RP that requires resources (if the UE uses multiple RPs);

[0225] Optionally, the instruction may also include:

[0226] The type of positioning method (e.g., RTT, SL-TDOA, SL-AoA, etc.).

[0227] The number of UEs participating in the positioning process;

[0228] The above information can be sent via the following methods:

[0229] triggering any control channel or data channel within the dedicated RP(s) that the UE uses for positioning together with other UE(s);

[0230] triggering any control channel or data channel within the shared RP(s) that the UE uses for communication and positioning with other UE(s) (e.g., PSCCH or PSSCH, or any new control channel or data channel);

[0231] The triggering UE uses any data channel (eg, PSSCH) within the SL communication RP(s) for communication with other UE(s).

[0232] When any UE other than the triggering UE receives an indication of resource allocation for the positioning procedure from the triggering UE, the UE sends an SR to its own serving cell (gNB).

[0233] In SR, each UE requests either:

[0234] Data and / or control channel resources on a dedicated RP for positioning, or

[0235] Data and / or control channel resources on a shared RP for positioning and communication, or

[0236] SL communicates data channel resources on RP.

[0237] In response to each UE's SR, the corresponding serving cell (gNB) allocates UL resources to each UE in order to send further information about the SR.

[0238] The UE then sends at least the following information to the gNB via the UL resources allocated to it:

[0239] The type of resources required (e.g., SL-PRS resources, measurement reporting resources, etc.);

[0240] The temporal characteristics / periodicity of the required resources (e.g., aperiodic / semi-persistent / periodic SL-PRS, or several measurement reports in a predefined sequence, etc.);

[0241] The preferred time-frequency location of resources (to avoid resource allocation conflicts between (multiple) different gNBs);

[0242] The index of the RP that requires resources (if the UE uses multiple RPs);

[0243] Optionally, the instruction may also include:

[0244] The type of positioning method (e.g., RTT, SL-TDOA, SL-AoA, etc.).

[0245] The number of UEs participating in the positioning process;

[0246] After receiving the above information, each gNB allocates the requested resources to the corresponding UE that sent the SR.

[0247] These resources include dynamically / configurably authorized SL resources for performing positioning-related signaling or data exchange.

[0248] These SL resource allocations may be within a dedicated RP or within a shared RP used for SL positioning by the UE sending the SR, depending on the information provided by the UE.

[0249] b. Resource allocation by LMF:

[0250] like Figure 14 As shown, a UE within the coverage area whose higher layer triggers the positioning process or triggers resource allocation sends an indication of initiating resource allocation to other (multiple) UEs participating in the SL positioning process.

[0251] Each participating UE that needs resources for SL positioning then sends a request to the LMF; this can be sent using the existing LPP.

[0252] The request should contain at least the following information:

[0253] The index of the RP for which resources are required (if the UE uses multiple RPs). The type of resources required (e.g., SL-PRS resources, resources for measurement reports, etc.). The temporal characteristics / periodicity of the resources required (e.g., aperiodic / semi-persistent / periodic SL-PRS, several measurement reports in a predefined sequence, etc.).

[0254] Optionally, the request may also include:

[0255] The type of positioning method (e.g., RTT, SL-TDOA, SL-AoA, etc.).

[0256] The number of UEs participating in the positioning process;

[0257] The LMF allocates the requested resources to each UE participating in positioning that sends a resource allocation request by routing the resource allocation via the respective serving cell (gNB) using NRPPa and LPP.

[0258] The resource allocation from the LMF can be received directly by the UE as an LPP message, or alternatively, the corresponding serving gNB can decode the message from the LMF and then provide the configuration grant / dynamic grant to the UE as appropriate, as shown in slides 25 and 26.

[0259] Figure 16 The flow chart of direct resource allocation (gNB) to UEs within coverage is shown.

[0260] Figure 17 The flow chart of direct resource allocation to other UEs (gNB) is shown.

[0261] Figure 18 An embodiment of direct resource allocation (gNB(s)) is shown.

[0262] Example 2 Direct resource allocation ((multiple) gNBs).

[0263] Consider that the operation of SL-TDOA is similar to DL-TDOA, where multiple anchor nodes send SL PRS to the target UE, and the target UE performs SL RSTD measurement.

[0264] It is assumed that at least one anchor UE belongs to a different cell from the target UE.

[0265] It is assumed that resource allocation is performed by the respective gNBs.

[0266] Assume that the target UE receives a trigger for SL-TDOA positioning from a higher layer.

[0267] The steps according to the proposed method are as follows:

[0268] 1. The target UE sends a resource allocation initiation to other UEs participating in the positioning process.

[0269] 2. Each UE sends an SR to its respective gNB; the gNB provides UL resources to each UE to send a SL positioning resource allocation request; each UE sends a resource allocation request for SL PRS transmission; the gNB sends a resource allocation grant to each UE.

[0270] 3. All anchor UE(s) perform SL PRS transmission on the allocated resources, and the target UE performs SL RSTD measurements for higher layers to calculate its own position.

[0271] Solution 3: Direct or indirect resource allocation is determined by the serving cell

[0272] In this solution, after the UE raises an SR for UL resources and the gNB grants UL resources for sending further information, the UE sends information on whether there are out-of-coverage UEs participating in positioning on the granted UL resources.

[0273] If there are out-of-coverage UEs involved, the gNB uses indirect resource allocation and sends these resources to the UE sending the SR, which forwards them to all other UEs.

[0274] If there is no out-of-coverage UE participating, the gNB can decide whether to use direct resource allocation or indirect resource allocation based on latency requirements, available resources, etc.

[0275] If direct resource allocation is to be used, the gNB sends an indication to the UE that sent the SR to send an indication of autonomous resource allocation request to all participating UEs.

[0276] If indirect resource allocation is to be used, the gNB sends an indication to the UE that sent the SR to forward the resource allocation to the corresponding UE.

[0277] Similarly, if resources are allocated by the LMF instead of the gNB, the LMF decides between direct and indirect resource allocation and sends appropriate indications to the requesting UE.

[0278] A new WID for extending and improving NR positioning was approved in RAN #98-e in December 2022, with work set to begin in 2023. The following is part of the WID: It specifies resource allocation to support SL PRS, including resource allocation schemes 1 and 2, where scheme 1 corresponds to network-centric SL PRS resource allocation and scheme 2 corresponds to UE-autonomous SL PRS resource allocation [RAN1]. This application provides a systematic approach to network-centric resource allocation, including when UEs belong to different cells. Unlike resource allocation for SL communication, SL positioning requires coordination between (multiple) UEs to efficiently utilize network-allocated resources.

[0279] abbreviation

[0280]

Claims

1. A method for network-centric resource allocation for sidelink positioning in a wireless communication system having at least one user equipment (UE), the method being characterized in that at least one or more user equipments (UEs) initiate indirect and / or direct resource allocation for performing a sidelink positioning procedure, wherein the positioning procedure itself is triggered by the UE or any other node.

2. The method according to claim 1, characterized in that At least one UE participating in SL positioning belongs to different serving cells in the wireless communication system.

3. The method according to claim 1 or 2, characterized in that When the user equipment (UE) performs indirect resource allocation, one of the UEs in the coverage area initiates SL positioning through its own serving cell or location management function (LMF) and handles resource allocation for all UEs participating in the SL positioning.

4. The method according to any one of claims 1 to 3, characterized in that SL positioning resource allocation is always routed through a UE in coverage, and the requesting UE forwards the resource allocation to other UEs via SL, and UEs out of coverage are able to participate in positioning.

5. The method according to any one of claims 1 to 4, characterized in that Whenever a UE within coverage receives a trigger of any subset or all of the following from its own upper layer or any other node in the network, the UE is triggered for resource allocation, where the trigger is the sending and / or reception of SL PRS, or the sending and / or reception of at least one SL positioning measurement report or signal, and / or the transmission of data related to the SL positioning operation.

6. The method according to any one of claims 1 to 5, characterized in that Before or after triggering the positioning procedure and before making the resource allocation request, the UEs within the coverage area request and receive the UE IDs and cell IDs of all other UEs participating in the positioning operation from all other UEs participating in the positioning operation.

7. The method according to any one of claims 1 to 6, characterized in that The UE IDs of all other UEs participating in the positioning operation and the cell IDs of all other participating UEs are obtained in the following manner: • any data channels or control channels within the dedicated resource pool (RP) used by the UE for positioning with other UEs, and / or • any data channels or control channels within a shared RP that the UE uses with other UEs for communication and positioning, and / or • Any data channel or control channel within the SL communication RP that is used by both the triggering UE and other UEs.

8. The method according to claim 7, characterized in that The data channel is a Physical Sidelink Shared Channel (PSSCH), and the control channel is a Physical Sidelink Control Channel (PSCCH).

9. The method according to claim 8, characterized in that The UE requests any of the following: data and / or control channel resources on a dedicated RP for positioning, or data and / or control channel resources on a shared RP for positioning and communication, or data channel resources on a SL communication RP; and the triggering UE within the coverage has obtained resource allocation through the gNB, the triggering UE within the coverage identifies the UE that does not belong to the same cell based on its cell ID, and then sends a scheduling request (SR) to its serving cell (gNB) to authorize UL resources to send further information.

10. The method according to claim 9, characterized in that The SR also indicates the amount of UL resources required by the UE to send further information, and as a response to the SR of the UE, the gNB allocates UL resources to the UE to send further information about the SR, and the UE sends at least this information to the gNB via the UL resources allocated to it, wherein the information includes the type of resources to be scheduled for each UE participating in the positioning procedure, the index of the RP requiring resources, and the time characteristics / periodicity of the required resources and / or the type of positioning method.

11. The method according to claim 9, characterized in that The UE that needs resources for SL positioning sends a request to the LMF, where the request can be sent using the existing Long Term Evolution (LTE) Positioning Protocol (LPP) and includes: • UE IDs and cell IDs of all participating UEs; •The number of UEs participating in the positioning process; • Index of the RP that requires resources (if the UE uses multiple RPs); • Type of resources required (e.g., SL-PRS resources, measurement reporting resources, etc.); • Temporal characteristics / periodicity of the required resources (e.g., aperiodic / semi-persistent / periodic SL-PRS, multiple measurement reports in a predefined sequence, etc.).

12. The method according to claim 1 or 2, characterized in that A UE within the coverage of which the positioning process is triggered by its higher layer sends an indication of initiating resource allocation to other participating UEs; the indication includes at least the following information: •The type of resources required; •The temporal nature / periodicity of the resources required; •Preferred time-frequency location of resources; •The index of the RP that requires the resource.

13. The method according to claim 12, characterized in that The following information can be sent via: • Any control channel or data channel within the dedicated RP that the triggering UE uses for positioning with other UEs; • Any control channel or data channel within the shared RP that the triggering UE uses with other UEs for communication and positioning; • Any data channel within the SL communication RP that the triggering UE uses for communication with other UEs.

14. The method according to claim 13, characterized in that In response to each UE's SR, the corresponding serving cell (gNB) allocates UL resources to each UE to send further information about the SR. The UE then sends at least the following information to the gNB via the allocated UL resources: •The type of resources required; •The temporal nature / periodicity of the resources required; •Preferred time-frequency location of resources; •The index of the RP that requires the resource.

15. The method according to claim 1 or 2, characterized in that The UE within the coverage area that is triggered by its upper layer to trigger the positioning process or trigger the resource allocation sends an indication to initiate resource allocation to other UEs participating in the SL positioning process, and then each participating UE that needs resources for SL positioning sends a request to the LMF, which can be sent using the existing LPP.

16. The method according to claim 1 or 2, characterized in that After the UE raises an SR for UL resources and the gNB grants UL resources for sending further information, the UE sends information on whether there are out-of-coverage UEs participating in positioning on the granted UL resources. If there are out-of-coverage UEs participating, the gNB uses indirect resource allocation and sends these resources to the UE that sent the SR, which forwards them to all other UEs. If there is no out-of-coverage UE participating, the gNB can decide whether to use direct resource allocation or indirect resource allocation based on latency requirements, available resources, etc. If direct resource allocation is to be used, the gNB sends an indication to the UE sending the SR to send an indication to all participating UEs to initiate autonomous resource allocation requests, If indirect resource allocation is to be used, the gNB sends an indication to the UE that sent the SR to forward the resource allocation to the corresponding UE, If resources are allocated by the LMF instead of the gNB, the LMF decides between direct resource allocation and indirect resource allocation and sends appropriate indications to the requesting UE.

17. An apparatus for network-centric resource allocation for sidelink positioning, the apparatus comprising a wireless transceiver, a processor coupled to a memory having computer program instructions stored therein, the instructions being configured to implement the steps of claims 1 to 16.

18. A user equipment within coverage, comprising the apparatus according to claim 17.

19. Other user equipment, comprising the apparatus according to claim 17.

20. A serving gNB, comprising the apparatus according to claim 17.

21. A neighboring gNB, comprising the apparatus according to claim 17.

22. A wireless communication system with network-centric resource allocation for sidelink positioning, wherein: The wireless communication system comprises a user equipment within the coverage area of ​​claim 18, other user equipments according to claim 19, a serving gNB according to claim 20, and a neighboring gNB according to claim 21, wherein the other user equipments, the serving gNB, and the neighboring gNB 24 each comprise a processor coupled to a memory having computer program instructions stored therein, the instructions being configured to implement the steps of claims 1 to 16.

Images