Configuring reference signal communications for multiple devices

Abstract

Apparatuses, methods, and systems for configuring reference signal communications for a plurality of devices are disclosed in the present disclosure. A method (800) includes receiving (802), at a user equipment (UE), an inter-UE coordination (IUC) configuration for sidelink (SL) positioning reference signal (PRS) communications. The IUC configuration includes a resource element offset or a frequency offset, or both, for the plurality of UEs. The method (800) includes transmitting (804) IUC information to the plurality of UEs based at least in part on the IUC configuration and a change to the resource element offset or the frequency offset, or both the resource element offset and the frequency offset, and the IUC information includes preferred information, non-preferred information, and resource conflict information for SL PRS communications.

Description

Technical Field

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

[0002] In some wireless communication systems, the positioning method may be user equipment (UE) assisted. In such systems, the positioning method may be inefficient. Summary of the invention

[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 a method includes receiving an inter-UE coordination (IUC) configuration for sidelink (SL) positioning reference signal (PRS) communication at a UE. The IUC configuration includes resource element offsets or frequency offsets or both resource element offsets and frequency offsets for multiple UEs. In some embodiments, the method includes sending IUC information to multiple UEs based at least in part on the IUC configuration and changes to the resource element offsets or frequency offsets or both resource element offsets and frequency offsets, and the IUC information includes preferred information, non-preferred information, and resource conflict information for SL PRS communication.

[0004] An apparatus for configuring reference signal communication for multiple devices includes a processor. In some embodiments, the apparatus includes a memory coupled to the processor, the processor being configured to cause the apparatus to: receive an IUC configuration for SLPRS communication, wherein the IUC configuration includes resource element offsets or frequency offsets or both resource element offsets and frequency offsets for multiple UEs; and send 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 resource element offsets and frequency offsets, and the IUC information includes preferred information, non-preferred information, and resource conflict information for SLPRS communication. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] A more particular description of the embodiments briefly described above will be presented by reference to specific embodiments illustrated in the accompanying drawings. Understanding that these drawings depict only some embodiments and are therefore not to be considered limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the drawings, in which:

[0006] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for configuring reference signal communication for a plurality of devices;

[0007] Figure 2is a schematic block diagram illustrating one embodiment of an apparatus that may be used to configure reference signal communication for multiple devices;

[0008] Figure 3 is a schematic block diagram illustrating one embodiment of an apparatus that may be used to configure reference signal communication for multiple devices;

[0009] Figure 4A and Figure 4B is a schematic block diagram illustrating one embodiment of an inter-UE coordination scheme;

[0010] Figure 5 is a schematic block diagram illustrating one embodiment of a system having an inter-UE coordination scheme including IUC requests;

[0011] Figure 6 is a schematic block diagram illustrating one embodiment of a system having an inter-UE coordination scheme including PRS requests;

[0012] Figure 7 is a schematic block diagram illustrating one embodiment of a system with an anchor UE using IUC information for coordination; and

[0013] Figure 8 is a flow chart illustrating one embodiment of a method for configuring reference signal communications for multiple devices. DETAILED DESCRIPTION

[0014] As will be appreciated by those skilled in the art, various 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 a combination of software aspects and hardware aspects that may be generally referred to as "circuit", "module" or "system" herein. In addition, the embodiments may take the form of a program product 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 certain embodiment, the storage device only uses a signal for accessing a code.

[0015] Certain functional units described in this specification may be labeled as modules to more particularly emphasize their implementation independence. For example, modules may be implemented as hardware circuits, including custom very large scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors (such as logic chips, transistors, or other discrete components). Modules may also be implemented in programmable hardware devices (such as field programmable gate arrays, programmable array logic, programmable logic devices, etc.).

[0016] 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, which may, for example, be organized as objects, processes, or functions. However, the executable files of the identified modules need not be physically located together, but may include different instructions stored in different locations, which, when logically joined together, comprise the module and implement the specified purpose for the module.

