Resource allocation based on field information

Abstract

Apparatuses, methods, and systems for allocating resources based on field information are disclosed. A method (700) includes receiving (702), at a user equipment (UE), downlink control information (DCI) that allocates sidelink (SL) resources. The DCI includes a first field indicating whether the SL resource is allocated for SL positioning reference signal (PRS) (SL-PRS) transmission. The method (700) includes, in response to the first field indicating that the SL resource is allocated for the SL-PRS transmission, performing (704) the SL-PRS transmission based at least in part on the DCI. The method (700) includes initiating a Physical SL Shared Channel (PSSCH) transmission in response to the first field indicating (706) that the SL resource is not allocated for the SL-PRS transmission.

Description

Technical Field

[0001] The subject matter disclosed herein relates generally to wireless communications, and more particularly to allocating resources based on field information. Background Art

[0002] In some wireless communication systems, side link (SL) resources and positioning may be used. In such systems, resource and positioning allocation may be inefficient. Summary of the invention

[0003] Methods for allocating resources based on field information are disclosed. Apparatus and systems also perform the functions of these methods. One embodiment of a method includes receiving downlink control information (DCI) allocating SL resources at a user equipment (UE). The DCI includes a first field indicating whether the SL resources are allocated for SL positioning reference signal (PRS) (SL-PRS) transmission. In some embodiments, the method includes performing SL-PRS transmission based at least in part on the DCI in response to the first field indicating that the SL resources are allocated for SL-PRS transmission. In certain embodiments, the method includes initiating a physical SL shared channel (PSSCH) transmission in response to the first field indicating that the SL resources are not allocated for SL-PRS transmission.

[0004] A device for allocating resources based on field information includes a processor. In some embodiments, the device includes a memory coupled to the processor, and the processor is configured to cause the device to: receive a DCI that allocates SL resources, wherein the DCI includes a first field indicating whether the SL resources are allocated for SL-PRS transmission; in response to the first field indicating that the SL resources are allocated for SL-PRS transmission, perform SL-PRS transmission based at least in part on the DCI; and in response to the first field indicating that the SL resources are not allocated for SL-PRS transmission, initiate PSSCH transmission.

[0005] Another embodiment of a method for allocating resources based on field information includes sending a DCI at a network device that allocates SL resources. The DCI includes a first field indicating whether the SL resources are allocated for SL-PRS transmission. In some embodiments, the method includes receiving a SL-PRS transmission based at least in part on the DCI in response to the first field indicating that the SL resources are allocated for SL-PRS transmission. In some embodiments, the method includes receiving a PSSCH transmission in response to the first field indicating that the SL resources are not allocated for SL-PRS transmission.

[0006] Another apparatus for allocating resources based on field information includes a processor. In some embodiments, the apparatus includes a memory coupled to the processor, and the processor is configured to cause the apparatus to: send a DCI that allocates SL resources, wherein the DCI includes a first field indicating whether the SL resources are allocated for SL-PRS transmission; in response to the first field indicating that the SL resources are allocated for SL-PRS transmission, receive a SL-PRS transmission based at least in part on the DCI; and in response to the first field indicating that the SL resources are not allocated for SL-PRS transmission, receive a PSSCH transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] The above embodiments will be described in more detail with reference to the specific embodiments shown in the accompanying drawings. It should be understood that these drawings depict only some embodiments and are therefore not to be considered limiting of scope, and the embodiments will be described and explained with additional specificity and detail using the accompanying drawings, in which:

[0008] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for allocating resources based on field information;

[0009] Figure 2 is a schematic block diagram illustrating one embodiment of an apparatus that may be used to allocate resources based on field information;

[0010] Figure 3 is a schematic block diagram illustrating one embodiment of an apparatus that may be used to allocate resources based on field information;

[0011] Figure 4A is a diagram illustrating an embodiment of a relative positioning variable coordinate system;

[0012] Figure 4B is a diagram illustrating an embodiment of a relative positioning variable movement coordinate system;

[0013] Figure 4C is a diagram illustrating one embodiment of an absolute positioning fixed coordinate system;

[0014] Figure 5 is a diagram illustrating one embodiment of a beam-based positioning framework;

[0015] Figure 6 is a diagram illustrating one embodiment of a vehicle ad hoc network (VANET) architecture;

[0016] Figure 7 is a flow chart illustrating one embodiment of a method of allocating resources based on field information; and

[0017] Figure 8is a flow chart illustrating another embodiment of a method of allocating resources based on field information. DETAILED DESCRIPTION

[0018] As will be appreciated by those skilled in the art, aspects of the embodiments may be embodied as systems, devices, methods or program products. Therefore, the embodiments may take the form of a complete hardware embodiment, a complete software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, which are generally referred to herein as "circuit", "module" or "system". In addition, the embodiments may take the form of a program product, which is embodied in one or more computer-readable storage devices, which store machine-readable code, computer-readable code and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transient and / or non-transmitting. The storage device may not embody a signal. In a specific embodiment, the storage device only uses a signal to access the code.

[0019] Some of the functional units described in this specification may be labeled as modules to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit, including a custom very large scale integrated circuit (VLSI) circuit or gate array, an off-the-shelf semiconductor (such as a logic chip, transistor, or other discrete component). A module may also be implemented in a programmable hardware device, such as a field programmable gate array, programmable array logic, a programmable logic device, etc.

[0020] Modules can also be implemented with code and / or software for various types of processors to perform. The code module of the identification can, for example, include one or more physical or logical blocks of executable code, which can, for example, be organized as objects, processes or functions. However, the executable program of the identified module does not need to be physically located together, but can include different instructions stored in different locations, which, when logically connected together, include the module and realize the described purpose of the module.

[0021] In fact, a code module can be a single instruction, or it can be many instructions, and it can even be distributed on several different code segments, between different programs, and between several memory devices. Similarly, operating data can be identified and illustrated in the module, and can be embodied in any suitable form and organized in any suitable type of data structure. The operating data can be collected as a single data set, or can be distributed in different locations, including on different computer-readable storage devices. In the case where a module or a module portion is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0022] 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 storing 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.

[0023] More specific examples of storage devices (a non-exhaustive list) include the following: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an 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.

[0024] The code for performing the operations of the embodiments 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++, etc.), as well as traditional procedural programming languages ​​(such as "C" programming language, etc.) 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 separate 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 case, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or a connection to an external computer (e.g., via the Internet using an Internet service provider) can be implemented.

[0025] References throughout this specification to "one embodiment," "an embodiment," or similar language indicate that a particular feature, structure, or characteristic described in conjunction with the embodiment is included in at least one embodiment. Therefore, unless otherwise expressly provided, the phrases "in one embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily, refer to the same embodiment, but to "one or more but not all embodiments." Unless otherwise expressly provided, the terms "include," "comprises," "has," and variations thereof refer to "including but not limited to." Unless otherwise expressly provided, a list of items listed does not indicate that any or all items are mutually exclusive. Unless otherwise expressly provided, the terms "one," "an," and "the" also refer to "one or more."

[0026] In addition, the features, structures or characteristics of the described embodiments may be combined in any suitable manner. In the following description, many specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a comprehensive understanding of the embodiments. However, those skilled in the relevant art will recognize that the embodiments may be practiced without one or more specific details or using other methods, components, materials, etc. In other cases, well-known structures, materials or operations are not shown or described in detail to avoid confusing the various aspects of the embodiments.

