Configuring reference signal communication for multiple devices

Abstract

Apparatuses, methods, and systems for configuring reference signal communication for multiple devices are disclosed. One method (800) includes receiving (802) an inter-UE coordination ("IUC") configuration for sidelink ("SL") positioning reference signal ("PRS") communication at a user equipment ("UE"). The IUC configuration includes resource element offsets, frequency offsets, or both for the multiple UEs. The method (800) also includes transmitting (804) IUC information to the multiple UEs based at least in part on the IUC configuration and changes to the resource element offsets, frequency offsets, or both, where the IUC information includes preference information, non-preference information, and resource contention information for SL PRS communication.

Description

[Technical Field]

[0001] The subject matter disclosed herein relates generally to wireless communications, and more particularly to configuring reference signal communications for multiple devices. [Background technology]

[0002] In certain wireless communication systems, positioning methods may be user equipment ("UE") assisted. In such systems, positioning methods may be inefficient. Summary of the Invention [Means for solving the problem]

[0003] A method for configuring reference signal communication for multiple devices is disclosed. Apparatus and systems also perform the functions of the method. One embodiment of the method includes receiving, at a UE, an inter-UE coordination ("IUC") configuration for sidelink ("SL") positioning reference signal ("PRS") communication. The IUC configuration includes resource element offsets or frequency offsets, or both, for the multiple UEs. In some embodiments, the method includes transmitting IUC information to the multiple UEs based at least in part on the IUC configuration and changes to the resource element offsets or frequency offsets, or both, where the IUC information includes preference information, non-preference information, and resource contention information for SL PRS communication.

[0004] An apparatus for configuring reference signal communication for a plurality of devices includes a processor. In some embodiments, the apparatus includes a memory coupled to the processor, the processor configured to cause the apparatus to: receive an IUC configuration for SL PRS communication, the IUC configuration including a resource element offset or a frequency offset, or both, for a plurality of UEs; and transmit IUC information to the plurality of UEs based at least in part on the IUC configuration and changes to the resource element offset or the frequency offset, or both, the IUC information including preference information, non-preference information, and resource contention information for the SL PRS communication.

[0005] A more particular description of the embodiments briefly described above will be given by reference to specific embodiments that are illustrated in the accompanying drawings. The embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, with the understanding that these drawings illustrate only some embodiments and therefore should not be considered limiting in scope. [Brief explanation of the drawings]

[0006] [Figure 1] 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for configuring reference signal communication for multiple devices. [Figure 2] FIG. 1 is a schematic block diagram illustrating one embodiment of an apparatus that may be used to configure reference signal communication for multiple devices. [Figure 3] FIG. 1 is a schematic block diagram illustrating one embodiment of an apparatus that may be used to configure reference signal communication for multiple devices. [Figure 4A] FIG. 1 is a schematic block diagram illustrating one embodiment of a UE cooperation scheme. [Figure 4B] FIG. 1 is a schematic block diagram illustrating one embodiment of a UE cooperation scheme. [Figure 5]1 is a schematic block diagram illustrating one embodiment of a system having a UE-to-UE cooperation scheme including an IUC request. [Figure 6] 1 is a schematic block diagram illustrating one embodiment of a system having a UE cooperation scheme including a PRS request. [Figure 7] FIG. 1 is a schematic block diagram illustrating one embodiment of a system having anchor UEs that cooperate using IUC information. [Figure 8] FIG. 1 is a flow chart diagram illustrating one embodiment of a method for configuring reference signal communication for multiple devices. DETAILED DESCRIPTION OF THE INVENTION

[0007] 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. Accordingly, the embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, all of which may be referred to generally herein as a "circuit," "module," or "system." Furthermore, the embodiments may take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage devices may be tangible, non-transitory, and / or non-transmittable. The storage devices may not embody signals. In certain embodiments, the storage devices merely use signals to access the code.

[0008] Some of the functional units described herein may be labeled as modules to more fully emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very large scale integrated ("VLSI") circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0009] Modules may also be implemented in code and / or software for execution by various types of processors. For example, an identified module of code may include one or more physical or logical blocks of executable code that may be organized, for example, as an object, procedure, or function. Nevertheless, the executable files of identified modules need not be physically located together, but may include different instructions stored in different locations that, when logically combined, comprise that module and achieve the purpose stated for that module.

