Patent Application
20250048327
The subject matter disclosed herein relates generally to wireless communications and more particularly relates to radio access technology (“RAT”)-independent positioning in sidelink.
In wireless networks, although there exists a third generation partnership project (“3GPP”) positioning framework, which enables user equipment (“UE”)-assisted and UE-based positioning methods, there is currently a lack of support for efficient UE-to-UE range/orientation determination, which is essential to support relative positioning applications across different vertical services, e.g., V2X, Public Safety, industrial internet of things (“IIoT”), commercial, or the like.
Disclosed are solutions for RAT-independent positioning in sidelink. The solutions may be implemented by apparatus, systems, methods, or computer program products.
In one embodiment, a first apparatus includes a memory and a processor coupled to the memory. The processor, in one embodiment, is configured to cause the apparatus to transmit, to at least one other device via an SL connection, a RAT-independent positioning information configuration and a RAT-independent reporting configuration. In one embodiment, the processor is configured to cause the apparatus to receive, from the at least one other device via the SL connection, a RAT-independent measurement and location report in response to the RAT-independent positioning information and reporting configuration. In one embodiment, the processor is configured to cause the apparatus to detect an error related to a SL positioning assistance data configuration, measurement, and information report. In one embodiment, the processor is configured to cause the apparatus to transmit, to the at least one other device via the SL connection, an indication of the error and a request for supported RAT-independent positioning capabilities of the at least one other device. In one embodiment, the processor is configured to cause the apparatus to receive, from the at least one other device via the SL connection, a response comprising the supported RAT-independent positioning capabilities of the at least one other device.
A first method, in one embodiment, transmits, to at least one other device via an SL connection, a RAT-independent positioning information configuration and a RAT-independent reporting configuration. In one embodiment, the first method receives, from the at least one other device via the SL connection, a RAT-independent measurement and location report in response to the RAT-independent positioning information and reporting configuration. In one embodiment, the first method detects an error related to a SL positioning assistance data configuration, measurement, and information report. In one embodiment, the first method transmits, to the at least one other device via the SL connection, an indication of the error and a request for supported RAT-independent positioning capabilities of the at least one other device. In one embodiment, the first method receives, from the at least one other device via the SL connection, a response comprising the supported RAT-independent positioning capabilities of the at least one other device.
In one embodiment, a second apparatus includes a memory and a processor coupled to the memory. In one embodiment, the processor is configured to cause the apparatus to receive, from an initiator device via a SL connection, a RAT-independent positioning information configuration and a RAT-independent reporting configuration. In one embodiment, the processor is configured to cause the apparatus to transmit, to the initiator device via the SL connection, a RAT-independent measurement and location report in response to the RAT-independent positioning information and reporting configuration. In one embodiment, the processor is configured to cause the apparatus to detect an error related to a SL positioning assistance data configuration, measurement, and information report. In one embodiment, the processor is configured to cause the apparatus to transmit, to the initiator device via the SL connection, an indication of the error and a response comprising supported RAT-independent positioning capabilities of the apparatus.
In one embodiment, a second method receives, from an initiator device via a SL connection, a RAT-independent positioning information configuration and a RAT-independent reporting configuration. In one embodiment, the second method transmits, to the initiator device via the SL connection, a RAT-independent measurement and location report in response to the RAT-independent positioning information and reporting configuration. In one embodiment, the second method detects an error related to a SL positioning assistance data configuration, measurement, and information report. In one embodiment, the second method transmits, to the initiator device via the SL connection, an indication of the error and a response comprising supported RAT-independent positioning capabilities.
A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:
As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects.
For example, the disclosed embodiments may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function.
Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.
Any combination of one or more computer readable medium 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 the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
More specific examples (a non-exhaustive list) of the storage device would 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 foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.
Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object-oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the “C” programming language, or the like, and/or machine languages such as assembly languages. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the 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”), wireless LAN (“WLAN”), or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider (“ISP”)).
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, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.
Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of 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 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.
As used herein, a list with a conjunction of “and/or” includes any single item in the list or a combination of items in the list. For example, a list of A, B and/or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one or more of” includes any single item in the list or a combination of items in the list. For example, one or more of A, B and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one of” includes one and only one of any single item in the list. For example, “one of A, B and C” includes only A, only B or only C and excludes combinations of A, B and C. As used herein, “a member selected from the group consisting of A, B, and C,” includes one and only one of A, B, or C, and excludes combinations of A, B, and C.” As used herein, “a member selected from the group consisting of A, B, and C and combinations thereof” includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.
Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. This 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, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart diagrams and/or block diagrams.
The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the flowchart diagrams and/or block diagrams.
The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart diagrams and/or block diagrams.
The flowchart diagrams and/or block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products according to various embodiments. In this regard, each block in the flowchart diagrams and/or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).
It should also be noted that, in some alternative implementations, the functions noted in the block 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 upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.
Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.
The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.
Generally, the present disclosure describes systems, methods, and apparatuses for RAT-independent positioning in sidelink. In certain embodiments, the methods may be performed using computer code embedded on a computer-readable medium. In certain embodiments, an apparatus or system may include a computer-readable medium containing computer-readable code which, when executed by a processor, causes the apparatus or system to perform at least a portion of the below described solutions.
Although there exists a 3GPP positioning framework, which enables UE-assisted and UE-based positioning methods, there is currently a lack of support for efficient UE-to-UE range/orientation determination, which is essential to support relative positioning applications across different vertical services, e.g., V2X, Public Safety, IIoT, Commercial, or the like.
3GPP has also supported different positioning technologies including RAT-dependent and RAT-independent positioning methods, which enables different positioning technologies to be used in a complementary fashion to determine and improve the target-UE's location estimate. Currently, RAT-independent positioning has been enabled for the Uu (uplink and downlink), however, the methods to trigger, configure, and report such RAT-independent positioning information between target-UEs and anchor nodes has not yet been solved, especially considering different coverage scenarios including in-coverage, partial coverage, and out-of-coverage scenarios.
This disclosure presents systems, methods, and apparatuses to enable RAT-independent positioning amongst UEs and anchor nodes using the sidelink (“SL”) (PC5) interface.
In one implementation, the RAN 120 is compliant with the 5G system specified in the Third Generation Partnership Project (“3GPP”) specifications. For example, the RAN 120 may be a Next Generation Radio Access Network (“NG-RAN”), implementing New Radio (“NR”) Radio Access Technology (“RAT”) and/or Long-Term Evolution (“LTE”) RAT. In another example, the RAN 120 may include non-3GPP RAT (e.g., Wi-Fi® or Institute of Electrical and Electronics Engineers (“IEEE”) 802.11-family compliant WLAN). In another implementation, the RAN 120 is compliant with the LTE system specified in the 3GPP specifications. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication network, for example Worldwide Interoperability for Microwave Access (“WiMAX”) or IEEE 802.16-family standards, among other networks. The present disclosure is not intended to be limited to the implementation of any wireless communication system architecture or protocol.
In one embodiment, the remote units 105 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), or the like. In some embodiments, the remote units 105 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units 105 may be referred to as the UEs, subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, user terminals, wireless transmit/receive unit (“WTRU”), a device, or by other terminology used in the art. In various embodiments, the remote unit 105 includes a subscriber identity and/or identification module (“SIM”) and the mobile equipment (“ME”) providing mobile termination functions (e.g., radio transmission, handover, speech encoding and decoding, error detection and correction, signaling and access to the SIM). In certain embodiments, the remote unit 105 may include a terminal equipment (“TE”) and/or be embedded in an appliance or device (e.g., a computing device, as described above).
The remote units 105 may communicate directly with one or more of the base units 121 in the RAN 120 via uplink (“UL”) and downlink (“DL”) communication signals. Furthermore, the UL and DL communication signals may be carried over the wireless communication links 123. Here, the RAN 120 is an intermediate network that provides the remote units 105 with access to the mobile core network 140. As described in greater detail below, the base unit(s) 121 may provide a cell operating using a first frequency range and/or a cell operating using a second frequency range.
In some embodiments, the remote units 105 communicate with an application server 151 via a network connection with the mobile core network 140. For example, an application 107 (e.g., web browser, media client, telephone and/or Voice-over-Internet-Protocol (“VoIP”) application) in a remote unit 105 may trigger the remote unit 105 to establish a protocol data unit (“PDU”) session (or other data connection) with the mobile core network 140 via the RAN 120. The mobile core network 140 then relays traffic between the remote unit 105 and the application server 151 in the packet data network 150 using the PDU session. The PDU session represents a logical connection between the remote unit 105 and the User Plane Function (“UPF”) 141.
To establish the PDU session (or PDN connection), the remote unit 105 must be registered with the mobile core network 140 (also referred to as “attached to the mobile core network” in the context of a Fourth Generation (“4G”) system). Note that the remote unit 105 may establish one or more PDU sessions (or other data connections) with the mobile core network 140. As such, the remote unit 105 may have at least one PDU session for communicating with the packet data network 150. The remote unit 105 may establish additional PDU sessions for communicating with other data networks and/or other communication peers.
In the context of a 5G system (“5GS”), the term “PDU Session” refers to a data connection that provides end-to-end (“E2E”) user plane (“UP”) connectivity between the remote unit 105 and a specific Data Network (“DN”) through the UPF 141. A PDU Session supports one or more Quality of Service (“QoS”) Flows. In certain embodiments, there may be a one-to-one mapping between a QoS Flow and a QoS profile, such that all packets belonging to a specific QoS Flow have the same 5G QOS Identifier (“5QI”).
In the context of a 4G/LTE system, such as the Evolved Packet System (“EPS”), a Packet Data Network (“PDN”) connection (also referred to as EPS session) provides E2E UP connectivity between the remote unit and a PDN. The PDN connectivity procedure establishes an EPS Bearer, e.g., a tunnel between the remote unit 105 and a Packet Gateway (“PGW”, not shown) in the mobile core network 140. In certain embodiments, there is a one-to-one mapping between an EPS Bearer and a QoS profile, such that all packets belonging to a specific EPS Bearer have the same QoS Class Identifier (“QCI”).
The base units 121 may be distributed over a geographic region. In certain embodiments, a base unit 121 may also be referred to as an access terminal, an access point, a base, a base station, a Node-B (“NB”), an Evolved Node B (abbreviated as eNodeB or “eNB,” also known as Evolved Universal Terrestrial Radio Access Network (“E-UTRAN”) Node B), a 5G/NR Node B (“gNB”), a Home Node-B, a relay node, a RAN node, or by any other terminology used in the art. The base units 121 are generally part of a RAN, such as the RAN 120, that may include one or more controllers communicably coupled to one or more corresponding base units 121. These and other elements of radio access network are not illustrated but are well known generally by those having ordinary skill in the art. The base units 121 connect to the mobile core network 140 via the RAN 120.
The base units 121 may serve a number of remote units 105 within a serving area, for example, a cell or a cell sector, via a wireless communication link 123. The base units 121 may communicate directly with one or more of the remote units 105 via communication signals. Generally, the base units 121 transmit DL communication signals to serve the remote units 105 in the time, frequency, and/or spatial domain. Furthermore, the DL communication signals may be carried over the wireless communication links 123. The wireless communication links 123 may be any suitable carrier in licensed or unlicensed radio spectrum. The wireless communication links 123 facilitate communication between one or more of the remote units 105 and/or one or more of the base units 121. Note that during NR operation on unlicensed spectrum (referred to as “NR-U”), the base unit 121 and the remote unit 105 communicate over unlicensed (e.g., shared) radio spectrum.
In one embodiment, the mobile core network 140 is a 5GC or an Evolved Packet Core (“EPC”), which may be coupled to a packet data network 150, like the Internet and private data networks, among other data networks. A remote unit 105 may have a subscription or other account with the mobile core network 140. In various embodiments, each mobile core network 140 belongs to a single mobile network operator (“MNO”). The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.
The mobile core network 140 includes several network functions (“NFs”). As depicted, the mobile core network 140 includes at least one UPF 141. The mobile core network 140 also includes multiple control plane (“CP”) functions including, but not limited to, an Access and Mobility Management Function (“AMF”) 143 that serves the RAN 120, a Session Management Function (“SMF”) 145, a Location Management Function (“LMF”) 144, a Unified Data Management function (“UDM”) and a User Data Repository (“UDR”). Although specific numbers and types of network functions are depicted in
The UPF(s) 141 is/are responsible for packet routing and forwarding, packet inspection, QoS handling, and external PDU session for interconnecting Data Network (DN), in the 5G architecture. The AMF 143 is responsible for termination of NAS signaling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. The SMF 145 is responsible for session management (e.g., session establishment, modification, release), remote unit (e.g., UE) IP address allocation & management, DL data notification, and traffic steering configuration of the UPF 141 for proper traffic routing.
The LMF 144 receives positioning measurements or estimates from RAN 120 and the remote unit 105 (e.g., via the AMF 143) and computes the position of the remote unit 105. The UDM is responsible for generation of Authentication and Key Agreement (“AKA”) credentials, user identification handling, access authorization, subscription management. The UDR is a repository of subscriber information and may be used to service a number of network functions. For example, the UDR may store subscription data, policy-related data, subscriber-related data that is permitted to be exposed to third party applications, and the like. In some embodiments, the UDM is co-located with the UDR, depicted as combined entity “UDM/UDR” 149.
In various embodiments, the mobile core network 140 may also include a Policy Control Function (“PCF”) (which provides policy rules to CP functions), a Network Repository Function (“NRF”) (which provides Network Function (“NF”) service registration and discovery, enabling NFs to identify appropriate services in one another and communicate with each other over Application Programming Interfaces (“APIs”)), a Network Exposure Function (“NEF”) (which is responsible for making network data and resources easily accessible to customers and network partners), an Authentication Server Function (“AUSF”), or other NFs defined for the 5GC. When present, the AUSF may act as an authentication server and/or authentication proxy, thereby allowing the AMF 143 to authenticate a remote unit 105. In certain embodiments, the mobile core network 140 may include an authentication, authorization, and accounting (“AAA”) server.
In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice. Here, a “network slice” refers to a portion of the mobile core network 140 optimized for a certain traffic type or communication service. For example, one or more network slices may be optimized for enhanced mobile broadband (“cMBB”) service. As another example, one or more network slices may be optimized for ultra-reliable low-latency communication (“URLLC”) service. In other examples, a network slice may be optimized for machine-type communication (“MTC”) service, massive MTC (“mMTC”) service, Internet-of-Things (“IoT”) service. In yet other examples, a network slice may be deployed for a specific application service, a vertical service, a specific use case, etc.
A network slice instance may be identified by a single-network slice selection assistance information (“S-NSSAI”) while a set of network slices for which the remote unit 105 is authorized to use is identified by network slice selection assistance information (“NSSAI”). Here, “NSSAI” refers to a vector value including one or more S-NSSAI values. In certain embodiments, the various network slices may include separate instances of network functions, such as the SMF 145 and UPF 141. In some embodiments, the different network slices may share some common network functions, such as the AMF 143. The different network slices are not shown in
In one embodiment, the remote unit 105 may be an initiator device and transmits a positioning measurement configuration 125 to a responder device 106. In some embodiments, the initiator device may be a base unit 121, e.g., agNB. In one embodiment, the initiator device receives a positioning/measurement report 127 from the responder device 106. In one embodiment, the initiator device sends the measurement configuration, and/or other configurations, and receives the positioning report 127 over a sidelink connection 115 between the initiator device and the responder device 106. As used herein, a sidelink connection 115 allows remote units 105 to communicate directly with each other (e.g., device-to-device communication) using sidelink (e.g., V2X communication) signals.
While
Moreover, in an LTE variant where the mobile core network 140 is an EPC, the depicted network functions may be replaced with appropriate EPC entities, such as a Mobility Management Entity (“MME”), a Serving Gateway (“SGW”), a PGW, a Home Subscriber Server (“HSS”), and the like. For example, the AMF 143 may be mapped to an MME, the SMF 145 may be mapped to a control plane portion of a PGW and/or to an MME, the UPF 141 may be mapped to an SGW and a user plane portion of the PGW, the UDM/UDR 149 may be mapped to an HSS, etc.
In the following descriptions, the term “RAN node” is used for the base station but it is replaceable by any other radio access node, e.g., gNB, ng-CNB, cNB, Base Station (“BS”), Access Point (“AP”), etc. Further, the operations are described mainly in the context of 5G NR. However, the proposed solutions/methods are also equally applicable to other mobile communication systems supporting sidelink power control for positioning reference signal transmission.
The AS layer (also referred to as “AS protocol stack”) for the User Plane protocol stack 201 consists of at least SDAP, PDCP, RLC and MAC sublayers, and the physical layer. The AS layer for the Control Plane protocol stack 203 consists of at least RRC, PDCP, RLC and MAC sublayers, and the physical layer. The Layer-2 (“L2”) is split into the SDAP, PDCP, RLC and MAC sublayers. The Layer-3 (“L3”) includes the RRC sublayer 245 and the NAS layer 250 for the control plane and includes, e.g., an Internet Protocol (“IP”) layer and/or PDU Layer (not depicted) for the user plane. L1 and L2 are referred to as “lower layers,” while L3 and above (e.g., transport layer, application layer) are referred to as “higher layers” or “upper layers.”
The physical layer 220 offers transport channels to the MAC sublayer 225. The physical layer 220 may perform a Clear Channel Assessment and/or Listen-Before-Talk (“CCA/LBT”) procedure using energy detection thresholds, as described herein. In certain embodiments, the physical layer 220 may send a notification of UL Listen-Before-Talk (“LBT”) failure to a MAC entity at the MAC sublayer 225. The MAC sublayer 225 offers logical channels to the RLC sublayer 230. The RLC sublayer 230 offers RLC channels to the PDCP sublayer 235. The PDCP sublayer 235 offers radio bearers to the SDAP sublayer 240 and/or RRC layer 245. The SDAP sublayer 240 offers QoS flows to the core network (e.g., 5GC). The RRC layer 245 provides for the addition, modification, and release of Carrier Aggregation and/or Dual Connectivity. The RRC layer 245 also manages the establishment, configuration, maintenance, and release of Signaling Radio Bearers (“SRBs”) and Data Radio Bearers (“DRBs”).
The NAS layer 250 is between the UE 205 and the 5GC 215. NAS messages are passed transparently through the RAN. The NAS layer 250 is used to manage the establishment of communication sessions and for maintaining continuous communications with the UE 205 as it moves between different cells of the RAN. In contrast, the AS layer is between the UE 205 and the RAN (e.g., RAN node 210) and carries information over the wireless portion of the network.
As background, NR positioning based on NR Uu signals and standalone access (“SA”) architecture (e.g., beam-based transmissions) is specified in Rel-16. The target use cases also included commercial and regulatory (e.g., emergency services) scenarios, as in Rel-15. The performance requirements are the following (e.g., from TR 38.855, incorporated herein by reference):
3GPP Rel-17 positioning defines the positioning performance requirements for commercial and IIoT use cases as follows (e.g., from TR 38.857, incorporated herein by reference):
Some UE positioning techniques supported in Rel-16 are listed in Table 3. The separate positioning techniques as indicated in Table 3 may be currently configured and performed based on the requirements of the LMF and/or UE capabilities. Note that Table 3 includes Terrestrial Beacon System (“TBS”) positioning based on PRS signals, but only observed time difference of arrival (“OTDOA”) based on LTE signals is supported. The E-CID includes Cell-ID for NR method. The TBS method refers to TBS positioning based on Metropolitan Beacon System (“MBS”) signals.
The transmission of PRS enable the UE to perform UE positioning-related measurements to enable the computation of a UE's location estimate and are configured per Transmission Reception Point (“TRP”), where a TRP may transmit one or more beams.
In one embodiment, the following RAT-dependent positioning techniques may be supported by the system 100:
DL-TDoA: The downlink time difference of arrival (“DL-TDOA”) positioning method makes use of the DL RS Time Difference (“RSTD”) (and optionally DL PRS RS Received Power (“RSRP”) of DL PRS RS Received Quality (“RSRQ”)) of downlink signals received from multiple TPs, at the UE (e.g., remote unit 105). The UE measures the DL RSTD (and optionally DL PRS RSRP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to locate the UE in relation to the neighboring Transmission Points (“TPs”).
DL-AoD: The DL Angle of Departure (“AoD”) positioning method makes use of the measured DL PRS RSRP of downlink signals received from multiple TPs, at the UE. The UE measures the DL PRS RSRP of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to locate the UE in relation to the neighboring TPs.
Multi-RTT: The Multiple-Round Trip Time (“Multi-RTT”) positioning method makes use of the UE Receive-Transmit (“Rx-Tx”) measurements and DL PRS RSRP of downlink signals received from multiple TRPs, measured by the UE and the gNB Rx-Tx measurements (e.g., measured by RAN node) and UL SRS-RSRP at multiple TRPs of uplink signals transmitted from UE, as shown in
As shown in
E-CID/NR E-CID: Enhanced Cell ID (“CID”) positioning method, the position of a UE is estimated with the knowledge of its serving ng-eNB, gNB and cell and is based on LTE signals. The information about the serving ng-eNB, gNB and cell may be obtained by paging, registration, or other methods. NR Enhanced Cell ID (“NR E-CID”) positioning refers to techniques which use additional UE measurements and/or NR radio resource and other measurements to improve the UE location estimate using NR signals.
Although NR E-CID positioning may utilize some of the same measurements as the measurement control system in the RRC protocol, the UE generally is not expected to make additional measurements for the sole purpose of positioning: e.g., the positioning procedures do not supply a measurement configuration or measurement control message, and the UE reports the measurements that it has available rather than being required to take additional measurement actions.
UL-TDoA: The UL TDOA positioning method makes use of the UL TDOA (and optionally UL SRS-RSRP) at multiple reception points (“RPs”) of uplink signals transmitted from the UE. The RPs measure the UL TDOA (and optionally UL SRS-RSRP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the location of the UE.
UL-AoA: The UL Angle of Arrival (“AoA”) positioning method makes use of the measured azimuth and the zenith angles of arrival at multiple RPs of uplink signals transmitted from the UE. The RPs measure A-AoA and Z-AoA of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the location of the UE.
According to Rel-16, the PRS can be transmitted by different base stations (serving and neighboring) using narrow beams over FR1 and FR2 as illustrated in
In one embodiment, the following RAT-independent positioning techniques may be supported by the system 100:
Network-assisted GNSS methods: these methods make use of UEs that are equipped with radio receivers capable of receiving GNSS signals. In 3GPP specifications the term GNSS encompasses both global and regional/augmentation navigation satellite systems. Examples of global navigation satellite systems include GPS, Modernized GPS, Galileo, GLONASS, and BeiDou Navigation Satellite System (“BDS”). Regional navigation satellite systems include Quasi Zenith Satellite System (“QZSS”) while the many augmentation systems, are classified under the generic term of Space Based Augmentation Systems (“SBAS”) and provide regional augmentation services. In this concept, different GNSSs (e.g. GPS, Galileo, etc.) can be used separately or in combination to determine the location of a UE.
Barometric pressure sensor positioning: the barometric pressure sensor method makes use of barometric sensors to determine the vertical component of the position of the UE. The UE measures barometric pressure, optionally aided by assistance data, to calculate the vertical component of its location or to send measurements to the positioning server for position calculation. This method should be combined with other positioning methods to determine the 3D position of the UE.
WLAN positioning: the WLAN positioning method makes use of the WLAN measurements (AP identifiers and optionally other measurements) and databases to determine the location of the UE. The UE measures received signals from WLAN access points, optionally aided by assistance data, to send measurements to the positioning server for position calculation. Using the measurement results and a references database, the location of the UE is calculated. Alternatively, the UE makes use of WLAN measurements and optionally WLAN AP assistance data provided by the positioning server, to determine its location.
Bluetooth positioning: the Bluetooth positioning method makes use of Bluetooth measurements (beacon identifiers and optionally other measurements) to determine the location of the UE. The UE measures received signals from Bluetooth beacons. Using the measurement results and a references database, the location of the UE is calculated. The Bluetooth methods may be combined with other positioning methods (e.g. WLAN) to improve positioning accuracy of the UE.
TBS positioning: a TBS consists of a network of ground-based transmitters, broadcasting signals only for positioning purposes. The current type of TBS positioning signals are the MBS signals and PRS signals. The UE measures received TBS signals, optionally aided by assistance data, to calculate its location or to send measurements to the positioning server for position calculation.
Motion sensor positioning: the motion sensor method makes use of different sensors such as accelerometers, gyros, magnetometers, to calculate the displacement of UE. The UE estimates a relative displacement based upon a reference position and/or reference time. UE sends a report comprising the determined relative displacement which can be used to determine the absolute position. This method should be used with other positioning methods for hybrid positioning.
As illustrated in
Similarly, UE positioning measurements such as Reference Signal Time Difference (“RSTD”) and PRS RSRP measurements are made between beams as opposed to different cells as was the case in LTE. In addition, there are additional UL positioning methods for the network to exploit to compute the target UE's location. Table 4 lists the RS-to-measurements mapping required for each of the supported RAT-dependent positioning techniques at the UE, and Table 5 lists the RS-to-measurements mapping required for each of the supported RAT-dependent positioning techniques at the gNB.
For a conceptual overview of the current implementation in Rel-16, the RAT-independent configurations including A-GNSS (see
The IE A-GNSS-Provide Assistance Data is used by the location server to provide assistance data to enable UE-assisted and UE-based A-GNSS. It may also be used to provide GNSS positioning specific error reasons.
The IE WLAN-ProvideAssistance Data is used by the location server to provide assistance data to enable UE-based and UE-assisted WLAN positioning. It may also be used to provide WLAN positioning specific error reason.
The IE A-GNSS-ProvideLocationInformation is used by the target device to provide location measurements (e.g., pseudo-ranges, location estimate, velocity) to the location server, together with time information. It may also be used to provide GNSS positioning specific error reason.
The IE WLAN-ProvideLocationInformation is used by the target device to provide measurements for one or more WLANs to the location server. It may also be used to provide WLAN positioning specific error reason.
Regarding RAT-dependent positioning measurements, the different DL measurements including DL PRS-RSRP, DL RSTD and UE Rx-Tx Time Difference required for the supported RAT-dependent positioning techniques are shown in Table 6. The following measurement configurations are specified, e.g., in TS 38.215 (incorporated herein by reference):
4 Pair of DL RSTD measurements can be performed per pair of cells. Each measurement is performed between a different pair of DL PRS Resources/Resource Sets with a single reference timing.
8 DL PRS RSRP measurements can be performed on different DL PRS resources from the same cell.
In one embodiment, integrity and reliability of the positioning estimate is defined by the following parameters:
The present disclosure details solutions for supporting RAT-independent positioning using SL (e.g., PC5 interface) for improving absolute and relative positioning/ranging. An overview of the solutions is presented as follows:
As used herein, the term “controller” may refer to a device that controls the ranging session and defines the ranging parameters by sending the ranging control information, the term “controlee” may refer to a device that utilizes the ranging parameters received from the controller by decoding the ranging control message, the term “initiator device” may refer to a device that initiates a SL positioning/ranging session, and the term “responder device” may refer to a device that responds to a SL positioning/ranging session from an initiator device. Further, as used herein, a target-UE may be referred to as a UE of interest whose position (absolute or relative) is to be obtained by the network or by the UE itself.
It is noted that the embodiments below may be implemented in combination with each other to support NR RAT-independent positioning over the SL (PC5) interface. For the purposes of this disclosure, a positioning-related reference signal may be referred to as a reference signal used for positioning procedures/purposes in order to estimate a target-UE's location, e.g., PRS, or based on existing reference signals such as CSI-RS or SRS: a target-UE may be referred to as the device/entity to be localized/positioned. In various embodiments, the term ‘PRS’ may refer to any signal such as a reference signal, which may or may not be used primarily for positioning.
According to a first embodiment, a SL capable device or network entity may configure another UE or group of UEs with RAT-independent positioning methods for the purposes of performing positioning, especially in out-of-coverage scenarios in addition to leveraging hybrid positioning solutions in combination with SL RAT-dependent positioning techniques.
In one embodiment, A-GNSS as a RAT-independent positioning technique is enabled over SL (PC5 interface) via a configuration and corresponding report detailed below. Network-assisted GNSS support over SL can enable rapid acquisition of absolute positioning estimates in addition to relative location estimation (using absolute location estimates). This may include support from global, regional and augmentation satellite systems. A-GNSS configuration can support the following scenarios:
Depending on the requirements of the location request, triggers or events for initiating A-GNSS positioning over SL may include:
In another implementation, the location request may necessitate the use of hybrid positioning based on both RAT-dependent and RAT-independent positioning methods including A-GNSS.
The following exemplary assistance data (A-GNSS configuration) elements may be signaled via PC5 interface to other entities as described above:
As shown in
As shown in
In another implementation, the A-GNSS configuration may be broadcasted by SL capable devices, or network entities such as base stations (e.g., gNBs), roadside units, location servers, or the like or combination thereof.
Furthermore, the A-GNSS assistance data/configuration information may be received in either a:
In another implementation, one of the member UEs in a group may request a SL A-GNSS configuration on behalf of other group members and thereafter all members in the group may receive the A-GNSS configuration.
In yet another realization of the embodiment, the SL assistance data/configuration information elements can be further grouped to functionally serve the following real-time kinematic (“RTK”) service levels:
In another embodiment, barometric pressure sensing as a RAT-independent positioning technique is enabled over SL (PC5 interface) to allow a SL capable device to share measured atmospheric pressure and reference atmospheric pressure information to the other SL capable device in in-coverage, partial coverage and out-of-coverage scenarios. SL Devices embedded with pressure sensors can enable accurate determination of the vertical position, which can aid in 3D location estimation.
Barometric pressure sensing configuration can support the following scenarios:
Depending on the requirements of the location request triggers or events for initiating barometric pressure sensor positioning may include:
The following assistance data (barometric pressure sensor configuration) elements may be signaled via PC5 interface to other entities as described above:
Similar to
In another embodiment, an SL capable device may report the RAT-independent measurement information to another UE or group of UEs using SL (PC5 interface) for the purposes of performing absolute or relative positioning. The RAT-independent information may comprise A-GNSS, motion sensor including barometric pressure sensor metrics, Bluetooth, and WLAN information.
In one embodiment, A-GNSS measurement information can be reported over SL (PC5 interface) to other UEs/SL capable devices. This can be applicable to Scenarios 1-4 as described above with reference to the first embodiment.
Table 8 shows the different A-GNSS measurement and location information elements that may be reported by SL capable devices, which are required to be reported:
In another embodiment, motion sensor measurement information can be reported over SL (PC5 interface) to other UEs/SL capable devices. This can be applicable to Scenarios 1-4 as described above with reference to the first embodiment. The motion sensor may be embedded within a SL capable device and may include accelerometers, gyroscopes, magnetometers or the like.
Table 9 shows the different motion sensor measurement and location information elements that may be reported by SL capable devices, which are required to be reported:
In another embodiment, Bluetooth measurement information can be reported over SL (PC5 interface) to other UEs/SL capable devices. This can be applicable to Scenarios 1-4 as described above with reference to the first embodiment. The Bluetooth chipset may also be embedded within a SL capable device.
Table 10 shows the different Bluetooth measurement and location information elements that may be reported by SL capable devices, which are required to be reported:
In another embodiment, wireless LAN (WLAN or WiFi) positioning as a RAT-independent positioning technique is enabled over SL (PC5 interface), a UE may report to another UE or group of UEs with RAT-independent positioning methods for the purposes of performing WLAN positioning in out-of-coverage scenarios (e.g., using ad-hoc WLAN connections) in addition to leveraging hybrid positioning solutions together with SL RAT-independent techniques.
In one embodiment, WLAN measurement information can be reported over SL (PC5 interface) to other UEs/SL capable devices. This can be applicable to Scenarios 1-4 as described above with reference to the first embodiment. The WLAN chipset may also be embedded within a SL capable device.
Table 11 shows the different WLAN measurement and location information elements that may be reported by SL capable devices, which are required to be reported:
In one embodiment, the initiating SL capable device may transmit a reporting configuration to the responding SL capable devices to configure the responding SL-capable device to report only certain information pertaining to each of the SL RAT-independent positioning methods.
In another embodiment, an SL capable device may initiate SL RAT-independent positioning information exchange with other SL capable devices in a unicast, groupcast or broadcast (depending on Model A or Model B discovery as indicated in TS23.303, incorporated herein by reference) fashion.
In another implementation, a UE within a group may groupcast the SL RAT-independent capability request to all or a subset of member within a group and receive the capability response message from at least one of the members within a group. In some embodiments, the discovery signaling maybe initiated and contains field to search for devices supporting SL RAT-independent capable devices supporting GPS, GNSS, sensors, Bluetooth, etc.
In another embodiment, an SL capable device may report error indications corresponding to at least one or more of the configured RAT-independent positioning methods in the event that there is a radio transmission issue with regards to the configuration and reporting of the aforementioned RAT-independent positioning techniques described above. Exemplary issues may comprise unable to receive the assistance data configuration, radio link failures resulting in retransmissions, poor link quality, multipath, non-line-of-sight (“NLOS”) links, resulting in potential error indications.
An SL capable device or network entity may report an error indication pertaining to SL configuration/assistance data and a measurement location information report.
In other implementations, the error indication is not only applicable to RAT-independent positioning methods but may be equally applicable to the configuration and reporting of SL RAT-dependent positioning methods, e.g., TDoA, RTT, AoA, AOD, E-CID, or the like.
In another implementation, the node transmitting the error indication may retransmit the assistance configuration data or measurement location information report after a configured duration or based on a configured reattempt timer which may comprise of different granularities. In another implementation, the error indication may be associated and signaled with each of the RAT-independent positioning methods such as Bluetooth, Wi-Fi, or the like, and a separate error indication may be associated and signaled for the RAT-dependent positioning method.
As depicted, the transceiver 1525 includes at least one transmitter 1530 and at least one receiver 1535. Here, the transceiver 1525 communicates with one or more base units 121. Additionally, the transceiver 1525 may support at least one network interface 1540 and/or application interface 1545. The application interface(s) 1545 may support one or more APIs. The network interface(s) 1540 may support 3GPP reference points, such as Uu and PC5. Other network interfaces 1540 may be supported, as understood by one of ordinary skill in the art.
The processor 1505, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 1505 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”), a digital signal processor (“DSP”), a co-processor, an application-specific processor, or similar programmable controller. In some embodiments, the processor 1505 executes instructions stored in the memory 1510 to perform the methods and routines described herein. The processor 1505 is communicatively coupled to the memory 1510, the input device 1515, the output device 1520, and the transceiver 1525. In certain embodiments, the processor 1505 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions.
The memory 1510, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 1510 includes volatile computer storage media. For example, the memory 1510 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 1510 includes non-volatile computer storage media. For example, the memory 1510 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 1510 includes both volatile and non-volatile computer storage media.
In some embodiments, the memory 1510 stores data related to RAT-independent positioning in sidelink. For example, the memory 1510 may store parameters, configurations, resource assignments, policies, and the like as described above. In certain embodiments, the memory 1510 also stores program code and related data, such as an operating system or other controller algorithms operating on the user equipment apparatus 1500, and one or more software applications.
The input device 1515, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 1515 may be integrated with the output device 1520, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 1515 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 1515 includes two or more different devices, such as a keyboard and a touch panel.
The output device 1520, in one embodiment, is designed to output visual, audible, and/or haptic signals. In some embodiments, the output device 1520 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 1520 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device 1520 may include a wearable display separate from, but communicatively coupled to, the rest of the user equipment apparatus 1500, such as a smart watch, smart glasses, a heads-up display, or the like. Further, the output device 1520 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.
In certain embodiments, the output device 1520 includes one or more speakers for producing sound. For example, the output device 1520 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the output device 1520 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the output device 1520 may be integrated with the input device 1515. For example, the input device 1515 and output device 1520 may form a touchscreen or similar touch-sensitive display. In other embodiments, the output device 1520 may be located near the input device 1515.
The transceiver 1525 includes at least transmitter 1530 and at least one receiver 1535. The transceiver 1525 may be used to provide UL communication signals to a base unit 121 and to receive DL communication signals from the base unit 121, as described herein. Similarly, the transceiver 1525 may be used to transmit and receive SL signals (e.g., V2X communication), as described herein. Although only one transmitter 1530 and one receiver 1535 are illustrated, the user equipment apparatus 1500 may have any suitable number of transmitters 1530 and receivers 1535. Further, the transmitter(s) 1530 and the receiver(s) 1535 may be any suitable type of transmitters and receivers. In one embodiment, the transceiver 1525 includes a first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum.
In certain embodiments, the first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and the second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum may be combined into a single transceiver unit, for example a single chip performing functions for use with both licensed and unlicensed radio spectrum. In some embodiments, the first transmitter/receiver pair and the second transmitter/receiver pair may share one or more hardware components. For example, certain transceivers 1525, transmitters 1530, and receivers 1535 may be implemented as physically separate components that access a shared hardware resource and/or software resource, such as for example, the network interface 1540.
In various embodiments, one or more transmitters 1530 and/or one or more receivers 1535 may be implemented and/or integrated into a single hardware component, such as a multi-transceiver chip, a system-on-a-chip, an ASIC, or other type of hardware component. In certain embodiments, one or more transmitters 1530 and/or one or more receivers 1535 may be implemented and/or integrated into a multi-chip module. In some embodiments, other components such as the network interface 1540 or other hardware components/circuits may be integrated with any number of transmitters 1530 and/or receivers 1535 into a single chip. In such embodiment, the transmitters 1530 and receivers 1535 may be logically configured as a transceiver 1525 that uses one more common control signals or as modular transmitters 1530 and receivers 1535 implemented in the same hardware chip or in a multi-chip module.
The processor 1505, in one embodiment, transmits, to at least one other device via an SL connection, a RAT-independent positioning information configuration and a RAT-independent reporting configuration. In one embodiment, the processor 1505 receives, from the at least one other device via the SL connection, a RAT-independent measurement and location report in response to the RAT-independent positioning information and reporting configuration. In one embodiment, the processor 1505 detects an error related to a SL positioning assistance data configuration, measurement, and information report. In one embodiment, the processor 1505 transmits, to the at least one other device via the SL connection, an indication of the error and a request for supported RAT-independent positioning capabilities of the at least one other device. In one embodiment, the processor 1505 receives, from the at least one other device via the SL connection, a response comprising the supported RAT-independent positioning capabilities of the at least one other device.
In one embodiment, the apparatus is embodied as at least one of base station, a roadside-unit, an anchor UE, a target-UE, or some combination thereof, and the at least one other device is embodied as at least one of a roadside-unit, an anchor UE, other UEs participating in a positioning session, or some combination thereof.
In one embodiment, the supported RAT-independent positioning capabilities for the SL positioning assistance data configuration comprises an A-GNSS, a barometric pressure sensor, or some combination thereof.
In one embodiment, the processor 1505 transmits, to the at least one other device, a location request, the location request based on a set of requirements, a set of events, or a combination thereof.
In one embodiment, the processor 1505 receives the RAT-independent positioning configuration in a solicitated manner or an unsolicited manner.
In one embodiment, the processor 1505 transmits the RAT-independent positioning configuration in a unicast manner or a groupcast manner.
In one embodiment, the processor 1505 groups the SL positioning assistance data to serve different RTK service levels as part of an SL A-GNSS RAT-independent configuration.
In one embodiment, the processor is configured to cause the apparatus to transmit barometric pressure sensor data as part of an SL barometric pressure sensor RAT-independent configuration.
In one embodiment, the RAT-independent positioning capabilities for the SL positioning reporting configuration and associated measurement and location information report may comprise an A-GNSS, a motion sensor, a WLAN, a Bluetooth device, a barometric pressure sensor, or some combination thereof.
In one embodiment, the error indication is transmitted from a network entity comprising at least one of a base station, a roadside unit, a location server, or a combination thereof in a unicast manner or a groupcast manner.
In one embodiment, the error indication is transmitted from an anchor device with a known location or another SL capable device participating in a positioning session in a unicast manner or a groupcast manner.
In one embodiment, the processor 1505 transmits and receives signals via PC5 RRC, MAC CE, PC5-S, discovery signaling, a dedicated PC5 positioning protocol, or a combination thereof.
In one embodiment, SL RAT-independent positioning capability exchange is supported for a unicast session, a groupcast session, and a broadcast session.
In one embodiment, the processor 1505 receives, from an initiator device via a SL connection, a RAT-independent positioning information configuration and a RAT-independent reporting configuration. In one embodiment, the processor 1505 transmits, to the initiator device via the SL connection, a RAT-independent measurement and location report in response to the RAT-independent positioning information and reporting configuration. In one embodiment, the processor 1505 detects an error related to a SL positioning assistance data configuration, measurement, and information report. In one embodiment, the processor 1505 transmits, to the initiator device via the SL connection, an indication of the error and a response comprising supported RAT-independent positioning capabilities of the apparatus.
As depicted, the transceiver 1625 includes at least one transmitter 1630 and at least one receiver 1635. Here, the transceiver 1625 communicates with one or more remote units 105. Additionally, the transceiver 1625 may support at least one network interface 1640 and/or application interface 1645. The application interface(s) 1645 may support one or more APIs. The network interface(s) 1640 may support 3GPP reference points, such as Uu, N1, N2, N3, N5, N6 and/or N7 interfaces. Other network interfaces 1640 may be supported, as understood by one of ordinary skill in the art.
The processor 1605, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 1605 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”), a digital signal processor (“DSP”), a co-processor, an application-specific processor, or similar programmable controller. In some embodiments, the processor 1605 executes instructions stored in the memory 1610 to perform the methods and routines described herein. The processor 1605 is communicatively coupled to the memory 1610, the input device 1615, the output device 1620, and the transceiver 1625. In certain embodiments, the processor 1605 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio function. In various embodiments, the processor 1605 controls the network apparatus 1600 to implement the above described network entity behaviors (e.g., of the gNB) for RAT-independent positioning in sidelink.
The memory 1610, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 1610 includes volatile computer storage media. For example, the memory 1610 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 1610 includes non-volatile computer storage media. For example, the memory 1610 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 1610 includes both volatile and non-volatile computer storage media.
In some embodiments, the memory 1610 stores data relating to RAT-independent positioning in sidelink. For example, the memory 1610 may store parameters, configurations, resource assignments, policies, and the like as described above. In certain embodiments, the memory 1610 also stores program code and related data, such as an operating system (“OS”) or other controller algorithms operating on the network apparatus 1600, and one or more software applications.
The input device 1615, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 1615 may be integrated with the output device 1620, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 1615 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 1615 includes two or more different devices, such as a keyboard and a touch panel.
The output device 1620, in one embodiment, may include any known electronically controllable display or display device. The output device 1620 may be designed to output visual, audible, and/or haptic signals. In some embodiments, the output device 1620 includes an electronic display capable of outputting visual data to a user. Further, the output device 1620 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.
In certain embodiments, the output device 1620 includes one or more speakers for producing sound. For example, the output device 1620 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the output device 1620 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the output device 1620 may be integrated with the input device 1615. For example, the input device 1615 and output device 1620 may form a touchscreen or similar touch-sensitive display. In other embodiments, all or portions of the output device 1620 may be located near the input device 1615.
As discussed above, the transceiver 1625 may communicate with one or more remote units and/or with one or more interworking functions that provide access to one or more PLMNs. The transceiver 1625 may also communicate with one or more network functions (e.g., in the mobile core network 80). The transceiver 1625 operates under the control of the processor 1605 to transmit messages, data, and other signals and also to receive messages, data, and other signals. For example, the processor 1605 may selectively activate the transceiver (or portions thereof) at particular times in order to send and receive messages.
The transceiver 1625 may include one or more transmitters 1630 and one or more receivers 1635. In certain embodiments, the one or more transmitters 1630 and/or the one or more receivers 1635 may share transceiver hardware and/or circuitry. For example, the one or more transmitters 1630 and/or the one or more receivers 1635 may share antenna(s), antenna tuner(s), amplifier(s), filter(s), oscillator(s), mixer(s), modulator/demodulator(s), power supply, and the like. In one embodiment, the transceiver 1625 implements multiple logical transceivers using different communication protocols or protocol stacks, while using common physical hardware.
The processor 1605, in one embodiment, transmits, to at least one other device via an SL connection, a RAT-independent positioning information configuration and a RAT-independent reporting configuration. In one embodiment, the processor 1605 receives, from the at least one other device via the SL connection, a RAT-independent measurement and location report in response to the RAT-independent positioning information and reporting configuration. In one embodiment, the processor 1605 detects an error related to a SL positioning assistance data configuration, measurement, and information report. In one embodiment, the processor 1605 transmits, to the at least one other device via the SL connection, an indication of the error and a request for supported RAT-independent positioning capabilities of the at least one other device. In one embodiment, the processor 1605 receives, from the at least one other device via the SL connection, a response comprising the supported RAT-independent positioning capabilities of the at least one other device.
In one embodiment, the apparatus is embodied as at least one of base station, a roadside-unit, an anchor UE, a target-UE, or some combination thereof, and the at least one other device is embodied as at least one of a roadside-unit, an anchor UE, other UEs participating in a positioning session, or some combination thereof.
In one embodiment, the supported RAT-independent positioning capabilities for the SL positioning assistance data configuration comprises an A-GNSS, a barometric pressure sensor, or some combination thereof.
In one embodiment, the processor 1605 transmits, to the at least one other device, a location request, the location request based on a set of requirements, a set of events, or a combination thereof.
In one embodiment, the processor 1605 receives the RAT-independent positioning configuration in a solicitated manner or an unsolicited manner.
In one embodiment, the processor 1605 transmits the RAT-independent positioning configuration in a unicast manner or a groupcast manner.
In one embodiment, the processor 1605 groups the SL positioning assistance data to serve different RTK service levels as part of an SL A-GNSS RAT-independent configuration.
In one embodiment, the processor is configured to cause the apparatus to transmit barometric pressure sensor data as part of an SL barometric pressure sensor RAT-independent configuration.
In one embodiment, the RAT-independent positioning capabilities for the SL positioning reporting configuration and associated measurement and location information report may comprise an A-GNSS, a motion sensor, a WLAN, a Bluetooth device, a barometric pressure sensor, or some combination thereof.
In one embodiment, the error indication is transmitted from a network entity comprising at least one of a base station, a roadside unit, a location server, or a combination thereof in a unicast manner or a groupcast manner.
In one embodiment, the error indication is transmitted from an anchor device with a known location or another SL capable device participating in a positioning session in a unicast manner or a groupcast manner.
In one embodiment, the processor 1605 transmits and receives signals via PC5 RRC, MAC CE, PC5-S, discovery signaling, a dedicated PC5 positioning protocol, or a combination thereof.
In one embodiment, SL RAT-independent positioning capability exchange is supported for a unicast session, a groupcast session, and a broadcast session.
In one embodiment, the processor 1605 receives, from an initiator device via a SL connection, a RAT-independent positioning information configuration and a RAT-independent reporting configuration. In one embodiment, the processor 1605 transmits, to the initiator device via the SL connection, a RAT-independent measurement and location report in response to the RAT-independent positioning information and reporting configuration. In one embodiment, the processor 1605 detects an error related to a SL positioning assistance data configuration, measurement, and information report. In one embodiment, the processor 1605 transmits, to the initiator device via the SL connection, an indication of the error and a response comprising supported RAT-independent positioning capabilities of the apparatus.
In one embodiment, the method 1700 begins and transmits 1705, to at least one other device via an SL connection, a RAT-independent positioning information configuration and a RAT-independent reporting configuration. In one embodiment, the method 1700 receives 1710, from the at least one other device via the SL connection, a RAT-independent measurement and location report in response to the RAT-independent positioning information and reporting configuration. In one embodiment, the method 1700 detects 1715 an error related to a SL positioning assistance data configuration, measurement, and information report. In one embodiment, the method 1700 transmits 1720, to the at least one other device via the SL connection, an indication of the error and a request for supported RAT-independent positioning capabilities of the at least one other device. In one embodiment, the method 1700 receives 1725, from the at least one other device via the SL connection, a response comprising the supported RAT-independent positioning capabilities of the at least one other device. The method 1700 ends.
In one embodiment, the method 1800 begins and receives 1805, from an initiator device via a SL connection, a RAT-independent positioning information configuration and a RAT-independent reporting configuration. In one embodiment, the method 1800 transmits 1810, to the initiator device via the SL connection, a RAT-independent measurement and location report in response to the RAT-independent positioning information and reporting configuration. In one embodiment, the method 1800 detects 1815 an error related to a SL positioning assistance data configuration, measurement, and information report. In one embodiment, the method 1800 transmits 1820, to the initiator device via the SL connection, an indication of the error and a response comprising supported RAT-independent positioning capabilities. The method 1800 ends.
A first apparatus is disclosed for RAT-independent positioning in sidelink. The first apparatus may include a UE as described herein, for example, the remote unit 105 and/or the user equipment apparatus 1500, or a network device such as a base unit 121 and/or a network equipment apparatus 1600. In some embodiments, the first apparatus may include a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
In one embodiment, the first apparatus includes a memory and a processor coupled to the memory. The processor, in one embodiment, is configured to cause the apparatus to transmit, to at least one other device via an SL connection, a RAT-independent positioning information configuration and a RAT-independent reporting configuration. In one embodiment, the processor is configured to cause the apparatus to receive, from the at least one other device via the SL connection, a RAT-independent measurement and location report in response to the RAT-independent positioning information and reporting configuration. In one embodiment, the processor is configured to cause the apparatus to detect an error related to a SL positioning assistance data configuration, measurement, and information report. In one embodiment, the processor is configured to cause the apparatus to transmit, to the at least one other device via the SL connection, an indication of the error and a request for supported RAT-independent positioning capabilities of the at least one other device. In one embodiment, the processor is configured to cause the apparatus to receive, from the at least one other device via the SL connection, a response comprising the supported RAT-independent positioning capabilities of the at least one other device.
In one embodiment, the apparatus is embodied as at least one of base station, a roadside-unit, an anchor UE, a target-UE, or some combination thereof, and the at least one other device is embodied as at least one of a roadside-unit, an anchor UE, other UEs participating in a positioning session, or some combination thereof.
In one embodiment, the supported RAT-independent positioning capabilities for the SL positioning assistance data configuration comprises an A-GNSS, a barometric pressure sensor, or some combination thereof.
In one embodiment, the supported RAT-independent positioning capabilities may comprise user equipment (“UE”)-based UE-configured positioning, UE-based network-configured positioning, UE-assisted UE-configured positioning, UE-assisted network-configured positioning, or some combination thereof.
In one embodiment, the processor is configured to cause the apparatus to transmit, to the at least one other device, a location request, the location request based on a set of requirements, a set of events, or a combination thereof.
In one embodiment, the processor is configured to cause the apparatus to receive the RAT-independent positioning configuration in a solicitated manner or an unsolicited manner.
In one embodiment, the processor is configured to cause the apparatus to transmit the RAT-independent positioning configuration in a unicast manner or a groupcast manner.
In one embodiment, the processor is configured to cause the apparatus to group the SL positioning assistance data to serve different RTK service levels as part of an SL A-GNSS RAT-independent configuration.
In one embodiment, the processor is configured to cause the apparatus to transmit barometric pressure sensor data as part of an SL barometric pressure sensor RAT-independent configuration.
In one embodiment, the RAT-independent positioning capabilities for the SL positioning reporting configuration and associated measurement and location information report may comprise an A-GNSS, a motion sensor, a WLAN, a Bluetooth device, a barometric pressure sensor, or some combination thereof.
In one embodiment, the error indication is transmitted from a network entity comprising at least one of a base station, a roadside unit, a location server, or a combination thereof in a unicast manner or a groupcast manner.
In one embodiment, the error indication is transmitted from an anchor device with a known location or another SL capable device participating in a positioning session in a unicast manner or a groupcast manner.
In one embodiment, the processor is configured to cause the apparatus to transmit and receive signals via PC5 RRC, MAC CE, PC5-S, discovery signaling, a dedicated PC5 positioning protocol, or a combination thereof.
In one embodiment, SL RAT-independent positioning capability exchange is supported for a unicast session, a groupcast session, and a broadcast session.
A first method is disclosed for RAT-independent positioning in sidelink. The first method may be performed by a UE as described herein, for example, the remote unit 105 and/or the user equipment apparatus 1500, or a network device such as a base unit 121 and/or a network equipment apparatus 1600. In some embodiments, the first method may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
The first method, in one embodiment, transmits, to at least one other device via an SL connection, a RAT-independent positioning information configuration and a RAT-independent reporting configuration. In one embodiment, the first method receives, from the at least one other device via the SL connection, a RAT-independent measurement and location report in response to the RAT-independent positioning information and reporting configuration. In one embodiment, the first method detects an error related to a SL positioning assistance data configuration, measurement, and information report. In one embodiment, the first method transmits, to the at least one other device via the SL connection, an indication of the error and a request for supported RAT-independent positioning capabilities of the at least one other device. In one embodiment, the first method receives, from the at least one other device via the SL connection, a response comprising the supported RAT-independent positioning capabilities of the at least one other device.
In one embodiment, the first method is performed by a device that is embodied as at least one of base station, a roadside-unit, an anchor UE, a target-UE, or some combination thereof, and the at least one other device is embodied as at least one of a roadside-unit, an anchor UE, other UEs participating in a positioning session, or some combination thereof.
In one embodiment, the supported RAT-independent positioning capabilities for the SL positioning assistance data configuration comprises an A-GNSS, a barometric pressure sensor, or some combination thereof.
In one embodiment, the supported RAT-independent positioning capabilities may comprise user equipment (“UE”)-based UE-configured positioning, UE-based network-configured positioning, UE-assisted UE-configured positioning, UE-assisted network-configured positioning, or some combination thereof.
In one embodiment, the first method transmits, to the at least one other device, a location request, the location request based on a set of requirements, a set of events, or a combination thereof.
In one embodiment, the first method receives the RAT-independent positioning configuration in a solicitated manner or an unsolicited manner.
In one embodiment, the first method transmits the RAT-independent positioning configuration in a unicast manner or a groupcast manner.
In one embodiment, the first method groups the SL positioning assistance data to serve different RTK service levels as part of an SL A-GNSS RAT-independent configuration.
In one embodiment, the first method transmits barometric pressure sensor data as part of an SL barometric pressure sensor RAT-independent configuration.
In one embodiment, the RAT-independent positioning capabilities for the SL positioning reporting configuration and associated measurement and location information report may comprise an A-GNSS, a motion sensor, a WLAN, a Bluetooth device, a barometric pressure sensor, or some combination thereof.
In one embodiment, the error indication is transmitted from a network entity comprising at least one of a base station, a roadside unit, a location server, or a combination thereof in a unicast manner or a groupcast manner.
In one embodiment, the error indication is transmitted from an anchor device with a known location or another SL capable device participating in a positioning session in a unicast manner or a groupcast manner.
In one embodiment, the first method transmits and receives signals via PC5 RRC, MAC CE, PC5-S, discovery signaling, a dedicated PC5 positioning protocol, or a combination thereof.
In one embodiment, SL RAT-independent positioning capability exchange is supported for a unicast session, a groupcast session, and a broadcast session.
A second apparatus is disclosed for RAT-independent positioning in sidelink. The second apparatus may include a UE as described herein, for example, the remote unit 105 and/or the user equipment apparatus 1500, or a network device such as a base unit 121 and/or a network equipment apparatus 1600. In some embodiments, the second apparatus may include a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
In one embodiment, a second apparatus includes a memory and a processor coupled to the memory. In one embodiment, the processor is configured to cause the apparatus to receive, from an initiator device via a SL connection, a RAT-independent positioning information configuration and a RAT-independent reporting configuration. In one embodiment, the processor is configured to cause the apparatus to transmit, to the initiator device via the SL connection, a RAT-independent measurement and location report in response to the RAT-independent positioning information and reporting configuration. In one embodiment, the processor is configured to cause the apparatus to detect an error related to a SL positioning assistance data configuration, measurement, and information report. In one embodiment, the processor is configured to cause the apparatus to transmit, to the initiator device via the SL connection, an indication of the error and a response comprising supported RAT-independent positioning capabilities of the apparatus.
A second method is disclosed for RAT-independent positioning in sidelink. The second method may be performed by a UE as described herein, for example, the remote unit 105 and/or the user equipment apparatus 1500, or a network device such as a base unit 121 and/or a network equipment apparatus 1600. In some embodiments, the second method may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
In one embodiment, the second method receives, from an initiator device via a SL connection, a RAT-independent positioning information configuration and a RAT-independent reporting configuration. In one embodiment, the second method transmits, to the initiator device via the SL connection, a RAT-independent measurement and location report in response to the RAT-independent positioning information and reporting configuration. In one embodiment, the second method detects an error related to a SL positioning assistance data configuration, measurement, and information report. In one embodiment, the second method transmits, to the initiator device via the SL connection, an indication of the error and a response comprising supported RAT-independent positioning capabilities.
Embodiments may be practiced 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 which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
This application claims priority to U.S. Patent Application Ser. No. 63/286,859 entitled “APPARATUSES, METHODS, AND SYSTEMS FOR RAT-INDEPENDENT POSITIONING IN SIDELINK” and filed on Dec. 7, 2021, for Robin Thomas, et al., which is incorporated herein by reference in its entirety.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/IB2022/061894 | 12/7/2022 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 63286859 | Dec 2021 | US |