[0027] The following reference is made to the schematic flow chart and / or schematic block diagram of the method, device, system and program product according to the embodiment to describe various aspects of the embodiment. It should be understood that each block of the schematic flow chart and / or schematic block diagram and the combination of blocks in the schematic flow chart and / or schematic block diagram can be realized 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 produce a machine, so that instructions executed via the processor of the computer or other programmable data processing devices can create a component for realizing the function / action specified in one or more schematic flow chart blocks and / or schematic block diagram blocks.

[0028] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other device to work 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 one or more schematic flowchart blocks and / or schematic block diagram blocks.

[0029] The code may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are executed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, so that the code executed on the computer or other programmable apparatus provides a process for implementing the functions / actions specified in one or more flowchart blocks and / or block diagram blocks.

[0030] The schematic flow charts and / or schematic block diagrams in the figures illustrate the possible implementation architectures, functions and operations of the devices, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flow charts and / or schematic block diagrams may represent a module, segment or portion of a code, which includes one or more executable instructions for implementing the code of (multiple) specified logical functions.

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

[0032] Although various arrow types and line types can be adopted in flow chart and / or block diagram, it should be understood that they do not limit the scope of corresponding embodiment.In fact, some arrows or other connectors can be used to indicate the logical flow of the described embodiment only.For example, the waiting or monitoring period of the unspecified duration between the enumeration steps of the described embodiment can be indicated by an arrow.It will also be noted that each block of block diagram and / or flow chart and the combination of blocks in block diagram and / or flow chart can be realized by a system based on special hardware or a combination of special hardware and code that performs a specified function or action.

[0033] The description of elements in each figure may refer to elements of subsequent figures. Like reference numerals refer to like elements throughout the drawings, including alternative embodiments of the like elements.

[0034] Figure 1 An embodiment of a wireless communication system 100 for allocating resources based on field information is depicted. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Although Figure 1 A specific number of remote units 102 and network units 104 are depicted in FIG. 1 , but one skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

[0035] In one embodiment, the remote unit 102 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smart phone, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), a vehicle computer, a network device (e.g., a router, a switch, a modem), an aircraft, a drone, etc. In some embodiments, the remote unit 102 includes a wearable device such as a smart watch, a fitness band, an optical head-mounted display, etc. In addition, the remote unit 102 may be referred to as a subscriber unit, a mobile station, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a subscriber station, a UE, a user terminal, a device, or other terms used in the art. The remote unit 102 may communicate directly with one or more of the network units 104 via UL communication signals. In some embodiments, the remote unit 102 may communicate directly with other remote units 102 via side link communications.

[0036] The network elements 104 may be distributed over a geographic area. In some embodiments, the network elements 104 may also be referred to as and / or may include one or more of the following: access point, access terminal, base station, base station, location server, core network (CN), radio network entity, node B, evolved node B (eNB), 5G node B (gNB), home node B, relay node, device, core network, air server, radio access node, access point (AP), new radio (NR), network entity, access and mobility management function (AMF), unified data management (UDM), unified database (UDR), UDM / UDR, policy control function (PCF), radio access network (RAN), network slice selection function (NSSF), operation, maintenance and management (OAM), session management function (SMF), user plane function (UPF), application function, authentication server function (AUSF), security anchor function (SEAF), trusted non-3GPP gateway function (TNGF) or any other term used in the art. The network element 104 is typically part of a radio access network, which includes one or more controllers communicatively coupled to one or more corresponding network elements 104. The radio access network is typically communicatively coupled to one or more core networks, which may be coupled to other networks, such as the Internet and the public switched telephone network, among other networks. These and other elements of the radio access network and core network are not shown, but are generally known to those of ordinary skill in the art.

[0037] In one implementation, the wireless communication system 100 conforms to the NR protocol standardized in the Third Generation Partnership Project (3GPP), wherein the network unit 104 transmits on the downlink (DL) using an orthogonal frequency division multiplexing (OFDM) modulation scheme, and the remote unit 102 transmits on the uplink (UL) using a single carrier frequency division multiple access (SC-FDMA) scheme or an OFDM scheme. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication protocol, such as WiMAX, an Institute of Electrical and Electronics Engineers (IEEE) 802.11 variant, a Global System for Mobile Communications (GSM), a General Packet Radio Service (GPRS), a Universal Mobile Telecommunications System (UMTS), a Long Term Evolution (LTE) variant, a Code Division Multiple Access 2000 (CDMA2000), ZigBee, Sigfox, etc. The present disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0038] The network unit 104 can serve multiple remote units 102 within a service area (eg, a cell or cell sector) via wireless communication links. The network unit 104 sends DL communication signals to serve the remote units 102 in the time, frequency, and / or spatial domains.

[0039] In various embodiments, the remote unit 102 may receive a DCI that allocates SL resources. The DCI includes a first field indicating whether the SL resources are allocated for SL-PRS transmission. In some embodiments, the remote unit 102 may perform SL-PRS transmission based at least in part on the DCI in response to the first field indicating that the SL resources are allocated for SL-PRS transmission. In some embodiments, the remote unit 102 may initiate a PSSCH transmission in response to the first field indicating that the SL resources are not allocated for SL-PRS transmission. Therefore, the remote unit 102 may be configured to allocate resources based on the field information.

[0040] In some embodiments, the network unit 104 may send a DCI that allocates SL resources. The DCI includes a first field indicating whether the SL resources are allocated for SL-PRS transmission. In some embodiments, the network unit 104 may receive a SL-PRS transmission based at least in part on the DCI in response to the first field indicating that the SL resources are allocated for SL-PRS transmission. In some embodiments, the network unit 104 may receive a PSSCH transmission in response to the first field indicating that the SL resources are not allocated for SL-PRS transmission. Therefore, the network unit 104 can be used to allocate resources based on the field information.

[0041] Figure 2 An embodiment of an apparatus 200 that can be used to allocate resources based on field information is depicted. Apparatus 200 includes an embodiment of a remote unit 102. In addition, remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, input device 206 and display 208 are combined into a single device, such as a touch screen. In some embodiments, remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, remote unit 102 may include one or more of processor 202, memory 204, transmitter 210, and receiver 212, and may not include input device 206 and / or display 208.

[0042] In one embodiment, the processor 202 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 202 may be a microcontroller, a microprocessor, a central processing unit (CPU), a graphics processing unit (GPU), an auxiliary processing unit, a field programmable gate array (FPGA), or a similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

[0043] In one embodiment, memory 204 is a computer readable storage medium. In some embodiments, memory 204 includes volatile computer storage media. For example, memory 204 may include RAM, including dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM) and / or static RAM (SRAM). In some embodiments, memory 204 includes non-volatile computer storage media. For example, memory 204 may include a hard drive, flash memory or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on remote unit 102.

[0044] In one embodiment, input device 206 may include any known computer input device, including a touchpad, button, keyboard, stylus, microphone, etc. In some embodiments, input device 206 may be integrated with display 208, for example, as a touch screen or similar touch-sensitive display. In some embodiments, input device 206 includes a touch screen so that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, input device 206 includes two or more different devices, such as a keyboard and a touchpad.