[0010] In practice, a module of code may be a single instruction or many instructions, and may even be distributed across several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and depicted herein in modules and may be embodied in any suitable form and organized within any suitable type of data structure. Operational data may be collected as a single data set or may be distributed across different locations, including across different computer-readable storage devices. When a module or portions of a module are implemented in software, the software portions are stored on one or more computer-readable storage devices.

[0011] Any combination of one or more computer-readable mediums 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, micro-mechanical, or semiconductor system, apparatus, or device, or any suitable combination of the above.

[0012] More specific examples (non-exhaustive list) of storage devices include the following: an electrical connection having one or more wires, a portable computer diskette, 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 disc read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the above. 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.

[0013] The code for performing operations for the embodiments may be any number of lines and may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code may run entirely on the user's computer, partially on the user's computer, as a standalone 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 may 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 the connection to the external computer may be made (e.g., through the Internet using an Internet Service Provider).

[0014] References throughout this specification to "one embodiment," "an embodiment," or similar phrases mean that a particular feature, structure, or characteristic described with respect to an embodiment is included in at least one embodiment. Thus, all appearances of the phrases "in one embodiment," "in an embodiment," and similar phrases throughout this specification may, but do not necessarily, refer to the same embodiment, but mean "one or more, but not all, embodiments" unless otherwise specified. The words "including," "comprising," and "having," and variations thereof, mean "including, but not limited to," unless otherwise specified. An enumerated list of items does not imply that any or all of the items are mutually exclusive unless otherwise specified. The terms "a," "an," and "the" also refer to "one or more," unless otherwise specified.

[0015] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, and hardware chips, to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can 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 an embodiment.

[0016] Aspects of the embodiments are described below with reference to schematic flowchart illustrations and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It will be understood that each block of the schematic flowchart illustrations and / or schematic block diagrams, and combinations of blocks in the schematic flowchart illustrations and / or schematic block diagrams, may be implemented by code. The code may be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, executed by the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in one or more blocks of the schematic flowchart illustrations and / or schematic block diagrams.

[0017] The code may also be stored in a storage device that can instruct a computer, other programmable data processing apparatus, or other device to function in a particular manner, such that the instructions stored on the storage device produce an article of manufacture that includes instructions that implement the functions / acts specified in one or more blocks of the schematic flowchart diagrams and / or schematic block diagrams.

[0018] The code may also be loaded into a computer, other programmable data processing apparatus, or other device to cause the computer, other programmable apparatus, or other device to perform a series of operational steps to generate a computer-implemented process, such that the code running on the computer or other programmable apparatus provides a process for implementing the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.

[0019] The schematic flowchart diagrams and / or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and / or schematic block diagrams may represent a module, segment, or portion of code that includes one or more executable instructions of code for implementing the specified logical function(s).

[0020] It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of 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 the reverse order, depending on the functionality involved. Other steps and methods may be contemplated that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated figures.

[0021] Various arrow and line types may be used in the flowchart and / or block diagrams, but these are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used only to indicate the logical flow of the illustrated embodiments. For example, arrows may indicate wait or monitoring periods of unspecified duration between enumerated steps of the illustrated embodiments. It should also be noted that each block of the block and / or flowchart diagrams, and combinations of blocks in the block and / or flowchart diagrams, may be implemented by dedicated hardware-based systems that perform the specified functions or acts, or a combination of dedicated hardware and code.

[0022] The description of an element in each figure may refer to the element in the preceding figure. Like numbers refer to like elements in all figures, including alternative embodiments of like elements.

[0023] 1 illustrates one embodiment of a wireless communication system 100 for configuring reference signal communication for multiple devices. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Those skilled in the art will recognize that although a particular number of remote units 102 and network units 104 are illustrated in FIG. 1, any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

[0024] In one embodiment, the remote units 102 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart televisions (e.g., Internet-connected televisions), set-top boxes, game consoles, security systems (including security cameras), vehicle-mounted computers, network devices (e.g., routers, switches, modems), aircraft, drones, etc. In some embodiments, the remote units 102 include wearable devices such as smart watches, fitness bands, optical head-mounted displays, etc. Furthermore, the remote units 102 may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UEs, user terminals, devices, or other terms used in the art. The remote units 102 may communicate directly with one or more of the network units 104 via UL communication signals. In particular embodiments, the remote units 102 may communicate directly with other remote units 102 via sidelink communication.