[0017] In fact, the module of code can be a single instruction or many instructions, and can even be distributed on a plurality of different code fragments, distributed between different programs and distributed across a plurality of memory devices.Similarly, operating data can be identified and illustrated in this article in the module, and can be embodied in any suitable form, and organized in the data structure of any suitable type.Operational data can be collected as a single data set, or can be distributed in different locations, including on different computer-readable storage devices.When a module or a part of a module is implemented with software, the software part is stored on one or more computer-readable storage devices.

[0018] 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. For example, the storage device may be, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, device, or apparatus, or any suitable combination of the foregoing.

[0019] More specific examples of storage devices (a non-exhaustive list) would include the following: an electrical connection having one or more conductors, 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 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 conjunction with an instruction execution system, apparatus, or device.

[0020] The code for performing the operation of the embodiment can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​(such as Python, Ruby, Java, Smalltalk, C++, etc.) and conventional 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 an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network (including a local area network (LAN) or a wide area network (WAN)), or can be conducted to an external computer (e.g., using an Internet service provider through the Internet).

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

[0022] In addition, the features, structures or characteristics of the described 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, 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 instances, known structures, materials or operations are not shown or described in detail to avoid confusing the various aspects of the embodiments.

[0023] Aspects of the embodiments are described below with reference to schematic flow charts and / or schematic block diagrams of the methods, devices, systems, and program products of the embodiments. It will be understood that each frame of the schematic flow charts and / or schematic block diagrams, and the combination of frames in the schematic flow charts and / or schematic block diagrams can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that instructions executed by the processor of the computer or other programmable data processing device create components for implementing the functions / actions specified in one or more frames of the schematic flow charts and / or schematic block diagrams.

[0024] 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, which includes instructions for implementing the functions / actions specified in one or more boxes of the schematic flowchart and / or schematic block diagram.

[0025] The code can also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operating steps to be executed on the computer, other programmable apparatus or other device, thereby producing 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 boxes of the schematic flowchart and / or schematic block diagram.

[0026] The schematic flow charts and / or schematic block diagrams in the figure illustrate the possible implementation architecture, functions, and operations of the devices, systems, methods, and program products according to various embodiments. In this regard, each box in the schematic flow charts and / or schematic block diagrams can 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.

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

[0028] Although various arrow types and line types can be adopted in flow chart and / or block diagram, various arrow types and line types are understood to 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 period or the monitoring period of the unspecified duration between the enumeration steps of the described embodiment can be indicated by an arrow.It should also be noted that the combination of each frame of block diagram and / or flow chart and the frame in block diagram and / or flow chart can be realized by the system based on special-purpose hardware or the combination of special-purpose hardware and code that performs a specified function or action.

[0029] Descriptions of elements in each figure may refer to elements of subsequent figures. Like reference numerals refer to like elements in all figures, including alternative embodiments of the like elements.

[0030] Figure 1 An embodiment of a wireless communication system 100 for configuring reference signal communication for multiple devices is depicted. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Although in Figure 1 A specific number of remote units 102 and network units 104 are depicted in FIG. 1 , but those 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.

[0031] 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-mounted 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 bracelet, 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 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.

[0032] The network unit 104 may be distributed over a geographical interval. In some embodiments, the network unit 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 data repository (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 elements 104 are generally part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network elements 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 a public switched telephone network. 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.

[0033] In one implementation, the wireless communication system 100 complies with the NR protocol standardized in the 3rd 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, and other protocols. The present disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0034] The network unit 104 can serve multiple remote units 102 within a service area, for example, serving 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.

[0035] In various embodiments, the remote unit 102 may receive an IUC configuration for SL PRS communication. The IUC configuration includes resource element offsets or frequency offsets or both resource element offsets and frequency offsets for multiple UEs. In some embodiments, the remote unit 102 may send IUC information to multiple UEs based at least in part on the IUC configuration and changes to the resource element offsets or frequency offsets or both resource element offsets and frequency offsets, and the IUC information includes preferred information, non-preferred information, and resource conflict information for SL PRS communication. Therefore, the remote unit 102 can be used to configure reference signal communication for multiple devices.

[0036] Figure 2An embodiment of an apparatus 200 that can be used to configure reference signal communication for multiple devices is depicted. Apparatus 200 includes an embodiment of remote unit 102. In addition, remote unit 102 may include processor 202, memory 204, input device 206, display 208, transmitter 210, and 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.

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