[0045] In one embodiment, display 208 may include any known electronically controllable display or display device. Display 208 may be designed to output visual, auditory and / or tactile signals. In some embodiments, display 208 includes an electronic display capable of outputting visual data to a user. For example, display 208 may include, but is not limited to, a liquid crystal display (LCD), a light emitting diode (LED) display, an organic light emitting diode (OLED) display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, display 208 may include wearable displays such as smart watches, smart glasses, and head-up displays. In addition, display 208 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0046] In some embodiments, the display 208 includes one or more speakers for generating sounds. For example, the display 208 can generate an audible alarm or notification (e.g., a beep or buzzer). In some embodiments, the display 208 includes one or more tactile devices for generating vibration, motion, or other tactile feedback. In some embodiments, all or part of the display 208 can be integrated with the input device 206. For example, the input device 206 and the display 208 can form a touch screen or similar touch-sensitive display. In other embodiments, the display 208 can be located near the input device 206.

[0047] In certain embodiments, the processor 202 is configured to cause the device to: receive a DCI that allocates SL resources, wherein the DCI includes a first field indicating whether the SL resources are allocated for SL-PRS transmission; in response to the first field indicating that the SL resources are allocated for SL-PRS transmission, perform SL-PRS transmission based at least in part on the DCI; and in response to the first field indicating that the SL resources are not allocated for SL-PRS transmission, initiate PSSCH transmission.

[0048] Although only one transmitter 210 and one receiver 212 are shown, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and receiver 212 may be any suitable type of transmitter and receiver. In one embodiment, the transmitter 210 and receiver 212 may be part of a transceiver.

[0049] Figure 3One embodiment of an apparatus 300 that can be used to allocate resources based on field information is depicted. The apparatus 300 includes one embodiment of the network unit 104. In addition, the network unit 104 can include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. It is understood that the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 can be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

[0050] In some embodiments, the processor 302 is configured to cause the apparatus to: send a DCI that allocates SL resources, wherein the DCI includes a first field indicating whether the SL resources are allocated for SL-PRS transmission; in response to the first field indicating that the SL resources are allocated for SL-PRS transmission, receive a SL-PRS transmission based at least in part on the DCI; and in response to the first field indicating that the SL resources are not allocated for SL-PRS transmission, receive a PSSCH transmission. It should be noted that one or more embodiments described herein may be combined into a single embodiment.

[0051] In 3GPP, a Uu interface positioning framework is defined that enables UE-assisted and UE-based positioning methods. As used herein, "Uu" refers to the wireless link / interface between a UE and a base station unit (such as a gNB). However, the positioning framework may lack efficient UE-to-UE distance and / or orientation determination, which is critical for supporting relative positioning applications for different vertical services, such as vehicle-to-everything (V2X), public safety, Industrial Internet of Things (IIoT), commerce, etc. Therefore, SL positioning technologies, including various Layer 1 (L1) and Layer 2 (L2) processes, will be developed to support absolute and / or relative positioning using SL resources, including distance estimation. It will be understood that positioning can span different scenarios (e.g., within coverage, within partial coverage, and outside coverage).

[0052] In some embodiments, sidelink resource allocation may be used only for SL data transmission. However, when supporting UE-to-UE ranging based services and sidelink positioning, the resource allocation mechanism needs to take into account SL-PRS transmission. Since the gNB can participate in the resource allocation process for SL-PRS, it is necessary to ensure that the gNB is aware of the required SL positioning service quality (QoS) and / or accuracy of the relevant positioning method and the received SL positioning and / or ranging service requests to achieve efficient scheduling of SL-PRS resources.

[0053] Various embodiments are described herein for efficient resource allocation for SL-PRS when performing various SL positioning procedures. Several embodiments are found herein for incorporating SL-PRS transmission within a SL resource allocation mechanism. When a UE requests sidelink resources from a gNB, the UE may include information about the required QoS to be used by the gNB for SL-PRS scheduling. Some embodiments may include signaling details of a DCI and / or sidelink control information (SCI) that allocates resources for the SL-PRS.

[0054] Table 1 lists the various positioning technologies supported.

[0055] Table 1: Supported UE positioning methods

[0056]

[0057]

[0058] NR positioning based on NR Uu signals and standalone (SA) architecture (e.g., beam-based transmission) can be used. Different use cases include commercial and regulatory (e.g., emergency services). Performance requirements are shown in Table 2.

[0059] Table 2

[0060] Positioning error indoor outdoor Horizontal positioning 80% of UEs are less than 3m 80% of UEs are less than 10m Vertical positioning 80% of UEs are less than 3m 80% of UEs are less than 3m

[0061] Positioning performance requirements for commercial and IIoT use cases can be defined as shown in Table 3.

[0062] Table 3

[0063]

[0064] Figure 4A-4C Depicted is an overview of absolute and relative positioning using different coordinate systems.

[0065] Figure 4AAn example of relative positioning using a variable coordinate system 400 is depicted. In some embodiments, the coordinate system 400 can be used to determine a relative positioning 413 between a first UE (denoted as UE-1) 403 and a 5G positioning node, such as a gNB 401 (having a fixed position), when the nodes are within 10 m of each other. In some embodiments, the coordinate system 400 can be used to determine a relative positioning 415 between two or more UEs, such as a second UE (denoted as UE-2) 405 and a fourth UE, when the UEs are within 10 m of each other. In some embodiments, the coordinate system 400 can be used to determine a vertical position 417 of a relative height (or depth) of a third UE (denoted as UE-2) 407 relative to the local ground. In some embodiments, the coordinate system 400 can be used to determine a relative positioning 419 between a fifth UE (denoted as UE-2) 411 outside the coverage 421 of the network and one or more UEs (e.g., UE-4) within the coverage 423 of the network as the UEs approach. The depicted gNB may be an embodiment of the network unit 104 and the UE may be an embodiment of the remote unit 102.

[0066] Figure 4B An example of relative positioning using a mutable mobile coordinate system 430 is depicted. In contrast to system 400, in system 430, the gNB 401 is moving, so the coordinate system also moves relative to a fixed ground location. In some embodiments, the coordinate system 410 can be used to determine the relative longitudinal position 431 (e.g., with an error less than 0.5m) of UEs supporting V2X applications for close-range platooning. In some embodiments, the coordinate system 410 can be used to determine the relative lateral position 433 (e.g., with an accuracy less than 0.1m error) between UEs supporting V2X applications. The depicted gNB 401 can be an embodiment of the network unit 104, and the UE can be an embodiment of the remote unit 102.

[0067] Figure 4C An example of absolute positioning using a fixed coordinate system 440 is depicted. Compared to systems 400 and 430, there are multiple fixed gNBs in the fixed coordinate system 440. In some embodiments, the coordinate system 440 can be used to determine an absolute position 441 of a UE 443 using a first gNB 445, a second gNB 447, and a third gNB 449. In some embodiments, the absolute position can be expressed using x, y, and z coordinates. The gNB depicted can be an embodiment of the network unit 104, and the UE can be an embodiment of the remote unit 102.