[0025] The network units 104 may be distributed across a geographic region. In a particular embodiment, the network units 104 may be an access point, an access terminal, a base, a base station, a location server, a core network ("CN"), a radio network entity, a Node B, an evolved Node B ("eNB"), a 5G Node B ("gNB"), a home Node B, a relay node, a device, a core network, an aeronautical server, a radio access node, an access point ("AP"), a new radio ("NR"), a network entity, an access and mobility management function ("AMF"), a unified data management ("UDM"), a unified data repository ("UDR"), a UDM / UDR, The network units 104 may also be referred to as and / or may include one or more of: Policy Control Function ("PCF"), Radio Access Network ("RAN"), Network Slice Selection Function ("NSSF"), Operations, Administration, 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 terminology used in the art. The network units 104 are generally part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network units 104. The radio access network is generally 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 well known by those skilled in the art.

[0026] In one implementation, the wireless communication system 100 conforms to the NR protocol standardized in the 3rd Generation Partnership Project (“3GPP®”), in which the network unit 104 transmits using an Orthogonal Frequency Division Multiplexing (“OFDM”) modulation scheme on the downlink (“DL”) and the remote unit 102 transmits using a Single Carrier Frequency Division Multiple Access (“SC-FDMA”) scheme or an OFDM scheme on the uplink (“UL”). More generally, however, the wireless communication system 100 may implement any other open or proprietary communication protocol, such as WiMAX, Institute of Electrical and Electronics Engineers ("IEEE") 802.11 variants, Global System for Mobile Communications ("GSM"), General Packet Radio Service ("GPRS"), Universal Mobile Telecommunications System ("UMTS"), Long Term Evolution ("LTE") variants, Code Division Multiple Access 2000 ("CDMA2000"), Bluetooth, ZigBee, Sigfox, among others. This disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0027] The network unit 104 may serve several remote units 102 within a serving area, e.g., a cell or a cell sector, via a wireless communication link. The network unit 104 transmits DL communication signals to serve the remote units 102 in the time domain, the frequency domain, and / or the spatial domain.

[0028] In various embodiments, the remote unit 102 may receive an IUC configuration for SL PRS communications. The IUC configuration includes resource element offsets, frequency offsets, or both, for multiple UEs. In some embodiments, the remote unit 102 may transmit IUC information to multiple UEs based at least in part on the IUC configuration and changes to the resource element offsets, frequency offsets, or both, where the IUC information includes preference information, non-preference information, and resource contention information for SL PRS communications. Thus, the remote unit 102 may be used to configure reference signal communications for multiple devices.

[0029] 2 illustrates one embodiment of an apparatus 200 that may be used to configure reference signal communication for multiple devices. The apparatus 200 includes one embodiment of the remote unit 102. Additionally, the 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, the input device 206 and the display 208 are combined in a single device, such as a touchscreen. In particular embodiments, the remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and / or the display 208.

[0030] The processor 202, in one embodiment, may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor 202 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to implement 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.

[0031] Memory 204, in one embodiment, is a computer-readable storage medium. In some embodiments, memory 204 includes a volatile computer storage medium. 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 a non-volatile computer storage medium. For example, memory 204 may include a hard disk 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 associated data, such as an operating system or other controller algorithms running on remote unit 102.

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

[0033] Display 208, in one embodiment, may include any known electronically controllable display or display device. Display 208 may be designed to output visual, audible, 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 similar display device capable of outputting images, text, and the like to a user. As another non-limiting example, display 208 may include a wearable display such as a smartwatch, smart glasses, a head-up display, and the like. Furthermore, display 208 may be a component of a smartphone, a personal digital assistant, a television, a tablet computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, and the like.

[0034] In certain embodiments, the display 208 includes one or more speakers for generating sound. For example, the display 208 may generate audible alerts or notifications (e.g., beeps or chimes). In some embodiments, the display 208 includes one or more haptic devices for generating vibrations, movements, or other haptic feedback. In some embodiments, all or a portion of the display 208 may be integrated with the input device 206. For example, the input device 206 and the display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, the display 208 may be located near the input device 206.

[0035] In a particular embodiment, the processor 202 is configured to cause the apparatus to receive an IUC configuration for SL PRS communication, the IUC configuration including a resource element offset or a frequency offset, or both, for a plurality of UEs; and transmit IUC information to the plurality of UEs based at least in part on the IUC configuration and changes to the resource element offset or the frequency offset, or both, the IUC information including preference information, non-preference information, and resource contention information for the SL PRS communication.