[0038] 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, which includes dynamic RAM (DRAM), synchronous dynamic DRAM (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, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile computer storage media 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.

[0039] 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 input 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.

[0040] In one embodiment, the display 208 may include any known electronically controllable display or display device. The display 208 may be designed to output visual signals, auditory signals and / or tactile signals. In some embodiments, the display 208 includes an electronic display capable of outputting visual data to a user. For example, the 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, the display 208 may include a wearable display, such as a smart watch, smart glasses, a head-up display, etc. Further, the 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.

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

[0042] In certain embodiments, the processor 202 is configured to cause the apparatus to: receive an IUC configuration for SL PRS communication, wherein the IUC configuration includes resource element offsets or frequency offsets or both resource element offsets and frequency offsets for a plurality of UEs; and send IUC information to the plurality of UEs based at least in part on the IUC configuration and changes to the resource element offsets or frequency offsets or both resource element offsets and frequency offsets, and the IUC information includes preferred information, non-preferred information, and resource conflict information for SL PRS communication.

[0043] Although only one transmitter 210 and one receiver 212 are illustrated, 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.

[0044] Figure 3 One embodiment of an apparatus 300 that can be used to configure reference signal communication for multiple devices is depicted. The apparatus 300 includes one embodiment of a 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. As can be appreciated, 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.

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

[0046] In certain embodiments of NR, there may be sidelink positioning enhancements considering vehicle-to-everything (V2X), commercial devices, and IIoT. Although there is a network-based absolute positioning framework that enables UE-assisted and UE-based positioning methods, there may not be 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 can be used for in-coverage scenarios, partially covered scenarios, and already covered scenarios.

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

[0048] In some embodiments, DL PRS may be transmitted in a beam. A DL PRS beam is referred to as a DL PRS resource, and a complete set of PRS beams transmitted from a transmission and reception point (TRP) on the same frequency is referred to as a DL PRS resource set. Comb patterns and muting patterns may be configured per resource set.

[0049] In some embodiments, there may be an inter-UE coordination method and procedure for SL PRS that takes into account sharing resources with anchor UEs for certain positioning techniques, such as to avoid half-duplex issues.

[0050] In various NR embodiments, there are different inter-UE coordination schemes as follows: 1) Scheme 1a - preferred resource set; 2) Scheme 1b - non-preferred resource set; and / or Scheme 2 - expected and / or potential resource conflict indication on reserved resources. In schemes 1a and 1b, UE-A sends the resource set sent to UE-B based on explicit trigger information received from UE-B or based on conditional triggers. The signaling container for sending explicit requests and sending resource sets is based on MAC CE and / or sidelink control information (SCI).

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

[0052] In various embodiments, for schemes for inter-UE coordination identified as feasible and / or beneficial, at least the following aspects may be determined: 1) how and / or when UE-A determines the contents of a "resource set", including considerations for UL scheduling; 2) when UE-A sends a "resource set" to UE-B, including which UEs send the "resource set"; 3) how UE-A and UE-B are determined; 4) how UE-A sends a "resource set" to UE-B, including a container for carrying the "resource set" implicitly or explicitly or both implicitly and explicitly; 5) how, when and / or whether UE-B receives the "resource set" and takes the "resource set" into account when making resource selection for its own transmission; and / or 6) how and / or whether to define the relationship between support and / or signaling for inter-UE coordination and propagation types.

[0053] As used herein, the term eNB and / or gNB is used for a base station, but it may be replaced by any other radio access node (e.g., base station (BS), eNB, gNB, AP, NR, etc.). Further, various embodiments may be described in the context of 5G NR; however, the embodiments are equally applicable to other mobile communication systems supporting a serving cell and / or carrier configured for sidelink communication via a UE-to-UE (PC5) interface.

[0054] Figure 4A and Figure 4B 4 is a schematic block diagram illustrating an embodiment of an inter-UE coordination scheme. In a first inter-UE coordination scheme set 400, there are UE-A 402 and UE-B 404. UE-B 404 sends an explicit request 406, and UE-A 402 sends an inter-UE coordination message 408 (e.g., for scheme 1a or scheme 1b). In a second inter-UE coordination scheme set 410, there are UE-A 412 (e.g., condition-based triggering) and UE-B 414. UE-A 412 sends an inter-UE coordination message 416 (e.g., for scheme 1a, scheme 1b, and scheme 2).