[0068] Figure 5A diagram 500 of NR beam-based positioning measurement and reference signal (RS) according to an embodiment of the present disclosure is shown. Here, downlink positioning reference signal (DL-PRS) can be sent by different base stations (serving gNB and neighboring gNB) on frequency range #1 (FR1, i.e., frequencies from 410 MHz to 7125 MHz) and frequency range #2 (FR2, i.e., frequencies from 24.25 GHz to 52.6 GHz) using narrow beams, which is relatively different from LTE in which PRS is sent over the entire cell. Figure 5 As shown, the remote unit 102 may receive DL-PRS from a neighboring first gNB / transmission reception point (TRP) (denoted as gNB1-TRP1) 510, a neighboring second gNB (denoted as gNB2-TRP1) 515, and a third gNB / TRP (denoted as gNB3-TRP1) 520 which serves as a reference or serving gNB.

[0069] Here, the DL-PRS may be locally associated with a DL-PRS resource identifier (ID) and a resource set ID (i.e., TRP) of a base station. In the depicted embodiment, each gNB 510, 515, 520 is configured with a first resource set ID (depicted as resource set ID #0) 525 and a second resource set ID (depicted as resource set ID #1) 530. As shown, the UE 205 receives DL-PRS on a transmission beam; here, DL-PRS is received from gNB1-TRP1 510 on DL-PRS resource ID #3 of the second resource set ID (resource set ID #1) 530, DL-PRS is received from gNB2-TRP1 515 on DL-PRS resource ID #3 of the first resource set ID (resource set ID #0) 525, and DL-PRS is received from gNB3-TRP1 520 on DL PRS resource ID #1 of the second resource set ID (resource set ID #1) 530.

[0070] Figure 6An exemplary system architecture 600 of a VANET according to an embodiment of the present disclosure is depicted. The VANET includes a group of mobile or stationary vehicles connected by a wireless network. In the illustrated implementation, the system architecture 600 involves multiple on-board units (OBUs) 605, which can be mobile or stationary. The OBUs 605 can be embodiments of remote units 102. One or more OBUs can communicate with at least one of multiple roadside units (RSUs) 610. The RSUs 610 can be embodiments of network units 104. The RSUs 610 can communicate with each other via wireless communications and / or via a data network 602. In addition, via the data network 602, the RSUs 610 can communicate with a V2X server 615. Note that the OBUs 605 can also communicate with the V2X server 615 via the RSUs 610. In various embodiments, the VANET entity can perform.

[0071] For the purpose of this disclosure, a positioning-related reference signal may be referred to as a reference signal used for positioning procedures / purposes in order to estimate the position of a target UE (e.g., a PRS) or based on an existing reference signal (such as a channel state information reference signal (CSI-RS) or a sounding reference signal (SRS)); a target UE may be referred to as a device / entity to be positioned. In various embodiments, the term "PRS" may refer to any signal that may be used for positioning, such as a reference signal, even if the signal is not primarily used for positioning.

[0072] SL positioning technology includes but is not limited to round-trip time (RTT) type solutions implemented using SL (including single-sided (also known as unidirectional) and double-sided (also known as bidirectional) RTT); side link angle of arrival (SL-AoA) (including A-AoA and Z-AoA); SL-TDOA (utilizing the SL reference signal time difference (RSTD) of SL signals received from multiple TRPs at the UE (and optional SL-PRS reference signal received power (RSRP)); side link angle of deviation (SL-AoD) (corresponding to a method in which RSRP and / or RSRPP measurements are similar to the DL-AoD method in Uu, including both azimuth angle deviation angle (A-AoD) and zenith angle deviation angle (Z-AoD)).

[0073] Regarding SL discontinuous reception (DRX) operation, when SL DRX is configured, the active time includes the following times: A) when sl-drx-onDurationTimer or sl-drx-InactivityTimer is running; or B) when sl-drx-RetransmissionTimer is running; or C) during the period of sl-LatencyBoundCSI-Report configured by radio resource control (RRC) when the SL-CSI report MAC control element (CE) is not received; or D) when the SL-CSI report MAC CE is received, the time between the transmission of the SL-CSI report request and the reception of the SL-CSI report MAC CE; or E) during the time slot associated with the announced periodic transmission of SL-SCH data by the UE.

[0074] When one or more SL DRXs are configured, if multiple SL DRX cycles mapped to multiple SL-QoS-Profiles of the destination Layer 2 ID and the propagation type of interest are associated with multicast or broadcast, the MAC entity selects an sl-drx-Cycle whose length is the shortest cycle among the multiple SL DRX cycles mapped to the multiple SL-QoS-Profiles associated with the destination Layer 2 ID. In addition, the MAC entity selects an sl-drx-onDurationTimer whose length is the longest timer among the multiple SL DRX onDuration timers that are mapped to the multiple SL-QoS-Profiles associated with the destination Layer 2 ID.

[0075] When one or more SL DRX are configured, if the sl-drx-HARQ-RTT-Timer expires, if the data of the corresponding side link process is not successfully decoded, or if the HARQ feedback (i.e., negative acknowledgment) for unicast is not sent due to UL / SL priority, the MAC entity starts the sl-drx-RetransmissionTimer for the corresponding side link process in the first time slot after the expiration of the sl-drx-HARQ-RTT-Timer.

[0076] When the upper layer indicates that the propagation type is multicast or broadcast, sl-drx-StartOffset and sl-drx-SlotOffset are derived from the following equations:

[0077] sl-drx-StartOffset (ms) = destination layer 2 ID modulo sl-drx-Cycle

[0078] sl-drx-SlotOffset (ms) = the time of the destination layer 2 ID modulo one subframe

[0079] Number of gaps

[0080] When the propagation type is multicast or broadcast, if the SL DRX cycle is used and [(DFN×10)+subframe number] modulo (sl-drx-Cycle)=sl-drx-StartOffset, the MAC entity starts sl-drx-onDurationTimer after sl-drx-SlotOffset from the start of the subframe.

[0081] If the SL DRX is in the active time, the MAC entity monitors the SCI (i.e., the first-level SCI and the second-level SCI) in the SL DRX. Then, if the SCI indicates a new SL transmission, and if the source layer 1 ID of the SCI is equal to the 8 least significant bits (LSBs) of the expected destination layer 2 ID, and the destination layer 1 ID of the SCI is equal to the 16 LSBs of the expected source layer 2 ID, and the propagation type indicator in the SCI is set to unicast, the MAC entity starts (or restarts) the sl-drx-InactivityTimer for the corresponding source layer 2 ID and destination layer 2 ID pair after the first time slot of the SCI reception.

[0082] In addition, if the SCI indicates a new SL transmission, and if the destination Layer 1 ID of the SCI (i.e., the second-level SCI) is equal to the 16 LSBs of the expected destination Layer 1 ID, and the propagation type indicator in the SCI is set to multicast, the MAC entity selects a sl-drx-InactivityTimer whose length is the largest among multiple SL DRX inactivity timers of multiple SL-QoS-Profiles mapped to the destination Layer 2 ID associated with the destination Layer 1 ID of the SCI. In addition, after the first time slot of SCI reception, the MAC entity starts (or restarts) the sl-drx-InactivityTimer for the corresponding destination Layer 2 ID.