[0036] 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.

[0037] 3 illustrates one embodiment of an apparatus 300 that may be used to configure reference signal communication for multiple devices. The apparatus 300 includes one embodiment of the network unit 104. Furthermore, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As can be appreciated, the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may 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.

[0038] It should be noted that one or more embodiments described herein may be combined into a single embodiment.

[0039] In certain embodiments of NR, there may be sidelink positioning extensions that account for vehicle-to-everything ("V2X"), commercial devices, and IIoT. While network-based absolute positioning frameworks exist that enable UE-assisted and UE-based positioning methods, there may be a lack of efficient UE-to-UE relative positioning, range, and / or orientation determination for different vertical services (e.g., V2X, public safety, IIoT, commercial, etc.). In some embodiments, NR V2X positioning may be used for in-coverage, partial coverage, and out-of-coverage scenarios.

[0040] In various embodiments, such as in network-based positioning, a location management function ("LMF") configures DL PRS over the DL positioning frequency layer ("PFL") and configures DL PRS resources for the target UE and / or initiator UE via a location protocol ("LPP"), including PRS configurations received from serving and neighboring gNBs, positioning types (e.g., angle of arrival ("AoA"), round trip time ("RTT"), time difference of arrival ("TDOA", "TDoA"), etc.), and measurement reports.

[0041] In certain embodiments, DL PRS may be transmitted in beams. A DL PRS beam is referred to as a DL PRS resource, while the complete set of PRS beams transmitted from a Transmit Receiving Point ("TRP") on the same frequency is referred to as a DL PRS resource set. Comb patterns and muting patterns may be configured for each resource set.

[0042] In some embodiments, there may be inter-UE coordination methods and procedures for SL PRS that allow for resource sharing with anchor UEs for specific positioning techniques, such as to avoid half-duplex issues.

[0043] In various NR embodiments, there are different inter-UE cooperation schemes: 1) Scheme 1a - preferred resource set, 2) Scheme 1b - non-preferred resource set, and / or Scheme 2 - indication of expected and / or potential resource contention on reserved resources. In Schemes 1a and 1b, UE-A sends a set of resources to be transmitted to UE-B based on explicit triggering information or condition-based triggering received from UE-B. The signaling container for sending the explicit request and transmitting the set of resources is based on MAC CE and / or sidelink control information ("SCI").

[0044] In certain embodiments, the UE-UE cooperation scheme in Mode 2 is classified as being based on the following types of "resource sets" sent by UE-A to UE-B: 1) UE-A sends to UE-B a set of resources that are preferred for UE-B transmissions (e.g., based on its sensing results), 2) UE-A sends to UE-B a set of resources that are not preferred for UE-B transmissions (e.g., based on its sensing results and / or expected and / or potential resource conflicts), and / or 3) UE-A sends to UE-B a set of resources for which a resource conflict is detected (e.g., in some configurations, there may be details of the resource conflict including the type of resource conflict, details of the sensing operation on the UE-A side, and / or which type of resource set information is useful and / or feasible for which cast types (these different types may be used in combination with each other)). In some embodiments, the LS may be sent to the RAN plenary.

[0045] In various embodiments, at least the following aspects may be determined for a scheme of UE-to-UE cooperation identified as feasible and / or beneficial: 1) how and / or when UE-A determines the contents of the "set of resources," including UL scheduling considerations; 2) when UE-A sends the "set of resources" to UE-B, including which UE sends the "set of resources"; 3) how UE-A and UE-B are determined; 4) how UE-A sends the "set of resources" to UE-B, including the container used to carry the "set of resources," either implicitly and / or explicitly; 5) how and when UE-B receives the "set of resources" and takes it into account in its resource selection for its own transmission, and / or whether UE-B does so; and / or 6) how and / or whether to define the relationship between UE-to-UE cooperation support and / or signaling and cast type.

[0046] As used herein, the terms eNB and / or gNB are used for base station, but are interchangeable with any other radio access node (e.g., base station (“BS”), eNB, gNB, AP, NR, etc.). Additionally, while different embodiments may be described in the context of 5G NR, the embodiments are equally applicable to other mobile communication systems that support serving cells and / or carriers configured for sidelink communication over a UE-to-UE (“PC5”) interface.