[0055] In a first embodiment, sidelink positioning techniques (such as TDoA, multi-UE RTT) require the target UE to send and receive SL PRS from multiple anchor UEs. These anchor UEs support positioning for the target UE through the SL interface (e.g., by sending and / or receiving reference signals for positioning, providing positioning-related information, etc.). In addition, resource coordination is required between multiple transmitting UEs to align SL PRS resources.

[0056] Preferred resource set: The transmitting UE may receive a preferred resource set including PRS resources in the form of one or more combinations of the following items: PRS resource id, PRS resources within the resource set, PRS time slot information, PRS bandwidth information, comb pattern within the PRS resource, and resource element offset / frequency offset 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 among candidate resource selections. In the preferred resource set, the TX UE that sends the SL PRS may be a target UE (e.g., an anchor UE that needs to exchange PRS resource configuration using an IUC message including IUC information). The IUC information may need to be exchanged between the target UE and the anchor UE so that the target UE may send a PRS request (e.g., a request to send a PRS request to one or more anchor UEs) Figure 6), and may indicate a preferred transmission of the SL PRS from the anchor UE to the target UE, which may include time-frequency resources, time slot information, PRS length, PRS bandwidth, PRS resource set identifier (ID), comb pattern, and / or resource element offset for each anchor UE that sends the SL PRS, which may be implicitly determined by a rule or explicitly indicated in the 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.

[0057] Figure 5 1 is a schematic block diagram illustrating one embodiment of a system 500 having an inter-UE coordination 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 an IUC 506, the UE-A 502 sends an IUC message 508 (e.g., a preferred resource set or a non-preferred resource set), and the UE-B 504 sends an SL PRS 510.

[0058] Figure 6 6 is a schematic block diagram illustrating one embodiment of a system 600 having an inter-UE coordination scheme including PRS requests. 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 for a SLPRS+IUC message 606 (e.g., a preferred resource set or a non-preferred resource set), and the UE-A 602 sends a SL PRS 608.

[0059] In one implementation of the first embodiment, the SL TDoA technique requires that SL PRS be transmitted from multiple anchor UEs toward a target UE in the same time slot, and different resource element offsets are used to reduce interference in terms of comb size for each TX UE that sends the SL PRS. Therefore, the TX UE may send a PRS request containing a PRS configuration (such as PRS time-frequency resources, length, bandwidth, comb pattern, and / or PRS resource element offset for each anchor UE that sends the SL PRS).

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

[0061] In another 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 sending SL PRS, such as Figure 7 as shown in .

[0062] Figure 7 7 is a schematic block diagram illustrating one embodiment of a system 700 with an anchor UE that coordinates using IUC information. The system 700 includes UE-A 702 (e.g., anchor UE), UE-B 704 (e.g., target UE), UE-C 706 (e.g., anchor UE), and UE-D 708 (e.g., anchor UE). UE-B 704 sends an explicit request for a SL PRS message 710, and UE-A 702 sends a SL PRS 712. In addition, UE-A 702 sends an IUC coordination message 714 and an IUC coordination message 716.

[0063] In certain embodiments, if the PRS resources fully and / or partially overlap in time and frequency with other UE reserved resources (which have the same or multiple comb size and the same resource element offset), and the PRS reference signal received power (RSRP) (PRS-RSRP) measurement is greater than a configured (or preconfigured) PRS-RSRP threshold compared to the PRS-RSRP measurement of the reserved resources of UE-B, an expected and / or potential resource conflict can be detected. Resource conflict information can be sent using MAC CE, SCI, or using LPP signaling, which indicates the time slot, comb pattern, resource element offset within the slot for the comb size to help other UEs reselect PRS resources in any combination of time-frequency resources, comb size, and / or resource element offset.

[0064] In some embodiments, there may be an always on model where a road side unit (RSU) as an anchor UE sends a SL PRS and may coordinate PRS configuration with other anchor UEs using IUC information.