[0083] When SL DRX is in active time, if SCI indicates SL transmission, if the next retransmission opportunity is scheduled in SCI, the MAC entity derives the sl-drx-HARQ-RTT-Timer from the retransmission resource timing of the next retransmission resource in SCI. Otherwise, the MAC entity uses the sl-drx-HARQ-RTT-Timer configured by the upper layer.

[0084] When SCI indicates SL transmission, if physical sidelink feedback channel (PSFCH) resources are not configured for the SL grant associated with the SCI, the MAC entity starts the sl-drx-HARQ-RTT-Timer for the corresponding sidelink process in the time slot after the end of the PSSCH transmission (i.e., the currently received PSSCH).

[0085] However, if PSFCH resources are configured for the SL grant associated with the SCI, the MAC entity starts the sl-drx-HARQ-RTT-Timer for the corresponding side link process in the first time slot after the end of the corresponding PSFCH transmission carrying the SL HARQ feedback if the SCI enables HARQ feedback and the propagation type indicator in the SCI is set to unicast, or if the SCI enables HARQ feedback and the propagation type indicator in the SCI is set to groupcast and positive and negative acknowledgments are selected. Alternatively, when the SL HARQ feedback is not sent due to UL / SL priority, the MAC entity starts the sl-drx-HARQ-RTT-Timer for the corresponding side link process in the first time slot after the end of the corresponding PSFCH resource for the SL HARQ feedback.

[0086] When PSFCH resources are configured for the SL grant associated with the SCI, if HARQ feedback is enabled for the SCI, and the propagation type indicator in the SCI is set to multicast, and only negative acknowledgment is selected, the MAC entity starts the sl-drx-HARQ-RTT-Timer for the corresponding side link process in the first time slot after the end of the corresponding PSFCH transmission carrying the SL HARQ feedback. Alternatively, when the SL HARQ feedback is not sent due to UL / SL priority, the MAC entity starts the sl-drx-HARQ-RTT-Timer for the corresponding side link process in the first time slot after the end of the corresponding PSFCH resource of the SL HARQ feedback. Alternatively, when the SL HARQ feedback is a positive acknowledgment, the MAC entity starts the sl-drx-HARQ-RTT-Timer for the corresponding side link process in the first time slot after the end of the corresponding PSFCH resource of the SL HARQ feedback.

[0087] When PSFCH resources are configured for the SL grant associated with the SCI, if the SCI disables HARQ feedback and (multiple) resources for one or more retransmission opportunities are not scheduled in the SCI, the MAC entity starts the sl-drx-HARQ-RTT-Timer for the corresponding side link process in the time slot after the end of the PSFCH resources.

[0088] When PSFCH resources are configured for the SL grant associated with the SCI, if the SCI disables HARQ feedback and (multiple) resources for one or more retransmission opportunities are scheduled in the SCI, the MAC entity starts the sl-drx-HARQ-RTT-Timer for the corresponding side link process in the time slot after the end of the PSSCH transmission (i.e., the currently received PSSCH). In addition, the MAC entity stops the sl-drx-RetransmissionTimer for the corresponding side link process.

[0089] When the propagation type is multicast or broadcast, if the SL DRX command MAC CE of the unicast source layer 2 ID and destination layer 2 ID pair is received, the MAC entity stops the sl-drx-onDurationTimer of the unicast source layer 2 ID and destination layer 2 ID pair. In addition, the MAC entity stops the sl-drx-InactivityTimer of the unicast source layer 2 ID and destination layer 2 ID pair.

[0090] Regarding UE behavior when sending SL-SCH data during SL DRX operation, regarding the SL DRX active time, the UE sending SL-SCH data should be consistent with the expected UE receiving SL-SCH data, as described above. In addition, the UE sending SL-SCH data determines the SL DRX active time based on the SL DRX timer (e.g., sl-drx-onDurationTimer, sl-drx-InactivityTimer, sl-drx-RetransmissionTimer) running at the (multiple) UEs receiving SL-SCH data or the SL DRX timer (e.g., sl-drx-onDurationTimer, sl-drx-InactivityTimer, sl-drx-RetransmissionTimer) to be run in the future.

[0091] The UE may select resources for the initial transmission of the multicast within the time that the sl-drx-onDurationTimer or sl-drx-InactivityTimer at the destination is running. Note that if the initial transmission causes the sl-drx-RetransmissionTimer to be started at the receiving UE, the UE may assume that the resources for the retransmission are within the active time.

[0092] According to the current 3GPP specifications, SL DRX operation will not be applicable for SL-PRS transmissions. This may lead to a situation where the UE participating in the positioning session is not awake and ready to receive SL-PRS transmissions from the initiating UE. On the other hand, if the UE participating in the sidelink positioning session will always be active and monitoring for potential SL-PRS transmissions will damage the battery power. By extending the SLDRX scheme to also cater for SL-PRS transmissions, this negative impact can be avoided.

[0093] As used herein, the initiator device initiates the SL positioning / ranging session and can be a network entity (e.g., gNB, Location Management Function (LMF)), UE, and / or Road Side Unit (RSU). RSU refers to a traffic infrastructure entity (e.g., an entity that transmits speed notifications or other V2X-related notifications). An RSU that performs UE-like behavior is referred to as a UE-type RSU, and an RSU that performs BS-like behavior is referred to as a gNB-type RSU.

[0094] As used herein, a responder device responds to a SL positioning / ranging session from an initiator device, which may be a network entity (e.g., gNB, LMF), UE, and / or RSU.

[0095] As used herein, a target UE refers to a UE of interest whose position (absolute or relative) is to be acquired by the network and / or the UE itself.

[0096] Sidelink positioning as used in this article refers to obtaining absolute position, relative position or ranging information using a reference signal sent through the SL (ie, UE to UE (PC5) interface).

[0097] As used herein, ranging refers to determining the distance and / or direction between a UE and another entity (eg, an anchor UE).

[0098] The SL-PRS used in this article refers to a reference signal sent through the SL for positioning purposes.

[0099] SL-PRS (pre) configuration: pre-configured parameters of SL-PRS, such as time-frequency resources (not excluding other parameters), including its bandwidth and period.

[0100] As used herein, an anchor UE refers to a UE that supports positioning of a target UE, for example, sending and / or receiving a reference signal for positioning through a SL interface, providing positioning related information, etc. An anchor UE may also be referred to as a SL reference UE.

[0101] As used herein, an auxiliary UE refers to a UE that supports ranging / sidelink positioning between a SL reference UE and a target UE through PC5 when direct ranging / sidelink positioning between the SL reference UE / anchor UE and the target UE cannot be supported. Measurements / results of ranging / sidelink positioning between the auxiliary UE and the SL reference UE and between the auxiliary UE and the target UE are determined and used to derive ranging / sidelink positioning results between the target UE and the SL reference UE.

[0102] As used in this article, SL positioning server UE refers to a UE that provides location server functions for side link positioning and side link ranging instead of LMF. It interacts with the target UE, reference UE, auxiliary UE and positioning UE as needed to calculate the position of the target UE.

[0103] As used in this article, SL positioning client UE refers to a UE that provides location calculation for SL positioning and ranging based services. It interacts with other UEs through PC5 as needed to calculate the location of the target UE. If location calculation is supported, the target UE or SL reference UE can act as a SL positioning server UE.