[0047] 4A and 4B are schematic block diagrams illustrating one embodiment of a UE-to-UE cooperation scheme. In a first set 400 of UE-to-UE cooperation schemes, there are UE-A 402 and UE-B 404. UE-B 404 sends an explicit request 406, and UE-A 402 sends a UE-to-UE cooperation message 408 (e.g., for Scheme 1a or Scheme 1b). In a second set 410 of UE-to-UE cooperation schemes, there are UE-A 412 (e.g., condition-based trigger) and UE-B 414. UE-A 412 sends a UE-to-UE cooperation message 416 (e.g., for Schemes 1a, 1b, and 2).

[0048] In a first embodiment, sidelink positioning techniques such as TDoA, multi-UE RTT, etc. require a target UE to transmit and receive SL PRS from multiple anchor UEs. These anchor UEs support the target UE's positioning over the SL interface (e.g., by transmitting and / or receiving positioning reference signals, providing positioning-related information, etc.). Resource coordination is also required among several transmitting UEs to align SL PRS resources.

[0049] Preferred resource set: A transmitting UE may receive a preferred resource set including PRS resources among one or more combinations of PRS resource ids, PRS resources within a resource set, PRS slot information, PRS bandwidth information, comb patterns within PRS resources, and resource element offsets / frequency offsets to efficiently multiplex PRS signals from multiple transmitters. The transmitting UE may receive the PRS preferred resource set and may perform resource reselection to select one or more of the above resource combinations in candidate resource selection. In the preferred resource set, the TX UE transmitting the SL PRS may be a target UE (e.g., an anchor UE that needs to exchange PRS resource configurations using an IUC message containing IUC information). IUC information may be needed to be exchanged between the target UE and the anchor UE, so that the target UE may send a PRS request toward one or more anchor UEs as shown in Figure 6, indicating a preferred transmission of the SL PRS from the anchor UE to the target UE, which may include time-frequency resources, slot information, PRS length, PRS bandwidth, PRS resource set identifier ("ID"), comb pattern, and / or resource element offset for each anchor UE transmitting the SL PRS, which may be implicitly determined by a specific rule or explicitly indicated in signaling. The IUC information may be signaled using MAC CE, SCI, and using LPP signaling. A new configuration message for IUC signaling may be added to the LPP container.

[0050] 5 is a schematic block diagram illustrating one embodiment of a system 500 having a UE-to-UE cooperation scheme including an IUC request. The system 500 includes a UE-A 502 (e.g., an anchor UE) and a UE-B 504 (e.g., a target UE). The UE-B 504 sends an explicit request for IUC 506, the UE-A 502 sends an IUC message 508 (e.g., a preferred or non-preferred resource set), and the UE-B 504 sends an SL PRS 510.

[0051] 6 is a schematic block diagram illustrating one embodiment of a system 600 having a UE-to-UE cooperation scheme including a PRS request. The system 600 includes a UE-A 602 (e.g., an anchor UE) and a UE-B 604 (e.g., a target UE). The UE-B 604 sends an explicit request 606 for an SL PRS+IUC message (e.g., a preferred or non-preferred resource set), and the UE-A 602 sends an SL PRS 608.

[0052] In one implementation of the first embodiment, the SL TDoA technique involves transmission of SL PRS from multiple anchor UEs to a target UE in the same time slot and interference reduction for each TX UE transmitting the SL PRS with a comb size using a distinct resource element offset. Thus, the TX UE may transmit a PRS request including a PRS configuration such as a PRS time-frequency resource, PRS length, PRS bandwidth, comb pattern, and / or PRS resource element offset for each anchor UE that transmits the SL PRS.

[0053] In another implementation of the first embodiment, one or more anchor UEs may autonomously select resource element offsets according to an anchor UE ID and / or a member ID.

[0054] In a further implementation of the first embodiment, after receiving the PRS request, one or more anchor UEs may coordinate time-frequency resources, comb patterns, and UE-specific resource element offsets for transmitting the SL PRS as shown in FIG. 7.

[0055] 7 is a schematic block diagram illustrating one embodiment of a system 700 having anchor UEs coordinating using IUC information. The system 700 includes a UE-A 702 (e.g., anchor UE), a UE-B 704 (e.g., target UE), a UE-C 706 (e.g., anchor UE), and a UE-D 708 (e.g., anchor UE). The UE-B 704 sends an explicit request for an SL PRS message 710, and the UE-A 702 sends an SL PRS 712. Additionally, the UE-A 702 sends IUC coordination messages 714 and 716.