[0065] Non-preferred resource set: The transmitting UE may receive a non-preferred resource set containing the following items: PRS resource id, PRS resource within the resource set, PRS time slot information, PRS bandwidth information, comb pattern and resource element offset / frequency offset within the PRS resource, and repetition of PRS within the resource set. Considering different combinations of non-preferred resource sets, such non-preferred resource sets may be regarded as different muting patterns. After receiving the non-preferred resource set or muting pattern information as part of the IUC information, the UE may choose not to send or send zero-power PRS.

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

[0067] In another implementation, the muting pattern may include repetition of PRS within a resource set, within a resource pool, or excluding some beam IDs. In another implementation, muting pattern option 1 may include PRS time slot information, PRS frequency information, muting pattern option 2 may include repetition information of PRS within a resource set and / or resource pool, muting pattern 3 may include comb patterns within PRS resources and / or resource element offsets / frequency offsets, and the muting pattern may be a combination of another muting pattern option.

[0068] Figure 8 8 is a flow chart 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 certain 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.

[0069] In various embodiments, the method 800 includes receiving 802 an IUC configuration for SL PRS communication. The IUC configuration includes a resource element offset or a frequency offset or both the resource element offset and the frequency offset for a plurality of UEs. In some embodiments, the method 800 includes sending 804 IUC information to a plurality of UEs based at least in part on the IUC configuration and a change to the resource element offset or the frequency offset or both the resource element offset and the frequency offset, and the IUC information includes preferred information, non-preferred information, and resource conflict information for SLPRS communication.

[0070] In some embodiments, the IUC configuration includes time-frequency resources, comb size, PRS length, or a combination of the above items for multiple UEs. In some embodiments, the method 800 also includes: determining a change to a resource element offset or a frequency offset or both a resource element offset and a frequency offset for multiple UEs; and determining ICU information for multiple UEs based at least in part on the determined change to the resource element offset or the frequency offset or both a resource element offset and a frequency offset. In various embodiments, the method 800 also includes autonomously selecting a resource element offset based on an anchor UE ID, a member ID, or a combination of the above items.

[0071] In one embodiment, the method 800 further comprises providing a muting pattern to the anchor UE as part of the non-preferred resources, wherein the muting pattern comprises a configuration for a zero energy PRS. In certain embodiments, the method 800 further comprises detecting a potential resource conflict in response to the PRS resource at least partially overlapping in time and frequency with other resources, the other resources having: the same resource element offset; and the same comb size or a multiple of the same comb size.

[0072] In one embodiment, a device for wireless communication includes: a processor; a memory coupled to the processor, the processor being configured to cause the device to: receive an IUC configuration for SL PRS communication, wherein the IUC configuration includes resource element offsets or frequency offsets or both resource element offsets and frequency offsets for multiple UEs; and send 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 resource element offsets and frequency offsets, and the IUC information includes preferred information, non-preferred information, and resource conflict information for SL PRS communication.

[0073] In some embodiments, 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.

[0074] In some embodiments, the processor is further configured to cause the apparatus to provide a muting pattern to the anchor UE as part of the non-preferred resources, and the muting pattern includes a configuration for a zero energy PRS.

[0075] 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 other resources having: the same resource element offset; and the same comb size or a multiple of the same comb size.

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

[0077] In certain embodiments, the processor is also configured to cause the device to: determine, for multiple UEs, a change to a resource element offset or a frequency offset, or both a resource element offset and a frequency offset; and determine ICU information for multiple UEs based at least in part on the determined change to a resource element offset or a frequency offset, or both a resource element offset and a frequency offset.

[0078] In one embodiment, a method at a UE includes: receiving an IUC configuration for SL PRS communication, wherein the IUC configuration includes resource element offsets or frequency offsets or both resource element offsets and frequency offsets for multiple UEs; and sending IUC information to multiple UEs based at least in part on the IUC configuration and changes to the resource element offsets or frequency offsets or both resource element offsets and frequency offsets, and the IUC information includes preferred information, non-preferred information, and resource conflict information for SL PRS communication.