[0104] As used herein, a SL positioning node may refer to a network entity and / or device / UE participating in a SL positioning session, such as a LMF (location server), a gNB, a UE, an RSU, an anchor UE, an initiator and / or a responder UE.

[0105] As used herein, a configuration entity refers to a network node or device / UE that is capable of configuring time-frequency resources and related SL positioning configuration.

[0106] Various embodiments herein correspond to resource allocation of SL-PRS.

[0107] In a first embodiment, MAC control signaling is used to request sidelink resources for SL-PRS from the gNB. In one example, the sidelink UE requests SL resources for SL-PRS transmission from the gNB by sending a new MAC control element. According to one implementation of the first embodiment, a new MAC CE for requesting resources for SL-PRS is mapped to an SR configuration configured by RRC. In one example, if the UE does not have available uplink resources for transmission of the new SL-PRS MAC CE, the UE (e.g., MAC layer) triggers transmission of the SR. According to some alternative implementations of this embodiment, any SR configuration may be used for the SR triggered by the new MAC requesting resources for SL-PRS transmission.

[0108] According to one implementation of the first embodiment, a new MAC CE for requesting resources for SL-PRS transmission is identified by a MAC subheader with a predefined logical channel identifier (LCID) and has a fixed size of zero bits. According to some alternative implementations of the first embodiment, the new MAC CE carries auxiliary information for allocation of SL-PRS resources in the gNB. In one example, the auxiliary information provides information about the required SL positioning QoS and / or accuracy of the relevant positioning method and the received SL positioning and / or ranging service request. In another example, the auxiliary information includes SL positioning delay to achieve end-to-end absolute and / or relative positioning measures and / or estimates and / or required SL positioning reliability. According to one implementation of the first embodiment, the MAC CE includes a set of SL-PRS parameters proposed by the requesting UE for the corresponding SL-PRS transmission. Example SL-PRS parameters include PRS comb size, bandwidth (e.g., maximum value), PRS resource or resource set, repetition, periodicity, resource element pattern offset and / or frequency layer.

[0109] In a second embodiment, the DCI that allocates side link resources includes a field indicating whether the side link resources are used for SL data transmission on the PSSCH or for SL-PRS transmission. According to one implementation of the second embodiment, the new field indicating the SL transmission type within the DCI is a 1-bit flag. For the case where the UE is configured with mode 1 resource allocation mode for SL-PRS transmission, the gNB explicitly allocates SL resources for SL-PRS transmission to the UE through the DCI. According to another implementation of the second embodiment, if the DCI allocates SL resources for SL-PRS transmission, the new data indicator (NDI) field and / or the HARQ process ID field are set to a predefined value. In one example, the DCI is DCI format 3_0.

[0110] In a third embodiment, a resource pool index within a DCI that allocates side link resources for SL-PRS transmission is set to a predefined value. In another embodiment, the resource pool index within the DCI is set to an index value pointing to a resource pool reserved for SL-PRS transmission, indicating that the resource allocation is for SL-PRS transmission. If the DCI schedules SL-PRS transmission by setting the resource pool index field within the DCI to a specific value, the NDI field and / or the HARQ process ID field of the DCI are set to some predefined values. In one example, the NDI field and / or the HARQ process ID field within the DCI that schedules SL-PRS transmission is repurposed (e.g., to indicate the start time, duration, period, or number of repetitions of the SL-PRS resources).

[0111] In a fourth embodiment, the side link resource configuration for SL-PRS transmission is provided by high-layer signaling (e.g., RRC signaling), and its activation and / or deactivation is signaled via PDCCH (e.g., SL DCI). In one example, a set of SL-PRS resource configurations is configured by RRC signaling, and a DCI is used to activate one of the pre-configured SL-PRS configurations. In one example, a set of SL-PRS resource configurations is configured for a resource pool. According to an implementation of the fourth embodiment, the DCI for activating and / or deactivating the configured SL-PRS resource configuration includes an identifier pointing to the SL-PRS configuration within the pre-configured SL-PRS resource configuration set.

[0112] In one example, RRC signaling only provides high-level parameters (e.g., period, number of SL-PRS transmissions, etc.) of the SL-PRS configuration. DCI signaling can realize rapid modification of semi-persistently allocated SL resources. In this way, it realizes the flexibility of semi-persistent SL-PRS transmission in terms of the required SL positioning QoS and / or accuracy of the relevant positioning method and the received SL positioning and / or ranging service request. According to an implementation of the third embodiment, the DCI that activates the SL-PRS configuration carries SL authorization information (e.g., time domain information and / or resources, frequency domain resources, comb-based time-frequency RE mapping information and other related parameters). In one example, after receiving the DCI that activates the pre-configured SL-PRS configuration, the UE verifies the activation DCI and performs SL-PRS transmission according to the resource allocation given by the RRC and DCI signaling. The term verification can generally be understood as a functional process in the UE, which is used to ensure that the DCI represents a valid PDCCH by identifying at least a specific field included in the DCI. In one example, a set of fields within the DCI that activates the SL-PRS is set to a predefined value. In response to receiving the DCI, the UE checks whether a set of fields within the DCI matches corresponding predefined values. Only if the verification is successful, the UE performs SL-PRS activation. In one example, the DCI indicates the number of SL-PRS transmissions to be performed by the UE.

[0113] In the fifth embodiment, the UE does not consider the time slots and / or symbols in which the SL-PRS transmission is scheduled as valid sidelink resources for SL data transmission. According to one implementation of the fifth embodiment, a UE configured with the mode 2 resource allocation mode does not consider the SL time slots and / or symbols allocated for SL-PRS transmission as candidate resources for sidelink communication (e.g., data transmission) when performing a resource selection process.

[0114] In the sixth embodiment, the UE skips the UL grant (e.g., allocated by the gNB) if the allocated SL resources overlap with the SL-PRS transmission. According to one implementation of the sixth embodiment, the UE prioritizes the SL-PRS transmission over the SL data transmission if there are (partial) overlapping resources.

[0115] According to some embodiments, the UE compares the priority of the SL-PRS transmission with the priority of the conflicting SL data transmission (e.g., PSSCH transmission) and performs the higher priority transmission (e.g., including any required corresponding SCI and / or physical sidelink control channel (PSCCH) transmission) when the SL-PRS transmission and the SL data transmission conflict. In one example, the priority of the SL-PRS transmission is determined as the priority indicated within the SCI accompanying the SL-PRS transmission.

[0116] According to one implementation of such an embodiment, if the UE does not perform SL-PRS transmission due to a higher priority conflicting SL data (eg, PSSCH) transmission, the UE (eg, MAC) triggers resource reselection for the SL-PRS resources.

[0117] In certain embodiments, the UE notifies the gNB of the selected SL-PRS resources to avoid collision and / or overlap of SL-PRS transmissions with SL resources used for SL communication (e.g., data).

[0118] In a seventh embodiment, a reserved SL-PRS transmission may be preempted by another higher priority SL-PRS transmission and / or SL data transmission. Using the preemption mechanism, a UE may use one or more resources originally reserved by another UE for a lower priority SL-PRS transmission and / or SL data transmission. The priority of the SL-PRS may be related to the required SL positioning QoS and / or accuracy of the relevant positioning method and the received SL positioning and / or ranging service request. In one example, the priority of the SL-PRS transmission is signaled within the accompanying SCI.