[0056] In particular embodiments, expected and / or potential resource conflicts may be detected when PRS resources fully and / or partially overlap in time and frequency with reserved resources of other UEs having the same or multiple comb sizes and the same resource element offsets, but a PRS Reference Signal Received Power (“RSRP”) (“PRS-RSRP”) measurement is greater than a configured (or pre-configured) PRS-RSRP threshold compared to the PRS-RSRP measurement of UE-B's reserved resources. Resource conflict information may be transmitted using MAC CE, SCI, or using LPP signaling indicating the time slot, comb pattern, resource element offset within a slot for the comb size to help other UEs reselect PRS resources among any combination of time-frequency resources, comb sizes, and / or resource element offsets.

[0057] In some embodiments, there may be an always-on model in which a roadside unit ("RSU") as an anchor UE transmits SL PRS and may use IUC information to coordinate PRS configuration with other anchor UEs.

[0058] Non-preferred resource set: A transmitting UE may receive a non-preferred resource set, including a PRS resource id, PRS resources within the resource set, PRS slot information, PRS bandwidth information, comb pattern and resource element offset / frequency offset within the PRS resources, and PRS repetition within the resource set. Such non-preferred resource sets may be considered as different muting patterns that consider different combinations of non-preferred resource sets. A UE after receiving non-preferred resource set or muting pattern information as part of the IUC information may choose not to transmit or transmit a zero-power PRS.

[0059] In various embodiments, a muting pattern may be provided by the target UE towards the anchor UE as part of the non-preferred resources, and the muting pattern may include a configuration of zero-energy PRS.

[0060] In another implementation, the muting pattern may include PRS repetition within a resource set, within a resource pool, or excluding some beam ids. In another implementation, muting pattern option 1 may include PRS slot information, PRS frequency information, muting pattern option 2 may include PRS repetition information within a resource set and / or resource pool, muting pattern option 3 may include comb pattern and / or resource element / frequency offset within PRS resources, and the muting pattern may be a combination of other muting pattern options.

[0061] 8 is a flow chart diagram illustrating one embodiment of a method 800 for configuring reference signal communication for multiple devices. In some embodiments, the method 800 is performed by an apparatus such as the remote unit 102. In particular embodiments, the method 800 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0062] In various embodiments, method 800 includes receiving 802 an IUC configuration for SL PRS communication. The IUC configuration includes resource element offsets, frequency offsets, or both, for a plurality of UEs. In some embodiments, method 800 includes transmitting 804 IUC information to the plurality of UEs based at least in part on the IUC configuration and changes to the resource element offsets, frequency offsets, or both, where the IUC information includes preference information, non-preference information, and resource contention information for the SL PRS communication.

[0063] In particular embodiments, the IUC configuration includes, for the plurality of UEs, time-frequency resources, comb sizes, PRS lengths, or a combination thereof. In some embodiments, method 800 further includes determining, for the plurality of UEs, changes to resource element offsets or frequency offsets, or both, and determining IUC information for the plurality of UEs based at least in part on the determined changes to resource element offsets or frequency offsets, or both. In various embodiments, method 800 further includes autonomously selecting resource element offsets according to an anchor UE ID, a member ID, or a combination thereof.

[0064] In one embodiment, the method 800 further includes providing a muting pattern to the anchor UE as part of the non-preferred resources, the muting pattern including a configuration of a zero-energy PRS. In a particular embodiment, the method 800 further includes detecting a potential resource conflict in response to the PRS resource at least partially overlapping in time and frequency with another resource having the same resource element offset and the same comb size or a multiple of the same comb size.

[0065] In one embodiment, an apparatus for wireless communications comprises: a processor; and a memory coupled to the processor; the processor is configured to cause the apparatus to: receive an IUC configuration for SL PRS communication, the IUC configuration including a resource element offset or a frequency offset, or both, for a plurality of UEs; and transmit IUC information to the plurality of UEs based at least in part on the IUC configuration and changes to the resource element offset or the frequency offset, or both, the IUC information including preference information, non-preference information, and resource contention information for the SL PRS communication.