[0079] In certain embodiments, the IUC configuration includes time-frequency resources, comb size, PRS length, or a combination thereof for multiple UEs.

[0080] In some embodiments, the method also includes: determining, for multiple UEs, changes to resource element offsets or frequency offsets, or both resource element offsets and frequency offsets; and determining ICU information for multiple UEs based at least in part on the determined changes to resource element offsets or frequency offsets, or both resource element offsets and frequency offsets.

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

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

[0083] 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, the other resources having: the same resource element offset; and the same comb size or a multiple of the same comb size.

[0084] Embodiments may be practiced in other specific forms. The described embodiments are considered to be illustrative in all aspects only, and not restrictive. Therefore, the scope of the present invention is indicated by the appended claims rather than by the foregoing description. All changes that fall within the equivalent meanings and equivalent scopes of the claims will be included within the scope of the claims.

Claims

1. A user equipment (UE), comprising: at least one memory; as well as at least one processor, the at least one processor being coupled to the at least one memory and configured to cause the UE to: Receiving an inter-UE coordination (IUC) configuration for sidelink (SL) positioning reference signal (PRS) communication, wherein the IUC configuration includes resource element offsets or frequency offsets or both resource element offsets and frequency offsets for a plurality of UEs; and IUC information is sent to the multiple UEs based at least in part on the IUC configuration and the changes to the resource element offset or the frequency offset or both the resource element offset and the frequency offset, and the IUC information includes preferred information, non-preferred information, and resource conflict information for the SL PRS communication.

2. The UE of claim 1, wherein the at least one processor is configured to enable the UE to autonomously select the resource element offset according to an anchor UE identifier (ID), a member ID, or a combination thereof. 3 . 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, and the muting pattern comprises a configuration for a zero energy PRS.

4. The UE of claim 1 , wherein the at least one processor is configured to cause the UE to detect a potential resource conflict in response to a PRS resource at least partially overlapping in time and frequency with other resources, the other resources having: the same resource element offset; and The same comb size or a multiple of said same comb size.

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

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

7. A method performed by a user equipment (UE), the method comprising: Receiving an inter-UE coordination (IUC) configuration for sidelink (SL) positioning reference signal (PRS) communication, wherein the IUC configuration includes resource element offsets or frequency offsets or both resource element offsets and frequency offsets for a plurality of UEs; and IUC information is sent to the multiple UEs based at least in part on the IUC configuration and the changes to the resource element offset or the frequency offset or both the resource element offset and the frequency offset, and the IUC information includes preferred information, non-preferred information, and resource conflict information for the SL PRS communication.

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

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

10. 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 an anchor UE as part of non-preferred resources, wherein the muting pattern includes a configuration for a zero energy PRS.

12. The method of claim 7, further comprising 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 said same comb size.

13. A processor for wireless communication, comprising: at least one controller coupled to the at least one memory and configured to cause the processor to: Receiving an inter-user equipment (UE) coordination (IUC) configuration for sidelink (SL) positioning reference signal (PRS) communication, wherein the IUC configuration includes resource element offsets or frequency offsets or both resource element offsets and frequency offsets for a plurality of UEs; and IUC information is sent to the multiple UEs based at least in part on the IUC configuration and the changes to the resource element offset or the frequency offset or both the resource element offset and the frequency offset, and the IUC information includes preferred information, non-preferred information, and resource conflict information for the SL PRS communication.

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 based on an anchor UE identifier (ID), a member ID, or a combination thereof.

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

16. The processor of claim 13, wherein the at least one controller is configured to cause the processor to detect a potential resource conflict in response to a 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 said same comb size.

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

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

19. A user equipment (UE), comprising: at least one memory; as well as at least one processor, the at least one processor being coupled to the at least one memory and configured to cause the UE to: sending an inter-UE coordination (IUC) configuration for sidelink (SL) positioning reference signal (PRS) communication, wherein the IUC configuration includes a resource element offset or a frequency offset or both the resource element offset and the frequency offset; and IUC information is received based at least in part on the IUC configuration and a change to the resource element offset or the frequency offset or both, and the IUC information includes preferred information, non-preferred information, and resource conflict information for the SLPRS communication.

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

Images