[0119] In an eighth embodiment, a sidelink UE may be configured with a first resource allocation mode for transmission of sidelink data and a second resource allocation mode for transmission of SL-PRS. In one implementation of the eighth embodiment, the first resource allocation mode is different from the second resource allocation mode. In one example, the UE may be configured with mode 1 for SL data communication (e.g., SL resources for PSSCH transmission are allocated and / or scheduled by the gNB), and the UE autonomously selects SL resources for SL-PRS transmission.

[0120] In a ninth embodiment, when generating an inter-UE coordination (IUC) report, the UE includes the time slots and / or symbols in which the SL-PRS transmission is scheduled in a non-preferred resource set. The SL UE may support IUC, whereby UE-A sends information about resources to UE-B, which then uses the information for resource selection (or reselection). Two schemes are supported for IUC: 1) IUC Scheme 1, where the coordination information sent from UE-A to UE-B is the preferred or non-preferred resources for UE-B's transmission; 2) IUC Scheme 2, where the coordination information sent from UE-A to UE-B is the presence of expected and / or potential resource conflicts on the resources indicated by UE-B's SCI.

[0121] According to one implementation of the ninth embodiment, the SL UE determines a set of resources used by the SL-PRS and includes these resources in a non-preferred time slot set. The UE includes time slots reserved by other UEs, or includes time slots in which UE-A does not expect to perform SL reception from UE-B due to half-duplex operation in the non-preferred resource set when UE-A is the intended receiver of UE-B.

[0122] In the tenth embodiment, the SCI includes a field for requesting SL-PRS transmission from a receiving UE and / or a destination. In one example, the field is a 1-bit flag, which indicates a SL-PRS transmission request when set to a predefined value (e.g., '1'). In another example, the target UE may request SL-PRS transmission from an anchor UE by sending an SCI with the field set to a predefined value. According to one implementation of the tenth embodiment, the SCI has no associated PSSCH (e.g., only SCI transmission). According to another implementation of the tenth embodiment, a new MAC control element is used to request SL-PRS transmission. The MAC CE may be identified by a MAC subheader with a predefined LCID and may have a fixed size of zero bits. According to some implementations of the tenth embodiment, the new MAC CE carries auxiliary information for SL-PRS transmission parameter selection in the anchor UE. In one example, the auxiliary information provides information about the required SL positioning QoS and / or accuracy of the relevant positioning method and the received SL positioning and / or ranging service request. In another example, the assistance information includes SL positioning delay to achieve end-to-end absolute and / or relative positioning measures and / or estimates and / or required SL positioning reliability. According to one implementation of the tenth embodiment, the MACCE includes a set of SL-PRS resource allocation parameters proposed by the requesting UE (e.g., the target UE) for the corresponding SL-PRS transmission.

[0123] According to one implementation of the tenth embodiment, the UE starts a timer in response to receipt of a SL-PRS request (e.g., a message). In one example, upon receiving a SL-PRS transmission request from a target UE, the anchor UE starts a timer indicating a maximum delay bound for SL-PRS transmission. In another example, the timer is set to a value signaled within the SL-PRS transmission request. In another example, the timer value is pre-configured or fixed in the specification. When the timer expires, the UE (e.g., the anchor UE) will stop performing SL-PRS transmission because the SL-PRS transmission will exceed the maximum allowed delay budget and is limited in use or no longer used. Typically, a UE requested to perform SL-PRS transmission can ensure that the SL-PRS occurs within the delay budget (e.g., while the timer is running).

[0124] Figure 7 is a flow chart illustrating one embodiment of a method 700 for allocating resources based on field information. In some embodiments, the method 700 is performed by a device such as the remote unit 102. In some embodiments, the method 700 may be performed by a processor that executes program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0125] In various embodiments, the method 700 includes receiving 702 a DCI that allocates SL resources. The DCI includes a first field indicating whether the SL resources are allocated for SL-PRS transmission. In some embodiments, the method 700 includes, in response to the first field indicating 704 that the SL resources are allocated for SL-PRS transmission, performing SL-PRS transmission based at least in part on the DCI. In certain embodiments, the method 700 includes initiating PSSCH transmission in response to the first field indicating 706 that the SL resources are not allocated for SL-PRS transmission.

[0126] In some embodiments, the DCI includes a second field and a third field, and in response to the first field indicating that the SL resources are allocated for SL-PRS transmission, the second field and the third field are set to predefined values. In some embodiments, the DCI activates a high-layer SL-PRS configuration. In various embodiments, the high-layer SL-PRS configuration is received via RRC signaling.

[0127] In one embodiment, the method 700 further comprises sending a request for a DCI allocating SL resources. In some embodiments, the request comprises a MAC CE.

[0128] Figure 88 is a flow chart illustrating another embodiment of a method 800 for allocating resources based on field information. In some embodiments, the method 800 is performed by a device such as the network unit 104. In some embodiments, the method 800 may be performed by a processor that executes program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0129] In various embodiments, the method 800 includes sending 802 a DCI that allocates SL resources. The DCI includes a first field indicating whether the SL resources are allocated for SL-PRS transmission. In some embodiments, the method 800 includes receiving a SL-PRS transmission based at least in part on the DCI in response to the first field indicating 804 that the SL resources are allocated for SL-PRS transmission. In some embodiments, the method 800 includes receiving a PSSCH transmission in response to the first field indicating 806 that the SL resources are not allocated for SL-PRS transmission.

[0130] In some embodiments, the DCI includes a second field and a third field, and in response to the first field indicating that the SL resources are allocated for SL-PRS transmission, the second field and the third field are set to predefined values. In some embodiments, the DCI activates a high-layer SL-PRS configuration. In various embodiments, the high-layer SL-PRS configuration is received via RRC signaling.

[0131] In one embodiment, the method 800 further comprises receiving a request for a DCI allocating SL resources. In some embodiments, the request comprises a MAC CE.

[0132] In one embodiment, a device includes: a processor; and a memory coupled to the processor, the processor being configured to enable the device to: receive a DCI that allocates SL resources, wherein the DCI includes a first field indicating whether the SL resources are allocated for SL-PRS transmission; in response to the first field indicating that the SL resources are allocated for SL-PRS transmission, perform SL-PRS transmission based at least in part on the DCI; and in response to the first field indicating that the SL resources are not allocated for SL-PRS transmission, initiate PSSCH transmission.

[0133] In some embodiments, the DCI includes a second field and a third field, and in response to the first field indicating that the SL resources are allocated for SL-PRS transmission, the second field and the third field are set to predefined values.

[0134] In some embodiments, the DCI activates the higher layer SL-PRS configuration.

[0135] In various embodiments, the higher layer SL-PRS configuration is received via RRC signaling.

[0136] In one embodiment, the processor is configured to cause the apparatus to send a request for a DCI allocating SL resources.

[0137] In some embodiments, the request includes a MAC CE.