[0066] In a particular embodiment, the processor is further configured to cause the apparatus to autonomously select a resource element offset according to an anchor UE ID, a member ID, or a combination thereof.

[0067] In some embodiments, the processor is further configured to cause the device to provide a muting pattern to the anchor UE as part of the non-preferred resources, the muting pattern including the configuration of a zero-energy PRS.

[0068] In various embodiments, the processor is further configured to cause the apparatus to detect a potential resource conflict in response to the PRS resource at least partially overlapping in time and frequency with another resource having the same resource element offset and the same comb size or a multiple of the same comb size.

[0069] In one embodiment, the IUC configuration includes time-frequency resources, comb sizes, PRS lengths, or a combination thereof for multiple UEs.

[0070] In particular embodiments, the processor is further configured to cause the apparatus to determine, for a plurality of UEs, changes to resource element offsets or frequency offsets, or both, and determine IUC information for the plurality of UEs based at least in part on the determined changes to resource element offsets or frequency offsets, or both.

[0071] In one embodiment, a method in a UE includes receiving an IUC configuration for SL PRS communication, the IUC configuration including a resource element offset or a frequency offset, or both, for a plurality of UEs; and transmitting IUC information to the plurality of UEs based at least in part on the IUC configuration and changes to the resource element offset or the frequency offset, or both, the IUC information including preference information, non-preference information, and resource contention information for the SL PRS communication.

[0072] In a particular embodiment, the IUC configuration includes time-frequency resources, comb sizes, PRS lengths, or a combination thereof for multiple UEs.

[0073] In some embodiments, the method further includes determining, for a plurality of UEs, changes to resource element offsets or frequency offsets, or both, and determining IUC information for the plurality of UEs based at least in part on the determined changes to resource element offsets or frequency offsets, or both.

[0074] In various embodiments, the method further includes autonomously selecting the resource element offset according to an anchor UE ID, a member ID, or a combination thereof.

[0075] In one embodiment, the method further comprises providing a muting pattern to the anchor UE as part of the non-preferred resources, the muting pattern comprising a configuration of zero energy PRS.

[0076] In certain embodiments, the method further includes detecting a potential resource conflict in response to the PRS resource at least partially overlapping in time and frequency with other resources having the same resource element offset and the same comb size or a multiple of the same comb size.

[0077] The embodiments may be embodied in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are intended to be embraced within their scope. [Explanation of symbols]

[0078] 100 Wireless Communication System 102 Remote Unit 104 Network Unit 200 equipment 202 processors 204 memory 206 Input Devices 208 Display 210 Transmitter 212 receiver 300 equipment 302 processor 304 memory 306 Input Devices 308 Display 310 Transmitter 312 Receiver 400 First set of UE cooperation methods 402 UE-A 404 UE-B 406 Explicit Request 408 UE-to-UE Coordination Message 410 Second set of inter-UE cooperation methods 412 UE-A 414 UE-B 416 UE-to-UE Coordination Message 500 Systems 502 UE-A 504 UE-B 506 Explicit Request for IUC 508 IUC Message 510 SL PRS 600 System 602 UE-A 604 UE-B 606 SL Explicit request for PRS+IUC message 608 SL PRS 700 System 702 UE-A 704 UE-B 706 UE-C 708 UE-D 710 SL Explicit request for PRS message 712 SL PRS 714 IUC Collaboration Message 716 IUC Collaboration Message 800 ways

Claims

1. A user equipment (UE), At least one memory; coupled to the at least one memory, to the UE; receiving an Inter-UE Coordination (IUC) configuration for sidelink (SL) positioning reference signal (PRS) communication, the IUC configuration including, for a plurality of UEs, a resource element offset or a frequency offset, or both; transmitting IUC information to the plurality of UEs based at least in part on the IUC configuration and changes to the resource element offset or the frequency offset, or both, the IUC information including preference information, non-preference information, and resource contention information for the SL PRS communication; at least one processor configured to cause UE equipped with.

2. 10. The UE of claim 1, wherein the at least one processor is configured to cause the UE to autonomously select the resource element offset according to an anchor UE identifier (ID), a member ID, or a combination thereof.

3. 2. The UE of claim 1, wherein the at least one processor is configured to cause the UE to provide a muting pattern to an anchor UE as part of non-preferred resources, the muting pattern including a configuration of a zero-energy PRS.

