Patent Application
20250112732
This present application claims the benefit of International Application No. PCT/CN2022/097870, “Frame Number Offset for Positioning of a Remote UE” filed on Jun. 9, 2022, which is incorporated herein by reference in its entirety.
This disclosure relates to wireless communications, and specifically to methods of determining the location of a remote UE receiving service from a cellular network via a relay UE.
The background description provided herein is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent the work is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.
Sidelink communication technologies enable direct communication between two devices without the participation of a base station in the transmission and reception of data traffic. Sidelink communication can be used to extend the service of a cellular network to a mobile device beyond the coverage of the base stations.
Aspects of the disclosure provide a method. The method can include receiving a system frame number (SFN) from a base station by a first relay UE, determining a timeline of the SFN based on one or more synchronization signals by the first relay UE, determining a timeline of a direct frame number (DFN) based on a reference time source by the first relay UE, computing an SFN-DFN offset based on the difference between the timeline of the SFN and the timeline of the DEN by the first relay UE, and transmitting the SFN-DFN offset and the DEN to a receiving UE on a sidelink interface.
In an embodiment, the receiving UE is a remote UE. In an embodiment, the receiving UE is a second relay UE. In an embodiment, the SFN-DFN offset is transmitted in a message of a PC5 radio resource control (PC5-RRC) protocol. In an embodiment, the message is an RRCReconfigurationSidelink message. n an embodiment, the message is an UEAssistanceInformationSidelink message. In an embodiment, the SFN-DFN offset comprises at least one of a frame-level offset, a subframe-level offset, and a slot-level offset. In an embodiment, the SFN-DFN offset is transmitted in a medium access control (MAC) control element (CE) of a PC5 MAC protocol. In an embodiment, the SFN-DFN offset is transmitted in a sidelink control information (SCI) transmission.
Aspects of the disclosure provide an apparatus comprising circuitry. The circuitry is configured to receive a system frame number (SFN) from a base station by a first relay UE, determine a timeline of the SFN based on one or more synchronization signals by the first relay UE, determine a timeline of a direct frame number (DFN) based on a reference time source by the first relay UE, compute an SFN-DFN offset based on the difference between the timeline of the SFN and the timeline of the DFN by the first relay UE, and transmit the SFN-DFN offset and the DEN to a receiving UE on a sidelink interface.
Aspects of the disclosure provide a non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform the method.
Various embodiments of this disclosure that are proposed as examples will be described in detail with reference to the following figures, wherein like numerals reference like elements, and wherein:
In certain cellular systems, such as 3GPP 5G New Radio (NR) from Rel-17 onward, a first user equipment (UE) may function in a relaying relationship with a second UE. For example, the first UE may be out of direct cellular coverage or in poor coverage, while the second UE is in good coverage, and the second UE may deliver communications between the first UE and the serving cellular network. In this scenario, the first UE may be referred to as a remote UE and the second UE may be referred to as a relay UE. The remote UE may be referred to as being in “indirect service” or having an “indirect path” to the network, while the relay UE may be referred to as being in “direct service” or having a “direct path” to the network. The relay and remote UEs may communicate via a sidelink interface, also called a PC5 interface, in which radio resources are used for direct communication between UEs without an intervening network node. This PC5 interface is contrasted with a Uu interface between a UE and a network node, which is used for conventional direct service. In the ordinary course of direct cellular service, a UE is aware of the system timing of the serving node, such as an eNode B (eNB) or gNode B (gNB). The system timing is represented by a system frame number (SFN), representing an essentially arbitrary time reference point for the serving cell. The timeline of the cell is divided into frames of a consistent length (for example, 10 ms), and the frame is subdivided into subframes of a consistent length (for example, 1 ms). Depending on the numerology of the radio configuration of the cell, the subframe may be further subdivided into slots of a consistent length, for example, 0.25 ms when the serving carrier has a subcarrier spacing of 60 kHz. Each frame is assigned an SFN, in a cycle of fixed length, for example, a cycle of 1024 frames starting at SFN #0, resulting in a range of SFN values from 0 to 1023. This structure allows the UE to have an unambiguous time reference for events on the radio interface. For example, a periodically occurring radio configuration may be described as occurring at SFN #x with a periodicity of N frames, meaning that the configuration occurs in SFNs x, x+N, x+2N, x+3N, and so on.
There are many scenarios in which it is desirable to know the location of a UE, such as for an emergency call, location-based services, network optimization, and so on. For a UE in direct service, the system may exploit timing or directional information about the cellular air interface to determine the location of the UE. As one example, the UE may measure the relative timing of signals arriving from a plurality of transmit points (TPs) of the network to determine the time difference of arrival (TDOA) values for a plurality of pairs of TPs. A TP may also be capable of reception and may accordingly be described as a transmit-receive point (TRP). In the context of downlink positioning, only the transmission function is relevant. The determined TDOA values may then be used, at a position calculation entity that may be located in the UE or in a network node such as a location management function (LMF) or Secure User Plane Location (SUPL) location platform (SLP), to determine an approximate location for the UE, according to well-known methods. As another example, the UE may receive signals from specific beams transmitted by a plurality of TPs, and measurement information on the beams may be combined, by the position calculation entity, with angular information describing the directions of transmission of the beams and with location information of the TPs to determine an approximate location for the UE, again according to well-known methods. These methods of positioning may be described as downlink time difference of arrival (DL-TDOA) and downlink angle of departure (DL-AoD) positioning methods, respectively. The downlink measurements that facilitate these positioning methods may be taken over a set of downlink positioning reference signals (DL-PRS), sometimes shortened to positioning reference signals (PRS) when the direction of transmission is unambiguous. The DL-PRS transmissions from the TPs may be configured in a coordinated way, and their configurations may be provided to the UE in the form of assistance data to allow the UE to measure the DL-PRS transmissions.
This disclosure is directed to the establishment of a system timeline facilitating the use of downlink positioning when the UE to be positioned is operating as a remote UE.
The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.
Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
As one example, DL-PRS configurations may have a dependency on the system frame number (SFN) of the frame in which they occur. The DL-PRS may be provided from a TP on a periodic basis, with the periodicity defined relative to the SFN cycle. Accordingly, the UE may need to know the SFN of the cell from which it measures DL-PRS, and configuration information may be provided as part of the assistance data to facilitate this knowledge. For example, an SFN offset for a neighbor cell to be measured may be included in the assistance data, describing the SFN timeline of the neighbor cell relative to the SFN of an assistance data reference cell. The assistance data reference cell may be the UE's serving cell. In the event that the assistance data reference cell is different from the UE's serving cell, well-known methods exist for enabling the UE to determine the SFN of the cells in the assistance data, provided the assistance data include at least one cell for which the UE can obtain the SFN. This one cell need not be the same as the assistance data reference cell nor as the UE's serving cell.
However, if the UE to be positioned is a remote UE, such as the remote UE 301 shown in
Timing on the sidelink interface is defined by a Direct Frame Number (DFN), which is assigned by the transmitting UE. For example, the relay UE in correspondence with the remote UE may provide a DFN as part of the MasterInformationBlockSidelink message. The DFN determines the frame number in which the sidelink synchronization signal block (S-SSB) is transmitted, and the S-SSB allows the receiving UE (in this case, the remote UE) to detect the frame boundary. In consequence, it may be assumed that the remote UE knows the DFN and the frame boundary timing on the sidelink interface, as provided by the relay UE.
The DFN indicated by the relay UE may be computed by a variety of methods, depending on the synchronization source used by the relay UE. For example, if the relay UE is synchronized to a global navigation satellite system (GNSS), the DFN may be derived from GNSS time by a formula (see for instance section 5.8.12 of 3GPP TS 38.331). A similar formula may be used to determine the subframe and slot timing of the PC5 interface. If the relay UE is synchronized to the serving cell, the DFN, the associated subframe, and slot timing may be derived directly from the SFN and other timing information on the Uu interface. In some cases, the relay UE may be synchronized to the serving gNB and align its DFN timeline with the SFN timeline. However, the remote UE may not be able to detect the synchronization in these cases since the remote UE does not have direct knowledge of the synchronization source of the relay UE.
Meanwhile, the relay UE may be in direct service, and thus be aware of the SFN, the frame boundary timing, and/or the slot timing provided by the serving base station. The radio frame size may be identical on the sidelink and Uu interfaces (for instance, 10 ms), meaning that the SFN on the Uu interface and the DEN on the sidelink interface are related by an offset. In an embodiment, this SFN-DFN offset may be signaled to the remote UE by the relay UE. In another embodiment, the SFN-DFN offset may be reported by the relay UE to the base station via signaling (e.g., a SidelinkUEInformation message of an RRC protocol), and the SFN-DFN offset may be signaled by the base station (for instance, via a Uu RRC message) over the indirect path to the remote UE. However, the embodiment in which the offset is signaled to the remote UE by the relay UE may be preferred since the relay UE uniquely has direct knowledge of both the SFN and DFN timelines. It is noted that significant drift in the value of the offset would not be anticipated, since the relay UE maintains awareness of the timeline of the serving cell and can keep the DFN timeline consistent with the serving cell's SFN timeline. However, if the SFN-DFN offset does drift over time or change, the relay UE may transmit a new value of the SFN-DFN offset to the remote UE.
In some embodiments, the SFN-DFN offset may also comprise an indication of the carrier numerology in use between the relay UE 402 and the serving cell. This may be necessary, for instance, to facilitate correct interpretation by the remote UE 401 of a slot offset signaled as part of the SFN-DFN offset. In particular, the slot offset may rely on joint signaling to indicate the carrier numerology and a corresponding slot offset, whose range may depend on the indicated carrier numerology. The SFN-DFN offset may be signaled in any message carried on the PC5 interface, such as a MasterInformationBlockSidelink message, an RRCReconfigurationSidelink message, a UEAssistanceInformationSidelink message, a new message specific to updating the timing information, and so on.
In an embodiment, this SFN-DFN offset may be signaled via a PC5 medium access control (MAC) control element (CE) or a sidelink control information (SCI) to the remote UE 401 by the relay UE 402. In another embodiment, this SFN-DFN offset may be signaled via a relay discovery message over PC5 to the remote UE 401 by the relay UE 402. In an additional embodiment, this SFN-DFN offset may be signaled together with one or more positioning system information blocks (posSIBs) over the PC5 interface to the remote UE 401 by the relay UE 402. The SFN-DFN offset may be signaled as an optional field of a message, with specified behavior by the remote UE 401 when the optional field is absent. As one example, the remote UE 401 may assume that the SFN-DEN offset is zero (that is, the SFN and DEN timelines are substantially aligned) when the optional field is not provided. Alternatively, the relay UE 402 may provide an explicit indication when the SFN and DEN timelines are substantially aligned, such as a boolean flag, a zero value for the signaled SFN-DFN offset, and so on.
Relay UE 603 can further maintain its own DFN timeline B, which may be the same as or different from DEN timeline A. (For example, relay UEs A and B may be synchronized to different sources.) Since the relay UE 603 knows both the SFN timeline and DEN timeline B, the relay UE 603 can derive an SFN-DFN offset B using the methods described above. The relay UE 603 can then transmit DFN timeline B (for example, in the MasterInformationBlockSidelink message), and relay UE 703 also delivers to the remote UE 604 the computed value of SFN-DFN offset B, using any of the methods previously described. From this information, the remote UE 604 can determine the SFN timeline by applying the received SFN-DFN offset B to the DFN timeline B.
In a multi-hop environment, if a remote UE can receive the timing information (e.g., DEN timeline and SFN-DFN offset) from two or more relay UEs, the remote UE may prioritize the timing information during positioning from the relay UE with fewer hops to the serving cell. For example, refer to
In some embodiments, sidelink communication between the remote and relay UEs may operate on a plurality of sidelink frequencies or carriers, referred to as multi-carrier operation or carrier aggregation (CA). In such a case, it may be necessary for the remote UE to determine which sidelink frequency the received SFN-DFN offset relates to (for instance, if the sidelink frequencies have independent timelines). Accordingly, the relay UE may indicate a frequency identifier along with the signaled SFN-DFN offset, indicating which sidelink frequency the offset corresponds to. This frequency identifier may take the form of an absolute radio frequency channel number (ARFCN), an index, and so on. (In an NR system, an ARFCN may be referred to as an NR-ARFCN, for disambiguation from other systems using similar terminology.) Similarly, Uu communication between the relay UE and the gNB may operate in a CA configuration, and in this case, the relay UE may indicate which Uu frequency the offset corresponds to.
At S710, an SFN timeline can be received by a relay UE from a base station. The SFN timeline is maintained by the base station.
At S720, an SFN-DFN offset can be determined based on the received SFN timeline and a DEN timeline. The DEN timeline is maintained by the relay UE.
At S730, an SFN-DFN offset and a DEN timeline can be transmitted by the relay UE to a remote UE.
At S740, an SFN timeline can be determined based on a received SFN-DFN offset and a received DEN timeline by a remote UE. The process 700 can proceed to S799 and terminate at S799.
In various examples, the processing circuitry 810 can include circuitry configured to perform the functions and processes described herein in combination with software or without software. In various examples, the processing circuitry 810 can be a digital signal processor (DSP), an application specific integrated circuit (ASIC), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), digitally enhanced circuits, or comparable devices or a combination thereof.
In some other examples, the processing circuitry 810 can be a central processing unit (CPU) configured to execute program instructions to perform various functions and processes described herein. Accordingly, the memory 820 can be configured to store program instructions. The processing circuitry 810, when executing the program instructions, can perform the functions and processes. The memory 820 can further store other programs or data, such as operating systems, application programs, and the like. The memory 820 can include non-transitory storage media, such as a read only memory (ROM), a random access memory (RAM), a flash memory, a solid state memory, a hard disk drive, an optical disk drive, and the like.
In an embodiment, the RF module 830 receives a processed data signal from the processing circuitry 810 and converts the data signal to beamforming wireless signals that are then transmitted via antenna arrays 840, or vice versa. The RF module 830 can include a digital to analog converter (DAC), an analog to digital converter (ADC), a frequency up converter, a frequency down converter, filters and amplifiers for reception and transmission operations. The RF module 830 can include multi-antenna circuitry for beamforming operations. For example, the multi-antenna circuitry can include an uplink spatial filter circuit, and a downlink spatial filter circuit for shifting analog signal phases or scaling analog signal amplitudes. The antenna arrays 840 can include one or more antenna arrays.
The apparatus 800 can optionally include other components, such as input and output devices, additional or signal processing circuitry, and the like. Accordingly, the apparatus 800 may be capable of performing other additional functions, such as executing application programs, and processing alternative communication protocols.
The processes and functions described herein can be implemented as a computer program which, when executed by one or more processors, can cause the one or more processors to perform the respective processes and functions. The computer program may be stored or distributed on a suitable medium, such as an optical storage medium or a solid-state medium supplied together with, or as part of, other hardware. The computer program may also be distributed in other forms, such as via the Internet or other wired or wireless telecommunication systems. For example, the computer program can be obtained and loaded into an apparatus, including obtaining the computer program through physical medium or distributed system, including, for example, from a server connected to the Internet.
The computer program may be accessible from a computer-readable medium providing program instructions for use by or in connection with a computer or any instruction execution system. The computer-readable medium may include any apparatus that stores, communicates, propagates, or transports the computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer-readable medium can be magnetic, optical, electronic, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. The computer-readable medium may include a computer-readable non-transitory storage medium such as a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a magnetic disk and an optical disk, and the like. The computer-readable non-transitory storage medium can include all types of computer-readable medium, including magnetic storage medium, optical storage medium, flash medium, and solid state storage medium.
While aspects of the present disclosure have been described in conjunction with the specific embodiments thereof that are proposed as examples, alternatives, modifications, and variations to the examples may be made. Accordingly, embodiments as set forth herein are intended to be illustrative and not limiting. There are changes that may be made without departing from the scope of the claims set forth below.
| Number | Date | Country | Kind |
|---|---|---|---|
| PCT/CN2022/097870 | Jun 2022 | WO | international |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/CN2023/092910 | 5/9/2023 | WO |