[0138] In one embodiment, a method at a UE includes: receiving a DCI that allocates SL resources, wherein the DCI includes a first field indicating whether the SL resources are allocated for SL-PRS transmission; in response to the first field indicating that the SL resources are allocated for SL-PRS transmission, performing SL-PRS transmission based at least in part on the DCI; and in response to the first field indicating that the SL resources are not allocated for SL-PRS transmission, initiating PSSCH transmission.

[0139] In certain embodiments, the DCI includes a second field and a third field, and in response to the first field indicating that the SL resources are allocated for SL-PRS transmission, the second field and the third field are set to predefined values.

[0140] In some embodiments, the DCI activates higher layer SL-PRS configuration.

[0141] In various embodiments, the higher layer SL-PRS configuration is received via RRC signaling.

[0142] In one embodiment, the method further comprises sending a request for a DCI allocating SL resources.

[0143] In some embodiments, the request includes a MAC CE.

[0144] In one embodiment, a device includes: a processor; and a memory coupled to the processor, the processor being configured to cause the device to: send a DCI that allocates SL resources, wherein the DCI includes a first field indicating whether the SL resources are allocated for SL-PRS transmission; in response to the first field indicating that the SL resources are allocated for SL-PRS transmission, receive a SL-PRS transmission based at least in part on the DCI; and in response to the first field indicating that the SL resources are not allocated for SL-PRS transmission, receive a PSSCH transmission.

[0145] In certain embodiments, the DCI includes a second field and a third field, and in response to the first field indicating that the SL resources are allocated for SL-PRS transmission, the second field and the third field are set to predefined values.

[0146] In some embodiments, the DCI activates the higher layer SL-PRS configuration.

[0147] In various embodiments, the higher layer SL-PRS configuration is received via RRC signaling.

[0148] In one embodiment, the processor is configured to cause the apparatus to receive a request for a DCI allocating SL resources.

[0149] In some embodiments, the request includes a MAC CE.

[0150] In one embodiment, a method at a network device includes: sending a DCI that allocates SL resources, wherein the DCI includes a first field indicating whether the SL resources are allocated for SL-PRS transmission; in response to the first field indicating that the SL resources are allocated for SL-PRS transmission, receiving a SL-PRS transmission based at least in part on the DCI; and in response to the first field indicating that the SL resources are not allocated for SL-PRS transmission, receiving a PSSCH transmission.

[0151] In some embodiments, the DCI includes a second field and a third field, and in response to the first field indicating that the SL resources are allocated for SL-PRS transmission, the second field and the third field are set to predefined values.

[0152] In some embodiments, the DCI activates the higher layer SL-PRS configuration.

[0153] In various embodiments, the higher layer SL-PRS configuration is received via RRC signaling.

[0154] In one embodiment, the method further comprises receiving a request for a DCI allocating SL resources.

[0155] In some embodiments, the request includes a MAC CE.

[0156] Embodiments may be practiced in other specific forms. The described embodiments are considered in all respects to be illustrative only, and not restrictive. Therefore, the scope of the present invention is indicated by the appended claims rather than by the above description. All changes within the equivalent meaning and scope of the claims should be included within their scope.

Claims

1. A user equipment (UE), comprising: at least one memory; as well as at least one processor coupled to the at least one memory and configured to cause the UE to: receiving downlink control information (DCI) allocating sidelink (SL) resources, wherein the DCI includes a first field indicating whether the SL resources are allocated for SL positioning reference signal (PRS) (SL-PRS) transmission; In response to the first field indicating that the SL resources are allocated for the SL-PRS transmission, performing the SL-PRS transmission based at least in part on the DCI; and In response to the first field indicating that the SL resources are not allocated for the SL-PRS transmission, a physical SL shared channel (PSSCH) transmission is initiated.

2. The UE according to claim 1, wherein the DCI includes a second field and a third field, and in response to the first field indicating that the SL resources are allocated for the SL-PRS transmission, the second field and the third field are set to predefined values.

3. The UE according to claim 1, wherein the DCI activates a higher layer SL-PRS configuration.

4. The UE of claim 3, wherein the high-layer SL-PRS configuration is received through radio resource control (RRC) signaling. 5 . The UE according to claim 1 , wherein the at least one processor is configured to cause the UE to send a request for the DCI allocating the SL resources. The UE of claim 5 , wherein the request comprises a medium access control (MAC) control element (CE).

7. A processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured to cause the processor to: receiving downlink control information (DCI) allocating sidelink (SL) resources, wherein the DCI includes a first field indicating whether the SL resources are allocated for SL positioning reference signal (PRS) (SL-PRS) transmission; In response to the first field indicating that the SL resources are allocated for the SL-PRS transmission, performing the SL-PRS transmission based at least in part on the DCI; and In response to the first field indicating that the SL resources are not allocated for the SL-PRS transmission, a physical SL shared channel (PSSCH) transmission is initiated.

8. The processor of claim 7, wherein the DCI comprises a second field and a third field, and in response to the first field indicating that the SL resource is allocated for the SL-PRS transmission, the second field and the third field are set to predefined values.

9. A method performed by a user equipment (UE), the method comprising: receiving downlink control information (DCI) allocating sidelink (SL) resources, wherein the DCI includes a first field indicating whether the SL resources are allocated for SL positioning reference signal (PRS) (SL-PRS) transmission; In response to the first field indicating that the SL resources are allocated for the SL-PRS transmission, performing the SL-PRS transmission based at least in part on the DCI; and In response to the first field indicating that the SL resources are not allocated for the SL-PRS transmission, a physical SL shared channel (PSSCH) transmission is initiated.

10. The method according to claim 9, wherein the DCI includes a second field and a third field, and in response to the first field indicating that the SL resource is allocated for the SL-PRS transmission, the second field and the third field are set to predefined values. The method of claim 9 , wherein the DCI activates a higher layer SL-PRS configuration.

12. The method of claim 11, wherein the high-layer SL-PRS configuration is received via radio resource control (RRC) signaling.

13. The method according to claim 9, further comprising: Sending a request for the DCI allocating the SL resources.

14. The method of claim 13, wherein the request comprises a medium access control (MAC) control element (CE).

15. A device for performing a network function, the device comprising: at least one memory; as well as at least one processor coupled to the at least one memory and configured to cause the apparatus to: transmitting downlink control information (DCI) allocating sidelink (SL) resources, wherein the DCI includes a first field indicating whether the SL resources are allocated for SL positioning reference signal (PRS) (SL-PRS) transmission; In response to the first field indicating that the SL resources are allocated for the SL-PRS transmission, receiving the SL-PRS transmission based at least in part on the DCI; and In response to the first field indicating that the SL resources are not allocated for the SL-PRS transmission, a physical SL shared channel (PSSCH) transmission is received.

16. The apparatus according to claim 15, wherein the DCI comprises a second field and a third field, and in response to the first field indicating that the SL resource is allocated for the SL-PRS transmission, the second field and the third field are set to predefined values. The apparatus of claim 15 , wherein the DCI activates a higher layer SL-PRS configuration.

18. The apparatus of claim 17, wherein the high-layer SL-PRS configuration is received via radio resource control (RRC) signaling.

19. The apparatus of claim 15, wherein the processor is configured to cause the apparatus to receive a request for the DCI allocating the SL resources.

20. The apparatus of claim 19, wherein the request comprises a medium access control (MAC) control element (CE).

Images