4. The at least one processor may further configure the UE to receive PRS resources, The same resource element offset and The same comb size or a multiple of the same comb size 10. The UE of claim 1, configured to cause detecting a potential resource conflict in response to at least partially overlapping in time and frequency with other resources having the same resource.

5. The UE of claim 1 , wherein the IUC configuration includes, for the plurality of UEs, time-frequency resources, comb sizes, PRS lengths, or a combination thereof.

6. The at least one processor may cause the UE to: determining the changes to the resource element offset or the frequency offset, or both, for the plurality of UEs; determining the IUC information for the plurality of UEs based at least in part on the determined changes to the resource element offset or the frequency offset, or both; The UE of claim 1 , configured to:

7. 1. A method implemented by a user equipment (UE), comprising: receiving an Inter-UE Coordination (IUC) configuration for sidelink (SL) positioning reference signal (PRS) communication, the IUC configuration including resource element offsets or frequency offsets, or both, for a plurality of UEs; transmitting IUC information to the plurality of UEs based at least in part on the IUC configuration and changes to the resource element offset or the frequency offset, or both, the IUC information including preference information, non-preference information, and resource contention information for the SL PRS communication; A method comprising:

8. The method of claim 7 , wherein the IUC configuration includes, for the plurality of UEs, time-frequency resources, comb sizes, PRS lengths, or a combination thereof.

9. determining the changes to the resource element offset or the frequency offset, or both, for the plurality of UEs; determining the IUC information for the plurality of UEs based at least in part on the determined changes to the resource element offset or the frequency offset, or both; 8. The method of claim 7, further comprising:

10. 8. The method of claim 7, further comprising autonomously selecting the resource element offset according to an anchor UE identifier (ID), a member ID, or a combination thereof.

11. The method of claim 7, further comprising providing a muting pattern to the anchor UE as part of non-preferred resources, the muting pattern including a configuration of zero-energy PRS.

12. PRS resources, The same resource element offset and The same comb size or a multiple of the same comb size 8. The method of claim 7, further comprising detecting a potential resource conflict in response to at least partial overlap in time and frequency with other resources having

13. 1. A processor for wireless communications, comprising: coupled to at least one memory, and configured to: receiving an inter-user equipment (UE) coordination (IUC) configuration for sidelink (SL) positioning reference signal (PRS) communication, the IUC configuration including resource element offsets or frequency offsets, or both, for a plurality of UEs; transmitting IUC information to the plurality of UEs based at least in part on the IUC configuration and changes to the resource element offset or the frequency offset, or both, the IUC information including preference information, non-preference information, and resource contention information for the SL PRS communication; a processor comprising at least one controller configured to cause

14. 14. The processor of claim 13, wherein the at least one controller is configured to cause the processor to autonomously select the resource element offset according to an anchor UE identifier (ID), a member ID, or a combination thereof.

15. 14. The processor of claim 13, wherein the at least one controller is configured to cause the processor to provide a muting pattern to the anchor UE as part of non-preferred resources, the muting pattern including configuration of zero-energy PRS.

16. The at least one controller may provide the processor with a PRS resource that: The same resource element offset and The same comb size or a multiple of the same comb size 14. The processor of claim 13, configured to cause detecting a potential resource conflict in response to at least partially overlapping in time and frequency with other resources having

17. 14. The processor of claim 13, wherein the IUC configuration comprises, for the plurality of UEs, time-frequency resources, comb sizes, PRS lengths, or a combination thereof.

18. The at least one controller may cause the processor to: determining the changes to the resource element offset or the frequency offset, or both, for the plurality of UEs; determining the IUC information for the plurality of UEs based at least in part on the determined changes to the resource element offset or the frequency offset, or both; 14. The processor of claim 13 configured to:

19. A user equipment (UE), At least one memory; coupled to the at least one memory, to the UE; transmitting an Inter-UE Coordination (IUC) configuration for sidelink (SL) positioning reference signal (PRS) communication, the IUC configuration including a resource element offset or a frequency offset, or both; receiving IUC information based at least in part on the IUC configuration and changes to the resource element offset or the frequency offset, or both, the IUC information including preference information, non-preference information, and resource contention information for the SL PRS communication; at least one processor configured to cause UE equipped with.

20. 20. The UE of claim 19, wherein the IUC configuration comprises a time-frequency resource, a comb size, a PRS length, or a combination thereof.

Images